CN111447133B

CN111447133B - Message transmission method and device, storage medium and electronic device

Info

Publication number: CN111447133B
Application number: CN201910040660.5A
Authority: CN
Inventors: 王佳; 李斌; 刘俊; 王青
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-01-16
Filing date: 2019-01-16
Publication date: 2022-07-29
Anticipated expiration: 2039-01-16
Also published as: CN111447133A

Abstract

The invention discloses a message transmission method and device, a storage medium and an electronic device. Wherein, the method comprises the following steps: detecting a first touch operation executed on a target button in a display page of a target application program, wherein the target application program runs in a first client of a first application, and an incidence relation exists between a first account logged in the first client and a second account logged in the target application program; and responding to the first touch operation, jumping to a display interface of the first client, and displaying a target session between the first account and a third account on the first client, wherein the third account is an account corresponding to the first identifier in the first application, the first identifier is an identifier in the second application, which is transmitted to the first client by the target application program in response to the first touch operation, and the target session is used for carrying out message transmission between the first account and a fourth account corresponding to the first identifier in the second application.

Description

Message transmission method and device, storage medium and electronic device

Technical Field

The present invention relates to the field of computers, and in particular, to a message transmission method and apparatus, a storage medium, and an electronic apparatus.

Background

Today, some instant messaging applications provide a third party applet invocation port through which a user can access the applet in the instant messaging application. The small program can have a simple customer service function, and message transmission between a user and a customer service person is realized.

However, the above message transmission method is provided by a Web method, and it is difficult for a third-party enterprise to obtain the message transmission contents between the user and the customer service staff. That is, the message transmission method in the related art has a problem that the acquisition of the message transmission content is difficult.

Disclosure of Invention

The embodiment of the invention provides a message transmission method and device, a storage medium and an electronic device, which are used for at least solving the technical problem that the message transmission content is difficult to obtain in a message transmission mode provided by the related technology.

According to an aspect of the embodiments of the present invention, there is provided a message transmission method, including: detecting a first touch operation executed on a target button in a display page of a target application program, wherein the target application program runs in a first client of a first application, and an incidence relation exists between a first account logged in the first client and a second account logged in the target application program; and responding to the first touch operation, jumping to a display interface of the first client, and displaying a target session between the first account and a third account on the first client, wherein the third account is an account corresponding to the first identifier in the first application, the first identifier is an identifier in the second application, which is transmitted to the first client by the target application program in response to the first touch operation, and the target session is used for carrying out message transmission between the first account and a fourth account corresponding to the first identifier in the second application.

According to another aspect of the embodiments of the present invention, there is provided a message transmission method, including: detecting a first touch operation executed on a target button in a display page of a target application program, wherein the target application program runs in a first client of a first application, and an incidence relation exists between a first account for logging in the first client and a second account for logging in the target application program; and responding to the first touch operation, jumping to a display interface of the first client, and displaying a target session between the first account and a third account on the first client, wherein the third account is an account corresponding to the first identifier in the first application, the first identifier is an identifier in the second application, which is transmitted to the first client by the target application program in response to the first touch operation, and the target session is used for carrying out message transmission between the first account and a fourth account corresponding to the first identifier in the second application.

According to another aspect of the embodiments of the present invention, there is also provided a message transmission apparatus, including: the system comprises a detection unit, a display unit and a display unit, wherein the detection unit is used for detecting a first touch operation executed on a target button in a display page of a target application program, the target application program runs in a first client of a first application, and an association relation exists between a first account for logging in the first client and a second account for logging in the target application program; the display unit is used for responding to the first touch operation, jumping to a display interface of the first client, and displaying a target session between a first account and a third account on the first client, wherein the third account is an account corresponding to the first identifier in the first application, the first identifier is an identifier in the second application, which is transmitted to the first client by the target application program in response to the first touch operation, and the target session is used for carrying out message transmission between the first account and a fourth account corresponding to the first identifier in the second application.

According to another aspect of the embodiments of the present invention, there is also provided a message transmission apparatus, including: the receiving unit is used for receiving a target message sent by a first client through a second client, wherein the first client is a client for logging in a first account in a first application, the second client is a client for logging in a fourth account in the second application, the target message is a message sent by a first session created by using a target identifier acquired from a target application program through the first client, and the fourth account is one of one or more accounts corresponding to the target identifier in the second application; and the display unit is used for displaying the target message in a second session corresponding to the first account on the second client.

According to a further aspect of the embodiments of the present invention, there is also provided a storage medium having a computer program stored therein, wherein the computer program is configured to perform the above method when executed.

According to another aspect of the embodiments of the present invention, there is also provided an electronic apparatus, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the method by the computer program.

In the embodiment of the invention, a first touch operation executed on a target button in a display page of a target application program is detected, wherein the target application program runs in a first client of a first application, and an association relationship is formed between a first account for logging in the first client and a second account for logging in the target application program; responding to a first touch operation, jumping to a display interface of a first client, and displaying a target session between a first account and a third account on the first client, wherein the third account is an account corresponding to a first identifier in a first application, the first identifier is an identifier in a second application transmitted to the first client by a target application program in response to the first touch operation, the target session is used for carrying out message transmission between the first account and a fourth account corresponding to the first identifier in the second application, and after a target button in the display interface of the target application program is detected to be touched, the client function is provided for a user by respectively establishing sessions in the first client of the first application and the second client of the second application, and compared with a mode of providing a customer service function through a Web mode, the method can conveniently acquire message transmission content, and improves the convenience of acquiring the message transmission content, the technical problem that the message transmission content is difficult to obtain in the message transmission mode provided by the related technology is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

fig. 1 is a schematic diagram of an application environment of a message transmission method according to an embodiment of the present invention;

fig. 2 is a flow chart illustrating an alternative message transmission method according to an embodiment of the present invention;

FIG. 3 is a diagram of an alternative message transmission method according to an embodiment of the present invention;

FIG. 4 is a flow chart illustrating an alternative message transmission method according to an embodiment of the present invention;

FIG. 5 is a flow chart illustrating an alternative message transmission method according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of an alternative messaging architecture according to an embodiment of the present invention;

FIG. 7 is a flow chart illustrating an alternative message transmission method according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of an alternative message transmission method according to an embodiment of the present invention;

FIG. 9 is a diagram of yet another alternative message transmission method according to an embodiment of the present invention;

FIG. 10 is a block diagram of an alternative message transmission apparatus according to an embodiment of the present invention;

FIG. 11 is a schematic structural diagram of an alternative message transmission apparatus according to an embodiment of the present invention; and

fig. 12 is a schematic structural diagram of an alternative electronic device according to an embodiment of the invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The small program: the target application provides a new open capability, so that a third party can develop own application, and the application can be conveniently acquired and spread in a client of the target application, and meanwhile, the application has excellent use experience.

According to one aspect of the embodiment of the invention, a message transmission method is provided. Alternatively, the above message transmission method may be applied, but not limited, to the application environment as shown in fig. 1. As shown in fig. 1, a first terminal 102 may be connected to a background server 104 of a target application program and a first server 106 of a first application program through a network. The first terminal 102 (user terminal) runs a first client logged in by a first application using a first account, and runs a target application (which may be an applet) on the first client. The first account and the second account of the login target application program have an association relation.

After detecting a first touch operation performed on a target button in a display page of a target application program, the first terminal 102, in response to the detected first touch operation, jumps to a display interface of a first client, and displays a target session between a first account and a third account on the first client, where the third account is an account in the first application corresponding to a first identifier, the first identifier is an identifier in a second application transmitted by the target application program to the first client in response to the first touch operation, and the target session is used for performing message transmission between the first account and a fourth account in the second application corresponding to the first identifier. The fourth account may be one of one or more accounts corresponding to the first identifier in the second application.

For the displayed target session, the first terminal 102 may obtain a first message to be transmitted of the first account in the target session, and transmit the first message to the first server 106 of the first application through the network. The first server 106 sends the first message to a second server 108 of the second application over the network, and the second server 108 sends the first message to a second client of the second application. The second client runs on the second terminal 110, and the second client is logged in by the fourth account. After receiving the first message, the second terminal 110 displays the first message in a second session corresponding to the first account on the second client.

Optionally, in this embodiment, the first terminal and the second terminal may include, but are not limited to, at least one of the following: mobile phones, tablet computers, desktop computers, and the like. The network may include, but is not limited to, a wired network and a wireless network, wherein the wired network may include, but is not limited to: a wide area network, metropolitan area network, or local area network, the wireless network comprising: bluetooth, WIFI (Wireless Fidelity), and other networks that enable Wireless communication. The background server, the first server and the second server may include, but are not limited to, at least one of: PC (Personal Computer) and other devices for services. The above is only an example, and the present embodiment is not limited to this.

Optionally, in this embodiment, as an optional implementation manner, as shown in fig. 2, the message transmission method may include:

s202, detecting a first touch operation executed on a target button in a display page of a target application program, wherein the target application program runs in a first client of a first application, and an association relation exists between a first account of a first client and a second account of the target application program;

and S204, responding to the first touch operation, jumping to a display interface of the first client, and displaying a target session between the first account and a third account on the first client, wherein the third account is an account corresponding to the first identifier in the first application, the first identifier is an identifier in the second application, which is transmitted to the first client by the target application program in response to the first touch operation, and the target session is used for message transmission between the first account and a fourth account corresponding to the first identifier in the second application.

Alternatively, the message transmission method may be applied to a terminal device (e.g., in the first terminal 102) operating with the first client. The message transmission method can be applied to the message transmission process between the client and the customer service staff, but is not limited to the message transmission process.

For example, taking message transmission between a client and a customer service staff as an example, a first client is operated on a first terminal, and an account for logging in the first client is a first account. The first client runs a target application program, the account number of the target application program is a second account number, and the first account number and the second account number have an association relation.

The customer clicks the "contact customer service" button in the display page of the target application. After detecting the click operation, the target application program transmits a customer service Identifier (Identifier, abbreviated as ID) to the first client. Responding to the detected first touch operation, the first terminal jumps to a display interface of the first client and displays a target session between a first account and a third account on the first client, wherein the third account is an account corresponding to the first identifier in the first application, the first identifier is an identifier in a second application transmitted to the first client by a target application program in response to the first touch operation, and the target session is used for message transmission between the first account and a fourth account corresponding to the first identifier in the second application.

