Conversation group migration method, device, computer equipment and storage medium
By adding the second user account to the target conversation group of the first user account and updating it to a conversation group across social applications, the problem of low efficiency in establishing conversation groups is solved, and rapid migration and intercommunication of conversation groups between different applications are achieved.
Patent Information
- Application Number
- CN202111138026.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-09-27
- Publication Date
- 2025-09-23
- Estimated Expiration
- 2041-09-27
AI Technical Summary
In the prior art, the efficiency of establishing a conversation group is low, and users need to actively request to join a new conversation group, resulting in low efficiency in group establishment.
By receiving a session group migration request, the first user account is added to the target session group of the second social application, and the target session group is updated to the session group associated with the first and second social applications, and the group migration information is sent to the server of the second social application, making it a session group of the second social application.
This achieves rapid migration of conversation groups, improves the efficiency of conversation group establishment, and enables conversation groups to communicate between two social applications, thereby improving conversation efficiency and interoperability.
Smart Images

Figure CN115883634B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method, apparatus, computer device, and storage medium for migrating a session group. Background Art
[0002] With the development of computer technology and Internet technology, more and more users are communicating through the network. For example, a conversation group can be created in an instant messaging application, and multiple users can be added to the conversation group. Users who have joined the conversation group can send messages to the conversation group and receive messages input by other users in the conversation group.
[0003] Currently, for a conversation group, each user in the conversation group usually actively requests to join a new conversation group, resulting in low efficiency in group establishment. Summary of the Invention
[0004] Based on this, it is necessary to provide a session group migration method, apparatus, computer equipment and storage medium to address the above technical issues.
[0005] A method for migrating a session group, the method comprising: receiving a session group migration request for a target session group corresponding to a first user account; the target session group includes the first user account corresponding to the first social application; in response to the session group migration request, adding a second user account corresponding to the first user account in a second social application to the target session group, and updating the target session group to a session group associated with the first social application and the second social application; sending group migration information corresponding to the target session group to a second server corresponding to the second social application, so that the second server uses the target session group as the session group corresponding to the second social application based on the group migration information.
[0006] A session group migration device, the device comprising: a session group migration request receiving module, configured to receive a session group migration request for a target session group corresponding to a first user account; the target session group comprising a first user account corresponding to the first social application; a session group updating module, configured to, in response to the session group migration request, add a second user account corresponding to the first user account in a second social application to the target session group, and update the target session group to a session group associated with the first social application and the second social application; and a group migration information sending module, configured to send group migration information corresponding to the target session group to a second server corresponding to the second social application, so that the second server uses the target session group as the session group corresponding to the second social application based on the group migration information.
[0007] A computer device includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps in the above-mentioned session group migration method when executing the computer program.
[0008] A computer-readable storage medium stores a computer program, which implements the steps in the above-mentioned conversation group migration method when executed by a processor.
[0009] A computer program product includes a computer program, which implements the steps in the above-mentioned conversation group migration method when executed by a processor.
[0010] The above-described conversation group migration method, apparatus, computer device, and storage medium add the second user account corresponding to the first user account in the second social application to the target conversation group, update the target conversation group to a conversation group associated with both the first and second social applications, and send group migration information corresponding to the target conversation group to the second server corresponding to the second social application. This allows the second server to use the target conversation group as the conversation group in the second social application based on the group migration information, thereby rapidly migrating the conversation group and improving the efficiency of conversation group establishment. Furthermore, since the target conversation group was a conversation group in the first social application before the update, and the target conversation group is also a conversation group in the second social application after the update, the target conversation group belongs to both the first and second social applications. This allows conversation messages in the target conversation group to be communicated between the first and second social applications, thereby improving conversation efficiency.
[0011] A method for migrating a session group, the method comprising: receiving group migration information corresponding to a target session group sent by a first server corresponding to a first social application; wherein the target session group includes a first user account corresponding to the first social application, and the first server responds to a session group migration request for the target session group by adding a second user account corresponding to a second social application of the first user account to the target session group and triggering the sending of the group migration information; based on the group migration information, the target session group is used as the session group corresponding to the second social application; and a group establishment notification message corresponding to the target session group is sent to a terminal corresponding to the second user account, so that the terminal displays the target session group based on the group establishment notification message through the second social application.
[0012] A session group migration device, the device comprising: a group migration information receiving module, configured to receive group migration information corresponding to a target session group sent by a first server corresponding to a first social application; wherein the target session group includes a first user account corresponding to the first social application, and the first server, in response to a session group migration request for the target session group, adds a second user account corresponding to a second social application of the first user account to the target session group and triggers the sending of the group migration information; a session group migration module, configured to use the target session group as the session group corresponding to the second social application based on the group migration information; and a group establishment notification message sending module, configured to send a group establishment notification message corresponding to the target session group to a terminal corresponding to the second user account, so that the terminal displays the target session group based on the group establishment notification message through the second social application.
[0013] The above-mentioned conversation group migration method, apparatus, computer device, and storage medium receive group migration information corresponding to a target conversation group sent by a first server corresponding to a first social application, identify the target conversation group as a conversation group corresponding to a second social application based on the group migration information, and send a group establishment notification message corresponding to the target conversation group to a terminal corresponding to a second user account. The terminal can then display the target conversation group in the second social application based on the group establishment notification message, thereby quickly migrating the conversation group in the first social application to the second social application, thereby improving the efficiency of conversation group establishment. In addition, since the target conversation group is a conversation group in the first social application, migrating the conversation group in the first social application to a conversation group in the second social application through migration makes the target conversation group a conversation group that communicates between the first social application and the second social application, thereby enabling conversation messages in the first social application to be sent to the second social application, and vice versa, thereby improving conversation interoperability and conversation efficiency.
[0014] A method for migrating a session group, the method comprising: displaying a set of candidate session groups to be migrated corresponding to a first user account; in response to a selection operation on a candidate session group in the set of candidate session groups, using the selected candidate session group as a target session group; the target session group includes the first user account corresponding to the first social application; triggering a session group migration request for the target session group to request a first server corresponding to the first social application to add a second user account corresponding to the first user account in a second social application to the target session group, and sending group migration information corresponding to the target session group to a second server corresponding to the second social application, so that the second server uses the target session group as the session group corresponding to the second social application based on the group migration information.
[0015] A session group migration device, the device comprising: a candidate session group set display module, configured to display a set of candidate session groups to be migrated corresponding to a first user account; a target session group obtaining module, configured to, in response to a selection operation on a candidate session group in the candidate session group set, use the selected candidate session group as a target session group; the target session group includes a first user account corresponding to the first social application; and a session group migration request triggering module, configured to trigger a session group migration request for the target session group, so as to request a first server corresponding to the first social application to add a second user account corresponding to the first user account in a second social application to the target session group, and to send group migration information corresponding to the target session group to a second server corresponding to the second social application, so that the second server uses the target session group as the session group corresponding to the second social application based on the group migration information.
[0016] The above-described conversation group migration method, apparatus, computer device, and storage medium display a set of candidate conversation groups to be migrated corresponding to a first user account. In response to a selection operation on a candidate conversation group in the set of candidate conversation groups, the selected candidate conversation group is selected as a target conversation group. The target conversation group includes a first user account corresponding to a first social application. A conversation group migration request is triggered for the target conversation group, requesting a first server corresponding to the first social application to add a second user account corresponding to a second social application of the first user account to the target conversation group. Group migration information corresponding to the target conversation group is then sent to a second server corresponding to the second social application, so that the second server, based on the group migration information, selects the target conversation group as the conversation group corresponding to the second social application. This allows the conversation group of the first social application to be quickly migrated to the second social application, improving the efficiency of conversation group establishment. Furthermore, the target conversation group becomes a conversation group for communication between the first and second social applications, allowing conversation messages in the first social application to be sent to the second social application, and vice versa, improving conversation interoperability and efficiency.
[0017] A method for migrating a conversation group, the method comprising: displaying a social application interface corresponding to a second user account logged in to a second social application; receiving a group migration operation for a first social application through the social application interface; and triggering an application jump request for the first social application in response to the group migration operation, requesting a jump from the second social application to the first social application, so that the first social application obtains a set of candidate conversation groups to be migrated corresponding to the first user account logged in to the first social application, and displays the set of candidate conversation groups to be migrated.
[0018] A conversation group migration device, the device comprising: a social application interface display module, configured to display a social application interface corresponding to a second user account logged in to a second social application; a group migration operation receiving module, configured to receive a group migration operation for a first social application via the social application interface; and an application jump request response module, configured to trigger an application jump request for the first social application in response to the group migration operation, requesting a jump from the second social application to the first social application, so that the first social application obtains a set of candidate conversation groups to be migrated corresponding to the first user account logged in to the first social application, and displays the set of candidate conversation groups to be migrated.
[0019] The above-mentioned conversation group migration method, apparatus, computer device, and storage medium display a social application interface corresponding to a second user account logged in to the second social application, receive a group migration operation for a first social application through the social application interface, and trigger an application jump request for the first social application in response to the group migration operation, requesting to jump from the second social application to the first social application, so that the first social application obtains a set of candidate conversation groups to be migrated corresponding to the first user account logged in to the first social application and displays the set of candidate conversation groups to be migrated. Based on the group migration operation, the user jumps from the second social application to the first social application and obtains the set of candidate conversation groups to be migrated. Thus, conversation groups in the set of candidate conversation groups can be migrated to the second social application, thereby improving the efficiency of establishing conversation groups and making the target conversation group a conversation group for intercommunication between the first and second social applications. Thus, conversation messages in the first social application can be sent to the second social application, and conversation messages in the second social application can also be sent to the first social application, thereby improving conversation interoperability and conversation efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 A diagram illustrating an application environment of a conversation group migration method in some embodiments;
[0021] Figure 2 is a flowchart of a method for migrating a session group in some embodiments;
[0022] Figure 3 This is an interface diagram for application jump in some embodiments;
[0023] Figure 4 is a timing diagram of a method for migrating a session group in some embodiments;
[0024] Figure 5 is a timing diagram of a method for migrating a session group in some embodiments;
[0025] Figure 6 is a flowchart of a method for migrating a session group in some embodiments;
[0026] Figure 7 is a timing diagram of a method for migrating a session group in some embodiments;
[0027] Figure 8 is a schematic diagram of a method for migrating a session group in some embodiments;
[0028] Figure 9 is a structural block diagram of a session group migration apparatus in some embodiments;
[0029] Figure 10 is a structural block diagram of a session group migration apparatus in some embodiments;
[0030] Figure 11 is a diagram of the internal structure of a computer device in some embodiments;
[0031] Figure 12 1 is a diagram of the internal structure of a computer device in some embodiments. DETAILED DESCRIPTION
[0032] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.
[0033] The session group migration method provided in this application can be applied to Figure 1 In the application environment shown, the application environment includes a terminal 102, a first server 104, and a second server 106. The terminal 102, the first server 104, and the second server 106 communicate via a network. A first client corresponding to a first social application and a second client corresponding to a second social application may be installed in the terminal 102. The first server 104 may be a backend server corresponding to the first social application, and the second server 106 may be a backend server corresponding to the second social application.
[0034] Specifically, a user can register an account in a first social application or a second social application. The account registered by the user in the first social application is referred to as a first user account, and the account registered by the user in the second social application is referred to as a second user account. The same user corresponds to a first user account or a second user account. For example, a user can have both a first user account and a second user account. The first social application and the second social application can support the function of creating a conversation group. The first client can create a conversation group in response to a conversation group creation operation, and the created conversation group can include one or more first user accounts. The second client can create a conversation group in response to a conversation group creation operation, and the conversation group can include one or more second user accounts. The conversation group created by the first client is referred to as a first conversation group, and the conversation group created by the second client is referred to as a second conversation group. The first conversation group and the second conversation group are ordinary conversation groups. Group messages in the first conversation group will not appear in the second client, and group messages in the second conversation group will not appear in the first client.
[0035] First server 104 can add the second user account to the first conversation group and update the first conversation group from a standard conversation group to a conversation group associated with the first and second social applications. A conversation group associated with the first and second social applications can be referred to as an associated conversation group. Group messages in the associated conversation group can appear in the first social application as well as in the second social application logged in by the second user account in the associated conversation group. For example, first server 104 can receive a conversation group migration request for a target conversation group in the first social application from the first user account. The target conversation group can be any first conversation group. In response to the conversation group migration request, first server 104 retrieves the second user account corresponding to the first user account, adds the second user account to the target conversation group, and updates the target conversation group to a conversation group associated with the first and second social applications. First server 104 can send group migration information corresponding to the target conversation group to second server 106 corresponding to the second social application. Based on the group migration information, second server 106 can set the target conversation group as the conversation group corresponding to the second social application.
[0036] The first server can send the updated group message in the target conversation group to the second server 106 corresponding to the second social application. The second server 106 can then send the group message to the second client corresponding to the second social application. The second client can then display the group message. The first user account and the second user account can be the same user account. The first social application and the second social application are different social applications.
[0037] The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, portable wearable devices or vehicle-mounted terminals, and the first server 104 and the second server 106 may be implemented as independent servers or a server cluster consisting of multiple servers.
[0038] In some embodiments, as Figure 2 As shown, a session group migration method is provided, which is applied to Figure 1 Taking the first server 104 in the example as an example, the following steps are included:
[0039] S202: Receive a session group migration request for a target session group corresponding to a first user account; the target session group includes the first user account corresponding to a first social application.
[0040] A social application is an application used for social interaction. For example, an instant messaging (IM) application is an application that allows instant sending and receiving of internet messages. An IM application can include at least one of a standard IM application and a team communication application. A team communication application is designed for team users. Team members can use this application to conduct work conversations and perform at least one of several office functions, such as file transfer, information statistics, daily attendance, meeting scheduling, or email exchanges, to facilitate team work and enable collaborative work. Compared to the friend relationship chain in standard IM applications, the social relationship chain in a team communication application is based on the departmental divisions and hierarchical relationships within the team. A team can be an enterprise or an organization. In contrast, the relationships between users in standard IM applications can be arbitrary, for example, they can be users in the same community or users in the same family. For example, a conversation group in a standard IM application can be residents of the same community. A conversation group consisting of residents in a community can also be called a resident group, while a conversation group consisting of users in the same family can be called a family group. The first social application is different from the second social application. The first and second social applications can be either common instant messaging applications or team communication applications. For example, the first social application is a common instant messaging application and the second social application is a team communication application, or the first social application is a team communication application and the second social application is a common instant messaging application. A first user account is logged in to the first social application. The first user account is an account registered in the first social application and used to log in to the first social application.
[0041] Conversation groups can be created in social applications. For example, a conversation group can be created in a first social application and a second social application. The conversation group created in the first social application can be called the first conversation group, and the conversation group created in the second social application can be called the second conversation group. A conversation refers to a method of conversation between at least two users. A conversation group can include multiple user accounts, where "multiple" means at least two. The user corresponding to a user account can be a living being, such as a person, or an inanimate being, such as a virtual robot. A conversation group can be, for example, a group of residents or a group of customers.
[0042] The target conversation group is a conversation group created in the first social application, and the target conversation group includes the first user account. For example, it can be a conversation group created by the first user account in the first social application, or it can be a conversation group created by other user accounts. The target conversation group can be one or more. The first user account can correspond to a conversation group set, and the conversation groups in the conversation group set are conversation groups of the first user account in the first social application. The target conversation group can include at least one conversation group in the conversation group set. Alternatively, the target conversation group can be selected from the conversation group set of the first user account based on the group member attributes of the first user account. The group member attributes can include at least one of a group owner, an administrator, or an ordinary member. For example, a conversation group with the first user account as the group owner can be obtained from the conversation group set as the target conversation group.
[0043] The session group migration request is used to request the migration of the session group, updating the target session group from a common session group to an associated session group, which may also be referred to as an intercommunication group. The associated session group includes at least one first user account and at least one second user account. The group message in the associated session group may be a message input into the associated session group by a user using a first social application logged in with a first user account, or a message input into the associated session group by a user using a second social application logged in with a second user account. The first server may obtain the associated session group. The session group migration request may carry a session group identifier corresponding to the target session group. The session group identifier is used to uniquely identify the session group. It should be noted that session group migration does not mean removing a session group from a first social application and migrating it to a second social application, but rather updating the session group to a session group shared by the first social application and the second social application, that is, a session group intercommunication between the first social application and the second social application.
[0044] Specifically, the first server can obtain various conversation groups of the first user account in the first social application based on the first user account to form a conversation group set. Each conversation group in the conversation group set includes the first user account. The target conversation group can be selected from the conversation group set. For example, the first server can select at least one conversation group from the conversation group set to obtain the target conversation group. For example, the target conversation group can be randomly selected from the conversation group set.
[0045] In some embodiments, the first server may use at least one of the conversation group sets as a candidate conversation group. The first server may randomly select a candidate conversation group from the conversation group set, or obtain candidate conversation groups from the conversation group set that meet conversation group screening conditions to form a candidate conversation group set. The conversation group screening conditions may include at least one of the following: the first user account being a member of a specific group or the conversation group type being of a specific group type. The specific group member may be, for example, a group owner, and the specific group type may be, for example, at least one of a government group, a resident group, or a customer group. The target conversation group may be selected from each candidate conversation group set. For example, the first server may send each candidate conversation group set to a first social application logged in by the first user account. The first social application may display the candidate conversation group set. When the first social application receives a selection operation on a candidate conversation group in the candidate conversation group set, the first server may use the candidate conversation group selected by the selection operation as the target conversation group. The interface displaying the candidate conversation group set may also display a group migration control. When the first social application receives a trigger operation on the group migration control, the first server uses the candidate conversation group selected by the selection operation as the target conversation group and sends a conversation group migration request carrying the conversation group identifier of the target conversation group to the first server.
[0046] In some embodiments, the candidate session group set is obtained by the first server in response to a candidate migration session group acquisition request. The candidate migration session group acquisition request may be sent to the first server by a first social application logged in by the first user account. For example, the first social application logged in by the first user account may display a group migration confirmation interface, which is used to trigger an operation to obtain candidate migration session groups. When the first social application receives the candidate migration session group acquisition operation through the group migration confirmation interface, it triggers the sending of a candidate migration session group acquisition request to the first server.
[0047] In some embodiments, the group migration determination interface may be displayed by the first social application in response to an application jump request sent by the second social application logged in by the second user account corresponding to the first user account. The application jump request may carry an interface identifier of the group migration determination interface, and the first social application may display the group migration determination interface based on the interface identifier. Among them, the group application jump request may be triggered when the second social application receives a group migration operation for the first social application. For example, the second social application may display a session group migration entry corresponding to the first social application. The session group migration entry corresponding to the first social application is used to trigger the group migration operation for the first social application. The group migration operation of the first social application triggers the first user account to be logged in to the second social application corresponding to the second user account of the session group migration of the first social application. Assuming that the first social application and the second social application are installed in the terminal, the first user account is logged in in the first social application, and the second user account corresponding to the first user account is logged in in the second social application, such as Figure 3 As shown, the terminal displays an interface (a) in the second social application, and the interface (a) displays a session group migration entrance 302. When the second social application receives a trigger operation on the session group migration entrance 302, it sends an application jump request to the first social application, and the interface displayed in the terminal switches from (a) to the group migration determination interface (b) in the first social application. The group migration determination interface (b) displays a group migration determination control 304. When the first social application receives a trigger operation on the group migration determination control 304, it can send a candidate migration session group acquisition request to the first server.
[0048] S204 , in response to the session group migration request, add the second user account corresponding to the first user account in the second social application to the target session group, and update the target session group to a session group associated with the first social application and the second social application.
[0049] The conversation group associated with the first and second social applications can become an intercommunication group, an associated conversation group, or a migrated conversation group of the first and second social applications. The intercommunication group can appear in both the first and second social applications. The intercommunication group can send messages received from the first social application to the second social application, and can also send messages received from the second social application to the first social application. A migrated conversation group can be associated with a migration identifier, which is used to indicate that the conversation group was obtained through migration.
[0050] Specifically, the first server may obtain a second user account corresponding to the first user account. The second user account is a user account established in the second social application. The second user account corresponding to the first user account may be obtained from the second server. The first server may store the second user account corresponding to the first user account. The first server may add the second user account to the target conversation group and update the group attribute of the target conversation group from a common group to an interconnected group. Prior to adding the second user account to the target conversation group, the target conversation group was a common group. After adding the second user account to the target conversation group, the group attribute of the target conversation group was updated to an interconnected group.
[0051] In some embodiments, when the first server adds the second user account to the target conversation group, it can change the group owner of the target conversation group to the second user account. For example, if the target conversation group is conversation group A in a first social application, where Zhang San has user account 1 in the first social application and user account 2 in the second social application, and user account 1 is the group owner of conversation group A, the first server can add user account 2 to conversation group A, update the group owner of conversation group A from user account 1 to user account 2, and update the group attribute of the conversation group from a common group to an interconnected group.
[0052] S206: Send group migration information corresponding to the target conversation group to the second server corresponding to the second social application, so that the second server uses the target conversation group as the conversation group corresponding to the second social application based on the group migration information.
[0053] The group migration information is used to prompt that the conversation group migration is successful. The group migration information may carry the conversation group identifier of the target conversation group and may also include each user account included in the target conversation group.
[0054] Specifically, when the first server determines that the target conversation group is updated to a conversation group associated with the first social application and the second social application, it can send group migration information for the target conversation group to the second server. The second server can obtain the conversation group identifier of the target conversation group from the group migration information and obtain conversation group display information for the target conversation group based on the conversation group identifier. The conversation group display information can include the migration identifier and the conversation group identifier of the target conversation group, and can also include the individual user accounts included in the target conversation group.
[0055] In some embodiments, the second server can obtain a session group identifier corresponding to the target session group from the group migration information, and add the session group identifier of the target session group to the second group identifier set corresponding to the second user account, thereby making the target session group the session group of the second user account in the second social application. The second group identifier set is the identifier of the session group of the second user account in the second social application, and the session groups corresponding to the identifiers in the second group identifier set include the second user account corresponding to the first user account.
[0056] In some embodiments, when the second server receives group migration information, it can send a group add request for the target conversation group to the second social application logged in by the second user account corresponding to the first user account. The group add request can carry conversation group related information corresponding to the target conversation group. The second social application logged in by the second user account can respond to the group add request and add the target conversation group to the second social application, that is, use the target conversation group as the conversation group of the second user account in the second social application, and can display the target conversation group. When displaying the target conversation group, a corresponding migration identifier can be displayed.
[0057] In some embodiments, when the target conversation group is updated to a conversation group associated with the first social application and the second social application, the first server can obtain the first group message input into the target conversation group by each user in the target conversation group through the first social application, and can send the first group message obtained from the first server to the second server. The second server can send the first group message obtained from the second server to the second social application logged in by the second user account, thereby displaying the first group message in the conversation interface of the target conversation group of the second social application logged in by the second user account.
[0058] In some embodiments, when the target conversation group is updated to a conversation group associated with a first social application and a second social application, the second server may obtain a second group message entered into the target conversation group by a user logged into the second social application with a second user account, and send the second group message to the first server. The first server may obtain a conversation account set corresponding to the target conversation group, where the conversation account set includes each user account in the target conversation group that belongs to the first social application. For example, the target conversation group is conversation group A in the first social application, where Zhang San has user account 1 in the first social application and user account 2 in the second social application. Conversation group A includes user accounts 1, 2, and 3, with user account 1 being the group owner of conversation group A. The first server may add user account 2 to conversation group A, update the group owner of conversation group A from user account 1 to user account 2, and update the group attribute of the conversation group from a common group to an intercommunication group. The set consisting of user accounts 1, 2, and 3 is then the conversation account set. The second server may determine the conversation endpoints corresponding to each user account in the conversation account set and send the second group message to the conversation endpoints corresponding to each user account. This enables user accounts in different social applications to conduct conversations, so that the second user account can conduct conversations with users belonging to the first social application in the target conversation group through the target conversation group of the second social application, thereby improving conversation efficiency.
[0059] like Figure 4 The figure shows a sequence diagram of the conversation group migration method in some embodiments, in which "user selects a group and clicks to upgrade" means that the first social application determines the target conversation group in response to the selection operation of the candidate conversation group in the candidate conversation group set, and sends a conversation group migration request to the first server. The process of updating the conversation group to an intercommunication group can also be called an upgrade of the conversation group. "Pulling a second user account into the group" means adding the second user account corresponding to the first user account in the second social application to the target conversation group. "Modifying the group owner and modifying the group attribute to an intercommunication group" means modifying the group owner of the target conversation group to the second user account added to the target conversation group. "Notifying and pushing new group information" means sending the message input by the user in the first social application to the target conversation group to the second server. "Notifying the corresponding account group of changes" means notifying the second social application that there is a new message updated in the target conversation group.
[0060] In some embodiments, the target conversation group in the second social application includes existing user accounts in the target conversation group and second user accounts added to the target conversation group. The existing user accounts refer to user accounts in the first social application included in the target conversation group. The existing user accounts in the target conversation group in the second social application may correspond to a first application account identifier, which indicates that the existing user accounts are user accounts registered in the first social application, or may correspond to an external application account identifier, which indicates that the existing user accounts are user accounts registered in an application other than the second social application. A user can enter a group message into the target conversation group in the first social application logged in with the first user account, or a user can enter a group message into the target conversation group in the second social application logged in with the second user account.
[0061] In the above-mentioned conversation group migration method, the second user account corresponding to the first user account in the second social application is added to the target conversation group, the target conversation group is updated to a conversation group associated with both the first and second social applications, and group migration information corresponding to the target conversation group is sent to the second server corresponding to the second social application. Based on the group migration information, the second server then uses the target conversation group as the conversation group in the second social application, thereby rapidly migrating the conversation group and improving the efficiency of conversation group establishment. Furthermore, because the target conversation group was a conversation group in the first social application before the update, and the target conversation group is now a conversation group in the second social application after the update, the target conversation group belongs to both the first and second social applications. This allows conversation messages in the target conversation group to be communicated between the first and second social applications, thereby improving conversation efficiency.
[0062] In some embodiments, the method further includes: receiving a candidate migration session group acquisition request sent by a first social application logged in through a first user account; in response to the candidate migration session group acquisition request, selecting a session group whose group member attributes of the first user account meet the member attribute conditions from the session group set corresponding to the first user account, and forming the session groups that meet the member attribute conditions into a candidate session group set; sending the candidate session group set to the terminal corresponding to the first user account, so that the terminal displays the candidate session group set through the first social application, and in response to a selection operation on a candidate session group in the candidate session group set, using the selected candidate session group as the target session group to be migrated.
[0063] The candidate migration session group acquisition request is used to request candidate session groups, where the group member attributes of the first user account in the candidate session groups meet a member attribute condition. The member attribute condition can be preset or configured as needed, for example, the member attribute can be group owner. The session group set includes multiple session groups, each of which includes the first user account. The group member attributes can include at least one of group owner, administrator, or ordinary member.
[0064] Specifically, the first server may obtain group member attributes of each conversation group of the first user account in the conversation group set. When the group member attributes meet the membership attribute conditions, the conversation group meeting the membership attribute conditions is selected as a candidate conversation group. For example, the first server may select, from the conversation group set, a conversation group in which the first user account is the group owner as a candidate conversation group.
[0065] In some embodiments, in response to a request to obtain candidate migration conversation groups, the first server detects a second user account corresponding to the first user account in the second social application. Upon determining that the second user account is detected, the first server selects a candidate conversation group set from the conversation group set corresponding to the first user account. For example, the first server may send an account acquisition request to the second server, the account acquisition request including the first user account. The second server may then, based on the first user account, acquire the second user account corresponding to the first user account and return the second user account to the first server.
[0066] In some embodiments, the candidate migration session group acquisition request carries target ticket information, which is obtained by the second server from the first server. The account acquisition request may be triggered when the target ticket information is verified and successfully verified. For example, the first server may compare the target ticket information with locally stored verification ticket information and, if the comparison is consistent, send the account acquisition request to the second server.
[0067] In this embodiment, conversation groups whose group member attributes of the first user account meet the member attribute conditions are selected from the conversation group set corresponding to the first user account to form a candidate conversation group set, thereby limiting the conversation groups that can be migrated. Not all conversation groups can be migrated, thereby improving the standardization of conversation group migration.
[0068] In some embodiments, in response to a request to obtain a candidate migration session group, a session group whose group member attributes of the first user account meet the member attribute conditions is selected from the session group set corresponding to the first user account, and the session groups that meet the member attribute conditions are formed into a candidate session group set, including: in response to the request to obtain a candidate migration session group, detecting a second user account associated with the first user account corresponding to a second social application; when the second user account is detected, a session group whose group member attributes of the first user account meet the member attribute conditions is selected from the session group set corresponding to the first user account, and the session groups that meet the member attribute conditions are formed into a candidate session group set.
[0069] Specifically, the second social application can include multiple second user accounts corresponding to the first user account. The second server can select a second user account from the second user accounts corresponding to the first user account as the selected user account, and send the selected user account to the first server. The first server will add the selected user account to the target conversation group and update the target conversation group.
[0070] In some embodiments, the first server may pre-store various second user accounts corresponding to the first user account, and the first server may obtain the second user account from the second server. For example, the first server may send an account acquisition request to the second server to obtain the second user account.
[0071] In some embodiments, the second server can determine the selected user account based on the second user account logged in to the second social application at the current time. For example, the second user account logged in to the second social application at the current time can be used as the selected user account. For example, user A has two accounts in the second social application, namely Account 1 and Account 2. The user logged in at the current time is Account 1, so Account 1 can be used as the selected user account.
[0072] In this embodiment, when a second user account is detected, a candidate conversation group set is obtained. Since the target conversation group is obtained from the candidate conversation group set, and the second user account needs to be added to the target conversation group before the target conversation group can be updated to a conversation group associated with the first social application and the second social application, if there is no second user account, the target conversation group cannot be updated even if it is obtained. Therefore, before obtaining the candidate conversation group set, determining whether there is a second user account that meets the requirements can reduce invalid execution processes and improve the efficiency of conversation group migration.
[0073] In some embodiments, in response to a candidate migration session group acquisition request, detecting a second user account associated with a first user account corresponding to a second social application includes: in response to the candidate migration session group acquisition request, sending an account acquisition request to a second server, the account acquisition request carrying the first user account, so that the second server acquires the associated second user account based on the first user account; when the second user account returned by the second server is received, it is confirmed that the second user account has been detected.
[0074] The account acquisition request is used to request the acquisition of a second user account associated with the first user account in the second social application, where the first user account and the associated second user account belong to the same user. Specifically, the account acquisition request may be sent to the second server after the first server performs ticket verification and the verification is successful. For example, the candidate migration session group acquisition request may carry target ticket information. The first server may respond to the candidate migration session group acquisition request, obtain the target ticket information from the candidate migration session group acquisition request, and compare the target ticket information with the locally stored verification ticket information of the second social application corresponding to the second user account. If the comparison is consistent, it is determined that the ticket verification has passed and the account acquisition request is sent to the second server.
[0075] In some embodiments, the target ticket information in the candidate migration session group acquisition request may be obtained from the second server. Specifically, the second server may receive a group migration trigger request, which is used to trigger the session group of the first user account in the first social application to be used as the session group of the second user account in the second social application associated with the first user account. In response to the group migration trigger request, the second server may send a ticket acquisition request to the first server, and the ticket acquisition request may carry the first user account. The first server may generate verification ticket information in response to the ticket acquisition request, and may establish a corresponding relationship between the first user account and the verification ticket information, so that the verification ticket information may be obtained based on the first user account. The first server may send the verification ticket information to the second server, and the second server may use the verification ticket information received from the first server as the target ticket information.
[0076] In some embodiments, the second server can send the target ticket information to the second social application logged in by the second user account. The second social application can generate an application jump request based on the obtained target ticket information. The application jump request can carry the target ticket information. The second social application can send an application jump request to the first social application logged in by the first user account. The application jump request is used to request that the currently displayed interface be switched from the interface in the second social application to the interface in the first social application.
[0077] In some embodiments, an application redirect request may carry a destination interface identifier. When the first social application receives the application redirect request, it determines the interface to display based on the destination interface identifier carried in the application redirect request. When the first social application determines that the destination interface identifier is the identifier of the group migration determination interface, the first social application may respond to the application redirect request by displaying the group migration determination interface, receive a candidate migration session group acquisition operation through the group migration determination interface, and send a candidate migration session group acquisition request to the first server in response to the candidate migration session group acquisition operation. For example, the group migration determination interface may display a group migration determination control. When the first social application detects a trigger operation on the group migration determination control, it may determine that a candidate migration session group acquisition operation has been obtained and send a candidate migration session group acquisition request to the first server.
[0078] In this embodiment, when the first terminal receives the second user account to be returned by the second server, it confirms that the second user account is detected and obtains the candidate session group set, so that the candidate session group set can be obtained when the existence of the second user account is determined, reducing invalid execution processes and improving the efficiency of session group migration.
[0079] In some embodiments, the candidate migration session group acquisition request carries target ticket information, and the method also includes: receiving a ticket acquisition request sent by the second server, the ticket acquisition request is triggered by a group migration trigger operation triggered in the second social application, and a second user account is logged in to the second social application; in response to the ticket acquisition request, generating verification ticket information, and returning the verification ticket information to the second server; in response to the candidate migration session group acquisition request, sending an account acquisition request to the second server includes: in response to the candidate migration session group acquisition request, acquiring the ticket information in the candidate migration session group acquisition request, and when the ticket information in the candidate migration session group acquisition request is compared and consistent with the verification ticket information, sending an account acquisition request to the second server.
[0080] The ticket acquisition request is used to request ticket information from the first server. The ticket information is used to verify the legitimacy of the ticket. The ticket acquisition request is triggered by a group migration trigger operation triggered in the second social application. The group migration trigger operation can be triggered by a session group migration entry in the second social application, for example, by Figure 3 When the second social application receives the trigger operation on the session group migration entrance 302, it sends a group migration trigger request to the second server. The second server can send a ticket acquisition request to the first server in response to the group migration trigger request.
[0081] Specifically, the ticket acquisition request may carry the first user account. The first server may generate verification ticket information in response to the ticket acquisition request, establish a corresponding relationship between the generated verification ticket information and the first user account, and return the verification ticket information to the second server.
[0082] In some embodiments, when the second server receives the ticket information returned by the first server, it sends the received ticket information as target ticket information to the second social application logged in by the second user account. The second social application can send an application jump request carrying the target ticket information to the first social application logged in by the first user account based on the target ticket information.
[0083] In some embodiments, the group migration trigger request may carry a first user account or a second user account. The second server may respond to the group migration trigger request and perform a user legitimacy verification based on the first user account or the second user account. When the verification passes, a ticket acquisition request is sent to the first server.
[0084] For example, Figure 5 The figure shows a sequence diagram of a session group migration method in some embodiments, wherein "clicking to request a ticket upgrade" means that the second social application receives a trigger operation for the session group migration entry and sends a group migration trigger request to the second server. "Verifying user legitimacy" means that the second server verifies the first and second user accounts contained in the group migration trigger request. "Requesting a ticket for this redirect" means that if the "verification of user legitimacy" results in a successful verification, the second server sends a ticket acquisition request to the first server. "Internally determining and issuing a ticket" means that the first server generates verification ticket information in response to the ticket acquisition request. "Redirecting with a ticket" means that the second social application sends an application redirect request containing ticket information to the first social application. "User redirects to the first social application to perform operations" means that the group migration confirmation interface is displayed in the first social application. "Determining ticket legitimacy" means comparing the ticket information in the application redirect request, i.e., the target ticket information, with the verification ticket information corresponding to the first user account stored on the first server. "Requesting the identity of the user in the second social application" means obtaining the second user account corresponding to the first user account. "Returning the corresponding identity" means sending the second user account to the first server, and "returning the list of upgradeable groups" means sending the candidate conversation groups to the first social application logged in by the first user account. Because the first and second social applications are independent applications, when switching from the second social application to the first social application, a ticket is required as a mutual agreement verification to ensure the user's current operation is legal.
[0085] In this embodiment, the target ticket information is compared with the verification ticket information. If the comparison is consistent, it means that the candidate migration session group acquisition request is legal. Therefore, if the comparison is consistent, the account acquisition request is sent to the second server, which can improve the security of the session group migration and reduce the occurrence of malicious migration of the session group.
[0086] In some embodiments, the method also includes: receiving a second group message for the target conversation group sent by the second server, the second group message being sent by a second social application logged in through a second user account; obtaining a set of conversation accounts corresponding to the first social application in the target conversation group; sending the second group message and the second user account to the conversation end corresponding to each conversation account in the conversation account set, so that the conversation end displays the second group message in the conversation interface of the target conversation group in the first social application, and displays the account information corresponding to the second user account corresponding to the second group message.
[0087] The second group message is sent via a second social application logged in by a second user account. The second group message may be a message entered by a user into the target conversation group within the second social application logged in by the second user account. The conversation account set includes each user account belonging to the first social application in the target conversation group. The target account information may include at least one of a user account, an avatar, or a nickname.
[0088] Specifically, when the second social application logged in by the second user account obtains the second group message input by the user into the target conversation group, the second social application can send the second group message to the second server, the second server can store the second group message, and can send the second group message to the first server, the first server can store the second group message, and can push the second group message to the conversation ends of each user account in the target conversation group in the first social application.
[0089] In some embodiments, a user account in a target conversation group in a first social application can log in to the first social application using a corresponding conversation terminal. The conversation interface corresponding to the target conversation group can be displayed in the first social application. When the conversation terminal receives a conversation message acquisition operation for the target conversation group, it can send a conversation message acquisition request to the first server. The conversation message acquisition request can carry the conversation group identifier and user account of the target conversation group. The first server can respond to the conversation message acquisition request and return the second group message to the sender of the conversation message acquisition request.
[0090] In some embodiments, when the conversation end receives the second group message and the second user account returned by the first server, it can obtain the account information of the second user account and display the second group message and the account information of the second user account in the conversation interface.
[0091] In this embodiment, the second group message and the second user account are returned to the session end corresponding to each session account in the session account set, so that the session end can display the second group message in the session interface of the target session group of the first social application, thereby realizing message communication between different social applications and improving session efficiency.
[0092] In some embodiments, as Figure 6 As shown, a session group migration method is provided, which is applied to Figure 1 Taking the second server 106 in the example as an example, the method includes the following steps:
[0093] S602, receiving group migration information corresponding to a target session group sent by a first server corresponding to a first social application; wherein the target session group includes a first user account corresponding to the first social application, and the first server responds to a session group migration request for the target session group, adds a second user account corresponding to the first user account in the second social application to the target session group, and triggers the sending of the group migration information.
[0094] The target conversation group includes a first user account corresponding to the first social application. The conversation group migration request is used to request that the conversation group of the first user account in the first social application be migrated to a second user account corresponding to the first user account in the second social application, thereby obtaining an interoperable group. This allows the conversation group in the first social application to become a conversation group shared or interoperable by the first and second social applications, thereby enabling intercommunication of conversation messages between different social applications.
[0095] The group migration information may include the conversation group identifier of the target conversation group, and may also include the user account corresponding to each conversation user included in the target conversation group or the account information corresponding to the user account.
[0096] Specifically, the group migration information can be triggered after the second user account is added to the target conversation group. For example, the first server can receive a conversation group migration request for the target conversation group, add the second user account corresponding to the first user account in the second social application to the target conversation group, and modify the group attributes of the target conversation group to an intercommunication group. When it is determined that the second user account has been added to the target conversation group and the group attributes of the target conversation group have been modified to an intercommunication group, the group migration information corresponding to the target conversation group is sent to the second server.
[0097] S604: Based on the group migration information, the target conversation group is used as the conversation group corresponding to the second social application.
[0098] Specifically, the second server can obtain the session group identifier corresponding to the target session group from the group migration information, use it as the first group identifier of the target session group, and add the first group identifier to the set of session group identifiers corresponding to the second user account, so that the target session group becomes the session group of the second user account in the second social application. The set of session group identifiers may include the identifiers of each session group corresponding to the second user account in the second social application.
[0099] In some embodiments, the second server may generate a second group identifier corresponding to the target conversation group, establish a correspondence between the first group identifier and the second group identifier, and add the second group identifier to the conversation group identifier set corresponding to the second user account, thereby making the target conversation group the conversation group of the second user account in the second social application.
[0100] S606: Send a group establishment notification message corresponding to the target conversation group to the terminal corresponding to the second user account, so that the terminal displays the target conversation group based on the group establishment notification message through the second social application.
[0101] The group establishment notification message is used to notify that a new conversation group has been established in the second social application, that is, the target conversation group has been added to the second social application. The group establishment notification message may carry the conversation group identifier of the target conversation group and may also carry user accounts in the target conversation group.
[0102] Specifically, when the second server uses the target conversation group as the conversation group in the second social application, the second server can send a group establishment notification message to the second social application logged in by the second user account. The group establishment notification message may include the conversation group identifier of the target conversation group. The second social application logged in by the second user account can display the target conversation group in the conversation interface of the second social application logged in by the second user account based on the conversation group identifier of the target conversation group.
[0103] In the above-mentioned conversation group migration method, group migration information corresponding to a target conversation group is received from a first server corresponding to a first social application. Based on the group migration information, the target conversation group is identified as a conversation group corresponding to a second social application. A group establishment notification message corresponding to the target conversation group is sent to a terminal corresponding to a second user account. The terminal can then display the target conversation group in the second social application based on the group establishment notification message, thereby quickly migrating the conversation group in the first social application to the second social application, thereby improving the efficiency of conversation group establishment. In addition, since the target conversation group is a conversation group in the first social application, migrating the conversation group in the first social application to a conversation group in the second social application through migration makes the target conversation group a conversation group that communicates between the first social application and the second social application. Thus, conversation messages in the first social application can be sent to the second social application, and conversation messages in the second social application can also be sent to the first social application, thereby improving conversation interoperability and conversation efficiency.
[0104] In some embodiments, the target conversation group is selected from a set of displayed candidate conversation groups, and the method further includes: receiving a group migration trigger request; the group migration trigger request is generated in response to a group migration trigger operation received by a second social application, and the second social application has a second user account logged in; in response to the group migration trigger request, sending a ticket acquisition request to the first server; receiving the ticket information returned by the first server in response to the ticket acquisition request as the target ticket information, and returning the target ticket information to the terminal corresponding to the second user account, so that the terminal jumps from the second social application to the first social application based on the target ticket information, and obtains the candidate conversation clusters through the first social application for merged display.
[0105] The group migration trigger request is used to trigger the migration of a conversation group of a first user account in a first social application to a conversation group to which a second application account in a second social application corresponding to the first user account belongs.
[0106] The group migration trigger operation is used to trigger a group migration trigger request. The group migration trigger operation can be any operation, such as a slide or a click, for example, a click on the session group migration entry displayed in the second social application. The ticket acquisition request is used to request the ticket information required for verification to complete the group migration.
[0107] Specifically, when the first server receives a ticket acquisition request sent by the second server, it can generate verification ticket information for the first server and return the verification ticket information to the second server. The second server can use the received ticket information as target ticket information and return the target ticket information to the second social application logged in by the second user account. The second social application can send an application jump request to the first social application logged in by the first user account based on the target ticket information. The application jump request can carry the target ticket information. The first social application responds to the application jump request, obtains a candidate conversation group set from the first server, and displays the candidate conversation group set in the first social application.
[0108] In some embodiments, the group migration trigger operation is a trigger operation of the session group migration entrance displayed in the second social application. The second social application can be logged in with the help of the first user account, that is, the second social application logged in with the second user account can be logged in with the help of the first user account. For example, the second social application can send a login request to the second server, and the login request can carry the first user account. The second server can log in to the second social application corresponding to the second user account based on the first user account. Figure 7 As shown, it shows that the second social application uses the first user account to log in to the second social application.
[0109] In some embodiments, when the second server determines that the second user account has been successfully logged into the second social application, the second server can obtain the attribute information of the user corresponding to the second user account, determine the group migration authority based on the user's attribute information, and display the session group migration entrance in the first social application when it is determined that the second user account has the group migration authority. Figure 7 As shown, the group migration permission can be determined by the second server or by other devices. For example, the second server can send a permission judgment request to the asynchronous judgment server. The permission judgment request can carry the attribute information of the user corresponding to the second user account. The asynchronous judgment server can determine whether the second user account has the group migration permission based on the user's attribute information, and return the judgment result to the second social application.
[0110] In this embodiment, the ticket information returned by the first server in response to the ticket acquisition request is received as the target ticket information, and the target ticket information is returned to the terminal corresponding to the second user account, so that the terminal jumps from the second social application to the first social application based on the target ticket information. Since the target ticket information is obtained from the first server, the first server can compare the target ticket information with the verification ticket generated in the first server to verify whether the ticket is legal. When the verification ticket is legal, a candidate session group set is obtained and the candidate session group set is sent to the first social application, thereby improving the security of session group migration and reducing malicious group migration.
[0111] In some embodiments, the group migration information includes a first group identifier corresponding to the target conversation group, and using the target conversation group as the conversation group corresponding to the second social application based on the group migration information includes: generating a second group identifier corresponding to the target conversation group and a migration identifier corresponding to the second group identifier, and establishing a corresponding relationship between the second group identifier and the first group identifier; the method further includes: receiving a group message sending request corresponding to the second user account, the group message sending request carrying the second group message and the second group identifier; when it is detected that the second group identifier has a corresponding migration identifier,
[0112] The migration identifier may be preset or set as needed, and the migration identifier is used to indicate that the target conversation group in the second social application is obtained through migration.
[0113] The group message sending request is used to request that the second group message be sent to the session ends of each user account in the target session group. The group message sending request may carry the second group message and the second group identifier, and may also carry the second user account.
[0114] Specifically, when the second server determines that there is a corresponding migration identifier for the second group identifier, that is, when it determines that the target conversation group in the second social application is obtained through migration, the second server can determine the corresponding first group identifier based on the second group identifier based on the correspondence between the first group identifier and the second group identifier, and send the second group message, the first group identifier and the second user account to the first server.
[0115] In some embodiments, when the first server receives the second group message and the first group identifier sent by the second server, it determines based on the first group identifier that the second group message is the group message corresponding to the target conversation group. The first server can then send the second group message to the conversation ends of each user account in the target conversation group, and the conversation ends can display the second user account and the second group message accordingly in the conversation interface corresponding to the first social application.
[0116] In this embodiment, a correspondence between the second group identifier and the first group identifier is established, a second group identifier corresponding to the target conversation group and a migration identifier corresponding to the second group identifier are generated, and a group message sending request corresponding to the second user account is received. When it is detected that the second group identifier has a corresponding migration identifier, the second group message and the first group identifier are sent to the first server. Therefore, based on the correspondence between the first group identifier and the second group identifier, a correspondence can be established between the target conversation group in the first social application and the target conversation group in the second social application, so that messages in the target conversation group can be communicated between the first social application and the second social application, thereby improving conversation efficiency.
[0117] In some embodiments, a method for migrating a session group is provided. Figure 1 Taking the terminal 102 in the example as an example, the following steps are included: displaying a set of candidate conversation groups to be migrated corresponding to the first user account. In response to a selection operation on a candidate conversation group in the set of candidate conversation groups, the selected candidate conversation group is used as a target conversation group; the target conversation group includes the first user account corresponding to the first social application. A conversation group migration request is triggered for the target conversation group to request the first server corresponding to the first social application to add the second user account corresponding to the first user account in the second social application to the target conversation group, and group migration information corresponding to the target conversation group is sent to the second server corresponding to the second social application, so that the second server uses the target conversation group as the conversation group corresponding to the second social application based on the group migration information.
[0118] In the above-mentioned conversation group migration method, a set of candidate conversation groups to be migrated corresponding to a first user account is displayed. In response to a selection operation on a candidate conversation group in the set of candidate conversation groups, the selected candidate conversation group is selected as a target conversation group. The target conversation group includes the first user account corresponding to a first social application. A conversation group migration request is triggered for the target conversation group, requesting a first server corresponding to the first social application to add a second user account corresponding to a second social application of the first user account to the target conversation group. Group migration information corresponding to the target conversation group is then sent to a second server corresponding to the second social application, so that the second server, based on the group migration information, selects the target conversation group as the conversation group corresponding to the second social application. This allows the conversation group of the first social application to be quickly migrated to the second social application, thereby improving the efficiency of conversation group establishment. Furthermore, the target conversation group becomes a conversation group for intercommunication between the first and second social applications, thereby enabling conversation messages in the first social application to be sent to the second social application, and vice versa, thereby improving conversation interoperability and efficiency.
[0119] In some embodiments, displaying the set of candidate conversation groups to be migrated corresponding to the first user account includes: receiving an application jump request for the first social application triggered by the second social application; when the application jump request is triggered in response to a group migration operation for the first social application, displaying the set of candidate conversation groups to be migrated corresponding to the first user account.
[0120] The application redirect request for the first social application is used to request a redirect from the second social application to the first social application. The application redirect request may carry a destination interface identifier, which is the identifier of the interface displayed after redirecting to the first social application. The destination interface identifier may be the identifier of the interface for determining group migration.
[0121] Specifically, a second social application logged in by the second user account can display a session group migration portal. When the second social application detects a trigger operation on the session group migration portal, it generates an application jump request to the first social application. The second social application logged in by the second user account can be logged in using the first user account.
[0122] In some embodiments, the first social application obtains a destination interface identifier from the application jump request, and when it is determined that the destination interface identifier is an identifier of a group migration confirmation interface, it is determined that the application jump request is triggered in response to a group migration operation for the second social application.
[0123] In some embodiments, the first social application can display a group migration confirmation control on the group migration confirmation interface. When a trigger operation on the group migration confirmation control is obtained, a candidate migration session group acquisition request is sent to the first server. The first server returns a candidate session group set to the first social application, and the first social application displays the candidate session group set.
[0124] In this embodiment, an application jump request for a first social application triggered by a second social application is received. When the application jump request is triggered in response to a group migration operation for the first social application, a set of candidate session groups to be migrated corresponding to the first user account is displayed, thereby improving the standardization of the session group migration process.
[0125] In some embodiments, a method for migrating a session group is provided. Figure 1 Taking the terminal 102 in the example as an example, the following steps are included: displaying a social application interface corresponding to the second user account logged in to the second social application; receiving a group migration operation for the first social application through the social application interface; triggering an application jump request for the first social application in response to the group migration operation, so as to request to jump from the second social application to the first social application, so that the first social application obtains a set of candidate conversation groups to be migrated corresponding to the first user account logged in to the first social application, and displays the set of candidate conversation groups to be migrated.
[0126] In the above-mentioned conversation group migration method, a social application interface corresponding to a second user account logged in to a second social application is displayed, a group migration operation for a first social application is received through the social application interface, and an application jump request for the first social application is triggered in response to the group migration operation, requesting to jump from the second social application to the first social application, so that the first social application obtains a set of candidate conversation groups to be migrated corresponding to the first user account logged in to the first social application and displays the set of candidate conversation groups to be migrated. Based on the group migration operation, the user jumps from the second social application to the first social application and obtains the set of candidate conversation groups to be migrated. Thus, conversation groups in the set of candidate conversation groups can be migrated to the second social application, thereby improving the efficiency of establishing conversation groups and making the target conversation group a conversation group for intercommunication between the first and second social applications. Thus, conversation messages in the first social application can be sent to the second social application, and conversation messages in the second social application can also be sent to the first social application, thereby improving conversation interoperability and conversation efficiency.
[0127] In some embodiments, displaying a social application interface corresponding to a second user account logged in to a second social application includes: receiving attribute information of a user corresponding to the second user account sent by a second server, where the second server is a server corresponding to the second social application; when it is determined based on the user's attribute information that the second user account has group migration authority, displaying a session group migration entrance on the displayed social application interface, where the session group migration entrance is used to receive group migration operations for the first social application.
[0128] Specifically, the user's attribute information may include the user type corresponding to the second user account. The user type may include at least one of an enterprise type and a personal type. When it is determined that the second user account is of an enterprise type, it can be determined that the second user account has group migration permissions.
[0129] In this embodiment, when it is determined based on the user's attribute information that the second user account has the group migration permission, the session group migration entrance is displayed on the displayed social application interface, so that the permission of the displayed session group migration entrance can be judged, malicious group migration behavior is reduced, and the security of group migration is improved.
[0130] The present application also provides an application scenario, which applies the above-mentioned session group migration method.
[0131] Specifically, the application of the session group migration method in this application scenario is as follows:
[0132] 1. A second client corresponding to the second social application sends a login request to a second server corresponding to the second social application, where the login request carries the first user account and authorization information.
[0133] The second server obtains the first user account and authorization information from the login request and performs a login legitimacy check.
[0134] 2. The second server verifies the legitimacy of the first user account and the authorization information carried in the login request, and returns a prompt message indicating a successful login to the second client of the second social application when the verification is determined to be successful.
[0135] 3. Based on the prompt information of successful login, the second social application displays the social application interface of the second user account corresponding to the second social application.
[0136] 4. After determining that the second user account has logged into the second social application, the second server sends a group migration permission verification request to the asynchronous judgment server, where the group migration permission verification request carries the user's attribute information.
[0137] 5. The asynchronous judgment server responds to the group migration permission verification request and sends a verification pass message to the second client when it is determined based on the user's attribute information that the second user account has the group migration permission.
[0138] 6. The second client displays a session group migration entrance in the social application interface of the second user account corresponding to the second social application based on the verification pass information returned by the asynchronous judgment server.
[0139] 7. The second social application receives the trigger operation on the session group migration portal, determines that a group migration operation for the first social application has been received, and sends a group migration trigger request to the second server in response to the group migration operation.
[0140] 8. In response to the group migration trigger request, the second server sends a ticket acquisition request to the first server.
[0141] 9. The first server generates verification ticket information in response to the ticket acquisition request and returns the verification ticket information to the second server.
[0142] 10. The second server receives the ticket sent by the first server as target ticket information, and sends the target ticket information to the second social application.
[0143] 11. When the second social application receives the target ticket information, it sends an application jump request to the first social application; the application jump request carries the target ticket information.
[0144] 12. The first social application displays a group migration confirmation interface in response to the application jump request, receives a candidate migration session group acquisition operation through the group migration confirmation interface, and sends a candidate migration session group acquisition request to the first server; the candidate migration session group acquisition request carries target ticket information.
[0145] 13. In response to the candidate migration session group acquisition request, the first server compares the target ticket information with the verification ticket information. When the comparison is consistent, the first server sends an account acquisition request to the second server; the account acquisition request carries the first user account.
[0146] 14. The second server obtains a second user account associated with the first user account and corresponding to the second social application based on the first user account, and returns the obtained second user account to the first server.
[0147] 15. When the first server obtains the second user account associated with the first user account, it obtains the conversation group set corresponding to the first user account, obtains each conversation group with the first user account as the group owner from the conversation group set, and forms a candidate conversation group set; and sends the candidate conversation group set to the first social application logged in by the first user account.
[0148] 16. The first social application logged in by the first user account displays a set of candidate conversation groups, and in response to a selection operation on a candidate conversation group in the set of candidate conversation groups, uses the selected candidate conversation group as a target conversation group to be migrated, and when a conversation group migration operation for the target conversation group is received, sends a conversation group migration request for the target conversation group to the first server.
[0149] 17. In response to the session group migration request, the first server adds the second user account corresponding to the first user account in the second social application to the target session group, updates the target session group to an intercommunication group with the first social application and the second social application, and then sends a migration success message to the first social application logged in by the first user account.
[0150] 18. The first server sends the conversation message input into the target conversation group through the first social application to the second server.
[0151] 19. The second server stores the conversation message of the target conversation group obtained from the first server, and sends a prompt message of group message update for the target conversation group to the second social application logged in by the second user account.
[0152] like Figure 8 As shown, the first server updates the group owner and group attributes, and sends the group message to the second server.
[0153] 20. The second social application logged in by the second user account receives a group message acquisition operation for the target conversation group and sends a group message acquisition request to the second server.
[0154] 21. The second server responds to the group message acquisition request and sends the group message for the target conversation group received from the first server to the second social application logged in by the second user account.
[0155] 22. The second social application logged in by the second user account displays the received group message in the corresponding interface.
[0156] Currently, assuming that a user's user account in a first social application is a first user account, and a user account in a second social application is a second user account, and the user is the group owner of a conversation group A created in the first social application, when the user needs to migrate users in conversation group A to the second social application, a new conversation group B is usually created in the second social application, and the users in conversation group A can be invited to join conversation group B separately, or users in conversation group A can be called upon to join conversation group B by scanning a QR code of conversation group B. However, if conversation group A includes a large number of users, if it is necessary to completely migrate all users in conversation group A to conversation group B, each user in the group needs to be notified, which makes the migration difficult, and whether the migration is successful depends on each user in conversation group A. The overall process will take a long time, the migration efficiency is low, and there is no guarantee that all users in conversation group A will be migrated to conversation group B. That is, when the user transfers users from the old group to the new group, because the path is long, if there are relatively many people in a group, the overall migration work will be more cumbersome and difficult. Furthermore, the group owner needs to configure conversation group B, such as setting a group title, group announcements, and group administrators. Furthermore, users in the group need to manually set nicknames, which is quite cumbersome. Furthermore, during the migration, group messages become disconnected, effectively creating two groups. Before all users join the new group, the old group may not have been decommissioned. This can create two sets of message flows between the old and new groups, leading to confusion and difficulty integrating the new and old groups. When a user has multiple conversation groups, due to the varying speaking times and user information updates within each group, the user may not be able to fully access their existing group list. Furthermore, the migration workload increases exponentially with a large number of groups. For example, for an individual employee, the first and second social applications appear to be separate and independent. Migrating their customer group list from the first to the second application would require creating new groups one by one on the second application and then manually or through promotional campaigns to encourage group members to migrate. This makes both practicality and maintainability very low.
[0157] The conversation group migration method provided by this application allows all users in the current group to seamlessly switch to the new group. Users do not need to record and recall searches. With a single click, all conversation groups of the migrating user, in which they are the group owner, can be pulled out for screening. Chat records and all group attributes can be transferred without the administrator having to make additional settings. The entire migration process requires only two jump-click steps to complete the transfer of a complete conversation group to an intercommunication group. For example, a company service staff's customer base is considered corporate property. Therefore, when a company employee needs to transfer a resident group in a first social application to a manageable intercommunication group within a second social application, the company administrator can promptly understand the overall migration status and perform the group transfer at a low cost without losing any customers in the group.
[0158] It should be understood that although Figure 2-Figure 8 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. In addition, Figure 2-Figure 8 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The order of execution of these steps or stages is not necessarily one by one, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.
[0159] In some embodiments, as Figure 9 As shown, a session group migration device is provided. The device can adopt a software module or a hardware module, or a combination of the two to become a part of a computer device. The device specifically includes: a session group migration request receiving module 902, a session group updating module 904 and a group migration information sending module 906, wherein: the session group migration request receiving module 902 is used to receive a session group migration request for a target session group corresponding to a first user account; the target session group includes a first user account corresponding to a first social application; the session group updating module 904 is used to respond to the session group migration request, add a second user account corresponding to the first user account in the second social application to the target session group, and update the target session group to a session group associated with the first social application and the second social application; the group migration information sending module 906 is used to send group migration information corresponding to the target session group to a second server corresponding to the second social application, so that the second server uses the target session group as the session group corresponding to the second social application based on the group migration information.
[0160] In some embodiments, the device also includes: a candidate migration session group acquisition request receiving module, which is used to receive a candidate migration session group acquisition request sent by a first social application logged in through a first user account; a candidate session group set obtaining module, which is used to select, from the session group set corresponding to the first user account, a session group whose group member attributes of the first user account meet the member attribute conditions in response to the candidate migration session group acquisition request, and form the session groups that meet the member attribute conditions into a candidate session group set; a candidate session group set sending module, which is used to send the candidate session group set to the terminal corresponding to the first user account, so that the terminal displays the candidate session group set through the first social application, and in response to the selection operation of the candidate session group in the candidate session group set, use the selected candidate session group as the target session group to be migrated.
[0161] In some embodiments, the candidate conversation group set obtaining module includes: a candidate migration conversation group obtaining request response unit, used to detect a second user account associated with the first user account corresponding to the second social application in response to a candidate migration conversation group obtaining request; a candidate conversation group set obtaining unit, used to, when the second user account is detected, select a conversation group whose group member attributes of the first user account meet the member attribute conditions from the conversation group set corresponding to the first user account, and form the conversation groups that meet the member attribute conditions into a candidate conversation group set.
[0162] In some embodiments, the candidate migration session group acquisition request response unit is further used to send an account acquisition request to the second server in response to the candidate migration session group acquisition request, where the account acquisition request carries the first user account, so that the second server obtains the associated second user account based on the first user account; when the second user account returned by the second server is received, it is confirmed that the second user account has been detected.
[0163] In some embodiments, the candidate migration session group acquisition request carries target ticket information, and the device also includes: a ticket acquisition request receiving module, used to receive the ticket acquisition request sent by the second server, the ticket acquisition request is triggered by a group migration trigger operation triggered in the second social application, and a second user account is logged in to the second social application; a verification ticket information sending module, used to respond to the ticket acquisition request, generate verification ticket information, and return the verification ticket information to the second server; the candidate migration session group acquisition request response unit, also used to respond to the candidate migration session group acquisition request, obtain the ticket information in the candidate migration session group acquisition request; when the ticket information in the candidate migration session group acquisition request is consistent with the verification ticket information, an account acquisition request is sent to the second server.
[0164] In some embodiments, the device also includes: a second group message receiving module, used to receive a second group message for the target conversation group sent by the second server, the second group message is sent by the second social application logged in through the second user account; a session account set acquisition module, used to obtain the session account set corresponding to the first social application in the target conversation group; a second group message sending module, used to send the second group message and the second user account to the conversation end corresponding to each conversation account in the conversation account set, so that the conversation end displays the second group message in the conversation interface of the target conversation group in the first social application, and displays the account information corresponding to the second user account corresponding to the second group message.
[0165] In some embodiments, as Figure 10 As shown, a session group migration device is provided. The device can adopt a software module or a hardware module, or a combination of the two to form a part of a computer device. The device specifically includes: a group migration information receiving module 1002, a session group migration module 1004 and a group establishment notification message sending module 1006, wherein: the group migration information receiving module 1002 is used to receive group migration information corresponding to a target session group sent by a first server corresponding to a first social application; wherein the target session group includes a first user account corresponding to the first social application, and the first server responds to a session group migration request for the target session group, adds a second user account corresponding to the first user account in the second social application to the target session group, and triggers the sending of group migration information; the session group migration module 1004 is used to set the target session group as the session group corresponding to the second social application based on the group migration information; and the group establishment notification message sending module 1006 is used to send a group establishment notification message corresponding to the target session group to the terminal corresponding to the second user account, so that the terminal displays the target session group based on the group establishment notification message through the second social application.
[0166] In some embodiments, the target conversation group is selected from a set of displayed candidate conversation groups, and the device also includes: a group migration trigger request receiving module, used to receive a group migration trigger request; the group migration trigger request is generated in response to a group migration trigger operation received by a second social application, and the second social application has a second user account logged in; a ticket acquisition request sending module, used to send a ticket acquisition request to the first server in response to the group migration trigger request; a verification ticket information receiving module, used to receive the verification ticket information returned by the first server in response to the ticket acquisition request, and return the verification ticket information to the terminal corresponding to the second user account, so that the terminal jumps from the second social application to the first social application based on the verification ticket information, and obtains the candidate conversation cluster through the first social application for merged display.
[0167] In some embodiments, the group migration information includes a first group identifier corresponding to the target conversation group; the conversation group migration module includes: a migration identifier generation unit, used to generate a second group identifier corresponding to the target conversation group and a migration identifier corresponding to the second group identifier, and establish a correspondence between the second group identifier and the first group identifier; the device also includes: a group message sending request receiving module, used to receive a group message sending request corresponding to the second user account, the group message sending request carries the second group message and the second group identifier; the second group message sending module is used to obtain the first group identifier based on the correspondence when it is detected that there is a corresponding migration identifier for the second group identifier, and send the second group message and the first group identifier to the first server, so that the first server determines that the second group message is the second group message for the target conversation group based on the first group identifier.
[0168] In some embodiments, a session group migration device is provided. The device can adopt a software module or a hardware module, or a combination of the two to become part of a computer device. The device specifically includes: a candidate session group set display module, a target session group acquisition module, and a session group migration request triggering module, wherein the candidate session group set display module is used to display a set of candidate session groups to be migrated corresponding to a first user account; the target session group acquisition module is used to respond to a selection operation on a candidate session group in the candidate session group set and use the selected candidate session group as a target session group; the target session group includes a first user account corresponding to a first social application; and the session group migration request triggering module is used to trigger a session group migration request for the target session group, so as to request a first server corresponding to the first social application to add a second user account corresponding to the first user account in the second social application to the target session group, and send group migration information corresponding to the target session group to a second server corresponding to the second social application, so that the second server uses the target session group as the session group corresponding to the second social application based on the group migration information.
[0169] In some embodiments, the candidate conversation group set display module includes: an application jump request receiving unit, used to receive an application jump request for a first social application triggered by a second social application; a candidate conversation group set display unit, used to display the candidate conversation group set to be migrated corresponding to the first user account when the application jump request is triggered in response to a group migration operation for the first social application.
[0170] In some embodiments, a session group migration device is provided. The device can use a software module or a hardware module, or a combination of the two to become part of a computer device. The device specifically includes: a social application interface display module, a group migration operation receiving module, and an application jump request response module, wherein the social application interface display module is used to display the social application interface corresponding to the second user account logged in to the second social application; the group migration operation receiving module is used to receive a group migration operation for the first social application through the social application interface; the application jump request response module is used to trigger an application jump request for the first social application in response to the group migration operation, requesting to jump from the second social application to the first social application, so that the first social application obtains a set of candidate session groups to be migrated corresponding to the first user account logged in to the first social application, and displays the set of candidate session groups to be migrated.
[0171] In some embodiments, the social application interface display module includes: a user attribute information receiving unit, used to receive attribute information of the user corresponding to the second user account sent by the second server, the second server being the server corresponding to the second social application; a session group migration entrance display unit, used to display the session group migration entrance on the displayed social application interface when it is determined based on the user's attribute information that the second user account has group migration authority, the session group migration entrance being used to receive group migration operations for the first social application.
[0172] The specific definitions of the session group migration apparatus can be found in the definitions of the session group migration method above and will not be further elaborated here. Each module in the aforementioned session group migration apparatus may be implemented in whole or in part via software, hardware, or a combination thereof. Each of these modules may be embedded in or independent of a processor within a computer device in hardware form, or may be stored in a computer device memory in software form, allowing the processor to invoke and execute the corresponding operations of each module.
[0173] In some embodiments, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 11As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a method for migrating a session group is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad provided on the computer device housing, or an external keyboard, touchpad or mouse.
[0174] In some embodiments, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 12 As shown. The computer device includes a processor, a memory, and a network interface connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store relevant data involved in the session group migration method. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a session group migration method is implemented.
[0175] Those skilled in the art will understand that Figure 11 and 12 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.
[0176] In some embodiments, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.
[0177] In some embodiments, a computer-readable storage medium is provided, storing a computer program, which implements the steps in the above-mentioned method embodiments when executed by a processor.
[0178] In some embodiments, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps of each of the above method embodiments.
[0179] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).
[0180] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0181] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.
Claims
1. A method for migrating a conversation group, characterized in that: Executed by a first server corresponding to a first social application, the method includes: In response to a ticket acquisition request sent by a second server corresponding to a second social application, generating verification ticket information, and returning the verification ticket information to the second server; a second user account is logged in to the second social application; receiving a candidate migration session group acquisition request sent by a first social application logged in through a first user account; When the target ticket information carried in the candidate migration session group acquisition request is consistent with the verification ticket information, the candidate session group set is sent to the terminal corresponding to the first user account, so that the terminal uses the first social application to select the candidate session group selected from the candidate session group set as the target session group to be migrated; receiving a session group migration request for a target session group corresponding to a first user account; the target session group includes the first user account corresponding to the first social application; In response to the session group migration request, adding a second user account corresponding to the first user account in the second social application to the target session group, and updating the target session group to a session group associated with the first social application and the second social application; The group migration information corresponding to the target conversation group is sent to a second server corresponding to the second social application, so that the second server uses the target conversation group as the conversation group corresponding to the second social application based on the group migration information.
2. The method according to claim 1, characterized in that The sending of the candidate conversation group set to the terminal corresponding to the first user account, so that the terminal uses the candidate conversation group selected from the candidate conversation group set as the target conversation group to be migrated through the first social application, includes: In response to the candidate migration session group acquisition request, selecting, from the session group set corresponding to the first user account, session groups whose group member attributes of the first user account meet a member attribute condition, and forming the session groups that meet the member attribute condition into a candidate session group set; The candidate conversation group set is sent to a terminal corresponding to the first user account, so that the terminal displays the candidate conversation group set through a first social application, and in response to a selection operation on a candidate conversation group in the candidate conversation group set, the selected candidate conversation group is used as a target conversation group to be migrated.
3. The method according to claim 2, characterized in that In response to the candidate migration session group acquisition request, selecting, from the session group set corresponding to the first user account, session groups whose group member attributes of the first user account satisfy a member attribute condition, and forming the session groups satisfying the member attribute condition into a candidate session group set includes: In response to the candidate migration session group acquisition request, detecting a second user account corresponding to the second social application and associated with the first user account; When the second user account is detected, a conversation group whose group member attributes of the first user account meet the member attribute conditions is selected from the conversation group set corresponding to the first user account, and the conversation groups meeting the member attribute conditions are formed into a candidate conversation group set.
4. The method according to claim 3, characterized in that In response to the candidate migration session group acquisition request, detecting a second user account corresponding to the second social application and associated with the first user account includes: In response to the candidate migration session group acquisition request, sending an account acquisition request to the second server, the account acquisition request carrying the first user account, so that the second server acquires an associated second user account based on the first user account; When the second user account returned by the second server is received, it is confirmed that the second user account is detected.
5. The method according to claim 1, wherein The method further comprises: receiving a second group message for the target conversation group sent by the second server, where the second group message is sent by the second social application logged in by the second user account; Obtaining a set of session accounts corresponding to the first social application in the target session group; The second group message and the second user account are sent to the session end corresponding to each session account in the session account set, so that the session end displays the second group message in the session interface of the target session group in the first social application, and displays the account information corresponding to the second user account corresponding to the second group message.
6. A method for migrating a conversation group, characterized in that: Executed by a second server corresponding to the second social application, the method includes: receiving a group migration trigger request; the group migration trigger request is generated in response to a group migration trigger operation received by the second social application, the second social application being logged in with a second user account; In response to the group migration trigger request, sending a ticket acquisition request to the first server; receiving ticket information returned by the first server in response to the ticket acquisition request as target ticket information, and returning the target ticket information to the terminal corresponding to the second user account, so that the terminal jumps from the second social application to the first social application based on the target ticket information, and obtains candidate session clusters through the first social application for merged display; receiving group migration information corresponding to a target session group sent by a first server corresponding to a first social application; wherein the target session group includes a first user account corresponding to the first social application, and the first server, in response to a session group migration request for the target session group, adds a second user account corresponding to the first user account in a second social application to the target session group and triggers the sending of the group migration information; the target session group is selected from a set of displayed candidate session groups; Based on the group migration information, the target conversation group is used as the conversation group corresponding to the second social application; Sending a group establishment notification message corresponding to the target conversation group to the terminal corresponding to the second user account, so that the terminal displays the target conversation group based on the group establishment notification message through the second social application.
7. The method according to claim 6, characterized in that The group migration information includes a first group identifier corresponding to the target conversation group; The setting the target conversation group as the conversation group corresponding to the second social application based on the group migration information includes: generating a second group identifier corresponding to the target conversation group and a migration identifier corresponding to the second group identifier, and establishing a correspondence between the second group identifier and the first group identifier; The method further comprises: receiving a group message sending request corresponding to the second user account, where the group message sending request carries the second group message and the second group identifier; When it is detected that the second group identifier has a corresponding migration identifier, the first group identifier is obtained based on the corresponding relationship, and the second group message and the first group identifier are sent to the first server, so that the first server determines that the second group message is the second group message for the target conversation group based on the first group identifier.
8. A method for migrating a conversation group, characterized in that: Executed by a first social application, the method includes: Displaying a set of candidate conversation groups to be migrated corresponding to the first user account; In response to a selection operation on a candidate conversation group in the set of candidate conversation groups, the selected candidate conversation group is used as a target conversation group; the target conversation group includes a first user account corresponding to the first social application; A session group migration request for the target session group is triggered to request a first server corresponding to the first social application to execute the session group migration method according to any one of claims 1 to 5.
9. The method according to claim 8, characterized in that The candidate conversation group set to be migrated corresponding to the first user account is displayed, including: receiving an application redirect request for the first social application triggered by the second social application; When the application jump request is triggered in response to a group migration operation for the first social application, a set of candidate session groups to be migrated corresponding to the first user account is displayed.
10. A method for migrating a conversation group, characterized in that: Executed by a second social application, the method includes: Displaying the social application interface corresponding to the second user account logged in to the second social application; Receiving a group migration operation for a first social application through the social application interface, and sending a group migration trigger request to a second server corresponding to a second social application, so that the second server executes the session group migration method according to claim 6 or 7; In response to the group migration operation, an application jump request is triggered for the first social application to request to jump from the second social application to the first social application, so that the first social application obtains the set of candidate session groups to be migrated corresponding to the first user account logged in to the first social application, and displays the set of candidate session groups to be migrated.
11. The method according to claim 10, characterized in that The displaying of the social application interface corresponding to the second user account logged in to the second social application includes: receiving attribute information of a user corresponding to the second user account from a second server, where the second server is a server corresponding to the second social application; When it is determined based on the attribute information of the user that the second user account has group migration permission, a session group migration entrance is displayed on the displayed social application interface, and the session group migration entrance is used to receive a group migration operation for the first social application.
12. A conversation group migration device, characterized in that: The device comprises: a ticket generation module, configured to generate verification ticket information in response to a ticket acquisition request sent by a second server corresponding to a second social application, and return the verification ticket information to the second server; a second user account is logged in to the second social application; a candidate migration request receiving module, configured to receive a candidate migration session group acquisition request sent by a first social application logged in through a first user account; a candidate session group set sending module, configured to send the candidate session group set to the terminal corresponding to the first user account when the target ticket information carried in the candidate migration session group acquisition request is consistent with the verification ticket information, so that the terminal uses the first social application to select the candidate session group selected from the candidate session group set as the target session group to be migrated; A migration request receiving module, configured to receive a session group migration request for a target session group corresponding to a first user account; the target session group includes the first user account corresponding to the first social application; a conversation group updating module, configured to, in response to the conversation group migration request, add a second user account corresponding to the first user account in the second social application to the target conversation group, and update the target conversation group to a conversation group associated with the first social application and the second social application; The group migration information sending module is used to send the group migration information corresponding to the target conversation group to the second server corresponding to the second social application, so that the second server uses the target conversation group as the conversation group corresponding to the second social application based on the group migration information.
13. The session group migration device according to claim 12, wherein: The apparatus further includes a candidate session group set generation module configured to, in response to the candidate migration session group acquisition request, select, from the session group set corresponding to the first user account, session groups whose group member attributes of the first user account satisfy a member attribute condition, and form the session groups satisfying the member attribute condition into a candidate session group set; The candidate conversation group set sending module is further used to send the candidate conversation group set to the terminal corresponding to the first user account, so that the terminal displays the candidate conversation group set through the first social application, and in response to a selection operation on a candidate conversation group in the candidate conversation group set, uses the selected candidate conversation group as the target conversation group to be migrated.
14. The session group migration device according to claim 13, wherein: The candidate conversation group set generation module is also used to respond to the candidate migration conversation group acquisition request and detect the second user account associated with the first user account corresponding to the second social application; when the second user account is detected, select the conversation group whose group member attributes of the first user account meet the member attribute conditions from the conversation group set corresponding to the first user account, and form the conversation groups that meet the member attribute conditions into a candidate conversation group set.
15. The session group migration device according to claim 14, wherein: The candidate session group set generation module is further configured to send an account acquisition request to the second server in response to the candidate migration session group acquisition request, wherein the account acquisition request carries the first user account, so that the second server acquires an associated second user account based on the first user account; When the second user account returned by the second server is received, it is confirmed that the second user account is detected.
16. The session group migration device according to claim 12, wherein: The device further comprises: A second group message receiving module is configured to receive a second group message for the target conversation group sent by the second server, where the second group message is sent by the second social application logged in by the second user account; A session account set acquisition module, configured to acquire a session account set corresponding to the first social application in the target session group; A second group message sending module is used to send the second group message and the second user account to the session end corresponding to each session account in the session account set, so that the session end displays the second group message in the session interface of the target session group in the first social application, and displays the account information corresponding to the second user account corresponding to the second group message.
17. A conversation group migration device, characterized in that: The device comprises: a group migration trigger request receiving module, configured to receive a group migration trigger request; the group migration trigger request being generated in response to a group migration trigger operation received by a second social application, the second social application being logged in by a second user account; a ticket acquisition request sending module, configured to send a ticket acquisition request to the first server in response to the group migration trigger request; a ticket information returning module, configured to receive the ticket information returned by the first server in response to the ticket acquisition request as target ticket information, and return the target ticket information to the terminal corresponding to the second user account, so that the terminal jumps from the second social application to the first social application based on the target ticket information, and obtains candidate session clusters through the first social application for merged display; a group migration information receiving module, configured to receive group migration information corresponding to a target session group, sent by a first server corresponding to a first social application; wherein the target session group includes a first user account corresponding to the first social application, and the first server, in response to a session group migration request for the target session group, adds a second user account corresponding to the first user account in a second social application to the target session group and triggers the sending of the group migration information; the target session group is selected from a set of displayed candidate session groups; a conversation group migration module, configured to use the target conversation group as the conversation group corresponding to the second social application based on the group migration information; A group establishment notification message sending module is used to send the group establishment notification message corresponding to the target conversation group to the terminal corresponding to the second user account, so that the terminal displays the target conversation group based on the group establishment notification message through the second social application.
18. The session group migration device according to claim 17, wherein: The group migration information includes a first group identifier corresponding to the target conversation group; The conversation group migration module includes: a migration identifier generating unit, configured to generate a second group identifier corresponding to the target conversation group and a migration identifier corresponding to the second group identifier, and establish a correspondence between the second group identifier and the first group identifier; The device further comprises: a group message sending request receiving module, configured to receive a group message sending request corresponding to the second user account, the group message sending request carrying the second group message and the second group identifier; The second group message sending module is used to obtain the first group identifier based on the corresponding relationship when it is detected that the second group identifier has the corresponding migration identifier, and send the second group message and the first group identifier to the first server, so that the first server determines that the second group message is the second group message for the target conversation group based on the first group identifier.
19. A conversation group migration device, characterized in that: The device comprises: a candidate conversation group set display module, configured to display a candidate conversation group set to be migrated corresponding to the first user account; a target conversation group obtaining module, configured to, in response to a selection operation on a candidate conversation group in the candidate conversation group set, select the selected candidate conversation group as a target conversation group; the target conversation group includes a first user account corresponding to the first social application; A session group migration request triggering module is used to trigger a session group migration request for the target session group, so as to request the first server corresponding to the first social application to execute the session group migration method according to any one of claims 1 to 5.
20. The session group migration device according to claim 19, wherein: The candidate conversation group set display module includes: an application jump request receiving unit, configured to receive an application jump request for the first social application triggered by the second social application; The candidate conversation group set display unit is configured to display a candidate conversation group set to be migrated corresponding to the first user account when the application jump request is triggered in response to a group migration operation for the first social application.
21. A conversation group migration device, characterized in that: The device comprises: A social application interface display module, configured to display a social application interface corresponding to the second user account logged in to the second social application; a group migration operation receiving module, configured to receive a group migration operation for a first social application through the social application interface, and send a group migration trigger request to a second server corresponding to a second social application, so that the second server executes the session group migration method according to claim 6 or 7; and an application jump request response module, configured to trigger an application jump request for the first social application in response to the group migration operation, requesting a jump from the second social application to the first social application, so that the first social application obtains a set of candidate session groups to be migrated corresponding to a first user account logged in to the first social application, and displays the set of candidate session groups to be migrated.
22. The session group migration device according to claim 21, wherein: The social application interface display module includes: a user attribute information receiving unit, configured to receive attribute information of the user corresponding to the second user account sent by a second server, where the second server is a server corresponding to the second social application; A session group migration entry display unit is used to display a session group migration entry on the displayed social application interface when it is determined based on the attribute information of the user that the second user account has group migration permission, and the session group migration entry is used to receive a group migration operation for the first social application.
23. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 11 are implemented.
24. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.
25. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.
Citation Information
Patent Citations
Session message transmission method and device, electronic equipment and storage medium
CN112787908A