Message synchronization method and device

文档序号：1936978 发布日期：2021-12-07 浏览：15次中文

阅读说明：本技术 一种消息同步方法和装置 (Message synchronization method and device ) 是由王雷于 2020-11-17 设计创作，主要内容包括：本发明公开了一种消息同步方法和装置,涉及计算机技术领域。该方法的一具体实施方式包括：接收业务系统下发的业务数据、用户数据和所述业务系统的信息；其中,所述用户数据包括用户标识或者应用程序标识；根据所述业务数据、所述用户数据和所述业务系统的信息,生成消息的消息体以及所述消息的消息主题；将所述消息同步至消息中间件。该实施方式能够解决无法及时获取数据的技术问题。(The invention discloses a message synchronization method and device, and relates to the technical field of computers. One embodiment of the method comprises: receiving service data, user data and information of the service system, wherein the service data, the user data and the information of the service system are issued by the service system; wherein the user data comprises a user identification or an application identification; generating a message body of the message and a message subject of the message according to the service data, the user data and the information of the service system; synchronizing the message to a message middleware. The implementation method can solve the technical problem that data cannot be acquired in time.)

1. A message synchronization method, comprising:

receiving service data, user data and information of the service system, wherein the service data, the user data and the information of the service system are issued by the service system; wherein the user data comprises a user identification or an application identification;

generating a message body of the message and a message subject of the message according to the service data, the user data and the information of the service system;

synchronizing the message to a message middleware.

2. The method of claim 1, wherein generating a message body of a message and a message subject of the message according to the service data, the user data and the information of the service system comprises:

judging whether the service data has a synchronization authority or not according to the user data;

if yes, generating a message body of the message according to the service data, and generating a message theme of the message according to the information of the service system and the user data.

3. The method of claim 2, wherein the user data comprises a user identification;

judging whether the service data has the synchronization authority according to the user data, including:

and judging whether the user identification exists in a pre-stored authorized user identification list or not, thereby judging whether the service data has the synchronization authority or not.

4. The method of claim 3, wherein generating a message topic for the message based on the information of the business system and the user data comprises:

acquiring an application program identification list corresponding to the user identification;

splicing the information of the service system and the application program identification in the application program identification list into a message subject of the message; wherein the information of the service system includes a name of the service system.

5. The method of claim 2, wherein the user data comprises an application identification;

judging whether the service data has the synchronization authority according to the user data, including:

and judging whether the application program identifier exists in a prestored authorized application program identifier list or not, thereby judging whether the service data has the synchronization authority or not.

6. The method of claim 5, wherein generating a message topic for the message based on the information of the business system and the user data comprises:

splicing the information of the service system and the application program identification into a message subject of the message; wherein the information of the service system includes a name of the service system.

7. The method of claim 1, wherein synchronizing the message to a message middleware comprises:

checking whether the mark of the message is sent;

if not, synchronizing the message to a message middleware;

and receiving a success identifier returned by the message middleware, and setting the mark of the message as sent.

8. A message synchronization apparatus, comprising:

the receiving module is used for receiving service data, user data and information of the service system which are issued by the service system; wherein the user data comprises a user identification or an application identification;

the generating module is used for generating a message body of the message and a message subject of the message according to the service data, the user data and the information of the service system;

a synchronization module to synchronize the message to a message middleware.

9. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

the one or more programs, when executed by the one or more processors, implement the method of any of claims 1-7.

10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for synchronizing messages.

Background

In recent years, ISVs (third-party independent software service providers, developers who develop software for the second time, for example, application software having an order printing function) relying on an open platform have been developed rapidly, and users of various merchants are served with the data and service capabilities of the open platform.

In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:

at present, many merchant users and ISVs adopt an interface mode to regularly acquire main information such as orders, articles, refunds and the like, but due to the influences of networks, servers, development technology levels and the like, the phenomena of data repetition, data missing or data unavailable acquisition often occur, so that data cannot be acquired in time, the service operation efficiency is influenced, and a large amount of network resources are consumed.

