WO2020015606A1

WO2020015606A1 - Communication method, device and system

Info

Publication number: WO2020015606A1
Application number: PCT/CN2019/095985
Authority: WO
Inventors: 葛翠丽; 杨艳梅
Original assignee: 华为技术有限公司
Priority date: 2018-07-16
Filing date: 2019-07-15
Publication date: 2020-01-23

Abstract

The present application discloses a communication method, a device and a system. The method is applied to a client side switched from a source system to a target system, comprising: the client side generating a first migration request message; the first migration request message carrying an identification of an involved server of the client side and an identification of the client side in the target system; and the client side sending the first migration request message to a control server of the client side in the source system. Using the method, the members in the group may keep normal communication in the case that they are provided with group communication servers by different systems.

Description

Communication method, device and system

Technical field

The present application relates to a communication system, and in particular, to a communication method, device, and system.

Background technique

In order to cope with communication abnormalities caused by frequent natural disasters (tsunami, earthquakes, etc.) or other factors, a backup system is usually used, for example, isolated E-UTRAN operation for public safety , IOPS) system. The backup system can use the link between the base station and the local core network to achieve normal communication within the local area.

FIG. 1a shows an architecture diagram of a communication system, and the communication system includes a macro system and an IOPS system. Among them, macro system refers to the communication system based on macro network; IOPS system is a simplified mobile communication system designed for emergency communication. The IOPS system can provide communication services when the link between the base station and the core network in the macro system is broken.

As shown in FIG. 1a, a base station (for example, eNB-1 and eNB-2 in FIG. 1a) may belong to both a macro system and an IOPS system. Specifically, eNB-1 is connected to the core network in the macro system (see line 1 in Figure 1a), and is also connected to the core network in the IOPS system (see line 2 in Figure 1a); eNB-2 is connected to the core in the macro system Network connection (line 1), and also the core network in the IOPS system (line 2). When the link between eNB-1, eNB-2 and the core network in the macro system is normal, the macro system provides communication services for users (that is, line 1); when eNB-1, eNB-2 and the macro system in the macro system When the link between the core networks is broken, the IOPS system continues to provide communication services for the user (ie, line 2).

In the prior art, when the link between the base station and the macro EPC returns to normal, the macro system continues to provide communication services for the user. However, when the user is a member of a group and the communication service is a group communication service, if the link between the base station and the macro EPC of some members in the group is restored, using the existing technology will The members of this part switch to the macro system, causing different members in the same group to provide group communication services from different systems. For example, the link between eNB-1 and the core network in the macro system returns to normal, but the eNB The link between the -2 and the core network in the macro system did not return to normal, which caused abnormal group communication.

Summary of the invention

Embodiments of the present application provide a communication method, device, and system, which can enable a group to maintain normal communication when members of a group provide group communication services from different systems.

According to a first aspect, a communication method is provided. The method is applied to a client switching from a source system to a target system, and includes: the client generates a first migration request message, where the first migration request message carries the migration request message. An identity of the client's participating server in the target system and an identity of the client; the client sends the first migration request message to a control server of the client in the source system. This method realizes the migration of the client from the source system to the target system, that is, the client connects to the participating server in the target system, and the participating server continues to provide group calls for the client to ensure the normal progress of the group call. This enables the group to maintain normal communication if the members of the group are provided by a group communication server from different systems.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the method further includes: the client sends a second migration request message to the participating server, and the second migration request message carries a The identity of the control server and the identity of the client.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the second migration request message further carries an identifier of a group to which the client belongs.

With reference to the first aspect or any one of the foregoing possible implementation manners of the first aspect, in a third possible implementation manner of the first aspect, before the client sends a second migration request message to the participating server, the The method further includes that the client receives a first migration response message from the control server, and the first migration response message carries an identifier of the control server.

With reference to the first aspect or any one of the foregoing possible implementation manners of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes: the client sends a first revocation request to the control server Message, the first revocation request message carries the identity of the client and the identity of the participating server; the client sends a second revocation request message to the participating server, and the second revocation request message carries the The identity of the client and the identity of the control server.

In a second aspect, a communication method is provided. The method is applied to a client switching from a source system to a target system. The method includes: the client generates a second migration request message, where the second migration request message carries the migration request message. An identifier of the control server of the client in the source system and an identifier of the client; the client sends the second migration request message to a participating server of the client in the target system. The method realizes the migration of the client from the source system to the target system, that is, the client connects to the participating server in the target system, and the participating server continues to provide the group call service for the client to ensure the normal progress of the group call So that the group can maintain normal communication when the members of the group are provided with group communication services by different systems.

With reference to the second aspect, in a possible implementation manner of the second aspect, the second migration request message further carries an identifier of a group to which the client belongs.

According to a third aspect, a communication method is provided, including: a control server receiving a first migration request message, where the first migration request message carries an identifier of the client's participating server and an identifier of the client; the control server Sending downlink information of the client to the participating server according to the first migration request message. This method enables the control server to send the downlink information of the client to the participating server of the client after the migration, and achieves the successful migration of the client. For example, the client migrates from the source system to the target system, thereby ensuring the normal call of the group, so that the group maintains normal communication when the members of the group are provided with group communication services by different systems.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the first migration request message further carries an identifier of a group to which the client belongs, and the downlink information is downlink information of the group .

With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the method further includes: the control server, according to the first migration request message, The participating server sends a second migration request message, and the second migration request message carries an identifier of the control server and an identifier of the client.

With reference to the third aspect or any one of the foregoing possible implementation manners of the third aspect, in a third possible implementation manner of the third aspect, the method further includes: the control server receives a first revocation from the client A request message, where the first revocation request message carries the identity of the client's participating server and the identity of the client; the control server stops sending the client to the participating server according to the first revocation request message The downlink information.

With reference to the third possible implementation manner of the third aspect, in the fourth possible implementation manner of the third aspect, the first revocation request message also carries an identifier of a group to which the client belongs, and the downlink information is all The downlink information of the group is described.

According to a fourth aspect, a communication method is provided, including: a participating server receives a second migration request message, and the second migration request message carries an identifier of a control server of the client and an identifier of the client; the participating server Sending uplink information of the client to the control server according to the second migration request message. This method enables the participating server after the migration to send the uplink information of the client to the control server of the client, and realizes the successful migration of the client. For example, the client migrates from the source system to the target system, thereby ensuring the normal call of the group, so that the group can maintain normal communication when the members of the group provide group communication services from different systems.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the second migration request message further carries an identifier of a group to which the client belongs, and the uplink information is uplink information of the group .

With reference to the fourth aspect or the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the method further includes: the participating server, according to the second migration request message, The control server sends a first migration request message, and the first migration request message carries an identifier of the participating server and an identifier of the client.

With reference to the fourth aspect or any one of the foregoing possible implementation manners of the fourth aspect, in a third possible implementation manner of the fourth aspect, the method further includes: the participating server receives a second revocation from the client A request message, where the second revocation request message carries the identity of the client's control server and the client's identity; the participating server stops sending the client to the control server according to the second revocation request message Upstream information.

According to a fifth aspect, a communication device is provided, which includes units or means for performing each step of any one of the methods of the first aspect above.

According to a sixth aspect, a communication device is provided, including a processor and a memory. The memory is used to store a program, and the processor calls the program stored in the memory to execute any method in the first aspect above.

According to a seventh aspect, there is provided a communication device including at least one processing element or chip for performing any one of the methods of the above first aspect.

According to an eighth aspect, there is provided a program for executing any one of the methods of the first aspect when executed by a processor.

In a ninth aspect, a computer-readable storage medium is provided, including the program in the eighth aspect.

According to a tenth aspect, a communication device is provided, which includes units or means for performing each step of any of the methods of the second aspect above.

According to an eleventh aspect, a communication device is provided, which includes a processor and a memory. The memory is used to store a program, and the processor calls the program stored in the memory to execute any method in the second aspect above.

In a twelfth aspect, a communication device is provided, including at least one processing element or chip for performing any one of the methods in the second aspect above.

According to a thirteenth aspect, a program is provided for executing any method of the above second aspect when executed by a processor.

A fourteenth aspect provides a computer-readable storage medium including the program of the thirteenth aspect.

In a fifteenth aspect, a communication device is provided, which includes units or means for performing each step of any of the methods in the third aspect above.

According to a sixteenth aspect, a communication device is provided, which includes a processor and a memory. The memory is used to store a program, and the processor calls the program stored in the memory to execute any method in the third aspect above.

In a seventeenth aspect, a communication device is provided, including at least one processing element or chip for performing any one of the methods in the third aspect above.

In an eighteenth aspect, a program is provided that, when executed by a processor, executes any of the methods of the third aspect above.

A nineteenth aspect provides a computer-readable storage medium including the program of the eighteenth aspect.

In a twentieth aspect, a communication device is provided, which includes units or means for performing each step of any of the methods in the fourth aspect above.

According to a twenty-first aspect, a communication device is provided, which includes a processor and a memory. The memory is used to store a program, and the processor calls the program stored in the memory to execute any method in the fourth aspect above.

In a twenty-second aspect, there is provided a communication device including at least one processing element or chip for performing any one of the methods in the fourth aspect above.

In a twenty-third aspect, a program is provided, which when executed by a processor, executes any of the methods in the fourth aspect above.

In a twenty-fourth aspect, a computer-readable storage medium is provided, including the program in the twenty-third aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to explain the technical solutions in the embodiments of the present application more clearly, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings in the following description are some embodiments of the present application. Those skilled in the art can also obtain other drawings according to these drawings without paying creative labor.

FIG. 1a is a schematic structural diagram of a communication system; FIG.

FIG. 1b is a schematic structural diagram of a mission-critical system;

FIG. 1c is a schematic structural diagram of another communication system; FIG.

2 is a flowchart of a communication method according to an embodiment of the present application;

3 is a flowchart of another communication method according to an embodiment of the present application;

4 is a flowchart of another communication method according to an embodiment of the present application;

5 is a flowchart of another communication method according to an embodiment of the present application;

6 is a schematic diagram of a communication method according to an embodiment of the present application;

7 is a schematic diagram of another communication method according to an embodiment of the present application;

8 is a schematic diagram of another communication method according to an embodiment of the present application;

FIG. 9 is a schematic diagram of another communication method according to an embodiment of the present application; FIG.

FIG. 9a is a schematic diagram of another communication method according to an embodiment of the present application; FIG.

FIG. 9b is a schematic diagram of another communication method according to an embodiment of the present application; FIG.

10 is a schematic structural diagram of a communication device according to an embodiment of the present application;

11 is a schematic structural diagram of another communication device according to an embodiment of the present application;

FIG. 12 is a hardware structural diagram of a communication device according to an embodiment of the present application; FIG.

13 is a flowchart of another communication method according to an embodiment of the present application;

14 is a flowchart of another communication method according to an embodiment of the present application;

15 is a flowchart of another communication method according to an embodiment of the present application;

16 is a flowchart of another communication method according to an embodiment of the present application;

17 is a flowchart of another communication method according to an embodiment of the present application;

18 is a flowchart of another communication method according to an embodiment of the present application;

19 is a flowchart of another communication method according to an embodiment of the present application;

20 is a flowchart of another communication method according to an embodiment of the present application;

21 is a flowchart of another communication method according to an embodiment of the present application;

22 is a schematic structural diagram of another communication device according to an embodiment of the present application;

23 is a schematic structural diagram of another communication device according to an embodiment of the present application;

24 is a schematic structural diagram of another communication device according to an embodiment of the present application;

25 is a schematic structural diagram of another communication device according to an embodiment of the present application;

26 is a schematic structural diagram of another communication device according to an embodiment of the present application;

27 is a schematic structural diagram of another communication device according to an embodiment of the present application;

FIG. 28 is a schematic structural diagram of another communication device according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. FIG. 1b provides a schematic structural diagram of a mission critical (MC) system. This structure can be applied to 2G, 3G, 4G, 5G or next-generation communication systems without limitation. The following briefly introduces each component of the structure:

Service control server (hereinafter referred to as the control server), that is, the user's service control server, which is responsible for the user's group communication or private communication service control server, and is responsible for the call control anchor point. Ruling.

The user participation server (hereinafter referred to as the participation server), that is, the user's registration server, is used for user addressing, routing the user's uplink information (for example, signaling, data, or media) to the control server, and will Downlink information (eg, signaling, data, or media) is sent to the user.

The configuration management server is responsible for issuing user configuration data and service configuration data.

Terminals, including various handheld devices with wireless communication capabilities, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of terminals, mobile stations (MS), and user equipment (user equipment, UE), soft terminals, etc., such as water meters, electricity meters, sensors, etc.

In Figure 1b, the terminal and the participating server can communicate through the access network and the core network. Among them, the access network and core network part may adopt 2G, 3G, 4G, 5G or next-generation communication technologies, for example, the access network and core network in the prior art.

Figure 1c shows another communication system. The communication system includes: a macro MC system and an IOPS MC system. Among them, macro MC system refers to MC system based on macro network. IOPS MC system is a public safety emergency system based on IOPS network and a simplified mobile communication system designed for emergency communication. IOPS MC system can provide communication services for public safety users (such as police, firefighters, medical personnel, etc.), such as mission-critical push-to-talk (MCPTT), MCVideo, MCData. Both IOPS MC system and macro MC system can be based on the system architecture diagram shown in Figure 1b.

In Figure 1c, 4G communication technology is taken as an example. The base station eNB-1 is connected to the core network in the macro MC system (see line 1 in Figure 1c), and is also connected to the core network in the IOPS MC system (see line 2 in Figure 1c). The base station eNB-2 is connected to the core network in the macro MC system (line 1), and is also connected to the core network in the IOPS MC system (line 2). When the link between eNB-1, eNB-2 and the core network in the macro MC system is normal, the macro MC system provides group communication services for members in the group (that is, line 1); when eNB-1, When the link between the eNB-2 and the core network in the macro MC system is broken, the IOPS MC system continues to provide communication services for members in the group (ie, line 2).

Among them, the base station can also be called an access network node, which provides network access functions for authorized users in a specific area, and can use different quality transmission tunnels according to the user level and business needs.

The terms involved in the application examples are described below, as follows.

The client can be an application or a functional module running on the terminal, or it can be an independent device. A client can only allow one user to log in at any time, that is, the client and the user can correspond one-to-one.

The group to which the client belongs can refer to the group to which the user who accesses the system through the client belongs.

Users can interact with the application server in the network through the client.

Public safety users, belonging to a category of users (such as police, firefighters, medical rescue personnel, etc.), can interact with mission-critical servers through clients to implement public safety services, such as registration of public safety users, service authentication and authorization, and Call, group call, etc. At this point, the client can be called a mission critical client (MC client).

The source system and the target system are for the client or the user corresponding to the client. The source system may refer to a system that currently provides services to a client, and the target system may refer to a system that is about to provide services to the client. For example, when the source system is a macro MC system as shown in Figure 1c, the target system may be an IOPS MC system without pre-limitation.

Control server, see the control server in Figure 1b. Specifically, the control server may be a mission-critical control server (controlling MC server), for example, controlling MCPTT server, controlling MCVideo server, or controlling MCData server. Further, the control server of the client may refer to a control server that provides services to the client or a user corresponding to the client, for example, the control server sends the downlink information of the client to the client's participating server so that the client The participating server of the client sends downlink information to the client.

Participation server, see the participation server in Figure 1b. Specifically, the participating server may be a mission-critical participating server (participating MC server), for example, participating MCPTT server, participating MCVideo server, or participating MCData server. Further, the client's participating server may refer to a participating server that provides services to the client or a user corresponding to the client. For example, the participating server receives the uplink information of the client and sends the uplink information to the client. server.

The uplink information of the client indicates the information that the user sends to the network through the client.

The downlink information of the client refers to the information sent by the network to the user through the client.

Among them, the uplink information and the downlink information may include signaling, voice, video, or data, etc., without limitation.

It should be noted that "a plurality" means two or more. The words "first" and "second" do not limit the number and execution order, and "first" and "second" do not limit the functions of messages or information, for example, they are only used to distinguish different messages. "/" Means "or", for example, A / B can mean A or B. "And / or" in this article is just an association relationship describing the associated objects, which means that there can be three kinds of relationships, for example, A and / or B, can mean: A exists alone, A and B exist simultaneously, and B exists alone These three situations.

As shown in FIG. 2, a communication method provided in an embodiment of the present application may be applied to a client switching, migrating, or redirecting from a source system to a target system, as described below.

201. The client generates a first migration request message.

The first migration request message carries the identity of the client participating server in the target system and the identity of the client. The first migration request message may be used to request or notify the client to migrate, switch, or redirect to the participating server in the target system, so that the participating server in the target system provides a communication service for the client. In other words, the first migration request message may be used to request that a participating server of a client in a target system provide a communication service for the client. For example, the control server of the client in the source system sends the downlink information of the client to the participating server, and the participating server sends the downlink information to the client.

It should be noted that the first migration request message may specifically be a participating server migration request. The names of the messages are not limited in the embodiments of the present application, and may be replaced with messages having the same or similar functions. For example, the migration request message may be replaced with a redirect request message, or a switch request message, etc .; accordingly, the migration response message may be replaced with a redirect response message, or a switch response message. In each embodiment of the present application, a migration request message is used as an example for description.

The identity of the participating server is used to identify the participating server, for example, the IP address of the participating server, a fully qualified domain name (FQDN), or the uniform resource identifier of the session initiation protocol (uniform resource identifier, SIP). URI), etc.

Optionally, step 201 includes the client acquiring the identity of the client's participating server in the target system, and generating a first migration request message according to the identity of the client's participating server. The client can obtain the identity of the client's participating server in the target system in the following ways:

In addition, the identity of the participating server may be configured on the terminal in advance, or may be obtained from the configuration management server after the user and the MC system perform authorization and identity authentication.

Exemplarily, the first migration request message is a session initiation protocol (SIP) message. At this time, the first migration request message carries the SIP URI of the participating server. Among them, the SIP URL is a format of the Public Service Identity (PSI) of the participating server, and is used to identify the participating server and the route of the message. The client can find the SIP URI of the participating server from the domain name system (DNS) or MC system according to the IP address of the participating server.

The identity of the client is used to identify the client or a user accessing the network through the client, which may be the identity of the client, and the identity of the user accessing the network through the client (for example, the identity of a public safety user) , Or Functional Alias. For example, MCPTT ID, MCVideo ID, MCData ID, MC ID, etc. Another example is username1@mcptt.homeoffice.com.

202. The client sends a first migration request message to a control server of the client in the source system.

Correspondingly, the client may also receive a first migration response message sent by the control server to respond to the first migration request message.

Exemplarily, assuming that the target system is a macro MC system, and the link between the base station and the core network in the macro MC system returns to normal, the base station broadcasts the network identification of the target system. After the terminal monitors the broadcast message, Notify the client on the terminal that the terminal can switch to the target system.

In one implementation, after the client learns that the link of the target system is back to normal, the client can send a human-machine interface prompt message to the user using the terminal, and ask the user whether to switch the client to the target system. When the user chooses to switch to the target system and the client's group call has not ended, the client can further ask whether the user chooses to hold the group call. If the user chooses to hold the group call, the client can perform step 201- 202.

In another implementation manner, when the client learns that the link of the target system returns to normal and the group call of the client has not ended, the client may directly perform steps 201-202.

In yet another implementation, the client can report information about the current access network (for example, access through an IOPS network or access through a macro network), and the control server can collect the members of the group to which the client belongs. Send information about the current network to this client. The client can present this information to the user so that the user can decide whether to hold the group call. If the user chooses to hold the group call, the client may perform steps 201-202.

The group call of the client refers to a call of a group to which a user who communicates with the network through the client belongs.

Optionally, the first migration request message further carries an identifier of a group to which the client belongs. At this time, the first migration request message is also used to request that the participating server of the client in the target system provide communication services for the client belonging to the group, for example, the participating server sends the client to the uplink of the group The information is transmitted to the control server, or the participating server sends the downlink information in the group to the client. By carrying the identifier of the group to which the client belongs in the first migration request message, the client in the specified group is migrated from the source system to the target system.

The identifier of the group may be the name of the group, or the ID of the group, that is, MC group ID, MCPTT group ID, MCVideo group ID, or MCData group ID. For example, group1@mcptt.homeoffice.com, or group2@mcptt.fireplace.homeoffice.com. When the client belongs to two or more groups, the identifier of the group carried in the first migration request message may be one or more, and the one or more group identifiers are the groups selected by the user to keep the group call. The identity of the group may also be the identity of the group with a high priority, or the identity of the group corresponding to the group call currently being performed by the client. Among them, the high-priority group may refer to a group related to public safety, for example, fire safety, emergency rescue, or medical assistance; it may also be set by an operator without restriction.

It should be noted that the first migration request message may be used by the control server to send a second migration request message to the participating server. The second migration request message may carry the identity of the control server and the identity of the client. The second migration request message may be used to request the participating server to migrate, switch or redirect the control server of the client to the control server corresponding to the identity of the control server in the second migration request message, so that the participating server can transfer the The downlink information received by the control server corresponding to the identifier is sent to the client, or the uplink information sent by the client is sent to the control server corresponding to the identifier of the control server, and the group call of the client is maintained. In other words, the second migration request message may be used to request that the control server corresponding to the identity of the control server in the second migration request message provide a routing service for the client. Obviously, the client may also send a second migration request message to the participating server. In addition, the second migration request message may be a control server migration request message, which is not limited.

The control server sends a second migration request message to the participating server according to the first migration request, and the second migration request message from the client to the participating server may be the same or different, and is not limited. Even if the two are different, the two also have the above-mentioned function, which is to request the participating server to migrate, switch or redirect the control server of the client to the control server corresponding to the control server identifier in the second migration request message, so that The participating server can send the downlink information received from the control server to the client, which is not described again.

The identifier of the control server may be the IP address, FQDN, or SIP URI of the control server.

Optionally, the method further includes: the client sends a second migration request message to the participating server.

The second migration request message may carry the identity of the control server and the identity of the client.

Exemplarily, the client may obtain the identity of the control server in the following manner.

Manner 1: The identifier of the control server is pre-configured on the terminal.

Method 2: After the user and the MC system perform authorization and identity authentication, the client obtains the configuration management server.

Manner 3: The client receives a first migration response message from the control server, and the first migration response message carries an identifier of the control server.

The first migration response message may be used to respond to the first migration request message. Obviously, the first migration response message may also be replaced with other messages without limitation.

In addition, the second migration request message may also carry the identifier of the group to which the client belongs. The second migration request message is further specifically used to request the participating server to migrate the control server of the client of the group, switch or redirect to the control server corresponding to the identity of the control server in the second migration request message. For example, when the user corresponding to the client belongs to multiple groups, the second migration request message carries the identifier of the group to implement the request to migrate the control server of the client in the specified group.

With the method provided in this embodiment, the client generates a first migration request message and sends the first migration request message to the control server of the client in the source system, thereby realizing the migration of the client from the source system to the target system, that is, the client Connect to the participating server in the target system, and the participating server will continue to provide the group call service for the client to ensure the normal progress of the group call, so that members in the group can provide group communication services from different systems The group can maintain normal communication.

It should be noted that the first migration request message in the embodiments of the present application may be a first notification message for notifying the control server of the source system of the client ’s participating server identification in the target system to which the client migrates. The second migration request message may be a second notification message, which is used to notify the client ’s participating server in the target system of the client ’s identification of the control server in the source system.

Optionally, in an implementation scenario of the foregoing method, the implementation scenario may be for the user corresponding to the client to opt out of the group call or the group call of the client ends, the method further includes: the client sends A first revocation request message, and sending a second revocation request message to the participating server.

The first revocation request message may carry the identity of the client and the identity of the participating server; the first revocation request message may be used to request revocation of the participation corresponding to the identity of the client that is migrated, switched, or redirected to the participating server The server, in other words, requests to revoke that the participating server corresponding to the identity of the participating server in the first revocation request message provides the client with a communication service.

The second revocation request message may carry the identity of the client and the identity of the control server; the second revocation request message may be used to request the participating server to revoke the client ’s control server, switch or redirect to the identity server of the control server The corresponding control server, in other words, requests the revocation to provide a routing service for the client by the control server corresponding to the identification of the control server in the second revocation request message.

The method provided in this implementation scenario enables flexible switching or transfer of clients between different systems to adapt to changes in the network environment and can greatly improve the reliability of group calls.

As shown in FIG. 3, another communication method provided by an embodiment of the present application may be applied to a client switching from a source system to a target system, as described below.

301: The client generates a second migration request message.

The second migration request message carries the identifier of the control server of the client and the identifier of the client in the source system. For details, refer to related descriptions in the embodiment shown in FIG. 2, and details are not described herein again.

302. The client sends a second migration request message to the client's participating server in the target system.

Correspondingly, the client may also receive a second migration response message sent by the participating server to respond to the second migration request message.

Optionally, the second migration request message also carries the identifier of the group to which the client belongs. For details, refer to related descriptions in the embodiment shown in FIG. 2, and details are not described herein again.

It should be noted that the second migration request message may be used by the participating server to send the first migration request message to the control server, and the first migration request message carries the identifier of the client and the identifier of the participating server.

The first migration request message may be the same as or different from the first migration request message sent by the client in the embodiment shown in FIG. 2. Even if the two are different, the two have the same or similar function, which is to request the client to be migrated, switched, or redirected to the participating server in the target system, so that the participating server in the target system provides communication for the client service. For the first migration request message, reference may be made to related descriptions in the embodiment shown in FIG. 2, and details are not described herein again.

With the method provided in this embodiment, migration, switching, or redirection of the client's participating control server can be achieved, so that the client's participating server in the target system can send the client's uplink information to the client's control server in the source system . The method realizes the migration of the client from the source system to the target system, that is, the client connects to the participating server in the target system, and the participating server continues to provide the group call service for the client to ensure the normal progress of the group call So that the group can maintain normal communication when the members of the group are provided with group communication services by different systems.

As shown in FIG. 4, another communication method provided by an embodiment of the present application is as follows.

401. The control server receives a first migration request message.

The first migration request message carries the identity of the client's participating server and the identity of the client. For details, refer to related descriptions in the embodiment shown in FIG. 2, and details are not described herein again.

Exemplarily, in step 401, the control server may receive the first migration request message from the client, or may receive the first migration request message from the participating server without limitation.

402. The control server sends downlink information of the client to the client's participating server according to the first migration request message.

Exemplarily, the control server identifies the downlink information sent to the client according to the identifier of the client in the first migration request message, and sends the downlink information of the client to the participating server corresponding to the identifier of the participating server, so as to facilitate the participating server Send the downlink information to the client.

Optionally, the first migration request message further carries an identifier of a group to which the client belongs, and the downlink information is downlink information of a group corresponding to the identifier of the group.

It should be noted that the above control server may refer to the control server of the client in the source system, and the participating server is the participating server of the client in the target system.

Optionally, the method further includes: the control server sends a second migration request message to the participating server according to the first migration request message.

The second migration request message carries an identifier of the control server and an identifier of the client, and may also carry an identifier of a group to which the client belongs. For details, refer to related descriptions in the embodiment shown in FIG.

Correspondingly, the participating server sends the uplink information of the client to the control server according to the second migration request message, thereby achieving successful migration of the client.

Optionally, the method further includes: the control server sends a first migration response message to respond to the received first migration request message.

With the method provided in this embodiment, the control server receives the first migration request message and sends the client's downlink information to the client's participating server according to the first migration request message, so that the control server can send the client's downlink information to the migration After the client's participating server, the client successfully migrated. For example, the client migrates from the source system to the target system, thereby ensuring the normal progress of the group call, so that the group maintains normal communication when the members of the group are provided with group communication services by different systems.

Optionally, the method further includes: the control server receives the first revocation request message from the client, and stops sending downlink information of the client to the participating server according to the first revocation request message.

The first revocation request message carries the identity of the client's participating server and the identity of the client. For details, refer to the related description in the embodiment shown in FIG. 2.

Further, the first revocation request message may further carry an identifier of a group to which the client belongs. Correspondingly, the control server stops sending downlink information of the group to the participating server according to the first revocation request message. The first cancellation request message enables the client's participating server to flexibly switch or transfer to adapt to changes in the network environment, which can greatly improve the reliability of group calls.

Optionally, step 402 is replaced with or the above method further includes: the control server saves the downlink routing information of the client according to the first migration request message. Further, the above method may further include: when the group call of the client ends, the control server deletes the downlink routing information of the client.

The downlink routing information may include an identifier of the participating server.

It should be noted that the control server in the embodiments shown in FIG. 4 and FIG. 5 may refer to the control server of the client in the source system, and the participating server is the participating server of the client in the target system.

As shown in FIG. 5, another communication method provided by an embodiment of the present application is as follows.

501. A participating server receives a second migration request message.

The second migration request message carries the identity of the client's control server and the identity of the client. For details, refer to the related description in the embodiment shown in FIG. 2.

Exemplarily, in step 501, the participating server may receive the second migration request message from the client, or may receive the second migration request message from the control server, without limitation.

The participating server is a migrated participating server, and the participating server is located on the target system.

502. The participating server sends uplink information of the client to the control server according to the second migration request message.

The control server in step 502 is the control server corresponding to the identification of the control server in the second migration request message.

Exemplarily, the participating server identifies the uplink information sent by the client according to the identifier of the client in the second migration request message, and sends the uplink information of the client to the control server corresponding to the identifier of the control server, so as to facilitate the control server Send the uplink information to other members in the group to which the client belongs.

The second migration request message may also carry the identifier of the group to which the client belongs, as described in the related description in the embodiment shown in FIG. 2. Accordingly, the uplink information may be uplink information of the group.

Optionally, step 502 is replaced by: the participating server saves the uplink routing information of the client according to the second migration request message. Further, the above method may further include: when the group call of the client ends, the participating server deletes the uplink routing information of the client. The uplink routing information may include an identifier of the control server.

Optionally, the method further includes: the participating server sends a first migration request message to the control server according to the second migration request message.

The first migration request message carries the identifier of the participating server and the identifier of the client. For details, refer to related descriptions in the embodiment shown in FIG. 2. In addition, the first migration request message may be the same as or different from the first migration request message sent by the client in the embodiment shown in FIG. 2, and even if the two are different, they also have the same or similar functions.

Exemplarily, after receiving the second migration request message, the participating server sends a first migration request message to the control server corresponding to the control server identifier in the second migration request message, where the first migration request message carries the second migration The identity of the client in the request message and the identity of the participating server.

Correspondingly, the control server sends the downlink information of the client to the participating server according to the first migration request message, thereby achieving successful migration of the client.

Optionally, the method further includes: the participating server sends a second migration response message to respond to the received second migration request message.

With the method provided in this embodiment, the participating server receives the second migration request message and sends the client's uplink information to the control server according to the second migration request message, so that the migrated participating server can send the client's uplink information to the client. The control server at the end realizes the successful migration of the client. For example, the client migrates from the source system to the target system, thereby ensuring the normal progress of the group call, so that the group can maintain normal communication when the members of the group are provided with group communication services by different systems.

Optionally, in an implementation scenario of the foregoing embodiment, the method further includes: the participating server receives a second revocation request message from the client, and stops sending the second revocation request message to the client's control server according to the second revocation request message. Upstream information of the client.

The second revocation request message carries the identity of the client's control server and the identity of the client.

As shown in FIG. 6, another communication method provided by an embodiment of the present application is as follows.

601. The client sends a first migration request message to a control server of the client in the source system.

The first migration request message carries the identifier of the participating server and the identifier of the client. For details, refer to related descriptions in the embodiment shown in FIG. 2, and details are not described herein again.

602. The control server receives the first migration request message, and sends downlink information of the client to the client's participating server according to the first migration request message.

Optionally, the method further includes: the control server sends a first migration response message to the client.

603. The client sends a second migration request message to the client's participating server in the target system.

604. The participating server receives the second migration request message, and sends uplink information of the client to the control server according to the second migration request message.

Optionally, the above method further includes: the participating server sends a second migration response message to the client.

It should be noted that the execution order of the above steps is not limited.

With the method provided in this embodiment, the client sends a first migration request message to a control server of the client in the source system, and the client sends a second migration request message to a participating server of the client in the target system. The method realizes the migration of the client from the source system to the target system, that is, the client connects to the participating server in the target system, and the participating server continues to provide the group call service for the client to ensure the normal progress of the group call So that the group can maintain normal communication when the members of the group are provided with group communication services by different systems.

As shown in FIG. 7, another communication method provided by an embodiment of the present application is as follows.

701. The client sends a first migration request message to a control server of the client in the source system.

Accordingly, the control server receives the first migration request message.

702. The control server sends downlink information of the client to a participating server of the client in the target system according to the first migration request message.

703. The control server sends a second migration request message to the participating server of the client in the target system according to the first migration request message.

704. The participating server receives the second migration request message, and sends uplink information of the client to the control server of the client in the source system according to the second migration request message.

Optionally, the method further includes: the participating server sends a second migration response message to the control server.

It should be noted that the execution order of the above steps is not limited.

With the method provided in this embodiment, the client sends a first migration request message to the control server of the client in the source system, and the control server sends a second migration request message to the client's participating server in the target system according to the first migration request message. The method realizes the migration of the client from the source system to the target system, that is, the client connects to the participating server in the target system, and the participating server continues to provide the group call service for the client to ensure the normal progress of the group call So that the group can maintain normal communication when the members of the group are provided with group communication services by different systems.

As shown in FIG. 8, another communication method provided by an embodiment of the present application is as follows.

801. The client sends a second migration request message to the client's participating server in the target system.

The identifier of the control server of the client and the identifier of the client are carried in the second migration request message. For details, reference may be made to the related description in the embodiment shown in FIG.

Accordingly, the participating server receives the second migration request message.

802. The participating server sends uplink information of the client to the control server of the client in the source system according to the second migration request message.

803. The participating server sends a first migration request message to the control server of the client in the source system according to the second migration request message.

The first migration request message carries the identity of the client's participating server and the identity of the client in the source system. For details, refer to related descriptions in the embodiment shown in FIG. 2, and details are not described herein again.

804. The control server receives the first migration request message, and sends downlink information of the client to the participating server of the client in the target system according to the first migration request message.

Optionally, the method further includes: the control server sends a first migration response message to the participating server.

It should be noted that the execution order of the above steps is not limited.

As shown in FIG. 9, another communication method provided by an embodiment of the present application is as follows.

901. The client sends a first revocation request message to a control server of the client in the source system.

The first revocation request message may carry the identity of the client and the identity of the client ’s participating server in the target system; the first revocation request message may be used to request revocation of the client ’s migration, switching, or redirection to the participating server. For the identification of the participating server, refer to the related description in the embodiment shown in FIG. 2.

902. The control server receives the first revocation request message, and stops sending downlink information of the client to the participating server of the client in the target system according to the first revocation request message.

The downlink information of the client may be downlink information of a group to which the client belongs.

Optionally, the method further includes: the control server sends a first revocation response message to the client.

903. The client sends a second revocation request message to the participating server.

The second revocation request message may carry the identity of the client and the identity of the client ’s control server; the second revocation request message may be used to request the participating server to revoke the client ’s control server, switch or redirect it to the control server For the control server corresponding to the identifier, refer to the related description in the embodiment shown in FIG. 2.

904. The participating server receives the second revocation request message, and stops sending uplink information of the client to the control server according to the second revocation request message.

The downlink information of the client may be uplink information sent by the client to a group to which the client belongs.

Step 902 may refer to the related description in the embodiment shown in FIG. 4, and step 904 may refer to the related description in the embodiment shown in FIG. 5, which is not described repeatedly.

Optionally, the above method further includes: the participating server sends a second revocation response message to the client.

It should be noted that the execution order of the above steps is not limited. Steps 901-904 may be performed on the basis of any of the embodiments shown in Figs. 6-8. For example, after steps 604, 704, or 804 and after the group call of the client ends, there is no restriction.

With the method provided in this embodiment, the client sends a first revocation request message to the client's control server in the source system, and the client sends a second revocation request message to the client's participating server in the target system, which enables the client to Flexible switching or transfer between systems to adapt to changes in the network environment can greatly improve the reliability of group calls.

It should be noted that, in the embodiment shown in FIG. 6-8, sending the client's downlink information to the client's participating server according to the first migration request message can be replaced by storing the client's downlink route according to the first migration request message. For information, refer to related descriptions in the embodiment shown in FIG. 4. Correspondingly, step 902 may be replaced by: the control server receives the first revocation request message, and deletes the downlink routing information of the client according to the first revocation request message.

In addition, sending the uplink information of the client to the control server according to the second migration request message may be replaced by storing the uplink routing information of the client according to the second migration request message. For the related description in the embodiment shown in FIG. 5. Correspondingly, step 904 may be replaced by: the participating server receives the second revocation request message, and deletes the uplink routing information of the client according to the second revocation request message.

As shown in FIG. 9a, another communication method provided by an embodiment of the present application may be applied to a link between a base station and a core network in a target system to be restored to normal, the client is ready to switch to the target system, and the client group When the group call is not ended. The details are as follows.

901a: The client sends a connection status report (connections status report) message to the first control server.

The first control server is located in the source system and provides communication services for the client.

The connection status report message may carry the identity of the client and the identity of the participating server of the client in the target system. For a manner of obtaining the identifier of the participating server, refer to related descriptions in the embodiment shown in FIG. 2.

Further, the connection status report message may also carry an identifier of a group to which the client belongs, or an identifier of a client's control server (referred to as a second control server) in the target system.

Further, the connection status report message may also carry network type information currently accessed by the client, and the network type information may be an IOPS network or a macro network.

Further, the connection status report message may also carry network type information that the client is allowed to access, and the network type information may be an IOPS network, or a macro network, or both.

The identifier of the second control server may be pre-configured on the client, or the group may be obtained from the client's participating server in the target system based on the identifier of the client's participating server in the target system and the group to which the client belongs. The identity of the group's control server in the target system.

902a: The first control server determines to switch the group call of the client to the second control server according to the connection status report message.

The switching of the group call of the client to the second control server may refer to the control server of the client being migrated from the source system to the target system, or the control server in the target system to provide routing services for the client.

For example, if the member of the group to which the client belongs to which the connection to the target system returns to normal exceeds a set threshold, it is determined that the group call of the client is switched to the target system. For another example, if a key member (for example, the member with the highest priority) in the group to which the client belongs returns to the target system, it is determined that the group call is switched to the target system.

The first control server receives the connection status report message reported by the client, which can indicate that the connection between the client and the target system returns to normal, that is, the link between the base station serving the client and the core network in the target system is restored. normal. In addition, the first control server may determine that the connection between the client and the target system returns to normal by using the identifier of the participating server in the connection status report message; it may also report the network type information and / or the client currently accesses in the connection status report message Information about the network type that the client is allowed to access to determine that the client's connection to the target system is back to normal without restrictions.

903a. The first control server sends a participating server migration request (participating server migration request) to the second control server.

The migration request of the participating server may carry the identifier of the client that is not connected to the target system, and the identifier of the participating server in the source system that is not connected to the target system. Exemplarily, when the participating server migration request carries the identities of multiple clients, the participating server migration request also carries the identities of the participating servers of each client in the source system.

Among them, the clients that are not connected to the target system may include clients that are served by the base station whose links to the core network in the target system have not recovered normally, or clients that choose not to switch to the target system, etc., without restriction .

Further, the participating server migration request may also carry the identifier of the group to which the client that is not connected to the target system belongs. Correspondingly, when there is downlink information to be sent to the group on the control server of the client in the target system, the control server of the client in the target system sends the downlink information to the participating server corresponding to the identity of the participating server in the participating server migration request.

904a. The first control server sends a control server migration request to a participating server in the source system of a client that is not connected to the target system.

The control server migration request may carry an identifier of a client that is not connected to the target system and an identifier of the second control server.

Further, the identifier of the group to which the client belongs may also be carried. Correspondingly, according to the control server migration request, the participating server sends the uplink information that the client received to the group to the second control server.

Among them, steps 903a-904a are optional steps, for example, they are not performed in a scenario where members of the group can all connect to the target system.

905a. The first control server instructs the client to switch to the target system.

Exemplarily, the first control server sends instruction information or an instruction message to the client. For example, a service redirect request for instructing a client to switch to a target system. The service redirection request may carry a handover instruction or an identifier of a group to which the client belongs.

906a: The client accesses the target system according to the instruction.

Exemplarily, the client is connected to the client's participating server in the target system.

The instruction may be instruction information or an instruction message in step 905a.

907a: The first control server sends context information of the group call to the second control server.

The context information may include: current speaker, members participating in the group call, and voice right queue information.

Exemplarily, the context information may be carried in a communication context synchronization (communication context synchronization) message for synchronizing the context of a group call.

It should be noted that the execution order of the above steps is not limited.

By using the method provided in this embodiment, the group call of the client is switched from the control server in the source system to the control server in the target system, and the normality of the group call is ensured in the migration scenario of the control server of the group call get on.

As shown in FIG. 9b, another communication method provided in the embodiment of the present application may be applied to a link between the base station and the core network in the target system to be restored to normal, the client is ready to switch to the target system, and the client group When the group call is not ended. The details are as follows.

901b. The client sends a participating server request to the control server in the source system.

Among them, the participating server request request is used to notify the client that the participating server has changed, and it can also be said that the participating server of the user corresponding to the client has changed. Specifically, the participating server request can carry the identity of the client and the identity of the participating server in the target system.

In addition, the request message may also carry the identity of the group to which the client belongs in group communication.

902b. The control server in the source system sends a participating server response to the client.

903b: The control server in the source system sets the participating server of the client as the participating server in the target system according to the participating server and migration request.

904b. The control server in the source system sends a control request to a participating server in the target system.

Among them, the controlling server request can carry the identity of the client and the identity of the control server in the source system.

905b. The participating server in the target system sends a control server response to the control server.

906b. The participating server in the target system sets the control server of the client as the control server in the source system according to the control server and the migration request.

Optionally, when the group to which the client belongs has downlink information, the above method further includes step 907b. Alternatively, when the client sends uplink information to the group, the above method further includes step 908b.

907b: The control server in the source system sends downlink information to the participating servers in the target system.

908b. The participating server in the target system sends uplink information to the control server in the source system.

It should be noted that steps 902b and 905b are optional steps. In addition, the execution order of the steps in the above embodiment is not limited.

As shown in FIG. 10, an embodiment of the present application provides a schematic composition diagram of a communication device. The device may be used to perform actions of a client in the foregoing method embodiments. The device may be a client, or may be located on the client or A chip on a terminal, a system on a chip, or a functional module. The device includes: a processing unit 1001 and a sending unit 1002.

The processing unit 1001 is configured to generate a first migration request message, where the first migration request message carries an identifier of a client server in a target system and an identifier of the client.

The sending unit 1002 is configured to send the first migration request message generated by the processing unit 1001 to a control server of the client in the source system.

Optionally, the sending unit 1002 is further configured to send a second migration request message to the participating server, where the second migration request message carries an identifier of the control server and an identifier of the client.

The second migration request message may further carry an identifier of a group to which the client belongs.

Optionally, the communication device further includes a receiving unit, configured to receive a first migration response message from the control server, where the first migration response message carries an identifier of the control server.

Optionally, the sending unit 1002 is further configured to:

Sending a first revocation request message to the control server, where the first revocation request message carries an identifier of the client and an identifier of the participating server;

Sending a second revocation request message to the participating server, where the second revocation request message carries an identifier of the client and an identifier of the control server.

By adopting the communication device provided in this embodiment, the first migration request message is generated and the first migration request message is sent to the control server of the client in the source system, thereby realizing the migration of the client from the source system to the target system, that is, the client connection To the participating server in the target system, and the participating server continues to provide the group call service for the client, ensuring the normal progress of the group call, so that in the case that the members in the group are provided with the group communication service by different systems This group is able to maintain normal communication.

Based on the schematic structural diagram shown in FIG. 10, an embodiment of the present application further provides another communication device. The device may be used to perform actions of a client in the foregoing method embodiments. The device may be a client or a client A chip on a terminal or terminal, a system on a chip, or a functional module. The device includes: a processing unit 1001 and a sending unit 1002.

The processing unit 1001 is configured to generate a second migration request message, where the second migration request message carries the identifier of the control server of the client in the source system and the identifier of the client.

The sending unit 1002 is configured to send the second migration request message generated by the processing unit 1001 to a participating server of the client in the target system.

The communication device provided in this embodiment is used to implement the migration, switching, or redirection of the client's participating control server, so that the client's participating server in the target system can send the client's uplink information to the client's control server in the source system. In this way, the migration of the client from the source system to the target system is achieved, that is, the client connects to the participating server in the target system, and the participating server continues to provide group calling services for the client, ensuring the normal group calling It is performed so that the group can maintain normal communication when the members of the group are provided with group communication services by different systems.

As shown in FIG. 11, an embodiment of the present application provides a schematic structural diagram of another communication device. The device may be used to perform actions of a control server in the foregoing method embodiments. The device may be a control server or a control server. A chip on a server, a system on a chip, or a functional module. The device includes a receiving unit 1101 and a processing unit 1102.

The receiving unit 1101 is configured to receive a first migration request message, where the first migration request message carries an identifier of a client's participating server and an identifier of the client.

The processing unit 1102 is configured to send downlink information of the client to the participating server according to the first migration request message.

Optionally, the first migration request message further carries an identifier of a group to which the client belongs, and the downlink information is downlink information of the group.

Optionally, the processing unit 1102 is further configured to send a second migration request message to the participating server according to the first migration request message, where the second migration request message carries the identifier and The identity of the client.

Optionally, in a scenario of the foregoing embodiment, the receiving unit is further configured to receive a first revocation request message from the client, where the first revocation request message carries an identifier of the client's participating server and An identification of the client; the processing unit is further configured to stop sending downlink information of the client to the participating server according to the first revocation request message.

Further optionally, the first revocation request message further carries an identifier of a group to which the client belongs, and the downlink information is downlink information of the group.

By adopting the communication device provided in this embodiment, by receiving the first migration request message and sending the client's downlink information to the client's participating server according to the first migration request message, the control server can send the client's downlink information to the migrated server. The client's participating server realized the successful migration of the client. For example, the client migrates from the source system to the target system, thereby ensuring the normal progress of the group call, so that the group can maintain normal communication when the members of the group are provided with group communication services by different systems.

Based on the composition diagram shown in FIG. 11, this embodiment of the present application further provides another communication device. The device may be used to perform the action of the participating server in the foregoing method embodiments. The device may be a participating server, or may be located at Participate in chips on the server, system-on-chip, or functional modules. The device includes a receiving unit 1101 and a processing unit 1102.

The receiving unit 1101 is configured to receive a second migration request message, where the second migration request message carries an identifier of a control server of a client and an identifier of the client.

The processing unit 1102 is configured to send uplink information of the client to the control server of the client according to the second migration request message.

Optionally, the second migration request message further carries an identifier of a group to which the client belongs, and the uplink information is uplink information of the group.

Optionally, the processing unit 1101 is further configured to send a first migration request message to the control server according to the second migration request message, where the first migration request message carries the identifier of the participating server and the The identity of the client.

Optionally, in a scenario of the foregoing embodiment, the receiving unit is further configured to receive a second revocation request message from the client, where the second revocation request message carries an identifier and An identification of the client; the processing unit is further configured to stop sending uplink information of the client to the control server according to the second revocation request message.

Further optionally, the second revocation request message further carries an identifier of a group to which the client belongs, and the uplink information is uplink information of the group.

The communication device provided in this embodiment receives the second migration request message and sends the uplink information of the client to the control server according to the second migration request message, so that the migrated participating server can send the client's uplink information to the client. The control server at the end realizes the successful migration of the client. For example, the client migrates from the source system to the target system, thereby ensuring the normal progress of the group call, so that the group maintains normal communication when the members of the group are provided with group communication services by different systems.

As shown in FIG. 12, an embodiment of the present application provides a schematic diagram of a hardware structure of a communication device. The communication device includes a processor 1201 (eg, processor 12011, processor 12012), a communication bus 1202, and a memory 1203.

The memory 1203 is configured to store a computer execution instruction for executing the solution of the present application, and the processor 1201 controls the execution.

The processor 1201 is configured to execute computer execution instructions stored in the memory 1203 to implement the methods provided by the embodiments of the present application. Specifically, the processor 1201 may be used to execute actions of a client, a control server, or a participating server, for example, in a source system The action of the client participating in the server, or the action of the client participating in the server in the target system.

The communication bus 1202 is configured to communicate between the components to transmit information.

Optionally, the above communication device further includes at least one communication interface 1204.

The communication interface 1204 is configured to communicate with other devices, chips, components, or a communication network. Specifically, any device such as a transceiver can be used, such as Ethernet, RAN node, wireless local area networks (WLAN), or radio frequency interface.

Among them, the processor 1201 may be one or more general-purpose central processing units (CPUs), microprocessors, application-specific integrated circuits (ASICs), or one or more for controlling the Integrated circuit for application program execution. As an implementation manner, the processor 1201 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 12. The processor 1201 may be a single-core (single-CPU) processor, or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

The memory 1203 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM), or other types that can store information and instructions The dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM-ready-only memory (EEPROM)), compact disc (read-only memory (CD-ROM)) or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.

The memory 1203 may exist independently, and is connected to the processor 1201 through a communication bus 1202. The memory 1203 may also be integrated with the processor 1201.

The computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not limited.

As an embodiment, the communication apparatus may further include an output device 1205 and an input device 1206, for performing information interaction with the user.

The output device 1205 communicates with the processor 1201 and can output information to the user in a variety of ways.

The input device 1206 communicates with the processor 1201 and can receive information input by the user in a variety of ways.

An embodiment of the present application provides a system including a client, a control server, and a participating server, all of which may adopt a hardware structure in the embodiment shown in FIG. 12. In an implementation scenario, the client can be used to execute the method in the embodiment shown in FIG. 2, 3, 13 or 17, and can also be used to execute the method performed by the client in the embodiment shown in FIG. 20 or 21, and control The server may be used to execute the method in the embodiment shown in FIG. 4 or 15, and may also be used to execute the method executed by the control server in the embodiment shown in FIG. 20 or 21. The participating server may be used to execute FIG. 5, 14, 16, The method in the embodiment shown in 18 or 19 can also be used to execute the method performed by the client participating server in the source system or the client participating server in the target system in the embodiment shown in FIG. 20 or 21. In another implementation scenario, a client, a control server, and a participating server may be used to execute a method corresponding to each device in any of the embodiments shown in FIG. 6-9a.

It should be noted that the following embodiments can refer to the steps, terms, terms, etc. in the foregoing embodiments, for example, the source system, the target system, the identity of the participating service, the identity of the client, downlink information, uplink information, etc. limit.

As shown in FIG. 13, an embodiment of the present application provides a flowchart of yet another communication method. This method can be applied to a client switching from a source system to a target system, as described below.

1301. The client generates a third migration request message.

For step 1301, reference may be made to the related description in step 201, and details are not described herein again.

The third migration request message may carry an identifier of the client's participating server in the target system and an identifier of the client. For example, the third migration request message may be a participating server switching request message.

In addition, the third migration request message may be used to request the client to be migrated, switched, or redirected to the server corresponding to the identity of the client's participating server in the target system. The migration request message 1 is similar to the first migration request message in the embodiment shown in FIG. 2 and will not be described again.

Optionally, the third migration request message further carries an identifier of a group to which the client belongs. Generally, the group currently has ongoing group communication in which the client participates, and there may be no ongoing group communication. If there are multiple such groups, multiple identifiers of the groups to which the client belongs can be carried. At this time, the third migration request message is also used to request that the participating server of the client in the target system provide communication services for the client belonging to the group. For example, the participating server sends the client to the group. The uplink information is transmitted to the control server, or the participating server sends the downlink information in the group to the client. The third migration request message carries the identifier of the group to which the client belongs, so that the client in the specified group is migrated from the source system to the target system. If the third migration request message carries the identifiers of multiple groups, it means that the above operation is performed for each of the annoying groups in the multiple groups.

It should be noted that the client can obtain the identity of the client's participating server in the target system in the manner shown in the embodiment shown in FIG.

1302. The client sends the third migration request message to a participating server of the client in the source system.

Optionally, the method further comprises: the client receiving a response message of the third migration request message from a participating server of the client in the source system.

The response message of the third migration request message may be a participating server switching response message.

Optionally, the method further includes:

The client sends uplink information of the client to a participating server of the client in the target system.

Optionally, the method further includes:

The client receives downlink information of the client from a participating server of the client in the target system.

It should be noted that the method provided in this embodiment may be executed in the following scenarios:

In one implementation scenario, after the client knows that the link of the target system is back to normal, the client may send a HMI prompt message to the user who uses the terminal, asking whether the user switches the client to the target system. When the user chooses to switch to the target system and the client's group call has not ended, the client can further ask whether the user chooses to hold the group call. If the user chooses to hold the group call, the client can perform step 1301- 1302.

In another implementation scenario, when the client learns that the link of the target system returns to normal and the group call of the client has not ended, the client may directly perform steps 1301-1302.

In another implementation scenario, the client can report information about the currently connected network (for example, access through an IOPS network or access through a macro network), and the control server can collect the members of the group to which the client belongs Send information about the current network to this client. The client can present this information to the user so that the user can decide whether to hold the group call. If the user chooses to hold the group call, the client may perform steps 1301-1302.

With the method provided in this embodiment, the client generates a third migration request message and sends a third migration request message to the client's participating server in the source system, thereby realizing the migration of the client from the source system to the target system, that is, the client Connect to the participating server in the target system, and the participating server will continue to provide routing services for the client, for example, the group call routing service ensures the normal call of the group, so that members in the group are provided by different systems In the case of communication services, the group can maintain normal communication.

As shown in FIG. 14, an embodiment of the present application provides a flowchart of yet another communication method. This method can be applied to a client switching from a source system to a target system, as described below.

1401. The participating server of the client in the source system receives a third migration request message from the client.

For the third migration request message, reference may be made to the related description in the embodiment shown in FIG. 13, and details are not described herein again.

1402. The participating server of the client in the source system sends a fourth migration request message to the control server of the client in the source system according to the third migration request message.

The fourth migration request message carries an identifier of the client's participating server in the target system and an identifier of the client.

In addition, the fourth migration request message may be used to request the client to be migrated, switched, or redirected to the server corresponding to the identity of the client's participating server in the target system.

The third migration request message and the fourth migration request message may be the same, for example, they are both participating server handover request messages; they may also be different and are not limited. For example, when the third migration request message carries the identifier of the group to which the client belongs, the fourth migration request message may also carry the identifier of the group to which the client belongs. For the identifier of the group to which the client belongs, reference may be made to the related description in the embodiment shown in FIG. 13, and details are not described herein again.

Exemplarily, in step 1402, the third migration request message may be used as a trigger message of the fourth migration request message, that is, when the participating server of the client in the target system receives the third migration request message from the client, it sends a message to the source system. The client's participating server sends a fourth migration request message. Obviously, the fourth migration request message may also be generated based on the parameters in the third migration request message. For example, the identifier of the group to which the client belongs in the third migration request message is carried in the fourth migration request message.

Optionally, the method further includes:

The participating server of the client in the source system receives a response message of the fourth migration request message from a control server of the client in the source system. The response message may be used to respond to the fourth migration request message.

The fourth migration request message may further carry an identifier of a group to which the client belongs.

Optionally, the method further comprises: the participating server of the client in the source system sends a fifth migration request message to a server corresponding to the identity of the participating server of the client in the target system.

The fifth migration request message carries an identifier of the client and an identifier of a control server of the client in the source system. Optionally, the fifth migration request message further carries an identifier of a group to which the client belongs. Specifically, the fifth migration request message may be a control server switch request message.

The fifth migration request message may be used to request that the control server of the client be migrated, switched or redirected to the control server corresponding to the control server identifier in the fifth migration request message, so that the client in the target system The participating server at the end can send the downlink information received from the control server corresponding to the control server's identity to the client, or send the uplink information sent by the client to the control server corresponding to the control server's identity, and then maintain The client's group call. In other words, the fifth migration request message may be used to request that the control server corresponding to the identity of the control server in the fifth migration request message provide a group call control service for the client. Obviously, the client may also send a fifth migration request message to the participating server. In addition, the fifth migration request message may be a control server migration request message, which is not limited.

Optionally, the method further includes: the participating server of the client in the source system receives a response message of the fifth migration request message from the participating server of the client in the target system. For example, the response message is a control server switching response (controlling server response) message.

By using the method provided in this embodiment, a participating server of a client in a source system receives a third migration request message, and sends a fourth migration request message to a control server of the client in the source system according to the third migration request message To realize the migration of the client from the source system to the target system, that is, the client connects to the participating server in the target system, and the participating server continues to provide the group call routing service for the client to ensure the normal progress of the group call So that the group can maintain normal communication when the members of the group are provided with group communication services by different systems.

As shown in FIG. 15, an embodiment of the present application provides a flowchart of yet another communication method. This method may be applied to a client switching from a source system to a target system, as described below.

1501. The control server of the client in the source system receives a fourth migration request message from a participating server of the client in the source system.

For the fourth migration request message, refer to related description in the embodiment shown in FIG. 14. Specifically, the fourth migration request message carries an identifier of the client's participating server in the target system and an identifier of the client.

1502. The control server of the client in the source system sends downlink information of the client to a server corresponding to an identifier of a participating server of the client in the target system.

Optionally, the method further includes: a control server of the client in the source system sends a response message of the fourth migration request message to a participating server of the client in the source system.

With the method provided in this embodiment, the control server of the client in the source system receives the fourth migration request message, and the fourth migration request message carries the identity of the client server in the target system and the identity of the client; The control server of the client in the source system sends the downlink information of the client to the server corresponding to the identification of the client's participating server in the target system, so that the control server can send the downlink information of the client to the migrated The client's participating server realized the successful migration of the client. For example, the client migrates from the source system to the target system, thereby ensuring the normal progress of the group call, so that the group maintains normal communication when the members of the group are provided with communication services by different systems.

Optionally, in an implementation scenario of the foregoing embodiment, the above method further includes: the control server of the client in the source system sends the request to the client of the client in the target system according to the fourth migration request message. The participating server sends a fifth migration request message.

For specific implementation of this step, reference may be made to the related description of step 1402, and details are not described herein again.

The fifth migration request message carries an identifier of the client and an identifier of a control server of the client in the source system. Optionally, the fifth migration request message further carries an identifier of a group to which the client belongs.

It should be noted that, for the fifth migration request message in this embodiment, reference may be made to the related description of the fifth migration request message in the embodiment shown in FIG. 14, and details are not described herein again.

Optionally, the method further includes: the control server of the client in the source system receives a response message of the fifth migration request message from a participating server of the client in the target system.

As shown in FIG. 16, an embodiment of the present application provides a flowchart of yet another communication method. The method can be applied to a client switching from a source system to a target system, as described below.

1601. The participating server of the client in the target system receives a fifth migration request message.

For the fifth migration request message, refer to related descriptions in the embodiments shown in FIG. 14 or 15. Specifically, the fifth migration request message carries an identifier of a control server of the client in the source system and an identifier of the client. Optionally, the fifth migration request message further carries an identifier of a group to which the client belongs.

Optionally, receiving a fifth migration request message by the participating server of the client in the target system in step 1601 includes:

The participating server of the client in the target system receives the fifth migration request message from the participating server of the client in the source system; or

The participating server of the client in the target system receives the fifth migration request message from a control server of the client in the source system.

1602. The participating server of the client in the target system receives uplink information from the client, and sends the uplink information to a server corresponding to the control server identifier of the client in the source system.

By adopting the method provided in this embodiment, a participating server of a client in a target system receives a fifth migration request message, and the fifth migration request message carries an identifier of a control server of the client in the source system and an identifier of the client; The participating server of the client in the target system receives uplink information from the client, and sends the uplink information to a server corresponding to the control server identifier of the client in the source system, so that the client in the target system participates The server can send the uplink information of the client to the control server of the client, and the successful migration of the client is achieved. For example, the client migrates from the source system to the target system, thereby ensuring the normal progress of the group call, so that the group maintains normal communication when the members of the group are provided with communication services by different systems.

Optionally, the method further includes:

The participating server of the client in the target system receives downlink information of the client from the control server of the client in the source system;

The participating server of the client in the target system sends the downlink information to the client.

As shown in FIG. 17, an embodiment of the present application provides a flowchart of yet another communication method. This method can be applied to a client switching from a source system to a target system, as described below.

1701. The client generates a sixth migration request message.

The sixth migration request message carries the identity of the client's participating server in the source system and the identity of the client. The identity of the participating server of the client in the source system may be the IP address, FQDN, or SIP URI of the participating server, without limitation.

In addition, the sixth migration request message may be used to request the client to be migrated from the server corresponding to the identity of the client's participating server in the source system, and switched or redirected to the client's participating server in the target system. Specifically, the sixth migration request message is a participating server handover request message.

Optionally, the sixth migration request message also carries the identifier of the group to which the client belongs. At this time, the role of the sixth migration request message may refer to the first migration request message in the embodiment shown in FIG.

1702. The client sends the sixth migration request message to a participating server of the client in the target system.

Optionally, the method further includes that the client receives a response message of the sixth migration request message from a participating server of the client in the target system.

Optionally, the method further comprises: the client sending uplink information of the client to a participating server of the client in the target system.

Optionally, the method further comprises: the client receiving downlink information of the client from a participating server of the client in the target system.

In one implementation scenario, after the client knows that the link of the target system is back to normal, the client may send a HMI prompt message to the user who uses the terminal, asking whether the user switches the client to the target system. When the user chooses to switch to the target system and the client's group call has not ended, the client can further ask whether the user chooses to hold the group call. If the user chooses to hold the group call, the client can perform step 1701- 1702.

In another implementation scenario, when the client learns that the link of the target system returns to normal and the group call of the client is not ended, the client may directly perform steps 1701-1702.

In another implementation scenario, the client can report information about the currently connected network (for example, access through an IOPS network or access through a macro network), and the control server can collect the members of the group to which the client belongs Send information about the current network to this client. The client can present this information to the user so that the user can decide whether to hold the group call. If the user chooses to hold the group call, the client may perform steps 1701-1702.

With the method provided in this embodiment, the client generates a sixth migration request message and sends a sixth migration request message to the client's participating server in the target system, thereby realizing the client's migration from the source system to the target system, that is, the client Connected to the participating server in the target system, and the participating server continues to provide routing services for the client, ensuring the normal progress of the group call, so that the members of the group are provided with communication services by different systems Able to maintain normal communication.

As shown in FIG. 18, an embodiment of the present application provides a flowchart of yet another communication method. This method can be applied to a client switching from a source system to a target system, as described below.

1801: The participating server of the client in the target system receives a sixth migration request message from the client.

For the sixth migration request message, refer to related descriptions in the embodiment shown in FIG. 17. Specifically, the sixth migration request message carries the identity of the client's participating server in the source system and the identity of the client.

1802. The participating server of the client in the target system sends a seventh migration request message to the participating server of the client in the source system according to the sixth migration request message.

The seventh migration request message carries an identifier of the client and an identifier of a participating server of the client in the target system. Optionally, the seventh migration request message further carries an identifier of a group to which the client belongs.

In addition, the seventh migration request message may be used to request the client to be migrated, switched, or redirected to the server corresponding to the identity of the client's participating server in the target system. Specifically, the seventh migration request message is a participating server handover request message.

The specific implementation of step 1802 is similar to step 1402, and details are not described herein again.

By using the method provided in this embodiment, a client participating server in a target system receives a sixth migration request message, and sends a seventh migration request message to the client participating server in the source system according to the sixth migration request message, so as to implement The migration of the client from the source system to the target system is achieved, that is, the client connects to the participating server in the target system, and the participating server continues to provide routing services for the client to ensure the normal progress of the group call, so that in the group The group can maintain normal communication when members in the communication service are provided by different systems.

Optionally, in an implementation scenario of the foregoing embodiment, the foregoing method further includes:

The participating server of the client in the target system receives the identity of the control server of the client in the source system from the participating server of the client in the source system; or,

The participating server of the client in the target system receives the identity of the control server of the client in the source system from the control server of the client in the source system.

The identifier of the control server of the client may be carried in a response message of the seventh migration request message.

Through the above implementation scenario, the participating server of the client in the target system successfully obtains the identity of the control server of the client in the source system, so that the participating server of the client in the target system can send the client's uplink information to the control server, Receive downlink information of the client from the control server, thereby ensuring normal communication of the client during the migration process.

Further, the method may further include:

The participating server of the client in the target system receives uplink information from the client;

The participating server of the client in the target system sends the uplink information to a server corresponding to the control server identifier of the client in the source system.

Optionally, the method further includes:

The participating server of the client in the target system receives downlink information of the client from a control server of the client in the source system;

As shown in FIG. 19, an embodiment of the present application provides a flowchart of yet another communication method. This method may be applied to a client switching from a source system to a target system, which is specifically described below.

1901. The participating server of the client in the source system receives a seventh migration request message from the participating server of the client in the target system.

The seventh migration request message carries an identifier of the client's participating server in the target system and an identifier of the client. Optionally, the seventh migration request message further carries an identifier of a group to which the client belongs. Specifically, for the seventh migration request message, refer to related descriptions in the embodiment shown in FIG. 18.

1902. The participating server of the client in the source system sends a fourth migration request message to the control server of the client in the source system according to the seventh migration request message.

For the fourth migration request message, refer to related description in the embodiment shown in FIG. 14. Specifically, the fourth migration request message carries the identity of the client's participating server in the target system and the identity of the client.

In addition, the specific implementation of step 1902 is similar to step 1402, and details are not described again.

Optionally, the method further includes: the participating server of the client in the source system receives a response message of the fourth migration request message from a control server of the client in the source system.

Further, when the seventh migration request message further carries an identifier of a group to which the client belongs, the fourth migration request message may further carry an identifier of a group to which the client belongs.

By using the method provided in this embodiment, a participating server of a client in a source system receives a seventh migration request message, and sends a fourth migration request message to a control server of the client in the source system according to the seventh migration request message. To realize the migration of the client from the source system to the target system, that is, the client connects to the participating server in the target system, and the participating server continues to provide the group call service for the client to ensure the normal progress of the group call. This enables the group to maintain normal communication if the members of the group are provided with group communication services by different systems.

Optionally, in an implementation scenario of the foregoing embodiment, the foregoing method further includes: sending the participating server of the client in the source system to the participating server of the client in the target system The identification of the client's control server.

The identifier of the control server of the client in the source system may be carried in a response message of the seventh migration request message.

Through the above implementation scenario, the participating server of the client in the target system successfully obtains the identity of the control server of the client in the source system, thereby enabling the participating server of the client in the target system to send the client's uplink information to the control server. The downlink information of the client can be received from the control server, thereby ensuring the normal communication of the client during the migration process.

As shown in FIG. 20, an embodiment of the present application provides a flowchart of yet another communication method. This method can be applied to a client switching from a source system to a target system, as described below.

