CN111694682A - Management method, device, equipment and storage medium for multi-level tenants - Google Patents
Management method, device, equipment and storage medium for multi-level tenants Download PDFInfo
- Publication number
- CN111694682A CN111694682A CN202010540502.9A CN202010540502A CN111694682A CN 111694682 A CN111694682 A CN 111694682A CN 202010540502 A CN202010540502 A CN 202010540502A CN 111694682 A CN111694682 A CN 111694682A
- Authority
- CN
- China
- Prior art keywords
- tenant
- node
- merchant
- link
- commodity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to the field of Internet, and discloses a method, a device, equipment and a storage medium for managing multi-level tenants, which are used for solving the problems of complicated operation and complicated coding of merchant codes in the conventional multi-level tenant management scheme. The method comprises the following steps: when a tenant adding request sent by a merchant client is received, determining a target tenant to which the merchant client applies to add and a target adding position in an organization structure tree of the target tenant; sending a tenant adding request to an administrator client of a target tenant; when receiving the auditing passing information returned by the administrator client, establishing a merchant node at the target joining position; allocating a link identification for the merchant node, wherein the link identification is used for identifying the link of the merchant node in the organization structure tree and the position of the merchant node in the link; and acquiring a tenant identification of the target tenant, and storing the tenant identification, the link identification and the established merchant node in an associated manner.
Description
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a method, an apparatus, a device, and a storage medium for managing multi-level tenants.
Background
With the development of internet technology and the maturity of application Software, a Software-as-a-service (SaaS) Software application model is widely applied to providing internet services for various large enterprises. Specifically, the services provided by SaaS to the user are application programs that are run by an operator on a cloud computing infrastructure, and the user can access the application programs through a client interface on various devices without managing or controlling any cloud computing infrastructure, including a network, a server, an operating system, storage, and the like. SaaS is not only suitable for small and medium-sized enterprises, but also can be used for all large-scale enterprises to profit from SaaS.
Multi-tenant is a concept in SaaS, which means that a same software service can be used by multiple users (also called tenants), and data of the multiple users are guaranteed to be isolated from each other. The multi-tenant solution in the industry at present can only solve single-level multi-tenant isolation, such as Business-to-customer e-commerce mode (B2C) application, and for multi-level tenants, such as the requirement of multi-level application of B2C (the first B refers to a supplier of goods or services, the second B refers to an enterprise engaged in e-commerce, and C refers to a Consumer) in the supply chain, the upper and lower level relationships between tenants need to be stored by additional codes in order to perform tenant isolation operation.
The above coding scheme has the disadvantages that: when one merchant joins the tenant system, the code needs to be modified, the operation is complicated, and as more and more merchants join the tenant system, the code information becomes extremely complex, and the application system analyzes the complex code information when performing isolation operation, which results in greater system performance consumption.
Disclosure of Invention
The invention mainly aims to provide a method, a device, equipment and a storage medium for managing multi-level tenants, and aims to solve the problems of complex operation and complex coding of merchant codes in the conventional multi-level tenant management scheme.
The first aspect of the present invention provides a method for managing a multi-level tenant, where the method includes:
when receiving a tenant adding request sent by a merchant client, determining a target tenant for which the merchant client applies to add and a target adding position in an organization structure tree of the target tenant, wherein the organization structure tree comprises at least one link, and the link is used for representing the upper and lower hierarchical relation among a plurality of merchant nodes under the target tenant;
sending the tenant adding request to an administrator client of the target tenant so that the administrator client can verify and confirm the tenant adding request;
when the auditing passing information returned by the administrator client is received, a merchant node is established at the target joining position;
allocating a link identifier for the merchant node, wherein the link identifier is used for identifying the link where the merchant node is located in the organizational structure tree and the position where the merchant node is located in the link;
and acquiring a tenant identification of the target tenant, and performing association storage on the tenant identification, the link identification and the established merchant node.
Optionally, in a first implementation manner of the first aspect of the present invention, when receiving the audit-passing information returned by the administrator client, the step of creating a merchant node at the target joining location includes:
when the auditing passing information returned by the administrator client is received, determining a father node corresponding to the target joining position in the organization structure tree;
acquiring the number of child nodes of the father node, and judging whether the number of the child nodes reaches a preset node number threshold value;
and if the number of the child nodes does not reach a preset node number threshold value, setting a distributed global lock for the father node, and creating a commercial tenant node at the target joining position according to the distributed global lock.
Optionally, in a second implementation manner of the first aspect of the present invention, after the steps of obtaining the tenant identity of the target tenant and performing association storage on the tenant identity, the link identity, and the created merchant node, the method further includes:
when a commodity viewing instruction sent by the merchant client is received, determining a commodity issuing node corresponding to the commodity viewing instruction;
acquiring the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
judging whether the merchant node and the commodity release node are in the same link under the same tenant according to the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
if the merchant node and the commodity release node are in the same link of the same tenant, judging whether the merchant node is a next-level node of the commodity release node;
and if the merchant node is the next-level node of the commodity publishing node, acquiring commodity information corresponding to the commodity viewing instruction from the commodity publishing node, and returning the commodity information to the merchant client.
Optionally, in a third implementation manner of the first aspect of the present invention, after the step of obtaining the commodity information corresponding to the commodity viewing instruction from the commodity issuing node and returning the commodity information to the merchant client if the merchant node is a next-level node of the commodity issuing node, the method further includes:
when an order viewing instruction sent by the merchant client is received, determining an order generating node corresponding to the order viewing instruction;
acquiring the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
judging whether the merchant node and the commodity release node are in the same link under the same tenant according to the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
if the merchant node and the commodity release node are in the same link of the same tenant, judging whether the merchant node is a previous node of the commodity release node;
and if the merchant node is the upper-level node of the commodity issuing node, acquiring order information corresponding to the order viewing instruction from the order generating node, and returning the order information to the merchant client.
Optionally, in a fourth implementation manner of the first aspect of the present invention, after the step of obtaining the tenant identity of the target tenant and performing association storage on the tenant identity, the link identity, and the created merchant node, the method further includes:
when a commodity allocation instruction sent by the merchant client is received, inquiring allocation nodes meeting preset commodity inventory conditions from the organization structure tree to obtain an allocation node list;
returning the allocation node list to the merchant client, and acquiring a target allocation node selected by the merchant client based on the allocation node list;
acquiring the current time, and judging whether the current time is in a preset time period range or not;
and if the current time is within a preset time interval range, transferring the corresponding commodity from the target transfer node according to the commodity transfer instruction.
Optionally, in a fifth implementation manner of the first aspect of the present invention, after the step of obtaining the tenant identity of the target tenant, and performing row association storage on the tenant identity, the link identity, and the created merchant node in an organizational structure tree, the method further includes:
when a tenant quitting request sent by the merchant client is received, acquiring a tenant identification and a link identification of the merchant node and historical service data of the merchant node, wherein the historical service data comprises historical commodity release data and historical order data;
carrying out data cleaning processing on the tenant identification and the link identification of the merchant node and the tenant identification and the link identification contained in the historical service data;
when data cleansing is complete, removing the merchant node from the organizational structure tree of the target tenant.
Optionally, in a sixth implementation manner of the first aspect of the present invention, after the step of obtaining the tenant identity of the target tenant and performing association storage on the tenant identity, the link identity, and the created merchant node, the method further includes:
when a login request sent by the merchant client is received, acquiring a login account of the merchant client;
inquiring prestored registration information according to the login account, and judging whether a plurality of tenant identities exist in the registration information, wherein different tenant identities correspond to different tenants;
if a plurality of tenant identities exist in the registration information, returning a tenant identity selection list to the merchant client;
and acquiring a target tenant identity selected by the merchant client based on the tenant identity selection list, and recording the target tenant identity in a cache.
A second aspect of the present invention provides a management apparatus for a multi-level tenant, including:
the system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for determining a target tenant for which a merchant client applies to join and a target joining position in an organization structure tree of the target tenant when receiving a tenant joining request sent by the merchant client, and the organization structure tree comprises at least one link which is used for representing the upper and lower hierarchical relationship among a plurality of merchant nodes under the target tenant;
the sending module is used for sending the tenant adding request to an administrator client of the target tenant so that the administrator client can check and confirm the tenant adding request;
the creation module is used for creating a merchant node at the target joining position when the auditing passing information returned by the administrator client is received;
the distribution module is used for distributing a link identification for the merchant node, and the link identification is used for identifying the link where the merchant node is located in the organization structure tree and the position where the merchant node is located in the link;
and the storage module is used for acquiring the tenant identification of the target tenant and storing the tenant identification, the link identification and the established merchant node in a correlation manner.
A third aspect of the present invention provides a management device for a multi-level tenant, including: a memory having instructions stored therein and at least one processor, the memory and the at least one processor interconnected by a line; the at least one processor calls the instructions in the memory to cause the management device of the multi-level tenant to perform the above-described management method of the multi-level tenant.
A fourth aspect of the present invention provides a storage medium having stored therein instructions that, when run on a computer, cause the computer to execute the above-described method for managing a multi-level tenant.
According to the management method of the multi-level tenant, the multi-level tenant is abstracted into the organization structure tree and the link, when a merchant node is added into the organization structure tree, the tenant where the merchant node is located, the link where the merchant node is located in the organization structure tree of the tenant and the position where the merchant node is located can be quickly and accurately located by distributing the corresponding tenant identification and the corresponding link identification to the merchant node. Compared with the prior art, the method can distinguish the merchant nodes in different tenants and different links only through the tenant identification and the link identification, and does not need additional coding to store the upper and lower hierarchical relations among the multi-level tenants. Therefore, the invention solves the problems of complex operation and complex coding of the merchant code in the existing multi-level tenant management scheme.
Drawings
Fig. 1 is a flowchart illustrating a method for managing a multi-level tenant according to an embodiment of the present invention;
FIG. 2 is a diagram of an organization structure tree in an embodiment of a method for managing a multi-level tenant of the present invention;
fig. 3 is a flowchart illustrating a method for managing multi-level tenants according to another embodiment of the present invention;
fig. 4 is a schematic block diagram of an embodiment of a management apparatus for multi-level tenants in the present invention;
fig. 5 is a schematic block diagram of another embodiment of a management apparatus for a multi-level tenant of the present invention;
fig. 6 is a schematic structural diagram of an embodiment of a management device of a multi-level tenant of the present invention.
Detailed Description
The embodiment of the invention provides a method, a device, equipment and a storage medium for managing a multi-level tenant, and solves the problems of complex operation and complex coding of merchant codes in the conventional multi-level tenant management scheme.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," or "having," and any variations thereof, are intended to cover non-exclusive inclusions, 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.
For convenience of understanding, a specific flow of an embodiment of the management method for the multi-level tenants of the present invention is described below.
Referring to fig. 1, fig. 1 is a schematic flowchart of an embodiment of a method for managing a multi-level tenant, where the method includes:
it is to be understood that the execution subject of the present invention may be a management apparatus of a multi-level tenant, and may also be a terminal or a server, which is not limited herein. The embodiment of the present invention is described by taking a server as an execution subject.
In this embodiment, a tenant management system (or called an application system) is installed on a server, where the tenant management system has a multi-tenant oriented characteristic of providing software services for multiple tenants simultaneously, where each tenant includes several merchants with common requirements, and these merchants often have a business circulation or membership hierarchical relationship in reality, for example, a large tenant may correspond to a supply chain, and the merchants under the large tenant are upstream and downstream enterprises in the supply chain that provide products or services to end user activities, and in addition, a large tenant may also correspond to a group with a certain scale, and the merchants under the large tenant are a group headquarters and all levels of subsidiaries with membership and management relationships in business.
In order to facilitate management of the multi-level tenants and achieve mutual isolation of data, the server abstracts the multi-level tenants into an organization structure tree and links, wherein one tenant corresponds to one organization structure tree, the organization structure tree includes at least one link, and each link includes a plurality of merchant nodes connected according to an upper-lower level relationship of service flow or membership.
For a certain merchant, when the merchant wants to apply for joining a certain tenant, the tenant can log in a tenant management system server through a merchant client, such as a mobile phone, a tablet computer, a computer and the like, and a tenant joining request is triggered through a related page; when a server receives a tenant adding request sent by a merchant client, the tenant adding request is firstly analyzed, and a target tenant which is carried in the tenant adding request and applied for adding by the merchant client and an adding position in an organization structure tree of the target tenant are obtained.
For example, when a certain merchant is a downstream enterprise of an enterprise a in a certain supply chain, a target tenant corresponding to the supply chain may be requested to join, and a target joining position in the organizational structure tree is requested to be a next-level child node of a node corresponding to the enterprise a.
102, sending a tenant adding request to an administrator client of a target tenant so that the administrator client can verify and confirm the tenant adding request;
in this step, the server sends the tenant join request to the administrator client of the target tenant, so that the administrator client performs audit confirmation on the tenant join request. Specifically, each tenant may include a tenant administrator, and the tenant administrator has the authority to view and operate resources (including resources of itself and tenant users) of the tenant to which the tenant belongs and add and delete tenant users, and when a new merchant joins the tenant, the tenant administrator must obtain an audit confirmation.
103, when the auditing passing information returned by the administrator client is received, a merchant node is established at the target joining position;
when the server receives the auditing passing information returned by the administrator client, namely a merchant node is created at the target joining position in the organization structure tree, and the merchant node represents an independent merchant.
For example, when the target entry location is a next-level child node of the node corresponding to the enterprise a, a child node of the node corresponding to the enterprise a is created, and the child node is the merchant node.
104, distributing a link identification for the merchant node, wherein the link identification is used for identifying the link of the merchant node in the organizational structure tree and the position of the merchant node in the link;
after the merchant node is created, the server allocates a link identifier to the merchant node, and the link where the merchant node is located in the organizational structure tree and the location of the merchant node in the link can be known through the link identifier. The allocation rule of the link id is illustrated below.
In this embodiment, a pre-constraint condition may be set: in each tenant, the merchant nodes are divided into 5 layers at most, the number of child nodes of a root node of the organization structure tree is 32767 at most, namely 0x7FFF, and the number of child nodes of other nodes is 65535 at most, namely 0 xFFFF; based on the pre-constraint condition, the link identifier may be represented by a 16-bit 16-ary number, where each four bits are a segment, the number of valid segments (the number of segments that is not 0) in each link identifier is the number of layers where the merchant node is located in the tenant, and the number of the last valid segment represents the position number of the merchant node in the layer where the merchant node is located, and meanwhile, the link identifier includes information of all upper-level nodes of the link where the merchant node is located.
Referring to fig. 2, fig. 2 is a schematic diagram of an organization structure tree in an embodiment of a management method for a multi-level tenant of the present invention. The organization structure tree comprises 5 levels, and the link identifiers of the merchant nodes in each level are distributed as follows:
root node: b: 0x 0000000000000000;
a first layer: b1: 0x 0001000000000000, B2: 0x 0002000000000000;
a second layer: b1-1: 0x 000100000000, B1-2: 0x 0001000200000000, B2-1: 0x 0002000100000000;
and a third layer: b 1: 0x 0001000100010000, b 2: 0x 000100020000, b 3: 0x 0001000200010000, b 4: 0x 0001000200020000, b 5: 0x 0002000100010000;
a fourth layer: c1: 0x 00010001000100010001, C2: 0x 0001000100020001, C3: 0x 0001000200020001, C4: 0x 0001000200020002.
Link identification with node B1-2: 0x 0001000200000000 is exemplified. The first segment number 0001 represents that the upper node B1 of the B1-2 node is 0x 0001000000000000, and the second segment number 0002 represents that the B1-2 node is a child node with the number 2 of the upper node B1; the link id has only two significand segments 0001 and 0002 representing the second tier of the B1-2 node below the root node B.
Further, with the link identification of the b4 node: 0x 0001000200020000 is exemplified. The first segment number 0001 and the second segment number 0002 represent the upper nodes of the b4 node as follows: 0x 0001000000000000, 0x 0001000200000000, and a third section number 0002 indicating that the B4 node is a child node numbered 2 of the upper node B1-2; the link id has 3 significand segments: 0001. 0002 and 0002 representing the B4 node being on the third level node below the root node B.
The link identifier is distributed in a manner that the server can analyze the link identifier and clearly know the link where a certain merchant node is located and the position of the merchant node in the link.
It should be noted that, besides the foregoing allocation manner, in a specific implementation, the hierarchy of the organization structure tree, the number of bits and segments of the link identifier, and the like may be flexibly set according to the service requirement, which is not limited in this embodiment.
And 105, acquiring a tenant identification of the target tenant, and performing association storage on the tenant identification, the link identification and the established merchant node.
After the merchant node is allocated with the link identifier, the server may obtain a tenant identifier of a target tenant carried in the tenant adding request, and may also query a preset database to obtain a tenant identifier of the target tenant, where the tenant identifier is used to uniquely identify a tenant, and may be a tenant name, a code, or the like; then, the server stores the tenant identity, the link identity, and the created merchant node in an associated manner, for example, the tenant identity and the link identity may be stored as attribute information of the merchant node. Therefore, when the server executes data isolation operation subsequently, different tenants can be distinguished through the tenant identification, so that isolation among tenants is achieved, in addition, different links under the same tenant can be distinguished through the link identification, so that isolation among links is achieved, and therefore the data isolation requirement of multi-level and multi-tenant is met.
In the management method for the multi-level tenant provided in this embodiment, the multi-level tenant is abstracted into the organization structure tree and the link, and when a merchant node is added to the organization structure tree, the tenant where the merchant node is located, the link where the merchant node is located in the organization structure tree of the tenant, and the position where the merchant node is located in the link can be quickly and accurately located by allocating the corresponding tenant identifier and the link identifier to the merchant node. Compared with the prior art, the embodiment can distinguish the merchant nodes in different tenants and different links only through the tenant identification and the link identification, and does not need additional coding to save the upper and lower hierarchical relationships among the multi-level tenants. Therefore, the embodiment solves the problems of complex operation and complex coding of the merchant codes in the existing multi-level tenant management scheme.
Referring to fig. 3, fig. 3 is a flowchart illustrating a management method of a multi-level tenant according to another embodiment of the present invention. In this embodiment, the method for managing multi-level tenants includes:
305, if the number of the child nodes does not reach a preset node number threshold value, setting a distributed global lock for a father node, and creating a merchant node at a target joining position according to the distributed global lock;
The difference between this embodiment and the first embodiment of the method for managing multi-level tenants of the present invention is that:
when the server receives the audit passing information returned by the administrator client, the server can firstly query the organization structure tree according to the target joining position to determine a parent node corresponding to the target joining position, then obtain the current child node number of the parent node, judge whether the child node number reaches a preset node number threshold value, if not, indicate that the current parent node is allowed to be inserted into the child node under the constraint condition of the preset node number, at the moment, the server sets a distributed global lock for the parent node, after the parent node obtains the lock resource, the server creates a merchant node at the target joining position, allocates a link identifier for the merchant node, and then releases the distributed global lock. The distributed global lock is used for preventing other processes except the current tenant adding process from modifying the parent node, so that the merchant node is ensured to be successfully created.
It should be noted that the node number threshold may be flexibly set according to actual needs, and if the number of child nodes of the parent node reaches the preset node number threshold, it indicates that the number of child nodes of the current parent node has reached the maximum constraint value, at this time, the server rejects the tenant join request of the merchant client, and returns a prompt message indicating that the join is unsuccessful to the merchant client.
Further, after the step 307, the method may further include: when a commodity viewing instruction sent by a merchant client is received, determining a commodity issuing node corresponding to the commodity viewing instruction; acquiring a tenant identification and a link identification of a merchant node and a tenant identification and a link identification of a commodity release node; judging whether the merchant node and the commodity publishing node are in the same link under the same tenant according to the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity publishing node; if the merchant node and the commodity release node are in the same link of the same tenant, judging whether the merchant node is a next-level node of the commodity release node; and if the merchant node is the next-level node of the commodity publishing node, acquiring commodity information corresponding to the commodity viewing instruction from the commodity publishing node, and returning the commodity information to the merchant client.
In this embodiment, for a merchant node in a target tenant, a server provides a commodity viewing function, and the viewing of commodities needs to be executed under a certain authority control rule, so as to meet tenant isolation requirements and link isolation requirements. Referring to fig. 2, taking a merchant node corresponding to a merchant client as B1-2 as an example, when a commodity release node requested to be checked by the merchant client is B1, a server respectively obtains tenant identifications and link identifications of a B1-2 node and a B1 node, and correspondingly compares the tenant identifications and the link identifications of the B1-2 node and the B1 node, when the tenant identifications of the two are the same and the link identifications of the two have a relationship of a parent node, it may be determined that the B1-2 node and the B1 node are in the same link of the same tenant, at this time, the server further determines whether the B1-2 node is a next-level node of the B1 node according to the link identifications, if so, obtains corresponding commodity information from the B1 node, and returns the commodity information to the merchant client corresponding to the B1-2 node.
It should be noted that, if the merchant node and the commodity issuing node are not in the same link of the same tenant, or the merchant node is not a previous-level node of the commodity issuing node, the server rejects the commodity viewing instruction of the merchant client.
By the mode, commodity checking can be guaranteed only between upper and lower merchant nodes on the same tenant and the same link, the arrangement meets the business requirement of commodity checking, and the tenant isolation and link isolation requirements in a multi-level tenant system are met.
Further, after the step of obtaining the order information corresponding to the order viewing instruction from the order generating node and returning the order information to the merchant client if the merchant node is the upper-level node of the commodity issuing node, the method may further include: when an order viewing instruction sent by a merchant client is received, determining an order generating node corresponding to the order viewing instruction; acquiring a tenant identification and a link identification of a merchant node and a tenant identification and a link identification of a commodity release node; judging whether the merchant node and the commodity publishing node are in the same link under the same tenant according to the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity publishing node; if the merchant node and the commodity release node are in the same link of the same tenant, judging whether the merchant node is a previous node of the commodity release node; and if the merchant node is the upper-level node of the commodity publishing node, acquiring order information corresponding to the order viewing instruction from the order generating node, and returning the order information to the merchant client.
In this embodiment, for a merchant node in a target tenant, the server further provides an order viewing function, and the viewing of an order needs to be executed under a certain authority control rule, so as to meet tenant isolation requirements and link isolation requirements.
It should be noted that, if the merchant node and the order generating node are not in the same link of the same tenant, or the merchant node is not a higher-level node of the order generating node, the server rejects the order viewing instruction of the merchant client.
By the mode, order checking can be carried out only between upper and lower merchant nodes on the same tenant and the same link, the arrangement meets the service requirement of order checking, and the tenant isolation and link isolation requirements in a multi-level tenant system are met.
Further, after the step 307, the method may further include: when a commodity allocation instruction sent by a merchant client is received, inquiring allocation nodes meeting preset commodity inventory conditions from an organization structure tree to obtain an allocation node list; returning the allocation node list to the merchant client, and acquiring a target allocation node selected by the merchant client based on the allocation node list; acquiring a tenant identification of a merchant node and a tenant identification of a target transfer node; judging whether the merchant node and the target transfer node are in the same tenant according to the tenant identification of the merchant node and the tenant identification of the target transfer node; if the merchant node and the target transfer node are in the same tenant, acquiring the current time, and judging whether the current time is in a preset time period range; and if the current time is within the preset time interval range, the corresponding commodity is dispatched from the target dispatching node according to the commodity dispatching instruction.
In this embodiment, for a merchant node in a target tenant, the server further provides a commodity allocation function, and unlike commodity viewing and order viewing, allocation of commodities can be performed across links in the same tenant, that is, only the tenant isolation requirement needs to be met. Referring to fig. 2, taking a merchant node corresponding to a merchant client as C1 as an example, when a server receives a commodity allocation instruction sent by the merchant client corresponding to the C1 node, first querying an allocation node meeting a preset commodity inventory condition from an organization structure tree in which the C1 node is located, where the commodity inventory condition may be flexibly set, for example, the commodity inventory must be greater than or equal to the preset value, or must be greater than or equal to the number that needs to be allocated; if the C3 node and the C4 node do not meet the preset inventory condition, the server returns a transfer node list containing the C3 node and the C4 node to the merchant client, and obtains a target transfer node C3 selected by the merchant client based on the transfer node list; and then, the server acquires the current time, judges whether the current time is in a preset time interval range, and if the current time is in the preset time interval range, the server transfers the corresponding commodity from the C3 node to the C1 node.
It should be noted that, if the current time is not within the preset time period range, the server rejects the commodity allocation request of the merchant client, that is, the allocation operation of the commodity must be within the set time period range.
In the method, in the commodity allocation process, the allocation node meeting the preset commodity inventory condition is inquired in the organization structure tree where the merchant node is located, so that the target allocation node is determined, and the tenant isolation requirement in the multi-level tenant system is met; by allowing the commodity to be allocated within the preset time period range, the business requirement of commodity allocation is met.
Further, after the step 307, the method may further include: when a tenant quitting request sent by a merchant client is received, acquiring a tenant identifier and a link identifier of a merchant node and historical service data of the merchant node, wherein the historical service data comprises historical commodity issuing data and historical order data; carrying out data cleaning processing on the tenant identification and the link identification of the merchant node and the tenant identification and the link identification contained in the historical service data; when the data cleansing is completed, the merchant nodes are removed from the organizational structure tree of the target tenant.
In this embodiment, when a server receives a tenant quit request sent by a merchant client, a tenant identifier and a link identifier of a merchant node corresponding to the merchant client and historical service data of the merchant node are obtained, where the historical service data includes historical commodity release data and historical order data; then, the server performs data cleaning processing on the tenant identification and the link identification of the merchant node and the tenant identification and the link identification contained in the historical service data of the merchant node, and specific data cleaning rules can be flexibly set, for example, the tenant identification and the link identification can be uniformly set to be-1 and 0; when the data cleaning is completed, the server can remove the merchant node from the organization structure tree of the target tenant.
Through data cleaning, the data pollution can be avoided in data query after the merchant node exits from the target tenant.
Further, after the step 307, the method may further include: when a login request sent by a merchant client is received, acquiring a login account of the merchant client; inquiring pre-stored registration information according to the login account, and judging whether a plurality of tenant identities exist in the registration information, wherein different tenant identities correspond to different tenants; if a plurality of tenant identities exist in the registration information, returning a tenant identity selection list to the merchant client; and acquiring the target tenant identity selected by the merchant client based on the tenant identity selection list, and recording the target tenant identity in a cache.
In this embodiment, considering that a certain merchant may belong to a plurality of different organizations in an actual service, when a certain merchant exists in a plurality of tenants, tenant identity selection is performed at login. Specifically, when a server receives a login request sent by a merchant client, a login account of the merchant client is obtained, registration information saved in advance is inquired according to the login account, and whether multiple tenant identities exist in the registration information is judged, wherein different tenant identities correspond to different tenants, namely belong to different organizations; if a plurality of tenant identities exist, returning a tenant identity selection list to the merchant client, acquiring a target tenant identity selected by the merchant client based on the tenant identity selection list, and recording the target tenant identity in a cache.
By the method, the flexibility of tenant management is enhanced, and meanwhile, the merchant determining the identity can only operate resources in the tenant corresponding to the target tenant identity, so that the tenant isolation requirement is met.
The embodiment of the invention also provides a management device of the multi-level tenants.
Referring to fig. 4, fig. 4 is a schematic block diagram of an embodiment of a management apparatus for multi-level tenants in the present invention. In this embodiment, the management apparatus for a multi-level tenant includes:
a first determining module 401, configured to determine, when receiving a tenant join request sent by a merchant client, a target tenant for which the merchant client applies for joining and a target join position in an organization structure tree of the target tenant, where the organization structure tree includes at least one link, and the link is used to represent an upper-lower hierarchical relationship between multiple merchant nodes under the target tenant;
a sending module 402, configured to send the tenant join request to an administrator client of the target tenant, so that the administrator client performs an audit confirmation on the tenant join request;
a creating module 403, configured to create a merchant node at the target joining location when receiving the audit pass information returned by the administrator client;
an assigning module 404, configured to assign a link identifier to the merchant node, where the link identifier is used to identify a link where the merchant node is located in the organizational structure tree and a location where the merchant node is located in the link;
a saving module 405, configured to obtain a tenant identifier of the target tenant, and perform association saving on the tenant identifier, the link identifier, and the created merchant node.
The function implementation and beneficial effects of each module in the management device of the multi-level tenant correspond to each step in the embodiment of the management method of the multi-level tenant, and are not described herein again.
Referring to fig. 5, fig. 5 is a schematic block diagram of another embodiment of a management apparatus for a multi-level tenant according to the present invention. In this embodiment, the management apparatus for a multi-level tenant includes:
a first determining module 401, configured to determine, when receiving a tenant join request sent by a merchant client, a target tenant for which the merchant client applies for joining and a target join position in an organization structure tree of the target tenant, where the organization structure tree includes at least one link, and the link is used to represent an upper-lower hierarchical relationship between multiple merchant nodes under the target tenant;
a sending module 402, configured to send the tenant join request to an administrator client of the target tenant, so that the administrator client performs an audit confirmation on the tenant join request;
a creating module 403, configured to create a merchant node at the target joining location when receiving the audit pass information returned by the administrator client;
an assigning module 404, configured to assign a link identifier to the merchant node, where the link identifier is used to identify a link where the merchant node is located in the organizational structure tree and a location where the merchant node is located in the link;
a saving module 405, configured to obtain a tenant identifier of the target tenant, and perform association saving on the tenant identifier, the link identifier, and the created merchant node.
The creating module 403 specifically includes:
a determining unit 4031, configured to determine, when receiving the audit pass information returned by the administrator client, a parent node corresponding to the target joining location in the organization structure tree;
a determining unit 4032, configured to obtain the number of child nodes of the parent node, and determine whether the number of child nodes reaches a preset node number threshold;
a creating unit 4033, configured to set a distributed global lock for the parent node if the number of child nodes does not reach a preset node number threshold, and create a merchant node at the target joining location according to the distributed global lock.
The function implementation and beneficial effects of each module in the management device of the multi-level tenant correspond to each step in the embodiment of the management method of the multi-level tenant, and are not described herein again.
Further, the management apparatus of the multi-level tenant further includes:
the second determining module is used for determining a commodity publishing node corresponding to the commodity viewing instruction when the commodity viewing instruction sent by the merchant client is received;
the first acquisition module is used for acquiring the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
the first judgment module is used for judging whether the merchant node and the commodity release node are in the same link under the same tenant according to the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
the second judgment module is used for judging whether the merchant node is a next-level node of the commodity release node or not if the merchant node and the commodity release node are in the same link of the same tenant;
and the first returning module is used for acquiring the commodity information corresponding to the commodity viewing instruction from the commodity publishing node and returning the commodity information to the merchant client if the merchant node is the next-level node of the commodity publishing node.
Further, the management apparatus of the multi-level tenant further includes:
the third determining module is used for determining an order generating node corresponding to the order viewing instruction when receiving the order viewing instruction sent by the merchant client;
the second acquisition module is used for acquiring the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
the third judging module is used for judging whether the merchant node and the commodity publishing node are in the same link under the same tenant according to the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity publishing node;
the fourth judging module is used for judging whether the merchant node is a previous-level node of the commodity publishing node or not if the merchant node and the commodity publishing node are in the same link of the same tenant;
and the second returning module is used for acquiring the order information corresponding to the order viewing instruction from the order generating node and returning the order information to the merchant client if the merchant node is the upper-level node of the commodity issuing node.
Further, the management apparatus of the multi-level tenant further includes:
the query module is used for querying the allocation nodes meeting the preset commodity inventory conditions from the organization structure tree to obtain an allocation node list when a commodity allocation instruction sent by the merchant client is received;
a third returning module, configured to return the allocation node list to the merchant client, and obtain a target allocation node selected by the merchant client based on the allocation node list;
the fifth judgment module is used for acquiring the current time and judging whether the current time is within a preset time period range;
and the allocation module is used for allocating corresponding commodities from the target allocation node according to the commodity allocation instruction if the current time is within a preset time interval range.
Further, the management apparatus of the multi-level tenant further includes:
a third obtaining module, configured to obtain, when receiving a tenant quit request sent by the merchant client, a tenant identifier and a link identifier of the merchant node and historical service data of the merchant node, where the historical service data includes historical commodity release data and historical order data;
the data cleaning module is used for carrying out data cleaning processing on the tenant identification and the link identification of the merchant node and the tenant identification and the link identification contained in the historical service data;
and the removing module is used for removing the merchant node from the organization structure tree of the target tenant when the data cleaning is finished.
Further, the management apparatus of the multi-level tenant further includes:
the fourth acquisition module is used for acquiring the login account of the merchant client when receiving the login request sent by the merchant client;
a sixth judging module, configured to query pre-stored registration information according to the login account, and judge whether multiple tenant identities exist in the registration information, where different tenant identities correspond to different tenants;
a fourth returning module, configured to return a tenant identity selection list to the merchant client if multiple tenant identities exist in the registration information;
and the cache module is used for acquiring the target tenant identity selected by the merchant client based on the tenant identity selection list and recording the target tenant identity in a cache.
The function implementation and beneficial effects of each module in the management device of the multi-level tenant correspond to each step in the embodiment of the management method of the multi-level tenant, and are not described herein again.
The above describes in detail the management apparatus of the multi-level tenant in the embodiment of the present invention from the perspective of the modular functional entity, and the following describes in detail the management device of the multi-level tenant in the embodiment of the present invention from the perspective of hardware processing.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a management device of a multi-level tenant according to an embodiment of the present invention. The management apparatus 600 of the multi-level tenant may have a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 610 (e.g., one or more processors) and a memory 620, one or more storage media 630 (e.g., one or more mass storage devices) storing applications 633 or data 632. Memory 620 and storage medium 630 may be, among other things, transient or persistent storage. The program stored in the storage medium 630 may include one or more modules (not shown), and each module may include a series of instruction operations in the management apparatus 600 for multi-level tenants. Still further, the processor 610 may be configured to communicate with the storage medium 630, and execute a series of instruction operations in the storage medium 630 on the management device 600 of the multi-level tenant.
The management appliance 600 of the multi-tier tenant may also include one or more power supplies 640, one or more wired or wireless network interfaces 650, one or more input-output interfaces 660, and/or one or more operating systems 631, such as Windows service, Mac OS X, Unix, Linux, FreeBSD, and so forth. Those skilled in the art will appreciate that the management device structure of the multi-level tenant illustrated in fig. 6 does not constitute a limitation of the management device of the multi-level tenant, and may include more or less components than those illustrated, or combine some components, or different component arrangements.
The present invention further provides a storage medium, which may be a nonvolatile storage medium or a volatile storage medium, wherein a hypervisor of a multi-level tenant is stored in the storage medium, and when executed by a processor, the hypervisor implements the steps of the method for managing the multi-level tenant as described above.
The method and the beneficial effects of the management program of the multi-level tenant running on the processor when executed can refer to the embodiments of the management method of the multi-level tenant of the present invention, and are not described herein again.
It will be appreciated by those skilled in the art that the above-described integrated modules or units, if implemented as software functional units and sold or used as separate products, may be stored in a storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A management method for multi-level tenants is characterized by comprising the following steps:
when receiving a tenant adding request sent by a merchant client, determining a target tenant for which the merchant client applies to add and a target adding position in an organization structure tree of the target tenant, wherein the organization structure tree comprises at least one link, and the link is used for representing the upper and lower hierarchical relation among a plurality of merchant nodes under the target tenant;
sending the tenant adding request to an administrator client of the target tenant so that the administrator client can verify and confirm the tenant adding request;
when the auditing passing information returned by the administrator client is received, a merchant node is established at the target joining position;
allocating a link identifier for the merchant node, wherein the link identifier is used for identifying the link where the merchant node is located in the organizational structure tree and the position where the merchant node is located in the link;
and acquiring a tenant identification of the target tenant, and performing association storage on the tenant identification, the link identification and the established merchant node.
2. The method for managing multi-level tenants as claimed in claim 1, wherein the step of creating a merchant node at the target joining location upon receiving the audit pass information returned by the administrator client comprises:
when the auditing passing information returned by the administrator client is received, determining a father node corresponding to the target joining position in the organization structure tree;
acquiring the number of child nodes of the father node, and judging whether the number of the child nodes reaches a preset node number threshold value;
and if the number of the child nodes does not reach a preset node number threshold value, setting a distributed global lock for the father node, and creating a commercial tenant node at the target joining position according to the distributed global lock.
3. The method for managing multi-level tenants as claimed in claim 1, wherein after the step of obtaining the tenant identity of the target tenant and performing associated saving on the tenant identity, the link identity and the created merchant node, the method further comprises:
when a commodity viewing instruction sent by the merchant client is received, determining a commodity issuing node corresponding to the commodity viewing instruction;
acquiring the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
judging whether the merchant node and the commodity release node are in the same link under the same tenant according to the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
if the merchant node and the commodity release node are in the same link of the same tenant, judging whether the merchant node is a next-level node of the commodity release node;
and if the merchant node is the next-level node of the commodity publishing node, acquiring commodity information corresponding to the commodity viewing instruction from the commodity publishing node, and returning the commodity information to the merchant client.
4. The method for managing multi-level tenants according to claim 3, wherein after the step of obtaining the commodity information corresponding to the commodity viewing instruction from the commodity issuing node and returning the commodity information to the merchant client if the merchant node is a node next to the commodity issuing node, the method further comprises:
when an order viewing instruction sent by the merchant client is received, determining an order generating node corresponding to the order viewing instruction;
acquiring the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
judging whether the merchant node and the commodity release node are in the same link under the same tenant according to the tenant identification and the link identification of the merchant node and the tenant identification and the link identification of the commodity release node;
if the merchant node and the commodity release node are in the same link of the same tenant, judging whether the merchant node is a previous node of the commodity release node;
and if the merchant node is the upper-level node of the commodity issuing node, acquiring order information corresponding to the order viewing instruction from the order generating node, and returning the order information to the merchant client.
5. The method for managing multi-level tenants as claimed in claim 1, wherein after the step of obtaining the tenant identity of the target tenant and performing associated saving on the tenant identity, the link identity and the created merchant node, the method further comprises:
when a commodity allocation instruction sent by the merchant client is received, inquiring allocation nodes meeting preset commodity inventory conditions from the organization structure tree to obtain an allocation node list;
returning the allocation node list to the merchant client, and acquiring a target allocation node selected by the merchant client based on the allocation node list;
acquiring the current time, and judging whether the current time is in a preset time period range or not;
and if the current time is within a preset time interval range, transferring the corresponding commodity from the target transfer node according to the commodity transfer instruction.
6. The method for managing multi-level tenants as claimed in claim 1, wherein after the step of obtaining the tenant identity of the target tenant and saving the tenant identity, the link identity and the created merchant node in an organizational structure tree in association, the method further comprises:
when a tenant quitting request sent by the merchant client is received, acquiring a tenant identification and a link identification of the merchant node and historical service data of the merchant node, wherein the historical service data comprises historical commodity release data and historical order data;
carrying out data cleaning processing on the tenant identification and the link identification of the merchant node and the tenant identification and the link identification contained in the historical service data;
when data cleansing is complete, removing the merchant node from the organizational structure tree of the target tenant.
7. The method for managing multi-tier tenants according to any one of claims 1 to 6, wherein after the step of obtaining the tenant identity of the target tenant and performing associated saving on the tenant identity, the link identity and the created merchant node, further comprising:
when a login request sent by the merchant client is received, acquiring a login account of the merchant client;
inquiring prestored registration information according to the login account, and judging whether a plurality of tenant identities exist in the registration information, wherein different tenant identities correspond to different tenants;
if a plurality of tenant identities exist in the registration information, returning a tenant identity selection list to the merchant client;
and acquiring a target tenant identity selected by the merchant client based on the tenant identity selection list, and recording the target tenant identity in a cache.
8. A management device of a multi-level tenant is characterized in that the management device of the multi-level tenant comprises:
the system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for determining a target tenant for which a merchant client applies to join and a target joining position in an organization structure tree of the target tenant when receiving a tenant joining request sent by the merchant client, and the organization structure tree comprises at least one link which is used for representing the upper and lower hierarchical relationship among a plurality of merchant nodes under the target tenant;
the sending module is used for sending the tenant adding request to an administrator client of the target tenant so that the administrator client can check and confirm the tenant adding request;
the creation module is used for creating a merchant node at the target joining position when the auditing passing information returned by the administrator client is received;
the distribution module is used for distributing a link identification for the merchant node, and the link identification is used for identifying the link where the merchant node is located in the organization structure tree and the position where the merchant node is located in the link;
and the storage module is used for acquiring the tenant identification of the target tenant and storing the tenant identification, the link identification and the established merchant node in a correlation manner.
9. A management device of a multi-level tenant is characterized by comprising: a memory having instructions stored therein and at least one processor, the memory and the at least one processor interconnected by a line;
the at least one processor invokes the instructions in the memory to cause a management device of the multi-tier tenant to perform the management method of the multi-tier tenant of any of claims 1-7.
10. A storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements a method of managing multi-tier tenants as recited in any one of claims 1-7.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2020105291564 | 2020-06-11 | ||
| CN202010529156 | 2020-06-11 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111694682A true CN111694682A (en) | 2020-09-22 |
| CN111694682B CN111694682B (en) | 2023-10-03 |
Family
ID=72480979
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010540502.9A Active CN111694682B (en) | 2020-06-11 | 2020-06-15 | Multi-level tenant management method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111694682B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113850642A (en) * | 2021-09-18 | 2021-12-28 | 北京京东乾石科技有限公司 | Goods data maintenance method and device, storage medium and electronic equipment |
| CN113947329A (en) * | 2021-10-29 | 2022-01-18 | 中国建设银行股份有限公司 | Merchant management method, device, equipment, medium and program product |
| CN114969612A (en) * | 2022-07-29 | 2022-08-30 | 深圳市星卡软件技术开发有限公司 | Multi-tenant data isolation method, system and computer equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140032228A1 (en) * | 2012-07-30 | 2014-01-30 | Microsoft Corporation | Security and data isolation for tenants in a business data system |
| CN107169772A (en) * | 2017-04-28 | 2017-09-15 | 英泰伟业信息技术股份有限公司 | Lottery customer relationship management method and system based on cloud |
| US20190182226A1 (en) * | 2017-12-11 | 2019-06-13 | International Business Machines Corporation | Provide access to data storage services in a network environment |
-
2020
- 2020-06-15 CN CN202010540502.9A patent/CN111694682B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140032228A1 (en) * | 2012-07-30 | 2014-01-30 | Microsoft Corporation | Security and data isolation for tenants in a business data system |
| CN107169772A (en) * | 2017-04-28 | 2017-09-15 | 英泰伟业信息技术股份有限公司 | Lottery customer relationship management method and system based on cloud |
| US20190182226A1 (en) * | 2017-12-11 | 2019-06-13 | International Business Machines Corporation | Provide access to data storage services in a network environment |
Non-Patent Citations (1)
| Title |
|---|
| 李保栋;孔兰菊;陆春生;李庆忠;李晓娜;: "SaaS交付平台多租户数据管理模型研究" * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113850642A (en) * | 2021-09-18 | 2021-12-28 | 北京京东乾石科技有限公司 | Goods data maintenance method and device, storage medium and electronic equipment |
| CN113947329A (en) * | 2021-10-29 | 2022-01-18 | 中国建设银行股份有限公司 | Merchant management method, device, equipment, medium and program product |
| CN114969612A (en) * | 2022-07-29 | 2022-08-30 | 深圳市星卡软件技术开发有限公司 | Multi-tenant data isolation method, system and computer equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111694682B (en) | 2023-10-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111694682A (en) | Management method, device, equipment and storage medium for multi-level tenants | |
| Malone et al. | Modeling the performance of organizational structures | |
| US9122685B2 (en) | Operating cloud computing and cloud computing information system | |
| US20080178147A1 (en) | Apparatus, system, and method for profiling and reusing software development assets | |
| US20120311111A1 (en) | Dynamic reconfiguration of cloud resources | |
| CN108399101A (en) | The methods, devices and systems of scheduling of resource | |
| CN101946258A (en) | Model based deployment of computer based business process on dedicated hardware | |
| CN102739771A (en) | Cloud application integrated management platform and method supporting service fusion | |
| CN105095970A (en) | Execution method and system of third-party application | |
| CN106170947A (en) | A kind of alarm information processing method, relevant device and system | |
| CN109787807B (en) | Self-service system based on Openstack architecture cloud platform workflow | |
| US10892947B2 (en) | Managing cross-cloud distributed application | |
| CN103377101A (en) | Testing system and testing method | |
| CN110058940A (en) | Data processing method and device under a kind of multi-thread environment | |
| Taifa et al. | Towards a digital revolution in the UK apparel manufacturing: An industry 4.0 perspective | |
| CN111143391A (en) | Data sharing exchange method and system | |
| CN112104726A (en) | Real-time monitoring system for object storage of industrial Internet of things | |
| US20070124185A1 (en) | State engine for business process execution | |
| CN109286617B (en) | Data processing method and related equipment | |
| CN114866416A (en) | Multi-cluster unified management system and deployment method | |
| BRPI0803389B1 (en) | computer-implemented methods for managing correlated event message sequence and a sequence of correlated service requests | |
| CN115309592B (en) | Resource scheduling method and device, computer equipment and storage medium | |
| US8863132B2 (en) | Using abstraction layers to facilitate communication between systems | |
| CN108681870A (en) | A kind of ERP coprocessing systems, server and method | |
| US20240176605A1 (en) | Method and apparatus for application deployment in software-as-a-service platform and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |