CN114338703A

CN114338703A - Cross-domain message management method and device, electronic equipment and storage medium

Info

Publication number: CN114338703A
Application number: CN202111669653.5A
Authority: CN
Inventors: 方思维
Original assignee: Koubei Shanghai Information Technology Co Ltd
Current assignee: Koubei Shanghai Information Technology Co Ltd
Priority date: 2021-12-31
Filing date: 2021-12-31
Publication date: 2022-04-12

Abstract

The present specification provides a cross-domain message management method, which is applied to a message management system, wherein the message management system maintains a mapping relationship between in-domain service information corresponding to any service information of subscription information and data objects of each out-of-domain service system for the in-domain service messages in the in-domain service system and any service information corresponding to the out-of-domain service information in the out-of-domain service system; the method comprises the following steps: acquiring intra-domain service messages generated by each intra-domain service system according to a first data format of the intra-domain service system, wherein the intra-domain service messages comprise intra-domain service information of specified data objects; and determining a subscriber system of the intra-domain service message according to the subscription information, converting the intra-domain service information contained in the intra-domain service message into the out-of-domain service information corresponding to the subscriber system according to the mapping relation, and generating the out-of-domain service message containing the out-of-domain service information according to a second data format configured for the subscriber system.

Description

Cross-domain message management method and device, electronic equipment and storage medium

Technical Field

One or more embodiments of the present disclosure relate to the field of communications technologies, and in particular, to a method and an apparatus for cross-domain message management, an electronic device, and a storage medium.

Background

The two service systems running independently may be merged, for example, the two service platforms cooperate to get through the service between the respective service systems, and mutually utilize the data of the other side to realize the corresponding service. Before the fusion, each service system generates messages according to respective data formats, and after the fusion, the two service systems are in relative terms of the relationship between the inside and outside of the domain. Then, cross-domain message communication between the intra-domain service system and the extra-domain system is a precondition for service implementation.

Disclosure of Invention

In view of this, one or more embodiments of the present disclosure provide a cross-domain message management method and apparatus, an electronic device, and a storage medium.

To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:

according to a first aspect of one or more embodiments of the present specification, there is provided a cross-domain message management system, comprising:

at least one intra-domain service system, configured to generate an intra-domain service message according to a first data format of the intra-domain service system, where the intra-domain service message includes intra-domain service information of a specified data object;

the system comprises a message management system, a service management system and a service management system, wherein the message management system maintains subscription information of each off-domain service system aiming at intra-domain service messages, and a mapping relation between intra-domain service information corresponding to any service information of a data object in the intra-domain service system and off-domain service information corresponding to any service information in the off-domain service system; the message management system is used for acquiring the intra-domain service messages generated by each intra-domain service system, determining a subscriber system of the intra-domain service messages according to the subscription information, converting the intra-domain service information contained in the intra-domain service messages into the out-of-domain service information corresponding to the subscriber system according to the mapping relation, and generating the out-of-domain service messages containing the out-of-domain service information according to a second data format of the subscriber system so as to send the out-of-domain service messages to the subscriber system;

at least one off-domain service system, which generates subscription information for the service messages in the domain and sends the generated subscription information to the message management system; and receiving the service information outside the domain sent by the information management system.

Optionally, the message management system is further configured to perform security check on the obtained intra-domain service message, so as to determine a subscriber system of the intra-domain service message that passes the security check.

According to a second aspect of one or more embodiments of the present specification, a cross-domain message management method is provided, which is applied to a message management system that maintains subscription information of each out-of-domain service system for intra-domain service messages, and a mapping relationship between intra-domain service information corresponding to any service information of a data object in the intra-domain service system and out-of-domain service information corresponding to the any service information in the out-of-domain service system; the method comprises the following steps:

acquiring intra-domain service messages generated by each intra-domain service system according to a first data format of the intra-domain service system, and performing security check on the acquired intra-domain service messages; the intra-domain service message comprises intra-domain service information of the specified data object;

determining a subscriber system of the intra-domain service message passing the security check according to the subscription information, converting the intra-domain service information contained in the intra-domain service message into the out-of-domain service information corresponding to the subscriber system according to the mapping relation, and generating the out-of-domain service message containing the out-of-domain service information according to a second data format configured for the subscriber system;

sending the out-of-domain service message to the subscriber system for receipt by the subscriber system of the out-of-domain service message.

Optionally, the intra-domain service messages generated by the intra-domain service systems are added to a preset message queue; the acquiring the intra-domain service message generated by each intra-domain service system according to the first data format of the intra-domain service system includes:

and reading the intra-domain service messages in the message queue according to a preset period.

Optionally, the message management system maintains authorization information of the data object for the service information of the data object, where the authorization information is used to indicate a read permission of each out-of-domain service system for the corresponding service information; the method further comprises the following steps:

and determining whether the service information of the specified data object has the reading authority aiming at the service information of the specified data object or not according to the authorization information of the specified data object, so as to convert the intra-domain service information contained in the intra-domain service information under the condition of having the reading authority.

Optionally, the generating a service message outside the domain including the service information outside the domain according to the second data format of the subscriber system includes:

filling the converted out-of-domain service information into a first field in the out-of-domain service message aiming at the first field with the same meaning in the second data format and the first data format;

and aiming at a second field with the meaning different from all fields in the first data format in the second data format, under the condition that the domain-outside service system has the reading authority, acquiring the domain-outside service information matched with the meaning of the second field according to the mapping relation and filling the domain-outside service information into the second field in the domain-outside service information.

According to a third aspect of one or more embodiments of the present specification, a cross-domain message management method is provided, which is applied to a message management system, where the message management system maintains subscription information of each out-of-domain service system for intra-domain service messages, and a mapping relationship between intra-domain service information corresponding to any service information of a data object in the intra-domain service system and out-of-domain service information corresponding to the any service information in the out-of-domain service system; the method comprises the following steps:

acquiring intra-domain service messages generated by each intra-domain service system according to a first data format of the intra-domain service system, wherein the intra-domain service messages comprise intra-domain service information of specified data objects;

determining a subscriber system of the intra-domain service message according to the subscription information, converting the intra-domain service information contained in the intra-domain service message into the out-domain service information corresponding to the subscriber system according to the mapping relation, and generating the out-domain service message containing the out-domain service information according to a second data format configured for the subscriber system;

According to a fourth aspect of one or more embodiments of the present specification, there is provided a cross-domain message management method applied to at least one out-of-domain service system, including:

generating subscription information of the intra-domain service messages generated by aiming at least one intra-domain service system respectively, and sending the generated subscription information to a message management system; the intra-domain service message is generated by an intra-domain service system according to a first data format of the intra-domain service system, and the intra-domain service message comprises intra-domain service information of a specified data object; the message management system maintains subscription information of each off-domain service system aiming at the intra-domain service messages, and a mapping relation between the intra-domain service information corresponding to any service information of the data object in the intra-domain service system and the off-domain service information corresponding to any service information in the off-domain service system;

receiving an outside-domain service message sent by the message management system when the outside-domain service system is determined to be a subscriber system of the inside-domain service message, wherein the outside-domain service message comprises outside-domain service information, the outside-domain service message is generated by the message management system according to a second data format of the outside-domain service system, the subscriber system acquires the inside-domain service message generated by each inside-domain service system by the message management system and determines the inside-domain service message according to the subscription information, and the outside-domain service message is obtained by converting the inside-domain service message contained by the inside-domain service message by the message management system according to the mapping relation.

According to a fifth aspect of one or more embodiments of the present specification, a cross-domain message management apparatus is provided, which is applied to a message management system that maintains subscription information of each out-of-domain service system for in-domain service messages, and a mapping relationship between in-domain service information corresponding to any service information of a data object in the in-domain service system and out-of-domain service information corresponding to the any service information in the out-of-domain service system; the device comprises:

the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring intra-domain service messages generated by each intra-domain service system according to a first data format of the intra-domain service system and carrying out security verification on the acquired intra-domain service messages; the intra-domain service message comprises intra-domain service information of the specified data object;

the generating unit is used for determining a subscriber system of the intra-domain service information passing the security verification according to the subscription information, converting the intra-domain service information contained in the intra-domain service information into the out-of-domain service information corresponding to the subscriber system according to the mapping relation, and generating the out-of-domain service information containing the out-of-domain service information according to a second data format configured for the subscriber system;

and the sending unit is used for sending the service information outside the domain to the subscriber system so as to receive the service information outside the domain by the subscriber system.

According to a sixth aspect of one or more embodiments of the present specification, a cross-domain message management apparatus is provided, which is applied to a message management system that maintains subscription information of each out-of-domain service system for intra-domain service messages, and a mapping relationship between intra-domain service information corresponding to any service information of a data object in the intra-domain service system and out-of-domain service information corresponding to the any service information in the out-of-domain service system; the device comprises:

the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring intra-domain service messages generated by each intra-domain service system according to a first data format of the intra-domain service system, and the intra-domain service messages comprise intra-domain service information of specified data objects;

