Group User Migration Method, Device, Equipment and Storage Medium

Abstract

The present application discloses a method, apparatus, device, and storage medium for migrating group users, belonging to the field of computer technology. Through the technical solution provided by the embodiments of the present application, when an application needs to be replaced, only a target graphic code needs to be created on the first application and the target graphic code is shared to the target group in the second application. Users in the target group can quickly join the group in the first application through the target graphic code, and the efficiency of migrating group users is relatively high. In addition, since there is a binding relationship between the target group and the target graphic code, it means that only users in the target group can join the first group based on the target graphic code, and users in other groups in the second application cannot join the first group based on the target graphic code, realizing one code for one group, and the security of the target graphic code is relatively high.

Description

Technical Field

[0001] This application relates to the field of computer technology, and particularly to a method, device, equipment, and storage medium for migrating group users. Background Art

[0002] With the development of Internet technology, the development of enterprises increasingly relies on the progress of Internet technology. Under this background, the way business personnel of enterprises communicate with customers is also changing.

[0003] In the related art, business personnel use instant messaging software to add multiple customers to a group to facilitate customer maintenance and management. However, during the work process, an enterprise may replace the instant messaging software to maintain customers. In this case, business personnel need to notify each customer in the original instant messaging software to join the group in the replaced instant messaging software one by one, resulting in low efficiency of group user migration. Summary of the Invention

[0004] Embodiments of this application provide a method, device, equipment, and storage medium for migrating group users, which can improve the efficiency of group user migration. The technical solution is as follows:

[0005] On the one hand, a method for migrating group users is provided, which is applied to a first application server. The first application server is used to provide background services for a first application. The method includes:

[0006] In response to a group user migration request of a target user, create a target QR code and a first group corresponding to the first application. The group user migration request is used to request migrating users in any group in a second application to the group in the first application;

[0007] In response to the target user sharing the target QR code to a target group in the second application, bind the target QR code to the target group;

[0008] In response to a join request of any user in the second application to the first group, determine the group to which the user belongs in the second application;

[0009] In response to the user belonging to the target group bound to the target QR code, add the user to the first group of the first application.

[0010] On the one hand, a method for migrating group users is provided. The method includes:

[0011] Receive a group user migration instruction, which is used to indicate migrating users in any group in a second application to a group in a first application;

[0012] In response to the group user migration instruction, display a target graphic code, where the target graphic code corresponds to a first group newly created in the first application;

[0013] In response to a sharing instruction for the target graphic code, share the target graphic code to a target group in the second application, so that the users of the target group can join the first group of the first application based on the target graphic code, and there is a binding relationship between the target group and the target graphic code.

[0014] In a possible implementation manner, the step of sharing the target graphic code to a target group in the second application in response to the sharing instruction for the target graphic code includes:

[0015] In response to the sharing instruction for the target graphic code, display a group sharing interface, where the group sharing interface includes at least one group in the second application;

[0016] In response to detecting a trigger operation on the target group in the group sharing interface, share the target graphic code to the target group in the second application.

[0017] In a possible implementation manner, a first account is logged in on the first application. After receiving the group user migration instruction, the method further includes any one of the following:

[0018] When the first account is not bound to any target account, display an account unbound prompt;

[0019] When the first account is bound to any target account and the any target account is in a blocked state, display an account blocked prompt;

[0020] Wherein, the target account is an account registered in the second application.

[0021] In a possible implementation manner, a first account is logged in on the first application and a second account is logged in on the second application. After responding to the sharing instruction for the target graphic code, the method further includes:

[0022] When the second account is different from a third account, display an account switching prompt, where the account switching prompt is used to prompt to log in to the second application using the third account, and the third account is an account registered in the second application and bound to the first account.

[0023] In a possible implementation manner, a first account is logged in on the first application. Before receiving the group user migration instruction, the method further includes:

[0024] When any graphic code has been created for the first account, a group display interface is shown, and the any graphic code and the number of groups corresponding to the any graphic code are shown on the group display interface.

[0025] On the one hand, a group user migration device is provided, which is applied to a first application server. The first application server is used to provide background services for a first application. The device includes:

[0026] A creation module, configured to create a target graphic code and a first group corresponding thereto in the first application in response to a group user migration request of a target user. The group user migration request is used to request migrating users in any group in a second application to a group in the first application;

[0027] A binding module, configured to bind the target graphic code to the target group in response to the target user sharing the target graphic code to the target group in the second application;

[0028] A determination module, configured to determine the group to which the user belongs in the second application in response to a join request of any user in the second application for the first group;

[0029] An addition module, configured to add the user to the first group of the first application in response to the user belonging to the target group bound to the target graphic code.

[0030] In a possible implementation manner, the addition module is further configured to add the user to the first group of the first application in response to the group identifier of the group to which the user belongs in the second application being the same as the group identifier of the target group.

[0031] In a possible implementation manner, the addition module is further configured to reject the user's join request for the first group in response to the user not belonging to the target group bound to the target graphic code.

[0032] In a possible implementation manner, the addition module is further configured to reject the user's join request for the first group in response to the group identifier of the group to which the user belongs in the second application being different from the group identifier of the target group.

[0033] In a possible implementation manner, the creation module is further configured to create a second group in the first application in response to the number of users in the first group meeting a target number condition. The second group corresponds to the target graphic code.

[0034] In a possible implementation, the adding module is further configured to, in response to a joining request from other users in the target group for the first group, add the other users to a second group of the first application.

[0035] On the one hand, a group user migration device is provided, and the device includes:

[0036] An instruction receiving module, configured to receive a group user migration instruction, where the group user migration instruction is used to indicate migrating users in any group in a second application to a group in a first application;

[0037] A graphic code display module, configured to, in response to the group user migration instruction, display a target graphic code, where the target graphic code corresponds to a first group newly created in the first application;

[0038] A second sharing module, configured to, in response to a sharing instruction for the target graphic code, share the target graphic code to a target group in the second application, so that users in the target group can join the first group of the first application based on the target graphic code, and there is a binding relationship between the target group and the target graphic code.

[0039] In a possible implementation, the graphic code display module is configured to, in response to the group user migration instruction, display a graphic code creation interface;

[0040] In response to a creation instruction triggered based on the graphic code creation interface, display a graphic code display interface, where the target graphic code is displayed on the graphic code display interface.

[0041] In a possible implementation, the number of users in the first group is further displayed on the graphic code display interface, and the graphic code display module is further configured to, when any user in the target group joins the first group, update the number of users in the first group on the graphic code display interface.

[0042] In a possible implementation, the group identifier of the first group is further displayed on the graphic code display interface, and the graphic code display module is further configured to, in response to detecting a trigger operation on the group identifier of the first group, display a group session interface of the first group.

[0043] In a possible implementation, the graphic code display module is further configured to, when the number of users in the first group meets a target number condition, display the group identifier of a second group on the graphic code display interface, where the second group is a group newly created in the first application and corresponds to the target graphic code.

[0044] In a possible implementation, the second sharing module is configured to, in response to a sharing instruction for the target graphic code, display a group sharing interface, where the group sharing interface includes at least one group in the second application; and in response to detecting a triggering operation on the target group in the group sharing interface, share the target graphic code to the target group in the second application.

[0045] In a possible implementation, a first account is logged in to the first application, and the device further includes any one of the following modules:

[0046] The first prompting module is configured to display an account unbound prompt when the first account is not bound to any target account.

[0047] The second prompting module is configured to display an account blocked prompt when the first account is bound to any target account and the any target account is in a blocked state.

[0048] Wherein, the target account is an account registered in the second application.

[0049] In a possible implementation, a first account is logged in to the first application, and a second account is logged in to the second application. The device further includes:

[0050] The third prompting module is configured to display an account switching prompt when the second account is different from a third account. The account switching prompt is used to prompt to log in to the second application using the third account, where the third account is an account registered in the second application and bound to the first account.

[0051] In a possible implementation, a first account is logged in to the first application, and the device further includes:

[0052] The group display interface display module is configured to display a group display interface when the first account has created any graphic code. The group display interface displays the any graphic code and the number of groups corresponding to the any graphic code.

[0053] On the one hand, a computer device is provided. The computer device includes one or more processors and one or more memories. At least one computer program is stored in the one or more memories. The computer program is loaded and executed by the one or more processors to implement the group user migration method.

[0054] On the one hand, a computer-readable storage medium is provided. At least one computer program is stored in the computer-readable storage medium. The computer program is loaded and executed by a processor to implement the group user migration method.

