CN112087362B

CN112087362B - Message forwarding method and device between clients and terminal

Info

Publication number: CN112087362B
Application number: CN201910511802.1A
Authority: CN
Inventors: 陈晓波; 王青; 李斌; 罗程
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-06-13
Filing date: 2019-06-13
Publication date: 2021-12-07
Anticipated expiration: 2039-06-13
Also published as: CN112087362A

Abstract

The embodiment of the application discloses a message forwarding method, a message forwarding device and a terminal, which are used for improving message forwarding efficiency and solving the problem of message compatibility when the message is forwarded across clients. The method provided by the embodiment of the application comprises the following steps: the message intercommunication device receives a conversion request sent by a first application program server, and acquires a first message from the conversion request, wherein the first message is packaged by adopting a first format; converting the first message into a second message, wherein the second message is packaged in a second format, and the second format is a message format which can be identified by a second application program client; and sending a second message to the first application server, wherein the second message is sent to the first application client by the first application server, and after the first application client jumps to the second application client, the first application client sends the second message to the second application client, and the first application client and the second application client run on the same terminal.

Description

Message forwarding method and device between clients and terminal

Technical Field

The embodiment of the application relates to the technical field of computers, in particular to a message forwarding method and device and a terminal.

Background

At present, people can operate one or more application programs installed on terminal equipment such as a mobile phone, a tablet or a notebook computer, and the like, wherein the application programs installed on the terminal equipment are various, such as enterprise WeChat and WeChat. And messages can be forwarded between the application programs.

Currently, when message forwarding is performed between application programs on terminal devices, the message forwarding can be performed based on an open interface component of an application program, for example, an OpenSDK interface component of a wechat application program provides an interface capability for sharing chat records, and an enterprise wechat application program can package various message type data in the chat records into corresponding formats according to the interface capability in the OpenSDK and transmit the formats to a wechat interface. In addition, the conversation message in the enterprise wechat application program on the terminal equipment can be shared with the wechat application program through 'multi-selection-forwarding to wechat', the conversation message can be a chat record generated in the enterprise wechat application program, and the chat record is carried in a PDF file format.

The problem of poor expansibility exists when the message is forwarded through the development interface component of one application program, and if the type of the message to be forwarded is expanded, the development interface component needs to be updated every time, so that the message forwarding efficiency is reduced. In addition, because the information carried by the PDF file format is limited, the communication experience between the enterprise wechat application program and the wechat application program is poor. When the PDF file mode is browsed and viewed, a great gap exists between the PDF file mode and a display mode of a native chat record in a wechat application program, and complete compatibility of message contents cannot be realized.

Disclosure of Invention

The embodiment of the application provides a message forwarding method, a message forwarding device and a terminal, which are used for improving the message forwarding efficiency and solving the problem of message compatibility when the message is forwarded across clients.

The embodiment of the application provides the following technical scheme:

in one aspect, an embodiment of the present application provides a message forwarding method, including:

the method comprises the steps that a message intercommunication device receives a conversion request sent by a first application server and obtains a first message from the conversion request, wherein the first message is obtained by the first application server from a first application client, the first message is packaged in a first format, and the first format is a message format which can be identified by the first application client;

the message intercommunication device converts the first message into a second message, the second message is packaged by adopting a second format, and the second format is a message format which can be identified by a second application program client;

the message intercommunication device sends the second message to the first application server, the second message is sent to the first application client by the first application server, after the first application client jumps to the second application client, the second message is sent to the second application client by the first application client, and the first application client and the second application client run on the same terminal.

On one hand, an embodiment of the present application further provides a message forwarding method, including:

a first application program client determines a first message to be forwarded, wherein the first message is packaged in a first format, and the first format is a message format which can be identified by the first application program client;

the first application program client sends a conversion request to a first application program server, wherein the conversion request carries the first message, the conversion request is sent to a message intercommunication device by the first application program server, the message intercommunication device converts the first message into a second message and sends the second message to the first application program server, the second message is packaged in a second format, and the second format is a message format which can be identified by the second application program client;

the first application program client receives the second message sent by the first application program server;

and after the first application program client jumps to the second application program client, the first application program client sends the second message to the second application program client, and the first application program client and the second application program client run on the same terminal.

after a first application program client side jumps to a second application program client side, the second application program client side receives a second message sent by the first application program client side, and the first application program client side and the second application program client side run on the same terminal; the second message is sent to the first application program client through the first application program server after being converted by the message intercommunication device, the first message is packaged in a first format, and the first format is a message format which can be identified by the first application program client;

and the second application program client analyzes the second message according to the second format, wherein the second format is a message format which can be identified by the second application program client.

In one aspect, an embodiment of the present application further provides a message interworking apparatus, including:

the receiving module is used for receiving a conversion request sent by a first application program server;

a processing module, configured to obtain a first message from the conversion request, where the first message is obtained by the first application server from a first application client, and the first message is encapsulated in a first format, where the first format is a message format that can be identified by the first application client;

the processing module is further configured to convert the first message into a second message, where the second message is encapsulated in a second format, and the second format is a message format that can be identified by a second application client;

and the sending module is used for sending the second message to the first application server, the second message is sent to the first application client by the first application server, when the first application client jumps to the second application client, the second message is sent to the second application client by the first application client, and the first application client and the second application client run on the same terminal.

In the foregoing aspect, the constituent modules of the message interworking apparatus may further perform the steps described in the foregoing aspect and various possible implementations, as described in detail in the foregoing aspect and various possible implementations.

In one aspect, an embodiment of the present application further provides an application client, where the application client is specifically a first application client, and the first application client includes:

the processing module is used for determining a first message to be forwarded, wherein the first message is packaged in a first format, and the first format is a message format which can be identified by the first application program client;

a sending module, configured to send a conversion request to a first application server, where the conversion request carries the first message, where the conversion request is sent by the first application server to a message interworking apparatus, the message interworking apparatus converts the first message into a second message, and sends the second message to the first application server, where the second message is encapsulated in a second format, and the second format is a message format that can be identified by a second application client;

a receiving module, configured to receive the second message sent by the first application server;

the sending module is further configured to send the second message to the second application client after the first application client jumps to the second application client, where the first application client and the second application client operate on the same terminal.

In the foregoing aspect, the component modules of the first application client may further perform the steps described in the foregoing aspect and various possible implementations, as described in detail in the foregoing aspect and various possible implementations.

In one aspect, an embodiment of the present application further provides an application client, where the application client is specifically a second application client, and the second application client includes:

the receiving module is used for receiving a second message sent by a first application program client after the first application program client jumps to a second application program client, and the first application program client and the second application program client run on the same terminal; the second message is sent to the first application program client through the first application program server after being converted by the message intercommunication device, the first message is packaged in a first format, and the first format is a message format which can be identified by the first application program client;

and the processing module is used for analyzing the second message according to the second format, wherein the second format is a message format which can be identified by the second application program client.

In the foregoing aspect, the constituent modules of the second application client may further perform the steps described in the foregoing aspect and various possible implementations, as described in detail in the foregoing aspect and various possible implementations.

On the other hand, an embodiment of the present application provides a terminal, including: a processor, a memory; the memory is used for storing instructions; the processor is configured to execute the instructions in the memory to cause the terminal to perform the method according to any one of the preceding aspects. Specifically, the terminal may specifically be the message interworking apparatus, the first application client, and the second application client.

In another aspect, the present invention provides a computer-readable storage medium, which stores instructions that, when executed on a computer, cause the computer to perform the method of the above aspects.