The message transmission method in the present embodiment is explained below with reference to fig. 2.

In step S202, a first touch operation performed on a target button in a display page of a target application program is detected, where the target application program is run in a first client of a first application, and an association relationship exists between a first account logged in the first client and a second account logged in the target application program.

The first application and the second application may be applications with an instant messaging function, and may include but are not limited to: the system comprises an instant messaging application, an application provided by a third-party payment platform, an application corresponding to a recommendation engine, an online shopping application and the like.

The target application may be an application developed by a third party. The third party may be a third party enterprise (or other organization, etc. that may provide interactive services for consultation, complaint, etc.). A third party may develop a target application (e.g., applet) running on a first client of a first application and maintain the operation of the target application.

Optionally, after logging in the first client using a first account (e.g., a user ID), the user may perform a target operation on the first client to enter the target application, and log in the target application using a second account (e.g., a client ID, an OpenId assigned by the first application, which may be an identifier assigned by the first application for the target application to the first account), where the first account and the second account have an association relationship.

For the first terminal, after detecting a target operation executed on a first client logged in by using a first account, responding to the detected target operation, running a target application program on the first client, and jumping to a display page (e.g. a main page) of the target application program.

The target operation may be one of: the method comprises the steps of performing searching operation on a target application program in a searching interface of a first client, and performing touch operation on the target application program in a searched searching result; and the touch operation is performed on the target application program in the latest application program (the application program which can run in the first client) called and displayed on the first client in response to the sliding operation.

For example, as shown in fig. 3, the first application is a first instant messaging application, and in the display interface of the first client, the most recently used applet is called by performing a slide-down operation, and the display page of the target application program is entered by clicking the target application program (e.g., applet 2).

There may be multiple display pages in the target application, e.g., a main page, various levels of sub-pages. The target button may be set in a target position of one or more displayed pages of the target application. The target button may provide a portal (which may be identified by a particular button, e.g., "contact customer service") to contact customer service (i.e., customer service person, customer service employee) so that the user may contact the customer service person by clicking on the target button.

Optionally, the backend server of the target application may store, in the backend server of the target application, the staff information of all or part of the customer service staff corresponding to the target application, where the staff information may include, but is not limited to: a first identification (e.g., customer service ID).

The first identifier is an identifier in the second application, and the first identifier may be a virtual account in the second application, and the first identifier may not be an account of a client used for logging in the second application, but may correspond to one or more accounts of clients used for logging in the second application. Each application running on the first client may correspond to a program ID, which may be used to distinguish between different applications. The program ID may be assigned by the first application, by the second application, or by other network devices. The specific allocation manner is not limited in this embodiment.

Optionally, after entering the target application, the target application may obtain the first identifier from a backend server (third party backend) of the target application. For the first terminal, the first terminal acquires the first identifier from a background server of the target application program through the target application program.

The timing of acquiring the first identifier may include, but is not limited to, one of: detecting entry into a target application; detecting that a current display page of a target application program is a target page (for example, a commodity display page or other pages which may need to be communicated with customer service personnel); and detecting touch operation executed on a target button in a currently displayed page of the target application program.

Alternatively, the target application may obtain the first identifier from the backend server in a request-response manner. The target application program sends a request message for requesting to distribute the target identification to the background server, and receives the first identification (the first identification is the distributed target identification) sent by the background server in response to the request message. The request message may carry the second account.

For example, the target application sends a request message for requesting to allocate a customer service to the background server, where the request message carries a customer ID (second account number) to allocate a customer service ID (first identifier) serving the customer ID in advance for the customer ID.

The first terminal detects a first touch operation executed on a target button in a display page of a target application program. The first touch operation may be detected by a touch screen of the first terminal. The first touch operation may include, but is not limited to, at least one of: click (single click, double click), long press, drag, slide.

In step S204, in response to the first touch operation, jump to a display interface of the first client, and display a target session between the first account and a third account on the first client, where the third account is an account in the first application corresponding to the first identifier, the first identifier is an identifier in the second application, which is transferred to the first client by the target application program in response to the first touch operation, and the target session is used for performing message transmission between the first account and a fourth account in the second application corresponding to the first identifier.

After detecting the first touch operation, the target application may transfer the first identifier to the first client. For example, the target application program transfers the first identifier to the first client by calling a target interface provided by the target application program, and the first client executes subsequent processing.

And the target application program sends a target instruction to the first client, wherein the target instruction carries the first identifier. The target instruction may also carry at least one of the following: the display page of the target application program, the first account number, the second account number and the program ID of the target application program.

For example, the applet sends a contact customer service instruction to the first client, and the contact customer service instruction carries the current page information, the customer service ID, the user ID and the customer ID of the applet.

The first terminal may create a target session between the first account and the third account on the first client before displaying the target session between the first account and the third account on the first client. The operation of jumping to the display interface of the first client may be performed before, after, or during the creation of the target session, and the specific jump timing may be set as needed, which is not specifically limited herein.

Some applications create sessions in this application that require the use of accounts in this application (both parties to the session are accounts in this application). In order to create a session in the first application when the first application belongs to such an application, after acquiring the first identifier, the first client may send, to the first server, a third request message for acquiring an account in the first application corresponding to the first identifier, where the third request message may carry the program ID and the first identifier.

The first server may send the third account allocated by the first server for the program ID and the first identifier to the first client through a response message after receiving the third request message.

The first server may store a mapping relationship between the allocated third account and the program ID and the first identifier, so that after receiving the request message carrying the program ID and the first identifier, the third account is obtained by matching the allocated account using the program ID and the first identifier.

Before sending the third account to the first client through the response message, the first server may match the allocated account with the program ID and the first identifier, and if an account corresponding to the program ID and the first identifier is matched, the matched account is the third account. And under the condition that the account corresponding to the program ID and the first identifier is not matched, the first server allocates a new account for the program ID and the first identifier, and the newly allocated account is the third account. Optionally, the third account may be an OpenIM ID in the first application. After acquiring the third account, the first terminal may create a target session using the first account and the third account.

Optionally, before displaying the target session between the first account and the third account on the first client, the description information of the first identifier may be acquired by the first client; and creating a target session between the first account and the third account on the first client by using the description information, wherein the description information is used for describing the third account in the target session.

Before the target session is created, in order to facilitate the user to know information of the other party performing the message session, the description information of the first identifier may be acquired by the first client, and when the target session is created, the acquired description information is used to describe the third account. The description information may be acquired by the first terminal from a second server of the second application via the first server through the first client.

Optionally, after acquiring the first identifier, the first client may send a first request message for acquiring the description information to the first server, where the first request message may carry the first identifier and a program identifier (program ID) for identifying the target application program. The first request message may also carry account information of the first account. The program identifier and the first identifier can be used together for distinguishing identifiers in different application programs, identifier confusion is avoided, and the program identifier and the first identifier can be verified.

As an optional implementation manner, the first server may store the acquired description information. After receiving the first request message, the first server may use the program identifier and the first identifier to search the stored description information, and determine whether the description information matching the program identifier and the first identifier is stored; and under the condition that the matched description information is found, returning the found description information to the first client, under the condition that the matched description information is not found, transmitting the first request message to a second server of the second application, and determining the description information by the second server according to the program identifier and the first identifier.

In order to reduce the interaction between the first device and the first server, the description information and the third account may be obtained through the same request message: after receiving the first identifier, the first terminal sends a request message to the first server through the first client, where the request message is used to obtain the third account and the description information of the first account, and the request message may carry the first account, the first identifier, and the program identifier. If the first server has already allocated the account for the first identifier, the first server may store the description information corresponding to the first identifier. The first server may send the third account to the first client along with the description information in response to the request message.

As an optional implementation manner, the first server does not store the acquired description information. After receiving the first request message, the first server may transmit the first request message to a second server of the second application, the second server determining the description information from the program identification and the first identification. By the method, timeliness of the acquired description information can be guaranteed.

In order to ensure the safety of message transmission, before transmitting the first request message to the second server, the first server may generate an encrypted check ticket using one or more of the first account, the second account, the first identifier, and the program identifier, where the check ticket may be used for the first server to check the message transmitted by the second server and carrying the check ticket, so as to verify the validity of the message.

The encrypted information in the verification ticket (the identity verification ticket of the first application) may be various, and may include but is not limited to at least one of the following: the method comprises the steps of encrypting a first identifier and a program identifier by using a first encryption key, encrypting a first account number by using the first encryption key, encrypting a second account number by using the first encryption key, and encrypting effective time information by using a second encryption key.

The valid time information is used for identifying the valid time of the check ticket, and when the message is transmitted subsequently, whether the transmitted message is within the valid time can be determined through the valid time information, and only the message within the valid time is transmitted.

After the verification ticket is generated, the first server sends a second request message to the second server to request the description information corresponding to the first identifier in the target application program from the second server, and the second request message may carry the generated verification ticket.

The second server receives the second request message sent by the first server. The second server may store a first decryption key corresponding to the first encryption key, and may decrypt the verification ticket using the first decryption key to obtain the program identifier and the first identifier. After obtaining the program identifier and the first identifier, the second server may perform an authentication operation to verify whether the program identifier and the first identifier have a binding relationship, and whether the first identifier has a right to perform message transmission with the first account (or the second account). And in the case of passing the verification, the second server sends the description information to the first client through the first server.

The verification pass means: the program identifier and the first identifier have a binding relationship, and the first identifier has the authority of message transmission with the first account (or the second account).

Before, after or during the sending of the description information to the first client through the first server, the second server may store the check ticket in the second request message for use in a subsequent message transmission process.

The target session may be created in response to an indication of the first server, and the indication information may be sent to the first client along with the description information. The target session may also be created according to predetermined configuration information. The predetermined configuration information indicates that the first client performs an operation of creating the target session after receiving the description information.

The two parties of the target session are a first account and a third account, and the third account is described in the target session by using the description information. For example, avatar information, nickname information, job information, business information, and the like corresponding to the third account may be obtained from the description information.

After the creation of the target session is completed, the created target session may be displayed on the first client.