the generating unit is used for determining a subscriber system of the intra-domain service message according to the subscription information, converting the intra-domain service information contained in the intra-domain service message into the out-domain service information corresponding to the subscriber system according to the mapping relation, and generating the out-domain service message containing the out-domain service information according to a second data format configured for the subscriber system;

Optionally, the intra-domain service messages generated by the intra-domain service systems are added to a preset message queue; the obtaining unit is specifically configured to:

Optionally, the message management system maintains authorization information of the data object for the service information of the data object, where the authorization information is used to indicate a read permission of each out-of-domain service system for the corresponding service information; the generation unit is further configured to:

Optionally, the generating unit is specifically configured to:

According to a seventh aspect of one or more embodiments of the present specification, there is provided a cross-domain message management apparatus applied to at least one out-of-domain service system, including:

the generating unit generates subscription information of the intra-domain service messages generated by aiming at least one intra-domain service system respectively and sends the generated subscription information to the message management system; the intra-domain service message is generated by an intra-domain service system according to a first data format of the intra-domain service system, and the intra-domain service message comprises intra-domain service information of a specified data object; the message management system maintains subscription information of each off-domain service system aiming at the intra-domain service messages, and a mapping relation between the intra-domain service information corresponding to any service information of the data object in the intra-domain service system and the off-domain service information corresponding to any service information in the off-domain service system;

the receiving unit is used for receiving the domain-outside service message sent by the message management system when the domain-outside service system is determined to be a subscriber system of the domain-outside service message, the domain-outside service message comprises the domain-outside service information, the domain-outside service message is generated by the message management system according to a second data format of the domain-outside service system, the subscriber system acquires the domain-inside service message generated by each domain-inside service system by the message management system and determines the domain-outside service message according to the subscription information, and the domain-outside service message is obtained by converting the domain-inside service message contained by the domain-inside service message by the message management system according to the mapping relation.

According to an eighth aspect of one or more embodiments herein, there is provided an electronic apparatus, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method as described in any of the above embodiments by executing the executable instructions.

According to a ninth aspect of one or more embodiments of the present description, there is provided a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method as described in any of the above embodiments.

In the technical solution of the present specification, two independent service systems generate service messages according to respective data formats, and when the two service systems cooperate to complete a service, from the perspective of any one of the two service systems, the service system itself is an intra-domain service system, and the other is an extra-domain service system.

In the present specification, a message management system is configured for the application scenario, and the message management system can acquire the service messages generated by each service system. Meanwhile, in order to implement cross-domain message communication, each service system can subscribe the service information required by itself to the message management system to cooperatively complete service implementation. Specifically, the service system may provide its own subscription information to the message management system, where the subscription information is used to characterize the conditions of its required service messages. Then, the message management system can screen out the service messages required by each service system from all the obtained service messages according to the subscription information and send the service messages to the corresponding subscriber system.

Because each service system processes the service message by adopting a respective data format, and also adopts a respective rule to describe the service information of the data object for the same data object, namely the same service information of the same data object is different from the description mode adopted in different service systems, each service system can only identify the service information described by adopting the description mode of the service system. Therefore, a mapping relation can be established between corresponding description modes of the same service information in different service systems, before the message management system sends the screened service information to the service systems, the description modes of the service information contained in the screened service information are converted into the description modes which can be identified by a subscriber system according to the mapping relation, and then the corresponding service information is regenerated according to the data format used by the subscriber system, so that cross-domain message communication is realized.

By the cross-domain message management scheme, asynchronous communication between service systems can be realized, and after one service message is sent by the service system, the next message can be sent at any time without waiting for result feedback. Meanwhile, the message management system can connect a plurality of service systems in series on the premise of not modifying the description mode of each service system for the service information and the data format of the service information, thereby achieving the purpose of communication among the service systems. In other words, the service systems are still independent from each other, and the intra-domain service system and the extra-domain service system are isolated from each other, so that zero service intrusion of the service systems is realized, the development cost is reduced, and the stability and the safety of the service systems are improved.

Drawings

Fig. 1 is a flowchart of a cross-domain message management method according to an exemplary embodiment.

Fig. 2 is a flow chart of another cross-domain message management method provided by an example embodiment.

Fig. 3 is a flow chart of another cross-domain message management method provided by an example embodiment.

FIG. 4 is a schematic block diagram of an apparatus provided in an exemplary embodiment.

Fig. 5 is a block diagram of a cross-domain message management apparatus according to an example embodiment.