[0055] On the one hand, a computer program product or a computer program is provided. The computer program product or the computer program includes program code stored in a computer-readable storage medium. A processor of a computer device reads the program code from the computer-readable storage medium, and the processor executes the program code, so that the computer device executes the above-mentioned group user migration method.

[0056] Through the technical solution provided by the embodiments of the present application, when an application program needs to be replaced, only a target graphic code needs to be created on the first application and shared to a target group in the second application. Users in the target group can quickly join the group in the first application through the target graphic code, and the efficiency of group user migration is relatively high. In addition, since there is a binding relationship between the target group and the target graphic code, it means that only users in the target group can join the first group based on the target graphic code, and users in other groups in the second application cannot join the first group based on the target graphic code, realizing one code for one group, and the security of the target graphic code is relatively high. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] To more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for description in the embodiments. Obviously, the following-described drawings are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0058] Figure 1 is a schematic diagram of the implementation environment of a group user migration method provided by an embodiment of the present application;

[0059] Figure 2 is a flowchart of a group user migration method provided by an embodiment of the present application;

[0060] Figure 3 is a flowchart of a group user migration method provided by an embodiment of the present application;

[0061] Figure 4 is a schematic diagram of an interface provided by an embodiment of the present application;

[0062] Figure 5 is a schematic diagram of an interface provided by an embodiment of the present application;

[0063] Figure 6 is a schematic diagram of an interface provided by an embodiment of the present application;

[0064] Figure 7 is a schematic diagram of an interface provided by an embodiment of the present application;

[0065] Figure 8It is a schematic diagram of an interface provided by an embodiment of the present application;

[0066] Figure 9 It is a schematic diagram of an interface provided by an embodiment of the present application;

[0067] Figure 10 It is a schematic diagram of an interface provided by an embodiment of the present application;

[0068] Figure 11 It is a schematic diagram of an interface provided by an embodiment of the present application;

[0069] Figure 12 It is a schematic diagram of an interface provided by an embodiment of the present application;

[0070] Figure 13 It is a schematic diagram of an interface provided by an embodiment of the present application;

[0071] Figure 14 It is a schematic diagram of an interface provided by an embodiment of the present application;

[0072] Figure 15 It is a flowchart of a method for migrating group users provided by an embodiment of the present application;

[0073] Figure 16 It is a logical block diagram of a method for migrating group users provided by an embodiment of the present application;

[0074] Figure 17 It is a schematic structural diagram of a device for migrating group users provided by an embodiment of the present application;

[0075] Figure 18 It is a schematic structural diagram of a device for migrating group users provided by an embodiment of the present application;

[0076] Figure 19 It is a schematic structural diagram of a terminal provided by an embodiment of the present application;

[0077] Figure 20 It is a schematic structural diagram of a first application server provided by an embodiment of the present application. Detailed implementation manners

[0078] To make the objectives, technical solutions, and advantages of the present application clearer, the following will further describe the embodiments of the present application in detail with reference to the accompanying drawings.

[0079] In the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and effects. It should be understood that there is no logical or temporal dependency between "first", "second", and "nth", nor are the quantity and execution order limited.

[0080] In this application, the term "at least one" means one or more, and "a plurality" means two or more. For example, a plurality of reference face images means two or more reference face images.

[0081] Figure 1 FIG. 4 is a schematic diagram of an implementation environment of a group user migration method provided by an embodiment of this application. Refer to Figure 1 In this implementation environment, a terminal 110 and a first application server 140 may be included.

[0082] The terminal 110 is connected to the first application server 140 through a wireless network or a wired network. Optionally, the terminal 110 is a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart watch, etc., but is not limited thereto. The terminal 110 installs and runs an application program that supports group user migration.

[0083] Optionally, the first application server 140 is an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, a content delivery network (CDN), and big data and artificial intelligence platforms.

[0084] Optionally, the terminal 110 generally refers to one of multiple terminals, and only the terminal 110 is used as an example in the embodiments of this application.

[0085] Those skilled in the art can know that the number of the above terminals may be more or less. For example, the above terminal is only one, or the above terminals are dozens or hundreds, or a larger number. In this case, other terminals are further included in the above implementation environment. The embodiments of this application do not limit the number and device types of the terminals.

[0086] After introducing the implementation environment of the embodiments of this application, the application scenarios of the embodiments of this application are described below.

[0087] The technical solution provided by the embodiments of this application can be applied to migrating users in a group in a second application to a group in a first application. The application scenarios of the embodiments of this application are further described below through two examples.

[0088] Example 1: There are Application A and Application B, both of which have the function of instant messaging. In the initial stage of the enterprise's development, Application A was used to communicate with customers. As the enterprise and the Internet have developed, Application A may no longer meet the enterprise's needs for communicating with customers. For example, the number of friends that can be added in Application A is relatively small. In this case, the enterprise may want to use Application B, which allows adding more friends, to communicate with customers. For this enterprise, directly abandoning Application A and adopting Application B will result in the loss of users, while introducing the original customers from Application A to Application B one by one will consume a lot of time. In addition, during the process of introducing the customers in Application A to Application B, the enterprise also needs to use both Application A and Application B to communicate with customers at the same time, and using Application A and Application B simultaneously is likely to cause message omission, resulting in a decline in the communication efficiency with customers. In this case, the enterprise can adopt the technical solution provided by the embodiment of the present application to quickly migrate the customers in Application A to Application B, thereby improving the efficiency of customer migration.

[0089] Example 2: An application development enterprise develops Application C and Application D simultaneously. When the application development enterprise wants to abandon the operation of one application and focus on the operation of another application, the application development enterprise can adopt the technical solution provided by the present application to migrate the users in the application to be abandoned to another application, so as to maximize the retention of the number of users. For example, if the application development enterprise wants to abandon the operation of Application C and focus on maintaining and operating Application D, then the application development enterprise can open an interface adopting the technical solution provided by the embodiment of the present application in Application C and Application D for users to use, so as to realize the migration of the users in Application C to Application D.

[0090] After introducing the application scenarios of the embodiments of the present application, the technical solutions provided by the embodiments of the present application will be described below.

[0091] In the embodiments of the present application, there are technical solutions on the terminal side and the server side. The technical solutions on the terminal side and the server side correspond to each other. Since the technical solutions on the terminal side are more visual and easier to understand, in the following description process, the technical solutions on the terminal side will be described first in combination with the accompanying drawings, and then the technical solutions on the server side will be described.

[0092] Figure 2 is a flowchart of a group user migration method provided by an embodiment of the present application. Refer to Figure 2 and the method includes:

[0093] 201. The terminal receives a group user migration instruction, and the group user migration instruction is used to indicate migrating the users in any group in the second application to the group in the first application.

[0094] Among them, the first application and the second application are applications capable of user data intercommunication. In some embodiments, the account in the second application can be directly used to log in to the first application.

[0095] Optionally, the group user migration instruction is triggered by the terminal in response to an operation of the user on the first application. The first application and the second application are both installed on the terminal, and both the first application and the second application are applications capable of creating groups.

[0096] 202. In response to the group user migration instruction, the terminal displays a target graphic code, and the target graphic code corresponds to a first group newly created in the first application.

[0097] Optionally, the target graphic code is a QR code or a barcode. The embodiments of the present application do not make any limitations in this regard. The first group is a group created simultaneously when the target graphic code is created. Users of any group in the second application can join the first group of the first application by scanning the target graphic code.

[0098] 203. In response to a sharing instruction for the target graphic code, the terminal shares the target graphic code to a target group in the second application, so that users of the target group can join the first group of the first application based on the target graphic code. The target group has a binding relationship with the target graphic code.

[0099] Among them, the target group is determined by the terminal based on the operation of the user, that is, it is determined by the user which group in the second application the target graphic code is shared to. In some embodiments, the establishment of the binding relationship between the target group and the graphic code is executed by the server.

[0100] Through the technical solution provided by the embodiments of the present application, when an application needs to be replaced, only a target graphic code needs to be created on the first application and the target graphic code is shared to the target group in the second application. Users in the target group can quickly join the group in the first application through the target graphic code, and the efficiency of group user migration is relatively high. In addition, since the target group has a binding relationship with the target graphic code, it means that only users in the target group can join the first group based on the target graphic code, and users in other groups in the second application cannot join the first group based on the target graphic code, realizing one code for one group, and the security of the target graphic code is relatively high.

[0101] Figure 3 It is a flowchart of a group user migration method provided by the embodiments of the present application. Refer to Figure 3 , the method includes:

[0102] 301. The terminal receives a group user migration instruction, and the group user migration instruction is used to instruct to migrate users in any group in the second application to a group in the first application.