Optionally, after the target session is displayed on the first client, prompt information may be displayed at a target location of the target session, where the prompt information is used to prompt link information corresponding to the display page; detecting a second touch operation executed on the prompt message; and responding to the second touch operation, and transmitting the link information to a second client logged in by a fourth account in the second application through the target session.

After the target session is displayed on the first client, prompt information may be displayed in the target session to prompt link information corresponding to the displayed page of the target application.

Alternatively, the prompt information may be displayed in the form of a floating window at the target position of the target session, and display parameters of the window (floating window) displaying the prompt information may be defined as needed. The display parameters may include, but are not limited to, at least one of: the position of the window, whether the window is in three-dimensional display or planar display, the shape of the window, the color of the window and whether the window is in dynamic display or not. The display parameters may be set as needed, which is not limited in this embodiment.

For example, the display position of the window may be above the message input box of the target conversation, above the trigger button for triggering the sending of the conversation message, or at the center of the target conversation.

After the target session is displayed on the first client, the first client may perform sending and receiving of messages through the target session. In order to ensure the accuracy and security of the transmission of the session message (e.g., link information, text information, pictures, motion pictures, videos, etc.), the session message may be transmitted together with various information by means of a session request when the session message is transmitted.

Optionally, after the target session is displayed on the first client, a first message (session message) to be transmitted of the first account may be acquired in the target session; after the first message is acquired, the first message is transmitted to the first server so as to instruct the first server to transmit the first message to a second server of the second application, and the second server transmits the first message to a second client logged in by a fourth account in the second application.

After obtaining the first message, the first client may send the first message to the first server. The first message may be sent with a variety of information, which may include, but is not limited to, at least one of: a first account number and a third account number. The first message and the various information may be carried simultaneously in the first session request. The format of the first session request may be determined according to a format specified by an interaction protocol employed between the first client and the first server.

The receiver of the first message is a third account, which is not an account of the client capable of logging in the first application, and the third account can be converted in multiple ways to transmit the first message in the first application and the second application.

As an optional implementation manner, after receiving the first session request, the first server may extract the third account from the first session request, determine the program identifier (identifier of the target application program) and the first identifier corresponding to the third account according to the stored correspondence between the third account and the program identifier and the first identifier, and send the first message, the first account, the program identifier, and the first identifier to the second server through the second session request. The second server may obtain the first message, the first account, the program identifier, and the first identifier.

As another optional implementation manner, after receiving the first session request, the first server sends a second session request to the second server, where the second session request carries the first account and the third account. The second server may extract the third account from the second session request, and determine the program identifier and the first identifier corresponding to the third account according to the stored correspondence between the third account and the program identifier and the first identifier, so as to obtain the first message, the first account, the program identifier, and the first identifier. The third account stored in the second server may be acquired by: the first request message is carried by the first request message sent to the first server, and the second request message is carried by the other messages sent to the first server except the first request message.

The format of the second session request may be determined according to a format specified by an interaction protocol (e.g., OpenIM protocol) employed between the first server and the second server.

After acquiring the first message, the first account, the program identifier, and the first identifier, the second server may perform a verification operation, for example, to verify a binding relationship between the program identifier and the first identifier, and a permission of the first identifier. And forwarding the first message to the second client according to the target rule under the condition that the verification is passed.

The target rule (e.g., the agent allocation rule) defines a correspondence between the first identifier and the account in the second application. When the first identifier and the account in the second application are in a one-to-one correspondence relationship, forwarding the first message to a client (a second client) logged in by using an account (a fourth account) corresponding to the first identifier, and when the account in the first identifier and the account in the second application are in a one-to-many correspondence relationship (the first identifier corresponds to accounts in a plurality of second applications), forwarding the first message to a client (a second client) logged in by using an account (a fourth account) corresponding to the first identifier at present.

And under the condition that the first identifier and the account in the second application are in one-to-many correspondence, the target rule defines the account of the second application corresponding to the first identifier under different scenes. The above-mentioned scene may be a temporal scene. The target rule defines accounts in the second application that correspond to the first identifier for different time periods.

For example, there are multiple accounts of the second application corresponding to the first identifier, and only one of the accounts is bound within one time. And after the verification is passed, according to the agent distribution rule, sending the first message to a second client logged in by an account in a second application currently bound with the first identifier.

The first message forwarded to the second client may be carried in the third session request, and the third session request may also carry a fourth account. The format of the third session request may be determined according to a format specified by an interaction protocol employed between the second server and the second client.

Optionally, after displaying the target session on the first client, the first client may receive a second message (session message) sent by the first server, wherein the second message is configured to be sent to the first server via the second server by a second client logged in by a fourth account in the second application; the second message is displayed in the target conversation.

The second message may be sent by the second client to the first server via the second server. When the second client sends the second message to the second server, the second message may be carried in a fourth session request, and the fourth session request may also carry various information, which may include but is not limited to at least one of the following: a fourth account and a fifth account, wherein the fifth account is an account corresponding to the first account in the second application. The format of the fourth session request may be determined according to a format specified by an interaction protocol employed between the second server and the second client.

The sender of the second message is a fourth account, the receiver is a fifth account (corresponding to the first account), the fifth account is not an account which can log in the client of the second application, and the fifth account can be converted so as to transmit the second message in the first application and the second application.

After receiving the fourth session request, the second server may extract a fifth account from the fourth session request, and determine a first account corresponding to the fifth account according to a stored correspondence between the fifth account and the first account; and extracting a fourth account from the fourth session request, and determining a program and a first identifier corresponding to the fourth account according to the corresponding relationship between the fourth account and the program identifier as well as the first identifier.

As an optional implementation manner, after determining the first account, the program identifier, and the first identifier, the second server sends the second message, the first account, the program identifier, and the first identifier to the first server through a fifth session request. After receiving the fifth session request, the first server extracts the program identifier and the first identifier from the fifth session request, determines a third account corresponding to the program identifier and the first identifier according to the stored correspondence between the program identifier and the first identifier and the third account, and sends the second message, the first account and the third account to the first client through a sixth session request so as to display the second message in the target session on the first client.

As another optional implementation, after determining the first account, the program identifier, and the first identifier, the second server determines, according to the stored program identifier and the correspondence between the first identifier and the third account, a third account corresponding to the program identifier and the first identifier; and sending the second message, the first account and the third account to the first server through a fifth session request. After receiving the fifth session request, the first server sends the second message, the first account and the third account carried in the fifth session request to the first client through the sixth session request, so as to display the second message in the target session on the first client.

The format of the fifth session request may be determined according to a format specified by an interaction protocol (e.g., OpenIM protocol) employed between the first server and the second server, and the format of the sixth session request may be determined according to a format specified by an interaction protocol employed between the first server and the first client.

It should be noted that, the above is only an optional manner in which the first client receives the session message from the second client, and both the manner in which the second client sends the session message to the first client via the second server of the second application and the first client of the first application can be used to implement the message transmission method of this example.

When the second server sends the second message to the first server, the second server may send the stored verification ticket to the first server together with the second message. After receiving the second message and the check ticket, the first server may unwrap the clear text of the check ticket, verify the validity of the ticket (which may include, but is not limited to, expiration time, identity, etc.) and synchronize the second message to the first client if the verification is passed.

Optionally, the first server receives a target message sent by the second server, where the target message carries a target session message (e.g., a second message) and a check ticket, and the target session message is set to be sent to the first server by a second client logged in by a fourth account in the second application via the second server of the second application; decrypting the first encrypted information in the check bill by using the first decryption key to obtain a first account number, a program identifier and a first identifier; decrypting the second encrypted information in the check bill by using a second decryption key corresponding to the second encryption key to obtain valid time information; the validity of the check bill is checked by using the first account number, the program identifier, the first identifier and the valid time information; and in the case of passing the verification, sending the target session message to the first client.

The validity check of the check ticket using the first account number, the program identifier, the first identifier and the valid time information may include at least one of:

determining whether the current time is within the valid time defined by the valid time information or not according to the valid time information, if so, passing the verification, and if not, failing to pass the verification;

and determining whether the first account is an effective account in the first application, whether the program identifier and the first identifier are effective, whether the program identifier and the first identifier are identification information for currently performing message transmission with the first account, and the like.

It should be noted that the session messages (e.g., the first message and the second message) of the present embodiment are session data (data content) that is acquired at the client of the sender and displayed at the client of the receiver.

The user may create a plurality of sessions for message transfer between the first account and the plurality of accounts in the second application, respectively, in the manner described above. The created multiple sessions may be collapsed into a target session list (a previous session of the target session). Each session in the target session list is used for carrying out message transmission between the first account and the target account of the second identifier in the second application, and the target session list comprises the target session.

Optionally, after the target session is created, the first terminal detects a target operation performed on the first client, where the target operation is used to indicate to return to a higher-level display interface of a current display interface of the first client; and displaying a target session list in the first client in response to the detected target operation.

The target operation may be a touch operation (e.g., click) performed on a button on the display interface of the first client that returns to a previous stage or exits from the current session, a touch operation (e.g., left-hand stroke or right-hand stroke) performed on a screen of the first terminal that displays the display interface of the first client, or a touch operation (e.g., click, double-click, continuous pressing for a predetermined time) performed on a virtual key or a physical key in the first terminal that controls the display of the interface.

According to the embodiment, a first touch operation executed on a target button in a display page of a target application program is detected, wherein the target application program runs in a first client of a first application, and an association relationship exists between a first account logged in the first client and a second account logged in the target application program; responding to the first touch operation, jumping to a display interface of a first client, and displaying a target session between a first account and a third account on the first client, wherein the third account is an account corresponding to a first identifier in the first application, the first identifier is an identifier in a second application, which is transmitted to the first client by a target application program in response to the first touch operation, and the target session is used for carrying out message transmission between the first account and a fourth account corresponding to the first identifier in the second application.

As an optional implementation, after displaying the target session between the first account and the third account on the first client, the method further includes:

s1, displaying prompt information at the target position of the target session, wherein the prompt information is used for prompting the link information corresponding to the display page;

s2, detecting a second touch operation executed on the prompt message;

and S3, responding to the second touch operation, and transmitting the link information to the second client logged in by the fourth account in the second application through the target session.

Optionally, the displaying the prompt information at the target location of the target session includes:

s11, a prompt message is displayed in the form of a floating window at the target position of the target session.

According to the embodiment, after the target session is created, the prompt information used for prompting the link information corresponding to the display page is displayed at the target position of the target session, and after the touch operation executed on the prompt information is detected, the link information is transmitted to the second client through the target session, so that the information of the current page of the target application program can be conveniently sent to the second client, and the communication efficiency is improved.

S1, detecting a target operation executed on the first client, wherein the target operation is used for indicating to return to a previous-level display interface of the current display interface of the first client;

and S2, responding to the target operation, displaying a target session list in the first client, wherein each session in the target session list is used for carrying out message transmission between the first account and a target account corresponding to the second identifier in the second application, and the target session list comprises the target session.

By the embodiment, the session between the first account and the target account corresponding to different identifiers in the second application is displayed in the session list mode, so that the user can manage the session corresponding to the second application conveniently, and the user experience is improved.

As an optional embodiment, before displaying the target session between the first account and the third account on the first client, the method further comprises: acquiring description information of a first identifier through a first client; and creating a target session between the first account and the third account on the first client by using the description information, wherein the description information is used for describing the third account in the target session.

Optionally, the obtaining, by the first client, the description information of the first identifier includes:

S1, sending a first request message to a first server of a first application, wherein the first request message carries a first account, a program identifier and a first identifier, and the program identifier is used for identifying a target application program;

s2, responding to the received first request message, encrypting the program identifier and the first identifier by using at least a first encryption key to obtain a check ticket, wherein the check ticket is used for the first server to check the received message carrying the check ticket;

s3, sending a second request message to a second server of a second application, wherein the second request message carries a check ticket;

s4, in response to the received second request message, decrypting the check ticket by using the first decryption key corresponding to the first encryption key to obtain the program identifier and the first identifier;

and S5, storing the check ticket and sending the description information to the first client through the first server under the condition that the program identifier has a binding relationship with the first identifier and the first identifier has the authority of message transmission with the first account.

Through the embodiment, the program identifier and the first identifier are verified by using the verification bill, so that the safety and the reliability of message transmission can be improved.

As an alternative embodiment, in response to receiving the first request message, encrypting at least the program identifier and the first identifier using the first encryption key, and obtaining the check ticket includes: encrypting the first account, the program identifier and the first identifier by using a first encryption key to obtain first encryption information; encrypting the valid time information by using a second encryption key to obtain second encryption information, wherein the verification bill comprises the first encryption information and the second encryption information, and the valid time information is used for identifying the valid time of the verification bill;

after displaying the target session between the first account and the third account on the first client, the method further comprises: receiving a target message sent by a second server, wherein the target message carries a target session message and a check bill, and the target session message is set to be sent to the first server by a second client logged in by a fourth account in a second application through the second server of the second application; decrypting the first encrypted information by using the first decryption key to obtain a first account, a program identifier and a first identifier; decrypting the second encrypted information by using a second decryption key corresponding to the second encryption key to obtain valid time information; carrying out validity check on the check bill by using the first account number, the program identifier, the first identifier and the valid time information; and in the case of passing the verification, sending the target session message to the first client.

Through this embodiment, through using first encryption key to encrypt program identification and first sign respectively, can improve message transmission's security and reliability, encrypt valid time information through using the second encryption key, use the second decryption key to decrypt valid time information, and carry out the validity check to the check-up bill through valid time information, can guarantee message transmission's ageing, avoided the second customer end can be for a long time to the condition that first customer end sent session message, improved user experience.

As an optional implementation, before displaying the target session between the first account and the third account on the first client, the method further includes:

s1, sending a third request message for acquiring a third account to the first server of the first application, where the third request message carries a program identifier and the first identifier, and the program identifier is used to identify a target application program;

and S2, receiving a response message returned by the first server in response to the third request message, wherein the response message carries a third account, and the third account is set as an account allocated by the first server for the first identifier of the target application program.

Through the embodiment, the first server allocates the third account corresponding to the first identifier, so that the third account is used for establishing the target session with the first account, message transmission between different applications can be realized under the existing network architecture, modification of the network architecture is reduced, and communication cost is saved.

According to another aspect of the embodiment of the invention, a message transmission method is provided. Alternatively, the message transmission method described above may be applied, but not limited, to the application environment shown in fig. 1.

Optionally, in this embodiment, as an optional implementation manner, as shown in fig. 4, the message transmission method may include:

s402, receiving a target message sent by a first client through a second client, wherein the first client is a client for logging in a first account in a first application, the second client is a client for logging in a fourth account in the second application, the target message is a message sent by a first session created by the first client by using a target identifier acquired from a target application program, and the fourth account is one of one or more accounts corresponding to the target identifier in the second application;

S404, displaying the target message in a second session corresponding to the first account on the second client.

Alternatively, the message transmission method may be applied to a terminal device (e.g., in the second terminal 110) operating with the first client. The message transmission method can be applied to the message transmission process of the client and the customer service staff, but not limited to the message transmission process.

For example, taking the message transmission between the client and the customer service staff as an example, the first terminal runs a first client logged in by a first account. The first client runs a target application program, the account number of the target application program is a second account number, and the first account number and the second account number have an association relation.

The customer clicks the "contact customer service" button in the display page of the target application. After detecting the click operation, the target application passes the customer service ID to the first client. The first terminal acquires the customer service identity information corresponding to the customer service ID through the first client, and creates a first session (acting as the target session) between a first account and a third account on the first client by using the customer service identity information, wherein the third account is an account corresponding to the first identifier in the first application. Because the third account and the first identifier have a corresponding relationship, the first message transmitted between the first account and the third account in the first session is the target message transmitted between the first account and the fourth account in the second application corresponding to the first identifier.

After receiving the first message sent by the first client, the second client of the second application displays the first message (i.e., the target message) in a second session corresponding to the first account on the second client.

The second session is established between the fourth account and a fifth account corresponding to the first account in the second application. Since the fifth account and the first account have a corresponding relationship, the first message transmitted between the fifth account and the fourth account in the second session is the first message transmitted between the first account and the fourth account.

The message transmission method in the present embodiment is explained below with reference to fig. 4.

In step S402, a first message (i.e., a target message) sent by a first client is received by a second client, where the first client is a client in which a first account in a first application is logged in, the second client is a client in which a fourth account in the second application is logged in, the first message is a message sent by a first session created by using a target identifier (acting as the first identifier) acquired from a target application program by the first client, and the fourth account is one of one or more accounts corresponding to the target identifier in the second application.

The target application program, the first application, the first client, the first account, the fourth account, the first session, and the target identifier (first identifier) are similar to those described above, and are not described herein again.

Optionally, the receiving, by the second client, the first message sent by the first client includes: and receiving a first message sent by a second server of the second application through the second client, wherein the first message is set to be sent to the second server by the first client through the first server of the first application.

The manner in which the second server receives the first message sent by the first client via the first server of the first application is similar to that described above, and is not described herein again.

In step S404, a first message is displayed in a second session corresponding to the first account on the second client.

The second session may be created before the first message is received (the second session being created from other messages sent by the first client before the first message is received) or may be created after the first message is received. In the created second session, the received first message is displayed.

Some applications create sessions in this application that require the use of accounts in this application (both parties to the session are accounts in this application). In the event that the second application belongs to such an application, a second session on the second client is created between the fourth account and the fifth account. Before creating the second session, the second terminal may send a request message for acquiring a fifth account to the second server, where the request message carries the first account, and the fifth account is an account corresponding to the first account in the second application; and receiving a response message returned by the second server response request message, wherein the response message carries a fifth account which is set as an account allocated for the first account by the second server.

After receiving the request message, the second server may allocate a fifth account corresponding to the first account, and send the allocated fifth account to the second client through a response message.

The second server may assign a fifth account to the first account for storage. And when a request message carrying the first account is received next time, matching the allocated accounts by using the first account, and matching to obtain a fifth account from the allocated accounts.

Optionally, after the first message is displayed in a second session corresponding to the first account on the second client, the second terminal may obtain a second message to be transmitted of the fourth account in the second session; the second message is transmitted to a second server of the second application to instruct the second server to transmit the second message to a first server of the first application, the second message is transmitted by the first server to the first client, and the second message is displayed in the first session.

After obtaining the second message, the second client may send the second message to the first server, so as to send the second message to the first client through the first server.

The second message may be sent with a variety of information, which may include, but is not limited to, at least one of: a fourth account number and a fifth account number. The second message and the plurality of messages may be carried in a fourth session request. The conversion method between the fifth account and the first account, the conversion method between the fourth account and the program identifier and the first identifier, the format of the session message, and the method for sending and displaying the second message to the first client may be similar to the foregoing, and details are not repeated here.

Optionally, after receiving a target message sent by a first client through a second client, a second terminal may obtain a historical session message corresponding to a first account, where the historical session message is a historical session message between the first account and one or more accounts; the historical conversation messages are displayed in the second conversation.

After receiving the target message sent by the first client through the second client, in order to enable customer service staff to know the historical session records (which may be chat records between one or more accounts corresponding to the first identifier, or chat records between other identifiers corresponding to the target application) before the user with the first account as soon as possible, the second terminal may obtain the historical session message corresponding to the first account.

The obtaining of the historical session message may be triggered by a target event, for example, a second session is created, an account of a second application corresponding to the first identifier is switched, and a first target operation performed on the second session is detected. After detecting that the target event occurs, the historical session message can be acquired by pulling from the second server.

Optionally, the acquiring the historical session message corresponding to the first account includes: detecting a first target operation executed on a second session, wherein the first target operation is used for triggering sending of a query message to a second server of a second application, and the query message is used for querying a historical session message; and receiving the history session message sent by the second server in response to the query message.

For example, after detecting a touch operation performed on a button of "historical conversation message" on the second conversation, or performing operations such as a slide-down operation, a left-hand operation, and a right-hand operation performed on an interface of the second conversation, the historical conversation message corresponding to the first account is pulled from the second server and displayed in the second conversation.

The user using the second client may create multiple sessions between the fourth account and multiple accounts in the first application, respectively, in the manner described above. The created plurality of sessions may be collapsed into a target session list (a previous session of the second session). The target session in the target session list is used for message transmission between the fourth account and the plurality of accounts in the first application, and the target session list includes the second session.

