Methods, apparatus, electronic devices and storage media for team merging

Abstract

This application provides a method, apparatus, electronic device, and storage medium for merging teams. The method includes a central process receiving merge request information from multiple teams, wherein the merge request information includes team change information and a version number of each team; then, in response to determining that the version number of each team is the latest version number, the central process generates member change information for each team based on the team change information; and the central process notifies the edge processes of each team to obtain the member change information from the central process, so that the multiple teams can be merged. This allows the merging of teams to be achieved through the central process, ensuring the correctness of the merged team data.

Description

Technical Field

[0001] This application relates to the field of team merging technology, and in particular to a method, apparatus, electronic device and storage medium for team merging. Background Technology

[0002] This section is intended to provide background or context for the embodiments of this application as set forth in the claims. The description herein is not intended to be a prior art simply because it is included in this section.

[0003] Most games currently have team-up features. In a standard team-up system, players and teams are independent entities. Players can join and leave teams, and team data changes accordingly. For example, a player joining might increase the team's combat power, thus affecting the team's progress in levels. With the diversification of game genres, an idle / idle game has emerged, allowing online players to help offline players perform actions such as monster hunting, influencing the offline players' data. Furthermore, to enhance player interaction, there's a desire to merge teams, meaning two or more teams can be combined, transferring data from the previous team to the new one. However, existing game team-up systems don't support merging teams; they only allow individual players to join teams. To merge teams A and B, players from team A often need to leave team A and then join team B. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a method, apparatus, electronic device and storage medium for team merging.

[0005] For the purposes described above, this application provides a method for merging teams, comprising:

[0006] The central process receives merge request information from multiple teams, wherein the merge request information includes team change information and version number of each team;

[0007] The central process responds to determining that the version number of each team is the latest version number, and generates member change information for each team based on the team change information;

[0008] The central process notifies the edge processes of each team to obtain the member change information from the central process, so that the multiple teams can be merged.

[0009] In some embodiments, before the central process determines that the version number of each team is the latest version number, the method further includes:

[0010] The central process responds by determining that the version number of each team is the maximum value among the same teams, and determines that the version number of each team is the latest version number;

[0011] In this context, each time the member information of each team changes, the version number increases by one unit value.

[0012] In some embodiments, after generating member change information for each team based on the team change information, the method further includes:

[0013] The central process updates the version number of each team;

[0014] In some embodiments, generating member change information for each team based on the team change information specifically includes:

[0015] The central process generates member change information for each team based on Lua scripts and the team change information.

[0016] The Lua script is used to ensure that no other instructions are inserted when generating member change information for each team multiple times.

[0017] In some embodiments, before generating the member change information for each team based on the team change information, the method further includes:

[0018] The central process determines whether the total number of members in the multiple teams is greater than a preset threshold.

[0019] In response to determining that the total number of members in the multiple teams is greater than a preset threshold, the central process will no longer generate member change information for each team.

[0020] In some embodiments, before generating the member change information for each team based on the team change information, the method further includes:

[0021] The central process determines whether the version number of each team has changed;

[0022] In response to determining that the version number of any one of the multiple teams has changed, the central process stops generating member change information for each team.

[0023] In some embodiments, after the central process notifies the edge processes of each team to obtain the member change information from the central process, the method further includes:

[0024] The edge process of each team obtains the member change information from the central process and merges the teams based on the member change information.

[0025] In some embodiments, the plurality of teams includes a receiving team and a transferring team, wherein the transferring team includes at least one member to be transferred; merging teams based on the member change information specifically includes:

[0026] The edge process where the transfer member team is located sends the data information of the member to be transferred to the edge process where the receiving member team is located, based on the member change information.

[0027] In some embodiments, the data information of the members to be transferred includes the team version number; merging teams based on the member change information further includes:

[0028] The edge process containing the transferred member team updates the team version number of the member to be transferred based on the member change information.