[0103] In a possible implementation, a first group user migration interface of a first application is displayed on a terminal, and a group user migration control is displayed on the first group user migration interface. In response to detecting a trigger operation on the group user migration control, the terminal triggers a group user migration instruction.

[0104] In this implementation, when a user wants to migrate the users of any group in a second application to the first application, the group user migration instruction can be quickly triggered through the first group user migration interface provided by the first application, so as to complete the subsequent group user migration.

[0105] For example, refer to Figure 4 , a group chat addition interface 401 of the first application is displayed on the terminal, and a group chat addition control 402 is displayed on the group chat addition interface 401. When a user wants to migrate the users of any group in the second application "AA" to the first application "BB", clicking the group chat addition control 402 can trigger a display instruction for the first group user migration interface. In response to the display instruction for the first group user migration interface, refer to Figure 5 , the terminal switches the group chat addition interface 401 to the first group user migration interface 501. A function introduction 502 of this interface and a group user migration control 503 are displayed on the first group user migration interface 501. The user can quickly trigger the group user migration instruction by clicking the group user migration control 503.

[0106] In a possible implementation, the group migration instruction can also be triggered by an operation performed by the user on the second application. That is, a second group user migration interface of the second application is displayed on the terminal, and a group user migration control is displayed on the second group migration interface. In response to detecting a trigger operation on the group user migration control, the terminal triggers a group user migration instruction.

[0107] In this implementation, when a user wants to migrate the users of any group in the second application to the first application, the group user migration instruction can also be quickly triggered directly through the second group user migration interface provided by the second application, so as to complete the subsequent group user migration.

[0108] For example, refer to Figure 6 , a group chat addition interface 601 of the second application is displayed on the terminal, and a group chat addition control 602 is displayed on the group chat addition interface. When a user wants to migrate the users of any group in the second application "AA" to the second application "BB", clicking the group chat addition control 602 can trigger a display instruction for the second group user migration interface. In response to the display instruction for the second group user migration interface, refer to Figure 7, the terminal switches the group chat addition interface 601 to the second group user migration interface 701. On the second group user migration interface 701, there is a function introduction 702 of this interface and a group user migration control 703. When the user clicks on the group user migration control 703, the group user migration instruction can be quickly triggered.

[0109] Optionally, if the user triggers the group user migration instruction through the first terminal, after the terminal receives the group user migration instruction, in addition to being able to execute the following step 302, it can also execute any one of the following methods first.

[0110] In a possible implementation manner, the first application logs in with the first account. When the first account is not bound to any target account, the terminal displays an account unbound prompt. In some embodiments, the account unbound prompt is "You have not bound the XX account yet. You can use it after binding." When the first account is bound to any target account and any target account is in a blocked state, the terminal displays an account blocked prompt. In some embodiments, the account blocked prompt is "The bound XX account is abnormal. Please unblock it in XX before proceeding with the operation." Here, the target account is an account registered in the second application. That is to say, before executing step 302, the terminal can verify the first account logged in on the first application. When the first account is not bound to any target account, it means that no connection can be established between the first account and the second application, so the terminal can display an account unbound prompt. The user can learn from the account unbound prompt that the first account is not bound to any target account, and the user can subsequently execute the binding process of the first account and the target account. Or, when the first account is bound to any target account, but the target account bound to the first account is in a blocked state, the terminal can display an account blocked prompt. The user can learn from the account blocked prompt that the target account bound to the first account is blocked, and subsequently can unbind the first account from the target account or unblock the target account.

[0111] For example, after the terminal receives the group user migration instruction, it can send a binding relationship verification request to the first application server. The binding relationship verification request is used to obtain the binding relationship between the first account and any target account. Among them, the binding relationship verification request carries the first account. In some embodiments, see Figure 4, the binding relationship verification request is triggered by the terminal detecting a click operation on the group chat addition control 402. After receiving the binding relationship verification request, the first application server can obtain the first account from the binding relationship verification request and query the binding status of the first account and the target account in the binding relationship database. When the first application server determines that there is no binding relationship between the first account and any target account, the first application server can send a binding relationship non-existence message to the terminal. In response to receiving the binding relationship non-existence message, the terminal displays an account unbound prompt; when the first application server determines that there is a binding relationship between the first account and any target account, but the account status of the target account is a blocked status, the first application server can send an account blocked message to the terminal. In response to receiving the account blocked message, the terminal displays an account blocked prompt.

[0112] 302. In response to the group user migration instruction, the terminal displays a QR code creation interface.

[0113] In a possible implementation manner, if the user triggers the group user migration instruction through the first group user migration interface displayed on the terminal, then in response to the group user migration instruction, the terminal switches the first group user migration interface to the QR code creation interface of the first application. In some embodiments, the user can set an identifier for the target QR code on the QR code creation interface of the first application, and the terminal can obtain the characters input by the user on the QR code creation interface of the first application as the identifier of the target QR code.

[0114] For example, refer to Figure 5 and Figure 8 , in response to the group user migration instruction, the terminal can Figure 5 switch the first group user migration interface 501 in Figure 8 to the QR code creation interface 801 of the first application in

[0115] which has a QR code identifier input box 802 displayed on it. In some embodiments, the identifier of the target QR code is also the name of the target QR code, and the user can input the name of the target QR code in the QR code identifier input box 802. The terminal can obtain the characters in the QR code identifier input box 802 as the name of the target QR code.

[0116] For example, refer toFigure 7 and Figure 9 in response to a group user migration instruction, the terminal is capable of switching the second group user migration interface 701 in Figure 7 to the graphic code creation interface 901 of the second application in Figure 9 and a graphic code identification input box 902 is displayed on the graphic code creation interface 901. In some embodiments, the identification of the target graphic code is also the name of the target graphic code, and the user can input the name of the target graphic code in the graphic code identification input box 902. The terminal can obtain the characters in the graphic code identification input box as the name of the target graphic code.

[0117] In a possible implementation manner, if the user triggers a group user migration instruction through the second group user migration interface displayed on the terminal, then in response to the group user migration instruction, the terminal switches the second group user migration interface to the graphic code creation interface of the first application. In some embodiments, the user can input the identification set for the desired target graphic code on the graphic code creation interface of the first application, and the terminal can obtain the characters input by the user on the graphic code creation interface of the first application as the identification of the target graphic code.

[0118] For example, referring to Figure 7 and Figure 8 in response to a group user migration instruction, the terminal is capable of switching the second application to the first application, that is, switching the second group user migration interface 701 in Figure 7 to the graphic code creation interface 801 of the first application in Figure 8 and a graphic code identification input box 802 is displayed on the graphic code creation interface 801. In some embodiments, the identification of the target graphic code is also the name of the target graphic code, and the user can input the name of the target graphic code in the graphic code identification input box 802. The terminal can obtain the characters in the graphic code identification input box as the name of the target graphic code.

[0119] 303. In response to a creation instruction triggered based on the graphic code creation interface, the terminal displays a graphic code display interface, and a target graphic code is displayed on the graphic code display interface, and the target graphic code corresponds to a first group newly created in the first application.

[0120] Optionally, the group identifier of the first group is associated with the identifier of the target graphic code. Here, the association between the group identifier of the first group and the identifier of the target graphic code means that they have the same part. Taking the identifier as the name as an example, if the name of the target graphic code is "Fruit Group", then the group identifier of the first group is "Fruit Group 1". In this case, the user only needs to set a name for the target graphic code, and the name of the first group can be automatically generated, with relatively high human-computer interaction efficiency. In some embodiments, the user can also set a validity period for the target graphic code, such as setting it to be permanently valid or valid for 7 days. The embodiments of the present application do not make any limitations on this.

[0121] In a possible implementation manner, a graphic code creation interface of a first application is displayed on the terminal, and a graphic code creation control is displayed on the graphic code creation interface of the first application. In response to detecting a click operation on the graphic code creation control, the terminal triggers a creation instruction. In response to the creation instruction triggered based on the graphic code creation interface, the terminal switches the graphic code creation interface of the first application to a graphic code display interface of the first application. The graphic code display interface of the first application displays the created target graphic code, and the target graphic code corresponds to a newly created first group in the first application. Users can join the first group by scanning the target graphic code.