Optionally, after the target message is displayed in a second session corresponding to the first account on the second client, a second target operation performed on the second client may be detected, where the second target operation is used to indicate to return to a previous display interface of a current display interface of the second client; and responding to the second target operation, displaying a target session list in the second client, wherein each session in the target session list is used for carrying out message transmission between the fourth account and the target account in the first application, and the target session list comprises the second session.

According to the embodiment, a first message sent by a first client is received by a second client, wherein the first client is a client for logging in a first account in a first application, the second client is a client for logging in a fourth account in the second application, the first message is a message sent by a first session created by using a target identifier acquired from a target application program through the first client, and the fourth account is one of one or more accounts corresponding to the target identifier in the second application; the first message is displayed in a second session corresponding to the first account on the second client, and the client functions are provided for the user in a mode of respectively establishing sessions in the first client of the first application and the second client of the second application, so that the message transmission content can be conveniently acquired, and the convenience of acquiring the message transmission content is improved.

As an optional implementation, after receiving, by the second client, the target message sent by the first client, the method further includes:

s1, acquiring historical session information corresponding to the first account, wherein the historical session information is historical session information between the first account and one or more accounts;

S2, displaying the history session message in the second session.

Optionally, the acquiring the historical session message corresponding to the first account includes:

s11, detecting a first target operation executed on a second session, wherein the first target operation is used for triggering sending of a query message to a second server of a second application, and the query message is used for querying a historical session message;

and S12, receiving the history session message sent by the second server in response to the query message.

Through the embodiment, the history session message corresponding to the first account is acquired and displayed, so that the session history of the first account can be known conveniently, accurate service can be provided, and the user experience is improved.

As an optional implementation, after displaying the target message in the second session corresponding to the first account on the second client, the method further includes:

s1, detecting a second target operation executed on the second client, wherein the second target operation is used for indicating to return to a previous-level display interface of the current display interface of the second client;

s2, in response to the second target operation, displaying a target session list in the second client, where each session in the target session list is used for message transmission between the fourth account and the target account in the first application, and the target session list includes the second session.

According to the embodiment, the session between the fourth account and the different accounts in the first application is displayed in the session list mode, so that the customer service staff can manage the session corresponding to the first application conveniently, and the user experience is improved.

As an optional implementation, before displaying the first message in the second session corresponding to the first account on the second client, the method further includes:

s1, sending a request message for acquiring a fifth account to the second server, where the request message carries the first account, and the fifth account is an account corresponding to the first account in the second application;

s2, receiving a response message returned by the second server in response to the request message, where the response message carries a fifth account, and the fifth account is set as an account allocated to the first account by the second server;

s3, a second session is created using the fourth account and the fifth account.

Through the embodiment, the second server allocates the fifth account corresponding to the first account, so that the session between the first account and the fourth account is established by using the fifth account, message transmission between different applications can be realized under the existing network architecture, modification of the network architecture is reduced, and communication cost is saved.

The message transmission method is described below with reference to an alternative example. The message transmission method in this example can be applied to an application environment as shown in fig. 1. As shown in fig. 5, the message transmission method may include the steps of:

s1, the target application program sends a request message for requesting allocation of the identification information in the second application to the background server.

A first client of the first application logs in by using a first account, and a target application program running on the first client logs in by using a second account. The target application program sends a request message for requesting allocation of the identification information in the second application to its background server.

S2, the background server returns the first identifier to the target application program.

After receiving the request message, the background server allocates identification information (i.e. a first identification) in the second application to the second account according to the content of the currently displayed page of the target application program, and returns the allocated first identification to the target application program.

S3, detecting a first touch operation executed on a target button in a display page of the target application program, and transmitting current page information and a first identifier.

After detecting a first touch operation (e.g., clicking) performed on a target button in a display page of a target application program, the target application program transmits current page information and a first identifier to a first client, and the first client acquires the first identifier.

S4, the first client sends a first request message to the first server, where the first request message carries a first account, a program identifier, and a first identifier, and the program identifier is used to identify a target application program.

After acquiring the first identifier, the first client sends a first request message to the first server, where the first request message may carry the first account, the program ID of the target application, and the first identifier. The first request message may be for requesting description information of the first identity.

And S5, the first server sends a second request message to the second server, wherein the second request message carries the check ticket.

After receiving the first request message, the first server encrypts the program ID and the first identifier by using at least a first encryption key to obtain a check ticket, wherein the check ticket is used for the first server to check the received message carrying the check ticket.

Optionally, the first server may encrypt the first account, the program ID, and the first identifier using a first encryption key, to obtain first encryption information; and encrypting the valid time information by using a second encryption key to obtain second encryption information, wherein the verification bill comprises the first encryption information and the second encryption information, and the valid time information is used for identifying the valid time of the verification bill.

After obtaining the check ticket, the first server sends a second request message to the second server, wherein the second request message carries the generated check ticket, and the second request message is used for requesting the description information of the first identifier.

And S6, the second server verifies the information carried by the verification bill, and if the verification is passed, the verification bill is stored.

After receiving the second request message, the second server firstly responds to the received second request message, and decrypts the check ticket by using the first decryption key corresponding to the first encryption key to obtain the program ID and the first identifier. Then, the check bill is checked, and the check mode can be as follows: and checking whether the program ID and the first identifier have a binding relationship, and whether the first identifier has the authority of transmitting the message with the first account. And under the condition that the program ID has a binding relationship with the first identifier and the first identifier has the authority of carrying out message transmission with the first account, the second server stores the check bill so as to be used in the subsequent session message transmission.

S7, the second server returns the description information of the first identifier to the first server.

Each first identification may correspond to an actual account number (e.g., a fourth account number) in one or more second applications. For a one-to-one scenario, the description information may include account related information of the actual account. For one-to-many scenarios, the description information may be preconfigured information.

S8, the first server transmits the description information of the first identifier back to the first client.

After receiving the description information, the first server transmits the description information back to the first client to instruct the first client to establish the target session. The target session is created according to the indication of the return message, and the return message carries indication information for indicating the first client to establish the target session. The target session may also be created according to the configuration information, where the configuration information is used to instruct the first client to create the target session between the first account and a third account after receiving the description information of the first identifier, where the third account is an account in the first application corresponding to the first identifier, and the target session is used to perform message transmission between the first account and a fourth account in the second application corresponding to the first identifier.

The third account may be obtained by the first client sending a third request message to the first server. The first client may send a third request message for acquiring a third account to the first server, where the third request message carries a program ID and a first identifier, and the program ID is used to identify the target application program. The first client may further receive a response message returned by the first server in response to the third request message, where the response message carries a third account, and the third account is set as an account allocated by the first server for the first identifier of the target application program.

After obtaining the description information, the first account, and the third account, the first client may create a target session between the first account and the third account, where the description information is used to describe the third account in the target session.

The target session may be included in a target session list, and each session in the target session list is used for performing message transmission between the first account and a target account corresponding to the second identifier (which may be the first identifier, or may be different from the first identifier) in the second application.

The target session list may be retrieved by: detecting a target operation executed on a first client, wherein the target operation is used for indicating to return to a previous-level display interface of a current display interface of the first client; and responding to the target operation, and displaying a target session list in the first client, wherein each session in the target session list is used for carrying out message transmission between the first account and a target account corresponding to the second identifier in the second application, and the target session list comprises the target session.

And S9, the first client sends the session message through the created target session.

After the target session is established, the first client can acquire a first message to be transmitted of the first account in the target session; the first message is transmitted to a first server.

The first client can display prompt information at a target position (displayed in a floating layer window form) of the target session, wherein the prompt information is used for prompting link information corresponding to a display page; detecting a second touch operation executed on the prompt information; and responding to the second touch operation, and transmitting the link information to the first server through the target session.

The first message may be other session messages to be transmitted in addition to the above-mentioned link information.

And S10, the first server and the second server carry out message intercommunication delivery.

After receiving a session message (first message) sent by a first client, the first server and a second server perform message intercommunication delivery, and send the received session message to the second server. The message for intercommunication delivery may carry a first account, a program ID, and a first identifier.

S11, performing message synchronization through the second session between the fourth account and the fifth account.

After receiving the delivery message of the first server, the second server verifies the binding relationship between the program ID carried in the message and the first identifier, and the authority of the first identifier. If the authentication is passed, the second server may forward the message to the second client logged in using a fourth account corresponding to the first identity.

After receiving the session message (first message) sent by the second server, the second client may display the session message in a second session corresponding to the first account on the second client.

The second session may be created by: sending a request message for acquiring a fifth account to the second server, wherein the request message carries the first account, and the fifth account is an account corresponding to the first account in the second application; receiving a response message returned by the second server in response to the request message, wherein the response message carries a fifth account which is set as an account allocated to the first account by the second server; a second session is created using the fourth account and the fifth account.

The second session may be included in a target session list, each session in the target session list is used for message transmission between the fourth account and a target account (which may be the first account or another account different from the first account) in the first application, and the target session list includes the second session.

The target session list may be retrieved by: detecting a second target operation executed on a second client, wherein the second target operation is used for indicating to return to a previous-level display interface of a current display interface of the second client; and responding to the second target operation, and displaying a target session list in the second client.

After the second session is created, a history session message (history session message is a history session message between the first account and one or more accounts corresponding to the first identifier in the second application) can be called and displayed in an active or passive mode. For the active calling mode, after the second session is established, the second client actively acquires the historical session message corresponding to the first account, and displays the historical session message in the second session. For the passive invocation mode, after detecting the first target operation executed on the second session, sending a query message for querying the historical session message to the second server of the second application, and receiving the historical session message sent by the second server in response to the query message.

S12, the second client sends a second message to the second server.

And the second client acquires a second message to be transmitted of the fourth account in the second session, and transmits the second message to a second server of the second application.

And S13, the second server and the first server carry out message intercommunication delivery.

After receiving a second message sent by the second client, the second server carries the previously stored encrypted ticket in the received message and sends the received message to the first server.

And S14, the first server checks the encrypted ticket carried in the received message, and synchronizes the message with the first client when the check is passed.

