CN114465968A

CN114465968A - Cross-application interconnection method between different devices and related device

Info

Publication number: CN114465968A
Application number: CN202011624842.6A
Authority: CN
Inventors: 马志伟
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-10-22
Filing date: 2020-12-31
Publication date: 2022-05-10

Abstract

A cross-application interconnection method and a related device between different devices are provided. The method is applied to a communication system comprising a first terminal and a second terminal, wherein a first interface of a first instant messaging application on the first terminal is displayed on the first terminal, the first interface comprises a second user, and the second user is a registered user of a second instant messaging application on the second terminal; the first instant messaging application and the second instant messaging application are different applications; the first instant messaging application responds to the first operation and initiates a first communication behavior such as video call, voice call or message sending to the second user; and displaying a second interface of the second instant messaging application on the second terminal, wherein the first communication behavior from the first user is displayed in the second interface, and the first user is a registered user of the first instant messaging application on the first terminal. By the mode, different instant messaging applications on the two terminals can be interconnected and intercommunicated, and communication is facilitated.

Description

Cross-application interconnection method between different devices and related device

The present application claims priority from chinese patent application entitled "a method for interworking internet instant messaging with carrier RCS messaging" filed at 22.10/2020 of china patent office, application number 202011140974.1, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a cross-application interconnection method between different devices and a related apparatus.

Background

The variety of instant messaging applications is increasing, and people can communicate with family and friends through various instant messaging applications. Generally, two terminal devices need to use the same instant messaging application for instant messaging. Taking Hua as an open connection application as an example, when the open connection application is installed on both the terminal of the user A and the terminal of the user B, the user A can communicate with the user B through the open connection application. This approach is relatively limited, and it is necessary to require the same instant messaging application on the terminals of the user a and the user B, and how to break through this limitation is a matter of thought.

Disclosure of Invention

The application aims to provide a cross-application interconnection method and a related device among different devices, which are used for improving communication convenience.

In a first aspect, a method for cross-application interconnection between different devices is provided, where the method is applied to a communication system including a first terminal and a second terminal, and the method includes: displaying a first interface of a first instant messaging application on the first terminal, wherein the first interface comprises a second user, the second user is a registered user of a second instant messaging application on the second terminal, and the first instant messaging application and the second instant messaging application are different applications; the first instant messaging application responds to a first operation on the first interface and initiates a first communication behavior to the second user, wherein the first communication behavior comprises a video call, a voice call or message sending; and displaying a second interface of the second instant messaging application on the second terminal, wherein the first communication behavior from a first user is displayed in the second interface, and the first user is a registered user of the first instant messaging application on the first terminal.

That is to say, different instant messaging applications on the two terminals can be interconnected and intercommunicated, and the communication is convenient.

The first instant messaging application may be preset in the first terminal when the first terminal leaves a factory, or may be downloaded and installed in the first terminal by a user after the first terminal leaves the factory and is bought by the user. The relationship of the second instant messaging application to the second terminal may be understood similarly.

In one possible design, the first interface is a first chat interface with the second user, and the first operation is an operation of sending a message to the second user in the first chat interface; the first communication behavior is a behavior of sending a message to the second user, the second interface is a second chat interface with the first user, and the second chat interface comprises the message sent by the first user.

Namely, different instant messaging applications on the two terminals can send messages to each other, and the communication is convenient.

In one possible design, the first interface is an address book interface of the first instant messaging application, and the first operation is an operation of initiating a voice or video call to the second user in the address book interface; the first communication behavior is a behavior of initiating a voice or video call to the second user, and the second interface is a voice incoming call interface or a video incoming call interface from the first user.

That is to say, the two terminals can carry out video and voice communication between different instant messaging applications, and the communication is convenient.

In one possible design, the method further includes: the first instant messaging application queries whether the second user registers or opens the second instant messaging application; when the first instant messaging application determines that the second user is registered or the second instant messaging application is opened, a first mark is displayed in the first interface and used for indicating that the second user is registered or the second instant messaging application is opened.

That is to say, the first instant messaging application on the first terminal can inquire whether the second user registers or opens the second instant messaging application, and if so, the first instant messaging application on the first terminal can be interconnected with the second instant messaging application on the second terminal, so that the communication is convenient.

In one possible design, the second user is also a registered user of a third instant messaging application on the second terminal; the third instant messaging application is the same application as the first instant messaging application; displaying a switching button in the first interface; when the switch button is in a first state, the first instant messaging application is configured to initiate communication behavior to the third instant messaging application in the second terminal, and when the switch button is in a second state, the first instant messaging application is configured to initiate communication behavior to the second instant messaging application in the second terminal; before the first instant messaging application initiates a first communication action to the second user in response to the first operation at the first interface, the method further comprises: determining that the toggle button is in the second state.

That is to say, the first instant messaging application on the first terminal can communicate with the third instant messaging application on the second terminal, and can also communicate with the second instant messaging application on the second terminal, so that the communication is more convenient.

In a possible design, the communication system further includes a first server, a second server, and a third server, where the first server is a server corresponding to the first instant messaging application, the first server supports a first communication protocol, the second server is a server corresponding to the second instant messaging application, and the second server supports a second communication protocol; the third server is connected with the first server and the second server;

the first instant messaging application initiates a first communication action to the second user in response to a first operation at the first interface, including:

the first instant messaging application responds to the first operation and sends first communication information to the first server; the first communication information comprises a video call request, a voice call request or a message; the first communication information supports the first communication protocol;

the first server sends the first communication information to the third server;

the third server performs protocol conversion processing on the first communication information to obtain second communication information supporting the second communication protocol;

the third server sends the second communication information to the second server;

and the second server sends the second communication information to the second terminal.

That is to say, the first server corresponding to the first instant messaging application can communicate with the second server corresponding to the second instant messaging application, so as to realize communication between the first instant messaging application and the second instant messaging application.

the first instant messaging application inquires whether the second user registers or opens the second instant messaging application, and the method comprises the following steps:

the first instant messaging application sends a first query request to the first server; the first query request carries identification information of a second user, and the first query request is used for requesting to query whether the second user registers or opens the second instant messaging application; the first query request supports the first communication protocol;

the first server sends the first query request to the third server;

the third server performs protocol conversion processing on the first query request to obtain a second query request supporting the second communication protocol;

the third server sends the second query request to the second server;

the second server judges whether the second user is registered or opens the second instant messaging application based on the second query request;

the second server sends a first query result to the third server; the first query result supports the second communication protocol;

the third server performs protocol conversion processing on the first query result to obtain a second query result supporting the first communication protocol;

the third server sends the second query result to the first server;

and the first server sends the second query result to the first terminal.

That is, the first server corresponding to the first instant messaging application may communicate with the second server corresponding to the second instant messaging application, so the first instant messaging application may query whether the second user registers or opens the second instant messaging application.

In one possible design, the method further includes at least one of:

the first instant messaging application is an application supporting the first communication protocol; the second instant messaging application is an application supporting the second communication protocol; the first server is a server supporting the first communication protocol; the second server is a server supporting the second communication protocol; the first communication protocol is a smooth connection protocol; and the second communication protocol is an RCS protocol;

alternatively, the method further comprises at least one of:

the first instant messaging application is an application supporting the first communication protocol; the second instant messaging application is an application supporting the second communication protocol; the first server is a server supporting the first communication protocol; the second server is a server supporting the second communication protocol; the first communication protocol is an RCS protocol; and the second communication protocol is a clear connection protocol;

alternatively, the method further comprises at least one of:

the first instant messaging application is a smooth connection application; the second instant messaging application is an RCS application; the first server is a smooth connection server; the second server is an RCS server; the first communication protocol is a smooth connection protocol; and the second communication protocol is the RCS protocol;

alternatively, the method further comprises at least one of:

the first instant messaging application is an RCS application; the second instant messaging application is a smooth connection application; the first server is an RCS server; the second server is a smooth connection server; the first communication protocol is an RCS protocol; and the second communication protocol is a clear connection protocol.

The above is only an example of the first instant messaging application and the second instant messaging application, and other instant messaging applications are also possible, and the embodiment of the present application is not limited thereto.

In one possible design, the first instant messaging application is an RCS application and the second instant messaging application is a connectionless application, the method further comprising:

displaying device identifications of a plurality of devices corresponding to the second user in the first interface; the second user has registered a smooth connection application on each of the plurality of devices;

the first instant messaging application, in response to the first operation on the first interface, further comprises, before initiating the first communication action to the second user: and selecting a first device identifier from the plurality of device identifiers, wherein the device corresponding to the first device identifier is the second terminal.

That is, the RCS application on the first terminal may query the device identifications of the plurality of devices, such as the television, the mobile phone, etc., for which the second user registered the clear connection application. In this way, the first user of the first terminal may select one of the multiple devices (e.g., a television) corresponding to the second user to communicate, and in brief, the first user may communicate with the full-scene device of the second user through the RCS application on the first terminal.

before the displaying the device identifiers of the multiple devices corresponding to the second user in the first interface, the method further includes:

the first instant messaging application sends a third query request to the first server; the third query request carries identification information of a second user, and is used for requesting to query equipment which is registered by the second user or open a smooth connection application; the third query request supports the first communication protocol;

the first server sends the third query request to the third server;

the third server performs protocol conversion processing on the third query request to obtain a fourth query request supporting the second communication protocol;

the third server sends the fourth query request to the second server;

the second server determines device identifications of a plurality of devices of which the second user is registered or has opened a smooth connection application based on the fourth query request;

the second server sends a third query result to the third server; the third query result supports the second communication protocol;

the third server performs protocol conversion processing on the third query result to obtain a fourth query result supporting the first communication protocol; the third query result and the fourth query result are both used for indicating that the second user has registered or opened the device identifiers of the multiple devices of the open connection application;

the third server sends the fourth query result to the first server;

and the first server sends the fourth query result to the first terminal.

That is, the first server corresponding to the first instant messaging application may communicate with the second server corresponding to the second instant messaging application, so the first instant messaging application may query the device identifications of the plurality of devices registered or provisioned by the second user.

In one possible design, the second server sends a third query result to the third server, including:

when the second server determines that the first user exists in a preset list, the third server sends the third query result to the third server; the preset list is used for indicating the second user to disclose a plurality of devices corresponding to the second user to the users in the preset list; or the second server sends an authentication request to the second terminal, where the authentication request is used to indicate whether to approve disclosure of multiple devices corresponding to the second user to the first user; and when the second server receives a confirmation instruction, sending the third query result to the third server.

That is to say, the user on the preset list may disclose the multiple devices corresponding to the second user to the user, or the user who is confirmed by the second user may disclose the multiple devices corresponding to the second user, otherwise, the multiple devices corresponding to the second user cannot be obtained.

In a second aspect, a cross-application interconnection method between different devices is provided, where the method is applied to a first terminal, and the method includes:

displaying a first interface of a first instant messaging application on the first terminal, wherein the first interface comprises a second user, and the second user is a registered user of a second instant messaging application on the second terminal; the second instant messaging application and the first instant messaging application are different applications;

and the first instant messaging application responds to a first operation on the first interface and initiates a first communication behavior to the second user, wherein the first communication behavior comprises a video call, a voice call or message sending.

In one possible design, the first interface is a first chat interface with the second user, and the first operation is an operation of sending a message to the second user in the first chat interface; the first communication action is an action of sending a message to the second user.

In one possible design, the first interface is an address book interface of the first instant messaging application, and the first operation is an operation of initiating a voice or video call to the second user in the address book interface; the first communication activity is an activity of initiating a voice or video call to the second user.

In one possible design, the method further includes: the first instant messaging application queries whether the second user registers or opens the second instant messaging application; when the first instant messaging application determines that the second user is registered or the second instant messaging application is opened, displaying a first mark in the first interface, wherein the first mark is used for indicating that the second user is registered or the second instant messaging application is opened.

In one possible design, the method further includes: displaying a switching button in the first interface; when the switching button is in a first state, the first instant messaging application is configured to initiate a communication action to a third instant messaging application in the second terminal, wherein the third instant messaging application is the same application as the first instant messaging application; when the switch button is in the second state, the first instant messaging application is configured to initiate a communication action to the second instant messaging application in the second terminal.

In one possible design, the first instant messaging application querying whether the second user registers or opens the second instant messaging application includes:

the first instant messaging application sends a first query request to a first server; the first query request carries identification information of a second user, and the first query request is used for requesting to query whether the second user registers or opens the second instant messaging application;

the first instant messaging application receives query results from the first server.

In one possible design, the method further includes at least one of: the first instant messaging application is a smooth connection application; the second instant messaging application is an RCS application;

alternatively, the method further comprises at least one of: the first instant messaging application is an RCS application; the second instant messaging application is a smooth connection application;

alternatively, the method further comprises at least one of: the first instant messaging application is an application supporting a first communication protocol; the second instant messaging application is an application supporting a second communication protocol; the first communication protocol is a smooth connection protocol; and the second communication protocol is the RCS protocol;