[0122] For example, referring to Figure 8 and Figure 10 , a graphic code creation interface 801 of a first application is displayed on the terminal. A graphic code identifier input box 802 and a graphic code creation control 803 are displayed on the graphic code creation interface 801. After the user enters the identifier of the target graphic code in the graphic code identifier input box 802, clicking the graphic code creation control can complete the creation of the target graphic code. For the terminal, in response to detecting a click operation on the graphic code creation control 803, the terminal triggers a creation instruction. In response to the creation instruction triggered based on the graphic code creation interface 801, that is, the creation instruction triggered by the user clicking the graphic code creation control 803, the terminal switches the graphic code creation interface 801 to a graphic code display interface 1001 of the first application. The target graphic code 1002 is displayed in the graphic code display interface 1001. After the user shares the target graphic code 1002 with other users, other users can join the first group corresponding to the target graphic code 1002 by recognizing the graphic code 1002. In some embodiments, group information 1003 corresponding to the target graphic code is also displayed on the graphic code display interface 1001, and the group identifier of the first group and the number of users in the first group are displayed in the group information 1003.

[0123] In a possible implementation, if a graphical code creation interface of a second application is displayed on the terminal, and a graphical code creation control is displayed on the graphical code creation interface of the second application. In response to detecting a triggering operation on the graphical code creation control, the terminal triggers a creation instruction. In response to the creation instruction triggered based on the graphical code creation interface, the terminal switches the graphical code creation interface of the second application to a graphical code display interface of the second application. The graphical code display interface of the second application displays a created target graphical code, and the target graphical code corresponds to a newly created first group in the first application. Users can join the first group by scanning the target graphical code.

[0124] For example, referring to Figure 9 and Figure 11 a graphical code creation interface 901 of a second application is displayed on the terminal. A graphical code identification input box 902 and a graphical code creation control 903 are displayed on the graphical code creation interface 901. After the user enters the identification of the target graphical code in the graphical code identification input box 902, clicking the graphical code creation control can complete the creation of the target graphical code. For the terminal, in response to detecting a click operation on the graphical code creation control 903, the terminal triggers a creation instruction. In response to the creation instruction triggered based on the graphical code creation interface 901, that is, the creation instruction triggered by the user clicking the graphical code creation control 903, the terminal switches the graphical code creation interface 901 to a graphical code display interface 1101 of the second application. The graphical code display interface 1101 displays a target graphical code 1102. After the user shares the target graphical code 1102 with other users, other users can join the first group corresponding to the target graphical code 1102 by identifying the graphical code 1102. In some embodiments, group information 1103 corresponding to the target graphical code is also displayed on the graphical code display interface 1101, and the group information 1103 displays the group identification of the first group and the number of users in the first group.

[0125] In a possible implementation, if a graphical code creation interface of a second application is displayed on the terminal, and a graphical code creation control is displayed on the graphical code creation interface of the second application. In response to detecting a triggering operation on the graphical code creation control, the terminal triggers a creation instruction. In response to the creation instruction triggered based on the graphical code creation interface, the terminal switches the graphical code creation interface of the second application to a graphical code display interface of the first application. The graphical code display interface of the first application displays a created target graphical code, and the target graphical code corresponds to a newly created first group in the first application. Users can join the first group by scanning the target graphical code.

[0126] For example, referring to Figure 9 and Figure 10, a graphical code creation interface 901 of a second application is displayed on the terminal. A graphical code identifier input box 902 and a graphical code creation control 903 are displayed on the graphical code creation interface 901. After the user enters the identifier of the target graphical code in the graphical code identifier input box 902, clicking the graphical code creation control can complete the creation of the target graphical code. For the terminal, in response to detecting a trigger click operation on the graphical code creation control 903, the terminal triggers a creation instruction. In response to the creation instruction triggered based on the graphical code creation interface 901, the terminal switches the graphical code creation interface 901 to a graphical code display interface 1001 of a first application. The target graphical code 1002 is displayed in the graphical code display interface 1001. After the user shares the target graphical code 1002 with other users, other users can join the first group corresponding to the target graphical code 1002 by recognizing the graphical code 1002. In some embodiments, group information 1003 corresponding to the target graphical code is also displayed on the graphical code display interface 1001, and the group identifier of the first group and the number of users in the first group are displayed in the group information 1003.

[0127] 304. In response to a sharing instruction for a target graphical code, the terminal displays a group sharing interface, and the group sharing interface includes at least one group in the second application.

[0128] In a possible implementation manner, if a graphical code display interface of a first application is displayed on the terminal, and a graphical code sharing control is displayed on the graphical code display interface of the first application. In response to detecting a click operation on the graphical code sharing control, the terminal triggers a sharing instruction for the target graphical code. In response to the sharing instruction for the target graphical code, the terminal switches the graphical code display interface of the first application to a group sharing interface of the second application, and the user can select a group to which the target graphical code is to be shared in the group sharing interface of the second application.

[0129] For example, referring to Figure 10 and Figure 12 , a graphical code display interface 1001 of a first application is displayed on the terminal, and a graphical code sharing control 1004 is displayed in the graphical code display interface 1001. The user can click the graphical code sharing control 1004 to control the terminal to switch the graphical code display interface of the first application to a group sharing interface 1201 of the second application. For the terminal, in response to detecting a click operation on the graphical code sharing control 1004, the terminal switches the graphical code display interface 1001 of the first application to the group sharing interface 1201 of the second application. In some embodiments, the group identifier and group avatar 1202 of at least one group in the second application are displayed in the group sharing interface 1201 of the second application, and the user can select a group to which the target graphical code is to be shared through the group sharing interface 1201.

[0130] In a possible implementation, if a graphical code display interface of a second application is displayed on the terminal, and a graphical code sharing control is displayed on the graphical code display interface of the second application. In response to detecting a click operation on the graphical code sharing control, the terminal triggers a sharing instruction for the target graphical code. In response to the sharing instruction for the target graphical code, the terminal switches the graphical code display interface of the second application to the group sharing interface of the second application, and the user can select the group to which the target graphical code is to be shared in the group sharing interface of the second application.

[0131] For example, referring to Figure 11 and Figure 12 , a graphical code display interface 1101 of a second application is displayed on the terminal, and a graphical code sharing control 1104 is displayed in the graphical code display interface 1101. When the user clicks the graphical code sharing control 1104, the user can control the terminal to switch the graphical code display interface of the second application to the group sharing interface 1201 of the second application. For the terminal, in response to detecting a click operation on the graphical code sharing control 1104, the terminal switches the graphical code display interface 1101 of the first application to the group sharing interface 1201 of the second application. In some embodiments, group identifiers and group avatars 1202 of at least one group in the second application are displayed in the group sharing interface 1201 of the second application, and the user can select the group to which the target graphical code is to be shared through the group sharing interface 1201.

[0132] It should be noted that in the above description process, it is assumed that the first application and the second application are both installed on the terminal. If the second application is installed on the terminal, the terminal can display the group sharing interface. If the second application is not installed on the terminal, the terminal can display a prompt indicating that the second application is not installed. In some embodiments, the prompt indicating that the second application is not installed is "Sharing failed. Please install the second application and try again."

[0133] Optionally, in response to the sharing instruction for the target graphical code, in addition to directly displaying the group sharing interface, the terminal can also verify the accounts logged in to the first application and the second application before displaying the group sharing interface. The method for account verification is as follows.

[0134] In a possible implementation, a first account is logged in to the first application, and a second account is logged in to the second application. When the second account is different from the third account, the terminal displays an account switching prompt, and the account switching prompt is used to prompt to log in to the second application using the third account, where the third account is an account registered in the second application and bound to the first account. In some embodiments, the account switching prompt is "Please log in to the second application using the bound XX account."

[0135] In this embodiment, when the first account logged in to the first application and the second account logged in to the second application do not have a binding relationship, the terminal can remind the user to log in to the third application with the second account that has a binding relationship with the first account by displaying an account switching prompt. That is, the user can only share the target graphic code to their own account, and the user can only migrate group users in their own account, avoiding the user's abuse of the group user migration method provided in the embodiments of the present application and causing harassment to other users.

[0136] For example, in response to a sharing instruction for the target graphic code, the terminal sends an account verification request to the first application server. The account verification request carries the first account and the second account, and the account verification request is used to obtain the binding relationship between the first account and the second account. In some embodiments, refer to Figure 12 , the account verification request is triggered by the terminal detecting a click operation on the graphic code sharing control 1004. After receiving the account verification request, the server can obtain the first account and the second account from the account verification request and query the binding situation between the first account and the second account in the binding relationship database. When the first application server determines that the first account is not bound to the second account, the first application server sends a binding relationship error message to the terminal. In response to receiving the binding relationship error message, the terminal displays an account switching prompt; when the first application server determines that the first account is bound to the second account, the first application server sends a binding relationship correct message to the terminal. In response to receiving the binding relationship correct message, the terminal displays a group sharing interface.