Fig. 6 is a block diagram of another cross-domain message management apparatus provided by an example embodiment.

Fig. 7 is a block diagram of another cross-domain message management apparatus provided by an example embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.

It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.

In the related art, there is a case where two service systems that operate independently from each other are merged, for example, two service platforms cooperate to make up services between the respective service systems, and mutually utilize data of the other side to implement corresponding services. For example, a credit payment platform, an e-commerce platform and a take-out platform are developed by three different enterprises respectively, and an enterprise subsequently developing the credit payment platform purchases other two enterprises, and service systems of the three platforms need to be connected and integrated into a whole to cooperatively complete a service. For example, a user places an order on an e-commerce platform or a take-away platform, and can use the payment rights and interests of a credit payment platform; as another example, the virtual rights and interests of the takeout platform can be obtained under the E-commerce platform; as another example, the same user may share red envelope for credit payment platforms, e-commerce platforms, and take-away platforms, and so on.

It should be noted that, before the convergence, the service systems generate messages according to respective data formats (e.g., different fields included), and the description modes (e.g., user name, brand id, store id, etc.) of the same service information are different in different service systems. After convergence, the two service systems are relatively related to each other from the inside to the outside of the domain. Then, cross-domain message communication between the intra-domain service system and the extra-domain system is a precondition for service implementation. In the above example, after the enterprise developing the credit payment platform purchases other enterprises, from the perspective of the credit payment platform, the business system of the credit payment platform is an intra-domain business system, and the business systems of the e-commerce platform and the takeout platform are extra-domain business systems. Of course, the intra-domain service system and the extra-domain service system are relative concepts, for example, from the perspective of the e-commerce platform, the service system of the e-commerce platform is the intra-domain service system, and the service systems of the credit payment platform and the take-out platform are the extra-domain service systems.

For the above application scenario, the present specification provides a cross-domain message management system, which may include:

at least one intra-domain service system, which is used for generating intra-domain service messages according to a first data format of the intra-domain service system, wherein the intra-domain service messages contain intra-domain service information of specified data objects;

the message management system maintains subscription information of each off-domain service system aiming at the intra-domain service messages, and a mapping relation between the intra-domain service information corresponding to any service information of the data object in the intra-domain service system and the off-domain service information corresponding to any service information in the off-domain service system; the message management system is used for acquiring the intra-domain service messages generated by each intra-domain service system, determining a subscriber system of the intra-domain service messages according to the subscription information, converting the intra-domain service information contained in the intra-domain service messages into the out-of-domain service information corresponding to the subscriber system according to the mapping relation, and generating the out-of-domain service messages containing the out-of-domain service information according to a second data format of the subscriber system so as to send the out-of-domain service messages to the subscriber system;

at least one off-domain service system, which generates subscription information for the service messages in the domain and sends the generated subscription information to the message management system; and receiving the service message outside the domain sent by the message management system.

The technical solution of the present specification is described in detail below from the perspective of each system in the cross-domain message management system, respectively.

Referring to fig. 1, fig. 1 is a flowchart illustrating a cross-domain message management method according to an exemplary embodiment. As shown in fig. 1, the method is applied to a message management system, where the message management system maintains subscription information of each out-of-domain service system for in-domain service messages, and a mapping relationship between in-domain service information of a data object in the in-domain service system and out-of-domain service information of the data object in the out-of-domain service system; the method may comprise the steps of:

step 102, obtaining an intra-domain service message generated by each intra-domain service system according to a first data format of the intra-domain service system, wherein the intra-domain service message comprises intra-domain service information of a specified data object.

In this embodiment, each service system (including the intra-domain service system and the extra-domain service system) still generates the service message according to the service information registered in its own system by each data object (e.g. for the user of the service system) and the data format configured by its own system (e.g. for the message format of the service message, which fields are included, what the content of the fields is, etc.). For the intra-domain service system, the intra-domain service message is generated by adopting the first data format, the intra-domain service message comprises the service information recorded by the data object in the intra-domain service system, and only the service message adopting the first data format can be identified and processed. For the domain-outside service system, the domain-outside service message is generated by adopting the second data format, the service information contained in the domain-outside service message is the service information recorded by the data object in the domain-outside service system, and only the service message adopting the second data format can be identified and processed.

