CN107342965A - Rich media communications method, system and server - Google Patents

Abstract

The embodiment of the present invention discloses a rich media communication method, system, and server. After receiving the first rich media message sent by the first client, the server detects whether communication between itself and the second client is possible; if communication fails, Then the server generates the first notification message and sends it to the first client, and the first client learns the reason for the failure of sending the first rich media message after parsing the first notification message. Furthermore, the sender user can handle the failure in other ways according to the reason for the message delivery failure, so as to enhance the user experience.

Description

Rich media communication method, system and server

technical field

The present invention relates to the technical field of communication, in particular to a rich media communication method, system and server.

Background technique

With the innovation of communication technology, it has entered the era of 4G (the 4th Generation mobile communication technology, the fourth generation mobile communication technology) of mobile communication. Network bandwidth is increasing at a rate of hundreds to thousands, which can provide more rapid transmission of information and richer business experience. Multimedia content replaces text information, video calls, and personal social presentations, etc., have become new trends in technological development. .

RCS (Rich Communication Suit, rich media communication) is a unified function set and implementation guidance implemented by GSMA (Global System for Mobile Communications assembly, GSM Association) based on existing technical standards and specifications, through iterative and agile methods, covering Business functions such as instant messaging, file transfer, group chat, network address book, message storage, and release and presentation of social information.

RCS is a typical service deployed on IMS (IP Multimedia Subsystem, IP Multimedia Subsystem). IMS is an IP-based network structure defined by 3GPP for mobile networks. It supports both fixed network access and mobile access. At present, the networks of operators all over the world are evolving to IMS networks.

Limited by the RCS standard protocol, in the current RCS solution, the server receives the rich media message sent by the sender user, and then the server sends the rich media message to the receiver user. However, when the receiving user is offline, the network side is faulty, or the receiving user is a non-RCS user, etc., the server cannot send the rich media message to the receiving user, and the server cannot notify the sending user of the failure status of sending the rich media message , that is, in this application scenario, the sender cannot know the sending status of the rich media message.

Contents of the invention

Embodiments of the present invention provide a rich media communication method, system, and server to solve the problem that in the prior art, when the receiver user is offline, the network side fails, or the receiver user is a non-RCS user, the sender user cannot know Issue with rich media messaging status.

In order to solve the above technical problems, the embodiment of the present invention discloses the following technical solutions:

In the first aspect, the embodiment of the present invention provides a rich media communication method, including: the server receives the first rich media message sent by the first client to the second client; the server detects that the server and the second client Whether communication is possible between the server and the second client; when the server cannot communicate with the second client, the server generates a first notification message, and the first notification message carries a communication failure reason; A client sends the first notification message, so that the first client displays the first notification message.

In the rich media communication method provided in this embodiment, when the server cannot communicate with the second client, the server generates a first notification message and sends it to the first client. After parsing the first notification message, the first client learns the reason why the delivery of the first rich media message fails. Further, the sender user can use other methods to deal with the failure of sending the message according to the reason, so as to enhance the user experience.

With reference to the first aspect, in a first possible implementation manner of the first aspect, when the communication between the server and the second client fails, the server generates a first notification message, including: when the When the server fails to communicate with the second client, the server obtains a communication failure reason between the server and the second client; the server generates the first notification message according to the communication failure reason.

With reference to the first aspect, in a second possible implementation manner of the first aspect, the method further includes: when the server and the second client can communicate, the server sends the first The rich media message is sent to the second client; the server obtains a second notification message, the second notification message is used to represent the receiving status of the second client receiving the first rich media message, and carries The second client corresponds to the extended information set by the user; the server sends the second notification message to the first client, so that the first client displays the extended information.

With reference to the first aspect, in a third possible implementation manner of the first aspect, the obtaining the second notification message by the server includes: receiving, by the server, the second notification message sent by the second client, and the first The second notification message is sent by the second client and carries the extended information.