alternatively, the method further comprises at least one of: the first instant messaging application is an application supporting a first communication protocol; the second instant messaging application is an application supporting a second communication protocol; the first communication protocol is an RCS protocol; and the second communication protocol is a clear connection protocol.

In one possible design, the first instant messaging application is an RCS application and the second instant messaging application is a clear connect application, the method further comprising:

In a possible design, before displaying device identifiers of a plurality of devices corresponding to the second user in the first interface, the method further includes:

the first instant messaging application sends a third query request to the first server; the third query request carries identification information of a second user, and is used for requesting to query equipment which is registered by the second user or open a smooth connection application;

In a third aspect, a cross-application interconnection method between different devices is provided, where the method is applied to a second terminal; the method comprises the following steps:

displaying a second interface of a second instant messaging application on the second terminal, wherein a first communication behavior from a first user is displayed in the second interface, the first communication behavior comprises a video call request, a voice call request or a message, the first user is a registered user of the first instant messaging application on the first terminal, and the first instant messaging application and the second instant messaging application are different applications;

and the second instant messaging application responds to the operation on the second interface and processes the first communication behavior.

In a possible design, the second interface is a first chat interface with the first user, the first communication behavior is that a message sent by the second user is received, and the processing on the first communication behavior includes message reply and message deletion.

In a possible design, the first communication behavior is a behavior of initiating a voice or video call to the second user, the second interface is a video call incoming interface or a voice call incoming interface of the first user, and the processing of the first communication behavior includes answering or rejecting a call.

In a fourth aspect, a cross-application interconnection method between different devices is provided, where the method is applied to a first server, where the first server is a server corresponding to a first instant messaging application in a first terminal, and the method includes:

the first server receives first communication information from the first terminal, wherein the first communication information comprises a video call request, a voice call request or a message initiated by a first user to a second user; the first user is a registered user of the first instant messaging application on the first terminal, the second user is a registered user of a second instant messaging application on a second terminal, and the first instant messaging application and the second instant messaging application are different applications;

and the first server sends the first communication information to a second server so as to send the first communication information to the second user through the second server, wherein the second server is a server corresponding to the second instant messaging application.

In one possible design, the first server sending the first communication to a second server, including:

the first server sends the first communication information to a third server, so that the third server converts the communication protocol of the first communication information from a first communication protocol to a second communication protocol, and sends the first communication information subjected to protocol conversion to the second server, wherein the first communication protocol is a communication protocol supported by the first server, and the second communication protocol is a communication protocol supported by the second server.

In one possible design, the method further includes at least one of: the first server is a server supporting a first communication protocol, the first instant messaging application is an application supporting the first communication protocol, the second server is a server supporting a second communication protocol, and the second instant messaging application is an application supporting the second communication protocol; the first communication protocol is a clear link protocol; and the second communication protocol is an RCS protocol;

alternatively, the method further comprises at least one of: the first server is a server supporting a first communication protocol, the first instant messaging application is an application supporting the first communication protocol, the second server is a server supporting a second communication protocol, and the second instant messaging application is an application supporting the second communication protocol; the first communication protocol is an RCS protocol; and the second communication protocol is a clear-to-connect protocol;

alternatively, the method further comprises at least one of: the first instant messaging application is a smooth connection application, the second instant messaging application is an RCS application, the first server is a smooth connection server, and the second server is an RCS server; the first communication protocol is a smooth connection protocol; the second communication protocol is an RCS protocol;

alternatively, the method further comprises at least one of: the first instant messaging application is an RCS application, the second instant messaging application is a smooth connection application, the first server is an RCS server, and the second server is a smooth connection server; the first communication protocol is an RCS protocol, and the second communication protocol is a smooth connection protocol.

In one possible design, the method further includes:

the first server receives a first query request from the first instant messaging application; the first query request carries identification information of a second user, and the first query request is used for requesting to query whether the second user registers or opens the second instant messaging application; the first query request supports the first communication protocol;

the first server sends the first query request to the third server, so that the third server performs protocol conversion processing on the first query request, processes the first query request into a second query request supporting the second communication protocol, and sends the second query request to the second server;

and the first server receives the query result from the third server and sends the query result to the first instant messaging application.

In one possible design, the method further includes:

the first server receives a third query request from the first instant messaging application; the third query request carries identification information of a second user, and is used for requesting to query equipment which is registered by the second user or open a smooth connection application; the third query request supports the first communication protocol;

the first server sends the third query request to the third server, so that the third query request is subjected to protocol conversion processing by the third server, processed into a fourth query request supporting the second communication protocol, and sent to the second server;

In a fifth aspect, a cross-application interconnection method between different devices is provided, where the method is applied to a third server, the third server is in communication with a first server and a second server, the first server is a server corresponding to a first instant messaging application, the first server supports a first communication protocol, the second server is a server corresponding to a second instant messaging application, the second server supports a second communication protocol, and the first instant messaging application and the second instant messaging application are different applications, and the method includes:

the third server receives first communication information from the first server, wherein the first communication information comprises a video call request, a voice call request or a message initiated by a first user to a second user; the first user is a registered user of the first instant messaging application and the second user is a registered user of the second instant messaging application;

and the third server sends the second communication information to the second server so as to send the second communication information to the second user through the second server.

In one possible design, the method further includes:

the third server receives a first query request from the first server; the first query request carries identification information of the second user, and the first query request is used for requesting to query whether the second user registers or opens the second instant messaging application; the first query request supports the first communication protocol;

the third server sends the second query request to the second server;

the third server receives a first query result from the second server; the first query result supports the second communication protocol;

and the third server sends the second query result to the first server.

In one possible design, the method further includes at least one of: the first instant messaging application is a smooth connection application, the second instant messaging application is an RCS application, the first server is a smooth connection server, and the second server is an RCS server; the first communication protocol is a smooth connection protocol; the second communication protocol is an RCS protocol;

alternatively, the method further comprises at least one of: the first instant messaging application is an RCS application, the second instant messaging application is a connectionless application, the first server is an RCS server (e.g., an RCS Hub shown in fig. 4), and the second server is a connectionless server (e.g., a connectionless cloud service shown in fig. 4, or referred to as a connectionless cloud server); the first communication protocol is an RCS protocol, and the second communication protocol is a smooth connection protocol.

In one possible design, the method further includes:

the third server (e.g., the easy-connect-RCS convergence gateway shown in fig. 4) receives the first query request from the first server; the first query request carries identification information of a second user, and is used for requesting to query equipment registered by the second user or open the second instant messaging application; the first query request supports the first communication protocol;

the third server sends the second query request to the second server;

and the third server sends the second query result to the first server.

In a sixth aspect, a method for cross-application interconnection between different devices is provided, where the method is applied to a second server, and the second server is a server corresponding to a second instant messaging application on a second terminal, and the method includes:

the second server receives first communication information from the first server, wherein the first communication information comprises a video call request, a voice call request or a message initiated by a first user to a second user; the first user is a registered user of a first instant messaging application on a first terminal, the second user is a registered user of a second instant messaging application on a second terminal, and the first instant messaging application and the second instant messaging application are not the same application;

and the second server sends the first communication information to the second user.

In one possible design, the second server receives the first communication from the first server, including:

the second server receives the first communication information from the first server through a third server, wherein the third server is used for connecting the first server and the second server, and the third server is used for converting the communication protocol of the first communication information from the first server into a second communication protocol due to the first communication protocol; wherein the first communication protocol is a protocol supported by the first server and the second communication protocol is a protocol supported by the second server.

In one possible design, the method further includes:

the second server receives a second query request sent by the third server; the second query request is used for requesting to query whether the second user registers or opens the second instant messaging application;

and the second server sends the first query result to the third server.

In one possible design, the method further includes:

the second server receives a fourth query request sent by the third server; the fourth query request is used for indicating the first user to request to query the equipment of the registered or open connection application of the second user;

and the second server sends a third query result to the third server.

when the second server determines that the first user exists in a preset list, the second server sends the third query result to the third server; the preset list is used for indicating the second user to disclose a plurality of devices corresponding to the second user to the users in the preset list; or the second server sends an authentication request to the second terminal, where the authentication request is used to indicate whether to approve disclosure of multiple devices corresponding to the second user to the first user; and when the second server receives a confirmation instruction, sending the third query result to the third server.

In a seventh aspect, there is provided a communication system, including: a first terminal and a second terminal;

the first terminal includes: a processor; a memory; wherein the memory stores one or more computer programs comprising instructions which, when executed by the processor, cause the first terminal to perform the steps of the first terminal in the method as provided in the first aspect above;

the second terminal includes: a processor; a memory; wherein the memory stores one or more computer programs comprising instructions which, when executed by the processor, cause the second terminal to perform the steps of the second terminal in the method as provided in the first aspect above.

In an eighth aspect, there is also provided a first terminal, including:

a processor, a memory, and one or more programs;

wherein the one or more programs are stored in the memory, the one or more programs comprising instructions which, when executed by the processor, cause the first terminal to carry out the method steps as provided in the second aspect above.

In a ninth aspect, there is also provided a second terminal, including:

a processor, a memory, and one or more programs;

wherein the one or more programs are stored in the memory, the one or more programs comprising instructions which, when executed by the processor, cause the second terminal to carry out the method steps as provided in the third aspect above.

In a tenth aspect, there is also provided a first server, including:

a processor, a memory, and one or more programs;

wherein the one or more programs are stored in the memory, the one or more programs comprising instructions which, when executed by the processor, cause the first server to carry out the method steps as provided in the fourth aspect above.

In an eleventh aspect, there is also provided a third server, including:

a processor, a memory, and one or more programs;

wherein the one or more programs are stored in the memory, the one or more programs including instructions which, when executed by the processor, cause the third server to carry out the method steps as provided in the fifth aspect above.

In a twelfth aspect, there is also provided a second server, including:

a processor, a memory, and one or more programs;

wherein the one or more programs are stored in the memory, the one or more programs comprising instructions which, when executed by the processor, cause the second server to carry out the method steps as provided in the sixth aspect above.

In a thirteenth aspect, a chip is provided, where the chip is coupled with a memory in an electronic device, and is used to call a computer program stored in the memory and execute the technical solution of any one of the first aspect to the sixth aspect of the embodiments of the present application, and "coupling" in the embodiments of the present application means that two components are directly or indirectly combined with each other.

In a fourteenth aspect, there is provided a computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method as provided in any of the first to sixth aspects above.

A fifteenth aspect provides a computer program product comprising a computer program which, when run on a computer, causes the computer to perform the method as provided in any of the first to sixth aspects above.

In a sixteenth aspect, there is provided a graphical user interface on an electronic device, the electronic device having a display, a memory, and a processor for executing one or more computer programs stored in the memory, the graphical user interface comprising graphical user interfaces displayed when the electronic device performs the methods of the first to sixth aspects.

The beneficial effects of the second aspect to the sixteenth aspect are referred to in the beneficial effects of the first aspect, and are not repeated.

Drawings

Fig. 1A is a schematic diagram of a hardware structure of a terminal device according to an embodiment of the present application;

fig. 1B is a schematic diagram of a software structure of a terminal device according to an embodiment of the present application;

fig. 1C is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 2A to 2D are schematic diagrams illustrating a communication principle of the connectionless application according to an embodiment of the present application;

fig. 3A to 3E are schematic diagrams illustrating a communication principle of an RCS application according to an embodiment of the present application;

fig. 4 is a schematic diagram illustrating a communication principle between an RCS application and a connectionless application according to an embodiment of the present application;

fig. 5A to 5C are schematic diagrams illustrating an RCS application on a first terminal querying whether a second terminal is open for a connection release application according to an embodiment of the present application;

fig. 6A to 6C are schematic diagrams illustrating a communication principle between an RCS application on a first terminal and a connectionless application on a second terminal according to an embodiment of the present application;

fig. 7 is a schematic diagram illustrating the communication principle between the RCS application on the first terminal and the tv of the second user according to an embodiment of the present application;

fig. 8A to 8C are schematic diagrams illustrating the second terminal uplink smooth application querying whether the first terminal activates the RCS application according to an embodiment of the present application;

fig. 9A to 9B are schematic diagrams illustrating a communication principle between an easy connection application on the second terminal and an RCS application on the first terminal according to an embodiment of the present application;

fig. 10 is a schematic diagram of another communication system provided in an embodiment of the present application;

fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Hereinafter, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

(1) Applications (app)

A software program that is capable of performing one or more specific functions. The applications can be of various types, such as video playing type applications, image shooting type applications, instant messaging applications, and the like. The instant messaging application includes, for example, a hua-chang application, various mailbox applications, WeChat (Wechat), Tencent chat software (QQ), WhatsApp Messenger, Link, Kakao Talk, or nailing. The application mentioned hereinafter may be an application installed when the electronic device is shipped, or an application downloaded from a network or acquired from another electronic device (for example, an application transmitted by another electronic device) during the use of the electronic device by a user.

(2) In the embodiments of the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items.