Aiming at the intra-domain service system and the extra-domain service system which need to complete the service cooperatively, the message management system is used for uniformly completing the cross-domain transmission of the service message. The message management system can acquire the service messages generated by each service system. Meanwhile, in order to implement cross-domain message communication, each service system can subscribe the service information required by itself to the message management system to cooperatively complete service implementation. Specifically, the service system may provide its own subscription information to the message management system, where the subscription information is used to characterize the conditions of its required service messages. Then, the message management system can screen out the service messages required by each service system from all the obtained service messages according to the subscription information and send the service messages to the corresponding subscriber system. For example, a business system of the credit payment platform needs to subscribe the order information of the user in the e-commerce platform and the take-away platform, and further, the credit payment amount of the user is adjusted according to the consumption amount recorded by the order information.

In this embodiment, each service system may send the generated service message to a preset message queue, and messages sent by all the service systems are queued in the message queue to be consumed. From the perspective of the intra-domain service system, the intra-domain service messages generated based on the intra-domain service systems are added to the preset message queue, and when the message management system acquires (for example, in a monitoring manner) the intra-domain service messages of the intra-domain service systems, the message management system may read the intra-domain service messages in the message queue according to a preset period.

Step 104, determining a subscriber system of the intra-domain service message according to the subscription information, converting the intra-domain service information contained in the intra-domain service message into the out-domain service information corresponding to the subscriber system according to the mapping relationship, and generating the out-domain service message containing the out-domain service information according to a second data format configured for the subscriber system.

In the embodiment, in order to ensure the security of each business system in the process of cross-domain message communication, a security policy can be configured in the message management system, and the security policy is used for verifying whether the business messages are safe and reliable. Then, the message management system may perform security check on the obtained intra-domain service message to determine a subscriber system of the intra-domain service message passing the security check.

In particular, the verification logic of the security policy may include identity verification logic, crawler verification logic, anti-duplication processing logic, key verification logic, current limit verification logic, privacy encryption logic, and so forth. Of course, developers can flexibly define various aspects of security verification required by the service type according to actual requirements. For example, a service type (e.g., indicated by a field of the service message) to which the service message belongs may be identified. In the case that the service types may include a basic service and a derived service, the basic service generally focuses on the operation performance, and then a security policy related to the improvement of the operation performance, such as an anti-duplication processing logic and a current limit checking logic, may be defined for the basic service. While the derived service generally focuses on the user identity, a security policy related to guaranteeing the user identity, such as identity checking logic, key checking logic, privacy encryption logic, etc., may be defined for the derived service. Of course, the specification does not limit the specific form of the check logic.

In this embodiment, each service system processes the service message by using a respective data format, and also describes the service information of the data object by using a respective description rule for the same data object, that is, the same service information of the same data object, and description manners adopted in different service systems are different accordingly, and each service system can only identify the service information described by using its own description manner. In the cross-domain message communication scenario, in order to avoid modifying the data format and description rule of each service system to realize zero intrusion to each service system, a mapping relationship can be established for corresponding description modes of the same service information in different service systems, before the message management system sends the screened service messages to the service systems, the description modes of the service information contained in the screened service messages are converted into the description modes which can be identified by the subscriber system according to the mapping relationship, and then the corresponding service messages are regenerated according to the data format used by the subscriber system, so that the cross-domain message communication is realized. Of course, the mapping relationship can be updated with the change of the service.

For example, services in the service system are handled by the micro service application for logic inside each service, and the mapping relationship is uniformly configured in the gateway system of the intra-domain service system, which does not relate to specific services, and it can be understood that all the out-of-domain messages need to pass through the gateway system first and then enter the intra-domain service system. In other words, the mapping is done at the outermost level before entering the intra-domain business systems, and there is no need for each intra-domain business system to complete the operation of the conversion. The gateway system may be independent of the message management system, or may be configured in the message management system, which is not limited in this specification.

In this embodiment, the intra-domain service information and the extra-domain service information belong to different description modes for the same service information of the data object, which can be understood as that the intra-domain service information and the extra-domain service information correspond to the same service information. For example, the user id of the same user, the first user id of the user recorded by the intra-domain service system, and the second user id of the user recorded by the extra-domain service system all correspond to the user.

The message management system needs to convert the service information in the domain into the service information outside the domain which can be identified by the service system outside the domain, and the problem of the read permission of the service information by the service system outside the domain is involved in the process, namely the service information belongs to the private data of the data object. In order to protect the data privacy of the data object, the data object may customize the reading authority of each business system for its own business information, such as embodied by authorization information. Furthermore, the message management system may maintain authorization information of each data object for its own service information, where the authorization information is used to indicate a reading authority of each out-of-domain service system for the corresponding service information. Based on this, the message management system can determine whether the out-of-domain service system has the read authority for the service information of the specified data object according to the authorization information of the specified data object, so as to convert the in-domain service information contained in the in-domain service message under the condition of having the read authority (i.e. convert the in-domain service information corresponding to the service information having the read authority into the out-of-domain service information corresponding to the service information). In other words, in the case where the out-of-domain service system does not have the read authority, the above-described conversion operation is not performed.