Disclosure of Invention

In view of this, embodiments of the present invention provide a message synchronization method and apparatus, so as to solve the technical problem that data cannot be obtained in time.

To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a message synchronization method, including:

generating a message body of the message and a message subject of the message according to the service data, the user data and the information of the service system;

synchronizing the message to a message middleware.

Optionally, generating a message body of a message and a message topic of the message according to the service data, the user data, and the information of the service system, includes:

judging whether the service data has a synchronization authority or not according to the user data;

if yes, generating a message body of the message according to the service data, and generating a message theme of the message according to the information of the service system and the user data.

Optionally, the user data comprises a user identification;

judging whether the service data has the synchronization authority according to the user data, including:

and judging whether the user identification exists in a pre-stored authorized user identification list or not, thereby judging whether the service data has the synchronization authority or not.

Optionally, generating a message topic of the message according to the information of the service system and the user data includes:

acquiring an application program identification list corresponding to the user identification;

Optionally, the user data comprises an application identity;

judging whether the service data has the synchronization authority according to the user data, including:

Optionally, generating a message topic of the message according to the information of the service system and the user data includes:

Optionally, synchronizing the message to a message middleware, comprising:

checking whether the mark of the message is sent;

if not, synchronizing the message to a message middleware;

and receiving a success identifier returned by the message middleware, and setting the mark of the message as sent.

In addition, according to another aspect of the embodiments of the present invention, there is provided a message synchronization apparatus, including:

the generating module is used for generating a message body of the message and a message subject of the message according to the service data, the user data and the information of the service system;

a synchronization module to synchronize the message to a message middleware.

Optionally, the generating module is further configured to:

judging whether the service data has a synchronization authority or not according to the user data;

if yes, generating a message body of the message according to the service data, and generating a message theme of the message according to the information of the service system and the user data.

Optionally, the user data comprises a user identification;

the generation module is further to:

and judging whether the user identification exists in a pre-stored authorized user identification list or not, thereby judging whether the service data has the synchronization authority or not.

Optionally, the generating module is further configured to:

acquiring an application program identification list corresponding to the user identification;

Optionally, the user data comprises an application identity;

the generation module is further to:

Optionally, the generating module is further configured to:

Optionally, the synchronization module is further configured to:

checking whether the mark of the message is sent;

if not, synchronizing the message to a message middleware;

and receiving a success identifier returned by the message middleware, and setting the mark of the message as sent.

According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including:

one or more processors;

a storage device for storing one or more programs,

when the one or more programs are executed by the one or more processors, the one or more processors implement the method of any of the embodiments described above.

According to another aspect of the embodiments of the present invention, there is also provided a computer readable medium, on which a computer program is stored, which when executed by a processor implements the method of any of the above embodiments.

One embodiment of the above invention has the following advantages or benefits: because the technical means of synchronizing the message to the message middleware by generating the message body and the message theme of the message according to the service data, the user data and the information of the service system issued by the service system is adopted, the technical problem that the data cannot be acquired in time in the prior art is solved. The embodiment of the invention actively pushes the data to the message middleware, so that a user can acquire the service data in real time, the data is ensured to be reliable, and the situations of missing list, data repetition and the like can not occur; and can provide stable data assurance, make the user need not to check data again, can direct use, can also guarantee data security simultaneously.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

fig. 1 is a schematic diagram of a main flow of a message synchronization method according to an embodiment of the present invention;

FIG. 2 is a system framework diagram according to an embodiment of the invention;

fig. 3 is a schematic diagram of a main flow of a message synchronization method according to a referential embodiment of the present invention;

FIG. 4 is a schematic diagram of a configuration message according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of an application publication message, according to an embodiment of the invention;

fig. 6 is a schematic diagram of a main flow of a message synchronization method according to another referenceable embodiment of the present invention;