The first server receives a third message sent by the second server, wherein the third message carries a second message and a check bill, and the second message is set to be sent to the first server by a second client logged in by a fourth account in the second application through the second server of the second application; decrypting the first encrypted information by using the first decryption key to obtain a first account, a program identifier and a first identifier; decrypting the second encrypted information by using a second decryption key corresponding to the second encryption key to obtain valid time information; carrying out validity check on the check bill by using the first account number, the program identifier, the first identifier and the valid time information; and in the case that the verification is passed, sending the second message to the first client.

The first client displays the second message in the target session after receiving the second message.

The following description is made on a scenario that the first application and the second application are both instant messaging applications, the target application program is an applet and the background server is a third-party background, and a third-party enterprise displays commodity information to a client through the applet in the first instant messaging application and provides a customer service function to the client through the second instant messaging application.

The above message transmission method can be applied to a network architecture as shown in fig. 6. As shown in fig. 6, the message transmission architecture includes: a third party (the third party's backend server), a first instant messaging application (the first application), and a second instant messaging application (the second application). Each part of the architecture is explained below.

1) Third party

The background server of the third party may store the staff information of all or part of the customer service staff of the third party enterprise, and the staff information may include: and (4) customer service ID.

2) First instant messaging application

The first instant messaging application comprises a client of the first instant messaging application (first client) and a first instant messaging application backend (first server). After detecting a touch operation performed on the target button (for example, detecting a click operation performed on a button of "contact customer service"), the first instant messaging application backend may generate identity authentication ticket information for the user to contact the customer service person, obtain the identity information of the customer service ID from the second instant messaging application backend (the second server), and initiate a customer service session.

3) Second instant messaging application

The second instant messaging application comprises a client of the second instant messaging application (the second client) and a second instant messaging application backend (the second server).

The second instant messaging application background stores the identity authentication bill transmitted by the first instant messaging application, acquires the identity of the client from the first instant messaging application, and distributes the customer service session to specific staff (customer service staff) according to the seat management system to realize real-time chat.

As shown in fig. 7, the message transmission method in this example may include the following steps:

and S1, the target application program in the first instant messaging application sends a request message for requesting to distribute the customer service to the third-party background.

When the target application program is entered through the first client for the first time, the client ID (second account) for logging in the target application program can be acquired in various ways, for example, the first instant messaging application may assign a client ID (second account) associated with each user ID to each user ID, and for example, the first instant messaging application may also acquire the client ID associated with the user ID from the third party backend by sending a request-response manner.

After detecting that the user logs in a target application program in the first instant messaging application by using the client ID or enters a commodity page in the target application program, the target application program sends a request message for requesting to distribute customer service to a third party background. The request message may carry a client ID (first identification).

And S2, the third party background sends the customer service information to the small program.

After receiving the request message, the third-party backend allocates a customer service person serving the user identity (such as the client ID) and the content of the current display page of the target application program to the user identity, and transmits the allocated customer service ID by calling a contact customer service interface provided by the target application program framework.

Through the steps, the third-party background distributes the customer service for the third-party background in advance according to the user identity. The contact client process may be transferred to the first client of the first instant messaging application for processing.

S3, the contact service is clicked, and the current page information and the service ID are transmitted.

After detecting that a target button of the contact customer service on the current page of the target application program is clicked, the target application program sends a contact customer service instruction to the first client. The contact service instruction may carry current page information, a service ID, a user ID, and a client ID.

And S4, the first client sends a first request for acquiring the customer service information to the first instant messaging application background.

After receiving a contact customer service instruction sent by a target application program, a first client transmits an applet ID (program identification) and a customer service ID to a first instant messaging application background (first server) in a login state of a current first instant messaging application user (namely, a user ID for logging in the first client currently is acquired). The above-mentioned delivery may be realized by sending a first request (first request message) for acquiring the customer service information (account information), and carrying the applet ID and the customer service ID in the first request. The first request may also carry at least one of the following: a user ID and a client ID.

And S5, the first instant messaging application background sends the generated ticket to the second instant messaging application background.

After receiving the first request, the first instant messaging application background encrypts the user ID, the customer service ID and the applet ID by using a first encryption key to generate an encrypted identity verification bill (bill information for identity verification and verification bill), and sends a second request (second request message) for requesting the customer service information to a second instant messaging application background (second server), wherein the second request carries the encrypted identity verification bill to request information such as the identity information of the customer service and enterprise authentication information from the second instant messaging application background.

Optionally, the identity check ticket may further carry encrypted valid time information, where the valid time information is used to indicate the valid time of the identity check ticket. There are various ways to encrypt the validity time information, which may include, but is not limited to, one of the following: encrypting the valid time information using a first encryption key; encrypting the valid time information using a second encryption key different from the first encryption key; the effective time information is encrypted by using a first encryption key, and then the encrypted effective time information is encrypted by using a second encryption key; the second encryption key is used for encrypting the valid time information, and then the first encryption key is used for encrypting the encrypted valid time information.

And S6, verifying the information carried by the bill, and storing the bill if the verification is passed.

After receiving a second request sent by the first instant messaging application background, the second instant messaging application background decrypts the encrypted identity verification bill information in the second request by using a first decryption key corresponding to the first encryption key to obtain the applet ID and the customer service ID.

The second instant messaging application background stores the binding relationship between the applet ID and the customer service ID, and the authority of each customer service ID (whether the customer service ID can provide service for the user ID or the client ID). The second instant messaging application background can verify the binding relationship between the applet ID and the customer service ID and the authority of the customer service. And if the verification is passed, storing the identity verification bill sent by the first instant messaging application background for subsequent use, and returning the customer service identity information to the first instant messaging application background.

For a scene that the encrypted valid time information is carried in the identity verification bill and the valid time information is encrypted only by using the first encryption key, the second instant messaging application background can decrypt the valid time information, and the verification performed by the second instant messaging application background can include the verification of the valid time.

For the scene that the encrypted effective time information is carried in the identity verification bill and the effective time information is encrypted by using the second encryption key, the second instant messaging application background cannot decrypt the effective time information because the second decryption key corresponding to the second encryption key cannot be known, and the verification performed by the second instant messaging application background does not include the verification of the effective time.

And S7, the second instant messaging application background returns the customer service identity information (description information) to the first instant messaging application background.

Each customer service ID may correspond to an actual account number (second account number) in one or more second instant messaging applications. For a one-to-one scenario, the customer service identity information may include account related information for the actual account. For a one-to-many scenario, the customer service identity information may be pre-configured customer service information.

The pre-configured customer service information may be information related to an account of one of the plurality of actual accounts corresponding to the customer service ID (i.e., associated with a specific actual account), or may not be information related to an account of one of the plurality of actual accounts corresponding to the customer service ID (i.e., not associated with a specific actual account).

The returned customer service identity information may be set as needed, which is not specifically limited in this example, and as long as the information that can be used by the first client to create a customer service session (first session, target session) between the user ID and the account corresponding to the customer service ID can be used as the customer service identity information.

And S8, the first instant messaging application background transmits the customer service identity information back to the first client.

After receiving the customer service identity information, the first instant messaging application background returns the customer service identity information to the first client side, and the first client side is made to establish a customer service session. The customer service session is created according to the instruction of the return message, and the return message carries instruction information for instructing the first client to establish the customer service session. The client session may also be created based on configuration information that instructs the first client to create a customer service session after receiving the client identity information.

And S9, the first instant communication application client sends a message to the customer service through the created customer service session.

And after receiving the customer service identity information, creating a customer service session according to the customer service identity information. The ID used for creation of the client service session may be a user ID and an OpenIm ID (OpenIm ID 1, i.e., a third account) is assigned to the client service ID with the first server. After the customer service session is created, the page information of the current page of the target application program is brought into the customer service session and emerges in a bubble form. The user can send it into the customer service session by one touch. The user may also send other information (by way of a session message) to the client in the client session in addition to the page information for the current page. The sent message may also carry a user ID and an OpenIm ID.

As shown in fig. 8, on the first client side (i.e., client side), the user clicks on the customer service in the applet, creating a customer service session. In the client session, the user can send the currently visited page to the customer service by one key.

The created customer service session can be folded in the first-level session of the customer service message (namely, the first-level session of the customer service session), a user can communicate with a plurality of customer services at the same time (the customer services can belong to the same third party or different third parties), and a plurality of next-level sessions (namely, customer service sessions) under the customer service message can be provided. For each customer service session, the user can view the customer service identity and the enterprise authentication information of the customer service personnel corresponding to the customer service session.

And S10, the first instant messaging application background and the second instant messaging application background carry out message intercommunication delivery.

The communication protocol used for the message intercommunication delivery can be OpenIM protocol. The OpenIM protocol establishes an interactive protocol between a first instant messaging application background and a second instant messaging application background, and comprises a series of contents such as user ID, identity authentication, message delivery and the like.

And the first instant messaging application background delivers the user message to the second instant messaging application background through an OpenIM protocol, wherein the message carries the user ID, the customer service ID and the applet ID.

S11, perform message synchronization through the customer service session between employee ID and OpenIm ID 2.

After receiving the delivery message of the first instant messaging background, the second instant messaging application background verifies the binding relationship between the applet ID and the customer service ID carried in the message and the authority of the customer service. And if the verification is passed, the second instant messaging application background forwards the message to a corresponding customer service staff (customer service staff) according to the configured seat distribution rule.

There may be a plurality of actual accounts (employee ID, fourth account) of the second instant application corresponding to the customer service ID, and only one actual account is allowed for one customer service ID at the same time. After the verification is passed, the second instant messaging application background forwards the message to a second client which logs in by using the ID of the employee logged in by using the actual account currently bound with the ID of the client according to the configured agent allocation rule. The second client receives the information sent by the user and generates a new session. The session may be a customer service session between the employee ID and OpenIm ID 2 (the fifth account, the account allocated by the second instant messaging application background for the first account).

And S12, the second client sends the reply message to the second instant messaging application background.

The customer service personnel replies to the user in the newly created session. And the second client sends the message of the customer service staff to a second instant messaging application background.

For example, as shown in fig. 9, on the second client side (customer service side), a customer service person may directly reply to the consultation of the client in the customer service session of the second client. The customer service session is folded in the first-level session of customer service, and the same customer service personnel can simultaneously serve a plurality of customers. There may be a plurality of next-level sessions (i.e., customer service sessions) under the "customer message".