[0029] In some embodiments, after merging teams based on the member change information, the method further includes:

[0030] The edge process of each team sends the current member information to the central process;

[0031] The central process saves the received current member information and deletes it after a preset time.

[0032] Based on the same inventive concept, an exemplary embodiment of this application also provides a team merging apparatus, the apparatus being applied to a distributed team-building system, wherein the team-building system includes a central process for processing team merging and edge processes where each team is located; the placement includes:

[0033] The receiving module receives merge request information from multiple teams, wherein the merge request information includes team change information and version number of each team;

[0034] The change module, in response to determining that the version number of each team is the latest version number, generates member change information for each team based on the team change information;

[0035] The notification module, wherein the central process notifies the edge processes of each team to obtain the member change information from the central process, so that the multiple teams can be merged.

[0036] Based on the same inventive concept, an exemplary embodiment of this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor executes the program to implement the team merging method as described above.

[0037] Based on the same inventive concept, an exemplary embodiment of this application also provides a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the team merging method as described above.

[0038] As can be seen from the above description, the team merging method, apparatus, electronic device, and storage medium provided in this application are applied to a distributed team-building system. The team-building system includes a central process for processing team merging and edge processes where each team resides. The method includes receiving merge request information from multiple teams through the central process. The merge request information includes team change information and the version number of each team. Then, in response to determining that the version number of each team is the latest version number, the central process generates member change information for each team based on the team change information. Furthermore, the central process notifies the edge processes where each team resides to obtain the member change information from the central process, enabling the multiple teams to merge. This allows for team merging through the central process, ensuring the correctness of the merged data. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in this application or related technologies, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 This is a flowchart illustrating a method for merging teams according to an embodiment of this application;

[0041] Figure 2 This is a schematic diagram illustrating the generation of member change information by a central process according to an embodiment of this application;

[0042] Figure 3 This is a schematic diagram illustrating a central process notifying an edge process to obtain member update information, according to an embodiment of this application.

[0043] Figure 4 This is a schematic diagram illustrating how an edge process sends data information of a member to be transferred, according to an embodiment of this application.

[0044] Figure 5 This is a schematic diagram illustrating how a central process stores the current member information of a peripheral process, according to an embodiment of this application.

[0045] Figure 6 This is a schematic diagram of a team merging device according to an embodiment of this application;

[0046] Figure 7 This is a schematic diagram of the structure of a specific electronic device according to an embodiment of this application. Detailed Implementation

[0047] The principles and spirit of this application will now be described with reference to several exemplary embodiments. It should be understood that these embodiments are provided merely to enable those skilled in the art to better understand and implement this application, and are not intended to limit the scope of this application in any way. Rather, these embodiments are provided to make this application more thorough and complete, and to fully convey the scope of this application to those skilled in the art.

[0048] According to embodiments of this application, a method, apparatus, electronic device, and storage medium for team merging are proposed.

[0049] In this article, it is important to understand that any number of elements in the accompanying figures is for illustrative purposes and not for limitation, and any naming is for distinction only and has no limiting meaning.

[0050] The principles and spirit of this application will be explained in detail below with reference to several representative embodiments.

[0051] In existing technologies, most games do not support merging teams; that is, players can only join teams individually. To merge two teams, A and B, players from team A often need to leave team A and then join team B. Furthermore, while some games implement team merging, these games are single-server architectures, meaning the two teams to be merged reside in the same process. Therefore, modifying team states can be done directly in memory. However, when teams A and B are not in the same process, if a player from team A successfully leaves team A but fails to join team B, that player will be in a teamless state. Additionally, because teams A and B are not in the same process, the merging process may be interspersed with operations from other teams. For example, if team B adds other members through other means, such as approving applications, team B's number of members will increase, potentially exceeding the team limit for both teams. Therefore, existing technologies cannot guarantee the correctness of team merging in a distributed architecture.