2001. The client generates a migration request message 1.

For step 2001, reference may be made to the related description in step 201, and details are not described herein again.

For the migration request message 1, refer to the related description of the third migration request message, and details are not described herein again.

2002. The client sends a migration request message 1 to the client's participating server in the source system.

Among them, step 2002 is similar to step 202, and reference may be made to related description in step 202, and details are not described herein again.

Optionally, the above method further comprises: the participating server of the client in the source system sends a response message of the migration request message 1 to the client. The response message may be used to respond to the migration request message 1 without limitation.

In 2003, the client's participating server in the source system receives the migration request message 1 and sends a migration request message 2 to the client's control server in the source system according to the migration request 1.

The migration request message 2 may carry the identity of the client's participating server and the identity of the client in the target system. For details, refer to the description of the fourth migration request message, and details are not described herein again.

In addition, the migration request message 2 may be used to request the client to be migrated, switched, or redirected to the server corresponding to the client ’s participating server identity in the target system.

The migration request message 1 and the migration request message 2 may be the same or different, and are not limited. For example, when the migration request message 1 carries the identifier of the group to which the client belongs, the migration request message 2 may also carry the identifier of the group to which the client belongs.

Specifically, for step 2003, reference may be made to the related description of step 1402, and details are not described herein again.

Optionally, the method further includes: the control server of the client in the source system sends a response message of the migration request message 2 to the client's participating server in the source system. The response message may be used to respond to the migration request message 2 without limitation.

In 2004, the client's participating server in the source system sends a migration request message 3 to the client's participating server in the target system.

Optionally, the above method further includes: the client's participating server in the target system sends a response message of the migration request message 3 to the client's participating server in the source system.

Alternatively, step 2004 is replaced with 2004a.

2004a. The control server of the client in the source system sends a migration request message 3 to the participating server of the client in the target system according to the migration request message 2.

Further, the above method may further include: the participating server of the client in the target system sends a response message of the migration request message 3 to the control server of the client in the source system. The response message may be used to respond to the migration request message 3 without limitation.

The migration request message 3 may carry the identity of the client and the identity of the client's control server in the source system. For the migration request message 3, refer to the foregoing description of the fifth migration request message.

The migration request message 3 may be used to request the participating server to migrate, switch, or redirect the control server of the client to the control server corresponding to the identity of the control server in the migration request message 3, so that the participating server can transfer data from the control server. The downlink information received by the control server corresponding to the identifier is sent to the client, or the uplink information sent by the client is sent to the control server corresponding to the identifier of the control server, and the group call of the client is maintained. In other words, the migration request message 3 may be used to request that the control server corresponding to the identity of the control server in the migration request message 3 provide a routing service for the client. Obviously, the client can also send a migration request message 3 to the participating server. In addition, the migration request message 3 may be a control server migration request message, which is not limited.

It should be noted that the steps and nouns between the embodiments of the present application can draw on each other, for example, the identifier of the control server, the identifier of the participating service, and the identifier of the client are not limited.

Optionally, the method further includes:

The client sends uplink information of the client to the client's participating server in the target system;

The client's participating server in the target system sends the uplink information to the client's control server in the source system.

Optionally, the method further includes:

The control server of the client in the source system sends downlink information to the client's participating servers in the target system;

The client's participating server in the target system sends the downlink information to the client.

With the method provided in this embodiment, a client participating server in a source system receives a migration request message 1 from the client, and sends a migration request message 2 to the control server of the client in the source system according to the migration request message 1. Further, the control server sends a migration request message 3 to the client's participating server in the target system, or the client's participating server in the source system sends a migration request message 3 to the client's participating server in the target system. Migration to the target system, that is, the client connects to the participating server in the target system, and the participating server continues to provide routing services for the client, ensuring the normal call of the group, so that members in the group are made by different systems The group is able to maintain normal communication while providing communication services.

As shown in FIG. 21, an embodiment of the present application provides a flowchart of yet another communication method. This method can be applied to a client switching from a source system to a target system, as described below.

2101 The client generates a migration request message 4 and sends a migration request message 4 to the client's participating server in the target system.

The migration request message 4 may carry the identity of the client's participating server and the identity of the client in the source system. Please refer to the foregoing description of the sixth migration request message.

In addition, the migration request message 4 may be used to request that the client be migrated from the server corresponding to the identity of the client's participating server in the source system, switch or redirect to the client's participating server in the target system.

The identity of the participating server of the client in the source system may be the IP address, FQDN, or SIP URI of the participating server, without limitation.

Optionally, the migration request message 4 also carries the identifier of the group to which the client belongs. At this time, the role of the migration request message 4 can be referred to the first migration request message in the embodiment shown in FIG.

Optionally, the above method further includes: the client's participating server in the source system sends a response message of the migration request message 4 to the client. The response message may be used to respond to the migration request message 4 without limitation.

2102. The client's participating server in the target system receives a migration request message 4 from the client, and sends a migration request message 5 to the client's participating server in the source system according to the migration request message 4.

The migration request message 5 may refer to a seventh migration request message, and the migration request message 5 may carry an identifier of the client and an identifier of a participating server of the client in a target system. Optionally, the migration request message 5 further carries an identifier of a group to which the client belongs.

In addition, the migration request message 5 may be used to request the client to be migrated, switched, or redirected to the server corresponding to the client ’s participating server identity in the target system.

For example, in step 2102, the migration request message 4 may be used as the trigger message of the migration request message 5, that is, when the client's participating server in the target system receives the migration request message 4 from the client, The client's participating server sends a migration request message 5. Obviously, the migration request message 5 may also be generated based on the parameters in the migration request message 4. For example, the identifier of the group to which the client belongs in the migration request message 4 is carried in the migration request message 5.

Optionally, the above method further includes: the participating server of the client in the source system sends a response message of the migration request message 5 to the participating server of the client in the target system. The response message may be used to respond to the migration request message 5 without limitation.

2103. The client's participating server in the source system receives a migration request message 5 from the client's participating server in the target system, and sends a migration request message 6 to the client's control server in the source system according to the migration request message 5.

The migration request message 6 carries the identity of the client's participating server and the identity of the client in the target system. Optionally, the migration request message 6 also carries the identifier of the group to which the client belongs.

In addition, for the migration request message 6, refer to the related description of the migration request message 2 or the fourth migration request message, and details are not described herein again.

Optionally, the above method further includes: the control server of the client in the source system sends a response message of the migration request message 6 to the participating server of the client in the source system. The response message may be used to respond to the migration request message 6 without limitation.

Optionally, the above method further includes step 2104a or 2104b, as described below.

2104a. The client's participating server in the source system sends the client's participating server in the target system to the client's controlling server identification.

The identifier of the control server of the client in the source system in step 2104a may be carried in the response message of the migration request message 5.

Correspondingly, the client's participating server in the target system receives the identity of the client's control server in the source system from the client's participating server in the source system.

2104b: The control server of the client in the source system sends the identification of the control server of the client in the source system to the participating server of the client in the target system.

The identifier of the control server of the client in the source system in step 2104b may be carried in the migration request message 7. The migration request message 7 may be used to request a migration control server, for example, the control server migration request message. The migration request message 7 may further include an identifier of the client, and may further carry an identifier of a group to which the client belongs, without limitation.

Correspondingly, the participating server of the client in the target system receives the identity of the control server of the client in the source system from the control server of the client in the source system.

Further, the above method may further include:

The participating server of the client in the target system receives the uplink information from the client;

The participating server of the client in the target system sends the uplink information to the server corresponding to the control server identifier of the client in the source system.

Further, the above method may further include:

The client's participating server in the target system receives the client's downlink information from the client's control server in the source system;

The client's participating server in the target system sends the downlink information to the client;

The client receives the downlink information from the client's participating server in the target system.

By using the method provided in this embodiment, the client's participating server in the target system receives the migration request message 4 from the client's participating server in the source system, and according to the migration request message 4 to the control server of the client in the source system Send a migration request message 5. Further, the client's participating server in the source system sends a migration request message 6 to the client's control server in the source system to implement the migration of the client from the source system to the target system, that is, the client connects to the target system. The participating server in the server, which continues to provide routing services for the client, ensures the normal call of the group, so that the group can maintain normal communication when the members in the group provide communication services from different systems .

Based on the composition diagram shown in FIG. 22, this embodiment of the present application further provides another communication device. The device may be used to perform the actions of the client in the method embodiment shown in FIG. 13. The device may be a terminal or a client. It can be a chip, a system on a chip, or a functional module located on the terminal or client. The device includes: a generating unit 2201 and a sending unit 2202.

A generating unit 2201 is configured to generate a third migration request message, where the third migration request message carries an identifier of a participating server of a client in a target system and an identifier of the client;

A sending unit 2202 is configured to send the third migration request message to a participating server of the client in the source system.

Optionally, the communication device method further includes a first receiving unit.

A first receiving unit is configured to receive a response message of the third migration request message from a participating server of the client in the source system.

Optionally, the sending unit 2202 is further configured to send uplink information of the client to a participating server of the client in the target system.

Optionally, the communication device method further includes a second receiving unit, configured to receive downlink information of the client from a participating server of the client in the target system.

Based on the composition diagram shown in FIG. 23, this embodiment of the present application further provides another communication device. The device may be used to execute the method in the method embodiment shown in FIG. 14. The device may be a participating server, or may be located at Participate in chips on the server, system-on-chip, or functional modules. The device includes a receiving unit 2301 and a sending unit 2302.

A receiving unit 2301 is configured to receive a third migration request message from a client, where the third migration request message carries an identifier of a participating server of the client in the target system and an identifier of the client;

A sending unit 2302 is configured to send a fourth migration request message to the control server of the client in the source system according to the third migration request message, where the fourth migration request message carries the client's The identity of the participating server and the identity of the client.

Optionally, the receiving unit 2301 is further configured to receive a response message of the fourth migration request message from a control server of the client in the source system.

Optionally, the sending unit 2302 is further configured to send a fifth migration request message to a server corresponding to the identity of the client's participating server in the target system, where the fifth migration request message carries the identity of the client and all The identity of the control server of the client in the source system.

The fifth migration request message may further carry an identifier of a group to which the client belongs.

Optionally, the receiving unit 2301 is further configured to receive a response message of the fifth migration request message from a participating server of the client in the target system.

Based on the composition diagram shown in FIG. 24, this embodiment of the present application further provides another communication device. The device may be used to execute the method in the method embodiment shown in FIG. 15. The device may be a control server or a Controls the chip, system-on-chip, or function module on the server. The device includes a receiving unit 2401 and a transmitting unit 2402.

A receiving unit 2401, configured to receive a fourth migration request message from a client participating server in a source system, where the fourth migration request message carries an identifier of the client participating server in the target system and an identifier of the client;

The sending unit 2402 is configured to send the downlink information of the client to a server corresponding to the identifier of the client's participating server in the target system.

Optionally, the sending unit 2402 is further configured to send a response message of the fourth migration request message to a participating server of the client in the source system.

Optionally, the sending unit 2402 is further configured to send a fifth migration request message to the participating server of the client in the target system according to the fourth migration request message, where the fifth migration request message carries the client The identity of the client and the identity of the control server of the client in the source system.

Optionally, the receiving unit 2401 is further configured to receive a response message of the fifth migration request message from a participating server of the client in the target system.