[0137] It should be noted that after the terminal executes step 304, it can also choose to execute the following steps 305-307, and the embodiments of the present application do not make any limitations in this regard.

[0138] 305. In response to detecting a trigger operation on the target group in the group sharing interface, the terminal shares the target graphic code to the target group in the second application, so that the users of the target group can join the first group of the first application based on the target graphic code, and the target group has a binding relationship with the target graphic code.

[0139] In a possible implementation, in response to detecting a trigger operation on a target group in the group sharing interface, the terminal displays a sharing confirmation interface, on which the group identifier of the target group and a sharing confirmation control are displayed. In response to detecting a click operation on the sharing confirmation control, the terminal shares the target graphic code to the target group in the second application. Users in the target group can join the first group in the first application by identifying the target graphic code, thereby achieving the purpose of migrating the users in the target group to the first group in the first application. Since there is a binding relationship between the target group and the target graphic code, in some embodiments, if a user in the target group shares the target graphic code to other groups in the second application, users in other groups cannot join the first group through the target graphic code.

[0140] For example, referring to Figure 12 and Figure 13 , a group sharing interface 1201 of the second application is displayed on the terminal, on which at least one group information 1202 in the second application and a group sharing control 1203 are displayed. The user can select the group to which they want to share the graphic code by clicking on the selection box 1204 in front of the group information 1202. After selecting the target group through the selection box 1204, clicking on the group sharing control 1203 can trigger a sharing confirmation instruction. In response to the sharing confirmation instruction, the terminal displays a sharing confirmation interface 1301, on which the group identifier 1302 of the target group, the target graphic code 1303, and a sharing confirmation control 1304 are displayed. In response to detecting a click operation on the sharing confirmation control 1304, the terminal shares the target graphic code to the target group in the second application, where the display of the group identifier 1302 of the target group and the target graphic code 1303 is used to remind the user to confirm whether the selected group is the group they want to share.

[0141] 306. The terminal switches the group sharing interface to display a graphic code display interface, on which the group identifier of the first group and the number of users in the first group are displayed.

[0142] In a possible implementation, in response to detecting an operation of sharing the target graphic code to the target group, the terminal switches the group sharing interface to the graphic code display interface of the first application.

[0143] For example, referring to Figure 10 , a graphic code display interface 1001 displays the target graphic code 1002 and the group information 1003 corresponding to the target graphic code. The group information 1003 includes the group identifier of the first group and the number of users in the first group. The user can quickly know the group identifier of the first group and the number of users in the first group through the group information 1003.

[0144] In some embodiments, in response to detecting a trigger operation on the group identifier of the first group, the terminal displays the group chat interface of the first group. That is to say, when the terminal displays the graphical code display interface, the user can quickly switch the graphical code display interface to the chat interface of the first group by clicking on the group identifier of the first group, and communicate with the users in the first group, with relatively high efficiency of human-computer interaction.

[0145] Based on the above implementation, when any user in the target group joins the first group, the terminal can update the number of users in the first group on the graphical code display interface.

[0146] That is to say, when the users in the target group join the first group by recognizing the graphical code, the terminal can update the number of users in the first group displayed on the graphical code display interface, and the user can know in real time the progress of migrating the users in the target group to the first group, with relatively high efficiency of human-computer interaction.

[0147] 307. When the number of users in the first group meets the target number condition, the terminal displays the group identifier of the second group and the number of users in the second group on the graphical code display interface. The second group is a newly created group in the first application and corresponds to the target graphical code.

[0148] Among them, that the number of users in the first group meets the target number condition means that the number of users in the first group is equal to the number threshold. In some embodiments, the number threshold is 200. The group identifier of the second group is associated with the group identifier of the first group and the identifier of the target graphical code. Taking the identifier as the name for example, if the name of the target graphical code is "Fruit Group" and the group identifier of the first group is "Fruit Group 1", then the group identifier of the second group is "Fruit Group 2". In this case, the user only needs to set a name for the target graphical code, and the name of the first group can be automatically generated. At the same time, when creating the second group again, the second group can automatically continue the name of the first group, with relatively high efficiency of human-computer interaction. In some embodiments, the target graphical code can correspond to 100 groups. That is to say, when the number of users in the second group meets the target number condition, the terminal can also display the group identifier of the third group and the number of users in the third group on the graphical code display interface, and so on.

[0149] By executing step 307, when the first group is full of users, the second group can be automatically created. When the users in the target group recognize the target graphical code again when the first group is full of users, they can directly join the second group. At the same time, the terminal can also display the relevant information of the second group on the graphical code display interface, and the user can quickly know the number of users in the second group through the graphical code display interface, with relatively high efficiency of human-computer interaction.

[0150] Optionally, before step 301, the terminal can also perform the following steps.

[0151] In a possible implementation, a first account is logged in to the first application. When any graphic code has been created under the first account, the terminal displays a group display interface, on which the identifier of the graphic code and the number of groups corresponding to the graphic code are displayed.

[0152] For example, referring to Figure 14 , the terminal can display a group display interface 1401, on which the graphic code 1402 created by the first account, the graphic code identifier 1403 corresponding to the graphic code 1402, the number of groups and the number of group users 1404 corresponding to the graphic code identifier 1403, the group sharing control 1405 corresponding to the graphic code identifier 1403, and the graphic code creation control 1406 are displayed. In response to detecting a click operation on the graphic code sharing control 1405, the terminal can perform the operation shown in step 303 above. In response to detecting a click operation on the graphic code creation control 1406, the terminal can perform the operation shown in step 301 above.

[0153] All of the above optional technical solutions can be combined arbitrarily to form alternative embodiments of the present application, which will not be elaborated here one by one.

[0154] Through the technical solution provided by the embodiments of the present application, when an application needs to be replaced, only a target graphic code needs to be created on the first application and the target graphic code is shared to a target group in the second application. Users in the target group can quickly join the group in the first application through the target graphic code, and the efficiency of group user migration is relatively high. In addition, since the target group is bound to the target graphic code, it means that only users in the target group can join the first group based on the target graphic code, and users in other groups in the second application cannot join the first group based on the target graphic code, realizing one code for one group, and the security of the target graphic code is relatively high.

[0155] The above steps 301-307 are described based on the terminal as the execution subject. Next, the process of executing the technical solution provided by the embodiments of the present application by the first application server as the execution subject will be described. The first application server is used to provide background services for the first application. Referring to Figure 15 , the method includes:

[0156] 1501. In response to a group user migration request from a target user, the first application server creates a target graphic code and a first group corresponding thereto in the first application. The group user migration request is used to request migrating users in any group in the second application to a group in the first application.

[0157] Among them, the second application and the first application are application programs with interoperable user data, and the account registered in the second application can be used to log in to the first application. The target user is a user who uses the first application.

[0158] In a possible implementation manner, in response to a creation instruction triggered by a graphic code creation interface, the terminal can send a group user migration request to the first application server. In response to receiving the group user migration request, the first application server can create a target graphic code and a first group corresponding to the target graphic code, and the first group is a group in the first application.

[0159] For example, referring to Figure 8 , in response to a creation instruction triggered by the graphic code creation interface 801, that is, a creation instruction triggered by the user clicking the graphic code creation control 803, the terminal sends a group user migration request to the first application server. If the user enters the identifier of the target graphic code on the graphic code creation interface 801, the group user migration request carries the identifier of the target graphic code. In response to receiving the group user migration request, the first application server creates the target graphic code and the first group corresponding to the target graphic code. If the group migration request carries the identifier of the target graphic code, the first application server can obtain the identifier of the target graphic code from the group user migration request and generate the group identifier of the first group based on the identifier of the target graphic code.

[0160] 1502. In response to the target user sharing the target graphic code to the target group in the second application, the first application server binds the target graphic code to the target group.

[0161] In a possible implementation manner, in response to a sharing instruction for the target graphic code, the terminal sends a sharing request for the target graphic code to the first application server. In response to receiving the sharing request for the target graphic code, the first application server shares the target graphic code to the target group in the second application and binds the target graphic code to the target group at the same time.

[0162] For example, referring to Figure 13 , in response to detecting a click operation on the sharing confirmation control 1304, the terminal sends a sharing request for the target graphic code to the first application server, and the sharing request for the target graphic code carries the group identifier of the target group. In response to receiving the sharing request for the target graphic code, the first application server shares the target graphic code to the target group in the second application, obtains the group identifier of the target group from the sharing request for the target graphic code, and binds the target graphic code to the group identifier of the target group.