fig. 7 is a schematic diagram of the main modules of a message synchronization apparatus according to an embodiment of the present invention;

FIG. 8 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

fig. 9 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Fig. 1 is a schematic diagram of a main flow of a message synchronization method according to an embodiment of the present invention. As an embodiment of the present invention, as shown in fig. 1, the message synchronization method may include:

step 101, receiving service data, user data and information of the service system issued by the service system.

As shown in fig. 2, the open platform may receive service data, user data and information of each service system sent by each upstream service system. Alternatively, the business system may be an order system, an inventory system, a logistics system, or an after-sales system, etc. Optionally, the user data includes a user identifier or an application identifier, and in an embodiment of the present invention, the user may be a merchant user. It should be noted that the user data may include one user identifier, or may include a plurality of user identifiers; the user data may comprise one application identity or a plurality of application identities. Optionally, the information of the service system may include a name of the service system, such as a full name or a short name.

And 102, generating a message body of the message and a message subject of the message according to the service data, the user data and the information of the service system.

After receiving service data, user data and information of the service system sent by an upstream service system, the open platform generates a message body of a message according to the service data, and simultaneously generates a message theme of the message according to the user data and the information of the service system.

Optionally, the received data is flushed prior to step 102. Specifically, required data (such as service data, user data, information of a service system, and the like) is disassembled from data issued by an upstream service system, and then the data is cleaned, for example, whether the data is empty is judged first, then whether the data is matched with a defined format is checked, finally, regular check (such as regular check mobile phone number) is started according to different fields, and the data which does not pass is regarded as dirty data and can be discarded.

Optionally, step 102 may comprise: judging whether the service data has a synchronization authority or not according to the user data; if yes, generating a message body of the message according to the service data, and generating a message theme of the message according to the information of the service system and the user data. In the embodiment of the invention, whether the service data has the synchronization authority is judged according to the user data, if the service data has the synchronization authority, a message body of a message is generated according to the service data, a message subject of the message is generated according to the information of the service system and the user data, and if the service data does not have the synchronization authority, the received service data, the received user data, the information of the service system and the like are directly ignored. Therefore, the embodiment of the invention provides stable data guarantee, so that a user can directly use the data without verifying the data.

Optionally, the user data comprises a user identification; judging whether the service data has the synchronization authority according to the user data, including: and judging whether the user identification exists in a pre-stored authorized user identification list or not, thereby judging whether the service data has the synchronization authority or not. In some embodiments of the present invention, the user data sent by the upstream service system includes a user identifier, the open platform stores an authorized user identifier list in advance, the open platform determines whether the user identifier sent by the upstream service system exists in the authorized user identifier list, if so, it indicates that the user is authorized, the permission check is passed, and the service data has a synchronization permission.

Optionally, generating a message topic of the message according to the information of the service system and the user data includes: acquiring an application program identification list corresponding to the user identification; and splicing the information of the service system and the application program identification in the application program identification list into a message subject of the message. In some embodiments of the present invention, the open platform may further pre-store an application identifier list corresponding to each authorized user identifier, acquire the application identifier list corresponding to the authorized user identifier if the permission check passes, and then splice information of the service system and the application identifiers in the application identifier list into a message topic of the message. Wherein the information of the service system includes a name of the service system. For example: message topic for order system: order _ appkey. It should be noted that, if there are multiple application identifiers in the application identifier list, the information of the service system and each application identifier are respectively spliced into a message topic.

Optionally, the user data comprises an application identity; judging whether the service data has the synchronization authority according to the user data, including: and judging whether the application program identifier exists in a prestored authorized application program identifier list or not, thereby judging whether the service data has the synchronization authority or not. In some embodiments of the present invention, the user data sent by the upstream service system includes an application identifier, the open platform stores an authorized application identifier list in advance, the open platform determines whether the application identifier sent by the upstream service system exists in the authorized application identifier list, if so, the application identifier is authorized, the permission check is passed, and the service data has a synchronization permission.