In an embodiment of the application, a first application server obtains a first message from a first application client and then sends a conversion request to a message interworking device, the message interworking device obtains the first message from the conversion request, the first message is encapsulated in a first format, the first format is a message format recognizable by the first application client, the message interworking device converts the first message into a second message, the second message is encapsulated in a second format, the second format is a message format recognizable by the second application client, the message interworking device sends the second message to the first application server, the first application server sends the second message to the first application client, and the first application client sends the second message to the second application client after the first application client jumps to the second application client, the first application client and the second application client run on the same terminal. The message intercommunication device in the embodiment of the application has a message format conversion function, so that a first message can be converted into a second message, after a first application client side jumps to a second application client side on the same terminal, the second application client side receives the second message sent by the first application client side, therefore, the second application client side can analyze the second message according to a second format which can be identified by the second application client side, and the second message sent by the first application client side is the message format which can be directly identified by the second application client side, so that the message forwarding efficiency is improved, and the problem of message compatibility when the message is forwarded across the client sides is solved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings according to these drawings.

Fig. 1a is a schematic structural diagram of a message forwarding system according to an embodiment of the present application;

fig. 1b is a schematic structural diagram of another message forwarding system provided in the embodiment of the present application;

fig. 2 is an interaction flow diagram of a message forwarding method according to an embodiment of the present application;

fig. 3 is an interaction flow diagram of a message forwarding method according to an embodiment of the present application;

fig. 4 is an interaction flow diagram of a message forwarding method according to an embodiment of the present application;

fig. 5 is an interaction flow diagram of a message forwarding method according to an embodiment of the present application;

fig. 6 is a schematic diagram of a system architecture of a chat record forwarding scenario of a message forwarding system according to an embodiment of the present application;

fig. 7 is a schematic flow chart illustrating an implementation process of chat record conversion and forwarding according to an embodiment of the present application;

fig. 8 is a schematic diagram of message format conversion provided in an embodiment of the present application;

fig. 9a is a schematic diagram of a chat record generated by an enterprise wechat client according to an embodiment of the present application;

fig. 9b is a schematic diagram illustrating an effect of a chat log forwarding entry provided in an embodiment of the present application;

fig. 10 is a schematic diagram illustrating an effect of forwarding a chat record to a chat client according to an embodiment of the present application;

fig. 11a is a schematic diagram illustrating an effect of a wechat client side after forwarding a chat record according to an embodiment of the present application;

fig. 11b is a schematic view of chat content of the wechat client side after forwarding the chat records according to the embodiment of the present application;

fig. 12a is a schematic diagram illustrating an effect of an enterprise WeChat client side after forwarding a chat record according to an embodiment of the present application;

fig. 12b is a schematic diagram of chat content of an enterprise WeChat client side after forwarding of a chat record according to an embodiment of the present application;

fig. 13a is a schematic diagram illustrating an effect of forwarding a chat record containing an applet on a WeChat client side according to an embodiment of the present application;

fig. 13b is a schematic diagram illustrating an effect of forwarding a chat record containing an applet on an enterprise WeChat client side according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a message interworking apparatus according to an embodiment of the present application;

fig. 15 is a schematic structural diagram illustrating a first application client according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a second application client according to an embodiment of the present application;

fig. 17 is a schematic structural diagram of a component in which the message forwarding method provided in the embodiment of the present application is applied to a terminal;

fig. 18 is a schematic structural diagram of a server to which the message forwarding method provided in the embodiment of the present application is applied.

Detailed Description

In order to make the objects, features and advantages of the embodiments of the present application more obvious and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the embodiments described below are only a part of the embodiments of the present application, but not all the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present application belong to the scope of protection of the embodiments in the present application.

The terms "comprises" and "comprising," and any variations thereof, in the description and claims of embodiments of the present application and the above-described drawings, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of elements is not necessarily limited to those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.

First, a system architecture applied to the message forwarding method provided in the embodiment of the present application is introduced, and as shown in fig. 1a, a schematic structural diagram of a message forwarding system provided in the embodiment of the present application is shown. Message forwarding system 1000 may include: a message interworking device 1001, a first application server 1002, a first application client 1003, a second application client 1004. The message interworking apparatus 1001 may communicate with a first application server 1002, where the first application server 1002 is a background server of a first application client 1003, and the first application server 1002 is configured to provide a background support service for the first application client 1003. For example, where the first application client 1003 is an enterprise wechat client, the first application server 1002 may be an enterprise wechat server (i.e., an enterprise wechat back office). The first application client 1003 needs to communicate with the message interworking means 1001 through the first application server 1002. In the embodiment of the present application, the message interworking apparatus 1001 may be deployed on one entity device, or may be deployed in a cloud, and the deployment manner of the message interworking apparatus 1001 is not limited.

The message interworking apparatus 1001 may be configured to convert message formats that can be supported by different application clients, for example, the message interworking apparatus 1001 has a function of converting message formats between heterogeneous systems, that is, has a hub capability of converting message formats in the heterogeneous systems, for example, the message interworking apparatus 1001 may be configured to convert message formats that can be supported by two application clients. In this embodiment of the present application, the Message interworking apparatus 1001 may be implemented in a form of a terminal or a server, specifically, the Message interworking apparatus 1001 may be an Instant Message unit (IMUnion), and the Message interworking apparatus 1001 may also be referred to as an interworking background or an IMUnion background, which is not limited herein.

The first Application client 1003 and the second Application client 1004 may be clients that respectively use different Applications (APPs), and the first Application client 1003 and the second Application client 1004 respectively run different applications, for example, the first Application client 1003 may be office communication software, and the second Application client 1004 may be social instant communication software. Specifically, the first application client 1003 may be a business WeChat, and the second application client 1004 may be a WeChat. In this embodiment of the application, the first application client 1003 and the second application client 1004 support a message type format recognized by each application program, for example, the message type format supported by the first application client 1003 is a protobuf encoded format, and the message type format supported by the second application client 1004 is a json string encoded format.

In this embodiment of the application, the first application client and the second application client run on the same terminal, for example, an enterprise wechat client and a wechat client may be installed on the same terminal at the same time, and a user may perform a skip control operation on the terminal to control which application client is displayed on a main interface of the terminal.

It should be noted that the application types used by the first application client 1003 and the second application client 1004, and the message format types supported by the first application client 1003 and the second application client 1004 are not limited.

Fig. 1b is a schematic diagram illustrating a structure of another message forwarding system according to an embodiment of the present application. Message forwarding system 1000 may include: a message interworking device 1001, a first application server 1002, a first application client 1003, a second application client 1004, a second application server 1005. The message interworking apparatus 1001 may communicate with a second application server 1005, where the second application server 1005 is a background server of the second application client 1004, and the second application server 1005 is configured to provide a background support service for the second application client 1004. For example, where the second application client 1004 is a wechat client, the second application server 1005 may be a wechat server (i.e., a wechat backend). A second application client 1004 needs to pass through a second application server 1005 to communicate with the messaging interworking unit 1001.

Based on the above message forwarding system, a message forwarding method provided in an embodiment of the present application is described next, please refer to fig. 2, where the message forwarding method provided in an embodiment of the present application may include the following steps:

201. the first application program client side determines a first message needing to be forwarded, the first message is packaged in a first format, and the first format is a message format which can be identified by the first application program client side.

In this embodiment, the first format is a message format that can be recognized by the first application client, for example, when the first application client is an enterprise wechat client, the first format may be a protobuf encoded format. The first application program client side firstly obtains the message needing to be forwarded, the message needing to be forwarded is called as a first message, and the first message is packaged in a first format which can be identified by the first application program client side. Wherein the first message may be at least one of the following message types: chat notes, text, pictures, video, files, geographical locations, links, applets, etc., the first message may be one or several or all of the above message types, depending on which messages the user desires to forward. The specific type of the first message that the first application client needs to forward is not limited herein.

