Multi-type multi-tenant system implementation system based on product delivery implementation
By establishing a tenant creation subsystem, a business creation subsystem, a testing and debugging subsystem, and an experience subsystem, the complexity of inter-module delivery in multi-module products is resolved, and unified management and data confidentiality of the multi-tenant system are achieved.
Patent Information
- Application Number
- CN202410956443.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-17
- Publication Date
- 2024-11-01
AI Technical Summary
Existing technologies struggle to achieve closed-loop delivery in multi-module products across multiple teams, ensuring smooth communication between modules, and also present high operational barriers.
The system employs a tenant creation subsystem, a business creation subsystem, a testing and debugging subsystem, and an experience subsystem. Through isolation mechanisms and SSO single sign-on, a multi-tenant system is implemented to ensure smooth communication and unified management between various business modules.
It has achieved unified management of the multi-tenant system, ensuring smooth communication between various business modules and improving data security and operational rationality.
Smart Images

Figure CN118890293A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of multi-tenant technology, and more specifically to a multi-type multi-tenant system implementation system based on product delivery. Background Art
[0002] Multi-tenancy Architecture is a software architecture model that supports providing services and resources to multiple users (tenants) in a single software instance. The traditional solution is to create a multi-tenant based on the company. Based on this, when a product is composed of multiple modules under multiple teams, it is complex to connect the modules and achieve unified management. Artificial intelligence systems, in particular, have a high operational threshold. For example, for the same business, some modules may need to be opened to the customer operation team for operation and management, and some modules may require AI trainers from professional companies to perform synchronous operation and management.
[0003] Therefore, when a product is composed of multiple modules under multiple teams, how to complete closed-loop delivery, ensure smooth channels between modules, and achieve unified management of multiple tenants is an urgent problem that technical personnel in this field need to solve. Summary of the invention
[0004] In view of the above problems, the present invention provides a multi-type multi-tenant system implementation system based on product delivery implementation to at least solve some of the technical problems mentioned in the above background technology.
[0005] In order to achieve the above object, the present invention adopts the following technical solution:
[0006] A multi-type multi-tenant system implementation system based on product delivery, including: tenant creation subsystem, business creation subsystem, testing and debugging subsystem and experience subsystem;
[0007] The tenant creation subsystem is used for each enterprise to create account information;
[0008] The business creation subsystem is used to create internal business and / or external business of each enterprise; every two menu function units under the internal business or the external business are connected through an interface unit; an isolation mechanism is provided between the internal business and the external business;
[0009] The testing and debugging subsystem is used to test the created internal business and / or external business, and debug the created internal business and / or external business according to the test results;
[0010] The experience subsystem is used to preview the internal business and / or external business that have completed testing and debugging, and optimize the system according to the preview results.
[0011] Furthermore, each of the menu function units includes a plurality of function sub-units; each of the function sub-units includes a plurality of function items.
[0012] Furthermore, the business creation subsystem also includes a definition unit;
[0013] The definition unit is used to decide whether to deliver the menu function unit to a tenant administrator using an enterprise account for operation, or to an internal tenant administrator corresponding to the enterprise for operation, or to a system provider for operation based on the content, nature and preset specialization level of each menu function unit.
[0014] Furthermore, the isolation mechanism includes database isolation, file isolation and logical isolation.
[0015] Further, the testing and debugging subsystem includes a functional testing module, a performance testing module and a safety testing module;
[0016] The functional testing module is used to test the implementation effect of the business function;
[0017] The performance testing module is used to test the response time, throughput and resource utilization of the system;
[0018] The security testing module is used to test the system's level of protection against illegal intrusion and level of protection against data leakage.
[0019] Further, the test and debugging subsystem also includes an administrator allocation module;
[0020] The administrator allocation module is used to allocate an administrator port to the created account, and enable corresponding function items for the created internal business and / or external business through the administrator port.
[0021] Furthermore, the experience subsystem includes a test-end experience module and an enterprise-end experience module; the experience content of the test-end experience module and the enterprise-end experience module includes functional experience, performance experience, interface and interaction experience, security experience, ease of use experience and service and support experience.
[0022] Further, it also includes a tenant login and use subsystem;
[0023] The tenant login subsystem is used for each enterprise login account to use the created services; each enterprise uses SSO single sign-on when logging in to the account.
[0024] Furthermore, the system front end shares cookies, and the system back end shares a Redis data center.
[0025] Furthermore, both the internal business and the external business use session-cookie to implement sessions.
[0026] It can be seen from the above technical solutions that, compared with the prior art, the present invention discloses a multi-type multi-tenant system implementation system based on product delivery, which has the following beneficial effects:
[0027] The present invention can create multiple tenants based on the business of an enterprise, ensure smooth channels between multiple business modules, and further realize unified management of multiple tenants.
[0028] The present invention can selectively deliver functional projects to corresponding teams for operation, making the entire business model more reasonable.
[0029] Other features and advantages of the present invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the present invention.
[0030] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.
[0032] Figure 1 A schematic diagram of a system framework for implementing a multi-type multi-tenant system based on product delivery provided in an embodiment of the present invention.
[0033] Figure 2 A schematic diagram of the business creation and operation process provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0034] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0035] See also Figure 1 and Figure 2 As shown, the embodiment of the present invention discloses a multi-type multi-tenant system implementation system based on product delivery, including: a tenant creation subsystem, a business creation subsystem, a testing and debugging subsystem and an experience subsystem; wherein:
[0036] The tenant creation subsystem is used by each enterprise to create account information;
[0037] The business creation subsystem is used to create internal business and / or external business of each enterprise; every two menu function units under internal business or external business are connected through an interface unit; an isolation mechanism is set between internal business and external business;
[0038] A testing and debugging subsystem, used to test the created internal services and / or external services, and debug the created internal services and / or external services according to the test results;
[0039] The experience subsystem is used to preview the internal and / or external services that have completed testing and debugging, and optimize the system based on the preview results.
[0040] Based on the system in the embodiment of the present invention, an internal tenant system or an external tenant system can be created by selecting menu functions under internal business or external business; compared with the prior art of creating multiple tenants based on the company, the multi-tenant system created based on the business in the embodiment of the present invention is more convenient for unified management, and can also ensure smooth channels between multiple menu function units under each same business; in addition, in the embodiment of the present invention, an isolation mechanism is provided between internal business and external business to ensure that the relevant data of each business will not be accessed by other business terminals, thereby improving the confidentiality of each business.
[0041] Next, each of the above subsystems will be described in further detail.
[0042] 1. Tenant creation subsystem
[0043] The tenant creation subsystem is used by each enterprise to create account information; the account information includes enterprise-related information and enterprise account information; specifically:
[0044] The company-related information includes the company name, English name, company logo, default language (i.e., the language displayed by the system after logging into the account), login restrictions (i.e., whether multiple logins are allowed at the same time), login method (i.e., login by username or password, etc.), and company configuration, etc.; the company configuration includes: 1) support for extended configuration with additional information in the company dimension, such as configuring the company's contact person, office address, etc.; 2) support for extended configuration with additional information in the business dimension, such as which sub-bots are used in each module corresponding to the business, initial threshold configuration, some initialization configuration information, etc.; 3) support for extended configuration with additional information in the user dimension, such as the user's occupation information, user's education information, user's interests, hobbies, etc.;
[0045] Corporate account information includes bank account information, account balance, transaction records, payment password and account authorization, etc.
[0046] 2. Business creation subsystem
[0047] (1) Internal and external business
[0048] The business creation subsystem includes an internal selection module and an external selection module; the internal selection module is used to create internal business for each enterprise; the external selection module is used to create external business for each enterprise; in the specific creation process, each enterprise can create internal business or external business separately according to its actual situation, or create internal business and external business at the same time; based on this, multiple enterprises and multiple business projects can be connected to share data and resources; internal business and external business can be shown in Table 1 below:
[0049] Table 1
[0050]
[0051]
[0052] (2) Menu function unit
[0053] Each internal business or external business includes multiple menu function units and an interface unit. Every two menu function units under the internal business or external business are connected through the interface unit. Among them, multiple menu functions can meet the needs of different enterprises. Through open interfaces and standardized data formats, the system integration can be made simpler and more efficient. Each menu function unit includes multiple functional sub-units; each functional sub-unit includes multiple functional projects. For example, the functional sub-unit includes knowledge base and speech management, wherein the knowledge base includes FAQ knowledge base and intelligent questioning and other functional projects; speech management includes speech type and speech library and other functional projects. Based on this, complex business logic and functions are split into small functional project blocks that are easy to manage and maintain, thereby ensuring the stability and scalability of business projects.
[0054] The connections between the menu function units under each business are connected through AIPI, so that any menu function unit under the business is no longer isolated, and unified login, unified authentication, unified business data connection, unified management and maintenance, etc. between all menu function units can be well completed; for example, account A can only see the data of the algorithm module + engineering module under account A, and account B can only see the data of the algorithm module + engineering module under account B; when creating business A, the algorithm module and engineering module belong to A, and when creating business B, the algorithm module and engineering module belong to B.
[0055] (3) Isolation mechanism
[0056] There is an isolation mechanism between different enterprises, and there is also an isolation mechanism between the internal business and the external business of the same enterprise. For example, in Table 1 above, the butler business and spokesperson business data of Company A are isolated, but the multiple menu function data under the same business are connected. The isolation mechanism includes database isolation, file isolation and logical isolation, etc. It ensures that the relevant data of each business will not be accessed by other business terminals, thereby improving the confidentiality of each business. Specifically:
[0057] (1) When the amount of business data is less than the preset value, the tenant identification solution is adopted by the tenant ID field. The implementation steps are as follows: 1) Design the database table: Add a tenant ID field (such as tenant_id) in the shared database table; this field is used to identify the tenant to which each data belongs; 2) Modify the query statement: When querying data, always add a filter condition for the tenant ID in the query statement; for example, use WHERE tenant_id = 'X';
[0058] (2) When the amount of business data is greater than or equal to the preset value, an independent database system is provided for each tenant. The implementation steps are as follows: 1) Create an independent database: Create an independent database instance for each tenant; for example, use a database management system such as MySQL to execute the CREATE DATABASE tenantX command for each tenant, where tenantX is the tenant's identifier; 2) Assign permissions: Assign access rights to each tenant's database; use the GRANT command to assign tenants full access rights to their databases, such as GRANT ALL PRIVILEGES ON tenantX.*TO'tenantX_user'@'localhost'; 3) Application configuration: Configure multiple database connections in the application so that it can connect to each tenant's database; dynamically connect to the corresponding database instance based on the tenant's identifier.
[0059] (4) Definition unit
[0060] The business creation subsystem also includes a definition unit, which is used to decide whether to deliver the menu function unit to a tenant administrator using an enterprise account for operation, or to an internal tenant administrator corresponding to the enterprise for operation, or to a professional company for operation based on the content, nature and preset specialization level of each menu function unit; for example, if the nature of the functional items under the business is external, it is delivered to a tenant administrator using an enterprise account for operation; if the nature of the functional items under the business is internal, it is delivered to the internal tenant administrator corresponding to the enterprise for operation; or it is delivered to a system provider for operation; for example, after the system provider delivers the system to Company A, Company A can maintain simple data, while for some more complex content such as knowledge base management and model training and reasoning, the system provider will provide internal operation and maintenance.
[0061] 3. Test and debug subsystem
[0062] The testing and debugging subsystem includes a functional testing module, a performance testing module and a security testing module; among them: the functional testing module is used to test the implementation effect of business functions; the performance testing module is used to test the system's response time, throughput and resource utilization; the security testing module is used to test the system's level of prevention of illegal intrusion and prevention of data leakage.
[0063] In addition, the test and debugging subsystem also includes an administrator allocation module, which is used to allocate an administrator port for the created account, and enable corresponding functional items for the created internal business and / or external business through the administrator port.
[0064] 4. Experience subsystem
[0065] The experience subsystem includes a test-end experience module and an enterprise-end experience module; the experience content of the test-end experience module and the enterprise-end experience module includes functional experience, performance experience, interface and interaction experience, security experience, usability experience, and service and support experience; among which:
[0066] (1) Functional experience: whether the basic functions of the system meet the needs. For example, whether an e-commerce system can support basic operations such as browsing products, adding to shopping carts, and settlement and payment; and whether these functions are stable and smooth during operation, and whether there will be any lag or crash;
[0067] (2) Performance experience: whether the system's response speed, loading time, processing speed, and other aspects meet the preset requirements; for example, whether the results can be displayed quickly when searching for products; whether the order can be processed quickly after submission; whether the system's performance can remain stable under high concurrency or large data volumes, and whether there will be phenomena such as slow page loading and operation delays;
[0068] (3) Interface and interactive experience: whether the system is concise, clear, beautiful, and meets the user's usage requirements;
[0069] (4) Security experience: that is, whether the system can provide comprehensive security measures during use, such as data encryption, identity authentication, and anti-attack measures, to ensure the security of user data and the smooth progress of transactions;
[0070] (5) Usability experience: whether the system can provide clear operation instructions and feedback to reduce learning costs and usage difficulty; in addition, the system also needs to consider the usage habits and needs of different user groups and provide personalized settings and options to meet the usage needs of different users.
[0071] (6) Service and support experience: Users may encounter various problems or need help when using the application system. The system needs to provide a complete service and support system, such as online customer service, help documents, user communities, etc., so that users can get help and solve problems in a timely manner.
[0072] During the specific implementation process, the test end can first conduct experience and perform initial optimization of the system based on the experience results; then the system is delivered to tenants, who will experience and provide feedback through the enterprise end, and the system will be optimized again based on the tenants' feedback.
[0073] In another embodiment, it also includes a tenant login subsystem, which is used for each enterprise login account to use the created services; each enterprise uses SSO single sign-on when logging in to the account, achieving the effect of logging in at one place and logging out at multiple places.
[0074] In another embodiment, the system front end shares cookies, and the system back end shares a Redis data center; both internal and external businesses use session-cookies to implement sessions;
[0075] Next, explain Cookie and Session:
[0076] (1) Cookies
[0077] As we all know, HTTP is a stateless protocol (it has no memory for transaction processing, and the server will not save any session information each time the client and server complete a session); so in order for the server to distinguish different clients, it must actively maintain a state, which is used to inform the server whether the previous and next requests come from the same browser. This state can be achieved through Cookies.
[0078] Characteristics of cookies: Cookies are stored on the client side and can be tampered with at will. They are insecure and have size limits, with a maximum of 4kb and a quantity limit. Generally, a browser can store no more than 20 cookies for a website. Browsers generally only allow 300 cookies to be stored. Cookies cannot cross domains, but first-level and second-level domain names can be shared (based on domain).
[0079] (2)Session
[0080] The abstract concept of Session is Session, which is an abstraction of the interaction between users and servers in the process of stateless protocol communication in order to achieve interruption / resume operation. Specifically, it is a Session structure generated by the server, which can be saved in a variety of ways, such as memory, database, file, etc. Large websites generally have a dedicated Session server cluster to save user sessions.
[0081] Principle process:
[0082] Client: The user sends a request to the server for the first time;
[0083] Server: Receives the data and automatically creates a specific Session / SessionID for the user to identify the user and track the user's current session process;
[0084] Client: The browser receives the response and obtains the session information, and will bring the Session / SessionID in the next request;
[0085] Server: After the server extracts the data, it compares it with the locally saved SessionID to find the session of the specific user and obtain the session status.
[0086] At this point, the communication between the client and the server becomes stateful communication;
[0087] (3) The specific authentication steps of Session-Cookie are analyzed as follows:
[0088] Client: Send login information username / password to the server to request login verification;
[0089] Server: Verify the login information, automatically create a Session after verification (save the Session in memory or Redis), then generate a unique identification string session identity credential session_id (usually called sid) for the Session, and set this unique identifier in the response header Set-Cookie; (Note: the sid can be encrypted using a signature, and the server will decrypt it according to the corresponding secret key)
[0090] Client: After receiving the response from the server, it will parse the response header and automatically save the sid in the local cookie. The browser will automatically attach the cookie information under the domain name to the request header during the next HTTP request.
[0091] Server: When receiving a client request, it will parse the sid in the request header cookie, and then use this sid to find the client's sid saved by the server, and then determine whether the request is legal;
[0092] The SSO single sign-out technology is used to achieve the effect of users logging out from one place and multiple places. Single sign-out means that when a user logs out from the single sign-on system, his / her login status will be cancelled in all related systems or applications, ensuring that the user can safely exit all systems.
[0093] The implementation mechanism is as follows: when the user chooses to log out, the single sign-on system will trigger a logout request; the request will be sent to all associated systems or applications to notify them to log out the user; after each system or application receives the logout request, it will perform the corresponding logout operation, such as clearing session information, logging out the user, etc.
[0094] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.
[0095] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A multi-type multi-tenant system implementation system based on product delivery, characterized in that: include: Tenant creation subsystem, business creation subsystem, testing and debugging subsystem, and experience subsystem; The tenant creation subsystem is used for each enterprise to create account information; The business creation subsystem is used to create internal business and / or external business of each enterprise; every two menu function units under the internal business or the external business are connected through an interface unit; an isolation mechanism is provided between the internal business and the external business; The testing and debugging subsystem is used to test the created internal business and / or external business, and debug the created internal business and / or external business according to the test results; The experience subsystem is used to preview the internal business and / or external business that have completed testing and debugging, and optimize the system according to the preview results.
2. According to claim 1, a multi-type multi-tenant system implementation system based on product delivery is characterized in that: Each of the menu function units includes a plurality of function sub-units; each of the function sub-units includes a plurality of function items.
3. According to claim 1, a multi-type multi-tenant system implementation system based on product delivery is characterized in that: The business creation subsystem also includes a definition unit; The definition unit is used to decide whether to deliver the menu function unit to a tenant administrator using an enterprise account for operation, or to an internal tenant administrator corresponding to the enterprise for operation, or to a system provider for operation based on the content, nature and preset specialization level of each menu function unit.
4. According to the multi-type multi-tenant system implementation system based on product delivery implementation as described in claim 1, it is characterized in that: The isolation mechanism includes database isolation, file isolation and logical isolation.
5. According to the multi-type multi-tenant system implementation system based on product delivery implementation as described in claim 1, it is characterized in that: The testing and debugging subsystem includes a functional testing module, a performance testing module and a safety testing module; The functional testing module is used to test the implementation effect of the business function; The performance testing module is used to test the response time, throughput and resource utilization of the system; The security testing module is used to test the system's level of protection against illegal intrusion and level of protection against data leakage.
6. A multi-type multi-tenant system implementation system based on product delivery implementation according to claim 2, characterized in that: The test and debugging subsystem also includes an administrator allocation module; The administrator allocation module is used to allocate an administrator port to the created account, and enable corresponding function items for the created internal business and / or external business through the administrator port.
7. According to the multi-type multi-tenant system implementation system based on product delivery implementation as described in claim 1, it is characterized in that: The experience subsystem includes a test-end experience module and an enterprise-end experience module; the experience content of the test-end experience module and the enterprise-end experience module includes functional experience, performance experience, interface and interaction experience, security experience, ease of use experience, and service and support experience.
8. According to the multi-type multi-tenant system implementation system based on product delivery implementation as claimed in claim 1, it is characterized in that: It also includes a tenant login and usage subsystem; The tenant login subsystem is used for each enterprise login account to use the created services; each enterprise uses SSO single sign-on when logging in to the account.
9. A multi-type multi-tenant system implementation system based on product delivery implementation according to claim 8, characterized in that: The system front end shares cookies, and the system back end shares the Redis data center.
10. A multi-type multi-tenant system implementation system based on product delivery implementation according to claim 1, characterized in that: Both the internal and external businesses use session-cookies to implement sessions.