[0052] To address the aforementioned problems, this application provides a method for merging teams, applied to a distributed team-building system, wherein the team-building system includes a central process for handling team merging and edge processes where each team resides; the method includes:

[0053] The central process receives merge request information from multiple teams, including team change information and each team's version number. Then, in response to confirming that each team's version number is the latest version number, the central process generates member change information for each team based on the team change information. Furthermore, the central process notifies the edge processes of each team to retrieve the member change information from the central process, enabling the multiple teams to merge. This allows for team merging through the central process, ensuring the accuracy of the merged data.

[0054] After introducing the basic principles of this application, the various non-limiting embodiments of this application will be described in detail below.

[0055] In specific application scenarios, the team merging method of this application can be applied to various game systems involving team formation systems.

[0056] In some specific application scenarios, the team merging method of this application can be applied to other network systems involving team systems, such as network chat systems, where the method of this application can realize the merging of chat teams.

[0057] The following describes a team merging method according to an exemplary embodiment of this application, using specific application scenarios. It should be noted that the above application scenarios are shown only to facilitate understanding of the spirit and principles of this application, and the embodiments of this application are not limited in any way. Rather, the embodiments of this application can be applied to any applicable scenario.

[0058] refer to Figure 1 This application provides a method for merging teams, applied to a distributed team-building system, wherein the team-building system includes a central process for handling team merging and edge processes where each team resides; the method includes the following steps:

[0059] S101, the central process receives merge request information from multiple teams, wherein the merge request information includes team change information and version number of each team.

[0060] In practice, when multiple teams need to merge, they will send a merge request message to the central process. Optionally, the merge request message can be sent directly by the system server where multiple teams are located, or it can be sent by the edge process where a team is located. There is no limitation here. For example, when team A initiates a team merge request to team B, and then team B agrees to the merge request, it sends a request to the central process to merge team A and team B.

[0061] In some embodiments, the distributed team system includes multiple network nodes, each network node corresponding to a process. Optionally, the central process is set on one network node, and the edge processes of different teams are set on different network nodes.

[0062] It should be noted that the merge request information includes team change information and the version number of each team. The team change information indicates how the multiple teams are merged. For example, when team A and team B merge, the team change information could be "Member A1 of team A is merged into team B". The version number of each team indicates the version corresponding to the current team member. Optionally, the version number will change each time the team members change. Optionally, the merge request information may also include member information for each team.

[0063] S102, the central process responds to determining that the version number of each team is the latest version number, and generates member change information for each team based on the team change information.

[0064] In practice, after receiving merge request information from multiple teams, the central process, upon confirming that the version number of each team is the latest version, generates member change information for each team based on the team change information. Optionally, since the team change information can indicate how the multiple teams should be merged, obtaining this member change information allows determining how the members of each team should change. (Reference) Figure 2 The central process generates member change information for team A and team B respectively based on the team change information.

[0065] It should be noted that ensuring each team's version number is the latest version number is to guarantee that the current team merge will not conflict with other teams. For example, if the current team merge request is for team A and team B, then, assuming the members of teams A and B have not changed, the version numbers of teams A and B should each be the latest. If, during the period when teams A and B issue a merge request but have not yet completed the merge, teams B and C complete their merge in the central process, since the version numbers of team B's members will definitely be updated after the merge, the merge of teams A and B should not continue. The merge of teams A and B will only continue when the version numbers of teams A and B are both the latest version numbers.

[0066] In some embodiments, before the central process determines that the version number of each team is the latest version number, the method further includes:

[0067] The central process responds by determining that the version number of each team is the maximum value among the same teams, and determines that the version number of each team is the latest version number;

[0068] In this context, each time the member information of each team changes, the version number increases by one unit value.

[0069] In practice, the version number corresponding to each change in the member information of each team increases by one unit value. That is, the larger the version number of each team, the newer the corresponding version number. Therefore, when the central process determines that the version number of each team is the maximum value among the same teams, it can determine that the version number of each team is the latest version number.

