CN114331359A - Multi-tenant management method - Google Patents
Multi-tenant management method Download PDFInfo
- Publication number
- CN114331359A CN114331359A CN202111632615.2A CN202111632615A CN114331359A CN 114331359 A CN114331359 A CN 114331359A CN 202111632615 A CN202111632615 A CN 202111632615A CN 114331359 A CN114331359 A CN 114331359A
- Authority
- CN
- China
- Prior art keywords
- tenant
- data
- request
- tenants
- receiving
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the disclosure discloses a multi-tenant management method, which comprises the following steps: after receiving a configuration request for the tenants, configuring the relationships among the tenants for the tenants; when a request for data issuing aiming at any configured tenant is received, generating a data issuing task so as to send data to be issued to the any tenant according to the data issuing task; and/or generating a data uploading task after any tenant generates data so that any tenant uploads the generated data according to the uploading task. By facing all tenants to carry out relationship configuration and data uploading and issuing, unified management and control of all tenants are realized. And then overcome the defect that in the correlation technique, can't carry out unified management and control to the tenant.
Description
Technical Field
The disclosure relates to the technical field of data processing, in particular to a multi-tenant management method.
Background
The multi-tenant technology is a software architecture technology, which is used for exploring and implementing how to share the same system or program components in a multi-user environment, and can still ensure the isolation of data among users.
In the related art, a large-medium enterprise generally includes a plurality of subsidiaries, and a group cannot uniformly control the subsidiaries, so that the data of all the subsidiaries cannot be further summarized and analyzed.
Disclosure of Invention
The main purpose of the present disclosure is to provide a multi-tenant management method.
In order to achieve the above object, according to a first aspect of the present disclosure, there is provided a multi-tenant management method including: after receiving a configuration request for the tenants, configuring the relationships among the tenants for the tenants; when a request for data issuing aiming at any configured tenant is received, generating a data issuing task so as to send data to be issued to the any tenant according to the data issuing task; and/or generating a data uploading task after any tenant generates data so that any tenant uploads the generated data according to the uploading task.
Optionally, the method further comprises: receiving a data uploading request sent by a preset service after the preset service is triggered to be operated by a service; and generating a data uploading task based on the content of the request indication so that a preset tenant uploads the data based on the task indication.
Optionally, the method further comprises: and after receiving a data issuing request sent by a preset service, generating a data issuing task so as to issue the data requested to be issued to a preset tenant.
Optionally, after receiving a request for data delivery for any configured tenant, the method further includes: based on the identification of any tenant, converting the identification of the data to be issued; and sending the converted data to be issued to the any tenant.
Optionally, after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant includes: after receiving a request for adding the main tenant, performing tenant relationship configuration on the added main tenant and other tenants; and/or after receiving a request for adding a sub-tenant under any main tenant, performing relationship configuration on any main tenant and the added sub-tenant.
Optionally, after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant includes: after receiving a configuration request for migrating the child tenant, reestablishing the tenant relationship between the child tenant and other tenants; and converting the identifier of the sub-tenant to obtain the identifier of the migrated tenant.
Optionally, after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant includes: after receiving an invitation request of a child tenant, sending the invitation request to the child tenant; and if the authorization indication of the sub-tenant is received, establishing the tenant relationship between the sub-tenant and other tenants.
Optionally, after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant includes: and after receiving a request for deleting the child tenant, releasing the relationship between the child tenant to be deleted and other tenants.
Optionally, the method further comprises: after receiving a request for configuring the permission of the tenant, configuring a preset permission for the tenant, wherein the method comprises the following steps: after receiving a request for authorizing the preset authority of the main tenant, authorizing the preset authority for the main tenant; and/or after receiving a request for changing the authority of the main tenant, changing the authority of the main tenant.
According to a second aspect of the present disclosure, a computer-readable storage medium is provided, in which computer instructions are stored, and the computer instructions are configured to enable the computer to execute the multi-tenant management method according to any one of the implementation manners of the first aspect
In the multi-tenant management method in the embodiment of the present disclosure, the method includes: after receiving a configuration request for the tenants, configuring the relationships among the tenants for the tenants; when a request for data issuing aiming at any configured tenant is received, generating a data issuing task so as to send data to be issued to the any tenant according to the data issuing task; and/or generating a data uploading task after any tenant generates data so that any tenant uploads the generated data according to the uploading task. By facing all tenants to carry out relationship configuration and data uploading and issuing, unified management and control of all tenants are realized. And then overcome the defect that in the correlation technique, can't carry out unified management and control to the tenant.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow diagram of a method of multi-tenant management according to an embodiment of the present disclosure;
FIG. 2 is a first application scenario diagram of a multi-tenant management method according to an embodiment of the present disclosure;
fig. 3 is a diagram of a second application scenario of a multi-tenant management method according to an embodiment of the present disclosure;
fig. 4 is a third application scenario diagram of a multi-tenant management method according to an embodiment of the present disclosure;
fig. 5 is a fourth application scenario diagram of a multi-tenant management method according to an embodiment of the present disclosure;
fig. 6 is a fifth application scenario diagram of a multi-tenant management method according to an embodiment of the present disclosure;
FIG. 7 is a sixth application scenario diagram of a multi-tenant management method according to an embodiment of the disclosure
Fig. 8 is a schematic diagram of an electronic device according to an embodiment of the disclosure.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those skilled in the art, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only some embodiments of the present disclosure, not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the present disclosure may be described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
The system architecture applicable to the method of the present embodiment may include a server or a server cluster for implementing a data control center management and control function, a server or a server cluster for implementing a tenant platform, and a server or a server cluster for implementing a service operation. The server or server cluster for realizing the control function of the data control center can perform data interaction with the server or server cluster for realizing the business operation so as to realize the business operation; the server or server cluster for realizing the control function of the data control center can perform data interaction with the server or server cluster for realizing the tenant platform, so that the tenant data is uniformly controlled.
The execution main body for implementing the method of the present embodiment may be a "server or a server cluster for implementing a data control center management and control function", which is hereinafter referred to as a server. The server can be used for realizing data communication among tenants, service registration, API registration, entity subscription relationship, data communication among tenants and the like. The server can realize tenant relationship management, tenant authority management, data issuing rule generation, data issuing task generation, task state collection, approval collaboration and the like. The data control center may also include a management interface through which a user manages the multi-tenants, including but not limited to viewing, editing, and the like.
According to an embodiment of the present disclosure, there is provided a multi-tenant management method, as shown in fig. 1, the method includes the following steps 101 to 103:
In this embodiment, the user may perform configuration of tenant relationships through a management interface with a server (an execution subject of the method of this embodiment) as a support. Illustratively, through the management interface, a user can determine the organization architecture of the tenant, and the information (e.g., number, affiliation, etc.) of the sub-tenants contained by the main tenant.
As an optional implementation manner of this embodiment, after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant includes: after receiving a request for adding the main tenant, performing tenant relationship configuration on the added main tenant and other main tenants; and/or after receiving a request for adding a sub-tenant under any main tenant, performing relationship configuration on any main tenant and the added sub-tenant.
In this optional implementation manner, the situation of adding the main tenant may be a situation that the main tenant joins the data control center, referring to fig. 2, a user may trigger a request for opening the main tenant through a management interface, and the server of this embodiment may establish a relationship between the main tenant and another tenant after receiving the request (the another tenant may be another main tenant or a sub tenant). When the main tenant is newly added, the server needs to generate a data reporting task and inform the main tenant of reporting the data, so that the main tenant can upload the data according to the reporting task. Meanwhile, for the newly added main tenants, when data is issued, an issued task can be generated. The issued data may include control data or data of other tenants, such as shared data of other main tenants.
When data is transmitted and different data is transmitted to different tenants, ID conversion can be firstly carried out, the ID of the transmitted data is converted into an identifier indicating a transmitted object (tenant), the ID identifier of the tenant to be received can be spliced at the head or any position of the ID of the transmitted data, and therefore the tenant to be received can be determined based on the converted identifier when the data is transmitted. Since all the sub-tenants adopt a database-based method for data storage, the cost is very high. Therefore, the data are transmitted through the conversion, and the sub-tenants can realize the data isolation without adopting a database splitting mode so as to ensure that the data of each tenant are unique. Tenant-level isolation of data is achieved.
Through the optional implementation mode, the main tenants in the tenant platform can be uniformly controlled, all data of the main tenants can be synchronized to the server, and meanwhile, the main tenants can receive the data issued by the server.
Further, referring to fig. 3, after receiving a request for adding a child tenant sent by a user from the management interface, if the child tenant is a new child tenant, child tenant information may be generated, and based on the configuration relationship indicated by the request, the child tenant is established under the indicated main tenant. Further, when a child tenant is added, an addition request may be sent to the child tenant, and if an addition feedback sent by the child tenant is received, the relationship of the child tenant may be generated. For the added sub-tenants, which need to meet the requirement of data synchronization, the server may generate a data synchronization task, so that the sub-tenants synchronize their own data to the execution subject of the method of this embodiment. Further, the executing body can also generate a sending task (9, 10, 11, 12, 13 in fig. 3) to realize data sending.
In the optional implementation manner, the addition of the sub-tenants under the main tenant is implemented based on a configuration manner, and the data of the added sub-tenants can be uniformly managed and controlled by the server.
As an optional implementation manner of this embodiment, after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant includes: after receiving a configuration request for migrating the child tenant, reestablishing the tenant relationship between the child tenant and other tenants; and converting the identifier of the sub-tenant to obtain the identifier of the migrated tenant.
In this optional implementation, the sub-tenant migration may include two situations, where the sub-tenant migration is a main tenant; and migrating the child tenants into child tenants of other main tenants.
Illustratively, when a child tenant migrates as a primary tenant, the Identity (ID) of the child tenant may be converted to identify the identity of the primary tenant after its conversion. And when the data is transmitted, the converted ID is used for realizing the data transmission. By the ID conversion mode, the data before migration can be used as the data of the main tenant again only by converting the ID, so that the loss of the tenant data is avoided. Data migration is facilitated, and isolation of data among tenants at the tenant level is achieved.
When a child tenant migrates to other main tenants, the identity ID of the child tenant needs to be converted to identify the identity of the main tenant corresponding to the converted child tenant.
As an optional implementation manner of this embodiment, after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant includes: after receiving an invitation request of a child tenant, sending the invitation request to the child tenant; and if the authorization indication of the sub-tenant is received, establishing the tenant relationship between the sub-tenant and other tenants.
In this optional implementation manner, tenants in a homogeneous or heterogeneous environment may be taken as child tenants that are uniformly controlled by the server in an invitation manner, or a uniform control relationship is released. Unified control may include unified data delivery, unified control of permissions of all tenants, and the like.
Illustratively, referring to fig. 4, a user may send an invitation request to a child tenant through a service end through a management interface, and after receiving feedback information of the child tenant agreeing to the invitation, a unified managed relationship may be generated with other child tenants.
As an optional implementation manner of this embodiment, after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant includes: and after receiving a request for deleting the child tenant, releasing the relationship between the child tenant to be deleted and other tenants.
In this optional implementation manner, deleting the child tenant may include requesting deletion of a relationship that is uniformly managed and controlled, or deleting the child tenant under the main tenant. When the child tenant is deleted, the control of the child tenant is released, and the server side does not need to control the data of the child tenant.
As an optional implementation manner of this embodiment, after receiving a request for configuring a tenant permission, configuring a preset permission for the tenant includes: after receiving a request for authorizing the preset authority of the main tenant, authorizing the preset authority for the main tenant; and/or after receiving a request for changing the authority of the main tenant, changing the authority of the main tenant.
In this alternative implementation, referring to fig. 7, after the authorization request of the main tenant is triggered by the user, the server may authorize the main tenant (refer to steps 1 to 7 in fig. 7). Meanwhile, the user can directly configure (add or modify) the authority of the main tenant through the management interface.
Step 102: and when a request for data issuing aiming at any configured tenant is received, generating a data issuing task so as to send the data to be issued to the any tenant according to the data issuing task.
In this embodiment, the implementation can manage and control data of the tenant by establishing a data control center (supported by the server and configurable by the management interface in this embodiment), and can generate a delivery task based on different delivery data. Illustratively, a user can perform configuration of fine-grained data delivery (including a delivery object, content of delivered data, and the like) based on the management interface, and the server can perform data delivery according to the configuration mode, so that differentiated management and control of data granularity and differentiated management and control of tenants are realized.
For example, the data issuing task may be generated by first issuing data through encapsulation and then generating a plurality of subtasks. The execution state of the tasks can be collected in the data issuing process of the subtasks.
Furthermore, the data transmission network of the server between the servers corresponding to the tenant platform may include a service layer and a data transmission layer, so that when a data delivery task is generated, service data may be organized at the service layer according to service characteristics of currently delivered data, the service data is encapsulated at the data transmission layer, and then a plurality of delivery subtasks are generated according to the obtained data.
Further, the issued data may be control data for controlling the tenant; or service data, for the tenant to receive different service data.
As an optional implementation manner of this embodiment, after receiving a request for data delivery to any tenant that has completed configuration, the method further includes: based on the identification of any tenant, converting the identification of the data to be issued; and sending the converted data to be issued to the any tenant.
In this optional implementation manner, when data is delivered, different data needs to be delivered to different tenants, so that ID conversion may be performed first, the ID of the delivered data is converted to include an identifier indicating an object to be delivered, and the ID identifier of the tenant to be received may be spliced at the head or any position of the ID of the delivered data, so that when data is delivered, the tenant to be received may be determined based on the converted identifier. For example, data of a certain item needs to be delivered to tenant a and tenant B, and the data identifier of the item is X, then X may be converted into XA (or another form including a) and XB during conversion, and during data delivery, based on the converted data identifier, it may be determined that data needs to be sent to tenant a and tenant B, respectively.
With the above alternative implementation, if all the sub-tenants adopt the separate database for data storage, the cost is very high. Therefore, the data are transmitted through the conversion, and the sub-tenants can realize the data isolation without adopting a database splitting mode so as to ensure that the data of each tenant are unique. Tenant-level isolation of data is achieved.
Step 103: and/or generating a data uploading task after any tenant generates data so that any tenant uploads the generated data according to the uploading task.
In the embodiment, the generation data of any tenant can be the enterprise information change of the tenant, the newly added tenant and the like.
As an optional implementation manner of this embodiment, after a preset service is triggered to perform a service operation, a data upload request sent by the preset service is received; and generating a data uploading task based on the content of the request indication so that a preset tenant uploads the data based on the task indication.
In this optional implementation manner, the preset service may be a service that can interact with the service end. Referring to fig. 6 (fig. 6 shows a system architecture suitable for the method of the present embodiment), a user may implement a service operation through a preset service (all-in-one). Such as document template management, fee type management, custom archive management, and the like. The business operation is implemented based on data of the tenant. In fig. 6, a tenant may join a data control center through a charge platform.
The server can receive a data uploading request of the preset service, and generate a data uploading task based on the request, so that the preset tenant uploads the data according to the uploading task, and the preset service can store the data uploaded by each tenant after receiving the data.
As an optional implementation manner of this embodiment, the method further includes: and after receiving a data issuing request sent by a preset service, generating a data issuing task so as to issue the data requested to be issued to a preset tenant.
In this optional implementation manner, the preset service may issue data through a server of the data control center.
According to the embodiment, the tenants are uniformly controlled, the data are efficiently issued in a uniform control mode, and the data granularity and the data operation permission are controlled in a differentiated mode; and the data isolation of the tenant level is realized, and the completion of technical actions such as data migration, database division, table division and the like is facilitated.
Referring to fig. 7, fig. 7 shows an application scenario diagram of the method of this embodiment, when a server issues data, it may respectively create an issue task for manual data issue or automatic data issue, and when the data is issued and the data issued is tenant data, the server may issue the data to a preset data transmission service (for example, a quick-report data transmission service in the diagram) through the data transmission service.
A timing task can be set in the data transmission process, and the transmission task is inquired so as to monitor the task state.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowcharts, in some cases, the steps illustrated or described may be performed in an order different than presented herein.
According to an embodiment of the present disclosure, there is also provided an apparatus for implementing the multi-tenant management method, where the apparatus includes: the configuration unit is configured to configure the relationship among the tenants for the tenants after receiving the configuration request for the tenants; after receiving a request for issuing data for any configured tenant, the data transmission unit generates a data issuing task so as to send the data to be issued to the tenant according to the data issuing task; and/or generating a data uploading task after any tenant generates data so that any tenant uploads the generated data according to the uploading task.
The embodiment of the present disclosure provides an electronic device, as shown in fig. 7, the electronic device includes one or more processors 71 and a memory 72, where one processor 71 is taken as an example in fig. 7.
The controller may further include: an input device 73 and an output device 74.
The processor 71, the memory 72, the input device 73 and the output device 74 may be connected by a bus or other means, as exemplified by the bus connection in fig. 7.
The processor 71 may be a Central Processing Unit (CPU). The processor 71 may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 72, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the control methods in the embodiments of the present disclosure. The processor 71 executes various functional applications and data processing of the server by running non-transitory software programs, instructions and modules stored in the memory 72, so as to implement the method of the above-mentioned method embodiment.
The memory 72 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of a processing device operated by the server, and the like. Further, the memory 72 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 72 may optionally include memory located remotely from the processor 71, which may be connected to a network connection device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 73 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the processing device of the server side. The output device 74 may include a display device such as a display screen.
One or more modules are stored in the memory 72, which when executed by the one or more processors 71 perform the method shown in FIG. 1.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium, and when executed, the program can include the processes of the embodiments of the motor control methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-only memory (ROM), a Random Access Memory (RAM), a flash memory (FlashMemory), a hard disk (hard disk drive, abbreviated as HDD) or a Solid State Drive (SSD), etc.; the storage medium may also comprise a combination of memories of the kind described above.
Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations fall within the scope defined by the appended claims.
Claims (10)
1. A multi-tenant management method, comprising:
after receiving a configuration request for the tenants, configuring the relationships among the tenants for the tenants;
when a request for data issuing aiming at any configured tenant is received, generating a data issuing task so as to send data to be issued to the any tenant according to the data issuing task;
and/or generating a data uploading task after any tenant generates data so that any tenant uploads the generated data according to the uploading task.
2. The multi-tenant management method of claim 1, further comprising:
receiving a data uploading request sent by a preset service after the preset service is triggered to be operated by a service;
and generating a data uploading task based on the content of the request indication so that a preset tenant uploads the data based on the task indication.
3. The multi-tenant management method of claim 1, further comprising:
and after receiving a data issuing request sent by a preset service, generating a data issuing task so as to issue the data requested to be issued to a preset tenant.
4. The multi-tenant management method according to claim 1, wherein after receiving a request for data delivery for any tenant whose configuration is completed, the method further comprises:
based on the identification of any tenant, converting the identification of the data to be issued;
and sending the converted data to be issued to the any tenant.
5. The multi-tenant management method of claim 1, wherein after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant comprises:
after receiving a request for adding the main tenant, performing tenant relationship configuration on the added main tenant and other tenants;
and/or after receiving a request for adding a sub-tenant under any main tenant, performing relationship configuration on any main tenant and the added sub-tenant.
6. The multi-tenant management method of claim 1, wherein after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant comprises:
after receiving a configuration request for migrating the child tenant, reestablishing the tenant relationship between the child tenant and other tenants;
and converting the identifier of the sub-tenant to obtain the identifier of the migrated tenant.
7. The multi-tenant management method of claim 1, wherein after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant comprises:
after receiving an invitation request of a child tenant, sending the invitation request to the child tenant;
and if the authorization indication of the sub-tenant is received, establishing the tenant relationship between the sub-tenant and other tenants.
8. The multi-tenant management method of claim 1, wherein after receiving a configuration request for a tenant, configuring a relationship between tenants for the tenant comprises:
and after receiving a request for deleting the child tenant, releasing the relationship between the child tenant to be deleted and other tenants.
9. The multi-tenant management method of claim 1, further comprising:
after receiving a request for configuring the permission of the tenant, configuring a preset permission for the tenant, wherein the method comprises the following steps: after receiving a request for authorizing the preset authority of the main tenant, authorizing the preset authority for the main tenant; and/or after receiving a request for changing the authority of the main tenant, changing the authority of the main tenant.
10. A computer-readable storage medium storing computer instructions for causing a computer to perform the multi-tenant management method of any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111632615.2A CN114331359A (en) | 2021-12-29 | 2021-12-29 | Multi-tenant management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111632615.2A CN114331359A (en) | 2021-12-29 | 2021-12-29 | Multi-tenant management method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114331359A true CN114331359A (en) | 2022-04-12 |
Family
ID=81014512
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111632615.2A Pending CN114331359A (en) | 2021-12-29 | 2021-12-29 | Multi-tenant management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114331359A (en) |
-
2021
- 2021-12-29 CN CN202111632615.2A patent/CN114331359A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11265367B2 (en) | System and method for signaling through data storage | |
| US9166978B2 (en) | Automatic resource provisioning for meeting collaboration | |
| WO2019068033A1 (en) | Leveraging microservice containers to provide tenant isolation in a multi-tenant api gateway | |
| WO2018099350A1 (en) | Resource sharing method, device and system | |
| US8874951B1 (en) | Private peer-to-peer network platform for secure collaborative production and management of digital assets | |
| KR20090007719A (en) | Tracking and editing a resource in real-time collaborative session | |
| DE112013002544T5 (en) | Cloud-based sharing of data points and collaboration among user groups | |
| US20170193448A1 (en) | Mixed collaboration teams | |
| US11652858B2 (en) | Integration of communication platform functionality with a third-party application | |
| US11126460B2 (en) | Limiting folder and link sharing | |
| US11973766B2 (en) | Dynamic membership assignment to users using dynamic rules | |
| US10956371B2 (en) | Team folder conversion and management | |
| CN107896242B (en) | Service sharing method and device | |
| CN114331359A (en) | Multi-tenant management method | |
| CN111061723B (en) | Workflow realization method and device | |
| KR102114374B1 (en) | Cloud-based device for processing data, and user device | |
| CN115086352A (en) | Block chain event processing method and related device, platform and storage medium | |
| Xia et al. | Design and Implementation of Docker-based Image Repository Management System of Dispatching and Control Cloud | |
| US11290523B1 (en) | High-speed transfer of data from device to service | |
| WO2023246127A1 (en) | System and methods for mission execution in network | |
| CN115600185B (en) | Resource operation method and system of cloud native platform | |
| US20220283867A1 (en) | Management of a scalable pool of workstation instances | |
| US20240098075A1 (en) | Access to messages sent via collaboration applications | |
| CN116614323B (en) | Cloud storage enterprise network management method and system based on Rclone | |
| US9531722B1 (en) | Methods for generating an activity stream |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |