A method, system and device for multi-tenant message isolation based on logical message domains
Patent Information
- Application Number
- CN202611197391.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-07
- Publication Date
- 2026-11-03
AI Technical Summary
In existing multi-tenant message broker systems, tenant business semantics are coupled with message topics, resulting in complex message topic maintenance, high costs for client adaptation and business migration, and complex and difficult-to-manage policy rules when sharing messages across tenants.
The message broker node maintains a mapping relationship between clients and logical message fields, generates propagation tags using output and receive propagation strategies, and achieves isolation and controlled sharing of multi-tenant messages through logical message fields, using logical message fields as control metadata within the message broker.
It reduces the naming coupling of message topics and the cost of client adaptation, simplifies the configuration complexity of cross-domain message sharing, and achieves controlled cross-domain message propagation visibility management.
Smart Images
Figure CN123034984A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the fields of message communication, network software and distributed message broker technology, and in particular to a multi-tenant message isolation method, system and device based on logical message domains. It is applicable to multi-tenant logical isolation in message broker nodes, controlled message sharing across logical message domains and message propagation visibility management, and is particularly suitable for publish / subscribe message communication environments using the MQTT protocol. Background Technology
[0002] Existing multi-tenant message broker systems typically distinguish different tenants by setting a tenant prefix in the message topic, which couples business semantics with tenant affiliation, increasing the complexity of message topic maintenance, client adaptation, and business migration.
[0003] In cross-tenant message sharing scenarios, existing solutions mainly rely on access control lists, message replication, or message broker bridging configurations, which make it difficult to uniformly represent the logical domain to which a message belongs and its cross-domain propagation conditions. This results in a large number of policy rules and makes message propagation visibility control and cross-node propagation management quite complex. Summary of the Invention
[0004] The purpose of this invention is to provide a multi-tenant message isolation method, system, and device based on logical message domains. By maintaining the mapping relationship between clients and logical message domains within the message broker node, and establishing a message propagation control mechanism using output propagation strategy, receive propagation strategy, and propagation tags, the logical isolation and controlled sharing of multi-tenant messages can be achieved.
[0005] To achieve the above objectives, the present invention provides a multi-tenant message isolation method based on logical message domains, applied to a message broker node. The message broker node maintains the mapping relationship between clients and logical message domains, the output propagation strategy corresponding to each logical message domain, and the receiving propagation strategy corresponding to each logical message domain. The logical message domain serves as internal control metadata of the message broker, distinct from the message topic namespace.
[0006] The method includes: receiving a message publishing request sent by a publishing client; querying the mapping relationship between the client and logical message domains based on the identity information of the publishing client; determining the first logical message domain to which the publishing client belongs; generating a propagation tag set for the message corresponding to the message publishing request based on the output propagation strategy corresponding to the first logical message domain; and establishing a message propagation context associated with the message, wherein the message propagation context includes the message topic of the message, the message domain identifier corresponding to the first logical message domain, and the propagation tag set.
[0007] The method further includes: receiving a message subscription request sent by a subscription client; querying the mapping relationship between the client and logical message domains based on the identity information of the subscription client to determine the second logical message domain to which the subscription client belongs; obtaining the reception and propagation strategy corresponding to the second logical message domain, and performing topic matching between the message topic of the message and the subscription topic corresponding to the message subscription request; performing message propagation visibility calculation based on the propagation tag set and the reception and propagation strategy to obtain the propagation visibility result of the message relative to the subscription client; and delivering the message to the subscription client when the message topic matches the subscription topic, the propagation visibility result indicates that the message is visible, and the message subscription request is in a valid state.
[0008] Furthermore, the logical message field is used to represent the logical isolation unit within the message broker node and to define the home context of the message within the message broker node; the logical message field is independent of the message topic namespace and is not represented by the tenant prefix in the message topic; the logical message field corresponds to at least one of tenant, enterprise organization, security domain, regional cluster, business system, and device group.
[0009] Furthermore, the output propagation strategy is used to define the propagation labels that are allowed to be generated in the corresponding logical message domain, and the receiving propagation strategy is used to define the propagation labels that are allowed to be received in the corresponding logical message domain. The propagation labels are used to represent the propagable attributes of messages between different logical message domains.
[0010] Furthermore, the message broker node automatically generates one or more propagation tags according to the output propagation strategy corresponding to the first logical message domain, and the one or more propagation tags are combined into the propagation tag set, and the publishing client does not directly specify the propagation tag set.
[0011] Further, the set of allowed receiving tags defined by the receiving and propagation strategy is obtained, and the intersection of the propagation tag set and the set of allowed receiving tags is calculated; when the intersection is a non-empty set, the message is determined to be visible to the subscribing client; when the intersection is an empty set, the message is determined to be invisible to the subscribing client.
[0012] Furthermore, the message broker node supports dynamically updating at least one of the following configurations: the mapping relationship between the client and the logical message domain, the output propagation strategy, and the receiving propagation strategy. After the configuration is updated, the cache used to perform message propagation processing is refreshed, so that the updated configuration is applied to the message propagation context established after the update. The message propagation context also includes strategy version information, and the message propagation context established before the configuration update retains the strategy version information corresponding to the time when the message propagation context was established.
[0013] Furthermore, the message broker node includes multiple message broker nodes that communicate with each other; when a message is propagated from the first message broker node to the second message broker node, the first message broker node sends the message and the message propagation context associated with the message to the second message broker node; after receiving the message and the message propagation context, the second message broker node performs message domain parsing, propagation strategy evaluation, and message propagation visibility determination according to the message propagation context, and controls the delivery of the message in the second message broker node according to the determination result.
[0014] This invention also provides a multi-tenant message isolation system based on logical message domains, including a domain management module, a policy management module, a propagation parsing module, and a message distribution module. The domain management module maintains the mapping relationship between clients and logical message domains, and determines the corresponding logical message domain based on the identity information of the publishing or subscribing client. The logical message domain serves as internal control metadata of the message broker, distinct from the message topic namespace. The policy management module maintains the output propagation policy and the receiving propagation policy corresponding to each logical message domain, and provides the corresponding output propagation policy or receiving propagation policy to the propagation parsing module. The propagation parsing module includes a tag parsing unit and a visibility parsing unit. The tag parsing unit generates a propagation tag set and establishes a message propagation context containing the message topic, message domain identifier, and propagation tag set. The visibility parsing unit performs message propagation visibility calculation based on the receiving propagation policy corresponding to the logical message domain to which the subscribing client belongs. The message distribution module performs message topic matching and delivers the message to the subscribing client when the topic matching, propagation visibility, and subscription validity conditions are all satisfied.
[0015] The present invention also provides an electronic device, including a processor and a memory for storing executable instructions of the processor, the processor being configured to execute the above-described multi-tenant message isolation method based on logical message domains by executing the executable instructions.
[0016] The present invention also provides a non-transitory computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, the processor performs the above-described multi-tenant message isolation method based on logical message fields.
[0017] Beneficial effects
[0018] I. This invention separates tenant affiliation from business message topics by setting up logical message fields within message broker nodes and using message field identifiers to indicate message ownership, thereby reducing naming coupling of message topics and the costs of client adaptation and business migration.
[0019] Second, this invention generates propagation tags by outputting a propagation strategy and performs message propagation visibility judgment by combining the receiving propagation strategy. While retaining the message topic matching mechanism, it realizes controlled cross-domain message sharing, thereby reducing the complexity of configuring access rules for a large number of clients and message topics separately. Attached Figure Description
[0020] Figure 1 This is a schematic diagram of the overall architecture of the multi-tenant message broker system in this invention.
[0021] Figure 2 This is a flowchart illustrating the process of establishing the message publishing and message propagation context in this invention.
[0022] Figure 3 This is a flowchart illustrating the subscription parsing and message delivery process in this invention.
[0023] Figure 4 This is a schematic diagram illustrating message propagation control among multiple message broker nodes in this invention. Detailed Implementation
[0024] The technical solution of the present invention will be fully described below with reference to the accompanying drawings. It should be understood that the following content is used to illustrate the technical concept and implementation process of the present invention, and is not intended to limit the scope of protection of the present invention. Unless otherwise specified, the further embodiments and optional embodiments described can be combined with the basic embodiments.
[0025] Overall Structure and Terminology Explanation
[0026] like Figure 1 As shown, the multi-tenant message broker system of this invention includes a publishing client, a subscribing client, and a message broker node located between the publishing client and the subscribing client. The message broker node receives publishing and subscribing requests, matches message topics, and controls message delivery based on message propagation visibility results. In a preferred application, the message broker node is a Broker supporting the MQTT protocol.
[0027] The message broker node includes a domain management module, a policy management module, a propagation parsing module, and a message distribution module. The domain management module maintains the mapping relationship between clients and logical message domains; the policy management module maintains the output propagation policy and the receiving propagation policy corresponding to each logical message domain; the propagation parsing module includes a tag parsing unit and a visibility parsing unit. The tag parsing unit generates a propagation tag set and establishes a message propagation context based on the output propagation policy, while the visibility parsing unit performs message propagation visibility calculation based on the propagation tag set and the receiving propagation policy; the message distribution module performs message topic matching and controls message delivery based on the topic matching result, the propagation visibility result, and the subscription relationship status.
[0028] A logical message domain is a control object within a message broker node used to represent the logical isolation relationship between clients and the message ownership context. It can correspond to a tenant, enterprise organization, security domain, regional cluster, business system, or device group. Logical message domains are independent of the message topic namespace; they are not indicated by a tenant prefix in the message topic, nor are they required to be directly exposed to clients. Message topics are used to represent business semantics, while logical message domains are used to represent tenant ownership or propagation control boundaries. The message broker node determines the logical message domain to which a client belongs based on the client's identity information and a pre-maintained mapping relationship.
[0029] The mapping relationship between clients and logical message domains can be recorded as a correspondence between client identifiers and message domain identifiers. For example, the publishing client device001 corresponds to Domain-OEM, the subscription client analytics01 corresponds to Domain-Analytics, and the subscription client regulator01 corresponds to Domain-Regulator. The above names are only used to illustrate the mapping relationship and do not constitute a restriction on the naming method of client identifiers or message domain identifiers.
[0030] The output propagation strategy corresponds to a logical message field and is used to define the propagation tags allowed to be generated by that logical message field. The receive propagation strategy also corresponds to a logical message field and is used to define the propagation tags allowed to be received by that logical message field. Propagation tags are used to represent the propagable attributes of a message, such as analytics, regulator, partner-share, or edge-sync. Propagation tags are generated by the message broker node according to the output propagation strategy; publishing clients do not directly specify propagation tags.
[0031] The message propagation context is the propagation control information associated with a message, which includes at least the message subject, the message domain identifier corresponding to the source logical message domain, and the propagation tag set. In scenarios involving dynamic policy updates or propagation across multiple message broker nodes, the message propagation context also includes policy version information; during cross-node propagation, the message subject, message domain identifier, propagation tag set, and policy version information are transmitted together.
[0032] Basic implementation method under a single message broker node
[0033] This basic implementation fully illustrates the process of a message going from a publication request to delivery to a subscribing client in a single message broker node. Figure 2 The publishing process shown is similar to Figure 3 The subscription parsing and delivery processes shown together constitute the complete basic flow of the method of this invention.
[0034] The message broker node pre-maintains the mapping relationship between clients and logical message domains. For example, device001 maps to Domain-OEM, analytics01 maps to Domain-Analytics, and regulator01 maps to Domain-Regulator. The message broker node also maintains output propagation and receive propagation policies. For example, the output propagation policy for Domain-OEM allows the generation of analytics and regulator tags; the receive propagation policy for Domain-Analytics allows the reception of analytics tags; and the receive propagation policy for Domain-Regulator allows the reception of regulator tags.
[0035] like Figure 2 As shown, the message publishing and message propagation context establishment process includes steps S101 to S106.
[0036] In step S101, the message broker node receives a message publishing request sent by the publishing client. The message publishing request includes the message subject and message content of the message to be published. For example, the message subject is telemetry / vehicle001.
[0037] In step S102, the message broker node identifies the identity information of the publishing client based on the connection context of the publishing client, and obtains the publishing client identifier.
[0038] In step S103, the domain management module queries the mapping relationship between the publishing client and the logical message domain based on the publishing client identifier to determine the first logical message domain to which the publishing client belongs. For example, the first logical message domain to which the publishing client device001 belongs is Domain-OEM.
[0039] In step S104, the propagation parsing module queries the policy management module for the output propagation policy corresponding to the first logical message domain, and the message broker node automatically generates a propagation tag set based on the output propagation policy. For example, if the output propagation policy corresponding to Domain-OEM allows the generation of analytics and regulator tags, then the generated propagation tag set is {analytics, regulator}.
[0040] In step S105, the propagation parsing module establishes a message propagation context associated with the message to be published, and writes the message topic, the message field identifier corresponding to the first logical message field, and the propagation tag set of the message to be published into the message propagation context. The propagation tags are automatically generated by the message broker node, and the publishing client cannot directly specify the propagation tag set, thereby reducing the risk of the client forging message propagation attributes.
[0041] In step S106, the message broker node hands over the message to be published and its message propagation context to the propagation parsing module and the message distribution module for subscription parsing, propagation visibility calculation and message delivery processing.
[0042] like Figure 3 As shown, the subscription resolution and message delivery process includes steps S201 to S206. The message broker node receives message subscription requests sent by the subscribing client and maintains the corresponding subscription relationship.
[0043] Step S201: The message broker node obtains the identity information of the subscribing client.
[0044] In step S202, the domain management module queries the mapping relationship between the client and the logical message domain based on the identity information of the subscribing client, and determines the second logical message domain to which the subscribing client belongs. For example, the second logical message domain to which the subscribing client analytics01 belongs is Domain-Analytics.
[0045] In step S203, the propagation parsing module queries the policy management module for the receiving propagation policy corresponding to the second logical message domain, and obtains the set of propagation tags that the second logical message domain is allowed to receive. For example, the set of allowed receiving tags corresponding to Domain-Analytics is {analytics}.
[0046] In step S204, the message distribution module performs topic matching between the message topic of the message to be published and the subscription topic corresponding to the message subscription request. If the topics do not match, the message is not delivered to the corresponding subscription client; if the topics match, the message propagation visibility calculation continues.
[0047] Step S205: The propagation parsing module performs message propagation visibility calculation based on the propagation tag set in the message propagation context and the receive propagation strategy corresponding to the second logical message domain. Let the propagation tag set in the message propagation context be Lmsg, and the allowed receive tag set defined by the receive propagation strategy be Limp. Then, the propagation visibility result V is determined according to the following formula:
[0048] When Lmsg∩Limp≠∅, V=TRUE; when Lmsg∩Limp=∅, V=FALSE.
[0049] Here, V=TRUE indicates that the message is visible to the subscribing client, and V=FALSE indicates that the message is not visible to the subscribing client. For example, if the message propagation tag set is {analytics, regulator}, and the allowed receiving tag set of Domain-Analytics is {analytics}, the intersection of the two is {analytics}, so the message is visible; if the allowed receiving tag set of the target logical message domain is {partner-share}, then the intersection of the two is empty, and the message is not visible.
[0050] In step S206, when the message topic matches the subscription topic, the propagation visibility result indicates that the message is visible, and the message subscription request is valid, the message distribution module delivers the message to the subscription client. Thus, message topic matching is used to determine messages that conform to the business subscription relationship, and propagation visibility calculation is used to further limit the logical message domains that the message can reach based on topic matching, eliminating the need to create multiple message topics for different receiving logical message domains.
[0051] Further Implementation Method 1: Propagation Control Among Multiple Message Broker Nodes
[0052] like Figure 4 As shown, in a further embodiment, multiple message broker nodes form a federated structure, including a first message broker node and a second message broker node, and messages can be propagated from the first message broker node to the second message broker node.
[0053] The first message broker node determines the logical message domain to which the publishing client belongs according to the basic implementation method, generates a propagation tag set according to the output propagation strategy, and establishes a message propagation context. When the first message broker node propagates a message to the second message broker node, it sends the message subject, message domain identifier, propagation tag set, and strategy version information as the message propagation context along with the message.
[0054] After receiving the message and the message propagation context, the second message broker node re-executes message domain parsing, propagation strategy evaluation, and message propagation visibility judgment based on the message propagation context and the receiving and propagation strategy corresponding to the target logical message domain, and controls the delivery of the message in the second message broker node based on the judgment result.
[0055] In scenarios involving three or more message broker nodes, each receiving message broker node can re-execute the message propagation visibility determination based on the message propagation context, as described above. This ensures that messages continue to be controlled by propagation policies when propagating across message broker nodes, preventing cross-node messages from being treated as transparently forwarded messages without policy constraints. This approach can be applied to message broker clusters, message broker federation, multi-region deployments, edge message brokers, cloud message federations, and carrier-grade message broker deployments.
[0056] Further Implementation Method Two: Dynamic Updates of the Propagation Strategy
[0057] In another further embodiment, the message broker node provides a management interface for dynamically updating at least one of the following configurations during the operation of the message broker node: the mapping relationship between clients and logical message domains, the output propagation strategy, and the receive propagation strategy, without restarting the message broker node.
[0058] After the configuration is updated, the domain management module or policy management module saves the updated configuration, and the propagation parsing module refreshes the cache used for message propagation processing, so that the updated configuration is applied to the message propagation context established after the update. New messages generate propagation tags according to the updated output propagation strategy, and perform message propagation visibility calculation according to the updated receive propagation strategy.
[0059] The message propagation context includes policy version information. Message propagation contexts established before the configuration update retain the policy version information corresponding to their establishment time. Newly established message propagation contexts after the configuration update record the updated policy version information. This distinguishes message propagation contexts established under different policy versions and reduces processing contention caused by the concurrent use of old and new policies during the policy update process.
[0060] Optional implementation methods
[0061] As an optional approach, logical message domains can adopt a hierarchical structure, including a parent logical message domain and one or more child logical message domains. Child logical message domains can inherit the propagation strategy of the parent logical message domain. This approach is used to reuse propagation strategies between organizational or business levels.
[0062] Alternatively, when using the MQTT 5 protocol, the message propagation context can be carried out through User Properties written by the message broker node. Publishing clients cannot modify the set of propagation tags generated by the message broker node based on the output propagation strategy by specifying propagation tags themselves.
[0063] Alternatively, the functionality described in this invention can be implemented as an EMQX plugin, a HiveMQ extension, a Mosquitto module, or a custom message broker component. The above deployment methods do not alter the processing relationships between domain management, policy management, propagation resolution, and message distribution.
[0064] Implementation of Multi-tenant Message Broker System
[0065] This invention also provides a multi-tenant message isolation system based on logical message domains. The system includes a domain management module, a policy management module, a propagation and parsing module, and a message distribution module. These modules work collaboratively according to the data processing relationships described in the aforementioned basic implementation. The logical message domain serves as internal control metadata for the message broker, distinct from the message topic namespace.
[0066] The domain management module maintains the mapping relationship between clients and logical message domains, and determines the corresponding logical message domain based on the identity information of the publishing client or the subscribing client, and provides the determined logical message domain to the propagation and parsing module.
[0067] The policy management module maintains the output propagation policy and the receive propagation policy corresponding to each logical message field. When the propagation parsing module processes a published message, the policy management module provides the output propagation policy corresponding to the first logical message field; when the propagation parsing module processes a subscription delivery, the policy management module provides the receive propagation policy corresponding to the second logical message field.
[0068] The propagation parsing module includes a tag parsing unit and a visibility parsing unit. The tag parsing unit generates a propagation tag set based on the first logical message domain and the corresponding output propagation strategy, and establishes a message propagation context including the message topic, message domain identifier, and propagation tag set. The visibility parsing unit performs message propagation visibility calculation based on the receiving propagation strategy corresponding to the second logical message domain and the propagation tag set in the message propagation context, and provides the propagation visibility result to the message distribution module.
[0069] The message distribution module performs topic matching between message topics and subscribed topics, and combines the propagation visibility results and subscription relationship status to form a message delivery decision. When topic matching is achieved, the message is visible, and the subscription relationship is valid, the message distribution module delivers the message to the subscribed client.
[0070] Implementation methods of electronic devices
[0071] The present invention also provides an electronic device, the electronic device comprising a processor and a memory, wherein the memory stores executable instructions of the processor. When the processor executes the executable instructions, it performs the following: determining the logical message domain to which the publishing client belongs, generating a propagation tag set, establishing a message propagation context, determining the logical message domain to which the subscribing client belongs, calculating message propagation visibility, and controlling message delivery, thereby performing the method of any one of claims 1 to 7.
[0072] Implementation methods of storage media
[0073] The present invention also provides a non-transitory computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor performs the aforementioned determination of the logical message domain to which the publishing client belongs, generation of the propagation tag set, establishment of the message propagation context, determination of the logical message domain to which the subscribing client belongs, calculation of message propagation visibility, and message delivery control, to implement the method of any one of claims 1 to 7.
[0074] The above description illustrates the basic technical solution, further embodiments, and optional embodiments of the present invention. Equivalent substitutions or appropriate adjustments made by those skilled in the art without altering the core technical concept of the present invention should all fall within the protection scope of the present invention.
Claims
1. A multi-tenant message isolation method based on logical message domains, characterized in that, This method is applied to a message broker node, which maintains a mapping relationship between clients and logical message domains, an output propagation strategy corresponding to each logical message domain, and a receive propagation strategy corresponding to each logical message domain. The logical message domain serves as internal control metadata of the message broker, distinct from the message topic namespace. The method includes: receiving a message publishing request sent by a publishing client; querying the mapping relationship between the client and logical message domains based on the publishing client's identity information to determine the first logical message domain to which the publishing client belongs; generating a propagation tag set for the message corresponding to the message publishing request based on the output propagation strategy corresponding to the first logical message domain; and establishing a message propagation context associated with the message, the message propagation context including the message topic of the message, the first logical message domain, and the first logical message domain. The system includes: a message domain identifier corresponding to the message domain and the propagation tag set; receiving a message subscription request sent by a subscribing client; querying the mapping relationship between the client and logical message domains based on the identity information of the subscribing client to determine the second logical message domain to which the subscribing client belongs; obtaining the receiving propagation strategy corresponding to the second logical message domain and performing topic matching between the message topic of the message and the subscription topic corresponding to the message subscription request; performing message propagation visibility calculation based on the propagation tag set and the receiving propagation strategy to obtain the propagation visibility result of the message relative to the subscribing client; and delivering the message to the subscribing client when the message topic matches the subscription topic, the propagation visibility result indicates that the message is visible, and the message subscription request is in a valid state.
2. The multi-tenant message broker isolation method according to claim 1, characterized in that, The logical message field is used to represent the logical isolation unit within the message broker node and to define the home context of the message within the message broker node; the logical message field is independent of the message topic namespace and is not represented by the tenant prefix in the message topic; the logical message field corresponds to at least one of tenant, enterprise organization, security domain, regional cluster, business system, and device group.
3. The multi-tenant message broker isolation method according to claim 1, characterized in that, The output propagation strategy is used to define the propagation tags that are allowed to be generated in the corresponding logical message domain; the receiving propagation strategy is used to define the propagation tags that are allowed to be received in the corresponding logical message domain; the propagation tags are used to represent the propagability attribute of a message between different logical message domains.
4. The multi-tenant message broker isolation method according to claim 1, characterized in that, The step of generating a propagation tag set according to the output propagation strategy corresponding to the first logical message domain includes: the message broker node automatically generating one or more propagation tags according to the output propagation strategy corresponding to the first logical message domain, and combining the one or more propagation tags into the propagation tag set; wherein, the publishing client does not directly specify the propagation tag set.
5. The multi-tenant message broker isolation method according to claim 1, characterized in that, The step of performing message propagation visibility calculation based on the propagation tag set and the receiving propagation strategy includes: obtaining the allowed receiving tag set defined by the receiving propagation strategy; calculating the intersection of the propagation tag set and the allowed receiving tag set; determining that the message is visible to the subscribing client when the intersection is a non-empty set; and determining that the message is not visible to the subscribing client when the intersection is an empty set.
6. The multi-tenant message broker isolation method according to claim 1, characterized in that, The message broker node supports dynamic updates of at least one of the following configurations: the mapping relationship between the client and the logical message domain, the output propagation strategy, and the receiving propagation strategy; after the configuration is updated, the cache used to perform message propagation processing is refreshed so that the updated configuration is applied to the message propagation context established after the update; the message propagation context also includes strategy version information, and the message propagation context established before the configuration update retains the strategy version information corresponding to the establishment of the message propagation context.
7. The multi-tenant message broker isolation method according to claim 1, characterized in that, The message broker node includes multiple message broker nodes that communicate with each other. When a message is propagated from the first message broker node to the second message broker node, the first message broker node sends the message and the message propagation context associated with the message to the second message broker node. The message propagation context includes the message subject, message domain identifier, propagation tag set, and policy version information. After receiving the message and the message propagation context, the second message broker node performs message domain parsing, propagation policy evaluation, and message propagation visibility determination based on the message propagation context, and controls the delivery of the message in the second message broker node based on the determination result.
8. A multi-tenant message isolation system based on logical message domains, characterized in that, include: The domain management module is used to maintain the mapping relationship between clients and logical message domains, and to determine the corresponding logical message domains based on the identity information of publishing clients or subscribing clients. The logical message domains serve as internal control metadata of the message broker, which is distinct from the message topic namespace. The strategy management module is used to maintain the output propagation strategy and the receiving propagation strategy corresponding to each logical message domain, and to provide the propagation parsing module with the output propagation strategy or the receiving propagation strategy corresponding to the logical message domain. The propagation parsing module is used to generate a propagation tag set according to the output propagation strategy corresponding to the logical message domain to which the publishing client belongs, establish a message propagation context including the message topic, message domain identifier, and the propagation tag set, and perform message propagation visibility calculation according to the receiving propagation strategy corresponding to the logical message domain to which the subscribing client belongs and the propagation tag set; the message distribution module is used to perform topic matching between the message topic and the subscribed topic, and deliver the message to the subscribing client when the message topic matches the subscribed topic, the message propagation visibility result indicates that the message is visible, and the subscription relationship is in a valid state.
9. An electronic device, characterized in that, include: processor; A memory for storing executable instructions of the processor; wherein the processor is configured to execute the multi-tenant message isolation method based on logical message domains according to any one of claims 1 to 7 by executing the executable instructions.
10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it causes the processor to perform the multi-tenant message isolation method based on logical message domains as described in any one of claims 1 to 7.