202. The first application program client sends a conversion request to the first application program server, the conversion request carries a first message, the conversion request is sent to the message intercommunication device by the first application program server, the message intercommunication device converts the first message into a second message and sends the second message to the first application program server, the second message is packaged in a second format, and the second format is a message format which can be identified by the second application program client.

In this embodiment of the application, after the first application client acquires the first message, when the first application client needs to forward the first message, the first application client generates a forwarding request, and the first application client sends the conversion request to the message interworking device through the first application server, where the conversion request carries the first message.

In some embodiments of the present application, before the first application client sends the forwarding request, the first application client further needs to perform a restriction check on the first message to determine whether the forwarding request can be sent, for example, the first application client performs various restriction checks on the first message, for example, whether a file size included in the first message exceeds a restriction (because the file message of the second application client has a size restriction), whether a message type can be forwarded (for example, voice, red packet, and the like, and some message types specific to the first application client), if the conditions are met after the check, the first application client sends the forwarding request, otherwise, the forwarding request is not sent.

211. The message intercommunication device receives a conversion request sent by a first application server and acquires a first message from the conversion request, wherein the first message is acquired from a first application client by the first application server, the first message is packaged in a first format, and the first format is a message format which can be identified by the first application client.

In the embodiment of the application, the message interworking device is dedicated to message format conversion between different application clients, and the message interworking device receives a conversion request sent by a first application client through a first application server.

212. The message intercommunication device converts the first message into a second message, the second message is packaged in a second format, and the second format is a message format which can be identified by the second application program client.

In the embodiment of the present application, the message interworking apparatus has a message format conversion capability, and after the message interworking apparatus acquires the first message, the message interworking means may perform a message format conversion on the first message, refer to the converted first message as a second message, encapsulate the first message in a first format, since the second application client cannot fully recognize the first format, or the second application client cannot recognize the first format as required by the second application client, the message interworking means may complete the format conversion of the first message before the first message is forwarded, for example, the first message is converted into a second message, the second message is packaged in a second format, and the second format is a message format that can be recognized by the second application client, so that the second application client no longer needs to recognize the first message in the first format.

In the embodiment of the application, the message interworking device may acquire the message formats that can be identified by different application clients through interaction with different application servers in advance, so that the message interworking device may complete format conversion for different message types.

In some embodiments of the present application, the step 212 of the message interworking means converting the first message into the second message comprises:

the message intercommunication device analyzes the first message according to the first format to obtain the following parameters: a first user identification, a first timestamp, a first content type, a first message content, a first sender name, a first sender address and a first session identification;

the message intercommunication device converts the first user identifier into a second user identifier, converts the first timestamp into a second timestamp, converts the first content type into a second content type, converts the first message content into second message content, converts the first sending end name into a second sending end name, converts the first sending end address into a second sending end address, and converts the first session identifier into a second session identifier;

and the message intercommunication device encapsulates the second user identifier, the second timestamp, the second content type, the second message content, the second sending end name, the second sending end address and the second session identifier into a second message according to the second format.

The message intercommunication device converts the message format of the first message. For example, the first message may include at least one of the following information: a first subscriber identity, a first timestamp, a first content type, a first message content, a first sender name, a first sender address and a first session identity. Specifically, the first user identifier is a user identifier of an application running on the first application client, the first timestamp is a generation time of the first message, the first content type is a type of message content included in the first message, the first message content is specific message content included in the first message, and may be, for example, a chat record, a text, a picture, a video, a file, a geographic location, a link, an applet, and the like, the first sender name is a name of a user sending side operating the first application client, the first sender address is a sending address corresponding to the first sender name, and the first session identifier is used to identify a session corresponding to the first message.

After determining the specific message fields included in the first message, the message interworking apparatus may perform message format conversion for each message field, for example, convert the first user identifier into the second user identifier, convert the first timestamp into the second timestamp, convert the first content type into the second content type, convert the first message content into the second message content, convert the first sending end name into the second sending end name, convert the first sending end address into the second sending end address, and convert the first session identifier into the second session identifier. The field names respectively indicated by the second user identifier, the second timestamp, the second content type, the second message content, the second sender name, the second sender address, and the second session identifier are not limited herein, and may be determined in combination with a specific scenario.

After the message intercommunication device completes the message format conversion, the message intercommunication device performs format encapsulation by using a second format which can be identified by a second application program client, and encapsulates a second user identifier, a second timestamp, a second content type, a second message content, a second sending end name, a second sending end address and a second session identifier into a second message according to the second format. Because the second message is encapsulated in the second format, the second application client can recognize the second message without performing format conversion.

In some embodiments of the present application, after obtaining the first message from the conversion request in step 211, the method provided in the embodiments of the present application further includes:

the message interworking device determines whether the first message comprises resource content downloaded by the first application program client;

when the first message comprises resource content, the message intercommunication device determines a download address corresponding to the resource content;

the message intercommunication device replaces the resource content in the first message with the download address to obtain the first message comprising the download address.

Specifically, the first message may include Resource content downloaded by the first application client, where the Resource content may be downloaded through a network, and then the first application client may add the Resource content to the first message, and if the first message includes the Resource content downloaded by the first application client, the message interworking apparatus determines a download address corresponding to the Resource content, where the download address is a downloadable path of the Resource content, and for example, the download address may be a Uniform Resource Locator (URL). The message intercommunication device replaces the resource content in the first message with the download address to obtain the first message including the download address, namely the first message does not need to carry the resource content, but replaces the resource content with one download address, so that the size of the first message can be greatly reduced, and the message transmission efficiency is improved. For example, the first message may be a chat record, and for video or file data in the chat record, it is not necessary to actually contain specific content, and only needs to transmit a corresponding download URL, so that a larger file can be transmitted, and thus, the extensibility and security of message transmission are further improved.

Further, in the case that the resource content in the first message is replaced with the download address, step 212 the message interworking means converts the first message into a second message, including:

the message interworking means translates the first message including the download address into a second message.

When the resource content in the first message is replaced by the download address, the first message does not carry the resource content but carries the download address, and the message interworking device can convert the first message including the download address into the second message, for example, the message interworking device can convert the download address in the first message into a message format that can be identified by the second application client, so that the second application client can acquire the corresponding resource content according to the download address.

213. The message intercommunication device sends a second message to the first application server, the second message is sent to the first application client by the first application server, after the first application client jumps to the second application client, the second message is sent to the second application client by the first application client, and the first application client and the second application client run on the same terminal.

In this embodiment, after the message interworking apparatus obtains the second message through message format conversion, the message interworking apparatus may send the second message to the first application client through the first application server, and then the second message is sent to the first application client by the first application server.

In some embodiments of the present application, as shown in fig. 3, the step 213 of the message interworking means sending a second message to the first application server, includes:

2131. the message intercommunication device encrypts the second message by using a preset key to obtain the encrypted second message;

2132. and after the first application program client jumps to the second application program client, the encrypted second message is sent to the second application program client by the first application program client.

After the message intercommunication device obtains the second message through message format conversion, the message intercommunication device can encrypt the second message to improve the safety of message transmission. The message interworking device encrypts the second message by using a preset key to obtain the encrypted second message, and the encryption and decryption algorithm and the corresponding key are not limited in the embodiment of the application. The message intercommunication device sends the encrypted second message to the first application server, and the encrypted second message is sent to the first application client by the first application server. In the embodiment of the application, the encryption operation of the second message is realized by the message intercommunication device, and encryption is not required to be carried out on the side of the first application program client, so that the first application program client does not need to store a secret key, and the configuration of the first application program client is simplified.