With reference to the first aspect, in a fourth possible implementation manner of the first aspect, the acquiring the second notification message by the server includes: receiving, by the server, receiving status information sent by the second client, where the receiving status information is The information includes a successfully received status and a read status; the server acquires extended information, and generates the second notification message according to the received status information and the extended information.

In a second aspect, an embodiment of the present invention provides a server, including: a receiver, a processor, and a sender; the receiver is configured to receive a first rich media message sent by a first client to a second client; The processor is configured to detect whether the server can communicate with the second client; when the server cannot communicate with the second client, generate a first notification message, and the first The notification message carries a communication failure reason; the sender is configured to send the first notification message to the first client, so that the first client displays the first notification message.

With reference to the second aspect, in a first possible implementation manner of the second aspect, when the processor generates the first notification message, it is specifically configured to: when the server cannot communicate with the second client, obtain A communication failure reason between the server and the second client; generating the first notification message according to the communication failure reason.

With reference to the second aspect, in a second possible implementation manner of the second aspect, the sender is further configured to: when the server and the second client can communicate, the server sends the The first rich media message is sent to the second client; the processor is further configured to obtain a second notification message, and the second notification message is used to indicate that the second client receives the first rich media The receiving status of the message, and carries the extended information set by the corresponding user of the second client; the sender is also used to send the second notification message to the first client, so that the The first client displays the extended information.

With reference to the second aspect, in a third possible implementation manner of the second aspect, when the processor is configured to acquire the second notification message, it is specifically configured to: acquire the information sent by the second client received by the receiver. A second notification message, where the second notification message is sent by the second client and carries the extended information.

With reference to the second aspect, in a fourth possible implementation manner of the second aspect, when the processor is configured to obtain the second notification message, it is specifically configured to: receive the received message sent by the second client through the receiver. Status information, where the receiving status information includes a successfully received status and a read status; acquiring extended information, and generating the second notification message according to the receiving status information and the extended information.

A third aspect of the embodiments of the present invention provides a rich media communication system, including a first client, a second client, and a server; the first client is configured to send a first rich media communication system to the second client media message; the server is configured to receive the first rich media message sent by the first client to the second client; detect whether communication between the server and the second client is possible; when the server and the When communication between the second clients fails, generate a first notification message and send it to the first client, where the first notification message carries a communication failure reason; the first client is also used to display the first notification message A notification message.

It can be seen from the above technical solutions that in the rich media communication method provided by the embodiment of the present invention, after the server receives the first rich media message sent by the first client, it detects whether it can communicate with the second client; if it cannot communicate, Then the server generates the first notification message and sends it to the first client, and the first client learns the reason for the failure of sending the first rich media message after parsing the first notification message. Further, the sender user can use other methods to deal with the failure of sending the message according to the reason, so as to enhance the user experience.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, In other words, other drawings can also be obtained from these drawings without paying creative labor.

FIG. 1 is a schematic diagram of a rich media communication system architecture according to an embodiment of the present invention;

FIG. 2 is a schematic flowchart of a rich media communication method according to an embodiment of the present invention;

FIG. 3 is a schematic flowchart of another rich media communication method according to an embodiment of the present invention;

FIG. 4 is a schematic flowchart of another rich media communication method according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of another rich media communication method according to an embodiment of the present invention;

Fig. 6 is a block diagram of a server according to an embodiment of the present invention.

detailed description

In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described The embodiments are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts shall fall within the protection scope of the present invention.

Referring to FIG. 1 , it is a schematic diagram of a rich media communication system according to an embodiment of the present invention. The rich media communication system includes a server 110 , at least one first client 120 and a second client 130 .

In this embodiment, one of the first client 120 and the second client 130 serves as the sending client, and the other client serves as the receiving client. Both the first client and the second client may be an APP (Application, application program) installed on a mobile terminal (for example, a mobile phone), for example, a short message APP. The rich media messages transmitted between the two clients are forwarded by the server 110 . For example, when the first client 120 sends a rich media message to the second client 130 , the first client 120 sends the rich media message to the server 110 , and then the server 110 forwards the rich media message to the second client 130 .