Based on the composition diagram shown in FIG. 25, an embodiment of the present application further provides another communication device. The device may be used to execute the method in the method embodiment shown in FIG. 16, and the device may be a participating server or may be located at Participate in chips on the server, system-on-chip, or functional modules. The device includes a receiving unit 2501 and a sending unit 2502.

The receiving unit 2501 is configured to receive a fifth migration request message from a participating server of a client in a target system, where the fifth migration request message carries an identifier of a control server of the client in the source system and an identifier of the client;

The receiving unit 2501 is further configured to receive uplink information from the client;

A sending unit 2502 is configured to send the uplink information to a server corresponding to an identifier of a control server of the client in the source system.

Optionally, the receiving unit 2501 is further configured to:

Receiving the fifth migration request message from a participating server of the client in the source system; or

Receiving the fifth migration request message from a control server of the client in the source system.

Optionally, the receiving unit 2501 is further configured to receive downlink information of the client from the control server of the client in the source system; the sending unit 2502 is further configured to send the downlink information to the client.

Based on the composition diagram shown in FIG. 26, an embodiment of the present application further provides another communication device. The device may be used to execute the method in the method embodiment shown in FIG. 17, and the device may be a client or a terminal, or A chip, system-on-a-chip, or functional module located on a client or terminal. The device includes: a generating unit 2601 and a sending unit 2602.

A generating unit 2601 is configured to generate a sixth migration request message, where the sixth migration request message carries an identifier of a client participating server in the source system and an identifier of the client;

The sending unit 2602 is configured to send the sixth migration request message to a participating server of the client in the target system.

Optionally, the communication device further includes: a first receiving unit.

A first receiving unit is configured to receive a response message of the sixth migration request message from a participating server of the client in the target system.

Optionally, the sending unit 2602 is further configured to send uplink information of the client to a participating server of the client in the target system.

Optionally, the communication device further includes: a second receiving unit.

A second receiving unit is configured to receive downlink information of the client from a participating server of the client in the target system.

Based on the composition diagram shown in FIG. 27, an embodiment of the present application further provides another communication device. The device may be used to execute the method in the method embodiment shown in FIG. 18. The device may be a participating server or may be located at Participate in chips on the server, system-on-chip, or functional modules. The device includes a receiving unit 2701 and a transmitting unit 2702.

The receiving unit 2701 is configured to receive a sixth migration request message from a client, where the sixth migration request message carries an identifier of the client's participating server in the source system and an identifier of the client;

A sending unit 2702 is configured to send a seventh migration request message to the client's participating server in the source system according to the sixth migration request message, where the seventh migration request message carries the identifier of the client and the Identification of the participating server of the client in the target system.

Optionally, the receiving unit 2701 is further configured to:

Receiving an identity of a control server of the client in the source system from a participating server of the client in the source system; or,

Receiving the identification of the control server of the client in the source system from the control server of the client in the source system.

Optionally, the receiving unit 2701 is further configured to receive uplink information from the client; the sending unit 2702 is further configured to send the uplink information to a server corresponding to an identifier of a control server of the client in the source system.

Optionally, the receiving unit 2701 is further configured to receive downlink information of the client from the control server of the client in the source system; the sending unit 2702 is further configured to send the downlink information to the client.

The seventh migration request message may further carry an identifier of a group to which the client belongs.

Based on the composition diagram shown in FIG. 28, an embodiment of the present application further provides another communication device. The device may be used to execute the method in the method embodiment shown in FIG. 19. The device may be a participating server or may be located at Participate in chips on the server, system-on-chip, or functional modules. The device includes a receiving unit 2801 and a transmitting unit 2802.

A receiving unit 2801 is configured to receive a seventh migration request message from a participating server of a client in a target system, where the seventh migration request message carries an identifier of the participating server of the client in the target system and an identifier of the client;

A sending unit 2802 is configured to send a fourth migration request message to the control server of the client in the source system according to the seventh migration request message, where the fourth migration request message carries the information about the client in the target system. The identity of the participating server and the identity of the client.

Optionally, the receiving unit 2801 is further configured to receive a response message of the fourth migration request message from a control server of the client in the source system.

Further, the fourth migration request message may further carry an identifier of a group to which the client belongs.

Optionally, the sending unit 2802 is further configured to send the identity of the control server of the client in the source system to the participating server of the client in the target system.

The above embodiments may refer to each other, and the same or similar steps and terms are not repeated one by one.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it 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 the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission by wire (for example, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (for example, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (Solid State Disk (SSD)), and the like.

Claims

A communication method, characterized in that the method is applied to a client switching from a source system to a target system and includes:

Generating, by the client, a third migration request message, where the third migration request message carries an identifier of the client's participating server in the target system and an identifier of the client;

Sending, by the client, the third migration request message to a participating server of the client in the source system.
The method according to claim 1, further comprising:

The client receives a response message of the third migration request message from a participating server of the client in the source system.
The method according to claim 1 or 2, further comprising:

The client sends uplink information of the client to a participating server of the client in the target system.
The method according to any one of claims 1 to 3, further comprising:

The client receives downlink information of the client from a participating server of the client in the target system.
A communication method, characterized in that the method is applied to a client switching from a source system to a target system and includes:

The client's participating server in the source system receives a third migration request message from the client, and the third migration request message carries the identity of the client's participating server in the target system and the client's Identification

The participating server of the client in the source system sends a fourth migration request message to the control server of the client in the source system according to the third migration request message, where the fourth migration request message carries the The identity of the client's participating server and the identity of the client in the target system.
The method according to claim 5, further comprising:

The participating server of the client in the source system receives a response message of the fourth migration request message from a control server of the client in the source system.
The method according to claim 5 or 6, wherein the fourth migration request message further carries an identifier of a group to which the client belongs.
The method according to any one of claims 5-7, wherein the method further comprises:

The client's participating server in the source system sends a fifth migration request message to the server corresponding to the identity of the client's participating server in the target system, where the fifth migration request message carries the identity of the client and all The identity of the control server of the client in the source system.
The method according to claim 8, wherein the fifth migration request message further carries an identifier of a group to which the client belongs.
The method according to claim 8 or 9, further comprising:

The participating server of the client in the source system receives a response message of the fifth migration request message from the participating server of the client in the target system.
A communication method, characterized in that the method is applied to a client switching from a source system to a target system and includes:

The control server of the client in the source system receives a fourth migration request message from a participating server of the client in the source system, and the fourth migration request message carries the participating server of the client in the target system And the identity of the client;

The control server of the client in the source system sends downlink information of the client to the server corresponding to the identification of the client's participating server in the target system.
The method according to claim 11, further comprising:

The control server of the client in the source system sends a response message of the fourth migration request message to a participating server of the client in the source system.
The method according to claim 11 or 12, wherein the fourth migration request message further carries an identifier of a group to which the client belongs.
The method according to any one of claims 11-13, wherein the method further comprises:

The control server of the client in the source system sends a fifth migration request message to the client's participating server in the target system according to the fourth migration request message, and the fifth migration request message carries the client The identity of the client and the identity of the control server of the client in the source system.
The method according to claim 14, wherein the fifth migration request message further carries an identifier of a group to which the client belongs.
The method according to claim 14 or 15, further comprising:

The control server of the client in the source system receives a response message of the fifth migration request message from a participating server of the client in the target system.
A communication method, characterized in that the method is applied to a client switching from a source system to a target system and includes:

A participating server of the client in the target system receives a fifth migration request message, where the fifth migration request message carries an identifier of a control server of the client in the source system and an identifier of the client;

The participating server of the client in the target system receives uplink information from the client, and sends the uplink information to a server corresponding to the control server identifier of the client in the source system.
The method according to claim 17, wherein the receiving server of the client in the target system receives a fifth migration request message, comprising:

The participating server of the client in the target system receives the fifth migration request message from the participating server of the client in the source system; or

The participating server of the client in the target system receives the fifth migration request message from a control server of the client in the source system.
The method according to claim 17 or 18, wherein the fifth migration request message further carries an identifier of a group to which the client belongs.
The method according to any one of claims 17 to 19, wherein the method further comprises:

The participating server of the client in the target system receives downlink information of the client from the control server of the client in the source system;

The participating server of the client in the target system sends the downlink information to the client.
A communication method, characterized in that the method is applied to a client switching from a source system to a target system and includes:

The client generates a sixth migration request message, where the sixth migration request message carries an identifier of the client's participating server in the source system and an identifier of the client;

Sending, by the client, the sixth migration request message to a participating server of the client in the target system.
The method according to claim 21, further comprising:

The client receives a response message of the sixth migration request message from a participating server of the client in the target system.
The method according to claim 21 or 22, further comprising:

The client sends uplink information of the client to a participating server of the client in the target system.
The method according to any one of claims 21-23, wherein the method further comprises:

The client receives downlink information of the client from a participating server of the client in the target system.
A communication method, characterized in that the method is applied to a client switching from a source system to a target system and includes:

The client's participating server in the target system receives a sixth migration request message from the client, and the sixth migration request message carries the identity of the client's participating server in the source system and the client's Identification

The participating server of the client in the target system sends a seventh migration request message to the client's participating server in the source system according to the sixth migration request message, and the seventh migration request message carries the client The identity of the client and the identity of the participating server of the client in the target system.
The method according to claim 25, further comprising:

The participating server of the client in the target system receives the identity of the control server of the client in the source system from the participating server of the client in the source system; or,

The participating server of the client in the target system receives the identity of the control server of the client in the source system from the control server of the client in the source system.
The method according to claim 26, wherein the identifier of the control server of the client is carried in a response message of the seventh migration request message.
The method according to claim 26 or 27, further comprising:

The participating server of the client in the target system receives uplink information from the client;

The participating server of the client in the target system sends the uplink information to a server corresponding to the control server identifier of the client in the source system.
The method according to any one of claims 26-28, wherein the method further comprises:

The participating server of the client in the target system receives downlink information of the client from the control server of the client in the source system;

The participating server of the client in the target system sends the downlink information to the client.
The method according to any one of claims 25-29, wherein the seventh migration request message further carries an identifier of a group to which the client belongs.
A communication method, characterized in that the method is applied to a client switching from a source system to a target system and includes:

The client's participating server in the source system receives a seventh migration request message from the client's participating server in the target system, and the seventh migration request message carries the client's participating server in the target system And the identity of the client;

The participating server of the client in the source system sends a fourth migration request message to the control server of the client in the source system according to the seventh migration request message, and the fourth migration request message carries the The identity of the client's participating server and the identity of the client in the target system.
The method according to claim 31, further comprising:

The participating server of the client in the source system receives a response message of the fourth migration request message from a control server of the client in the source system.
The method according to claim 31 or 32, wherein the seventh migration request message further carries an identifier of a group to which the client belongs.
The method according to claim 33, wherein the fourth migration request message further carries an identifier of a group to which the client belongs.
The method according to any one of claims 31-34, wherein the method further comprises:

The participating server of the client in the source system sends an identification of the control server of the client in the source system to the participating server of the client in the target system.
The method according to claim 35, wherein the identifier of the control server of the client in the source system is carried in a response message of the seventh migration request message.
A communication device, comprising: a processor, a memory, and a communication bus, wherein the processor and the memory communicate through the communication bus;

The memory is configured to store computer-executable instructions for performing the method of any one of claims 1-36;

The processor is configured to execute computer execution instructions stored in the memory.