In some embodiments of the present application, as shown in fig. 3, after the step 2132 of the message interworking apparatus sending the encrypted second message to the first application server, the method provided by an embodiment of the present application further includes:

214. the message intercommunication device receives a decryption request sent by the second application server and acquires an encrypted second message from the decryption request, wherein the encrypted second message is acquired from the second application client by the second application server;

215. the message intercommunication device decrypts the encrypted second message by using the key to obtain a decrypted second message;

216. and the message intercommunication device sends the decrypted second message to the second application program server, and the decrypted second message is sent to the second application program client by the second application program server.

After the message intercommunication device obtains the second message through message format conversion, the message intercommunication device can encrypt the second message to improve the safety of message transmission. And the message intercommunication device encrypts the second message by using a preset key to obtain the encrypted second message. The message intercommunication device sends the encrypted second message to the first application server, and the encrypted second message is sent to the first application client by the first application server. The first application client receives the encrypted second message, and the first application client sends the encrypted second message to the second application client, so that the security of message transmission is ensured through encrypted transmission of the second message. The second application program client side can request the message intercommunication device to decrypt the second message through the second application program server because the second application program client side receives the encrypted second message, the message intercommunication device can complete decryption of the second message because the message intercommunication device stores the secret key, the message intercommunication device can also send the decrypted second message to the second application program client side through the second application program server, and the second application program client side can directly identify the decrypted second message. In the embodiment of the application, the encryption and decryption operations of the second message are realized by the message intercommunication device, encryption is not required to be performed on one side of the first application client, and decryption is not required to be performed on one side of the second application client, so that the first application client and the first application client do not need to store keys, the configuration of the first application client and the second application client is simplified, and the efficiency of message safe transmission is improved.

In some embodiments of the present application, as shown in fig. 4, after the step 213 of the message interworking apparatus sending the second message to the first application server, the method provided by the embodiments of the present application further includes:

217. the message intercommunication device receives a first forwarding request sent by a second application program server and acquires a second message from the first forwarding request, wherein when the second application program client needs to forward the second message to the first application program client, the first forwarding request is sent to the second application program server by the second application program client;

218. the message interworking means sends a second message to the first application server, the second message being sent by the first application server to the first application client.

After the second application client receives the second message from the first application client, the second application client may further forward the second message. For example, the second application client may perform a cross-client type forwarding operation, and when the second application client needs to forward the second message to the first application client, the first forwarding request is sent to the second application server by the second application client. The message intercommunication device receives a first forwarding request sent by the second application server, and forwards the second message to the first application client through the first application server, so that the first application client can receive the second message forwarded by the second application client, and the cross-client type message forwarding operation is realized.

In some embodiments of the present application, as shown in fig. 5, after the step 213 of the message interworking apparatus sending the second message to the first application server, the method provided by the embodiments of the present application further includes:

219. the message intercommunication device receives a second forwarding request sent by a second application server and acquires a second message from the second forwarding request, wherein when the second application client needs to forward the second message to the first application client and the third application client respectively, the second forwarding request is sent to the second application server by the second application client;

210. the message intercommunication device respectively sends second messages to the first application server and the second application server, wherein the second messages are sent to the first application client by the first application server, the second messages are sent to the third application client by the second application server, and the second application server provides background services for the third application client.

After the second application client receives the second message from the first application client, the second application client may further forward the second message. For example, the second application client may perform a cross-client type forwarding operation and an intra-group forwarding operation of clients of the same type, and when the second application client needs to forward the second message to the first application client and the third application client, the second application client sends the second forwarding request to the second application server. The message intercommunication device receives a second forwarding request sent by the second application server, and forwards the second message to the first application client through the first application server, so that the first application client can receive the second message forwarded by the second application client, and the cross-client type message forwarding operation is realized. And the second message is sent to the third application program client by the second application program server, the second application program server provides background service for the third application program client, and the second application program server provides background service for the second application program client, for example, when the second application program client and the third application program client belong to the same group, the third application program client can receive the second message forwarded by the second application program client, and the in-group forwarding operation of the clients of the same type is realized.

203. And the first application program client receives the second message sent by the first application program server.

In this embodiment, the message interworking apparatus may send the second message to the first application client through the first application server, and the first application client may receive the second message converted by the message interworking apparatus.

204. And after the first application program client side jumps to the second application program client side, the first application program client side sends a second message to the second application program client side, and the first application program client side and the second application program client side run on the same terminal.

In the embodiment of the application, when a user needs to forward a message from a first application client to a second application client, the user can operate the terminal to enable the first application client to jump to the second application client, the first application client sends a second message to the second application client, and the second application client directly receives the second message from the first application client, the second message is packaged in a second format, and the second format is a message format capable of being recognized by the second application client, so that the second application client does not need to recognize the first message in the first format any more, and the second application client can directly analyze the second message, and therefore the efficiency of message forwarding is improved.

In some embodiments of the present application, the step 203 of the first application client receiving the second message sent by the first application server includes: and the first application program client receives the encrypted second message sent by the first application program server.

If the message intercommunication device encrypts the second message and the message intercommunication device sends the encrypted second message to the first application program client, the first application program client receives the encrypted second message, and the security of message transmission is ensured through encrypted transmission of the second message.

Step 204 the first application client sends a second message to the second application client, comprising: and the first application program client sends the encrypted second message to the second application program client.

If the message intercommunication device encrypts the second message and the message intercommunication device sends the encrypted second message to the first application program client, the first application program client receives the encrypted second message, the first application program client sends the encrypted second message to the second application program client, and the security of message transmission is ensured through encrypted transmission of the second message.

221. After the first application program client side jumps to a second application program client side, the second application program client side receives a second message sent by the first application program client side, and the first application program client side and the second application program client side run on the same terminal; and the second message is sent to the first application program client through the first application program server after being converted by the message intercommunication device, and the first message is packaged in a first format which can be identified by the first application program client.

In some embodiments of the present application, when the second application client receives the encrypted second message, as shown in fig. 3, the method provided in this embodiment of the present application further includes:

223. the second application program client sends a decryption request to the second application program server, the decryption request is sent to the message intercommunication device by the second application program server, and the message intercommunication device decrypts the encrypted second message and sends the decrypted second message to the second application program server;

224. and the second application program client receives the decrypted second message sent by the second application program server.

The first application program client side receives the encrypted second message, the first application program client side sends the encrypted second message to the second application program client side, and the safety of message transmission is guaranteed through encryption transmission of the second message. The second application program client side can request the message intercommunication device to decrypt the second message through the second application program server because the second application program client side receives the encrypted second message, the message intercommunication device can complete decryption of the second message because the message intercommunication device stores the secret key, the message intercommunication device can also send the decrypted second message to the second application program client side through the second application program server, and the second application program client side can directly identify the decrypted second message. In the embodiment of the application, the encryption and decryption operations of the second message are realized by the message intercommunication device, encryption is not required to be performed on one side of the first application client, and decryption is not required to be performed on one side of the second application client, so that the first application client and the first application client do not need to store keys, the configuration of the first application client and the second application client is simplified, and the efficiency of message safe transmission is improved.

222. The second application client parses the second message in a second format, the second format being a message format that the second application client is capable of recognizing.

In some embodiments of the present application, as shown in fig. 4, after the second application client parses the second message according to the second format in step 222, the method provided in this embodiment of the present application further includes:

225. when the second application program client needs to forward the second message to the first application program client, the second application program client sends a first forwarding request to the second application program server, the first forwarding request carries the second message, the first forwarding request is sent to the message intercommunication device by the second application program server, and then the second message is sent to the first application program client by the message intercommunication device through the first application program server.

In some embodiments of the present application, as shown in fig. 5, after the second application client parses the second message according to the second format in step 222, the method provided in this embodiment of the present application further includes:

226. when the second application program client needs to respectively forward the second message to the first application program client and the third application program client, the second application program client sends a second forwarding request to the second application program server, the second forwarding request carries the second message, the second forwarding request is sent to the message intercommunication device by the second application program server, and then the second message is sent to the first application program client by the message intercommunication device through the first application program server and is sent to the third application program client by the second application program server.

As can be seen from the above description of the embodiments of the present application, a first application server obtains a first message from a first application client and then sends a conversion request to a message interworking device, the message interworking device obtains the first message from the conversion request, the first message is encapsulated in a first format, the first format is a message format that can be recognized by the first application client, the message interworking device converts the first message into a second message, the second message is encapsulated in a second format, the second format is a message format that can be recognized by a second application client, the message interworking device sends the second message to the first application server, the first application server sends the second message to the first application client, the first application client sends the second message to the second application client after the first application client jumps to the second application client, the first application client and the second application client run on the same terminal. The message intercommunication device in the embodiment of the application has a message format conversion function, so that a first message can be converted into a second message, after a first application client side jumps to a second application client side on the same terminal, the second application client side receives the second message sent by the first application client side, therefore, the second application client side can analyze the second message according to a second format which can be identified by the second application client side, and the second message sent by the first application client side is the message format which can be directly identified by the second application client side, so that the message forwarding efficiency is improved, and the problem of message compatibility when the message is forwarded across the client sides is solved.

In order to better understand and implement the above-described scheme of the embodiments of the present application, the following description specifically illustrates a corresponding application scenario.

Next, an example is given by taking the first application client as an enterprise wechat client, the second application client as a wechat client, the first application server as an enterprise wechat background, the second application server as a wechat background, and the message interworking device as an interworking background imuion.

The embodiment of the application provides a technical scheme of chat conversion logic based on an enterprise wechat and wechat intercommunication channel, which can avoid the problems of message forwarding among clients in aspects of expansibility, safety, size limitation and the like, and can also achieve the purpose of sharing the original chat records from the enterprise wechat to the wechat.

In the embodiment of the application, the IMUnion is used for realizing message intercommunication and heterogeneous account management among a plurality of heterogeneous systems based on one message intercommunication IMUnion background, the IMUnion provides a universal interface and an event center to ensure data consistency, and each heterogeneous system is accessed according to the universal interface, for example, the universal interface provided by the IMUnion can be an interface which can be identified by different application servers to realize communication between different application servers and the IMUnion. In addition, the IMUnion registers events needing attention through the event center at the same time, for example, the registration events are mainly registered for specific sessions, and when the messages in the sessions change, the corresponding events are triggered to be executed.

Specifically, the enterprise wechat client converts the chat record R _ WW into an encrypted chat record R _ WX _ Encoded which can be supported by wechat through an enterprise wechat background- > IMUnion background, and then calls a wechat OpenSDK jump wechat to transmit the R _ WX _ Encoded to the wechat client. The WeChat client decrypts the chat record R _ WX through the WeChat background- > IMUnion background, and then shares the R _ WX with WeChat friends or group conversations in a native chat record mode through the message sending interface of the WeChat client. In the whole process, data transmitted between the enterprise wechat and the wechat through the OpenSDK only has one R _ WX _ Encoded binary data, and is transparent to both the enterprise wechat and the wechat, so that even if a newly-added message type is added subsequently, the interfaces of the OpenSDK are not updated by both the enterprise wechat and the wechat, the R _ WX _ Encoded is also encrypted and decrypted by the IMUnion background, and a secret key cannot exist in a client; in addition, the video or file data in the chat records do not need to really contain specific content, and only the corresponding download Url needs to be transmitted, so that a larger file can be transmitted. Thus, the expansibility and the safety of the whole message forwarding are higher.

Fig. 6 is a schematic diagram of a system architecture of a chat record forwarding scenario of the message forwarding system according to the embodiment of the present application. The message forwarding system comprises the following parts:

the interworking background (i.e., the imuion background) is responsible for logic processing and data storage of a plurality of heterogeneous systems, such as heterogeneous account management, message format conversion, cluster logic, key value pair (KV) storage, event center, and the like, and can implement other functions that need to be converted between heterogeneous systems by extending a logic module, and the imuon background has a central hub capability of message format conversion in the heterogeneous systems. In addition, the IMUnion background is also provided with an IMUnion access layer, and the IMUnion access layer is used for carrying out cross-background communication with the enterprise WeChat access layer and the WeChat access layer.

The enterprise wechat background has functions of KV storage, relation chains, account numbers, group logic, safety logic, notification, messages and the like, and is responsible for interaction logic and data processing between the enterprise wechat background and an enterprise wechat client and an IMUnion background. The enterprise wechat background is also provided with an enterprise wechat access layer.

The enterprise wechat client side is provided with a session interface and used for receiving the chat records after the IMUnion background performs message format conversion from the enterprise wechat background, and then sending the chat records to the wechat client side through the data transmission channel through the wechat SDK, wherein the wechat SDK has the functions of application information management and data processing conversion. Wherein, the data transmission channel can be through openURL: url and uipanel. The enterprise wechat client is responsible for logic processing and UI display such as chat records, wechat OpenSDK call management, session interfaces and the like.

The WeChat background has functions of KV storage, relation chains, account numbers, group logic, safety logic, notification, messages and the like, and is responsible for interaction logic and data processing between the WeChat background and the WeChat client side and the IMUnion. The WeChat background is also provided with a WeChat access layer.

The WeChat client is responsible for logic processing such as chat records, OpenSDK calling processing, session lists, session interfaces and the like and displaying of user graphical interfaces. For example, the wechat client receives the chat records sent by the enterprise wechat client through a data transmission channel by using the apihandle, the apihandle has the functions of data distribution and data conversion, the wechat client has a session list interface and a session interface, and the wechat client can display the chat records on the session interface.

As shown in fig. 7, a schematic view of an implementation flow of chat record conversion and forwarding provided in the embodiment of the present application mainly includes the following processes:

steps 1 to 5 illustrate the flow of chat log conversion.

In step 1 and step 2, the enterprise wechat user WW _ a selects a plurality of message combinations to combine into a chat record R _ WW in any existing chat session, and then clicks 'forward to wechat', and then performs various limit checks on the messages in the R _ WW, such as whether the size of the included file exceeds the limit (because the file message at the wechat side has size limit), whether the message type can be forwarded (voice, red packet, etc., and also some message types specific to the enterprise wechat); and if the conditions are met after the checking, sending a request for converting the R _ WW to an enterprise WeChat background.

In step 3, step 4 and step 5, the enterprise wechat background receives R _ WW, and then transmits the data to the message interworking imuunion background for conversion, and the imuunion converts R _ WW into a message format R _ WX that can be identified by wechat, as shown in fig. 8, which is a schematic diagram of message format conversion provided in the embodiment of the present application and is encrypted to R _ WX _ Encoded, and then the encrypted and converted R _ WX _ Encoded is returned to the enterprise wechat background, and finally returned to WW _ a.

Steps 6 to 15 illustrate the flow of forwarding the chat log.