Optionally, generating a message topic of the message according to the information of the service system and the user data includes: and splicing the information of the service system and the application program identification into a message subject of the message. In some embodiments of the present invention, if the permission check passes, the information of the service system and the application program identifier sent by the service system are directly spliced into the message subject of the message. Wherein the information of the service system includes a name of the service system. It should be noted that, if there are multiple application program identifiers issued by the service system, the information of the service system and each application program identifier are respectively spliced into a message topic.

Step 103, synchronizing the message to the message middleware.

The open platform synchronizes the generated message to a message middleware (such as a cloud message middleware). The ISV can pull the message from the message middleware, so that the service data can be acquired in real time.

Optionally, step 103 may comprise: checking whether the mark of the message is sent; if not, synchronizing the message to a message middleware; and receiving a success identifier returned by the message middleware, and setting the mark of the message as sent. Because the open platform has a retry mechanism, the same message may be sent multiple times due to an exception, so that each message needs to be configured with a unique credential. And after the message is successfully sent, setting the identifier of the message as sent. Therefore, before sending the message, whether the message is sent or not is checked, if the message is sent, the message is ignored, and if the message is not sent, the message is sent, so that the idempotency of the data is ensured. And finally, the development platform directly pushes the message to a message middleware according to different themes, returns a success identifier, proves that the pushing is finished, and sets the message identifier as sent.

Optionally, the data may also be encrypted before the message is synchronized to the message middleware. Sensitive data (such as a mobile phone number, a mailbox and the like) exist in service data, so that RSA encryption needs to be carried out on the sensitive data, data confusion can also be carried out on a user account, and unique data without rules is generated, so that the safety and reliability of the data are ensured. As shown in fig. 2, the ISV pulls the message from the message middleware, parses the message, and decrypts the sensitive data, thereby acquiring the service data in real time. Therefore, the embodiment of the invention not only can synchronize data in real time, but also can ensure the safety, reliability and stability of the data.

According to the various embodiments described above, it can be seen that the technical means of synchronizing the message to the message middleware by generating the message body and the message subject of the message according to the service data, the user data and the information of the service system issued by the service system in the embodiments of the present invention solves the technical problem that the data cannot be obtained in time in the prior art. The embodiment of the invention actively pushes the data to the message middleware, so that a user can acquire the service data in real time, the data is ensured to be reliable, and the situations of missing list, data repetition and the like can not occur; and can provide stable data assurance, make the user need not to check data again, can direct use, can also guarantee data security simultaneously.

Fig. 3 is a schematic diagram of a main flow of a message synchronization method according to a referential embodiment of the present invention. As still another embodiment of the present invention, as shown in fig. 3, the message synchronization method may include:

step 301, configure the message.

The message may be preconfigured, as shown in FIG. 4, according to the message template, and the json string within the messagebody of the message is entered in the message body instance entry box

Example (c):