Referring to Fig. 1 and Fig. 2, wherein, Fig. 2 is a schematic flowchart of a rich media communication method provided by an embodiment of the present invention, the method is applied in a server, as shown in Fig. 2, the method may include:

S110. The server receives the first rich media message sent by the first client to the second client.

In some embodiments of the present invention, the type of the first rich media message may include text, picture, voice, video, geographic location, electronic business card, two-dimensional code, and the like.

In this embodiment, the first client is a sender client, and the second client is a receiver client. The server is various application servers, for example, RCS AS (Application Server, application server), MMTel (MultiMedia Telephony, multimedia telephone) AS and so on. RCS AS provides users with various instant message service functions, such as peer-to-peer chat, group chat, file transfer, content sharing and so on.

S120. The server detects whether communication between the server and the second client is possible.

After receiving the first rich media message sent by the first client, the server detects whether it can communicate with the second client. The server sends a connection request to the second client, and if a connection response message returned by the second client is received, an MSRP (Message Session Relay Protocol, session relay protocol) connection between the server and the second client is established. If the connection response message returned by the second client is not received, it is determined that the communication between the server and the second client fails.

S130. When the communication between the server and the second client fails, the server generates a first notification message, where the first notification message carries a communication failure reason.

If the server cannot communicate with the second client, the server generates a first notification message, and the first notification message carries a communication failure reason.

For example, when the first rich media message is an IM (Instant Message, Instant Message) message, the first notification message may be an IMDN (Instant Message Disposition Notification, Instant Message Disposition Notification) message, and the reason for the communication failure may be included in the message content of the IMDN message. field. Wherein, the information in the message content field may be in XML (eXtensible Markup Language, eXtensible Markup Language) format.

For example, the reason for the communication failure may be that the user is offline, a network failure or a non-RCS user, and the like.

S140. The server sends a first notification message to the first client, so that the first client displays the first notification message.

The server sends the generated first notification message to the first client, and the first client parses the first notification message to obtain the reason for the failure of delivering the first rich media message, that is, the reason for the communication failure between the server and the second client.

In the rich media communication method provided by this embodiment, after receiving the first rich media message sent by the first client, the server detects whether communication between itself and the second client is possible; if communication is not possible, the server generates a first notification message, and send it to the first client, and the first client learns the reason why the delivery of the first rich media message fails after parsing the first notification message. Further, the sender user can use other methods to deal with the failure of sending the message according to the reason, so as to enhance the user experience.

Referring to FIG. 3 , it is a flowchart of another rich media communication method provided by an embodiment of the present invention. The method is applied to the rich media communication system shown in FIG. 1 . In this embodiment, the first rich media message is an IM message such as As shown in Figure 3, the method may include:

S210, the first client detects an IM message sent by the user to the second client, and sends a first connection request to the server; the first connection request carries account information corresponding to the user of the second client.

In this embodiment, the first client refers to the APP installed in the first client for rich media communication. After the APP detects the IM message sent by the user to another user, it sends a first connection request to the server. A connection request is used to request to establish a communication connection between the first client and the server, for example, an MSRP connection.

Moreover, the first connection request carries account information for receiving the IM message.

S220, the server establishes a communication connection between the server and the first client according to the first connection request.

For example, the communication connection may be an MSRP connection.

S230. The server sends a second connection request to the second client.

The second connection request is used to request to establish a communication connection between the server and the second client, for example, an MSRP connection.

In addition, this embodiment does not limit the execution order of S220 and S230, and the two steps may be executed simultaneously, or S230 is executed first, and then S220 is executed.

S240, the first client sends an IM message through the communication connection between itself and the server.

S250. When the server fails to establish a communication connection with the second client, acquire a communication failure reason.

For example, when the corresponding user of the second client is offline, the network side is faulty, or the non-RCS user is an application scenario, the communication between the server and the second client cannot be performed. Correspondingly, the cause of the communication failure may be that the user is offline, a network failure or a non-RCS user.