In the steps 6 to 7, after the enterprise wechat WW _ a obtains the R _ WX _ Encoded data, the data is packaged through an OpenSDK interface provided by the wechat, and then the wechat user WX _ a on the same mobile phone is called up through the OpenSDK interface and the data is transmitted to the wechat; and after receiving the data, the WeChat client side analyzes the data to obtain R _ WX _ Encoded. This process is an interaction between pure clients, and reference may be made to the functionality of the data transmission channel bridging enterprise wechat and wechat as shown in fig. 6.

In steps 7 to 10, the WeChat WX _ A is analyzed to obtain R _ WX _ Encoded, and the R _ WX _ Encoded is decrypted to obtain R _ WX through a link of WeChat background- > intercommunication IMUnion background, and then a latest chat session list box can be called up to show the abstract content of the R _ WX.

In step 11, WX _ a may select a session in the list of the most recent chat sessions, or may create a new chat session, and then forward R _ WX to the corresponding session.

In step 12 to step 13, if the session that WX _ a selects to forward is a wechat user or wechat group, the wechat background may push R _ WX directly to the wechat user or wechat group, and does not go through the im union background.

In steps 14 to 15, if the session that WX _ a selects to forward is an enterprise wechat user or an interworking group (the interworking group includes wechat and enterprise wechat users), the wechat background will send R _ WX to the interworking imuion background, and then the IMUnion will push R _ WX to the enterprise wechat background or wechat background, and finally each background will push R _ WX to its respective client user.

Fig. 8 is a schematic diagram of message format conversion provided in the embodiment of the present application. The IMUnion background can convert the enterprise WeChat chat record (WW _ RecordItem) into the WeChat chat record (WX _ RecordItem) mainly because of the difference between the message types and the content formats of the two parties, for example, the message content of the enterprise WeChat is in a protobuf coded format, and the WeChat is in a json string format. In addition, the message types that can be converted by both parties are necessarily displayed by both parties, such as common texts, pictures, videos, files, geographical positions, links, applets, chat records and the like. Specifically, the WW _ recordtem may include uin, time, content _ type, content (protobuf), sender _ name, sender _ header, and conversion _ id, which are respectively converted into from _ openid, msg _ time, type, content (json string), from _ name, from _ header, and is _ control in the WX _ recordtem.

It should be noted that, forwarding the chat record to the enterprise WeChat by the WeChat may also be implemented according to a similar process, but the direction of IMUnion converting the message format is opposite, and is not described herein again.

Fig. 9a is a schematic view of a chat record generated by an enterprise wechat client according to an embodiment of the present application, and fig. 9b is a schematic view of an effect of a chat record forwarding entry according to an embodiment of the present application, where a user may click a "forward to wechat" forwarding button 902 on a chat window 901 of an enterprise wechat to trigger a message forwarding operation.

Fig. 10 is a schematic diagram illustrating an effect of forwarding a chat log after jumping to a WeChat client according to an embodiment of the present application, and fig. 10 illustrates a forwarding window 903 for forwarding to a WeChat, where a user may select a "send" button.

Fig. 11a is a schematic diagram of an effect of a wechat client side after forwarding a chat record provided in an embodiment of the present application, a chat record 1002 for forwarding an enterprise wechat is illustrated in a chat window 1001 of the wechat, and a user can click on the summary content of the chat record, so as to display the display effect on the chat window 1001 of the wechat shown in fig. 11b, and fig. 11b is a schematic diagram of a chat content of the wechat client side after forwarding a chat record provided in an embodiment of the present application.

Fig. 12a is a schematic diagram of an effect of an enterprise wechat client side after forwarding a chat record provided in the embodiment of the present application, a chat record 1003 forwarded by wechat is illustrated in a chat window 901 of the enterprise wechat, and a user can click the summary content of the chat record, so as to display the display effect on the chat window 1001 of the wechat shown in fig. 12b, and fig. 12b is a schematic diagram of a chat content of the enterprise wechat client side after forwarding a chat record provided in the embodiment of the present application.

Fig. 13a is a schematic diagram illustrating an effect of forwarding a chat record containing a small program at a WeChat client side according to an embodiment of the present application, where the chat record containing the small program is forwarded in a WeChat chat window 1001, and fig. 13b is a schematic diagram illustrating an effect of forwarding a chat record containing a small program at an enterprise WeChat client side according to an embodiment of the present application, where the chat record containing the small program is forwarded in an enterprise WeChat chat window 901.

It should be noted that, the illustration shows the effect of presenting the forwarding entry of the chat record, and the chat record, the name, the identifier, the avatar, and the format and the content of the chat record shown in the illustration are all examples, which are not limited herein, and various information of the chat record may be configured according to the actual application scenario.

It should be noted that, for simplicity of description, the foregoing method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present embodiment is not limited by the described order of acts, as some steps may occur in other orders or concurrently depending on the embodiment. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required for the embodiments of the application.

To facilitate better implementation of the above-described aspects of the embodiments of the present application, the following also provides relevant means for implementing the above-described aspects.

Referring to fig. 14, a message interworking apparatus 1400 provided by an embodiment of the present application may include: a receiving module 1401, a processing module 1402, a sending module 1403, wherein,

a receiving module 1401, configured to receive a conversion request sent by a first application server;

a processing module 1402, configured to obtain a first message from the conversion request, where the first message is obtained by the first application server from a first application client, and the first message is encapsulated in a first format, where the first format is a message format that can be identified by the first application client;

the processing module 1402 is further configured to convert the first message into a second message, where the second message is encapsulated in a second format, and the second format is a message format that can be recognized by a second application client;

a sending module 1403, configured to send the second message to the first application server, where the second message is sent to the first application client by the first application server, and after the first application client jumps to the second application client, the second message is sent to the second application client by the first application client, and the first application client and the second application client operate on the same terminal.

In some embodiments of the present application, the processing module 1402 is further configured to encrypt the second message by using a preset key, so as to obtain an encrypted second message;

a sending module 1403, configured to send the encrypted second message to the first application server, where the encrypted second message is sent to the first application client by the first application server, and after the first application client jumps to the second application client, the encrypted second message is sent to the second application client by the first application client.

In some embodiments of the present application, the receiving module 1401 is further configured to, after the sending module 1403 sends the encrypted second message to the first application server, receive a decryption request sent by a second application server, and obtain the encrypted second message from the decryption request, where the encrypted second message is obtained by the second application server from the second application client;

the processing module 1402 is further configured to decrypt the encrypted second message using the key to obtain a decrypted second message;

a sending module 1403, configured to send the decrypted second message to the second application server, where the decrypted second message is sent to the second application client by the second application server.

In some embodiments of the present application, the processing module 1402 is further configured to parse the first message according to the first format to obtain the following parameters: a first user identification, a first timestamp, a first content type, a first message content, a first sender name, a first sender address and a first session identification; converting the first user identifier into a second user identifier, converting the first timestamp into a second timestamp, converting the first content type into a second content type, converting the first message content into a second message content, converting the first sending end name into a second sending end name, converting the first sending end address into a second sending end address, and converting the first session identifier into a second session identifier; and according to the second format, encapsulating the second user identifier, the second timestamp, the second content type, the second message content, the second sender name, the second sender address and the second session identifier into the second message.

In some embodiments of the present application, the processing module 1402 is further configured to determine, after obtaining the first message from the conversion request, whether the first message includes resource content downloaded by the first application client; when the first message comprises the resource content, determining a download address corresponding to the resource content; and replacing the resource content in the first message with the download address to obtain a first message comprising the download address.

In some embodiments of the present application, the processing module 1402 is further configured to convert the first message including the download address into a second message.