{

"vender Id", "xxxx",// Merchant user ID, for authorization mode

"appkeyArray" [ "xxxx", "xxxx" ],// Appkey array for specifying Appkey patterns

MessageBody {// JOS will forward the content in the messageBody directly

"xxxx"// used herein to define the traffic field }

}

Such as: { "Mobile": Mobile number "," Price ": Price", "orderId": order number }

Further, basic information such as version number and name of the message can be configured.

Further, a message type may be configured, and the message type is used to determine the grouping of messages (such as order messages, inventory messages, or after-sales messages, etc.).

Further, a filtering mode can be configured, such as an authorization mode, a specified AppKey mode, or a broadcast mode.

In the authorization mode, data sent by a service system needs to contain user identifiers (renderId), and an appkey list corresponding to each authorized user identifier is stored in an open platform; under a designated AppKey mode, data issued by a service system needs to contain an AppKey list; in broadcast mode, all subscribing users can receive the message.

Step 302, apply for publishing messages.

After the message configuration is completed, the application issues a message, as shown in fig. 5. There are currently two modes of release: the first is publishing to the outside, all developers can see messages and subscribe; and the second method is directed release, and only a specific application type can acquire the message and is realized through message authority.

After the issued message is approved, and after the issued message is approved, the multithreading is automatically started to process the message. Multithreading is to increase the processing speed of message data and process multiple pieces of data simultaneously in parallel. Each thread performs step 303-310.

Step 303, receiving the service data, the user identifier and the name of the service system sent by the service system.

The open platform can receive the service data, the user identification and the name of each service system issued by each upstream service system. Alternatively, the business system may be an order system, an inventory system, a logistics system, or an after-sales system, etc.

Step 304, judging whether the user identification exists in a pre-stored authorized user identification list; if yes, go to step 305; if not, the process is ended.

The open platform stores an authorized user identification list in advance, and judges whether a user identification issued by an upstream service system exists in the authorized user identification list or not.

And 305, generating a message body of the message according to the service data.

If the user identification exists in the pre-stored authorized user identification list, the user is authorized, the authority verification is passed, and the service data has the synchronous authority, a message body of the message is generated according to the service data.

Step 306, acquiring an application program identifier list corresponding to the user identifier.

The open platform also stores an application program identification list corresponding to each authorized user identification in advance, and if the authority verification is passed, the application program identification list corresponding to the authorized user identification is obtained.

Step 307, the name of the service system and the application program identifier in the application program identifier list are spliced into the message subject of the message.

And after the application program identification list corresponding to the user identification is obtained, splicing the name of the service system and the application program identification in the application program identification list into the message theme of the message.

Step 308, checking whether the mark of the message is sent; if yes, ending; if not, go to step 309.

Step 309, synchronize the message to the message middleware.

And 310, receiving a success identifier returned by the message middleware, and setting the mark of the message as sent.

In addition, in one embodiment of the present invention, the detailed implementation of the message synchronization method is described in detail above, and therefore the repeated content is not described herein.

Fig. 6 is a schematic diagram of a main flow of a message synchronization method according to another referenceable embodiment of the present invention. As another embodiment of the present invention, as shown in fig. 6, the message synchronization method may include:

step 601, configuring a message.

The message may be preconfigured, as shown in fig. 4, and the configuration process is similar to step 301, and is not described in detail.

Step 602, apply for issuing a message.

This step is similar to step 302 and will not be described again.

Step 603, receiving the service data, the application program identifier and the name of the service system sent by the service system.

The open platform can receive service data, application program identification and the name of each service system sent by each service system at the upstream. Alternatively, the business system may be an order system, an inventory system, a logistics system, or an after-sales system, etc.

Step 604, judging whether the application program identifier exists in a prestored authorized application program identifier list; if yes, go to step 605; if not, the process is ended.

The open platform prestores an authorized application program identification list, and judges whether an application program identification issued by an upstream service system exists in the authorized application program identification list or not.

Step 605, generating a message body of the message according to the service data.

And if the application program identification exists in the pre-stored authorized application program identification list, the application program is authorized, the authority verification is passed, and the service data has the synchronous authority, generating a message body of the message according to the service data.

Step 606, the name of the service system and the application program identification are spliced into the message subject of the message.

And if the authority passes the verification, directly splicing the name of the service system issued by the service system and the application program identifier into the message subject of the message.

Step 607, checking whether the mark of the message is sent; if yes, ending; if not, go to step 608.

Step 608, synchronize the message to the message middleware.

Step 609, receiving the success mark returned by the message middleware, and setting the mark of the message as sent.

In addition, in another embodiment of the present invention, the detailed implementation of the message synchronization method is described in detail above, and therefore the repeated content is not described herein.

Fig. 7 is a schematic diagram of main modules of a message synchronization apparatus according to an embodiment of the present invention, and as shown in fig. 7, the message synchronization apparatus 700 includes a receiving module 701, a generating module 702, and a synchronization module 703; the receiving module 701 is configured to receive service data, user data, and information of a service system, which are issued by the service system; wherein the user data comprises a user identification or an application identification; the generating module 702 is configured to generate a message body of a message and a message subject of the message according to the service data, the user data, and the information of the service system; the synchronization module 703 is configured to synchronize the message to the message middleware.

Optionally, the generating module 702 is further configured to:

judging whether the service data has a synchronization authority or not according to the user data;

if yes, generating a message body of the message according to the service data, and generating a message theme of the message according to the information of the service system and the user data.

Optionally, the user data comprises a user identification;

the generating module 702 is further configured to:

and judging whether the user identification exists in a pre-stored authorized user identification list or not, thereby judging whether the service data has the synchronization authority or not.

Optionally, the generating module 702 is further configured to:

acquiring an application program identification list corresponding to the user identification;

Optionally, the user data comprises an application identity;

the generating module 702 is further configured to:

Optionally, the generating module 702 is further configured to:

Optionally, the synchronization module 703 is further configured to:

checking whether the mark of the message is sent;

if not, synchronizing the message to a message middleware;

and receiving a success identifier returned by the message middleware, and setting the mark of the message as sent.

It should be noted that, in the implementation of the message synchronization apparatus of the present invention, details have been described in the above message synchronization method, and therefore, a repeated description is not repeated here.

Fig. 8 shows an exemplary system architecture 800 to which the message synchronization method or the message synchronization apparatus of the embodiments of the present invention may be applied.

As shown in fig. 8, the system architecture 800 may include terminal devices 801, 802, 803, a network 804, and a server 805. The network 804 serves to provide a medium for communication links between the terminal devices 801, 802, 803 and the server 805. Network 804 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.

A user may use the terminal devices 801, 802, 803 to interact with a server 805 over a network 804 to receive or send messages or the like. The terminal devices 801, 802, 803 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).

