WO2018033015A1

WO2018033015A1 - Method and device for communicating between terminals in multiple systems

Info

Publication number: WO2018033015A1
Application number: PCT/CN2017/096803
Authority: WO
Inventors: 刘悦
Original assignee: 中国移动通信有限公司研究院; 中国移动通信集团公司
Priority date: 2016-08-16
Filing date: 2017-08-10
Publication date: 2018-02-22
Also published as: CN107770033A

Abstract

The embodiments of the invention provide a method and device for communicating between terminals in multiple systems. The method comprises: acquiring first login state information of a first type of terminal logging in to a first communication system, and second login state information of a second type of terminal logging in to a second communication system, and storing the first login information and the second login information into a user state database, wherein the first type of terminal and the second type of terminal log in on the basis of a same application and a same account; transmitting, to the second communication system corresponding to the second type of terminal logging in secondly, to enable the second communication system to determine, according to the first login information and the second login information, and a prestored rule for login conflict between different types of terminals, whether to log in the second type of terminal. The disclosed solution is utilized to deal with the same communication between terminals in a plurality of communication systems.

Description

Method and device for communication between terminals in multiple systems

Cross-reference to related applications

Priority is claimed on Japanese Patent Application No. 201610674892.2, filed on Aug.

Technical field

The present disclosure relates to the field of communications technologies, and in particular, to a method and apparatus for communication between terminals in a multiple system.

Background technique

In the era of 4G mobile Internet, Internet manufacturers have developed rapidly in the field of mobile applications, and there have been a number of OTT (Over The Top) applications such as WeChat, QQ, and Mi Chat. They have the features of free and rich experience, and they are fast and iterative. Users provide new business features, which gradually eroded the operator's user base and revenue.

To solve this problem, operators have adopted two different ways to launch their own converged communication instant messaging services:

The first is that operators directly learn Internet vendors and launch their own instant messaging software based on private communication protocols using OTT technology (hereinafter referred to as OTT private system, the terminal used is called OTT APP), such as China Mobile's Fetion and China Telecom. E-mail, etc., this way completely uses the Internet solution, users need to download and install a specific APP, and register a account (for the operator's OTT instant messaging software, usually use the mobile phone number as the user account to progress registration, that is, the user name Mobile phone number, and actual message routing distribution, etc. use OTT internal identification);

The second is to use the international standard of telecommunications to realize the instant messaging system (hereinafter referred to as the converged communication standard instant messaging system) through the support of the GSMA RCS (Global System for Mobile Communications Association Rich Communication Suite), such as China Mobile Fusion. Communication. This method is further divided into three major communication portals for promoting the original call, short/mMS and address book on the upgrade terminal of the mobile phone manufacturer, and supporting the instant message in the terminal native mode (Native, that is, the terminal has the function at the time of leaving the factory) (hereinafter referred to as Standard Native mode, the terminal used is called Native Terminal), and downloading an instant message implemented by an APP based on the converged communication standard (hereinafter referred to as a standard APP method, the terminal used is referred to as an RCS APP). Due to the use of international standards, this method guarantees the global accessibility of carrier basic communication services and the quality of carrier-class services. It can be said that this method is based on communication capabilities.

Some of the larger operators, such as China Mobile, have strong technical capabilities and strong industrial driving force, so they have a converged communication standard instant messaging system and OTT private instant messaging system, so that the same user It is possible to use the APP while having a Native terminal, and the APP may be an OTT APP or an RCS APP. At the same time, this user may also have various clients such as a PC client and a Pad client, so that the same user will have There are many different terminals, and there may be more than one APP or Native portal with the same function on the same terminal. In this way, if the message is sent to different portals of different terminals, the user needs to repeatedly switch between different portals of different terminals. Will cause trouble for the user's use. At the same time, the operator's traditional short MMS system still exists, which will further increase the difficulty of users.

Summary of the invention

The present disclosure provides a method and apparatus for communication between terminals in a multi-system, thereby enabling the same communication between terminals in a plurality of communication systems.

In order to solve the above technical problem, an embodiment of the present disclosure provides the following solution:

A method for communication between terminals in a multi-system includes:

Obtaining first login status information that the first type terminal uses to log in using the first communication system, and second login status information that the second type terminal uses to log in using the second communication system, and the first login status information and the first The second login status information is stored in the user status database; the first type terminal and the second type terminal are different types of terminals that log in based on the same account of the same application;

Transmitting the first login state information and the second login state information to a second communication system corresponding to the second type terminal that is logged in later, so that the second communication system is configured according to the first login state information and the second login The status information, and pre-stored login conflict rules between different types of terminals, determine whether the second type of terminal is allowed to log in.

In an optional implementation manner of the disclosure, the login conflict rule includes: the first type end The terminal is a native terminal that supports instant messaging and supports other instant messaging applications, and the second type of terminal is factory-supported for instant messaging but does not support installation of other instant messaging applications other than non-Native terminals. All types of terminals can be online at the same time.

In an optional implementation manner of the present disclosure, the login conflict rule includes: the first type terminal is a terminal that installs an instant messaging application rich media communication RCS APP1, and the second type terminal is a terminal that installs an RCS APP1, Both types of terminals can be online at the same time, but the terminals that are installed with RCS APP2, OTT APP 1 and OTT APP 2 cannot be online at the same time, and the logins that are logged in before are logged off; wherein, RCS APP1 and RCS APP2 is a different application based on the same communication protocol, and OTT APP 1 and OTT APP 2 are different applications based on the same communication protocol.

The login conflicting rule includes: the first type of terminal is a terminal for installing an instant messaging application rich media communication RCS APP2, and when the second type of terminal is a terminal for installing an RCS APP2, both types of terminals can be online at the same time. However, the terminals that are installed with RCS APP1, OTT APP 1, and OTT APP 2 are not online at the same time, and the logins that are logged in before are logged off; wherein RCS APP1 and RCS APP2 are different applications based on the same communication protocol. OTT APP 1 and OTT APP 2 are different applications based on the same communication protocol.

The login conflicting rule includes: the first type of terminal is a terminal that installs an instant messaging application OTT APP 1 of a private communication protocol, and when the second type of terminal is an OTT APP 1, both types of terminals can be online at the same time. However, the terminals that are installed with RCS APP1, RCS APP 2, and OTT APP 2 are not online at the same time, and the logins that will be logged in before are offline; wherein, RCS APP1 and RCS APP2 are different based on the same communication protocol. Applications, OTT APP 1 and OTT APP 2 are different applications based on the same communication protocol.

The login conflicting rule includes: the first type of terminal is a terminal that installs the OTT APP 2 of the instant messaging application of the private communication protocol, and when the second type of terminal is the terminal that installs the OTT APP 2, both types of terminals may be used. Simultaneously online, but the terminals that install RCS APP1, RCS APP 2, and OTT APP1 are not online at the same time, and the logins that will be logged in before are offline; wherein RCS APP1 and RCS APP2 are based on the same communication protocol. For different applications, OTT APP 1 and OTT APP 2 are different applications based on the same communication protocol.