[0163] In this implementation manner, during the process of the first application server subsequently adding users to the first group, the first application server will only add users who are in the target group to the first group, thereby improving the security of the target graphic code.

[0164] 1503. In response to a join request from any user in the second application to the first group, the first application server determines the group to which the user belongs in the second application.

[0165] Optionally, the join request for the first group is triggered by the user based on the target graphic code.

[0166] In a possible implementation manner, the join request for the first group carries the group identifier of the group to which the user belongs in the second application. The first application server can obtain the group identifier of the group to which the user belongs in the second application from the join request for the first group, and this group identifier can also indicate the group to which the user belongs in the second application.

[0167] 1504. In response to the user belonging to the target group bound to the target graphic code, the first application server adds the user to the first group of the first application.

[0168] In a possible implementation manner, in response to the group identifier of the group to which the user belongs in the second application being the same as the group identifier of the target group, the first application server adds the user to the first group of the first application.

[0169] Optionally, after step 1503, in addition to being able to execute step 1504, the first application server can also execute the following steps.

[0170] In a possible implementation manner, in response to the user not belonging to the target group bound to the target graphic code, the first application server rejects the user's join request for the first group.

[0171] In this implementation manner, only users in the target group can join the first group, and users not in the target group cannot join the first group, achieving "one group, one code", and improving the security of the target graphic code.

[0172] The above implementation manners are illustrated below through two examples.

[0173] Example 1. In response to the user's join request for the second group based on the target graphic code, the first application server obtains the group identifier of the group to which the user belongs in the second application. In response to the group identifier of the group to which the user belongs not including the group identifier of the target group, the first application server rejects the user's join request for the first group, and the user cannot join the first group.

[0174] Example 2: The group ID of the group to which the user belongs in the second application is carried in the join request for the first group. The first application server can obtain the group ID of the group to which the user belongs in the second application from the join request for the first group. In response to the group ID of the group to which the user belongs in the second application being different from the group ID of the target group, the first application server rejects the user's join request for the first group, and the user cannot join the first group.

[0175] 1505. In response to the number of users in the first group meeting the target number condition, the first application server creates a second group in the first application, and the second group corresponds to the target graphic code.

[0176] 1506. In response to a first group join request of other users in the target group based on the target graphic code, the first application server adds the other users to the second group of the first application.

[0177] Through steps 1505 and 1506, when the number of users in the first group is full, the first application server can automatically create a second group corresponding to the target graphic code. Users in the target group can directly join the second group based on the target graphic code without the need for users to manually create a group, saving labor operation costs.

[0178] Of course, in the above description process, only steps 1501 - 1505 are taken as examples for illustration. After step 1505, in response to the number of users in the second group meeting the target number condition, the first application server can continue to create a third group corresponding to the target graphic code, and so on. The number of groups corresponding to the target graphic code in the embodiments of the present application is not limited.

[0179] The following will combine the attached Figure 16 , and the drawings in the above steps 301 - 307, the above steps 1501 - 1506, and the various embodiments above, to further illustrate the technical solutions provided by the present application.

[0180] In the following description process, the graphic code is taken as a QR code, and the user's operation on the first application is taken as an example. Refer to Figure 4 , the group chat addition interface 401 of the first application is displayed on the terminal, and the group chat addition control 402 is displayed on the group chat addition interface 401. The user can migrate the users of any group in the second application to the first application by clicking the group chat addition control 402. In response to detecting a click operation on the group chat addition control 402, the terminal can trigger a group user migration instruction. In response to the group user migration instruction, the terminal determines whether the first account logged in on the first application is bound to any target account. In the case where the first account is bound to the target account and the target account is not in a blocked state, refer to Figure 5, the terminal switches the group chat addition interface 401 of the first application to the first group user migration interface 501. On the first group user migration interface 501, a function introduction 502 of this interface and a group user migration control 503 are displayed. In response to detecting a click operation on the group user migration control 503, refer to Figure 5 , the terminal switches the first group user migration interface 501 to the graphic code creation interface 801 of the first application. On the graphic code creation interface 801, a graphic code identifier input box 802 and a graphic code creation control 803 are displayed. In response to detecting a click operation on the graphic code creation control 803, the terminal sends a group user migration request to the first application server. The group user migration request carries the characters entered in the graphic code identifier input box 802. In response to the first application server receiving the group user migration request, it can generate a target graphic code and a first group corresponding to the target graphic code based on the characters entered in the graphic code identifier input box 802, and send the target graphic code to the terminal. The terminal receives the target graphic code sent by the first application server and displays the target graphic code 1002 on the graphic code display interface 1001 of the first application. A graphic code sharing control 1004 is also displayed on the graphic code display interface 1001. In response to detecting a click operation on the graphic code sharing control 1004, the terminal determines whether the second application is installed. If the second application is installed, the terminal determines whether there is a binding relationship between the second account logged in on the second application and the first account logged in on the first application. In the case where there is a binding relationship between the first account and the second account, the application can select a group in the second application through the terminal. Refer to Figure 13, in response to detecting a click operation on the sharing confirmation control 1304, the terminal can send a sharing request for the target graphic code to the first application server, and the sharing request for the target graphic code carries the group identifier of the target group. In response to receiving the sharing request for the target graphic code, the first application server shares the target graphic code with the target group. At the same time, the first application server obtains the group identifier of the target group from the sharing request for the target graphic code and binds the group identifier of the target group to the target graphic code. Users in the target group in the second application can join the first group of the first application by recognizing the target graphic code, and the first application server can update the number of users in the first group. When users in other groups in the second application want to join the first group through the target graphic code, the first application server will reject the joining request of the other users to the first group, that is, users in other groups cannot join the first group through the target graphic code. When the first application server determines that the number of people in the first group reaches the upper limit, it can create a second group corresponding to the target graphic code and send the relevant information of the second group to the first application, and the terminal can display the relevant information of the second group to the user through the first application. When the user wants to query the group information corresponding to the target graphic code, he only needs to browse the graphic code display interface 1001 of the first application.

[0181] The above description explains the process of the user creating a new graphic code. For the method of the user viewing the existing graphic code, refer to the relevant description of Figure 14 in step 307, which will not be elaborated here.

[0182] Through the technical solution provided by the embodiments of the present application, when an application program needs to be replaced, only a target graphic code needs to be created on the first application and shared to the target group in the second application. Users in the target group can quickly join the group in the first application through the target graphic code, and the efficiency of group user migration is relatively high. In addition, since there is a binding relationship between the target group and the target graphic code, it means that only users in the target group can join the first group based on the target graphic code, and users in other groups in the second application cannot join the first group based on the target graphic code, realizing one code for one group, and the security of the target graphic code is relatively high.

[0183] Figure 17 is a schematic structural diagram of a group user migration device provided by the embodiments of the present application. The device is applied to the first application server, and the first application server is used to provide background services for the first application. Refer to Figure 17 , the device includes: a creation module 1701, a binding module 1702, a determination module 1703, and an addition module 1704.

[0184] A creation module 1701, configured to create a target graphic code and a first group corresponding thereto in a first application in response to a group user migration request of a target user, where the group user migration request is used to request to migrate users in any group in a second application to a group in the first application.

[0185] A binding module 1702, configured to bind the target graphic code to a target group in the second application in response to the target user sharing the target graphic code to the target group in the second application.

[0186] A determination module 1703, configured to determine the group to which a user belongs in the second application in response to a join request of any user in the second application for the first group.

[0187] An addition module 1704, configured to add a user to the first group of the first application in response to the user belonging to the target group bound to the target graphic code.

[0188] In a possible implementation manner, the addition module is further configured to add a user to the first group of the first application in response to the group identifier of the group to which the user belongs in the second application being the same as the group identifier of the target group.

[0189] In a possible implementation manner, the addition module is further configured to reject a join request of a user for the first group in response to the user not belonging to the target group bound to the target graphic code.

[0190] In a possible implementation manner, the addition module is further configured to reject a join request of a user for the first group in response to the group identifier of the group to which the user belongs in the second application being different from the group identifier of the target group.

[0191] In a possible implementation manner, the creation module is further configured to create a second group in the first application in response to the number of users in the first group meeting a target number condition, where the second group corresponds to the target graphic code.

[0192] In a possible implementation manner, the addition module is further configured to add other users to the second group of the first application in response to a join request of other users in the target group for the first group.

[0193] It should be noted that: when migrating group users, the group user migration device provided in the above embodiments is only illustrated by dividing the above functional modules. In actual applications, the above functions can be allocated to different functional modules as needed, that is, the internal structure of the computer device is divided into different functional modules to complete all or part of the functions described above. In addition, the group user migration device provided in the above embodiments and the group user migration method embodiments belong to the same concept. For the specific implementation process, refer to the method embodiments, which will not be elaborated here.

[0194] Through the technical solution provided by the embodiments of the present application, when an application needs to be replaced, only a target graphic code needs to be created on the first application and the target graphic code is shared to a target group in the second application. Users in the target group can quickly join the group in the first application through the target graphic code, and the efficiency of group user migration is relatively high. In addition, since there is a binding relationship between the target group and the target graphic code, it means that only users in the target group can join the first group based on the target graphic code, and users in other groups in the second application cannot join the first group based on the target graphic code, realizing one code for one group, and the security of the target graphic code is relatively high.

[0195] Figure 18 is a schematic structural diagram of a group user migration device provided by the embodiments of the present application. Refer to Figure 18 The device includes: an instruction receiving module 1801, a graphic code display module 1802, and a second sharing module 1803.

[0196] The instruction receiving module 1801 is configured to receive a group user migration instruction, and the group user migration instruction is used to indicate migrating users in any group in the second application to a group in the first application.

[0197] The graphic code display module 1802 is configured to display a target graphic code in response to the group user migration instruction, and the target graphic code corresponds to a first group newly created in the first application.

[0198] The second sharing module 1803 is configured to share the target graphic code to a target group in the second application in response to a sharing instruction for the target graphic code, so that users in the target group can join the first group in the first application based on the target graphic code, and there is a binding relationship between the target group and the target graphic code.

[0199] In a possible implementation manner, the graphic code display module is configured to display a graphic code creation interface in response to the group user migration instruction.

[0200] In response to a creation instruction triggered based on the graphic code creation interface, a graphic code display interface is displayed, and the target graphic code is displayed on the graphic code display interface.

[0201] In a possible implementation manner, the number of users in the first group is also displayed on the graphic code display interface, and the graphic code display module is further configured to update the number of users in the first group on the graphic code display interface when any user in the target group joins the first group.

[0202] In a possible implementation manner, the group identifier of the first group is also displayed on the graphic code display interface, and the graphic code display module is further configured to display the group conversation interface of the first group in response to detecting a trigger operation on the group identifier of the first group.

[0203] In a possible implementation manner, the graphic code display module is further configured to, when the number of users in the first group meets the target number condition, display the group identifier of the second group on the graphic code display interface, where the second group is a newly created group in the first application and the second group corresponds to the target graphic code.

[0204] In a possible implementation manner, the second sharing module is configured to, in response to a sharing instruction for the target graphic code, display a group sharing interface, where the group sharing interface includes at least one group in the second application. In response to detecting a trigger operation on the target group in the group sharing interface, share the target graphic code to the target group in the second application.

[0205] In a possible implementation manner, a first account is logged in to the first application, and the device further includes any one of the following modules:

[0206] The first prompt module is configured to display an account unbound prompt when the first account is not bound to any target account.

[0207] The second prompt module is configured to display an account blocked prompt when the first account is bound to any target account and any target account is in a blocked state.

[0208] Wherein, the target account is an account registered in the second application.

[0209] In a possible implementation manner, a first account is logged in to the first application, and a second account is logged in to the second application. The device further includes:

[0210] The third prompt module is configured to display an account switching prompt when the second account is different from the third account. The account switching prompt is used to prompt to log in to the second application with the third account, where the third account is an account registered in the second application and bound to the first account.

[0211] In a possible implementation manner, a first account is logged in to the first application, and the device further includes:

[0212] The group display interface display module is configured to, when the first account has created any graphic code, display a group display interface, where any graphic code and the number of groups corresponding to any graphic code are displayed on the group display interface.

[0213] It should be noted that: when migrating group users, the group user migration device provided in the above embodiments is only illustrated by dividing the above functional modules. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the computer device is divided into different functional modules to complete all or part of the functions described above. In addition, the group user migration device provided in the above embodiments and the embodiments of the group user migration method belong to the same concept. For the specific implementation process, please refer to the method embodiments and will not be elaborated here.

[0214] Through the technical solution provided by the embodiments of the present application, when an application needs to be replaced, only a target graphic code needs to be created on the first application and the target graphic code is shared to the target group in the second application. Users in the target group can quickly join the group in the first application through the target graphic code, and the efficiency of group user migration is relatively high. In addition, since there is a binding relationship between the target group and the target graphic code, it means that only users in the target group can join the first group based on the target graphic code, and users in other groups in the second application cannot join the first group based on the target graphic code, realizing one code for one group, and the security of the target graphic code is relatively high.

[0215] The embodiments of the present application provide a computer device for executing the above method. The computer device can be implemented as a terminal or a first application server. First, the structure of the terminal will be introduced below:

[0216] Figure 19 It is a schematic structural diagram of a terminal provided by the embodiments of the present application. The terminal 1900 can be: a smart phone, a tablet computer, a notebook computer or a desktop computer. The terminal 1900 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, etc.

[0217] Generally, the terminal 1900 includes: one or more processors 1901 and one or more memories 1902.

[0218] The processor 1901 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. The processor 1901 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), or PLA (Programmable Logic Array). The processor 1901 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the wake state, also known as the CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 1901 may be integrated with a GPU (Graphics Processing Unit), and the GPU is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 1901 may further include an AI (Artificial Intelligence) processor, and the AI processor is used to process computational operations related to machine learning.

[0219] The memory 1902 may include one or more computer-readable storage media, and the computer-readable storage media may be non-transitory. The memory 1902 may further include high-speed random access memory and non-volatile memory, such as one or more disk storage devices and flash storage devices. In some embodiments, the non-transitory computer-readable storage media in the memory 1902 is used to store at least one computer program, and the at least one computer program is used to be executed by the processor 1901 to implement the group user migration method provided in the method embodiments of this application.

[0220] In some embodiments, the terminal 1900 may further optionally include: a peripheral device interface 1903 and at least one peripheral device. The processor 1901, the memory 1902, and the peripheral device interface 1903 may be connected through a bus or signal lines. Each peripheral device may be connected to the peripheral device interface 1903 through a bus, signal lines, or a circuit board. Specifically, the peripheral devices include at least one of a radio frequency circuit 1904, a display screen 1905, a camera module 1906, an audio circuit 1907, a positioning module 1908, and a power supply 1909.

[0221] The peripheral device interface 1903 can be used to connect at least one I / O (Input / Output) related peripheral device to the processor 1901 and the memory 1902. In some embodiments, the processor 1901, the memory 1902, and the peripheral device interface 1903 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1901, the memory 1902, and the peripheral device interface 1903 can be implemented on a separate chip or circuit board, and this embodiment does not limit this.

[0222] The radio frequency circuit 1904 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuit 1904 communicates with a communication network and other communication devices through electromagnetic signals. The radio frequency circuit 1904 converts an electrical signal into an electromagnetic signal for transmission, or converts the received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1904 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, and so on.

[0223] The display screen 1905 is used to display a UI (User Interface). The UI can include graphics, text, icons, videos, and any combination thereof. When the display screen 1905 is a touch display screen, the display screen 1905 also has the ability to collect touch signals on or above the surface of the display screen 1905. The touch signal can be input to the processor 1901 as a control signal for processing. At this time, the display screen 1905 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard.

[0224] The camera component 1906 is used to collect images or videos. Optionally, the camera component 1906 includes a front camera and a rear camera. Generally, the front camera is set on the front panel of the terminal, and the rear camera is set on the back of the terminal.

[0225] The audio circuit 1907 can include a microphone and a speaker. The microphone is used to collect sound waves of the user and the environment, and convert the sound waves into electrical signals for input to the processor 1901 for processing, or input to the radio frequency circuit 1904 to achieve voice communication.

[0226] The positioning component 1908 is used to locate the current geographical location of the terminal 1900 to achieve navigation or LBS (Location-Based Service).

[0227] The power supply 1909 is used to supply power to each component in the terminal 1900. The power supply 1909 can be alternating current, direct current, a primary battery, or a rechargeable battery.

[0228] In some embodiments, the terminal 1900 further includes one or more sensors 1910. The one or more sensors 1910 include, but are not limited to: an acceleration sensor 1911, a gyroscope sensor 1912, a pressure sensor 1913, a fingerprint sensor 1914, an optical sensor 1915, and a proximity sensor 1916.

[0229] The acceleration sensor 1911 can detect the magnitude of acceleration on the three coordinate axes of the coordinate system established with the terminal 1900.