And, unless stated to the contrary, the embodiments of the present application refer to the ordinal numbers "first", "second", etc., for distinguishing a plurality of objects, and do not limit the size, content, sequence, timing, priority, degree of importance, etc., of the plurality of objects. For example, the first terminal, the second terminal, and the like are merely for distinguishing different terminals, and do not indicate a difference in priority, importance, or the like of the terminals.

The information interaction method across applications between different devices provided by the embodiment of the present application can be applied to electronic devices, and the following introduces an electronic device, a Graphical User Interface (GUI) for such an electronic device, and an embodiment for using such an electronic device. In some embodiments of the present application, the electronic device may be a portable electronic device, such as a mobile phone, a PAD, a portable computer, a wearable device with wireless communication function (such as a smart watch, smart glasses, a smart band, or a smart helmet), or an in-vehicle device. Exemplary embodiments of the portable electronic device include, but are not limited to, a mount

Or other operating system.

Fig. 1A shows a schematic structural diagram of an electronic device.

As shown in fig. 1A, the electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identity Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processor (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), among others. The different processing units may be separate devices or may be integrated into one or more processors. The controller can be a neural center and a command center of the electronic device. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution. A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device, and may also be used to transmit data between the electronic device and a peripheral device. The charging management module 140 is configured to receive charging input from a charger. The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like.