Further, the conversion operation performed for the message management system is defined according to the meaning of the fields in the first data format and the second data format. Specifically, there may be first fields with the same meaning in the first data format and the second data format, such as fields both containing information representing user id, user address, etc., and then the information is directly filled in the corresponding fields. That is, for the first field with the same meaning as that in the first data format in the second data format, the message management system may fill the converted out-of-domain service information into the first field in the out-of-domain service message. The second data format may also have fields that are not present in the first data format, such as a field for indicating the gender of the user being included in the second data format, but not included in the first data format. Then, for the second field whose meaning is different from all fields in the first data format in the second data format, under the condition that the domain-outside service system has the reading authority, the domain-outside service information matched with the meaning of the second field can be obtained according to the mapping relation and is filled in the second field in the domain-outside service message.

Step 106, sending the service message outside the domain to the subscriber system, so that the subscriber system receives the service message outside the domain.

Of course, when multiple intra-domain service systems and multiple out-of-domain service systems are involved, the principle of cross-domain message communication is similar to that described above and will not be described herein again. By the cross-domain message management scheme, asynchronous communication between service systems can be realized, and after one service message is sent by the service system, the next message can be sent at any time without waiting for result feedback. Meanwhile, the message management system can connect a plurality of service systems in series on the premise of not modifying the description mode of each service system for the service information and the data format of the service information, thereby achieving the purpose of communication among the service systems. In other words, zero service intrusion of the service system can be realized, the development cost is reduced, and the stability is improved.

For ease of understanding, the process of implementing cross-domain messaging by a message management system is described in detail below with reference to fig. 2. Referring to fig. 2, fig. 2 is a flowchart illustrating another cross-domain message management method according to an exemplary embodiment. As shown in fig. 2, the method is applied to a message management system, and may include the following steps:

step 202, reading the subscription information and the authorization information.

Step 204, obtaining the service message of the message queue.

In this embodiment, a service system that generates a service message is taken as an intra-domain service system, and the service message is generated by the intra-domain service system and transmitted to an extra-domain service system as an example.

Each service system can send the generated service message to a preset message queue, and all the messages sent by the service systems are queued in the message queue to wait for consumption. The message management system can be divided into a message acquisition system and a message push system. The message acquisition system acquires and analyzes the messages (the messages are queued in the message queue and wait to be consumed) sent by the intra-domain service system from the message queue in a message acquisition mode, and then comprehensively filters the messages by combining the read authorization information and subscription information after the messages are analyzed, and converts or enhances the filtered messages.

The user of each service system can authorize the service system to read the authority of the service information, and the authorization information can be recorded in the developer center, or the information acquisition system can read the authorization information from the developer center and record the authorization information locally. The developer center is an abstract definition of a developer, and the developer can publish subscription information through the developer center, so that the developer can be simply understood as a system configuration center provided for the developer. For example, the authorization information may be authorized by an offline user of the service system by means of a code scanning or an offline protocol, and the authorization result is stored in the developer center, or any other server.

Meanwhile, in order to implement cross-domain message communication, each service system can subscribe the service information required by itself to the message management system to cooperatively complete service implementation. Specifically, the service system may provide its own subscription information, which is used to characterize the conditions of its required service message, to the message acquisition system through the developer center. Then, the message acquiring system may read the subscription information of each off-domain service system recorded by the developer center, and read the authorization information of the user (i.e. the data object in the embodiment of fig. 1, which may be a merchant, for example) (for example, the authorization information of the corresponding user is queried according to the user id). Then, the message acquisition system can comprehensively filter the acquired service messages according to the read authorization information and subscription information, and convert or enhance the filtered messages.

And step 206, filtering the obtained service message to obtain the intra-domain service message to be pushed.

The filter preconditions include two, one is a data type defined by the subscription information, and the other is authorization information of the user, the subscribed data type determines which types of message data need to be acquired, and the authorization information of the user determines whether a certain type of message data can be acquired.

And 208, converting or enhancing the service message obtained by filtering to obtain the service message outside the domain.