S260, the server generates a first IMDN message according to the cause of the communication failure. The first IMDN message carries a communication failure reason between the server and the second client.

S270. The server sends the first IMDN message to the first client.

S280. The first client parses the first IMDN message to obtain the communication failure reason, and presents the communication failure reason to the user.

In the rich media communication method provided in this embodiment, when the first client sends an IM message to the second client, when the server fails to send the IM message to the second client, the reason why the server fails to send the IM message is obtained, and A corresponding IMDN message is generated, and the IMDN message carries the specific reason for the failure to deliver the IM message, and is then sent to the first client. After parsing the IMDN message, the first client learns that the IM message has not been successfully delivered to the second client and the specific reason for the failure. Further, the user corresponding to the first client may use other methods to handle the failure according to the cause of the failure, so as to enhance user experience.

Referring to FIG. 4 , it is a flow chart of another rich media communication method according to an embodiment of the present invention. As shown in FIG. 4 , the method includes S210-S340. For S210-S240, please refer to the corresponding content in the embodiment shown in FIG. 3 , which will not be repeated here; S310～S340 are as follows:

S310. After the server successfully establishes a communication connection with the second client, send an IM message to the second client.

S320, the second client generates a second IMDN message and sends it to the server, where the second IMDN message carries IM message receiving status information and preset extended information.

The receiving party conveys the receiving status information of the IM message to the sending party through the IMDN message, for example, the receiving status information may include statuses such as delivered or read. After the second client successfully receives the IM message, it will generate the delivered status information; then, if the user corresponding to the second client has read the IM message, it will generate the read status information.

The extended information can be freely set by the second client corresponding to the user, and the user can set personalized content, for example, "I am on vacation, please call for urgent matters" and so on.

S330. The server sends the received second IMDN message to the first client.

S340, the first client parses the second IMDN message to obtain the extended information, and presents the extended information.

In the rich media communication method provided in this embodiment, the first client sends an IM message to the second client, and when the IM message is successfully delivered to the second client, the second client can generate a corresponding IMDN message, and send an IMDN message in the IMDN message Extended information carrying personalized content in the message, thus enriching the content carried in the IMDN message. At the same time, compared with sending the extended information separately, the extended information is directly carried in the IMDN message, and message interaction is not required again, so the traffic occupied by network message interaction is reduced.

Referring to FIG. 5 , it is a flow chart of another rich media communication method according to an embodiment of the present invention. As shown in FIG. 5 , the method includes S210-S450. For S210-S240, please refer to the corresponding content in the embodiment shown in FIG. 3 , which will not be repeated here; S410～S450 are as follows:

S410. After the server successfully establishes a communication connection with the second client, send an IM message to the second client.

S420. The second client generates a third IMDN message, where the third IMDN message carries receiving status information of the IM message.

The receiving status information may include statuses such as delivered or read.

S430. The server receives the third IMDN message, and inserts the pre-obtained extended information into the third IMDN message to obtain a fourth IMDN message.

The extended information can be set by the server, or can also be set by the receiving user and uploaded to the server.

S440. The server sends the fourth IMDN message to the first client.

S450, the first client parses the fourth IMDN message to obtain the extended information, and presents the extended information.

In the rich media communication method provided in this embodiment, the first client sends an IM message to the second client, and when the IM message is successfully delivered to the second client, the second client can generate a corresponding IMDN message and send it to the server. The server can insert extended information of personalized content in the IMDN message, thereby enriching the content carried in the IMDN message. The extended information can be set by the server or set by the corresponding user of the second client, which improves the flexibility of setting the extended information. At the same time, compared with sending the extended information separately, the extended information is directly carried in the IMDN message, and message interaction is not required again, so the traffic occupied by network message interaction is reduced.

Corresponding to the embodiment of the rich media communication method provided by the present invention, the present invention also provides an embodiment of a server for implementing rich media communication.