The wireless communication function of the electronic device may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, the baseband processor, and the like. The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in an electronic device may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication applied to electronic devices, including Wireless Local Area Networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), Global Navigation Satellite Systems (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, antenna 1 of the electronic device is coupled to the mobile communication module 150 and antenna 2 is coupled to the wireless communication module 160 so that the electronic device can communicate with the network and other devices through wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The display screen 194 is used to display a display interface of an application, and the like. The display screen 194 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the electronic device may include 1 or N display screens 194, with N being a positive integer greater than 1.

The camera 193 is used to capture still images or video. The cameras 193 may include a front camera and a rear camera.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The processor 110 executes various functional applications of the electronic device and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Wherein, the storage program area can store an operating system, software codes of at least one application program (such as an Aichi art application, a WeChat application, etc.), and the like. The data storage area may store data (e.g., images, video, etc.) generated during use of the electronic device, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as pictures, videos, and the like are saved in an external memory card.

The electronic device may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playing, recording, etc.

The pressure sensor 180A is used for sensing a pressure signal, and converting the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The gyro sensor 180B may be used to determine the motion pose of the electronic device. In some embodiments, the angular velocity of the electronic device about three axes (i.e., x, y, and z axes) may be determined by the gyroscope sensor 180B.

The gyro sensor 180B may be used for photographing anti-shake. The air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device calculates altitude, aiding in positioning and navigation, from barometric pressure values measured by barometric pressure sensor 180C. The magnetic sensor 180D includes a hall sensor. The electronic device may detect the opening and closing of the flip holster using the magnetic sensor 180D. In some embodiments, when the electronic device is a flip, the electronic device may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the opening and closing state of the leather sheath or the opening and closing state of the flip cover, the automatic unlocking of the flip cover is set. The acceleration sensor 180E can detect the magnitude of acceleration of the electronic device in various directions (typically three axes). When the electronic device is at rest, the magnitude and direction of gravity can be detected. The method can also be used for recognizing the posture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device may measure distance by infrared or laser. In some embodiments, taking a picture of a scene, the electronic device may utilize the distance sensor 180F to range to achieve fast focus. The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device emits infrared light to the outside through the light emitting diode. The electronic device uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device. When insufficient reflected light is detected, the electronic device may determine that there are no objects near the electronic device. The electronic device can detect that the electronic device is held by a user and close to the ear for conversation by utilizing the proximity light sensor 180G, so that the screen is automatically extinguished, and the purpose of saving power is achieved. The proximity light sensor 180G may also be used in a holster mode, a pocket mode automatically unlocks and locks the screen.

The ambient light sensor 180L is used to sense the ambient light level. The electronic device may adaptively adjust the brightness of the display screen 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 180L may also cooperate with the proximity light sensor 180G to detect whether the electronic device is in a pocket to prevent accidental touches. The fingerprint sensor 180H is used to collect a fingerprint. The electronic equipment can utilize the collected fingerprint characteristics to realize fingerprint unlocking, access to an application lock, fingerprint photographing, fingerprint incoming call answering and the like.

The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device implements a temperature processing strategy using the temperature detected by temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device performs a reduction in performance of a processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, the electronic device heats the battery 142 when the temperature is below another threshold to avoid an abnormal shutdown of the electronic device due to low temperatures. In other embodiments, the electronic device performs a boost on the output voltage of the battery 142 when the temperature is below a further threshold to avoid abnormal shutdown due to low temperature.

The touch sensor 180K is also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation applied thereto or nearby. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided through the display screen 194. In other embodiments, the touch sensor 180K may be disposed on a surface of the electronic device at a different position than the display screen 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, the bone conduction sensor 180M may acquire a vibration signal of the human vocal part vibrating the bone mass. The bone conduction sensor 180M may also contact the human pulse to receive the blood pressure pulsation signal.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic device may receive a key input, and generate a key signal input related to user settings and function control of the electronic device. The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc. The SIM card interface 195 is used to connect a SIM card. The SIM card can be attached to and detached from the electronic device by being inserted into the SIM card interface 195 or being pulled out of the SIM card interface 195.

It is to be understood that the components shown in fig. 1A do not constitute a specific limitation of the electronic device. The electronic device in embodiments of the invention may include more or fewer components than in fig. 1A. In addition, the combination/connection relationship between the components in fig. 1A may also be modified.

Fig. 1B shows a block diagram of a software structure of an electronic device according to an embodiment of the present application.

As shown in fig. 1B, the software structure of the electronic device may be a layered architecture, for example, the software may be divided into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer (FWK), an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom.

The application layer may include a series of application packages. As shown in FIG. 1B, the application layer may include cameras, settings, skin modules, User Interfaces (UIs), three-party applications, and the like. The three-party application program may include WeChat, QQ, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer may include some predefined functions. As shown in FIG. 1B, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like. The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device. Such as management of call status (including connection, hangup, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

The Android runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android. The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), media libraries (media libraries), three-dimensional graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The hardware layer may include various sensors, such as an acceleration sensor, a gyro sensor, a touch sensor, and the like, which are referred to in the embodiments of the present application.

Fig. 1C is a schematic diagram of a communication system according to an embodiment of the present application. As shown in fig. 1C, the communication system includes at least two terminals. Such as a first terminal and a second terminal. The hardware structure of the first terminal and the second terminal can be seen in fig. 1A, and the software structure can be seen in fig. 1B. The first terminal can be any device such as a mobile phone, a tablet computer, a PC, a watch, a bracelet and the like, wherein the device can be used for installing instant messaging application and the like. The second terminal can be any device such as a mobile phone, a tablet computer, a PC, a watch and a bracelet, which can be provided with instant messaging application. The first terminal and the second terminal may be the same or different, for example, both the first terminal and the second terminal are mobile phones, or one of the first terminal and the second terminal is a mobile phone and the other is a tablet computer; or, one is a mobile phone, the other is a bracelet, and the like, which are combined differently, and the embodiment of the application is not limited.

The first terminal comprises a first instant messaging application. The first instant messaging application may be a Huacheng chat application, WeChat, Tencent chat software (QQ), WhatsApp Messenger, Lianme (Line), RCS application, Kakao Talk, and so on.

The second terminal includes a second instant messaging application therein, which may be a Huacheng chat application, WeChat, Tencent chat software (QQ), WhatsApp Messenger, Link, RCS, Kakao Talk, etc.

Generally, if the first instant messaging application and the second instant messaging application are not the same application, the first instant messaging application in the first terminal and the second instant messaging application in the second terminal are not communicable. For example, the first instant messaging application is Huacheng freely connected application, the second instant messaging application is RCS application, and if the second terminal has no freely connected application, the first terminal cannot communicate with the second terminal through the freely connected application; similarly, if the first terminal does not have the RCS application, the second terminal cannot communicate with the first terminal through the RCS application.

In the cross-application interconnection method between different devices provided in the embodiment of the present application, when the first instant messaging application and the second instant messaging application are not the same application, the first terminal may communicate with the second instant messaging application in the second terminal through the first instant messaging application, or the second terminal may also communicate with the first instant messaging application in the first terminal through the second instant messaging application, so as to implement cross-application information interaction between different devices. The cross-application interconnection mode among different devices breaks through the limitation that two devices must use the same instant messaging application to communicate, and the application range is wider.

As shown in fig. 1C, the communication system further includes a first server and a second server, where the first server is a server corresponding to a first instant messaging application in the first terminal, and the second server is a server corresponding to a second instant messaging application in the second terminal. For example, if the first instant messaging application is a smooth connection application, the first server is a smooth connection cloud server, and if the second instant messaging application is an RCS application, the second server is an RCS server.

In the current scheme, the first server and the second server cannot communicate, so that the first instant messaging application in the first terminal and the second instant messaging application in the second terminal cannot communicate.

In this embodiment of the application, the communication system shown in fig. 1C further includes a third server, where the third server is used to connect the first server and the second server, so as to implement information interaction between the first server and the second server, and further implement information interaction between the first instant messaging application in the first terminal and the second instant messaging application in the second terminal.

Generally speaking, the communication protocols used by the first instant messaging application and the second instant messaging application are different, and it is assumed that the first instant messaging application uses the first communication protocol, that is, the first communication protocol is used for information interaction between the first instant messaging application and the first server. It is assumed that the second instant messaging application uses the second communication protocol, i.e. the information interaction between the second instant messaging application and the second server uses the second communication protocol.

If interworking between the first instant messaging application and the second instant messaging application is to be achieved, then interworking between the first server and the second server requires protocol conversion. In this embodiment, the third server may perform protocol conversion, such as conversion between the first communication protocol and the second communication protocol. For example, a first instant messaging application in a first terminal sends first communication information, such as a video call request, a voice call request, a message, etc., to a first server, which may be initiated to a second terminal. The first communication information is based on a first communication protocol. The first server sends the first communication information to a third server, the third server performs protocol conversion, the communication protocol of the first communication information is converted into a second communication protocol from the first communication protocol, then the first communication information based on the second communication protocol is sent to a second server, and then the second server sends the first communication information to a second instant messaging application in a second terminal, so that cross-application information interaction between different devices is achieved. That is, the third server performs protocol conversion to realize the intercommunication between the first server and the second server, and further realize the intercommunication between the first instant messaging application and the second instant messaging application.

The above takes as an example that the first instant messaging application uses one communication protocol and the second instant messaging application uses another communication protocol. Optionally, the first instant messaging application may use multiple communication protocols, for example, the first instant messaging application has a video/voice call function, and further includes a message (message) sending function. The different functions use different communication protocols, e.g. the messaging function of the first instant messaging application uses text protocol 1 and the video/voice call uses volite protocol 1. Similarly, the second instant messaging application may also use multiple communication protocols, for example, the messaging function of the second instant messaging application uses text protocol 2 and the video/voice call uses volite protocol 2. In this case, the third server may implement conversion between the text protocol 1 and the text protocol 2, and may also implement conversion between the volite protocol 1 and the volite protocol 2.

For example, in a scenario where a first instant messaging application on a first terminal sends a message (message) to a second instant messaging application on a second terminal: the first terminal sends the message to the first server, where the message uses text protocol 1. The first server sends the message to the third server, the third server converts the text protocol 1 of the message into the text protocol 2 adapted to the second server, then the third server can send the message after protocol conversion to the second server, and the second server sends the message to the second terminal, so as to realize the message (message) transmission between the first instant messaging application and the second instant messaging application.

For another example, in a scenario where a first instant messaging application on a first terminal initiates a video/voice call to a second instant messaging application on a second terminal: the first terminal sends a video/voice call request to the first server, the video/voice call request being based on volite protocol 1. The first server sends the video/voice call request to the third server, the third server converts the volite protocol 1 of the video/voice call request into the volite protocol 2 adaptive to the second server, then the third server can send the video/voice call request after protocol conversion to the second server, and the second server sends the video/voice call request to the second terminal, so that the video/voice call between the first instant messaging application and the second instant messaging application is realized.

The following embodiments mainly take a message (message) transmission process between a first instant messaging application and a second instant messaging application as an example to specifically describe the cross-application interconnection method between different devices provided in the present application.

The first terminal and the second terminal need to be involved in the explanation process of the scheme, and for convenience of understanding, it is assumed that the first terminal and the second terminal satisfy the following conditions:

the first terminal is a mobile phone, the user of the first terminal is a first user such as David, and the mobile phone number of the first terminal is a first number; the first terminal includes a first instant messaging application, which is hua liang chang application as an example.

The second terminal is a mobile phone, the user of the second terminal is a second user such as john, and the mobile phone number of the second terminal is a second number. The second terminal includes a second instant messaging application, and the second instant messaging application is an RCS application as an example.

For economy, the first instant messaging application is abbreviated as the first application, and the second instant messaging application is abbreviated as the second application.

The Huacheng Changjun application and the RCS application will be briefly described below.

Yichang applications

Fig. 2A is a schematic diagram of a communication system supporting a connectionless application. As shown in fig. 2A, the system includes a first terminal and a second terminal and a smooth cloud service. The first terminal comprises a smooth connection application, and the second terminal also comprises a smooth connection application. The freely connected cloud service may be understood as a cloud server, and the type of the cloud server is not limited in the present application. The smooth connection cloud service comprises a call subsystem, a management subsystem and a message subsystem. The call subsystem is responsible for call management of voice and video, the message subsystem is responsible for management of messages (such as receiving and sending of messages), and the management subsystem is responsible for registration and storage of telephone numbers with a smooth connection function and the like.

The first terminal and the second terminal may register before using the open connection application. It can be understood that if the first terminal and the second terminal have the smooth connection application when leaving the factory, the first terminal and the second terminal can be directly registered, and if the first terminal and the second terminal do not have the smooth connection application when leaving the factory, the first terminal can download and install the smooth connection application, and then register the smooth connection application.

For example, please refer to fig. 2B, wherein steps S101 to S103 are performed to register a flow of the connection-disconnected application for the first terminal and the second terminal. Specifically, the process includes:

s101, a first terminal and a second terminal send registration requests to a management subsystem in smooth connection cloud service; specifically, S101 includes S101a and S101 b. S101a, the first terminal sends a first registration request to the smooth cloud service, where the first registration request carries a first number of the first terminal. And S101b, the second terminal sends a second registration request to the smooth connection cloud service, wherein the second registration request carries a second number of the second terminal. The execution order between S201a and S201b is not limited.

And S102, registering a management subsystem in the smooth connection cloud service, namely recording that the first number and the second number register the smooth connection application.

And S103, the management subsystem in the smooth connection cloud service sends registration feedback to the first terminal and the second terminal, wherein the registration feedback is used for indicating whether the registration is successful or not. Specifically, S103 includes S103a and S103 b. And S103a, the smooth connection cloud service sends registration feedback to the first terminal, and S103b, the smooth connection cloud service sends registration feedback to the second terminal. The execution order between S103a and S103b is not limited. S103a and S103b are optional steps, which may or may not be executed, and are indicated by dotted lines in the figure, if not executed, the smooth cloud service does not need to perform registration feedback to the registered user.

The above description is given by taking the registration of the smooth connection application by the first terminal and the second terminal as an example, and it can be understood that more terminal devices can register the smooth connection application, and the registration principle is the same, so that a large number of telephone numbers in which the smooth connection application is registered can be stored in the smooth connection cloud service.

After the first terminal and the second terminal register the smooth connection application, the smooth connection application in the first terminal may discover the smooth connection function of the second terminal, and the smooth connection application in the second terminal may also discover the smooth connection function of the first terminal. For example, with continued reference to fig. 2B, the process of the first terminal finding the connection-free capability of the second terminal may be steps S104 to S106. Specifically, the process includes:

and S104, the first terminal sends a smooth connection inquiry request to a management subsystem in the smooth connection cloud service, wherein the smooth connection inquiry request carries an inquired number, namely a second number, and is used for requesting to inquire whether the second number is registered or not.

And S105, the management subsystem in the smooth connection cloud service determines whether the second number is registered for smooth connection.

And S106, the management subsystem in the smooth connection cloud service sends a query result to the first terminal, wherein the query result is used for indicating whether the second number is registered smoothly.

After the smooth connection application in the first terminal inquires that the second terminal registers the smooth connection, the smooth connection application can be labeled in a certain mode. For example, when the address book of the first terminal includes the second number of the second terminal, the address book may be labeled. For example, please refer to fig. 2C (a), which is a schematic diagram of an address book of a first terminal, the address book includes a second user john, and a smooth connection video tag 201 and a smooth connection voice tag 202 are displayed for indicating that a smooth connection application has been opened by the second user, the first terminal may implement a video call with the second user through the smooth connection video tag 201, and implement a voice call with the second user through the smooth connection voice tag 202. That is, the first terminal may find out that the contacts of the smooth connection application are registered in all the numbers in the address book. For example, the first terminal reports the numbers of all contacts in the address book to the smooth connection cloud service, and since all mobile phone numbers of registered smooth connection applications are stored in the smooth connection cloud service, the smooth connection cloud service can judge which contacts in the address book of the first terminal have their mobile phone numbers registered with the smooth connection applications, and notify the first terminal of the contacts registered with the smooth connection applications. The first terminal can mark the contacts registered in the contact list and used for smooth connection in a certain mode.

After the first terminal finds that the second terminal registers the smooth connection, the first terminal can send a message to a smooth connection application in the second terminal through the smooth connection application. For example, with continued reference to fig. 2B, the flow of the first terminal sending the clear link message to the second terminal may be steps S107 to S112. Specifically, the process includes:

s107, the first terminal detects the operation of sending the connection opening message to the second user.

Before S107, the method may further include the steps of: and the first terminal opens an open connection chat conversation interface with the second user and sends an open connection message to the second user in the chat opposite interface. One way is that the first terminal opens a chat counterpart interface with the second user in the address book. With continued reference to fig. 2C (a), when the first terminal detects an operation (such as a click operation) for contact john, an interface as shown in fig. 2C (b) is displayed, and the interface includes a clear connection video tag 201, a clear connection voice tag 202, and a clear connection message tag 203. When the first terminal detects an operation with respect to the smooth message mark 203, an interface as shown in (C) of fig. 2C is displayed, which may be understood as a smooth chat conversation interface of the first user of the first terminal with the second user (i.e., john), in which a picture, a voice message, a location, an emoticon, and so on may be transmitted to the second user. For example, the operation in S107 may include an operation of inputting text information in an input box and then clicking a "send" button; or an operation of selecting and transmitting a picture, and the like.

And S108, the first terminal sends a smooth connection message to a message subsystem in the smooth connection cloud service, wherein the smooth connection message carries the opposite party number, namely the second number, and also carries the specific content of the message sent to the second user. For example, it may be text content, pictures, or position information, etc.

Because the smooth connection message carries the second number, the smooth connection cloud service can inquire whether the second number is registered for the smooth connection cloud service or not, and the smooth connection message is prevented from being sent to the phone number which is not registered for the smooth connection. Optionally, the smooth connection message may further carry a first number of the first terminal, so that the smooth connection cloud service may also query whether the first number is registered for the smooth connection application, and avoid receiving a message from a non-registered user. Specifically, the process of inquiring whether the number registers the smooth connection application may be implemented by the following steps S209 to S211.

And S109, the message subsystem sends a query request to the management subsystem, wherein the query request carries the second number. Optionally, if the first number is carried in the connect-disconnect message, the query request may also carry the first number.

S110, the management subsystem in the smooth connection cloud service inquires whether the second number is registered smoothly. Optionally, if the query request carries the first number, the management subsystem may further query whether the first number is registered for a clear connection.

The management subsystem records all mobile phone numbers registered with the smooth connection application, so that the management subsystem determines whether a second number exists in all the recorded mobile phone numbers, and if so, determines that the second number is registered with the smooth connection application. In this way, sending clear messages to telephone numbers that do not register for a clear connect application is avoided. Optionally, the query request may also carry a first number. In this way, whether the first number of the first terminal is registered for the smooth connection application can be further inquired, the smooth connection message can be initiated only when the smooth connection telephone number is registered, and the safety is improved.

And S111, the management subsystem sends the query result to the call subsystem.

The query result may be that the second number is registered for the smooth connection application or that the second number is not registered for the smooth connection application. Optionally, if the query request further includes the first number, the query result may further include that the first number is registered or unregistered with the clear connection application. Optionally, S209 to S211 may or may not be executed, and this embodiment of the present application is not limited, so the diagram uses a dashed line to indicate. S212 may be performed when the query result indicates that the second number is registered for the open connection application.

And S112, the conversation subsystem sends a connection opening message to the second terminal.

When receiving the smooth message, the second terminal may display a display interface as shown in (d) in fig. 2C, where the interface is a smooth chat conversation interface between the second user and the first user on the second terminal, and the interface includes the smooth message sent by the first user, such as text information, a picture, a geographical location, and the like.

The foregoing embodiment describes a process in which the first terminal sends the clear connection message to the clear connection application in the second terminal through the clear connection application, and it should be noted that the clear connection message is based on the clear connection protocol, and the following briefly describes the clear connection protocol.

The fluent protocol may be a text protocol based on a binary compiled language, but does not limit the binary of the compiled language, and may also be decimal, and so on. The clear link Protocol may be carried in a Transmission Control Protocol (TCP), for example, see table 1 below, which is an example of a format of the clear link Protocol.

TABLE 1

As shown in table 1 above, the connectionless protocol includes a protocol header, a service header, and service data. The protocol header mainly carries protocol information, the service header mainly carries information related to a service, and the service data carries specific service data, for example, specific contents of the connection information sent from the first user to the second user, such as text information, pictures, geographical positions, and the like. The protocol header, the service header and the service data are introduced as follows:

the protocol header includes: message length (BodyLength), Version (Version), service type (ServiceType), Control field (Control), trace id (traceid).

Body length: the device is used for indicating that the length is calculated from version, comprises a part of protocol header, and also comprises a total length of a service header and service data; the total length can be understood as the total number of bytes occupied.

Version: indicating a protocol version number, indicating the version of the current protocol, such as tandem version 1.0, tandem version 2.0, etc.

ServiceType: for indicating the type of service, which may also be referred to as a traffic type, e.g., call signaling, message signaling, etc. Wherein, the call signaling is used for indicating that the current service is a smooth connection voice or video call, and the message signaling is used for indicating that the current service is the receiving and sending of a smooth connection message.

Control: for indicating the control field. For example, each field is limited to a certain number of bits, so that excessive consumption of traffic due to too many bits is avoided.

TraceId: and the tracking ID is used for indicating the tracking ID and is used for message tracking at the terminal side and the smooth cloud service side.

The service head comprises: MsgType, MsgHeaderLength, MsgHeader, MsgBody.

Msgtype: for indicating the sub-message type corresponding to the ServiceType, if the ServiceType is message signaling, the MsgType includes, for example, message sending, message receipt, etc., where the message receipt includes, for example, message read, message unread, counterpart is inputting, etc.

MsgHeaderLength: for indicating the service header length of the sub-message type.

MsgHeader: a service header part of a sub-message type, and if the MsgType is message sending, the MsgHeader is used to indicate the format of a specific sent message, such as a picture format, a text format, a geographical location format, and the like. Taking the picture format as an example, the MsgHeader may further include information of resolution, pixels, and the like of the picture.

The service data comprises: MsgBody.

MsgBody: service data of a sub-message type; indicating the particular transmitted message content such as the transmitted text content, picture content, geographic location, etc.

In the above embodiment, the first terminal and the second terminal perform the smooth connection registration by using the mobile phone number as an example, so the first registration request and the second registration request in S201 in fig. 2B only include the mobile phone number. Optionally, in addition to using only the mobile phone number for registration, the first terminal and the second terminal may also use the mobile phone number, the device identifier, and/or the hua as a system account for registration. The device identification may be the model, type (cell phone, television, etc.) of the device, etc.

Take the example of using the mobile phone number, the system account number and the device identifier to register together. Suppose that the mobile phone number of the first terminal is a first number, the system account is a first account, the mobile phone number of the second terminal is a second number, and the system account is a second account. The registration process of the first terminal may be that the first terminal sends a first registration request to the smooth cloud service, where the first registration request carries a first number, a first account, and a device identifier of the first terminal. The registration process of the second terminal may be that the second terminal sends a second registration request to the smooth cloud service, where the second registration request carries a second number, a second account, and a device identifier of the second terminal. Therefore, the smooth cloud service can register after receiving registration requests from the first terminal and the second terminal. For example, the correspondence between the mobile phone number, the system account, and the device identifier may be stored. For example, see table 2 below for an example of the correspondence:

TABLE 2

Mobile phone number	Device identification	System account
			First number	Huazhimate 30	First of allAccount number
Second number	Hua is P40	Second account number

Generally, one system account may be logged into different devices. For example, the first user includes a mobile phone and a television, and both of them log in using the first account. The number of the mobile phone is a first number, and the first number, the first account and the device type (namely, the mobile phone) can be used for registration. Similarly, the television may also register the smooth connection application using the first number and the first account number and the device type (i.e., the television). Considering that the SIM card is not installed in the television, the television may obtain the first number in a certain manner, for example, the user inputs the first number on the television, or the television displays the two-dimensional code, and the first user uses the mobile phone to scan the two-dimensional code to connect with the television and send the first number to the television. After the television acquires the first number, the television can register by using the first number, the first account and the equipment identifier. Namely, the television sends a registration request to the smooth cloud service, and the registration request carries a first number, a first account and a device identifier: hua is an intelligent screen X65. And when receiving a registration request from the television, the smooth connection cloud service performs registration. For example, see table 3:

TABLE 3

Mobile phone number	Device identification	System account
			First, aNumber(s)	Intelligent screen X65	First account number
Second number	Intelligent screen V55	Second account number

It is understood that the liberty cloud service can integrate the above tables 2 and 3, resulting in the following table 4:

TABLE 4

Since the device identifiers of different devices corresponding to the user (such as a mobile phone number) are stored in the smooth connection cloud service, when a smooth connection video/voice call is initiated to the user or a smooth connection message is sent to the user, the call can be initiated to the television of the opposite side, or the call can be initiated to the mobile phone of the opposite side.

Therefore, the smooth connection cloud service can realize interconnection and intercommunication among full scene equipment. For example, referring to fig. 2D, the full-scene device refers to a general name of various types of devices, such as a mobile phone, a sound box, or a smart screen such as a tablet computer, a PC, and a television, and further includes wearable devices such as a watch, a bracelet, an earphone, and glasses. Through the smooth connection cloud service, the full scene devices can communicate with each other, for example, between a mobile phone and a television, between the mobile phone and a vehicle machine, between the mobile phone and a watch, and the like.

However, there is a limitation to the open connection application, for example, when two terminals use open connection interconnection messages or perform open connection voice or video calls, the two terminals must be required to register the open connection application on both terminals, and the method is not suitable for terminals that do not install the open connection application or do not register the open connection application.

Two, RCS applications

The RCS application is an application which adds a 5G message function on the basis of the traditional short message application, and in brief, is an application obtained by upgrading the traditional short message application. Generally, a traditional sms application can send and receive text and pictures (i.e., mms). Compared with the traditional short message application, the RCS application can support various rich media messages (also called 5G messages or RCS messages) such as user graphics, expressions, audio/video, group chat, positions and files, and the like, and is expanded to more service types.

Before introducing a communication system supporting RCS applications, an IP Multimedia Subsystem (IMS) and rich media services (RCS), RCS Hub are introduced.

The IMS is responsible for network access of a terminal, which may be a mobile terminal, a fixed telephone terminal, a multimedia terminal, a PC, etc., and the access method is not limited to a cellular radio interface, and may be a wireless WCDMA, or a wired LAN, xDSL, etc. The aim of IMS is to enable terminals of various types to establish an IP connection through which the terminals can communicate information with each other. The number of the IMS is more than one, for example, the IMS corresponding to different operators is different, for example, the IMS corresponding to telecom corresponds to IMS1, and communicates with the corresponding IMS2 and the corresponding IMS 3.

The RCS integrates communication services such as voice, message and location service, and is used for enriching the customer experience of native applications of mobile phone systems such as conversation, short message and contact person. The number of the RCSs is more than one, for example, the RCSs corresponding to different operators are different, for example, the RCSs corresponding to telecom correspond to the RCSs 1, the RCSs corresponding to Unicom correspond to the RCSs 2, and the RCSs corresponding to Mobile 3. Then the telecommunications corresponding RCS1 provides communication service for the telecommunications code, the telecommunications corresponding RCS2 provides communication service for the unicom number, and the mobile corresponding RCS3 provides communication service for the mobile number.

The RCS Hub is a higher-level server provided above the RCS for managing the respective RCSs, such as the above-described RCS1 through RCS 3.

Fig. 3A shows a schematic diagram of a communication system supporting RCS applications. The system comprises a first terminal, a second terminal, an IMS1, an IMS2, an RCS1, an RCS2 and an RCS Hub. The first terminal is in the jurisdiction of the IMS1, that is, the first terminal accesses the network through the IMS1, and the IMS1 is in the range of the RCS1, and when receiving an RCS message from a terminal in its jurisdiction, the IMS1 sends the RCS message to the RCS1 for processing. The second terminal is in the jurisdiction of the IMS2, that is, the second terminal accesses the network through the IMS2, and the IMS2 is in the range of the RCS2, and when receiving an RCS message from a terminal in its jurisdiction, the IMS2 sends the RCS message to the RCS2 for processing. The RCS Hub is responsible for managing RCS1 and RCS 2.

The first terminal and the second terminal may activate the RCS function before using the RCS application. For example, please refer to fig. 3B for a flow of turning on RCS for the first terminal and the second terminal. The process comprises the following steps:

s201, the first terminal sends a first provisioning request to the IMS1, where the first provisioning request carries a first number of the first terminal.

Optionally, the RCS service is preconfigured in the SIM card, that is, the SIM card is an SIM card supporting RCS, so that when the SIM card is inserted into the first terminal, the first provisioning request may be sent to complete provisioning; or when the SIM card is inserted into the first terminal, providing an opening key in the first terminal, and when detecting that the user triggers the opening key, sending a first opening request to finish the opening.

S202, the IMS1 sends a first provisioning request to the RCS 1.

S203, the RCS1 registers, i.e., records, the first number.

S204, the RCS1 sends the first number to the RCS Hub.

S205, the RCS Hub registers, i.e., records the first number.

The principle of the process of the second terminal for opening the RCS is the same as that of the first terminal for opening the RCS, and the method specifically includes the following steps:

s206, the second terminal sends a second provisioning request to the IMS2, where the second provisioning request carries a second number of the second terminal.

S207, the IMS2 sends a second provisioning request to the RCS 2.

S208, the RCS2 registers, i.e., records, the second number.

S209, the RCS2 sends the second number to the RCS Hub.

S210, the RCS Hub registers, i.e., records the second number.

If the first number of the first terminal and the second number of the second terminal do not belong to the same operator, the IMS1 and the IMS2 are not the same IMS, and the RCS1 and the RCS2 are not the same RCS. If the first number of the first terminal and the second number of the second terminal belong to the same operator, the IMS1 and the IMS2 may be the same IMS, and the RCS1 and the RCS2 may be the same RCS. That is, all telephone numbers stored in the RCS1 belong to the same carrier, and all telephone numbers stored in the RCS2 belong to another carrier. However, all the numbers of the RCS1 and the RCS2 are registered at the RCS Hub, that is, the phone numbers registered in each RCS are stored in the RCS Hub. For example, referring to table 5 below, a number of telephone numbers are stored in the RCS Hub, along with the RCS from which each telephone number came.

TABLE 5

The above is the process of the first terminal and the second terminal opening the RCS, and the principle is the same for the process of other terminals opening the RCS.

After the first terminal and the second terminal turn on the RCS, the first terminal may discover the RCS function of the second terminal, and the second terminal may also discover the RCS function of the first terminal. Taking the RCS function of the first terminal discovering the second terminal as an example, see fig. 3C, which is a schematic flow diagram illustrating the RCS function of the second terminal discovering the RCS application in the first terminal. As shown in fig. 3C, the process includes:

s301, the first terminal and the second terminal turn on RCS. Specifically, S301 includes S301a and S301 b.

S302, the first terminal sends an RCS capability query request to the IMS1, where the RCS capability query request carries the first number and the second number, and is used to request to query whether the second number turns on the RCS.

S303, the IMS1 sends an RCS capability query request to the RCS 1.

S304, the RCS1 determines whether the first number and the second number belong to the same operator. If yes, the PCS1 is used for locally inquiring whether the second number exists, if yes, the second number is determined to open the RCS, otherwise, the second number is determined not to open the RCS. If the first number and the second number are not the same carrier, S305 is entered.

As described above, if the first number and the second number are of the same operator, both the first number and the second number open services to the RCS1, so the first number and the second number exist in the RCS 1. If the first number and the second number are not the same operator, the second number is not present in the RCS1, and then it can be queried by means of the RCS Hub whether the second number turns on the RCS.

S305, the RCS1 sends an RCS capability query request to the RCS Hub.

S306, the RCS Hub sends the query result to the RCS 1.

As described above, the RCS Hub stores the mobile phone numbers from all RCSs, and when the second number is included, it is determined that the second number has the RCS enabled, otherwise, it is determined that the second number has no RCS enabled.

S307, the RCS1 sends the query result to the IMS 1.

S308, the IMS1 sends the query result to the first terminal.

When the first terminal queries that the second terminal has the RCS function, the second terminal may be labeled in a certain manner, for example, when the address book of the first terminal stores the second number of the second terminal, the second terminal may be labeled in the address book. For example, referring to fig. 3D (a), a second user, such as john, is displayed in the address book of the first terminal, and an RCS video tag 301, an RCS voice tag 302, and an RCS message tag 303 are also displayed to indicate that the second user, john, has RCS activated. Optionally, the first terminal may discover a contact opening the RCS in the address book.

Thus, the first terminal may report the address book to the RCS1 (e.g., send the address book to the RCS1 via the IMS 1), and the RCS1 reports the address book to the RCS Hub. The RCS Hub knows all the mobile phone numbers for opening the RCS, and can judge which contact mobile phone numbers in the address list of the first terminal open the RCS and inform the first terminal. The first terminal can mark the contact with the RCS opened in the address book in a certain way.

And when the first terminal inquires that the second terminal opens the RCS, the first terminal can carry out RCS communication with the second terminal. The RCS communication may include RCS video/voice communication, or RCS messaging. The following description mainly takes mutual sending of RCS messages as an example. Referring to fig. 3E, a schematic flow chart of the first terminal sending the RCS message to the second terminal is shown. As shown, the process includes:

s401, the first terminal detects an operation for sending an RCS message to the second number.

Before S401, the method may further include: and the first terminal opens an RCS chat conversation interface with the second user and sends an RCS message to the second user in the RCS chat counterpart interface. For example, with continued reference to (a) in fig. 3D, when the first terminal detects an operation for contact john, an interface as shown in (b) in fig. 3D is displayed, which may be understood as an RCS chat conversation interface with the second number, john, including a picture sending option, a voice messaging option, a video call option, and the like for selection by the user. I.e., a first user of a first terminal may send various RCS messages to a second user. For example, the operation in S401 may include an operation of inputting text information in an input box and then clicking a "send" button; or an operation of selecting and transmitting a picture, and the like.

S402, the first terminal sends an RCS message to the IMS1, where the RCS message includes a second number, and the RCS message includes specific content of the message sent by the first terminal, such as text information, a picture, a geographical location, and the like. Optionally, the RCS message may also carry a first number.

S403, the IMS1 sends an RCS message to the RCS 1.

S404, the RCS1 sends an RCS message to the RCS Hub.

Optionally, before S404, the RCS1 may determine whether the first number and the second number are in the same operator, and if so, the RCS1 may directly send the RCS message to the second terminal, because the RCS1 is responsible for the terminal of the same operator, and if the first number of the first terminal and the second number of the second terminal are in agreement with the operator, the first terminal and the second terminal are both open to the RCS 1. Therefore, the RCS1 may directly transmit the RCS message to the second terminal. If the RCS1 determines that the first number and the second number do not belong to the same operator, the RCS1 cannot directly transmit the RCS message to the second terminal, may transmit the RCS message to the second terminal through the RCS Hub, and the process of transmitting the RCS message to the second terminal through the RCS Hub is implemented through the following steps.

S405, the RCS Hub determines that the RCS corresponding to the second number is RCS 2.

For example, referring to table 5 above, the RCS Hub stores the mobile phone numbers that are provisioned for the RCS of different carriers. Therefore, the RCS Hub can determine the RCS corresponding to the second number, such as RCS2, according to table 5 above.

S406, the RCS Hub sends an RCS message to the RCS 2.

S407, the RCS2 sends an RCS message to the IMS 2.

S408, the IMS2 sends an RCS message to the second terminal. Since the RCS message carries the second number of the second terminal, the IMS2 may send the RCS message to the second terminal based on the second number.

For example, referring to (c) of fig. 3D, the RCS message sent by the first user (i.e., the grand satellite) is displayed on the second terminal.

In the above embodiment, the process of the first terminal sending the RCS message to the second terminal through the RCS application is described, and when it needs to be described, the sending of the RCS message needs to be processed by using the RCS protocol. The RCS protocol is briefly described below.

The RCS protocol is defined by GSMA, is carried by UDP or TCP, belongs to SIP protocol, and has large message body, large flow consumption and excessive interaction flow. See, for example, table 6 below, which is an example of one format of the RCS protocol.

TABLE 6

The format of the SIP message body includes:

message-header

CRLF (enter and shift)

message-body

The message-header includes RCS protocol information, such as conversion-ID (randomly generated character string) and the like, and the message-body includes a sender number, a receiver number, specific content of the sent information and the like.

Because the RCS application is added with the 5G function on the basis of the traditional short message application, generally speaking, the traditional short message application exists on each terminal device, for example, the short message application is installed regardless of the manufacturer and model of the mobile phone, so the RCS application exists on each terminal, and a user can not worry about the situation that the RCS application is not installed, in other words, the RCS application has a large number of potential user groups. However, the RCS application also has certain limitations, for example, the carrier is still a mobile phone, and cannot be extended to any device, such as a television without a SIM card, a tablet computer, a PC, and other devices.

The Huacheng Changjun application and the RCS application are introduced above, and have both advantages and disadvantages. Currently, a smooth connection application and an RCS application cannot be intercommunicated, for example, a smooth connection application on one terminal can only be intercommunicated with a smooth connection application on another terminal, or an RCS application on one terminal can only be intercommunicated with an RCS application on another terminal, and a smooth connection application on one device cannot be intercommunicated with an RCS application on another device. The cross-application intercommunication method between different devices provided by the embodiment of the application can realize the communication between the smooth connection application on one terminal and the RCS application on the other terminal.

For convenience of description, the RCS application is activated by the first terminal, and the second terminal registers the smooth connection application as an example. Fig. 4 is a schematic diagram of a communication system of a cross-application interconnection method between different devices according to an embodiment of the present application. As shown in fig. 4, the system includes a first terminal and a second terminal. The first terminal comprises RCS application. The system also comprises an IMS which is responsible for managing the first terminal, an RCS which is responsible for managing the IMS, and an RCS Hub which is responsible for managing and controlling the RCS. The information interaction process between the RCS application in the first terminal and the IMS and the RCS Hub of the RCS may be as shown in fig. 3B or fig. 3C, and is not repeated here. The second terminal is installed with a smooth connection application. The system further comprises a smooth connection cloud service which is responsible for communication with a smooth connection application in the second terminal. The information interaction process between the second terminal and the smooth connection cloud service may be as shown in fig. 2B, and is not repeated herein.

The system further includes a smooth connection-RCS convergence gateway (the name is merely an example, and other names may also be used), which connects the RCS Hub and the smooth connection cloud service, and may implement conversion between a smooth connection protocol and an RCS protocol, so as to implement intercommunication between an RCS application in the first terminal and a smooth connection application in the second terminal.

Comparing the communication system corresponding to the smooth connection application shown in fig. 2A and the communication system shown in fig. 4, compared to the communication system shown in fig. 2A, the communication system shown in fig. 4 does not only include the smooth connection cloud service, and the smooth connection-RCS convergence gateway and the IMS, RCS, and RCS Hub supporting the RCS application are added. Comparing the communication system corresponding to the RCS application shown in fig. 3A with the communication system shown in fig. 4, compared to the communication system shown in fig. 3A, the communication system shown in fig. 4 does not only include IMS, RCS, and RCS Hub, and a smooth connection-RCS convergence gateway and a smooth connection cloud service are added. Namely, the connection between the RCS Hub and the smooth connection cloud service is realized through the smooth connection-RCS convergence gateway, and further, the intercommunication between the RCS application in the first terminal and the smooth connection application in the second terminal is realized.

The following embodiments are described with reference to the architecture shown in fig. 4.

Specifically, the first embodiment and the second embodiment are included, and the first embodiment is a communication process between an RCS application in a first terminal and a connectionless application in a second terminal. Embodiment two is a procedure of communication between the connectionless application in the second terminal and the RSC application in the first terminal.

Example one

In this embodiment, a process in which the first terminal initiates communication to the smooth connection application in the second terminal through the RCS application is described as an example in which the first terminal includes the RCS application and the second terminal includes the smooth connection application. The communication includes a smooth connection video/voice call, and also includes sending a smooth connection message, and this embodiment is mainly described by taking sending a smooth connection message as an example.

In this embodiment, the RCS application in the first terminal may find whether the second terminal is registered for a clear connection, and if so, may communicate with the clear connection application in the second terminal through the RCS application. Specifically, the RCS application in the first terminal finds the procedure of the connect/disconnect function of the second terminal, see fig. 5A to 5C. The process of the first terminal communicating with the connect-now application in the second terminal through the RCS application is illustrated in fig. 6A to 7.

Please refer to fig. 5A, which is a flowchart illustrating a procedure for discovering an open connection function of a second terminal for an RCS application in a first terminal. As shown in fig. 5A, the process includes:

and S500, the second terminal registers the smooth connection application. The process of registering the smooth connection application by the second terminal is described in the foregoing description of the smooth connection application, and is not repeated here.

S501, the first terminal switches on the RCS. The process of turning on the RCS by the first terminal is described in the foregoing description of the RCS application, and is not repeated here.

The execution order of S500 and S501 is not limited.

S502, the first terminal sends an RCS capability query request to the IMS, wherein the RCS capability query request carries a second number of the second terminal. The RCS capability query request is for requesting query of the RCS capability of the second number (i.e., whether the RCS is turned on). The RCS capability query request is encapsulated using the RCS protocol.

Optionally, the first terminal may send the RCS capability query request immediately after the RCS is activated, where the RCS capability query request may carry all numbers in the address book of the first terminal, that is, the first terminal immediately queries a contact with RCS capability in all numbers in the address book after the RCS is activated. Or, when detecting the operation for triggering the query of the RCS capability of the second user, the first terminal sends the RCS capability query request. The operation of the user triggering and querying the RCS capability of the second user may be, for example, an operation of opening an RCS chat conversation interface with the second user, that is, when the first terminal detects that the RCS chat conversation interface with the second user is opened, the RCS capability query request is sent.

S503, the IMS sends an RCS capability query request to the RCS.

S504, the RCS sends an RCS capability inquiry request to the RCS Hub.

For ease of understanding, a comparison may be made with the procedure described above in fig. 3E in which the RCS application in the first terminal queries the RCS capabilities of the second terminal. In fig. 3E, when receiving the RCS capability query request, and when the first number and the second number are different operators, the RCS sends the RCS capability query request to the RCS Hub to query whether the second number turns on the RCS, and when the first number and the second number are the same operator, the RCS capability query request does not need to be sent to the RCS Hub, and the RCS can query locally. However, in fig. 5A, when receiving the RCS capability query request, the RCS default to send the RCS capability query request to the RCS Hub, which is not only to query whether the second number opens the RCS, but also to query whether the second number registers the clear connection. That is, the RCS does not need to determine whether the first number and the second number belong to the same operator, and the RCS capability query request is sent to the RCS Hub by default, so that the RCS is relieved.

And S505, the RCS Hub sends an RCS capability inquiry request to the smooth connection-RCS fusion gateway.

Continuing with the previous fig. 3E comparison. In fig. 3E, when receiving the RCS capability query request, the RCS Hub determines whether the second number turns on the RCS and feeds back the query result. In fig. 5A, the RCS Hub not only needs to determine whether the second number opens the RCS and feed back the result, but also needs to send an RCS capability query request to the smooth connection-RCS convergence gateway to query whether the second number registers the smooth connection.

The easy connect-RCS convergence gateway may provide a first capability query interface. The first capability query interface is used for receiving an RCS capability query request.

S506, the smooth connection-RCS fusion gateway makes a protocol conversion for the RCS capability query request into a smooth connection protocol to obtain the smooth connection query request.

Because the RCS capability query request from the RCS Hub received by the tandem-RCS convergence gateway is encapsulated using the RCS protocol, if the tandem query request needs to be sent to the tandem cloud service, the RCS capability query request needs to be protocol-converted to the tandem protocol. The introduction of the clear link protocol and the RCS protocol is referred to the previous sections and will not be repeated here.

And S507, the smooth connection-RCS fusion gateway sends the smooth connection query request to the smooth connection cloud service.

S508, the smooth connection cloud service inquires whether the second number is registered for smooth connection application or not, and a first inquiry result is obtained.

And S509, the smooth connection cloud service sends a first query result to the smooth connection-RCS fusion gateway, and the first query result is packaged by using a smooth connection protocol.

And S510, the smooth connection-RCS convergence gateway performs protocol conversion on the first query result so as to convert the first query result into an RCS protocol.

Since the first query result from the clear link cloud service received by the clear link-RCS convergence gateway is encapsulated by using the clear link protocol, if the first query result needs to be sent to the RCS Hub, the first query result needs to be subjected to protocol conversion so as to be converted into the RCS protocol.

And S511, the smooth connection-RCS fusion gateway sends the first query result after the protocol conversion to the RCS Hub.

And S512, the RCS Hub inquires whether the second number opens the RCS or not to obtain a second inquiry result.

S513, the RCS Hub sends the third query result to the RCS. The third query result includes the first query result and the second query result.

And S514, the RCS sends the third query result to the IMS.

S515, the IMS sends the third query result to the first terminal.

In the above embodiment, the first query result and the second query result are sent to the first terminal together. Optionally, the first query result and the second query result may be sent separately. For example, after S504, the RCS Hub immediately performs S512, that is, queries whether the second number opens the RCS, and feeds back the second query result to the first terminal, so that S512 does not need to be performed after S511, and only the first query result is sent in S513 to S515.

The first terminal may perform the marking when determining that the second number is registered for the smooth connection application. For example, the first terminal may be marked in an RCS chat conversation interface with the second number. Referring to fig. 5B, the RCS chat conversation interface between the RCS application of the first terminal and the second user (john) includes a connect token 501 in the RCS chat conversation interface, for indicating that the second user (john) has registered a connect application. Optionally, the display position and the display style of the open connection mark 501 in the RCS chat conversation interface with the second number are not limited (for example, may be a bubble). For convenience of understanding, the foregoing fig. 3D (B) may be compared with fig. 5B, and the RCS application in fig. 3D (B) cannot find the open connection function of the chat counterpart, so the open connection mark is not displayed in the chat interface. However, in this embodiment, the RCS application in the first terminal may discover the open connection capability of the chat partner, and display an open connection mark in the chat interface. Continuing with the example of the interface shown in FIG. 5B, the easy connect flag 501 may cause switching between the easy connect mode and the RCS mode. For example, in a case where the open connection flag 501 is selected (for example, the open connection flag 501 displays a first color or a first brightness), the text information, the sent voice message, the picture, the geographical location, and the like, which are input by the user in the input box, are all the open connection messages sent to the opposite open connection application. That is, in the case where the clear connection flag 501 is selected, the RCS application of the first terminal communicates with the clear connection application in the second terminal. In a case where the clear connection flag 501 is not selected (for example, the clear connection flag 501 displays a second color or a second brightness), the text information, the transmitted voice message, the picture, the geographical location, and the like, which are input by the user in the input box, are all the clear connection messages transmitted to the RCS application of the opposite party. That is, in the case where the clear connection flag 501 is not selected, the RCS application of the first terminal communicates with the RCS application in the second terminal.

In addition to marking in the RCS chat conversation interface with the second user (i.e., john), the second user may be marked in the contact book that the second user registered for the clear connect application. For example, please refer to fig. 5C, which is a schematic diagram of an address book of the first terminal, where the address book includes contacts with phone numbers stored in the first terminal, such as john, tom, and the like. Assuming that john opens the easy connect function, the contact person john is shown with an easy connect tab 502 corresponding to john on the contact list interface, indicating that john has opened the easy connect function. Assuming tom does not open the clear to connect application, then the contact tom does not display the clear to connect flag. When the first terminal detects an operation for clicking the open connection mark 502, an interface as shown in fig. 5B may be displayed, and the open connection mark 501 in the interface is selected.

The following describes a procedure in which the RCS application of the first terminal sends an open connection message to the second terminal.

Referring to fig. 6A, a schematic flow chart of an RSC application in a first terminal sending an open connection message to a second terminal is shown. As shown in fig. 6A, the process includes:

s600, the first terminal responds to the operation and opens an RCS chat conversation interface between the RCS application and the second user.

For example, the RCS chat conversation interface with the second user may be an interface as shown in FIG. 5B, including a connect tab 501 for indicating that the second user has registered a connect application.

S601, the first terminal sets a smooth connection message mode. For example, in the interface shown in fig. 5B, when the clear link flag 501 is selected, the clear link message mode is set.

S602, the first terminal detects an operation for sending a message to the second user.

For example, continuing with the interface shown in fig. 5B as an example, the operation may be an operation in which the user enters text information in the input box and then clicks the send button. Since the smooth connection flag 501 is selected, i.e., the user wants to send a smooth connection message to the second user. Therefore, in order to conveniently identify that the message sent by the first terminal needs to be sent to the smooth connection cloud service, the message may carry a smooth connection mark for identifying that the message needs to be sent to the smooth connection cloud service, and the message is encapsulated by using an RCS protocol.

S603, the first terminal sends a message to the IMS, wherein the message carries the second number of the second user, the specific content of the sent message and the smooth connection mark.

S604, the IMS sends a message to the RCS.

And S605, the RCS determines that the message needs to be sent to the smooth connection cloud service according to the smooth connection mark carried in the message. The RCS transmits the message to the RCS Hub for transmission to the smooth cloud service through the RCS Hub.

S606, the RCS sends the message to the RCS Hub.

And S607, the RCS Hub determines that the message needs to be sent to the smooth connection cloud service according to the smooth connection mark carried in the message. Therefore, the RCS Hub sends the message to the smooth connection-RCS convergence gateway to send to the smooth connection cloud service through the smooth connection-RCS convergence gateway.

And S608, the RCS Hub sends the message to the smooth connection-RCS convergence gateway.

The clear-to-RCS convergence gateway may provide a first messaging interface. The first messaging interface is for receiving messages from the RCS Hub.

And S609, the smooth connection-RCS fusion gateway performs protocol conversion on the message to convert the message into a smooth connection protocol.

Because the message from the RCS Hub received by the smooth connection-RCS convergence gateway is encapsulated by using the RCS protocol, if the message needs to be sent to the smooth connection cloud service, the message needs to be protocol-converted to be converted into the smooth connection protocol. The introduction of the clear link protocol and the RCS protocol is referred to the previous sections and will not be repeated here.

And S610, the smooth connection-RCS fusion gateway sends the message subjected to the protocol conversion to the smooth connection cloud service.

And S611, the smooth connection cloud service sends a message to the second terminal.

And S612, the second terminal processes the information. The processing includes viewing, replying, and the like.

S613, the second terminal sends a receipt message to the first terminal. Specifically, S613 includes S613a to S613 g. The receipt message includes information that the other party has read, the other party has not read, the other party is inputting, etc. that characterizes the processing state of the other party to the message. For example, referring to fig. 6B, the receipt information "the other party has read" is displayed in the chat interface with the second user.

From the foregoing description of the smooth connection application, not only the phone number but also the system account and the device identifier may be registered in the smooth connection cloud service, such as table 4. Therefore, before S611 in fig. 6A, when the smooth connection cloud service receives a message from the first terminal, if it is determined that the number of the devices corresponding to the second number includes at least two, one device may be randomly selected and a message may be sent to the device; or, the device with the priority higher than the second number may also include a mobile phone and a television, when the priority of the mobile phone is higher than the priority of the television, the smooth cloud service sends a message to the mobile phone, and when the priority of the television is higher than the priority of the mobile phone, the smooth cloud service sends a message to the television. The priority relationship may be set by default or by a user, which is not limited in the embodiment of the present application.

In the above manner, the first terminal does not need to know which devices correspond to the second number, and when the smooth connection cloud service receives the message from the first terminal and determines the receiving end of the message, that is, multiple devices corresponding to the second number, the first terminal determines a device randomly or based on a priority relationship and then sends the message to the device. In the mode, the plurality of devices corresponding to the second user in the smooth connection cloud service cannot be exposed to the first terminal, and the security is high.

Certainly, the smooth connection cloud service may also send the device identifiers of the multiple devices corresponding to the second number to the first terminal. For example, in S508 in fig. 5A, when the smooth connection cloud service receives a smooth connection query request from the RCS Hub and determines that a number to be queried in the smooth connection query request is multiple devices corresponding to a second number, the device identifiers of the multiple devices may be sent to the RCS Hub, so as to send the multiple device identifiers corresponding to the second number to the first terminal through the RCS Hub. That is, the first terminal may query whether the second user has registered the clear connection application, and if so, may also query a plurality of devices for which the second user has registered the clear connection application. The correspondence stored in the smooth cloud service is the correspondence shown in table 4 above. When the smooth connection cloud service receives the smooth connection query request, it is determined that the devices corresponding to the second number in the smooth connection query request comprise Huaqi mobile phones and Huaqi smart screens, and then the two device identifications are sent to the first terminal.

In this way, the device identifiers of the multiple devices corresponding to the second number may be displayed on the first terminal. For example, referring to fig. 6c (a), a "happy connection" tab 601 is displayed in the RCS chat conversation interface with the second number. When the first terminal detects an operation (such as a long press operation) for the easy connection flag 601, device identifications of the devices of the other party are displayed: television identification and mobile phone identification. Assuming that the television set identification is selected, the text information entered by the user in the input box, the voice message sent, the picture, the geographical location, etc. are the clear connection messages sent to the television set of the other party. Assuming that the mobile phone identification is selected, the user enters text information, a voice message to be sent, a picture, a geographical location, etc. in the input box as a clear connection message to be sent to the mobile phone of the other party.

Assuming that the tv id is selected, the process of the first terminal sending a message to the counterpart tv may be as shown in fig. 7, and the process includes:

s700, the first terminal responds to the operation and opens an RCS chat conversation interface between the RCS application and the second user.

S701, the first terminal sets a smooth connection message mode. For example, in the interface shown in FIG. 5B, when clear link flag 501 is selected, the clear link extinction mode is set.

S702, the first terminal device detects that the television identifier is selected.

S703, the first terminal detects an operation for sending a message to the second user. The message comprises the transmitted content, a second number of a second user, a smooth connection mark and a television mark.

S704, the first terminal sends a message to the IMS.

S705, the IMS sends a message to the RCS.

S706, the RCS determines that the message needs to be sent to the smooth connection cloud service according to the smooth connection mark carried in the message.

S707, the RCS sends the message to the RCS Hub.

And S708, the RCS Hub determines that the message needs to be sent to the smooth connection cloud service according to the smooth connection mark carried in the message.

S709, the RCS Hub sends the message to the smooth connection-RCS fusion gateway.

And S710, the smooth connection-RCS fusion gateway performs protocol conversion on the message to convert the message into a smooth connection protocol.

And S711, the smooth connection-RCS fusion gateway sends the message subjected to the protocol conversion to the smooth connection cloud service.

And S712, the smooth connection cloud service determines that the message needs to be sent to the television of the second user according to the television identifier in the message.

S713, the smooth connection cloud service sends a message to the television of the second user.

And S714, the television of the second user processes the information.

S715, the television sends a receipt message to the first terminal. Specifically, S715 includes S715a to S715 g.

In this way, the first terminal can know that the second user has opened the smooth connection function, and optionally what the opposite smooth connection device is, the first user at the first terminal can select to send a smooth connection message to a certain device, and user experience is high.

Optionally, before the cloud service sends the device identifiers of the multiple devices corresponding to the second number to the first terminal, the cloud service may request confirmation of the second user, and send the multiple device identifiers corresponding to the second number to the first terminal under the condition that the second user agrees. For example, after receiving a smooth connection query request from a first terminal, the smooth connection cloud service sends a confirmation request to a second user, where the confirmation request is used to indicate whether to approve disclosure of multiple devices corresponding to the second user to the first user; and if the confirmation instruction is received, sending the plurality of equipment identifications to the first terminal.

Or the second user sets a white list in advance, and sends the white list to the smooth cloud service, wherein the white list comprises one or more telephone numbers and is used for indicating that the smooth cloud service can disclose a plurality of devices of the second user to the telephone numbers in the white list. In this way, after the smooth connection cloud service receives the smooth connection query request from the first terminal, if the first number of the first terminal is determined to be in the white list, the multiple device identifiers of the second user are sent to the first terminal, otherwise, the multiple devices of the second user are not disclosed to the first terminal.

Example two

The first embodiment describes a procedure for a connectionless application of a first terminal to communicate with an RCS application in a second terminal. The second embodiment describes a procedure in which the second terminal communicates with the RCS application in the first terminal through the open connection application.

In the second embodiment, the smooth connection application in the second terminal may find whether the RCS is turned on by the first terminal, and if so, may communicate with the RCS application in the first terminal through the smooth connection application. The process of discovering the RCS capability of the first terminal by the connectionless application in the second terminal is shown in fig. 8A to 8C. Fig. 9A to 9B show a procedure of the first terminal communicating with the RCS application in the first terminal through the open connection application.

Please refer to fig. 8A, which is a flowchart illustrating a procedure for discovering the RCS function of the first terminal for the smooth connection application in the second terminal. As shown in fig. 8A, the process includes:

and S800, the second terminal registers the smooth connection application. The process of registering the smooth connection application by the second terminal is described in the foregoing description of the smooth connection application, and is not repeated here.

And S801, the first terminal switches on the RCS. The process of turning on the RCS by the first terminal is described in the foregoing description of the RCS application, and is not repeated here.

The execution order of S800 and S801 is not limited.

S802, the second terminal sends a smooth connection inquiry request to the smooth connection cloud service. The smooth connection inquiry request comprises the inquired number, namely the first number. The clear connection inquiry request is used for inquiring whether the first number is opened with the clear connection function. The clear link query request is encapsulated using the clear link protocol.

And S803, the smooth connection cloud service sends an RCS query request to the smooth connection-RCS convergence gateway.

For convenience of understanding, please compare with the procedure of querying the smooth connection capability of the second terminal by the smooth connection application in the first terminal shown in fig. 2B, when the smooth connection cloud service receives the smooth connection query request, the smooth connection cloud service feeds back the query result to the querying party, and does not need to forward the query result to the smooth connection-RCS convergence gateway. However, in fig. 8A, when the smooth connection cloud service receives the smooth connection query request, it is necessary to query whether the second number is registered for smooth connection (S810) and feed back a query result, and also to send the smooth connection query request to the smooth connection-RCS convergence gateway, so as to query whether the second number is provisioned for the RCS through the smooth connection-RCS convergence gateway.

The easy connect-RCS convergence gateway may provide a second capability query interface. The second capability query interface is used for receiving a clear link capability query request.

And S804, the smooth connection-RCS fusion gateway converts the smooth connection query request into an RCS protocol to obtain an RCS capacity query request. The RCS capability query request is encapsulated using the RCS protocol.

S805, the smooth connection-RCS fusion gateway sends the RCS capability query request to the RCS Hub.

S806, the RCS Hub inquires whether the first number turns on RCS.

S807, the RCS Hub sends a first query result to the smooth connection-RCS convergence gateway, wherein the first query result is used for indicating whether the first number opens the RCS or not. The first query result is encapsulated using the RCS protocol.

And S808, the smooth connection-RCS convergence gateway performs protocol conversion on the first query result so as to convert the first query result into a smooth connection protocol.

And S809, the smooth connection-RCS fusion gateway sends the first query result after the protocol conversion to the smooth connection cloud service.

S810, the smooth connection cloud service inquires whether the first number is registered to be smooth connection or not, and a second inquiry result is obtained.

And S811, the smooth connection cloud service sends a third query result to the second terminal, wherein the third query result comprises the first query result and the second query result.

In the above embodiment, the first query result and the second query result are sent to the second terminal together, and optionally, the first query result and the second query result may also be sent separately, for example, after S802, the RCS Hub immediately performs S810, that is, queries whether the second number is registered for a clear connection, and feeds back the second query result, then after S809, S810 does not need to be performed, and only the first query result is sent in S811.

And when the second terminal inquires that the first number opens the RCS, the second terminal can mark the first number. For example, the second terminal may mark in the address book or in the chat conversation interface with the first number.

For example, please refer to fig. 8B, which is a schematic diagram of the chat interface between the second terminal and the first user (i.e., the grand satellite). An RCS tab 801 may be displayed in the chat interface for instructing the first user to open an RCS. Optionally, the RCS tab 801 is not limited in display position and display style (e.g., may be a bubble) in the RCS chat conversation interface with the second number. For convenience of understanding, fig. 2C (d) may be compared with fig. 8B, and the RCS function of the chat partner cannot be found by the smooth application in fig. 2C (d), so that the RCS mark is not displayed in the chat interface. The connect-chat application in the second terminal of this embodiment may discover the RCS capabilities of the chat partner and display the RCS mark 801 in the chat interface. Continuing with the example of the interface shown in FIG. 8B, the RCS indicia 801 can be toggled between the clear connect mode and the RCS mode. For example, in the case where the RCS tab 801 is selected, the user inputs text information, a transmitted voice message, a picture, a geographical location, and the like in the input box as the RCS message transmitted to the RCS application of the counterpart. That is, with the RCS flag 801 selected, the clear connection application in the second terminal communicates with the RCS application in the first terminal. In the case where the RCS flag 801 is not selected, the user inputs text information, a transmitted voice message, a picture, a geographical location, and the like in the input box as a connect message transmitted to the connect application of the counterpart. That is, in the case where the RCS flag 801 is not selected, the smooth connection application in the second terminal communicates with the smooth connection application in the first terminal.

Alternatively, the second terminal may also mark in the address book, see fig. 8C, which is an address book interface of the second terminal, the interface includes the contact person of the first user (the number is the first number) grand guard, and the RCS mark 802 of the first user is displayed. When the second terminal detects an operation with respect to the RCS flag 802, an interface shown in fig. 8B may be displayed, and the clear connection flag 801 in the interface is selected.

The following embodiment describes a procedure in which the second terminal interacts with the RCS of the first terminal through the open connection application. Specifically, please refer to fig. 9A, which is a schematic flowchart illustrating the interaction between the second terminal and the RCS application in the first terminal using the connect-disconnect application. As shown in fig. 9A, the process includes:

and S900, the second terminal responds to the operation and opens a chat conversation interface with the first user in the open-linked application.

For example, the open chat conversation interface with the first user may be the interface shown in FIG. 8B, which includes an RCS flag 801 to indicate that the first user has opened RCS.

S901, the first terminal sets an RCS message mode. For example, in the interface shown in fig. 8B, when the RCS flag 801 is selected, the RCS message mode is set.

S902, the second terminal detects the operation of sending the message to the first user.

For example, taking fig. 8B as an example, the operation may be an operation of inputting text information in an input box and clicking a "send" button.

And S903, the second terminal sends a message to the smooth connection cloud service, wherein the message comprises specific content sent to the first user, the first number and the second number, and an RCS mark for marking that the message needs to be sent to the RCS application. The message is encapsulated using the clear to connect protocol.

And S904, the smooth connection cloud service determines that the message needs to be sent to the RCS according to the RCS mark in the message.

And S905, the smooth connection cloud service sends the message to the smooth connection-RCS fusion gateway.

The clear to connect-RCS convergence gateway may provide a second messaging interface. The second messaging interface is to receive a message from a disconnected cloud service.

And S906, the smooth connection-RCS convergence gateway carries out protocol conversion on the message so as to convert the message into an RCS protocol.

And S907, the smooth connection-RCS fusion gateway sends the RCS call request subjected to the protocol conversion to the RCS Hub.

S908, the RCS Hub sends the message to the RCS.

Optionally, before S908, the RCS Hub may further determine the receiving end of the message, that is, the RCS corresponding to the first number. Since the RCS Hub stores the mobile phone numbers registered in each RCS, the RCS Hub may determine the corresponding RCS according to the first number and then transmit the message to the determined RCS.

S909, the RCS sends the message to the IMS.

S910, the IMS sends the message to the first terminal.

And S911, the first terminal processes the message. The processing includes viewing, replying, and the like.

S912, the first terminal sends a receipt message to the second terminal. S912 includes S912a through S912 g. The receipt message comprises information that the other party has read, the other party has not read, the other party is inputting and the like.

For example, referring to fig. 9B, the receipt information of "the other party has read" is displayed in the chat interface of the second terminal with the first user.

In the above embodiment, two terminals are taken as an example, and in other embodiments, the first instant messaging application in the first terminal, the second instant messaging application in the second terminal, and the third instant messaging application in the third terminal may also be interconnected. Wherein the first instant messaging application, the second instant messaging application and the third instant messaging application are not the same application. For example, please refer to fig. 10, which is a schematic diagram of another communication system according to an embodiment of the present application. The communication system comprises a first terminal, a second terminal and a third terminal. The first terminal comprises an RCS application, the second terminal comprises a smooth connection application, the third terminal comprises a third party instant messaging application, and a server corresponding to the third party instant messaging application is a third party server. The third-party server can realize the connection with the RCS Hub or the connection with the smooth connection cloud service through the fusion gateway, and further realize the intercommunication between the third-party instant messaging application in the third terminal and the RCS application in the first terminal or the intercommunication between the third-party instant messaging application and the smooth connection application in the second terminal. The interworking principle of the third party instant messaging application and the RCS application in the first terminal or the interworking principle of the smooth connection application in the second terminal is the same as the interworking principle of the RCS application in the first terminal and the smooth connection application in the second terminal in the foregoing first and second embodiments, and thus, the details are not repeated.

Based on the same concept, fig. 11 illustrates an electronic device 1100 provided in the present application. The electronic device 1100 may be the first terminal, the second terminal, the first server, the second server, or the third server as described above. As shown in fig. 11, the electronic device 1100 may include: one or more processors 1101; one or more memories 1102; a communications interface 1103, and one or more computer programs 1104, which may be connected by one or more communications buses 1105. The communication interface 1103 is used for communicating with other devices, and may be a transceiver, for example. One or more computer programs 1104 are stored in the memory 1102 and configured to be executed by the one or more processors 1101, the one or more computer programs 1104 comprising instructions which may be used to perform the relevant steps as provided in the respective embodiments above. For example, when the electronic device 1100 is the first terminal as described above, the instructions may be used to perform the steps associated with the first terminal as provided in the corresponding embodiments above; when the electronic device 1100 is the second terminal as in the above, the above instructions may be used to perform the steps associated with the second terminal as provided in the respective embodiments above; when the electronic device 1100 is the first server as described above, the above instructions may be used to perform the relevant steps of the first server as provided in the corresponding embodiments above; when the electronic device 1100 is the second server as in the above, the above instructions may be used to perform the steps associated with the second server as provided in the respective embodiments above; when the electronic device 1100 is the third server as in the above, the above instructions may be used to perform the relevant steps of the third server as provided in the respective embodiments above.

In the embodiments provided in the present application, the method provided in the embodiments of the present application is described from the perspective of electronic devices (e.g., a first terminal and a second terminal) as execution subjects. In order to implement the functions in the method provided by the embodiments of the present application, the electronic device may include a hardware structure and/or a software module, and the functions are implemented in the form of a hardware structure, a software module, or a hardware structure and a software module. Whether any of the above functions is implemented as a hardware structure, a software module, or a combination of a hardware structure and a software module depends upon the particular application and design constraints imposed on the technical solution.

As used in the above embodiments, the terms "when …" or "after …" may be interpreted to mean "if …" or "after …" or "in response to determining …" or "in response to detecting …", depending on the context. Similarly, depending on the context, the phrase "at the time of determination …" or "if (a stated condition or event) is detected" may be interpreted to mean "if the determination …" or "in response to the determination …" or "upon detection (a stated condition or event)" or "in response to detection (a stated condition or event)". In addition, in the above-described embodiments, relational terms such as first and second are used to distinguish one entity from another entity without limiting any actual relationship or order between the entities.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless otherwise specifically stated.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others. The aspects of the above embodiments may all be used in combination without conflict.

It is noted that a portion of this patent application contains material which is subject to copyright protection. The copyright owner reserves the copyright rights whatsoever, except for making copies of the patent files or recorded patent document contents of the patent office.

Claims

1. A cross-application interconnection method between different devices is applied to a communication system comprising a first terminal and a second terminal, and the method comprises the following steps:

displaying a first interface of a first instant messaging application on the first terminal, wherein the first interface comprises a second user, the second user is a registered user of a second instant messaging application on the second terminal, and the first instant messaging application and the second instant messaging application are different applications;

the first instant messaging application responds to a first operation on the first interface and initiates a first communication behavior to the second user, wherein the first communication behavior comprises a video call, a voice call or message sending;

and displaying a second interface of the second instant messaging application on the second terminal, wherein the first communication behavior from a first user is displayed in the second interface, and the first user is a registered user of the first instant messaging application on the first terminal.

2. The method of claim 1, wherein the first interface is a first chat interface with the second user, the first operation being an operation to send a message to the second user in the first chat interface; the first communication behavior is a behavior of sending a message to the second user, the second interface is a second chat interface with the first user, and the second chat interface comprises the message sent by the first user.

3. The method of claim 1, wherein the first interface is a contact list interface of the first instant messaging application, and the first operation is an operation of initiating a voice or video call to the second user in the contact list interface; the first communication behavior is a behavior of initiating a voice or video call to the second user, and the second interface is a voice incoming call interface or a video incoming call interface from the first user.

4. The method of any of claims 1-3, wherein the method further comprises:

the first instant messaging application queries whether the second user registers or opens the second instant messaging application;

when the first instant messaging application determines that the second user is registered or the second instant messaging application is opened, displaying a first mark in the first interface, wherein the first mark is used for indicating that the second user is registered or the second instant messaging application is opened.

5. A method according to any of claims 1-4, wherein the second user is also a registered user of a third instant messaging application on the second terminal; the third instant messaging application is the same application as the first instant messaging application; displaying a switching button in the first interface; when the switch button is in a first state, the first instant messaging application is configured to initiate communication behavior to the third instant messaging application in the second terminal, and when the switch button is in a second state, the first instant messaging application is configured to initiate communication behavior to the second instant messaging application in the second terminal;

before the first instant messaging application initiates a first communication action to the second user in response to the first operation at the first interface, the method further comprises: determining that the toggle button is in the second state.

6. The method according to any one of claims 1-5, wherein the communication system further comprises a first server, a second server and a third server, wherein the first server is a server corresponding to the first instant messaging application, the first server supports a first communication protocol, the second server is a server corresponding to the second instant messaging application, and the second server supports a second communication protocol; the third server is connected with the first server and the second server;

the first server sends the first communication information to the third server;

7. The method according to any of claims 4-6, wherein the communication system further comprises a first server, a second server and a third server, wherein the first server is a server corresponding to the first instant messaging application, the first server supports a first communication protocol, the second server is a server corresponding to the second instant messaging application, and the second server supports a second communication protocol; the third server is connected with the first server and the second server;

the first server sends the first query request to the third server;

the third server sends the second query request to the second server;

the third server sends the second query result to the first server;

and the first server sends the second query result to the first terminal.

8. The method of any one of claims 1-7, further comprising at least one of:

alternatively, the method further comprises at least one of:

the first instant messaging application is a smooth connection application; the second instant messaging application is an RCS application; the first server is a smooth connection server; the second server is an RCS server; the first communication protocol is a smooth connection protocol; and the second communication protocol is an RCS protocol;

alternatively, the method further comprises at least one of:

9. The method of claim 8, wherein the first instant messaging application is an RCS application and the second instant messaging application is a clear to connect application, the method further comprising:

10. The method according to claim 9, wherein the communication system further comprises a first server, a second server and a third server, the first server is a server corresponding to the first instant messaging application, the first server supports a first communication protocol, the second server is a server corresponding to the second instant messaging application, and the second server supports a second communication protocol; the third server is connected with the first server and the second server;

the first server sends the third query request to the third server;

the third server sends the fourth query request to the second server;

the third server sends the fourth query result to the first server;

and the first server sends the fourth query result to the first terminal.

11. The method of claim 10, wherein the second server sending a third query result to the third server, comprising:

when the second server determines that the first user exists in a preset list, the third server sends the third query result to the third server; the preset list is used for indicating the second user to disclose a plurality of devices corresponding to the second user to the users in the preset list;

alternatively, the first and second electrodes may be,

the second server sends an authentication request to the second terminal, wherein the authentication request is used for indicating whether to agree to disclose a plurality of devices corresponding to the second user to the first user;

and when the second server receives a confirmation instruction, sending the third query result to the third server.

12. A cross-application interconnection method between different devices is applied to a first terminal, and the method comprises the following steps:

the first instant messaging application responds to a first operation on the first interface and initiates a first communication behavior to the second user, wherein the first communication behavior comprises a video call, a voice call or message sending.

13. The method of claim 12, wherein the first interface is a first chat interface with the second user, the first operation being an operation in the first chat interface to send a message to the second user; the first communication action is an action of sending a message to the second user.

14. The method of claim 12, wherein the first interface is a contact list interface of the first instant messaging application, and the first operation is an operation of initiating a voice or video call to the second user in the contact list interface; the first communication activity is an activity of initiating a voice or video call to the second user.

15. The method of any of claims 12-14, wherein the method further comprises:

16. The method of any of claims 12-15, wherein the method further comprises:

displaying a switching button in the first interface; when the switch button is in a first state, the first instant messaging application is configured to initiate a communication action to a third instant messaging application on the second terminal, the third instant messaging application being the same application as the first instant messaging application; when the toggle button is in a second state, the first instant messaging application is configured to initiate a communication action to the second instant messaging application on the second terminal.

17. The method of any one of claims 15-16, wherein the first instant messaging application querying whether the second user registers or opens the second instant messaging application comprises:

18. The method of any one of claims 12-17, further comprising at least one of: the first instant messaging application is a smooth connection application; the second instant messaging application is an RCS application;

alternatively, the method further comprises at least one of: the first instant messaging application is an application supporting a first communication protocol; the second instant messaging application is an application supporting a second communication protocol; the first communication protocol is a smooth connection protocol; and the second communication protocol is an RCS protocol;

19. The method of claim 18, wherein the first instant messaging application is an RCS application and the second instant messaging application is a clear to connect application, the method further comprising:

20. The method of claim 19, wherein before displaying the device identifications of the plurality of devices corresponding to the second user in the first interface, further comprising:

21. A communication system, comprising: a first terminal and a second terminal;

the first terminal includes: a processor; a memory; wherein the memory stores one or more computer programs comprising instructions which, when executed by the processor, cause the first terminal to perform the steps of the first terminal in the method according to any one of claims 1 to 11;

the second terminal includes: a processor; a memory; wherein the memory stores one or more computer programs comprising instructions which, when executed by the processor, cause the second terminal to perform the steps of the second terminal in the method according to any of claims 1 to 11.

22. A terminal device, comprising:

a processor, a memory, and one or more programs;

wherein the one or more programs are stored in the memory, the one or more programs including instructions which, when executed by the processor, cause the terminal device to perform the method steps of any of claims 12 to 20.

23. A computer-readable storage medium, for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 20.

24. A computer program product, comprising a computer program which, when run on a computer, causes the computer to perform the method according to any one of claims 1-20.

25. A graphical user interface on an electronic device, the electronic device having a display, a memory, and a processor for executing one or more computer programs stored in the memory, the graphical user interface comprising a graphical user interface displayed when the electronic device performs the method of any of claims 12-20.