Through the API provided by the second instant messaging application, the third-party enterprise can inquire the identity of the first instant messaging application user in the applet, and further realize the management of the client relationship in the internal system. The internal system is a customer management system of a third-party enterprise.

The enterprise administrator of the third party can inquire the service records of the customer service and the customer in the management background, wherein the service records comprise information of specific staff, start and stop time, chat content and the like for providing the service. If the user has previously been contacted and subsequently distributed to another customer service employee, the user's historical service record can also be viewed by the new customer service employee.

Therefore, for each customer service session, the customer service personnel can check the customer information corresponding to the customer service session and the historical chat records of other customer services and the customer, and interface the internal system.

And S13, the second instant messaging application background and the first instant messaging application background carry out message intercommunication delivery.

After receiving the message sent by the second client, the second instant messaging application background carries the previously stored encrypted ticket in the received message and sends the message to the first instant messaging application background, wherein the sending protocol is an OpenIM protocol.

And S14, the first instant messaging application background checks the encrypted ticket carried in the received message, and when the check is passed, the first instant messaging application background synchronizes the message with the first client.

The first instant messaging application background unwraps the clear text of the ticket (by using the first decryption key or the first decryption key and the second decryption key), verifies the validity of the ticket (including information such as expiration time and identity), and synchronizes the message to the first client of the user if the verification is passed.

Because of the existence of the ticket, the customer service cannot actively send information to a user who has never been contacted, nor can he actively contact the user after the ticket expires.

By the method, the scheme of intercommunication between the applet customer service and the second instant messaging application is opened, the enterprise can uniformly manage customer resources, and the employee can communicate with the customer to provide services by using the client of the second instant messaging application at any time, so that the limitation that the customer can be contacted only by using a computer online is eliminated.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. 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 by the invention.

According to still another aspect of the embodiments of the present invention, there is also provided a message transmission apparatus for implementing the message transmission method, as shown in fig. 10, the apparatus includes:

(1) the detecting unit 1002 is configured to detect a first touch operation performed on a target button in a display page of a target application program, where the target application program is run in a first client of a first application, and an association relationship exists between a first account logged in the first client and a second account logged in the target application program;

(2) The display unit 1004 is configured to jump to a display interface of the first client in response to the first touch operation, and display a target session between a first account and a third account on the first client, where the third account is an account in the first application corresponding to the first identifier, the first identifier is an identifier in the second application, which is transferred to the first client by the target application program in response to the first touch operation, and the target session is used for performing message transmission between the first account and a fourth account in the second application corresponding to the first identifier.

Alternatively, the message transmission apparatus may be applied to a terminal device (e.g., in the first terminal 102) operating with the first client. The message transmission method can be applied to the message transmission process between the client and the customer service staff, but not limited to the message transmission process.

Alternatively, the detection unit 1002 may be configured to perform the foregoing step S202, and the display unit 1004 may be configured to perform the foregoing step S204.

According to the embodiment, a first touch operation executed on a target button in a display page of a target application program is detected, wherein the target application program runs in a first client of a first application, and an association relationship exists between a first account logged in the first client and a second account logged in the target application program; and after detecting that a target button in the display interface of the target application program is touched, providing client functions for a user in a mode of respectively displaying the sessions in the first client of the first application and the second client of the second application, so that the message transmission content can be conveniently acquired, and the convenience of acquiring the message transmission content is improved.

As an alternative embodiment, the above apparatus further comprises:

(1) the first display unit is used for displaying prompt information at a target position of a target session after the target session between a first account and a third account is established on a first client, wherein the prompt information is used for prompting link information corresponding to a display page;

(2) the first detection unit is used for detecting second touch operation executed on the prompt information;

(3) and the transmission unit is used for responding to the second touch operation and transmitting the link information to a second client logged in by a fourth account in the second application through the target session.

Optionally, the first display unit comprises: and the display module is used for displaying the prompt information on the target position of the target session in a floating layer window mode.

According to the embodiment, after the target session is created, the prompt information used for prompting the link information corresponding to the displayed page is displayed at the target position of the target session, and after the touch operation performed on the prompt information is detected, the link information is transmitted to the second client through the target session, so that the information of the current page of the target application program can be conveniently sent to the second client, and the communication efficiency is improved.

As an alternative embodiment, the above apparatus further comprises:

(1) the second detection unit is used for detecting a target operation executed on the first client after a target session between the first account and the third account is established on the first client, wherein the target operation is used for indicating to return to a previous-level display interface of a current display interface of the first client;

(2) and the second display unit is used for responding to the target operation and displaying a target session list in the first client, wherein each session in the target session list is used for carrying out message transmission between the first account and a target account corresponding to the second identifier in the second application, and the target session list comprises the target session.

As an alternative embodiment, the above apparatus further comprises:

(1) the acquisition unit is used for acquiring the description information of the first identifier through the first client before the target session between the first account and the third account is established on the first client;

(2) The creating unit is used for creating a target session between the first account and the third account on the first client by using the description information, wherein the description information is used for describing the third account in the target session.

Optionally, the obtaining unit includes:

(1) the system comprises a first sending module, a first receiving module and a second sending module, wherein the first sending module is used for sending a first request message to a first server of a first application, the first request message carries a first account, a program identifier and a first identifier, and the program identifier is used for identifying a target application program;

(2) the encryption module is used for responding to the received first request message and encrypting the program identifier and the first identifier by using at least a first encryption key to obtain a check bill, wherein the check bill is used for the first server to check the received message carrying the check bill;

(3) the second sending module is used for sending a second request message to a second server of a second application, wherein the second request message carries the check bill;

(4) the receiving module is used for responding to the received second request message and decrypting the check bill by using a first decryption key corresponding to the first encryption key to obtain a program identifier and a first identifier;

(5) And the third sending module is used for storing the check bill and sending the description information to the first client through the first server under the condition that the program identifier and the first identifier have a binding relationship and the first identifier has the authority of message transmission with the first account.

The first sending module is located at a first terminal running with a first client, the encryption module and the second sending module are located at a first server, and the receiving module and the second sending module are located at a second server.

As an alternative embodiment, the above apparatus further comprises: the first receiving unit, first decryption unit, second decryption unit, check unit and first transmitting unit, the encryption module includes: a first encryption sub-module and a second encryption sub-module, wherein,

the first encryption submodule is used for encrypting the first account, the program identifier and the first identifier by using a first encryption key to obtain first encryption information;

the second encryption submodule is used for encrypting the valid time information by using a second encryption key to obtain second encryption information, wherein the check bill comprises the first encryption information and the second encryption information, and the valid time information is used for identifying the valid time of the check bill;

The first receiving unit is used for receiving a target message sent by a second server after a target session between a first account and a third account is established on a first client, wherein the target message carries a target session message and a check bill, and the second message is set to be sent to the first server by a second client logged in by a fourth account in a second application through a second server of the second application;

the first decryption unit is used for decrypting the first encrypted information by using a first decryption key to obtain a first account, a program identifier and a first identifier;

a second decryption unit, configured to decrypt the second encrypted information using a second decryption key corresponding to the second encryption key, to obtain valid time information;

the verifying unit is used for verifying the validity of the verifying bill by using the first account number, the program identifier, the first identifier and the valid time information;

and the first sending unit is used for sending the target session message to the first client under the condition that the verification is passed.

As an alternative embodiment, the above apparatus further comprises:

(1) a second sending unit, configured to send, in response to the first touch operation, a third request message for obtaining a third account to the first server of the first application after obtaining the first identifier of the second application through the first client, where the third request message carries a program identifier and the first identifier, and the program identifier is used to identify the target application program;

(2) and the second receiving unit is used for receiving a response message returned by the first server in response to the third request message, wherein the response message carries a third account, and the third account is set as an account allocated by the first server for the first identifier of the target application program.

According to still another aspect of the embodiments of the present invention, there is also provided a message transmission apparatus for implementing the message transmission method, as shown in fig. 11, the apparatus includes:

(1) A receiving unit 1102, configured to receive, by a second client, a target message sent by a first client, where the first client is a client in which a first account in a first application is logged in, the second client is a client in which a fourth account in a second application is logged in, the target message is a message sent by a first session created by using a target identifier acquired from a target application program by the first client, and the fourth account is one of one or more accounts corresponding to the target identifier in the second application;

(2) a display unit 1104, configured to display the target message in a second session corresponding to the first account on the second client.

Alternatively, the message transmission apparatus may be applied to a terminal device (e.g., in the second terminal 110) operating with the second client. The message transmission device can be applied to the message transmission process of the client and the customer service staff, but not limited to the message transmission process.

Alternatively, the receiving unit 1102 may be configured to perform the aforementioned step S402, and the display unit 1104 may be configured to perform the aforementioned step S404.

According to the embodiment, a target message sent by a first client is received by a second client, wherein the first client is a client for logging in a first account in a first application, the second client is a client for logging in a fourth account in the second application, the target message is a message sent by a first session created by the first client by using a target identifier acquired from a target application program, and the fourth account is one of one or more accounts corresponding to the target identifier in the second application; and displaying the target message in a second session corresponding to the first account on the second client, and providing client functions for the user in a mode of respectively establishing sessions in the first client of the first application and the second client of the second application, so that the message transmission content can be conveniently acquired, and the convenience of acquiring the message transmission content is improved.

As an alternative embodiment, the above apparatus further comprises: a second obtaining unit, wherein,

(1) the system comprises an acquisition unit, a first client and a second client, wherein the acquisition unit is used for acquiring historical session messages corresponding to a first account after receiving a target message sent by the first client through the second client, and the historical session messages are between the first account and one or more accounts;

(2) and a display unit 1104 for displaying the history session message in the second session.

Optionally, the obtaining unit includes:

(1) the detection module is used for detecting a first target operation executed on a second session, wherein the first target operation is used for triggering the sending of a query message to a second server of a second application, and the query message is used for querying a historical session message;

(2) and the receiving module is used for receiving the historical conversation message sent by the second server responding to the query message.

As an alternative embodiment, the above apparatus further comprises: a detection unit, wherein,

(1) The detection unit is used for detecting a second target operation executed on a second client after displaying a first message in a second session corresponding to the first account on the second client, wherein the second target operation is used for indicating to return to a previous-level display interface of a current display interface of the second client;