Referring to FIG. 6 , it is a block diagram of a server according to an embodiment of the present invention. As shown in FIG. 6 , the server may include: a receiver 110 , a processor 120 and a sender 130 .

The receiver 110 is configured to receive the first rich media message sent from the first client to the second client.

Rich media communication is performed between the first client and the second client through the server. In this embodiment, the first client is the sender, and the second client is the receiver. The first client first sends the first rich media message to the server, and then the server sends the first rich media message to the second client.

The processor 120 is configured to detect whether communication between the server and the second client is possible, and when the server and the second client cannot communicate, generate a first notification message, the first notification message carrying the communication failure reason.

When it is detected that normal communication with the second client cannot be performed, a first notification message is generated, and the communication failure reason is carried in the first notification message. If the first rich media message is an IM message, the first notification message is an IMDN message. For example, the reason for the communication failure may be that the user is offline, a network failure or a non-RCS user, and the like.

In some embodiments of the present invention, when the processor 120 generates the first notification message, it is specifically used to: when the server cannot communicate with the second client, obtain the cause of the communication failure between the server and the second client; The failure reason generates the first notification message.

The sender 130 is configured to send the first notification message to the first client, so that the first client displays the first notification message.

The first notification message generated by the processor 120 is sent to the first client through the transmitter 130, and the first client displays the first notification message to the user, so that the user is informed of the sending of the first rich media message sent to the second client. state.

The server provided in this embodiment, after receiving the first rich media message sent by the first client, detects whether communication between itself and the second client is possible; if communication is not possible, the server generates a first notification message and sends For the first client, the first client learns the reason why the delivery of the first rich media message fails after parsing the first notification message. Further, the sender user can use other methods to deal with the failure of sending the message according to the reason, so as to enhance the user experience.

In other embodiments of the present invention, in the application scenario where the server in the embodiment shown in FIG. 6 can communicate with the second client, it may also send extended information to the first client, where the extended information is the second Personal information set by the client, for example, "I am on vacation, please call for urgent matters".

In this embodiment, when the processor 120 detects that the server can communicate with the second client, the sender 130 sends the first rich media message to the second client. At the same time, the processor 120 acquires a second notification message, where the second notification message carries extended information set by the corresponding user of the second client. Then, the sender 130 sends the second notification message to the first client, so that the first client displays the extended information to the user.

In some embodiments of the present invention, after receiving the first rich media message, the second client may generate the second notification message and send it to the server. After receiving the second notification message, the receiver 110 in the server provides it to the processor 120, and the processor 120 provides the second notification message to the sender 130, and the sender 130 sends the second notification message to the first client.

In other embodiments of the present invention, the server may generate the second notification message. After receiving the first rich media message, the second client generates corresponding receiving state information and provides it to the server. The processor in the server generates a second notification message according to the received receiving state information and the extended information preset by the corresponding user of the second client, and the processor 120 generates a second notification message through the transmitter 130 to the second notification message. A client, after receiving the second notification message, the first client determines that the second client has received the first rich media message, and can obtain the extended information carried in the second notification message.

In the server provided in this embodiment, the first client sends the first rich media message to the second client through the server, and when the first rich media message is successfully delivered to the second client, the server can obtain the second notification message, and the second The extended information of the personalized content is carried in the notification message, thereby enriching the content carried in the second notification message. At the same time, compared with sending the extended information alone, the extended information is directly carried in the second notification message without message interaction again, thus reducing the traffic occupied by network message interaction.

An embodiment of the present invention also provides a rich media communication system, which includes a first client, a second client and a server. In this embodiment, the first client is the sending end, the second client is the receiving end, and the first client sends the first rich media message to the second client. Specifically, when the first client sends the first rich media message to the second client, it first sends the first rich media message to the server, and the server detects whether communication between itself and the second client is possible. If the client fails to communicate, the server generates a first notification message, and the first notification message carries a communication failure reason of the communication failure between the server and the second client. And the first notification message is sent to the first client, and the first client displays the first notification message to the user, so that the user learns the reason why the sending of the first rich media message fails.