[0070] It should be noted that the method described above for determining that the version number of each team is the latest version number is only one specific implementation of the embodiments of this application. Those skilled in the art can also determine that the version number of each team is the latest version number in other ways, which are not limited here. For example, the version number update time can be used to determine whether the version number of each team is the latest version number.

[0071] In some embodiments, after generating member change information for each team based on the team change information, the method further includes:

[0072] The central process updates the version number of each team;

[0073] In practice, to avoid conflicts during team merging, after generating member change information for each team, the central process updates the version number of each team. When merging teams after this update, the version number needs to be compared with the updated version number to determine which version number is newer. Optionally, the specific method of updating the version number is not limited here; for example, the version number can be updated by incrementing the value, or the update time corresponding to the updated version number can be recorded.

[0074] In some embodiments, generating member change information for each team based on the team change information specifically includes:

[0075] The central process generates member change information for each team based on Lua scripts and the team change information.

[0076] The Lua script is used to ensure that no other instructions are inserted when generating member change information for each team multiple times.

[0077] In practice, since the central process executes the instructions in the list sequentially according to the time they are received, to avoid inserting instructions for another team merge during a single team merge process, the central process generates member change information for each team based on a Lua script and the team change information. The Lua script ensures that no other instructions are inserted when generating member change information for each team multiple times. Optionally, the instructions for generating member change information for each team can be concatenated using a Lua script, allowing the central process to execute these instructions continuously until all teams have generated member change information. Alternatively, the multiple generation of member change information for each team can be edited into a single instruction using a Lua script, enabling the central process to generate member change information for each team multiple times using this single instruction.

[0078] To avoid exceeding the total number of members after team merging, in some embodiments, before generating the member change information for each team based on the team change information, the method further includes:

[0079] The central process determines whether the total number of members in the multiple teams is greater than a preset threshold.

[0080] In response to determining that the total number of members in the multiple teams is greater than a preset threshold, the central process will no longer generate member change information for each team.

[0081] It should be noted that the preset threshold can be set as needed, and no limitation is made here.

[0082] To further ensure the accuracy of team merging, in some embodiments, before generating the member change information for each team based on the team change information, the method further includes:

[0083] The central process determines whether the version number of each team has changed;

[0084] In response to determining that the version number of any one of the multiple teams has changed, the central process will no longer generate member change information for each team.

[0085] S103, the central process notifies the edge process of each team to obtain the member change information from the central process so that the multiple teams can be merged.

[0086] In practice, after the central process generates member change information for each team based on the team change information, the central process notifies the edge processes of each team to retrieve the member change information from the central process, so that the multiple teams can be merged. (Reference) Figure 3The central process sends a notification to edge processes 1 and 2 to retrieve the member change information, enabling edge processes 1 and 2 to obtain their respective member change information from the central process. Optionally, to prevent edge processes from missing the member change information, each team's edge process can be periodically notified to retrieve the member change information from the central process.

[0087] In some embodiments, after the central process notifies the edge processes of each team to obtain the member change information from the central process, the method further includes:

[0088] The edge process of each team obtains the member change information from the central process and merges the teams based on the member change information.

[0089] In some implementations, to prevent the team change process from being lost even after the central process's notification messages are lost, each team's edge process can periodically obtain the member change information from the central process.

[0090] In some embodiments, the plurality of teams includes a receiving team and a transferring team, wherein the transferring team includes at least one member to be transferred; merging teams based on the member change information specifically includes:

[0091] The edge process where the transfer member team is located sends the data information of the member to be transferred to the edge process where the receiving member team is located, based on the member change information.