(2) the display unit 1104 is further configured to display a target session list in the second client in response to the second target operation, where each session in the target session list is used for message transmission between the fourth account and a target account in the first application, and the target session list includes the second session.

As an alternative embodiment, the above apparatus further comprises: a sending unit and a creating unit, wherein,

(1) a sending unit, configured to send, to a second server, a request message for acquiring a fifth account before displaying a first message in a second session corresponding to a first account on a second client, where the request message carries the first account, and the fifth account is an account corresponding to the first account in a second application;

(2) The receiving unit 1102 is further configured to receive a response message returned by the second server in response to the request message, where the response message carries a fifth account, and the fifth account is set as an account allocated to the first account by the second server;

(3) and the creating unit is used for creating the second session by using the fourth account and the fifth account.

According to a further aspect of embodiments of the present invention, there is also provided a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the above-mentioned method embodiments when executed.

Alternatively, in the present embodiment, the storage medium may be configured to store a computer program for executing the steps of:

s1, detecting a first touch operation executed on a target button in a display page of a target application program, wherein the target application program runs in a first client of a first application, and an association relationship exists between a first account of a first client and a second account of the target application program;

And S2, responding to the first touch operation, jumping to a display interface of the first client, and displaying a target session between the first account and a third account on the first client, wherein the third account is an account corresponding to the first identifier in the first application, the first identifier is an identifier in the second application, which is transmitted to the first client by the target application program in response to the first touch operation, and the target session is used for message transmission between the first account and a fourth account corresponding to the first identifier in the second application.

s1, receiving a target message sent by a first client through a second client, wherein the first client is a client for logging in a first account in a first application, the second client is a client for logging in a fourth account in the second application, the target message is a message sent by a first session created by the first client by using a target identifier acquired from a target application program, and the fourth account is one of one or more accounts corresponding to the target identifier in the second application;

and S2, displaying the target message in the second session corresponding to the first account on the second client.

Alternatively, in this embodiment, a person skilled in the art may understand that all or part of the steps in the methods of the foregoing embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

According to still another aspect of the embodiments of the present invention, there is also provided an electronic device for implementing the message transmission method, as shown in fig. 12, the electronic device including: a processor 1202, a memory 1204, a display 1206, a transmitting device 1208, and the like. The memory has stored therein a computer program, and the processor is arranged to execute the steps of any of the above method embodiments by means of the computer program.

Optionally, in this embodiment, the electronic apparatus may be located in at least one network device of a plurality of network devices of a computer network.

Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:

Alternatively, it can be understood by those skilled in the art that the structure shown in fig. 12 is only an illustration, and the electronic device may also be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palmtop computer, and a Mobile Internet Device (MID), a PAD, etc. Fig. 12 is a diagram illustrating a structure of the electronic device. For example, the electronic device may also include more or fewer components (e.g., network interfaces, etc.) than shown in FIG. 12, or have a different configuration than shown in FIG. 12.

The memory 1204 can be used for storing software programs and modules, such as program instructions/modules corresponding to the message transmission method and apparatus in the embodiment of the present invention, and the processor 1202 executes various functional applications and data processing by running the software programs and modules stored in the memory 1204, that is, implements the message transmission method. The memory 1204 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 1204 may further include memory located remotely from the processor 1202, which may be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 1208 is used for receiving or sending data via a network. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 1208 includes a NIC (Network Interface Controller) that is connected to the router via a Network cable and other Network devices so as to communicate with the internet or a local area Network. In one example, the transmission device 1208 is a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner. Display 1206 displays the first session or the second session.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing one or more computer devices (which may be personal computers, servers, network devices, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention.

In the above embodiments of the present invention, the description of each embodiment has its own emphasis, and reference may be made to the related description of other embodiments for parts that are not described in detail in a certain embodiment.

In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims

1. A method for message transmission, comprising:

detecting a first touch operation executed on a target button in a display page of a target application program, wherein the target application program runs in a first client of a first application, and an association relation exists between a first account logged in the first client and a second account logged in the target application program;

and responding to the first touch operation, jumping to a display interface of the first client, and displaying a target session between the first account and a third account on the first client, wherein the third account is an account corresponding to a first identifier in the first application, the first identifier is an identifier in a second application transmitted to the first client by the target application program in response to the first touch operation, and the target session is used for carrying out message transmission between the first account and a fourth account corresponding to the first identifier in the second application.

2. The method of claim 1, wherein after displaying the target session between the first account and the third account on the first client, the method further comprises:

displaying prompt information at a target position of the target session, wherein the prompt information is used for prompting link information corresponding to the display page;

detecting a second touch operation executed on the prompt message;

and responding to the second touch operation, and transmitting the link information to a second client logged in by the fourth account in the second application through the target session.

3. The method of claim 2, wherein displaying the reminder information at the target location of the target session comprises:

and displaying the prompt message in a floating layer window form on the target position of the target session.

4. The method of claim 1, wherein prior to displaying the target session between the first account and the third account on the first client, the method further comprises:

obtaining description information of the first identifier through the first client;

And creating the target session between the first account and the third account on the first client by using the description information, wherein the description information is used for describing the third account in the target session.

5. The method of claim 4, wherein obtaining, by the first client, the description information of the first identifier comprises:

sending a first request message to a first server of the first application, where the first request message carries the first account, a program identifier, and the first identifier, and the program identifier is used to identify the target application program;

responding to the received first request message, and encrypting the program identifier and the first identifier by using at least a first encryption key to obtain a check bill, wherein the check bill is used for the first server to check the received message carrying the check bill;

sending a second request message to a second server of the second application, wherein the second request message carries the check ticket;

responding to the received second request message, and decrypting the check ticket by using a first decryption key corresponding to the first encryption key to obtain the program identifier and the first identifier;

And under the condition that the program identifier has a binding relationship with the first identifier and the first identifier has the authority of message transmission with the first account, storing the check ticket, and sending the description information to the first client through the first server.

6. The method of claim 5,

responding to the received first request message, encrypting the program identifier and the first identifier by using at least the first encryption key, and obtaining the check ticket comprises: encrypting the first account, the program identifier and the first identifier by using the first encryption key to obtain first encryption information; encrypting effective time information by using a second encryption key to obtain second encryption information, wherein the verification bill comprises the first encryption information and the second encryption information, and the effective time information is used for identifying the effective time of the verification bill;

after displaying the target session between the first account and the third account on the first client, the method further comprises: receiving a target message sent by the second server, wherein the target message carries a target session message and the check ticket, and the target session message is set to be sent to the first server by a second client logged in by the fourth account in the second application through the second server of the second application; decrypting the first encrypted information by using the first decryption key to obtain the first account, the program identifier and the first identifier; decrypting the second encrypted information by using a second decryption key corresponding to the second encryption key to obtain the valid time information; using the first account number, the program identifier, the first identifier and the valid time information to carry out validity check on the check bill; and sending the target session message to the first client under the condition that the verification is passed.

7. The method of any of claims 1-6, wherein prior to displaying the target session between the first account and the third account on the first client, the method further comprises:

sending a third request message for acquiring the third account to the first server of the first application, wherein the third request message carries a program identifier and the first identifier, and the program identifier is used for identifying the target application program;

and receiving a response message returned by the first server in response to the third request message, wherein the response message carries the third account, and the third account is set as an account allocated by the first server for the first identifier of the target application program.

8. A method for message transmission, comprising:

receiving a target message sent by a first client through a second client, wherein the first client is a client for logging in a first account in a first application, the second client is a client for logging in a fourth account in a second application, the target message is a message sent by a first session created by the first client by using a target identifier acquired from a target application program, the fourth account is one of one or more accounts corresponding to the target identifier in the second application, and the target application program runs in the first client of the first application;

And displaying the target message in a second session corresponding to the first account on the second client.

9. The method of claim 8, wherein after receiving, by the second client, the target message sent by the first client, the method further comprises:

acquiring historical session messages corresponding to the first account, wherein the historical session messages are historical session messages between the first account and the one or more accounts;

displaying the historical conversation message in the second conversation.

10. The method of claim 9, wherein obtaining the historical session message corresponding to the first account comprises:

detecting a first target operation executed on the second session, wherein the first target operation is used for triggering sending of a query message to a second server of the second application, and the query message is used for querying the historical session message;

and receiving the historical conversation message sent by the second server in response to the query message.

11. The method of any of claims 8 to 10, wherein prior to displaying the target message in the second session corresponding to the first account on the second client, the method further comprises:

Sending a request message for acquiring a fifth account to the second server, wherein the request message carries the first account, and the fifth account is an account corresponding to the first account in the second application;

receiving a response message returned by the second server in response to the request message, wherein the response message carries the fifth account, and the fifth account is set as an account allocated to the first account by the second server;

and creating the second session by using the fourth account and the fifth account.

12. A message transmission apparatus, comprising:

the system comprises a detection unit, a display unit and a display unit, wherein the detection unit is used for detecting a first touch operation executed on a target button in a display page of a target application program, the target application program runs in a first client of a first application, and an association relationship exists between a first account logged in the first client and a second account logged in the target application program;

and the display unit is used for responding to the first touch operation, jumping to a display interface of the first client, and displaying a target session between the first account and a third account on the first client, wherein the third account is an account corresponding to a first identifier in the first application, the first identifier is an identifier in a second application transmitted to the first client by the target application program in response to the first touch operation, and the target session is used for carrying out message transmission between a fourth account corresponding to the first identifier in the first account and the second application.

13. A message transmission apparatus, comprising:

a receiving unit, configured to receive, by a second client, a target message sent by a first client, where the first client is a client in which a first account in a first application is logged in, the second client is a client in which a fourth account in a second application is logged in, the target message is a message sent by a first session created by the first client using a target identifier acquired from a target application program, the fourth account is one of one or more accounts corresponding to the target identifier in the second application, and the target application program is run in the first client of the first application;

and the display unit is used for displaying the target message in a second session corresponding to the first account on the second client.

14. A storage medium, in which a computer program is stored, wherein the computer program is arranged to perform the method of any of claims 1 to 11 when executed.

15. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method of any of claims 1 to 11 by means of the computer program.