In some embodiments of the present application, the receiving module 1401 is further configured to, after the sending module 1403 sends the second message to the first application server, receive a first forwarding request sent by a second application server, and obtain the second message from the first forwarding request, where when the second application client needs to forward the second message to the first application client, the first forwarding request is sent to the second application server by the second application client;

a sending module 1403, configured to send the second message to the first application server, where the second message is sent to the first application client by the first application server.

In some embodiments of the present application, the receiving module 1401 is further configured to, after the sending module 1403 sends the second message to the first application server, receive a second forwarding request sent by the second application server, and obtain the second message from the second forwarding request, where when the second application client needs to forward the second message to the first application client and a third application client respectively, the second forwarding request is sent to the second application server by the second application client;

a sending module 1403, configured to send the second messages to the first application server and the second application server, respectively, where the second message is sent to the first application client by the first application server, the second message is sent to the third application client by the second application server, and the second application server provides a background service for the third application client.

Referring to fig. 15, in an application client provided in an embodiment of the present application, the application client is specifically a first application client 1500, where the first application client 1500 includes: a processing module 1501, a sending module 1502, a receiving module 1503, wherein,

a processing module 1501, configured to determine a first message to be forwarded, where the first message is encapsulated in a first format, and the first format is a message format that can be identified by the first application client;

a sending module 1502, configured to send a conversion request to a first application server, where the conversion request carries the first message, where the conversion request is sent by the first application server to a message interworking apparatus, the message interworking apparatus converts the first message into a second message, and sends the second message to the first application server, where the second message is encapsulated in a second format, and the second format is a message format that can be identified by a second application client;

a receiving module 1503, configured to receive the second message sent by the first application server;

the sending module 1502 is further configured to send the second message to the second application client after the first application client jumps to the second application client, where the first application client and the second application client operate on the same terminal.

In some embodiments of the present application, the receiving module 1503 is configured to receive the encrypted second message sent by the first application server;

a sending module 1502, configured to send the encrypted second message to the second application client.

Referring to fig. 16, an application client provided in the embodiment of the present application is specifically a second application client 1600, where the second application client 1600 includes: a receiving module 1601, a processing module 1602, a sending module 1603, wherein,

a receiving module 1601, configured to receive a second message sent by a first application client after the first application client jumps to a second application client, where the first application client and the second application client operate on the same terminal; the second message is sent to the first application program client through the first application program server after being converted by the message intercommunication device, the first message is packaged in a first format, and the first format is a message format which can be identified by the first application program client;

a processing module 1602, configured to parse the second message according to the second format, where the second format is a message format that can be recognized by the second application client.

In some embodiments of the present application, the sending module 1603 is configured to, when the second application client receives the encrypted second message, send a decryption request to a second application server, where the decryption request is sent to the message interworking apparatus by the second application server, and the message interworking apparatus decrypts the encrypted second message and sends the decrypted second message to the second application server;

a receiving module 1601, configured to receive the decrypted second message sent by the second application server.

In some embodiments of the present application, the sending module 1603 is configured to, after the processing module 1602 parses the second message according to the second format, send a first forwarding request to a second application server when the second application client needs to forward the second message to the first application client, where the first forwarding request carries the second message, the first forwarding request is sent to the message interworking apparatus by the second application server, and then the second message is sent to the first application client by the message interworking apparatus through the first application server.

In some embodiments of the present application, the sending module 1603 is configured to, after the processing module 1602 parses the second message according to the second format, send a second forwarding request to a second application server when the second application client needs to forward the second message to the first application client and a third application client, respectively, where the second forwarding request carries the second message, the second forwarding request is sent to the message interworking apparatus by the second application server, and then the second message is sent to the first application client by the message interworking apparatus through the first application server and is sent to the third application client by the second application server.

The embodiment of the present application further provides a terminal, which may specifically be the message interworking apparatus, the first application client, and the second application client. As shown in fig. 17, for convenience of explanation, only the portions related to the embodiments of the present application are shown, and details of the specific techniques are not disclosed, please refer to the method portion of the embodiments of the present application. The terminal may be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), a vehicle-mounted computer, etc., taking the terminal as the mobile phone as an example:

fig. 17 is a block diagram illustrating a partial structure of a mobile phone related to a terminal provided in an embodiment of the present application. Referring to fig. 17, the handset includes: radio Frequency (RF) circuitry 1710, memory 1720, input unit 1730, display unit 1740, sensor 1750, audio circuitry 1760, wireless fidelity (WiFi) module 1770, processor 1780, and power supply 1790. Those skilled in the art will appreciate that the handset configuration shown in fig. 17 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The following describes each component of the mobile phone in detail with reference to fig. 17:

the RF circuit 1710 can be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, for processing the received downlink information of the base station in the processor 1780; in addition, the data for designing uplink is transmitted to the base station. In general, the RF circuitry 1710 includes, but is not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuitry 1710 may also communicate with networks and other devices via wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), and the like.

The memory 1720 can be used for storing software programs and modules, and the processor 1780 executes various functional applications and data processing of the mobile phone by operating the software programs and modules stored in the memory 1720. The memory 1720 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, and the like), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 1720 may include high-speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 1730 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone. Specifically, the input unit 1730 may include a touch panel 1731 and other input devices 1732. The touch panel 1731, also referred to as a touch screen, may collect touch operations of a user (e.g., operations of the user on the touch panel 1731 or near the touch panel 1731 by using any suitable object or accessory such as a finger or a stylus), and drive a corresponding connection device according to a preset program. Alternatively, the touch panel 1731 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, and sends the touch point coordinates to the processor 1780, and can receive and execute commands sent from the processor 1780. In addition, the touch panel 1731 may be implemented by various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 1730 may include other input devices 1732 in addition to the touch panel 1731. In particular, other input devices 1732 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 1740 may be used to display information input by or provided to the user and various menus of the mobile phone. The Display unit 1740 may include a Display panel 1741, and optionally, the Display panel 1741 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch panel 1731 may cover the display panel 1741, and when the touch panel 1731 detects a touch operation on or near the touch panel 1731, the touch panel is transmitted to the processor 1780 to determine the type of the touch event, and then the processor 1780 provides a corresponding visual output on the display panel 1741 according to the type of the touch event. Although in fig. 17, the touch panel 1731 and the display panel 1741 are implemented as two separate components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 1731 and the display panel 1741 may be integrated to implement the input and output functions of the mobile phone.

The handset may also include at least one sensor 1750, such as light sensors, motion sensors, and other sensors. Specifically, the light sensor may include an ambient light sensor that adjusts the brightness of the display panel 1741 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 1741 and/or the backlight when the mobile phone is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.

Audio circuitry 1760, speaker 1761, and microphone 1762 may provide an audio interface between the user and the handset. The audio circuit 1760 may transmit the electrical signal converted from the received audio data to the speaker 1761, and the electrical signal is converted into a sound signal by the speaker 1761 and output; on the other hand, the microphone 1762 converts the collected sound signals into electrical signals, which are received by the audio circuit 1760 and converted into audio data, which are then processed by the audio data output processor 1780 and sent to, for example, another cell phone via the RF circuit 1710, or output to the memory 1720 for further processing.

WiFi belongs to short-distance wireless transmission technology, and the mobile phone can help a user to send and receive e-mails, browse webpages, access streaming media and the like through the WiFi module 1770, and provides wireless broadband Internet access for the user. Although fig. 17 shows the WiFi module 1770, it is understood that it does not belong to the essential constitution of the handset, and can be omitted entirely as needed within the scope not changing the essence of the invention.