Each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device or system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and for relevant parts, refer to part of the description of the method embodiments. The device and system embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, It can be located in one place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without creative effort.

The foregoing is only a specific embodiment of the present invention. It should be pointed out that for those of ordinary skill in the art, some improvements and modifications can also be made without departing from the principle of the present invention. It should be regarded as the protection scope of the present invention.

Claims (11)

1. A kind of 1. rich media communications method, it is characterised in that including：

   Server receives first Rich Media's message that the first client is sent to the second client；

   Whether the server detects can communicate between the server and second client；

   When that can not be communicated between the server and second client, the server generates the first notification message, described First notification message carries communication failure reason；

   The server sends first notification message to first client, so that first client displaying described the One notification message.
2. 2. according to the method for claim 1, it is characterised in that when can not between the server and second client During communication, the server generates the first notification message, including：

   When the server can not be with second client communication, the server obtains the server and the described second visitor The communication failure reason at family end；

   The server generates first notification message according to the communication failure reason.
3. 3. according to the method for claim 1, it is characterised in that methods described also includes：

   When that can be communicated between the server and second client, the server sends out first Rich Media message Give second client；

   The server obtains second notification message, and the second notification message is used to characterizing second client and receives described the The reception state of one Rich Media's message, and carry the extension information that user's setting is corresponded to by second client；

   The second notification message is sent to first client by the server, so that described in first client displaying Extend information.
4. 4. according to the method for claim 3, it is characterised in that the server obtains second notification message, including：

   The server receives the second notification message that second client is sent, and the second notification message is by the described second visitor Family end sends and carries the extension information.
5. 5. according to the method for claim 3, it is characterised in that the server obtains second notification message, including：

   The server receives the receiving status information that second client is sent, and the receiving status information includes being properly received State and reading state；

   The server obtains extension information, and according to the receiving status information and the extension information generation second notice Message.
6. A kind of 6. server, it is characterised in that including：Receiver, processor and transmitter；

   The receiver, first Rich Media's message of the second client is sent to for receiving the first client；

   The processor, whether can be communicated between the server and second client for detecting；When the server with When can not be communicated between second client, the first notification message is generated, first notification message carries communication failure reason；

   The transmitter, for sending first notification message to first client, so that first client is shown First notification message.
7. 7. server according to claim 6, it is characterised in that when the processor generates the first notification message, specifically For：

   When the server can not be with second client communication, the communication of the server and second client is obtained Failure cause；

   First notification message is generated according to the communication failure reason.
8. 8. server according to claim 6, it is characterised in that：

   The transmitter, it is additionally operable to when that can be communicated between the server and second client, the server is by institute State first Rich Media's message and be sent to second client；

   The processor, it is additionally operable to obtain second notification message, the second notification message is used to characterize the second client termination The reception state of first Rich Media message is received, and carries the extension information that user's setting is corresponded to by second client；

   The transmitter, it is additionally operable to the second notification message being sent to first client, so that first client Show the extension information.
9. 9. server according to claim 8, it is characterised in that when the processor is used to obtain second notification message, It is specifically used for：

   The second notification message that second client that the receiver receives is sent is obtained, the second notification message is by institute The second client is stated to send and carry the extension information.
10. 10. server according to claim 8, it is characterised in that when the processor is used to obtain second notification message, It is specifically used for：

    The receiving status information of the second client transmission is received by the receiver, the receiving status information is included successfully Reception state and reading state；

    Extension information is obtained, and the second notification message is generated according to the receiving status information and the extension information.
11. 11. a kind of rich media communications system, it is characterised in that including the first client, the second client and server；

    First client, for sending first Rich Media's message to second client；

    The server, first Rich Media's message of the second client is sent to for receiving the first client；Detect the service Whether can be communicated between device and second client；It is raw when that can not be communicated between the server and second client Into the first notification message and first client is sent to, first notification message carries communication failure reason；

    First client, it is additionally operable to show first notification message.