[0092] In specific implementation, refer to Figure 4 Team A is the team transferring members, and Team B is the team receiving members. According to... Figure 3 The edge process 1, where team A is located, sends the data information of the member to be transferred to the edge process 2, where team B is located. Optionally, to ensure successful data transmission, the edge process of the receiving team sends an acknowledgment of receipt to the edge process of the transferring team after receiving the data information of the member to be transferred. If the edge process of the transferring team does not receive the acknowledgment of receipt within a predetermined time, it repeatedly sends the data information of the member to be transferred to the edge process of the receiving team until it receives the acknowledgment of receipt.

[0093] In some embodiments, the data information of the members to be transferred includes the team version number; merging teams based on the member change information further includes:

[0094] The edge process containing the transferred member team updates the team version number of the member to be transferred based on the member change information.

[0095] In practice, during the process of merging teams, some members of the teams to be transferred may be offline. In this case, the team version number of the member to be transferred needs to be updated to the latest team version number to prevent the member from reverting to the team before the merge upon logging back in. Optionally, to avoid loading a large number of players into memory, when a member to be transferred is offline, the transfer of the offline member's data can be paused. When the offline member logs back in, the offline member's data is sent to the edge process where the receiving member's team is located.

[0096] In some embodiments, after merging teams based on the member change information, the method further includes:

[0097] The edge process of each team sends the current member information to the central process;

[0098] The central process saves the received current member information and deletes it after a preset time.

[0099] In practice, to back up the current member information of each merged team, after merging the teams based on the member change information, the edge process of each team sends the current member information to the central process, and the central process saves the received current member information. (Reference) Figure 5 The central process updates and saves the current member information of edge processes 1 and 2. Meanwhile, since the edge processes save their respective team's current member information, this information can be deleted after a period of time, thus saving memory for the central process.

[0100] The team merging method provided in this application receives merge request information from multiple teams through a central process. The merge request information includes team change information and the version number of each team. Then, in response to determining that the version number of each team is the latest version number, the central process generates member change information for each team based on the team change information. Furthermore, the central process notifies the edge processes of each team to obtain the member change information from the central process, so that the multiple teams can be merged. This allows the team merging to be achieved through the central process, ensuring the correctness of the merged team data.

[0101] Based on the same inventive concept, corresponding to any of the above embodiments, this application also provides a team merging apparatus, which is applied to a distributed team system, wherein the team system includes a central process for processing team merging and edge processes where each team is located.

[0102] refer to Figure 6 The apparatus for merging the teams includes:

[0103] The receiving module 201 receives merge request information from multiple teams, wherein the merge request information includes team change information and version number of each team;

[0104] In the change module 202, the central process, in response to determining that the version number of each team is the latest version number, generates member change information for each team based on the team change information;

[0105] Notification module 203: The central process notifies the edge processes of each team to obtain the member change information from the central process, so that the multiple teams can be merged.

[0106] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, in implementing this application, the functions of each module can be implemented in one or more software and / or hardware.

[0107] The apparatus of the above embodiments is used to implement the corresponding team merging method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0108] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the team merging method described in any of the above embodiments.

[0109] Figure 7 This embodiment illustrates a more specific hardware structure of an electronic device, which may include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, memory 1020, input / output interface 1030, and communication interface 1040 are interconnected internally via the bus 1050.

[0110] The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0111] The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.

[0112] The input / output interface 1030 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components within the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., while output devices may include displays, speakers, vibrators, indicator lights, etc.

[0113] The communication interface 1040 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0114] Bus 1050 includes a pathway for transmitting information between various components of the device, such as processor 1010, memory 1020, input / output interface 1030, and communication interface 1040.

[0115] It should be noted that although the above-described device only shows the processor 1010, memory 1020, input / output interface 1030, communication interface 1040, and bus 1050, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.

[0116] The electronic devices described above are used to implement the corresponding team merging methods in any of the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0117] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the team merging method as described in any of the above embodiments.

[0118] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0119] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to execute the team merging method as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0120] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this application (including the claims) is limited to these examples; within the framework of this application, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this application as described above, which are not provided in detail for the sake of brevity.