[0230] The gyroscope sensor 1912 can detect the body orientation and rotation angle of the terminal 1900. The gyroscope sensor 1912 can cooperate with the acceleration sensor 1911 to collect the 3D actions of the user on the terminal 1900.

[0231] The pressure sensor 1913 can be disposed on the side frame of the terminal 1900 and / or the lower layer of the display screen 1905. When the pressure sensor 1913 is disposed on the side frame of the terminal 1900, it can detect the holding signal of the user on the terminal 1900, and the processor 1901 can perform left / right hand recognition or quick operation according to the holding signal collected by the pressure sensor 1913. When the pressure sensor 1913 is disposed on the lower layer of the display screen 1905, the processor 1901 can control the operable controls on the UI interface according to the pressure operation of the user on the display screen 1905.

[0232] The fingerprint sensor 1914 is used to collect the fingerprint of the user. The processor 1901 can identify the user's identity according to the fingerprint collected by the fingerprint sensor 1914, or the fingerprint sensor 1914 can identify the user's identity according to the collected fingerprint.

[0233] The optical sensor 1915 is used to collect the ambient light intensity. In one embodiment, the processor 1901 can control the display brightness of the display screen 1905 according to the ambient light intensity collected by the optical sensor 1915.

[0234] The proximity sensor 1916 is used to collect the distance between the user and the front of the terminal 1900.

[0235] Those skilled in the art can understand that Figure 19 the structure shown in [[ ]] does not constitute a limitation on the terminal 1900, and it may include more or fewer components than shown in the figure, or combine certain components, or adopt different component arrangements.

[0236] The above computer device can also be implemented as a first application server. The structure of the first application server will be introduced below:

[0237] Figure 20 FIG. 550 is a schematic structural diagram of a first application server provided by an embodiment of the present application. The first application server 2000 may vary greatly due to different configurations or performances, and may include one or more processors (Central Processing Units, CPUs) 2001 and one or more memories 2002. Among them, at least one computer program is stored in the one or more memories 2002, and the at least one computer program is loaded and executed by the one or more processors 2001 to implement the methods provided in the above various method embodiments. Of course, the first application server 2000 may also have components such as a wired or wireless network interface, a keyboard, and an input / output interface for input / output. The first application server 2000 may also include other components for implementing the functions of the device, which will not be elaborated here.

[0238] In an exemplary embodiment, a computer-readable storage medium is also provided, such as a memory including a computer program. The above computer program can be executed by a processor to complete the group user migration method in the above embodiment. For example, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0239] In an exemplary embodiment, a computer program product or a computer program is also provided. The computer program product or the computer program includes program code, and the program code is stored in a computer-readable storage medium. A processor of a computer device reads the program code from the computer-readable storage medium, and the processor executes the program code, so that the computer device executes the above group user migration method.

[0240] Those of ordinary skill in the art can understand that all or part of the steps for implementing the above embodiments can be completed by hardware, or can be completed by a program instructing relevant hardware. The program can be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk, an optical disc, etc.

[0241] The above are only optional embodiments of the present application, and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for migrating group users, characterized in that, Applied to the first application server, which is used to provide background services for the first application, the method includes: In response to a group user migration request from a target user, create a target barcode and a first group corresponding to the first application in the first application, where the group user migration request is used to request migrating users in any group in the second application to the group in the first application; In response to the target user sharing the target barcode to the target group in the second application, bind the target barcode to the target group; In response to a join request from any user in the second application to the first group, determine the group to which the user belongs in the second application; If the user belongs to the target group bound to the target barcode, add the user to the first group of the first application; If the user does not belong to the target group bound to the target barcode, reject the user's join request to the first group; In response to the number of users in the first group being equal to the threshold number, create a second group in the first application, where the second group corresponds to the target barcode; In response to a join request from other users in the target group to the first group, add the other users to the second group; Wherein, the group identifier of the second group is associated with the group identifier of the first group and the identifier of the target barcode.

2. The method according to claim 1, wherein The step of adding the user to the first group of the first application if the user belongs to the target group bound to the target barcode includes: If the group identifier of the group to which the user belongs in the second application is the same as the group identifier of the target group, add the user to the first group of the first application.

3. The method according to claim 1, wherein The step of rejecting the user's join request to the first group if the user does not belong to the target group bound to the target barcode includes: If the group identifier of the group to which the user belongs in the second application is different from the group identifier of the target group, reject the user's join request to the first group.

4. A method for migrating group users, characterized in that, The method further includes: Receive a group user migration instruction, which is used to indicate migrating users in any group in the second application to the group in the first application; In response to the group user migration instruction, display a target barcode, where the target barcode corresponds to the newly created first group in the first application; In response to a sharing instruction for the target barcode, share the target barcode to the target group in the second application, so that the users in the target group can join the first group of the first application based on the target barcode, where the target group has a binding relationship with the target barcode, and the join requests from users in groups other than the target group in the second application to the first group are rejected; In response to the number of users in the first group being equal to a threshold number, display the group identifier of a second group on the graphical code display interface. The second group corresponds to the target graphical code, and the second group is a newly created group in the first application. The second group is used for users in the target group to join the second group after requesting to join the first group when the number of users in the first group is equal to the threshold number; wherein the group identifier of the second group is associated with the group identifier of the first group and the identifier of the target graphical code.

5. The method according to claim 4, characterized in that, The displaying of the target graphical code in response to the group user migration instruction includes: In response to the group user migration instruction, display a graphical code creation interface; In response to a creation instruction triggered based on the graphical code creation interface, display a graphical code display interface, and the target graphical code is displayed on the graphical code display interface.

6. The method according to claim 5, characterized in that The number of users in the first group is also displayed on the graphical code display interface, and the method further includes: When any user in the target group joins the first group, update the number of users in the first group on the graphical code display interface.

7. The method according to claim 5, characterized in that, The group identifier of the first group is also displayed on the graphical code display interface, and the method further includes: In response to detecting a trigger operation on the group identifier of the first group, display the group chat interface of the first group.

8. A group user migration device, characterized in that, Applied to a first application server, the first application server is used to provide background services for a first application, and the device includes: A creation module, configured to create a target graphical code and a corresponding first group in the first application in response to a group user migration request of a target user, where the group user migration request is used to request to migrate users in any group in a second application to a group in the first application; A binding module, configured to bind the target graphical code to the target group in response to the target user sharing the target graphical code to the target group in the second application; A determination module, configured to determine the group to which the user belongs in the second application in response to a join request of any user in the second application for the first group; An adding module, configured to add the user to the first group of the first application when the user belongs to the target group bound to the target graphical code; and reject the user's join request for the first group when the user does not belong to the target group bound to the target graphical code; The creation module is further configured to create a second group in the first application in response to the number of users in the first group being equal to the threshold number, and the second group corresponds to the target graphical code; The adding module is further configured to add the other users to the second group in response to a join request of other users in the target group for the first group; wherein the group identifier of the second group is associated with the group identifier of the first group and the identifier of the target graphical code.

9. A group user migration device, characterized in that, The device includes: An instruction receiving module, configured to receive a group user migration instruction for instructing to migrate users in any group in a second application to a group in a first application; A graphic code display module, configured to display a target graphic code in response to the group user migration instruction, where the target graphic code corresponds to a first group newly created in the first application; A second sharing module, configured to share the target graphic code to a target group in the second application in response to a sharing instruction for the target graphic code, so that users in the target group can join the first group in the first application based on the target graphic code. There is a binding relationship between the target group and the target graphic code, and join requests from users in groups other than the target group to the first group are rejected; The graphic code display module is further configured to display a group identifier of a second group on the graphic code display interface in response to the number of users in the first group being equal to a threshold. The second group corresponds to the target graphic code, and the second group is a group newly created in the first application. The second group is used for users in the target group to join after requesting to join the first group when the number of users in the first group is equal to the threshold; Wherein, the group identifier of the second group is associated with the group identifier of the first group and the identifier of the target graphic code.

10. A computer device, characterized in that, The computer device includes one or more processors and one or more memories. At least one computer program is stored in the one or more memories, and the computer program is loaded and executed by the one or more processors to implement the group user migration method according to any one of claims 1 to 3, or to implement the group user migration method according to any one of claims 4 to 7.

11. A computer-readable storage medium, characterized in that, At least one computer program is stored in the computer-readable storage medium, and the computer program is loaded and executed by a processor to implement the group user migration method according to any one of claims 1 to 3, or to implement the group user migration method according to any one of claims 4 to 7.

Images