For example, when a merchant in the platform a in the domain performs an operation of modifying a store name, the message acquiring system may acquire a service message for completing the operation, thereby acquiring a merchant ID, a brand ID, and a store ID of the merchant in the platform a recorded by the message. Assuming that the service message is a message subscribed by the platform B, the merchant ID, the brand ID, and the store ID of the merchant in the platform a need to be converted into the merchant ID, the brand ID, and the store ID of the merchant in the platform B outside the domain through a mapping relationship between service information before the platform a inside the domain and the platform B outside the domain.

For another example, if the business message of the platform B defines the gender of the merchant, the gender information of the merchant can be read according to the merchant ID to fill in the corresponding field of the out-of-domain business message, thereby completing the enhanced operation.

Step 210, selecting a message channel to send the service message outside the domain.

In this embodiment, the message management system further includes a message pushing system, and the message pushing system is configured to push the off-domain service message obtained by the message obtaining system to a corresponding subscriber system.

The message pushing system can select one message sending channel to push messages, and specifically can select different message channel orientations to push messages according to different channels transmitted by users. For example, the message body of the service message includes a field indicating the channel.

Step 212, if the message is successfully sent, step 214 is executed; otherwise, go to step 216.

Step 214, communicating with the out-of-domain service system.

At step 216, a failure message is recorded.

In this embodiment, if the message transmission fails, the message may be retransmitted for the failed message using a message retry mechanism. When the number of times of transmission failure reaches a preset threshold value, the message of transmission failure can be recorded locally.

As can be seen from the foregoing embodiments, in the technical solution of the present specification, two independent service systems generate service messages according to respective data formats, and when the two service systems cooperate to complete a service, from the perspective of any one of the two service systems, the service system itself is an intra-domain service system, and the other is an extra-domain service system.

Referring to fig. 3, fig. 3 is a flowchart illustrating another cross-domain message management method according to an exemplary embodiment. As shown in fig. 3, the method is applied to at least one out-of-domain service system, and may include the following steps:

step 302, generating subscription information of the intra-domain service messages generated respectively aiming at least one intra-domain service system, and sending the generated subscription information to a message management system; the intra-domain service message is generated by an intra-domain service system according to a first data format of the intra-domain service system, and the intra-domain service message comprises intra-domain service information of a specified data object; the message management system maintains subscription information of each off-domain service system aiming at the intra-domain service messages, and a mapping relation between the intra-domain service information corresponding to any service information of the data object in the intra-domain service system and the off-domain service information corresponding to any service information in the off-domain service system;

step 304, receiving an outside-domain service message sent by the message management system when determining that the outside-domain service system is a subscriber system of the inside-domain service message, where the outside-domain service message includes outside-domain service information, the outside-domain service message is generated by the message management system according to a second data format of the outside-domain service system, the subscriber system acquires the inside-domain service message generated by each inside-domain service system by the message management system and determines the inside-domain service message according to the subscription information, and the outside-domain service message is obtained by the message management system by converting the inside-domain service message included in the inside-domain service message according to the mapping relationship.

It should be noted that the description related to the embodiment shown in fig. 1-2 can also be applied to the embodiment shown in fig. 3, and this description is not repeated herein.

Corresponding to the method embodiment, the specification also provides a corresponding device embodiment.

FIG. 4 is a schematic block diagram of an apparatus provided in an exemplary embodiment. Referring to fig. 4, at the hardware level, the apparatus includes a processor 402, an internal bus 404, a network interface 406, a memory 408, and a non-volatile memory 410, but may also include hardware required for other services. One or more embodiments of the present description may be implemented in software, such as by processor 402 reading corresponding computer programs from non-volatile storage 410 into memory 408 and then executing. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 5, the apparatus may be applied to the device shown in fig. 4 to implement the technical solution of the present specification. The device is applied to a message management system, the message management system maintains subscription information of each off-domain service system aiming at intra-domain service messages, and a mapping relation between intra-domain service information corresponding to any service information of a data object in the intra-domain service system and off-domain service information corresponding to any service information in the off-domain service system; the device comprises:

an obtaining unit 51, configured to obtain an intra-domain service message generated by each intra-domain service system according to a first data format of the intra-domain service system, and perform security check on the obtained intra-domain service message; the intra-domain service message comprises intra-domain service information of the specified data object;

a generating unit 52, configured to determine, according to the subscription information, a subscriber system of the intra-domain service message that passes the security check, convert, according to the mapping relationship, the intra-domain service information included in the intra-domain service message into the out-of-domain service information corresponding to the subscriber system, and generate the out-of-domain service message including the out-of-domain service information according to a second data format configured for the subscriber system;

a sending unit 53, configured to send the out-of-domain service message to the subscriber system, so that the subscriber system receives the out-of-domain service message.