The processor 1780 is the control center of the handset, connects various parts of the entire handset using various interfaces and lines, and performs various functions of the handset and processes data by running or executing software programs and/or modules stored in the memory 1720 and calling data stored in the memory 1720, thereby monitoring the entire handset. Optionally, processor 1780 may include one or more processing units; preferably, the processor 1780 may integrate an application processor, which primarily handles operating systems, user interfaces, application programs, etc., and a modem processor, which primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 1780.

The handset also includes a power supply 1790 (e.g., a battery) to power the various components, which may preferably be logically connected to the processor 1780 via a power management system, to manage charging, discharging, and power consumption via the power management system.

Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which are not described herein.

In the embodiment of the present application, the processor 1780 included in the terminal further has a function of controlling and executing the above method flows executed by the message interworking apparatus, the first application client, and the second application client.

Fig. 18 is a schematic diagram of a server structure provided in this embodiment, where the server 1800 may be the message interworking device, and the server 1800 may have a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 1822 (e.g., one or more processors) and a memory 1832, and one or more storage media 1830 (e.g., one or more mass storage devices) storing applications 1842 or data 1844. The memory 1832 and the storage medium 1830 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 1830 may include one or more modules (not shown), each of which may include a series of instruction operations on a server. Still further, a central processor 1822 may be provided in communication with the storage medium 1830 to execute a series of instruction operations in the storage medium 1830 on the server 1800.

The Server 1800 may also include one or more power supplies 1826, one or more wired or wireless network interfaces 1850, one or more input-output interfaces 1858, and/or one or more operating systems 1841, such as a Windows Server^TM，Mac OS X^TM，Unix^TM,Linux^TM，FreeBSD^TMAnd so on.

The steps performed by the message interworking transpose in the above embodiments may be based on the server architecture shown in fig. 18.

It should be noted that the above-described embodiments of the apparatus are merely schematic, where the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. In addition, in the drawings of the device embodiments provided in the embodiments of the present application, a connection relationship between modules indicates that there is a communication connection therebetween, and may be specifically implemented as one or more communication buses or signal lines. One of ordinary skill in the art can understand and implement it without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that the embodiments of the present application can be implemented by software plus necessary general hardware, and certainly can also be implemented by special hardware including application specific integrated circuits, special CPUs, special memories, special components and the like. Generally, functions performed by computer programs can be easily implemented by corresponding hardware, and specific hardware structures for implementing the same functions may be various, such as analog circuits, digital circuits, or dedicated circuits. However, for the embodiments of the present application, the implementation of the software program is more preferable. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied in the form of a software product, where the computer software product is stored in a readable storage medium, such as a floppy disk, a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random-Access Memory (RAM), a magnetic disk or an optical disk of a computer, and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) to execute the methods described in the embodiments of the present application.

In summary, the above embodiments are only used for illustrating the technical solutions of the embodiments of the present application, and not for limiting the same; although the embodiments of the present application have been described in detail with reference to the above embodiments, it should be understood by those skilled in the art that: the technical solutions described in the above embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A message forwarding method, comprising:

2. The method of claim 1, wherein the message interworking means sending the second message to the first application server comprises:

the message intercommunication device encrypts the second message by using a preset secret key to obtain an encrypted second message;

and the message intercommunication device sends the encrypted second message to the first application server, the encrypted second message is sent to the first application client by the first application server, and the encrypted second message is sent to the second application client by the first application client after the first application client jumps to the second application client.

3. The method of claim 2, wherein after the message interworking apparatus sends the encrypted second message to the first application server, the method further comprises:

the message intercommunication device receives a decryption request sent by a second application server and acquires the encrypted second message from the decryption request, wherein the encrypted second message is acquired from the second application client by the second application server;

the message intercommunication device decrypts the encrypted second message by using the key to obtain a decrypted second message;

and the message intercommunication device sends the decrypted second message to the second application program server, and the decrypted second message is sent to the second application program client by the second application program server.

4. The method of any of claims 1 to 3, wherein the message interworking apparatus converts the first message into a second message, comprising:

the message intercommunication device converts the first user identifier into a second user identifier, converts the first timestamp into a second timestamp, converts the first content type into a second content type, converts the first message content into a second message content, converts the first sending end name into a second sending end name, converts the first sending end address into a second sending end address, and converts the first session identifier into a second session identifier;

and the message interworking apparatus encapsulates the second user identifier, the second timestamp, the second content type, the second message content, the second sender name, the second sender address, and the second session identifier as the second message according to the second format.

5. The method according to any one of claims 1 to 3, wherein after acquiring the first message from the conversion request, the method further comprises:

when the first message comprises the resource content, the message intercommunication device determines a download address corresponding to the resource content;

and the message intercommunication device replaces the resource content in the first message with the download address to obtain the first message comprising the download address.

6. The method of any of claims 1-3, wherein after the message interworking apparatus sends the second message to the first application server, the method further comprises:

the message intercommunication device receives a first forwarding request sent by a second application server and acquires a second message from the first forwarding request, wherein when the second application client needs to forward the second message to the first application client, the first forwarding request is sent to the second application server by the second application client;

and the message intercommunication device sends the second message to the first application server, and the second message is sent to the first application client by the first application server.

7. The method of any of claims 1-3, wherein after the message interworking apparatus sends the second message to the first application server, the method further comprises:

the message intercommunication device receives a second forwarding request sent by the second application server and acquires the second message from the second forwarding request, wherein when the second application client needs to forward the second message to the first application client and a third application client respectively, the second forwarding request is sent to the second application server by the second application client;

the message interworking device sends the second message to the first application server and the second application server respectively, wherein the second message is sent to the first application client by the first application server, the second message is sent to the third application client by the second application server, and the second application server provides background service for the third application client.

8. A message forwarding method, comprising:

9. A message forwarding method, comprising:

after a first application program client side jumps to a second application program client side, the second application program client side receives a second message sent by the first application program client side, and the first application program client side and the second application program client side run on the same terminal; the second message is sent to the first application program client through a first application program server after being converted by a message intercommunication device, the first message is acquired from the first application program client by the first application program server, the first message is packaged in a first format, and the first format is a message format which can be identified by the first application program client;

and the second application program client analyzes the second message according to a second format, wherein the second format is a message format which can be identified by the second application program client.

10. The method of claim 9, wherein when the second application client receives the encrypted second message, the method further comprises:

the second application program client sends a decryption request to a second application program server, the decryption request is sent to the message intercommunication device by the second application program server, and the message intercommunication device decrypts the encrypted second message and sends the decrypted second message to the second application program server;

and the second application program client receives the decrypted second message sent by the second application program server.

11. The method of claim 9 or 10, wherein after the second application client parses the second message in the second format, the method further comprises:

when the second application client needs to forward the second message to the first application client, the second application client sends a first forwarding request to a second application server, the first forwarding request carries the second message, the first forwarding request is sent to the message intercommunication device by the second application server, and then the second message is sent to the first application client by the message intercommunication device through the first application server.

12. A message interworking apparatus, comprising:

13. An application client, specifically a first application client, the first application client comprising:

14. An application client, specifically a second application client, the second application client comprising:

the receiving module is used for receiving a second message sent by a first application program client after the first application program client jumps to a second application program client, and the first application program client and the second application program client run on the same terminal; the second message is sent to the first application program client through a first application program server after being converted by a message intercommunication device, the first message is acquired from the first application program client by the first application program server, the first message is packaged in a first format, and the first format is a message format which can be identified by the first application program client;

and the processing module is used for analyzing the second message according to a second format, wherein the second format is a message format which can be identified by the second application program client.

15. A computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 7, or 8, or 9 to 11.