The terminal devices 801, 802, 803 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 805 may be a server that provides various services, such as a back-office management server (for example only) that supports shopping-like websites browsed by users using the terminal devices 801, 802, 803. The background management server can analyze and process the received data such as the article information query request and feed back the processing result to the terminal equipment.

It should be noted that the message synchronization method provided by the embodiment of the present invention is generally executed by the server 805, and accordingly, the message synchronization apparatus is generally disposed in the server 805.

It should be understood that the number of terminal devices, networks, and servers in fig. 8 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 9, shown is a block diagram of a computer system 900 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 9, the computer system 900 includes a Central Processing Unit (CPU)901 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM903, various programs and data necessary for the operation of the system 900 are also stored. The CPU 901, ROM 902, and RAM903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.

The following components are connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section 907 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The above-described functions defined in the system of the present invention are executed when the computer program is executed by a Central Processing Unit (CPU) 901.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer programs according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a receiving module, a generating module, and a synchronizing module, where the names of the modules do not in some cases constitute a limitation on the modules themselves.

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, implement the method of: receiving service data, user data and information of the service system, wherein the service data, the user data and the information of the service system are issued by the service system; wherein the user data comprises a user identification or an application identification; generating a message body of the message and a message subject of the message according to the service data, the user data and the information of the service system; synchronizing the message to a message middleware.

According to the technical scheme of the embodiment of the invention, the technical means that the message body and the message theme of the message are generated according to the service data, the user data and the information of the service system issued by the service system, so that the message is synchronized to the message middleware is adopted, and the technical problem that the data cannot be acquired in time in the prior art is solved. The embodiment of the invention actively pushes the data to the message middleware, so that a user can acquire the service data in real time, the data is ensured to be reliable, and the situations of missing list, data repetition and the like can not occur; and can provide stable data assurance, make the user need not to check data again, can direct use, can also guarantee data security simultaneously.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

20页详细技术资料下载

Message synchronization method and device

相关技术

网友询问留言