The login conflict rule includes: when the first type of terminal is the computer PC1, and when the second type of terminal is the computer PC2, the two types of terminals cannot be online at the same time, and the later logins are logged in before. Kick off the line; PC1 and PC2 are different computers.

In an optional implementation manner of the present disclosure, different types of terminals are distinguished by a terminal identifier: a terminal of a Native obtains a terminal identifier by using an instance of the session initiation protocol sip.instance=imei; and a terminal that installs the RCS APP 1 The terminal identifier is obtained based on the instance sip.instance=UUid1 of the session initiation protocol; the terminal that installs the RCS APP 2 obtains the terminal identifier by using the instance sip.instance=UUid2 of the session initiation protocol; the terminal of the OTT APP 1 is installed, and the corresponding terminal identifier is Eid1; the terminal that installs OTT APP 2, the corresponding terminal identifier is Eid2; the PC1 terminal, the corresponding terminal identifier is PCid1; the PC2 terminal, the corresponding terminal identifier is PCid2; wherein Eid1 is different from Eid2, and PCid1 is different from PCid2.

In an optional implementation manner of the present disclosure, the method for communicating between the terminals in the multiple system further includes: acquiring a message sent by the sending terminal, and storing the message in the first message queue of the sending terminal;

Obtaining, from the user state database, at least one type of receiver terminal that is currently in a login state;

And according to the message, a notification message is respectively written in the notification queue of the at least one type of access terminal, and the notification message in the queue is notified by the system server corresponding to the at least one type of receiver terminal. They are sent to the receiver terminal separately.

In an optional implementation manner of the present disclosure, the method for communication between terminals in the multiple system further includes: performing, by the first message queue of the sending terminal, message synchronization to the second message queue of the receiver terminal.

In an optional implementation manner of the disclosure, the message sent by the sending terminal has an identifier, where the identifier is used to identify that the sending terminal is the same as the sending terminal and is in the login state and is based on the same application. The receiving terminal of the account sent.

In an optional implementation manner of the present disclosure, after the first message queue of the sending terminal performs message synchronization to the second message queue of the receiving terminal, the method further includes: at least one type of receiving terminal corresponding to the communication system, which will be updated this time. The message is sent to the recipient terminal.

In an optional implementation manner of the present disclosure, the method for communication between terminals in the multiple system further includes: when the receiving terminal receives the message of the update, the message of the current update is already in the at least one type. If the other recipient terminal receives it, the receiver terminal performs silent processing.

In an optional implementation manner of the present disclosure, the method for communication between terminals in multiple systems further includes: if at least one type of receiver terminal, only the factory can support instant messaging but does not support When the non-Native terminal that installs other instant messaging applications is in the login state, the communication system adopted by the non-Native terminal converts the updated message into a short message or a multimedia message, and sends the message to the receiving terminal through the short message center.

An embodiment of the present disclosure further provides an apparatus for communication between terminals in a multiple system, including:

An acquiring module, configured to acquire first login status information that is used by the first type terminal to log in using the first communication system, and second login status information that is used by the second type terminal to log in using the second communication system, and the first login status is The information and the second login status information are stored in a user status database; the first type terminal and the second type terminal are different types of terminals that log in based on the same account of the same application;

a sending module, configured to send the first login state information and the second login state information to a second communication system corresponding to the second type terminal that is logged in later, so that the second communication system is configured according to the first login state The information and the second login status information, and the login conflict rule between the different types of terminals stored in advance, determine whether the second type terminal is allowed to log in.

In an optional implementation manner of the disclosure, the login conflict rule includes: the first type of terminal is a native terminal that is ready to support instant messaging and supports other instant messaging applications, and the second type of terminal is Both types of terminals can be online at the same time when the factory supports instant messaging but does not support the installation of other non-Native terminals for instant messaging applications; or

The first type of terminal is a terminal for installing an instant messaging application rich media communication RCS APP1, and when the second type terminal is a terminal for installing an RCS APP1, both types of terminals can be online at the same time, but with RCS APP2 and OTT installed. The terminals of APP 1 and OTT APP 2 cannot be online at the same time, and the logins that are logged in after the login are offline; or

The first type of terminal is a terminal for installing an instant messaging application rich media communication RCS APP2, and when the second type of terminal is a terminal for installing an RCS APP2, both types of terminals can be online at the same time, but with the installation of RCS APP1, OTT The terminals of APP 1 and OTT APP 2 cannot be online at the same time, and the logins that are logged in after the login are offline; or

The first type of terminal is a terminal of an instant messaging application OTT APP 1 that installs a private communication protocol. When the second type of terminal is an OTT APP 1, both types of terminals can be online at the same time, but the RCS APP1 is installed. The terminals of RCS APP 2 and OTT APP 2 cannot be online at the same time, and the logins that are logged in after the login are offline; or

The first type of terminal is a terminal for installing an instant messaging application OTT APP 2 of a private communication protocol, and when the second type of terminal is a terminal for installing an OTT APP 2, both types of terminals can be online at the same time, but with the installation of RCS The terminals of APP1, RCS APP 2, and OTT APP 1 cannot be online at the same time, and the logins that are logged in after the login are offline; or

The first type of terminal is a computer PC1, and when the second type of terminal is a computer PC2, the two types of terminals cannot be online at the same time, and the later logins are logged in.

In an alternative embodiment of the present disclosure, the RCS APP1 and the RCS APP2 are different applications based on the same communication protocol, and the OTT APP 1 and the OTT APP 2 are different applications based on the same communication protocol, and PC1 and PC2 are different computers.

In an optional implementation manner of the present disclosure, different types of terminals are distinguished by a terminal identifier: a terminal of a Native obtains a terminal identifier by using an instance of the session initiation protocol sip.instance=imei; and a terminal that installs the RCS APP 1 The terminal identifier is obtained based on the instance sip.instance=UUid1 of the session initiation protocol; the terminal that installs the RCS APP 2 obtains the terminal identifier by using the instance sip.instance=UUid2 of the session initiation protocol; the terminal of the OTT APP 1 is installed, and the corresponding terminal identifier is Eid1; the terminal that installs OTT APP 2, the corresponding terminal identifier is Eid2; PC1, the corresponding terminal identifier is PCid1; PC2, the corresponding terminal identifier is PCid2; wherein Eid1 is different from Eid2, and PCid1 is different from PCid2.

In an optional implementation of the present disclosure, the device for communicating between the terminals in the multiple system further includes: a message synchronization module, configured to acquire a message sent by the sending terminal, and store the message in the first message queue of the sending terminal; Obtaining at least one type of receiver terminal that is currently in a login state in the user state database; and writing a notification message to the notification queue of the at least one type of access party terminal according to the message, and by the The system server corresponding to the at least one type of receiver terminal sends the notification message in the notification queue to the receiver terminal.

In an optional implementation manner of the disclosure, the message synchronization module is further configured to: perform a message synchronization by using a first message queue of the sending terminal to a second message queue of the receiving terminal.

In an optional implementation manner of the disclosure, the message sent by the sending terminal has an identifier, where the identifier is used to identify that the message is the same as the sending terminal is in the login state and is based on the same application. The receiving terminal of the account sent.

In an optional implementation manner of the present disclosure, the device for communication between terminals in the multiple systems further includes: The communication system corresponding to the at least one type of recipient terminal transmits the message of the update to the receiver terminal.

In an optional implementation manner of the present disclosure, the device for communicating between the terminals in the multiple system further includes: when the receiving terminal receives the message of the update, the message of the current update is already in the at least one type. If the other recipient terminal receives it, the receiver terminal performs silent processing.

In an optional implementation manner of the present disclosure, the device for communication between the terminals in the multiple system further includes: if at least one type of the receiver terminal, only the factory can support instant messaging but does not support installing other instant messaging applications. When the non-Native terminal is in the login state, the communication system adopted by the non-Native terminal converts the updated message into a short message or a multimedia message, and sends the message to the recipient terminal through the short message center.

processor;

A memory is stored with computer readable instructions executable by the processor, the processor performing the following operations when the computer readable instructions are executed:

Embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing computer readable instructions executable by a processor, the processor executing when the computer readable instructions are executed by a processor The following operations:

Obtaining first login status information that the first type terminal uses to log in using the first communication system, and second login status information that the second type terminal uses to log in using the second communication system, and the first login status information and the first The second login status information is stored in the user status database; One type of terminal and the second type of terminal are different types of terminals that log in based on the same account of the same application;

The above aspects of the present disclosure include at least the following beneficial effects:

The foregoing solution of the present disclosure, by acquiring first login status information that the first type terminal uses to log in using the first communication system, and second login status information that the second type terminal uses to log in using the second communication system, and the first The login status information and the second login status information are stored in a user status database; the first type terminal and the second type terminal are different types of terminals that log in based on the same account of the same application; a login status information and a second login status information are sent to the second communication system corresponding to the second type terminal that is logged in later, so that the second communication system is based on the first login status information and the second login status information, and A login conflict rule between different types of terminals stored in advance determines whether the second type terminal is allowed to log in. Realize multi-terminal online state management and message communication management between different systems.

DRAWINGS

FIG. 1 is a related art IMS multi-terminal message communication mechanism;

2 is a multi-terminal message communication mechanism of an OTT system in the related art;

3 is a schematic diagram of an instant messaging delivery channel of each type of terminal in the related art;

4 is a flow chart of a method for communication between terminals in a multiple system of the present disclosure;

5 is a system architecture diagram of communication between terminals in a multiple system of the present disclosure;

6 is a schematic diagram of a state of an initial user terminal in a method for communication between terminals in a multi-system according to the present disclosure;

7 is a schematic diagram of a user OTT APP 1 going online at the terminal B in the method for communication between terminals in the multiple systems of the present disclosure;

8 is a schematic diagram of a user OTT APP logging in on a Native terminal in a method for communication between terminals in a multiple system according to the present disclosure;

FIG. 9 is a schematic diagram of a state in which a user PC APP is deregistered in a method for communication between terminals in a multi-system according to the present disclosure;

10 is another flow chart of a method for communication between terminals in a multiple system of the present disclosure;

FIG. 11 is a flow chart of sending a multi-terminal message on the calling side in the process shown in FIG. 10;

12 is a flow of receiving a multi-terminal message on the called side in the flow shown in FIG. 10;

FIG. 13 is a flow chart showing that only the short message terminal is online in the flow shown in FIG. 10;

Figure 14 is a diagram showing the structure of a computer system of a device suitable for implementing communication between terminals in a multi-system of the embodiment of the present application or a device for communication between terminals in a plurality of systems.

detailed description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings.

In the related art, each communication system is independent of each other, and the message cannot be distributed between terminals in different systems. The messages in the IMS system can only be sent to the terminals in the IMS system, and the messages in the OTT system can only be sent to The problem of the terminal in the OTT system, the embodiment of the present disclosure realizes the multi-terminal online state management between different systems by establishing a unified data layer, integrating the terminal state data and the message data of each system into the unified data layer. And message management.

Reasonable integration of many message channels owned by operators, including telecom standard instant messaging channels, OTT instant messaging channels, and traditional short multimedia messaging channels, enables users to have different usages of different message portals, and is an operator to enhance user message experience. An important means of increasing user stickiness. For example, for different terminals, all messages are guaranteed to be received. When users look at different terminals, they can have a complete message history. However, only the terminals that the user currently operates can make prompts such as voices, and other terminals perform silent processing; for the same terminal. Only one message entry displays the message (either the terminal Native native message entry, or the only one APP message entry, which does not need to be repeatedly switched at each message entry).

For a multi-terminal scenario, the related technologies are generally classified into a multi-terminal processing method in an IMS (IP Multimedia Subsystem) system and a multi-terminal processing method in an OTT system, where:

The IMS multi-terminal message mechanism is shown in Figure 1. This method requires all terminals used by the same user to be based on SIP. They all have the same SIP user identity (IMPI/IMPU) and pass different SIP instances (sip.instance or GRUU). ) registering in IMS, for different terminals, There are two types of processing: the terminal identifiers are identical. The terminal that is registered later kicks the terminal that is registered first, and only the online terminal receives the message.

Different terminals can be distinguished by parameters such as GRUU or sip.instance, and can be registered at the same time. All messages are stored in the centralized message storage platform. When receiving the message, the same message is copied into multiple copies through the IMS forking mechanism. To each terminal instance, for a terminal that is not online, the message synchronization is implemented by using a push mode through a centralized message storage platform after being online.

The OTT instant messaging system uses a similar method, but generally multiple terminals are classified into a master terminal and a slave terminal (for example, WeChat and WeChat web versions). Generally, on a device, only one terminal can log in to the same account (for example, two mobile phones cannot log in to the same account). In addition, the login from the terminal depends on the main terminal. For example, when the mobile phone logs in, the PC can be used. Personal computer) side web client login, etc. For a scenario where the receiver has multiple devices, the messages are respectively written into multiple message queues according to the login state of the receiver, and each terminal of the receiver is notified of the message update, and the receiver compares the local message records. The server pulls the corresponding message, after which the receiving device notifies the server that a message has been received, and the server can set the part of the message of the device to be read in the message queue.

For an operator with multiple messaging systems, the instant messaging delivery channel of each type of terminal is shown in FIG. 3. It can be seen that each message system is a separate vertical structure, and multiple terminals and message entry relationships owned by the user are also complicated. The existing technical solutions cannot implement multi-terminal management and message requirements in such a scenario.

The above-mentioned FIG. 1 and FIG. 2, whether the multi-terminal solution in the IMS system or the multi-terminal solution in the OTT system, cannot coexist with the unified operator IMS message system and the OTT message system, and the multiple terminals exist in different systems respectively. A scenario, that is, multiple terminals in different systems cannot be uniformly managed. Because the systems are independent of each other and cannot distribute messages between terminals in different systems, messages in the IMS system can only be sent to terminals in the IMS system, and messages in the OTT system can only be sent to the OTT system. terminal.

As shown in FIG. 4, an embodiment of the present disclosure provides a method for communication between terminals in a multiple system, including:

Step 41: Acquire first login status information that the first type terminal uses to log in using the first communication system, and second login status information that the second type terminal uses to log in using the second communication system, and And storing the first login status information and the second login status information in a user status database; the first type terminal and the second type terminal are different types of terminals that are logged in based on the same account of the same application. ;

Step 42: Send the first login state information and the second login state information to the second communication system corresponding to the second type terminal that is logged in later, so that the second communication system is based on the first login state information and The second login status information, and the login conflict rule between the different types of terminals stored in advance, determines whether the second type terminal is allowed to log in.

In this embodiment of the disclosure, the multiple systems may be a plurality of different instant messaging systems and a traditional short multimedia messaging system for the same operator, the user has multiple different terminals, and there may be different Native/APP entries on the same terminal. The scenario realizes multi-terminal online state management and message management between different systems by establishing a unified data layer and integrating terminal data and message data of each system into a unified data layer.

In the embodiment of the present disclosure, the client can be classified into the following four types:

1.1) PC-type client: An APP on a PC implemented based on the PC OTT proprietary protocol.

1.2) RCS APP client: An APP on a mobile phone based on the RCS standard.

1.3) OTT APP client: An APP on a mobile phone based on the mobile phone OTT proprietary protocol.

1.4) Native: The original message portal of the mobile phone. If the RCS message capability has been upgraded, the RCS instant message and short multimedia message can be sent and received. Otherwise, the short multimedia message can only be sent and received. The type is an independent type, and the mobile client APP and native can be online at the same time regardless of whether the APP and the native are on the same terminal.

The online rules of the client, that is, the login conflict rules of each type of terminal are as follows:

2.1) The Native terminal is bound to the user SIM card. Each user can only have a unique Native terminal, and the terminal cannot be kicked off the line by other terminals.

2.2) When the Native terminal has a data connection, it has RCS instant messaging capability.

2.3) When the Native terminal has no data connection, it still has the traditional short multimedia message receiving capability.

2.4) Non-Native terminals, only short MMS receiving capabilities.

2.5) Both the RCS APP and the OTT APP can be installed on a Native terminal or a non-Native terminal.

2.6) On the same terminal, the RCS APP and the OTT APP can only have one online, and the client that goes online will kick the other client off the line.

2.7) Different versions of the same type of client cannot be online at the same time.

2.8) When the APP is installed on the Native terminal, the instant message will be sent only to the Native terminal regardless of the version of the APP. If the user enters directly from the APP portal, the APP reads the history from the database of the Native terminal.

2.9) The PC client can be online at the same time as the mobile phone Native/APP and will receive all messages.

The conflict relationship between various types of terminals is shown in Table 1. If there are different conflict rules, you can implement the new rules by reconfiguring the rules table.

Table 1

Among them, in the above table, N/A means that online is allowed, and × means that online is not allowed. When there is a conflict between the logged-in terminals, the terminal that is logged in will kick the terminal that is logged in first.

For different terminals, the difference is identified by their device identifier:

3.1) Native terminal and RCS APP are based on the integrated communication standard instant messaging system, using IMS-based RCS standard, the identification is based on IMS code number system: Native device identification and device type are obtained by sip.instance=imei; RCS APP The device identification and device type are obtained by sip.instance=uuid.

3.2) OTT allows registration of logins on different devices. Each time a device is registered, the OTT server assigns a device identifier to the device, such as: APP1: the identifier is eid1, and APP2: the identifier is eid2.

3.3) The PC client is similar to the OTT APP: PC client 1: ID is PCid1, PC client 2: ID is PCid2; Eid1 is different from Eid2, and PCid1 is different from PCid2.

The types of terminal identifiers are shown in Table 2.

Table 2

As shown in FIG. 5, in order to implement the system architecture of the above method, a unified user state database is set on the same operator having multiple different instant messaging systems and a traditional short multimedia messaging system. A unified message queue is set on each instant messaging system and SMS system. In the figure, a one-way solid arrow indicates that the message is delivered, a two-way dotted arrow indicates that it can be installed, and a two-way solid arrow indicates that the message can be read.

The silo-type message systems that are independent of each other need to be docked in the newly created user state database, and the login status of the respective terminal in the own system is submitted to the user state database through the data interface, and the user is all logged in to the device returned by the user state database. status information.

The vertical silo message systems that are independent of each other need to be connected to the newly created unified message queue. The message queue is divided into two parts: a message queue and a notification queue. The message queue is used to store the sent and received messages themselves, and the notification queue is used to notify each corresponding. The terminal has a new message coming.

A specific implementation example of the multi-terminal login management method: when the user's various devices log in or log out, the corresponding server in the access system (IM AS (application server) in the RCS instant messaging system, OTT in the OTT instant messaging system) The AS, the PC AS in the PC system needs to write the login or logout information of the device to the user status database (the user's SMS defaults online, and the user status database has SMS terminal information by default unless the user is in the CS (circuit) domain. Up), the information returned by the user status database to the server carries the information of all the users logging in to the device.

The server in each system determines whether it is necessary to kick the other end off the line according to the database return and the device mutual exclusion policy, and if necessary, initiates a logout request to the server where the end is located. Because the short multimedia messaging system is not mutually exclusive with other systems, the short multimedia messaging center does not need to initiate a logout request to other systems.

The example steps are as follows:

(1) The user's Native terminal (number 138XXXXXXXX) is online. As shown in Figure 6, an RCS APP is installed on the Native terminal. The information in the user status database is as shown in Table 3 below:

table 3

(2) The user logs in on the terminal B (number is 139XXXXXXXX) with the OTT APP. As shown in FIG. 7, the OTT AS allocates eid1 and writes the information of the OTT APP in the terminal B login. The user status database, the user status database returns all current online terminal information to the OTT AS, and the OTT AS determines that there is no conflict according to the conflict rule, and does not need to initiate a logout request.

At this point, the user's status information is as shown in Table 4 below:

Table 4

(3) The user OTT APP logs in on the Native terminal, as shown in FIG. The OTT AS allocates the eid2 and writes the information of the OTT APP in the terminal B to the user status database. The user status database returns all the current online terminal information to the OTT AS. The OTT AS determines that the RCS APP exists on the same terminal according to the conflict rule. The conflict between OTT APP2, so the OTT APP2 that logs in later needs to kick the RCS APP that is logged in first. Therefore, the OTT AS initiates a logout request to the RCS AS through the Network API call mode, and the RCS APP in the RCS instant messaging system is used. Kick off the line. The status of the user at this time is as shown in Table 5 below:

table 5

(4) When the terminal is revoked, the same reason. As shown in Figure 9. For example, if the user PC APP logs out, the PC AS writes the information to the user state database, and the user state database returns all the current online terminal information to the PC AS. At this time, the terminal has no conflict and does not need to initiate the logout.

The status of the user at this time is as shown in Table 6 below:

Table 6

As shown in FIG. 10, an embodiment of the present disclosure provides a method for communication between terminals in a multiple system, including:

Step 101: Acquire first login status information that the first type terminal uses to log in using the first communication system, and second login status information that the second type terminal uses to log in using the second communication system, and the first login status information and The second login status information is stored in a user status database; the first type terminal and the second type terminal are different types of terminals that log in based on the same account of the same application;

Step 102: Send the first login state information and the second login state information to the second communication system corresponding to the second type terminal that is logged in later, so that the second communication system is based on the first login state information and a second login status information, and a login conflict rule between different types of terminals stored in advance, determining whether the second type terminal is allowed to log in;

Step 103: Acquire a message sent by the sending terminal in the login state, and store the message in the first message queue of the sending terminal. The message sent by the sending terminal has an identifier, where the identifier is used to identify that the message is Transmitting the terminal to the receiving terminal that is in the login state at the same time as the sending terminal and based on the same account of the same application;

Step 104: Obtain, from the user state database, at least one type of receiver terminal that is currently in a login state;

Step 105: Write a notification message to the notification queue of the at least one type of access terminal according to the message, and notify the queue by the system server corresponding to the at least one type of receiver terminal. The notification message is sent to the receiver terminal separately;

And further, the method may further include:

Step 106: The first message queue of the sending terminal performs message synchronization with the second message queue of the receiving terminal.

Step 107: The communication system corresponding to the at least one type of receiver terminal sends the message of the update to the receiver terminal.

Step 108: When the receiving terminal receives the message of the update, if the message of the current update has been received on the other receiving terminal of the at least one type, the receiving terminal performs a silent process.

In this embodiment of the present disclosure, the method of setting a unified message queue on the short message system implements multi-terminal message transmission, which may further include a multi-terminal message sending mechanism on the calling side and a multi-terminal message receiving mechanism on the called side. The calling side multi-terminal message sending mechanism is as follows:

Each user (telephone number) has a home message queue as the main queue. The message queue of another node that is not owned by the user acts as a slave queue and keeps synchronization with the main queue; the message sent by the caller is simultaneously written into the self-receiving message queue. Medium, used to achieve the CC at the other end of the calling side. The message is delivered in the same way as the receiver, but the message has a special identifier indicating that it is a message of its own. The calling other terminal does not form a delivery report message.

As shown in Figure 11, the calling side multi-terminal message sending process:

1 Caller A sends a message;

2 The server to which it belongs writes the message to its own receiving message queue. This message has a special flag indicating that it is a message sent by itself;

3 The message queue database service queries which end of user A is online according to the information in the A user status database, and writes the corresponding notification queue;

4 The notification queue notifies the corresponding server of the new message;

5 The corresponding server pulls the message from the message queue;

6 The corresponding server sends the message to the other end of the calling party A. The other end judges that this is a message sent by itself according to the flag in the message, and is displayed in the sending message. Because these messages are not prompted to the sending user, although the other end of the sender user will receive the same message record from the user, the user does not need to switch between their respective message entries.

Thereafter, the message queue of the sender user A performs message synchronization with the message queue of the receiver user B.

The process of the called side multi-terminal message receiver is as follows:

The called side also uses the unified message queue to provide multi-terminal message reception on the called side, and the processing rules are as follows. under:

Different terminal devices of the same user respectively set different pointers in a message notification queue to identify messages received by the terminal. If the currently called user B status database, the mobile phone number of the called user B, except for the short message, no terminal is online, that is, when there is no notification queue to be written, the online list of users obtained by each server is also Empty, in this state, the RCS AS will pull the instant message and convert it into a short message and deliver it to the called user B via SMS. Since only the TCS converged communication instant messaging system based on the telecommunication standard has the ability to interact with the short message in the telecommunication signaling network, the function of transferring the short message needs to be completed by the RCS AS. If the pointer of a device is lower than the highest pointer of the user, it indicates that the message of the terminal needs to be silently processed. Each terminal delivery report is also written to the message queue in accordance with the message rules. For the delivered and read reports, the message queue is weighted and only the first delivery report is retained. For the forwarded SMS report, the IMS AS writes a new message as a new message to the message queue, and does not perform weighting processing with other delivery reports.

As shown in FIG. 12, the called side multi-terminal message receiving process: First, the user B message queue writing/synchronization is completed, and the queue writing is notified. The current B online terminal is queried according to the user B user status database. For example, at this time, the receiving user B has a Native and a PC client, and the status of the latest message is as follows:

最新消息latest news	8585
最新已读Recently read	7272
RCS NativeRCS Native	7272
RCS APPRCS APP	6060
OTT APP 1 OTT APP 1	6868
OTT APP 2 OTT APP 2	33
PCPC	5555

The process includes:

1Notify the Native and PC clients that there is new news;

2IMS AS obtains the message (73-85) after the current pointer of the IMS client, updates the native pointer to 85, and the latest read update to 85;

3IMS server is pushed to RCS Native by IMS;

The 4PC client goes online or the user clicks to receive the message;

The 5PC server obtains the message (56-85) after the current pointer of the PC client, and updates the PC pointer to 85;

Before the 6PC client obtains the message, the pointer 55 is smaller than the highest read pointer 85, and the PC needs to perform silent processing. The PCAS adds a silent flag to the sent message, that is, the other online terminals of the user still receive the same message, but will not remind the user. Users also do not need to switch back and forth between individual message entries. When the user actively enters from another message entry, the same message record can still be seen because the entry has been received before.

As shown in FIG. 13, when the called party only has the short message online, the process includes:

Complete user B message queue write/synchronization, and notify queue writes. The current B online terminal is queried according to the user B user status database. And the status of the latest news is as follows:

最新消息latest news	8585
最新已读Recently read	8585
RCS NativeRCS Native	8585
RCS APPRCS APP	6060
OTT APP 1 OTT APP 1	6868
OTT APP 2 OTT APP 2	33
PCPC	8585

The process is as follows:

1 The user status database query finds that all the instant messaging capable terminals on the mobile phone that is sent to the called user B's mobile phone number are not online, and then need to notify the RCS AS with the short message capability to pull a new message;

2RCS AS query currently has 3 messages (86-88) between the latest news, then pull these 3 messages down to local, and set the latest read pointer of RCS Native to 88;

3RCS AS converts these three messages into short messages and sends them to the SMS center of the calling user through the No. 7 signaling network;

4 The call center of the calling user sends 3 short messages to the called user B according to the standard short message process.

In the above embodiments of the present disclosure, the plurality of systems may be a plurality of different instant messaging systems owned by the same operator and a conventional short multimedia messaging system, and the above embodiments of the present disclosure have multiple different instant messaging systems by the same operator. And setting a unified user state on top of the traditional short multimedia messaging system The database realizes online state management of multiple terminals by uniformly storing information of the online end of the user in the database; and realizing message distribution between multiple terminals by setting a unified message queue on each instant messaging system and the short message system. Thereby, the unified management of the terminal online state between the respective message systems which are independent of each other is realized; and the message distribution between the plurality of terminals originally belonging to the respective independent message systems is realized, and different terminals can see the same message record. However, only the terminal currently operated by the user will prompt the user, and the user does not need to repeatedly switch between the terminals, thereby improving the user experience.

For different terminals, all messages are guaranteed to be received. When users look at different terminals, they can have a complete message history. However, only the terminals that the user currently operates can make sounds and other prompts, and other terminals perform silent processing. For the same terminal, only One message entry displays the message (either the terminal Native native message entry, or the only one APP message entry, which does not need to be repeatedly switched at each message entry).

The login conflict rule includes: the first type terminal is a native terminal that can support instant messaging and supports other instant messaging applications, and the second type terminal is factory-supported for instant messaging but does not support installation. When instant messaging is applied to a non-Native terminal, both types of terminals can be online at the same time; or

The first type of terminal is a terminal for installing an instant messaging application rich media communication RCS APP1, and the second type of terminal is a terminal for installing an RCS APP1, both types of terminals can be online at the same time, but with the installation of RCS APP2, OTT APP 1 and OTT APP 2 terminals cannot be online at the same time. Recorded kicking off the line before logging in; or

The first type of terminal is a terminal for installing an instant messaging application rich media communication RCS APP2, and the second type of terminal is a terminal for installing an RCS APP2, both types of terminals can be online at the same time, but with RCS APP1, OTT APP 1 and OTT installed The terminals of APP 2 cannot be online at the same time, and those who log in later will log in before the line; or

The first type of terminal is a terminal that installs the instant messaging application OTT APP 1 of the private communication protocol, and when the second type of terminal is installed with the OTT APP 1, both types of terminals can be online at the same time, but with the installation of RCS APP1, RCS APP 2 and The terminals of OTT APP 2 cannot be online at the same time, and the logins that will be logged in before will be offline; or

The first type of terminal is a terminal for installing an instant messaging application OTT APP 2 of a private communication protocol, and when the second type of terminal is a terminal for installing an OTT APP 2, both types of terminals can be online at the same time, but with the installation of RCS APP1, RCS APP 2 and the terminal of OTT APP 1 cannot be online at the same time, and the login that is logged in later will be kicked off the line; or

When the first type of terminal is the computer PC1 and the second type of terminal is the computer PC2, the two types of terminals cannot be online at the same time, and the later logins are logged in before the kick-off line;

The RCS APP1 and the RCS APP2 are different applications based on the same communication protocol, and the OTT APP 1 and the OTT APP 2 are different applications based on the same communication protocol, and PC1 and PC2 are different computers.

The terminal of different types is distinguished by the terminal identifier: the native terminal obtains the terminal identifier by using the instance sip.instance=imei based on the session initial protocol; the RCS APP 1 terminal is installed, and the instance based on the session initial protocol is sip.instance= UUid1 obtains the terminal identifier; installs the RCS APP 2 terminal, obtains the terminal identifier by using the instance of the session initial protocol sip.instance=UUid2; the OTT APP 1 terminal, the corresponding terminal identifier is Eid1; the OTT APP 2 terminal, and the corresponding terminal identifier is Eid2 PC1 terminal, the corresponding terminal identifier is PCid1; PC2 terminal, and the corresponding terminal identifier is PCid2.

The device for communicating between the terminals in the multiple system further includes: a message synchronization module, configured to acquire a message sent by the sending terminal, and store the message in the first message queue of the sending terminal; and obtain the current status from the user state database. At least one type of recipient terminal of the login state; according to the message, respectively writing a notification cancellation in the notification queue of the at least one type of access terminal And transmitting, by the system server corresponding to the at least one type of receiver terminal, the notification message in the notification queue to the receiver terminal.

The message synchronization module is further configured to: perform message synchronization on the first message queue of the sending terminal to the second message queue of the receiver terminal.

The message sent by the sending terminal has an identifier, where the identifier is used to identify that the message is sent by the sending terminal to the receiving terminal that is in the login state with the sending terminal and is based on the same account of the same application.

The device for communicating between the terminals in the multiple system further includes: a communication system corresponding to the at least one type of the receiver terminal, and sending the updated message to the receiver terminal.

The device for communicating between the terminals in the multiple system further includes: when the receiving terminal receives the message of the update, the message of the current update is received on the other receiving terminal of the at least one type. Then, the receiver terminal performs silent processing.

The device for communicating between the terminals in the multiple systems further includes: if at least one type of the receiver terminal is in a login state only if the non-Native terminal that supports the instant messaging service but does not support the installation of other instant messaging applications is in the login state, The communication system adopted by the non-Native terminal converts the updated message into a short message or a multimedia message, and sends the message to the receiver terminal through the short message center.

The device is a device corresponding to the above method, and all implementations in the above method are applicable to the embodiment of the terminal, and the same technical effects can be achieved.

In the device embodiment of the present disclosure, the multiple systems may be multiple different instant messaging systems owned by the same operator and the traditional short multimedia messaging system. The above embodiments of the present disclosure have multiple different instant messages by the same operator. A unified user state database is set on the system and the traditional short multimedia message system, and the online state management of the multi-terminal is realized by uniformly storing the information of the user online end in the database; setting a unified message queue on each instant messaging system and the short message system The way to achieve message distribution between multiple terminals. Thereby, the unified management of the terminal online state between the respective message systems which are independent of each other is realized; and the message distribution between the plurality of terminals originally belonging to the respective independent message systems is realized, and different terminals can see the same message record. However, only the terminal currently operated by the user will prompt the user, and the user does not need to repeatedly switch between the terminals, thereby improving the user experience.

Referring next to Figure 14, a block diagram of a computer system 1400 suitable for use in implementing the means for communicating between terminals in a multi-system of embodiments of the present application is shown.

As shown in FIG. 14, computer system 1400 includes a central processing unit (CPU) 1401 that can be loaded into a program in random access memory (RAM) 1403 in accordance with a program stored in read only memory (ROM) 1402 or from storage portion 1408. And perform various appropriate actions and processes. In the RAM 1403, various programs and data required for the operation of the system 1400 are also stored. The CPU 1401, the ROM 1402, and the RAM 1403 are connected to each other through a bus 1404. An input/output (I/O) interface 1405 is also coupled to bus 1404.

The following components are connected to the I/O interface 1405: an input portion 1406 including a keyboard, a mouse, etc.; an output portion 1407 including a cathode ray tube (CRT), a liquid crystal display (LCD), and the like, and a speaker; a storage portion 1408 including a hard disk or the like And a communication portion 1409 including a network interface card such as a LAN card, a modem, or the like. The communication section 1409 performs communication processing via a network such as the Internet. Driver 1410 is also coupled to I/O interface 1405 as needed. A removable medium 1411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory or the like is mounted on the drive 1410 as needed so that a computer program read therefrom is installed into the storage portion 1408 as needed.

In particular, the processes described above with reference to the flowcharts may be implemented as a computer software program in accordance with an embodiment of the present disclosure. For example, an embodiment of the present disclosure includes a computer program product comprising a computer program tangibly embodied on a machine readable medium, the computer program comprising program code for performing the method of the above flow chart. In such an embodiment, the computer program can be downloaded and installed from the network via the communication portion 1409, and/or installed from the removable medium 1411.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products in accordance with various embodiments of the present disclosure. In this regard, each block of the flowchart or block diagrams can represent a module, a program segment, or a portion of code that includes one or more logic for implementing the specified. Functional executable instructions. It should also be noted that in some alternative implementations, the functions noted in the blocks may also occur in a different order than that illustrated in the drawings. For example, two successively represented blocks may in fact be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts, can be implemented in a dedicated hardware-based system that performs the specified function or operation. Or it can be implemented by a combination of dedicated hardware and computer instructions.

The units or modules described in the embodiments of the present application may be implemented by software or by hardware. The described unit or module can also be provided in the processor. The names of these units or modules do not in any way constitute a limitation on the unit or module itself.

The above is an alternative embodiment of the present disclosure, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present disclosure. It should also be considered as the scope of protection of the present disclosure.

Claims

A method for communication between terminals in a multi-system includes:

Obtaining first login status information that the first type terminal uses to log in using the first communication system, and second login status information that the second type terminal uses to log in using the second communication system, and the first login status information and the first The second login status information is stored in the user status database; the first type terminal and the second type terminal are different types of terminals that log in based on the same account of the same application;

Transmitting the first login state information and the second login state information to a second communication system corresponding to the second type terminal that is logged in later, so that the second communication system is configured according to the first login state information and the second login The status information, and pre-stored login conflict rules between different types of terminals, determine whether the second type of terminal is allowed to log in.
The method of claim 1 wherein said login conflicting rules comprise:

The first type of terminal is a native terminal that can support instant messaging and support other instant messaging applications. The second type of terminal is factory-supported for instant messaging but does not support installation of other instant messaging applications. Both types of terminals can be online at the same time.
The method of claim 1 wherein said login conflicting rules comprise:

The first type of terminal is a terminal for installing an instant messaging application rich media communication RCS APP1, and when the second type terminal is a terminal for installing an RCS APP1, both types of terminals can be online at the same time, but with RCS APP2 and OTT installed. The terminals of APP 1 and OTT APP 2 cannot be online at the same time.

Wherein, the RCS APP1 and the RCS APP2 are different applications based on the same communication protocol, and the OTT APP 1 and the OTT APP 2 are different applications based on the same communication protocol.
The method of claim 1 wherein said login conflicting rules comprise:

The first type of terminal is a terminal for installing an instant messaging application rich media communication RCS APP2, and when the second type of terminal is a terminal for installing an RCS APP2, both types of terminals can be online at the same time, but with the installation of RCS APP1, OTT The terminals of APP 1 and OTT APP 2 cannot be online at the same time.

Wherein, the RCS APP1 and the RCS APP2 are different applications based on the same communication protocol, and the OTT APP 1 and the OTT APP 2 are different applications based on the same communication protocol.
The method of claim 1 wherein said login conflicting rules comprise:

The first type of terminal is a terminal of an instant messaging application OTT APP 1 that installs a private communication protocol. When the second type of terminal is an OTT APP 1, both types of terminals can be online at the same time, but the RCS APP1 is installed. The terminals of RCS APP 2 and OTT APP 2 cannot be online at the same time.

Wherein, the RCS APP1 and the RCS APP2 are different applications based on the same communication protocol, and the OTT APP 1 and the OTT APP 2 are different applications based on the same communication protocol.
The method of claim 1 wherein said login conflicting rules comprise:

The first type of terminal is a terminal for installing an instant messaging application OTT APP 2 of a private communication protocol, and when the second type of terminal is a terminal for installing an OTT APP 2, both types of terminals can be online at the same time, but with the installation of RCS The terminals of APP1, RCS APP 2, and OTT APP 1 cannot be online at the same time, and the logins that will be logged in before are kicked off the line;

Wherein, the RCS APP1 and the RCS APP2 are different applications based on the same communication protocol, and the OTT APP 1 and the OTT APP 2 are different applications based on the same communication protocol.
The method of claim 1 wherein said login conflicting rules comprise:

The first type of terminal is a computer PC1, and when the second type of terminal is a computer PC2, the two types of terminals cannot be online at the same time, and the later logins are logged in.

Among them, PC1 and PC2 are different computers.
The method according to any of claims 2-7, wherein different types of terminals are distinguished by a terminal identifier:

The terminal of the Native obtains the terminal identifier by using the instance sip.instance=imei based on the session initial protocol;

The terminal that installs the RCS APP 1 obtains the terminal identifier by using the instance sip.instance=UUid1 of the session initial protocol;

The terminal that installs the RCS APP 2 obtains the terminal identifier by using the instance sip.instance=UUid2 of the session initial protocol;

The terminal of the OTT APP 1 is installed, and the corresponding terminal identifier is Eid1.

Install the terminal of OTT APP 2, and the corresponding terminal identifier is Eid2;

PC1, the corresponding terminal identifier is PCid1;

PC2, the corresponding terminal identifier is PCid2;

Among them, Eid1 is different from Eid2, and PCid1 is different from PCid2.
The method of claim 1 further comprising:

Obtaining a message sent by the sending terminal, and storing the message in the first message queue of the sending terminal;

Obtaining, from the user state database, at least one type of receiver terminal that is currently in a login state;

And according to the message, a notification message is respectively written in the notification queue of the at least one type of access terminal, and the notification message in the queue is notified by the system server corresponding to the at least one type of receiver terminal. They are sent to the receiver terminal separately.
The method of claim 9 further comprising:

The first message queue of the sending terminal synchronizes the message with the second message queue of the receiving terminal.
The method according to claim 9, wherein the message sent by the sending terminal has an identifier, and the identifier is used to identify that the message is that the sending terminal is in a login state with the sending terminal and is based on the same application. The same account is sent by the receiving terminal.
The method according to claim 10, wherein after the first message queue of the transmitting terminal performs message synchronization to the second message queue of the receiving terminal, the method further comprises:

The communication system corresponding to the at least one type of recipient terminal transmits the message of the update to the receiver terminal.
The method of claim 12 further comprising:

When the receiving terminal receives the message of the update, if the message of the current update has been received on the other receiving terminal of the at least one type, the receiving terminal performs a silent process.
The method of claim 12 further comprising:

If at least one type of receiver terminal only has a non-Native terminal that is ready to support instant messaging but does not support installation of other instant messaging applications, the communication system adopted by the non-Native terminal will transfer the updated message. For SMS or MMS, send it to the recipient terminal through the SMS center.
A device for communication between terminals in a multi-system, comprising:

An acquiring module, configured to acquire first login status information that is used by the first type terminal to log in using the first communication system, and second login status information that is used by the second type terminal to log in using the second communication system, and the first login status is The information and the second login status information are stored in a user status database; the first type terminal and the second type terminal are different types of terminals that log in based on the same account of the same application;

a sending module, configured to send the first login state information and the second login state information to a second communication system corresponding to the second type terminal that is logged in later, so that the second communication system is configured according to the first login state The information and the second login status information, and the login conflict rule between the different types of terminals stored in advance, determine whether the second type terminal is allowed to log in.
The apparatus of claim 15, wherein the login conflict rule comprises:

The first type of terminal is a native terminal that can support instant messaging and support other instant messaging applications. The second type of terminal is factory-supported for instant messaging but does not support installation of other instant messaging applications. When the terminal is used, both types of terminals can be online at the same time; or the first type of terminal is a terminal for installing an instant messaging application rich media communication RCS APP1, and the second type of terminal is a terminal for installing an RCS APP1, Terminals of the type can be online at the same time, but the terminals that are installed with RCS APP2, OTT APP 1 and OTT APP 2 cannot be online at the same time, and the logins that are logged in after the login are offline; or

The first type of terminal is a terminal for installing an instant messaging application rich media communication RCS APP2, and when the second type of terminal is a terminal for installing an RCS APP2, both types of terminals can be online at the same time, but with the installation of RCS APP1, OTT The terminals of APP 1 and OTT APP 2 cannot be online at the same time, and the logins that are logged in after the login are offline; or

The first type of terminal is a terminal of an instant messaging application OTT APP 1 that installs a private communication protocol. When the second type of terminal is an OTT APP 1, both types of terminals can be online at the same time, but the RCS APP1 is installed. The terminals of RCS APP 2 and OTT APP 2 cannot be online at the same time, and the logins that are logged in after the login are offline; or

The first type of terminal is a terminal for installing an instant messaging application OTT APP 2 of a private communication protocol, and when the second type of terminal is a terminal for installing an OTT APP 2, both types of terminals can be online at the same time, but with the installation of RCS The terminals of APP1, RCS APP 2 and OTT APP 1 cannot be simultaneously Online, after logging in, will be kicked off the line before signing in; or

The first type of terminal is a computer PC1, and when the second type of terminal is a computer PC2, the two types of terminals cannot be online at the same time, and the later logins are logged in.

The RCS APP1 and the RCS APP2 are different applications based on the same communication protocol, and the OTT APP 1 and the OTT APP 2 are different applications based on the same communication protocol, and PC1 and PC2 are different computers.
The apparatus of claim 16 wherein the different types of terminals are distinguished by a terminal identifier:

The terminal of the Native obtains the terminal identifier by using the instance sip.instance=imei based on the session initial protocol;

The terminal that installs the RCS APP 1 obtains the terminal identifier by using the instance sip.instance=UUid1 of the session initial protocol;

The terminal that installs the RCS APP 2 obtains the terminal identifier by using the instance sip.instance=UUid2 of the session initial protocol;

The terminal of the OTT APP 1 is installed, and the corresponding terminal identifier is Eid1.

Install the terminal of OTT APP 2, and the corresponding terminal identifier is Eid2;

PC1, the corresponding terminal identifier is PCid1;

PC2, the corresponding terminal identifier is PCid2;

Among them, Eid1 is different from Eid2, and PCid1 is different from PCid2.
The apparatus of claim 15 further comprising:

a message synchronization module, configured to acquire a message sent by the sending terminal, stored in a first message queue of the sending terminal, and obtain, from the user state database, at least one type of receiving terminal that is currently in a login state; according to the message Writing a notification message to the notification queue of the at least one type of access terminal, and transmitting, by the system server corresponding to the at least one type of the receiver terminal, the notification message in the notification queue to the receiving Party terminal.
The apparatus according to claim 18, wherein the message synchronization module is further configured to: the first message queue of the sending terminal performs message synchronization with the second message queue of the receiving terminal.
The device according to claim 18, wherein the message sent by the sending terminal has an identifier, and the identifier is used to identify that the message is sent by the sending terminal to the same time as the sending terminal. Transmitted by the receiving terminal of the same account in the login state and based on the same application.
The apparatus of claim 19, further comprising:

The communication system corresponding to the at least one type of recipient terminal transmits the message of the update to the receiver terminal.
The apparatus of claim 21 further comprising:

When the receiving terminal receives the message of the update, if the message of the current update has been received on the other receiving terminal of the at least one type, the receiving terminal performs a silent process.
The apparatus of claim 21 further comprising:

If at least one type of receiver terminal only has a non-Native terminal that is ready to support instant messaging but does not support installation of other instant messaging applications, the communication system adopted by the non-Native terminal will transfer the updated message. For SMS or MMS, send it to the recipient terminal through the SMS center.
A device for communication between terminals in a multi-system, comprising:

processor;

A memory is stored with computer readable instructions executable by the processor, the processor performing the following operations when the computer readable instructions are executed:

Obtaining first login status information that the first type terminal uses to log in using the first communication system, and second login status information that the second type terminal uses to log in using the second communication system, and the first login status information and the first The second login status information is stored in the user status database; the first type terminal and the second type terminal are different types of terminals that log in based on the same account of the same application;

Transmitting the first login state information and the second login state information to a second communication system corresponding to the second type terminal that is logged in later, so that the second communication system is configured according to the first login state information and the second login The status information, and pre-stored login conflict rules between different types of terminals, determine whether the second type of terminal is allowed to log in.
A non-transitory computer readable storage medium storing computer readable instructions executable by a processor, the processor performing the following operations when the computer readable instructions are executed by a processor:

Obtaining first login status information that the first type terminal uses to log in using the first communication system, and second login status information that the second type terminal uses to log in using the second communication system, and the first login status information and the first The second login status information is stored in the user status database; the first type terminal and the second type terminal are different types of terminals that log in based on the same account of the same application;

Transmitting the first login state information and the second login state information to a second communication system corresponding to the second type terminal that is logged in later, so that the second communication system is configured according to the first login state information and the second login The status information, and pre-stored login conflict rules between different types of terminals, determine whether the second type of terminal is allowed to log in.