[0121] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this application, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this application, and this also takes into account the fact that the details of the implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this application will be implemented (i.e., these details should be entirely within the understanding of those skilled in the art). While specific details (e.g., circuits) have been set forth to describe exemplary embodiments of this application, it will be apparent to those skilled in the art that the embodiments of this application can be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0122] Although this application has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.

[0123] The embodiments of this application are intended to cover all such substitutions, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the embodiments of this application should be included within the protection scope of this application.

Claims

1. A method for merging teams, characterized in that, The method is applied to a distributed team-building system, wherein the team-building system includes a central process for handling team merging and edge processes where each team is located; the method includes: The central process receives merge request information from multiple teams, wherein the merge request information includes team change information and version number of each team; The central process responds by determining that the version number of each team is the maximum value among the same teams, and determines that the version number of each team is the latest version number; wherein, the version number increases by one unit value for each change in the member information of each team. The central process responds to determining that the version number of each team is the latest version number, generates member change information for each team based on the team change information, and updates the version number of each team; The central process notifies the edge processes of each team to obtain the member change information from the central process, so that the multiple teams can be merged.

2. The method according to claim 1, characterized in that, Based on the team change information, member change information for each team is generated, specifically including: The central process generates member change information for each team based on Lua scripts and the team change information. The Lua script is used to ensure that no other instructions are inserted when generating member change information for each team multiple times.

3. The method according to claim 1, characterized in that, Before generating the member change information for each team based on the team change information, the method further includes: The central process determines whether the total number of members in the multiple teams is greater than a preset threshold. In response to determining that the total number of members in the multiple teams is greater than a preset threshold, the central process will no longer generate member change information for each team.

4. The method according to claim 1, characterized in that, Before generating the member change information for each team based on the team change information, the method further includes: The central process determines whether the version number of each team has changed; In response to determining that the version number of any one of the multiple teams has changed, the central process will no longer generate member change information for each team.

5. The method according to claim 1, characterized in that, After the central process notifies the edge processes of each team to obtain the member change information from the central process, the method further includes: The edge process of each team obtains the member change information from the central process and merges the teams based on the member change information.

6. The method according to claim 5, characterized in that, The multiple teams include a receiving team and a transferring team, wherein the transferring team includes at least one member to be transferred; The team merging is performed based on the aforementioned member change information, specifically including: The edge process where the transfer member team is located sends the data information of the member to be transferred to the edge process where the receiving member team is located, based on the member change information.

7. The method according to claim 6, characterized in that, The data information of the members to be transferred includes the team version number; merging teams based on the member change information also includes: The edge process containing the transferred member team updates the team version number of the member to be transferred based on the member change information.

8. The method according to claim 5, characterized in that, After merging teams based on the member change information, the method further includes: The edge process of each team sends the current member information to the central process; The central process saves the received current member information and deletes it after a preset time.

9. A device for merging teams, characterized in that, The device is applied to a distributed team-building system, wherein the team-building system includes a central process for handling team merging and edge processes for each team; the placement includes: The receiving module receives merge request information from multiple teams, wherein the merge request information includes team change information and version number of each team; The central process responds by determining that the version number of each team is the maximum value among the same teams, and determines that the version number of each team is the latest version number; wherein, the version number increases by one unit value for each change in the member information of each team. The change module, in response to determining that the version number of each team is the latest version number, generates member change information for each team based on the team change information, and updates the version number of each team; The notification module, wherein the central process notifies the edge processes of each team to obtain the member change information from the central process, so that the multiple teams can be merged.

10. An electronic device, characterized in that, The method includes a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor, when executing the program, implements the method as described in any one of claims 1 to 8.

11. A non-transitory computer-readable storage medium, characterized in that, The non-transitory computer-readable storage medium stores computer instructions for causing a computer to perform the method according to any one of claims 1 to 8.

Images