Referring to fig. 6, the apparatus may be applied to the device shown in fig. 4 to implement the technical solution of the present specification. The device is applied to a message management system, the message management system maintains subscription information of each off-domain service system aiming at intra-domain service messages, and a mapping relation between intra-domain service information corresponding to any service information of a data object in the intra-domain service system and off-domain service information corresponding to any service information in the off-domain service system; the apparatus may include:

an obtaining unit 61, configured to obtain an intra-domain service message generated by each intra-domain service system according to a first data format of the intra-domain service system, where the intra-domain service message includes intra-domain service information of a specified data object;

a generating unit 62, configured to determine a subscriber system of the intra-domain service message according to the subscription information, convert intra-domain service information included in the intra-domain service message into extra-domain service information corresponding to the subscriber system according to the mapping relationship, and generate an extra-domain service message including the extra-domain service information according to a second data format configured for the subscriber system;

a sending unit 63, configured to send the out-of-domain service message to the subscriber system, so that the subscriber system receives the out-of-domain service message.

Optionally, the intra-domain service messages generated by the intra-domain service systems are added to a preset message queue; the obtaining unit 61 is specifically configured to:

Optionally, the message management system maintains authorization information of the data object for the service information of the data object, where the authorization information is used to indicate a read permission of each out-of-domain service system for the corresponding service information; the generating unit 62 is further configured to:

Optionally, the generating unit 62 is specifically configured to:

Referring to fig. 7, the apparatus may be applied to the device shown in fig. 4 to implement the technical solution of the present specification. The device is applied to at least one out-of-domain service system, and may include:

a generating unit 71, configured to generate subscription information of intra-domain service messages generated for at least one intra-domain service system, and send the generated subscription information to the message management system; the intra-domain service message is generated by an intra-domain service system according to a first data format of the intra-domain service system, and the intra-domain service message comprises intra-domain service information of a specified data object; the message management system maintains subscription information of each off-domain service system aiming at the intra-domain service messages, and a mapping relation between the intra-domain service information corresponding to any service information of the data object in the intra-domain service system and the off-domain service information corresponding to any service information in the off-domain service system;

a receiving unit 72, configured to receive an outside-domain service message sent by the message management system when determining that the outside-domain service system is a subscriber system of the inside-domain service message, where the outside-domain service message includes outside-domain service information, the outside-domain service message is generated by the message management system according to a second data format of the outside-domain service system, the subscriber system obtains the inside-domain service message generated by each inside-domain service system and determines the inside-domain service message according to the subscription information, and the outside-domain service message is obtained by the message management system by converting the inside-domain service message included in the inside-domain service message according to the mapping relationship.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.

Claims

1. A cross-domain message management system, comprising:

2. A cross-domain message management method is characterized in that the method is applied to a message management system, the message management system maintains subscription information of each off-domain service system aiming at intra-domain service messages, and a mapping relation between intra-domain service information corresponding to any service information of a data object in the intra-domain service system and off-domain service information corresponding to any service information in the off-domain service system; the method comprises the following steps:

3. The method according to claim 2, wherein the message management system maintains authorization information of the data object for its own service information, the authorization information indicating the read authority of each out-of-domain service system for the corresponding service information; the method further comprises the following steps:

4. The method of claim 3, wherein generating the out-of-domain service message including the out-of-domain service information according to the second data format of the subscriber system comprises:

5. A cross-domain message management method is characterized in that the method is applied to a message management system, the message management system maintains subscription information of each off-domain service system aiming at intra-domain service messages, and a mapping relation between intra-domain service information corresponding to any service information of a data object in the intra-domain service system and off-domain service information corresponding to any service information in the off-domain service system; the method comprises the following steps:

6. A cross-domain message management method is applied to at least one out-of-domain service system and comprises the following steps:

7. A cross-domain message management device is characterized in that the device is applied to a message management system, the message management system maintains subscription information of each off-domain service system aiming at intra-domain service messages, and a mapping relation between intra-domain service information corresponding to any service information of a data object in the intra-domain service system and off-domain service information corresponding to any service information in the off-domain service system; the device comprises:

8. A cross-domain message management device is characterized in that the device is applied to a message management system, the message management system maintains subscription information of each off-domain service system aiming at intra-domain service messages, and a mapping relation between intra-domain service information corresponding to any service information of a data object in the intra-domain service system and off-domain service information corresponding to any service information in the off-domain service system; the device comprises:

9. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of any one of claims 2-6 by executing the executable instructions.

10. A computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, perform the steps of the method according to any one of claims 2-6.