A cross-zone team processing method and related device

Abstract

The application discloses a cross-region team processing method and related device. The method comprises the following steps: in the case that a first account belongs to a first service area, a second account belongs to a second service area, and the first service area is different from the second service area, deploying a cross-region team process in a cross-region service area different from the first service area and the second service area, so as to bear the team function between the accounts in different service areas; creating a cross-region team belonging to the first account through the cross-region team process; when the second account sends a join request of the cross-region team to the cross-region team process, forwarding the join request to the first account through the cross-region team process; when the first account sends an approval request of the join request to the cross-region team process, adding the second account to the cross-region team based on the approval request through the cross-region team process, sending the join data of the second account in the cross-region team to a first world process belonging to the first service area, and sending the related data of the cross-region team to a second world process belonging to the second service area.

Description

Technical Field

[0001] This application relates to the field of data processing, and in particular to a cross-regional team processing method and related apparatus. Background Technology

[0002] At present, the application can provide multiple service areas, each with multiple accounts, and multiple accounts in each service area can team up.

[0003] In related technologies, the team-up processing method refers to deploying a team-up process in each service area to carry out the team-up function between multiple accounts in this service area.

[0004] However, multiple accounts in different service areas have a need to form teams, and the team-forming process in each service area described above cannot support the team-forming function between multiple accounts in different service areas. Summary of the Invention

[0005] To address the aforementioned technical issues, this application provides a cross-regional team-up processing method and related apparatus. When multiple accounts in different service areas have a team-up requirement, a cross-regional team-up process is deployed in a cross-regional service area outside the different service areas to support the team-up function between multiple accounts in different service areas.

[0006] The embodiments of this application disclose the following technical solutions:

[0007] On the one hand, embodiments of this application provide a method for cross-regional team formation, the method comprising:

[0008] After creating a cross-region team belonging to the first account through the cross-region team-up process, if the cross-region team-up process receives a join request from the second account, the join request is sent to the first account; the first account belongs to the first service region, the second account belongs to the second service region, the cross-region team-up process belongs to the cross-region service region, and the first service region, the second service region, and the cross-region service region are different;

[0009] If the first account receives an agreement request for joining the team through the cross-regional team formation process, the second account is added to the cross-regional team according to the agreement request;

[0010] The cross-region team-up process sends the joining data of the second account in the cross-region team to the first world process, and sends the relevant data of the cross-region team to the second world process; the first world process belongs to the first service area, and the second world process belongs to the second service area.

[0011] On the other hand, embodiments of this application provide a cross-regional team-up processing device, the device comprising: a sending unit and a joining unit;

[0012] The sending unit is configured to, after creating a cross-region team belonging to the first account through the cross-region team-up process, if it receives a join request for the cross-region team from the second account through the cross-region team-up process, send the join request to the first account; the first account belongs to the first service area, the second account belongs to the second service area, the cross-region team-up process belongs to the cross-region service area, and the first service area, the second service area, and the cross-region service area are different;

[0013] The joining unit is configured to, if it receives an agreement request for the joining request sent by the first account through the cross-regional team-up process, add the second account to the cross-regional team according to the agreement request;

[0014] The sending unit is further configured to send the joining data of the second account in the cross-region team to the first world process through the cross-region team formation process, and send the relevant data of the cross-region team to the second world process; the first world process belongs to the first service area, and the second world process belongs to the second service area.

[0015] On the other hand, embodiments of this application provide a computer device, the computer device including a processor and a memory:

[0016] The memory is used to store computer programs and to transfer the computer programs to the processor;

[0017] The processor is configured to execute the method described in any of the foregoing aspects according to instructions in the computer program.

[0018] On the other hand, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer device, causes the computer device to perform the methods described in any of the foregoing aspects.

[0019] On the other hand, embodiments of this application provide a computer program product, including a computer program that, when run on a computer device, causes the computer device to perform the method described in any of the foregoing aspects.

[0020] As can be seen from the above technical solution, for situations where the first account belongs to the first service area and the second account belongs to the second service area, and the first and second service areas are different, a cross-regional team-up process is deployed in a cross-regional service area that is different from the first and second service areas. This cross-regional team-up process carries the team-up function between multiple accounts in different service areas. A cross-regional team belonging to the first account is created through the cross-regional team-up process. When the second account sends a join request to the cross-regional team-up process, the join request is forwarded to the first account through the cross-regional team-up process. When the first account sends an acceptance request to the cross-regional team-up process, the second account is added to the cross-regional team based on the acceptance request. In this way, the first account in the first service area creates a cross-regional team through the cross-regional team-up process. Based on the cross-regional team-up process carrying the team-up function between multiple accounts in different service areas, the second account in the second service area (different from the first service area) can join the cross-regional team through the cross-regional team-up process, enabling multiple accounts in different service areas to complete team-up through the cross-regional team-up process. Based on this, the method sends the joining data of the second account in the cross-region team to the first world process belonging to the first service region through the cross-region team formation process, and sends the relevant cross-region team data to the second world process belonging to the second service region, so that different service regions can clearly identify the team status of the cross-region team. Therefore, when there is a team formation need between multiple accounts in different service regions, this method deploys a cross-region team formation process in a cross-region service region outside the different service regions to support the team formation function between multiple accounts in different service regions. Attached Figure Description

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

[0022] Figure 1 A system schematic diagram of a cross-regional team formation processing method provided in an embodiment of this application;

[0023] Figure 2 A flowchart illustrating a cross-regional team formation processing method provided in this application embodiment;

[0024] Figure 3 A schematic diagram illustrating the deployment of team-up processes, world processes, and scene processes in a service area, provided as an embodiment of this application;

[0025] Figure 4 This is a schematic diagram illustrating how a second account is added to a cross-region team based on a cross-region team join request sent by a second account, as provided in an embodiment of this application.

[0026] Figure 5 This is a schematic diagram illustrating a cross-region team creation process based on a cross-region team creation request sent by a first account, provided as an embodiment of this application.

[0027] Figure 6 This is a schematic diagram illustrating how a second account is removed from a cross-region team based on a leave request sent by the second account during a cross-region team formation process, as provided in an embodiment of this application.

[0028] Figure 7 A structural diagram of a cross-regional team-up processing device provided in this application embodiment;

[0029] Figure 8 A structural diagram of a server provided in an embodiment of this application;

[0030] Figure 9 This is a structural diagram of a terminal provided in an embodiment of this application. Detailed Implementation

[0031] The embodiments of this application will now be described with reference to the accompanying drawings.

[0032] Currently, to enable team-up between multiple accounts in each of the application's multiple service regions, a team-up process is deployed in each service region to handle the team-up functionality between multiple accounts within that service region. However, when multiple accounts in different service regions across multiple service regions have a need to team up, the team-up process in each service region cannot handle the team-up functionality between multiple accounts in different service regions. For example, in a game with multiple service regions, each service region deploys a team-up process to handle the team-up functionality between multiple player accounts within that service region. However, when multiple player accounts in different service regions across multiple service regions have a need to team up, the team-up process in each service region cannot handle the team-up functionality between multiple player accounts in different service regions.

[0033] This application provides a method for cross-region team formation. For cases where a first account belongs to a first service region and a second account belongs to a second service region (different from the first and second service regions), a cross-region team formation process is deployed in a service region different from both the first and second service regions. This process handles team formation functionality between multiple accounts in different service regions. A cross-region team belonging to the first account is created through this process. When the second account sends a join request to the process, the request is forwarded to the first account. When the first account sends an acceptance request, the process adds the second account to the team based on that acceptance request. In this method, the first account in the first service region creates a cross-region team through the process. Since the process handles team formation functionality between multiple accounts in different service regions, a second account in the second service region (different from the first service region) can join the team through this process, enabling multiple accounts in different service regions to form teams. Based on this, the process of forming a cross-region team sends the joining data of the second account in the cross-region team to the first world process belonging to the first service area, and sends the relevant data of the cross-region team to the second world process belonging to the second service area, so as to enable different service areas to clearly understand the team status of the cross-region team.

[0034] Next, the system architecture for cross-region team formation will be introduced. See [link / reference] Figure 1 ,Should Figure 1 This is a schematic diagram of a cross-regional team formation processing method provided in an embodiment of this application. The system includes a computer device 100, which is used to execute the cross-regional team formation processing method.

[0035] After computer device 100 creates a cross-region team belonging to the first account through the cross-region team formation process, if it receives a cross-region team join request sent by the second account through the cross-region team formation process, it sends a join request to the first account; the first account belongs to the first service area, the second account belongs to the second service area, the cross-region team formation process belongs to the cross-region service area, and the first service area, the second service area, and the cross-region service area are different.

[0036] As an example, the first account is account 1, the first service area is service area 1, the second account is account 2, and the second service area is service area 2; then, for the case where account 1 belongs to service area 1 and account 2 belongs to service area 2, and service area 1 and service area 2 are different, computer device 100 deploys a cross-regional team-up process in a cross-regional service area that is different from service area 1 and service area 1. The cross-regional team-up process creates a cross-regional team belonging to account 1. When account 2 sends a cross-regional team-up request to the cross-regional team-up process, the cross-regional team-up process forwards the request to account 1.

[0037] If computer device 100 receives a request for consent to join from the first account through the cross-regional team formation process, it adds the second account to the cross-regional team according to the request for consent.

[0038] As an example, based on the above example, when account 1 sends a consent request to the cross-regional team-up process to join the team, computer device 100 adds account 2 to the cross-regional team based on the consent request.

[0039] Computer device 100 sends the joining data of the second account in the cross-region team to the first world process through the cross-region team formation process, and sends the relevant data of the cross-region team to the second world process; the first world process belongs to the first service area, and the second world process belongs to the second service area.

[0040] As an example, based on the above example, the first world process is world process 1 and the second world process is world process 2; then the computer device 100 sends the joining data of account 2 in the cross-region team to world process 1 belonging to service area 1 through the cross-region team process, and sends the relevant data of the cross-region team to world process 2 belonging to service area 2.

[0041] In other words, when multiple accounts in different service areas have a need to form a team, a cross-regional team-up process is deployed in a cross-regional service area outside the different service areas to support the team-up function between multiple accounts in different service areas.

[0042] It should be noted that, in the embodiments of this application, the computer device can be a server or a terminal. The method provided in the embodiments of this application can be executed by the terminal or the server alone, or it can be executed by the terminal and the server in cooperation. Specifically, when the method provided in the embodiments of this application is executed by the terminal or the server alone, its execution method is similar to... Figure 1 The corresponding embodiments are similar, mainly replacing the computer device with a terminal or server. Furthermore, when the method provided in this application is executed by a terminal and a server, steps that need to be displayed on the front-end interface can be executed by the terminal, while steps that require background calculations and do not need to be displayed on the front-end interface can be executed by the server.

[0043] The terminal can be a smartphone, tablet, laptop, desktop computer, intelligent voice interaction device, vehicle terminal, extended reality device, or aircraft, but is not limited to these. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services, but is not limited to these. The terminal and server can be connected directly or indirectly through wired or wireless communication, and this application does not impose any restrictions. For example, the terminal and server can be connected through a network, which can be wired or wireless.

[0044] The method provided in this application embodiment can be applied to multiplayer online games, which are games that allow multiple players to participate simultaneously via an internet connection.

[0045] Next, the cross-regional team processing method provided in this application embodiment will be described in detail using a computer device executing the method provided in the embodiments of this application as an example, in conjunction with the accompanying drawings.

[0046] See Figure 2 ,Should Figure 2 The flowchart of a cross-regional team formation processing method provided in this application embodiment includes the following steps S201-S203.

[0047] S201: After creating a cross-region team belonging to the first account through the cross-region team-up process, if the cross-region team-up process receives a join request from the second account, a join request is sent to the first account; the first account belongs to the first service area, the second account belongs to the second service area, the cross-region team-up process belongs to the cross-region service area, and the first service area, the second service area, and the cross-region service area are different.

[0048] S202: If a request to join is received from the first account through the cross-region team formation process, the second account is added to the cross-region team according to the request to join.

[0049] In related technologies, each of the multiple service areas of an application deploys a team-up process to support the team-up function between multiple accounts in that service area. However, there is a team-up requirement between multiple accounts in different service areas, and the team-up process in each service area cannot support the team-up function between multiple accounts in different service areas.

[0050] In this embodiment, to address the aforementioned issues, a cross-regional service area can be added. A cross-regional team-up process is deployed in this service area, enabling team-up functionality between multiple accounts from different service areas. Specifically, after an account in one service area creates a cross-regional team through the cross-regional team-up process, an account in another service area can join that team via the same process. Therefore, for cases where the first account belongs to the first service area and the second account belongs to the second service area (which are different service areas), a cross-regional team-up process is deployed in a cross-regional service area that differs from both the first and second service areas. When a cross-regional team belonging to the first account is created through this process, and the second account sends a join request to the process, the process forwards the request to the first account. When the first account sends an acceptance request to the process, the process adds the second account to the cross-regional team based on that acceptance request.

[0051] Here, the first service area is a service area within the application, and the first account is an account within the first service area; the second service area is a service area within the application that is different from the first service area, and the second account is an account within the second service area; the cross-regional service area is a service area within the application that is different from the first and second service areas; the cross-regional team-up process is a process within the cross-regional service area that carries the team-up function between multiple accounts from different service areas; the cross-regional team is a team that can join multiple accounts from different service areas; the join request is a request from the second account to join the cross-regional team, which carries the team identifier of the cross-regional team and the account identifier of the second account; and the consent request is a request from the first account to consent to the second account joining the cross-regional team.

[0052] In the aforementioned steps S201-S202, where the first account belongs to the first service area and the second account belongs to the second service area (and the first and second service areas are different), a cross-regional service area, different from the first and second service areas, is added. A cross-regional team-up process is deployed in this cross-regional service area to support team-up functionality between multiple accounts in different service areas. The first account creates a cross-regional team through the cross-regional team-up process. When the second account sends a join request to the cross-regional team-up process, the process forwards the join request to the first account. When the first account sends an acceptance request to the cross-regional team-up process, the process adds the second account to the cross-regional team based on the acceptance request. This allows the first account in the first service area and the second account in the second service area to team up through the cross-regional team-up process, enabling multiple accounts in different service areas to team up through this process.

[0053] As an example of S201-S202, the first account is player account x, the first service area is service area A, the second account is player account y, and the second service area is service area B. Given that player account x belongs to service area A and player account y belongs to service area B (service areas A and B are different), the computer device deploys a cross-region team-up process in a cross-region service area that is different from both service areas A and B. This process creates a cross-region team belonging to player account x. When player account y sends a join request to the cross-region team-up process, the process forwards the join request to player account x. When player account x sends an acceptance request to the cross-region team-up process, the process adds player account y to the cross-region team based on that acceptance request.

[0054] S203: Send the joining data of the second account in the cross-region team to the first world process through the cross-region team formation process, and send the relevant data of the cross-region team to the second world process; the first world process belongs to the first server region, and the second world process belongs to the second server region.

[0055] In this embodiment, after executing S201-S202 (receiving a cross-region team joining request from a second account via the cross-region team formation process, sending a joining request to the first account, receiving an acceptance request from the first account, and adding the second account to the cross-region team based on the acceptance request), the first and second service areas need to clarify the team status of the cross-region team. For the first service area, since the first account has already created the cross-region team via the cross-region team formation process, and the first service area to which the first account belongs has clarified the team status before the second account was added to the cross-region team, the first service area needs to clarify the addition of the second account to the cross-region team. For the second service area, it needs to clarify the relevant data of the cross-region team. Therefore, the cross-region team formation process sends the joining data of the second account in the cross-region team to the first world process belonging to the first service area, and sends the relevant data of the cross-region team to the second world process belonging to the second service area. This allows the first world process to send the joining data of the second account in the cross-region team to each scene process and the first account in the first service area, and the second world process to send the relevant data of the cross-region team to each scene process and the second account in the second service area.

[0056] Among them, the first world process is the process that carries global management services in the first service area; the data on the addition of a second account in a cross-region team is the data on the addition of a second account in a cross-region team; the second world process is the process that carries global management services in the second service area; and the relevant data of cross-region teams represents the team status of cross-region teams.

[0057] In step S203, after adding a second account to the cross-region team created by the first account through the cross-region team formation process in steps S201-S202, the process sends the addition data of the second account in the cross-region team to the first world process belonging to the first service area, and sends the relevant data of the cross-region team to the second world process belonging to the second service area. This allows the first service area to be aware of the addition of the second account to the cross-region team, and the second service area to be aware of the relevant status of the cross-region team, thus enabling different service areas to be aware of the team status of the cross-region team.

[0058] As an example of S203, based on the example of S202 above, the first world process is world process A, and the second world process is world process B; then the computer device sends the joining data of player account y in the cross-region team to world process A belonging to service area A through the cross-region team process, and sends the relevant data of the cross-region team to world process B belonging to service area B.

[0059] As can be seen from the above technical solution, for situations where the first account belongs to the first service area and the second account belongs to the second service area, and the first and second service areas are different, a cross-regional team-up process is deployed in a cross-regional service area that is different from the first and second service areas. This cross-regional team-up process carries the team-up function between multiple accounts in different service areas. A cross-regional team belonging to the first account is created through the cross-regional team-up process. When the second account sends a join request to the cross-regional team-up process, the join request is forwarded to the first account through the cross-regional team-up process. When the first account sends an acceptance request to the cross-regional team-up process, the second account is added to the cross-regional team based on the acceptance request. In this way, the first account in the first service area creates a cross-regional team through the cross-regional team-up process. Based on the cross-regional team-up process carrying the team-up function between multiple accounts in different service areas, the second account in the second service area (different from the first service area) can join the cross-regional team through the cross-regional team-up process, enabling multiple accounts in different service areas to complete team-up through the cross-regional team-up process. Based on this, the method sends the joining data of the second account in the cross-region team to the first world process belonging to the first service region through the cross-region team formation process, and sends the relevant cross-region team data to the second world process belonging to the second service region, so that different service regions can clearly identify the team status of the cross-region team. Therefore, when there is a team formation need between multiple accounts in different service regions, this method deploys a cross-region team formation process in a cross-region service region outside the different service regions to support the team formation function between multiple accounts in different service regions.

[0060] In this embodiment of the application, when the above-mentioned S201 is executed, the specific implementation of receiving the cross-region team joining request sent by the second account through the cross-region team forming process is actually the second account sending the cross-region team joining request to the cross-region team forming process. Considering that the second account belongs to the second service area, which deploys the world process and the scene process, and the cross-region team forming process belongs to the cross-region service area, when the second account interacts with the cross-region team forming process, it needs to go through the scene process and the world process of the second service area in turn. Moreover, for the second account to send the cross-region team joining request, the world process of the second service area needs to check the status of the second account.

[0061] Therefore, the second account sending a cross-region team join request to the cross-region team formation process can be done in the following ways: the second account sends the join request to the second scene process of the second service area; the second scene process sends the join request to the second world process of the second service area; and when the second world process determines that the second account has passed the status check, the second world process sends the join request to the cross-region team formation process of the cross-region service area. Based on this, this application provides a possible implementation method in which the cross-region team join request sent by the second account is received through the cross-region team formation process in the above-mentioned S201, for example, it can include the following S201a-S201c (not shown in the figure).

[0062] S201a: Receives a join request sent by a second account through the second scenario process; the second scenario process belongs to the second service area.

[0063] S201b: Receive the join request sent by the second scenario process through the second world process.

[0064] S201c: If the second account passes the status check of the second world process, it receives the join request sent by the second world process through the cross-region team-up process.

[0065] Among them, the second scene process is the process that carries the scene in the second service area; the second account indicates that the second world process determines that the second account is in a state without a team through the status check of the second world process.

[0066] In the aforementioned S201a-S201c scenarios, where the second account belongs to the second service area, the cross-region team-up process belongs to the cross-region service area, and the interaction between the second account and the cross-region team-up process requires sequentially passing through the second scene process and the second world process of the second service area, the second account sequentially passes through the second scene process and the second world process. If the second world process checks the status of the second account and confirms that the second account does not belong to another team, it accurately sends a cross-region team join request to the cross-region team-up process. This ensures the data synchronization, consistency, and accuracy of the cross-region team join request sent by the second account across the second scene process, the second world process of the second service area, and the cross-region team-up process of the cross-region service area. This guarantees the security and stability of the second account's interaction with the cross-region team-up process to join a cross-region team.

[0067] As an example of S201a-S201c, based on the example of S201 above, the second scene process is scene process B; then the computer device receives the join request sent by player account y through scene process B of service area B; the computer device receives the join request sent by scene process B through world process B; if player account y passes the status check of world process B, the computer device receives the join request sent by world process B through cross-region team formation process.

[0068] In this embodiment of the application, when the specific implementation of sending the join request to the first account in S201 is executed, the join request of the cross-region team is actually forwarded to the first account through the cross-region team process. Considering that the cross-region team process belongs to the cross-region service area and the first account belongs to the first service area, the first service area deploys the world process and the scene process. When the cross-region team process interacts with the first account, it needs to go through the world process of the second service area at least.

[0069] Therefore, forwarding the cross-region team join request to the first account through the cross-region team formation process can be achieved by: sending the join request to the first world process of the first service region through the cross-region team formation process; or sending the join request to the first account through the first world process. Based on this, this application provides a possible implementation method, in which sending the join request to the first account in S201 above can, for example, include the following S201d-S201c (not shown in the figure).

[0070] S201d: Send a join request to the first-world process via the cross-region team-up process.

[0071] S201e: Send a join request to the first account via the first world process.

[0072] In cases where the cross-region team-up process belongs to a cross-region service area, the first account belongs to the first service area, and the cross-region team-up process needs to interact with the first account through at least the first world process of the first service area, the cross-region team-up process accurately forwards the aforementioned join request to the first account through the first world process. This ensures the data synchronization, consistency, and accuracy between the cross-region team-up process in the cross-region service area and the first world process in the first service area regarding the cross-region team join request sent by the second account. This, in turn, guarantees the security and stability of the cross-region team-up process interacting with the first account to forward the cross-region team join request of the second account.

[0073] As an example of S201d-S201c, based on the example of S201 above, the computer device sends the above-mentioned join request to the world process A through the cross-region team-up process; and sends the join request to the player account x through the world process A.

[0074] In this embodiment of the application, when the above-mentioned S201 is executed, the first account sends the consent request for joining the first account to the cross-region team-up process. Considering that the first account belongs to the first service area, which deploys the world process and the scene process, and the cross-region team-up process belongs to the cross-region service area, when the first account interacts with the cross-region team-up process, it needs to go through the scene process and the world process of the first service area in turn.

[0075] Therefore, the first account sending the consent request for joining the cross-region team-up process can be done in the following ways: the first account sending the consent request to the first scene process of the first service area; sending the consent request to the first world process of the first service area through the first scene process; or sending the consent request to the cross-region team-up process of the cross-region service area through the first world process. Based on this, this application provides a possible implementation method in which the consent request for joining the first account sent by the cross-region team-up process in the above-mentioned S201 can, for example, include the following S201f-S201h (not shown in the figure).

[0076] S201f: Receives consent requests from the first account through the first scenario process; the first scenario process belongs to the first service area.

[0077] S201g: Receives the consent request sent by the first scenario process through the first world process.

[0078] S201h: Receives consent requests from first-world processes via cross-regional team formation processes.

[0079] Among them, the first scenario process is the process that carries the scenario in the first service area.

[0080] In the aforementioned S201f-S201h, where the first account belongs to the first service area, the cross-region team-up process belongs to the cross-region service area, and the interaction between the first account and the cross-region team-up process requires sequentially going through the first scene process and the first world process of the first service area, the first account sequentially and accurately sends the aforementioned consent request for joining to the cross-region team-up process through the first scene process and the first world process. This ensures the data synchronization, data consistency, and data accuracy of the consent request for joining sent by the first account in the first scene process and the first world process of the first service area, as well as the cross-region team-up process of the cross-region service area. This, in turn, guarantees the security and stability of the first requesting account's interaction with the cross-region team-up process to agree to the second account joining the cross-region team.

[0081] As an example of S201f-S201h, based on the example of S201 above, the first scene process is scene process A; then the computer device receives the consent request sent by player account x through scene process A of service area A; the computer device receives the consent request sent by scene process A through world process A; the computer device receives the consent request sent by world process A through cross-region team process.

[0082] See Figure 3 ,Should Figure 3 This is a schematic diagram illustrating the deployment of a team process, a world process, and a scene process in a service area, as provided in an embodiment of this application. Based on the above example, Figure 3In the middle (a), it means that the service area A deploys the team process A, the world process A, and the scene process A. The team process A carries the team function between multiple player accounts in the service area A. Figure 3 (b) indicates that Service B deploys the team process B, world process B, and scene process B. The team process B carries the team-up function between multiple player accounts in Service B. Figure 3 (c) indicates that cross-region service areas deploy cross-region team-up processes, cross-region world processes, and cross-region scene processes. The cross-region team-up process carries the team-up function between multiple player accounts in different regions, such as the team-up function between multiple player accounts in service area A and service area B. In addition, cross-region service areas deploy cross-region recruitment processes to carry the recruitment function of cross-region teams.

[0083] In this embodiment, when the second account is the first account to join a cross-region team in the second service area, it indicates that the second service area does not have any cross-region team data. In this case, the full data of the cross-region team needs to be sent to the second world process belonging to the second service area through the cross-region team formation process. When the second account is the Mth account to join a cross-region team in the second service area, where M is a positive integer and M≥2, it indicates that the second service area already has cross-region team data before the second account joins the cross-region team. In this case, the joining data of the second account in the cross-region team needs to be sent to the second world process belonging to the second service area through the cross-region team formation process. Based on this, this application provides a possible implementation: if the second account is the first account to join a cross-region team in the second service area, the relevant data of the cross-region team is the full data of the cross-region team; if the second account is the Mth account to join a cross-region team in the second service area, the relevant data of the cross-region team is the joining data of the second account in the cross-region team; M is a positive integer and M≥2.

[0084] Among them, the full data of cross-region teams is all the data of cross-region teams.

[0085] In this method, if the second account is the first account to join a cross-region team in the second service area, the second service area does not know any data about the cross-region team. Instead, it sends all the data of the cross-region team to the second world process belonging to the second service area through the cross-region team formation process, so that the second service area knows the full status of the cross-region team. If the second account is not the first account to join a cross-region team in the second service area, the second service area already knows the status of the team before the second account joined. Instead, it sends the joining data of the second account in the cross-region team to the second world process belonging to the second service area through the cross-region team formation process, so that the second service area knows that the second account has joined the cross-region team.

[0086] As an example, based on the example of S203 above, when player account y is the first account to join a cross-region team in server B, the relevant data of the cross-region team is the full data of the cross-region team, that is, the computer device sends the full data of the cross-region team to the world process B belonging to server B through the cross-region team formation process; when player account y is the Mth account to join a cross-region team in server B, where M is a positive integer and M≥2, the relevant data of the cross-region team is the joining data of player account y in the cross-region team, that is, the computer device sends the joining data of player account y in the cross-region team to the world process B belonging to server B through the cross-region team formation process.

[0087] See Figure 4 ,Should Figure 4 This illustration shows how a second account is added to a cross-region team based on a cross-region team join request sent by a second account, as provided in this application embodiment. Building upon the above example, service A deploys world process A and scene process A, service B deploys world process B and scene process B, and the cross-region service deploys a cross-region team join process. First, player account y sends a cross-region team join request to scene process B. Scene process B then sends the join request to world process B. When world process B determines that player account y has passed the status check, it sends the join request to the cross-region team join process. The cross-region team join process then sends the join request to world process A, which in turn sends it to player account x. Next, player account x sends an acceptance request to scene process A, which in turn sends the acceptance request to world process A. World process A then sends the acceptance request to the cross-region team join process, which, based on the acceptance request, adds player account y to the cross-region team. Finally, the cross-region team-up process sends the joining data of player account y in the cross-region team to world process A; when player account y is the first account to join the cross-region team in server B, the cross-region team-up process sends the full data of the cross-region team to world process B; when player account y is the Mth account to join the cross-region team in server B, where M is a positive integer and M≥2, the cross-region team-up process sends the joining data of player account y in the cross-region team to world process B. In addition, server A deploys team-up process A, server B deploys team-up process B, and the cross-region service deploys the cross-region world process, cross-region scene process, and cross-region recruitment process. Player account y sees the cross-region team's profile data through the cross-region recruitment process and sends a joining request to the scene process B.

[0088] In this embodiment, when implementing the specific implementation of creating a cross-region team belonging to the first account through the cross-region team-up process in S201, the cross-region team is actually created by the cross-region team-up process based on the creation request when the first account sends a cross-region team creation request to the cross-region team-up process. Furthermore, the first service area needs to clarify the team status of the cross-region team. Since the first service area does not have any cross-region team data, in this case, it is necessary to send the full data of the cross-region team to the first world process belonging to the first service area through the cross-region team-up process, so that the first world process can send the full data of the cross-region team to each scene process and the first account in the first service area. Based on this, this application provides a possible implementation method. The creation of a cross-region team belonging to the first account through the cross-region team-up process in S201 may include, for example, the following S1-S2 (not shown in the figure).

[0089] S1: If a cross-region team creation request is received from the first account through the cross-region team formation process, a cross-region team is created according to the creation request.

[0090] S2: Send the full data of cross-region teams to the first-world process through the cross-region team formation process.

[0091] Among them, the creation request is the request from the first account to create a cross-region team.

[0092] When the first account sends a cross-region team creation request to the cross-region team formation process, the cross-region team formation process creates a cross-region team based on the creation request. This enables the first account in the first service area to create a cross-region team through the cross-region team formation process, laying the foundation for multiple accounts in different service areas to form teams through the cross-region team formation process in the future.

[0093] As an example of S1-S2, based on the example of S201 above, when player account x sends a cross-region team creation request to the cross-region team creation process, the computer device creates a cross-region team based on the creation request through the cross-region team creation process; the computer device sends the full data of the cross-region team to the world process A belonging to server A through the cross-region team creation process.

[0094] In this embodiment of the application, when the specific implementation of receiving the cross-region team creation request sent by the first account through the cross-region team formation process in S1 is executed, the first account actually sends the cross-region team creation request to the cross-region team formation process. Considering that the first account belongs to the first service area, which deploys the world process and the scene process, and the cross-region team formation process belongs to the cross-region service area, when the first account interacts with the cross-region team formation process, it needs to go through the scene process and the world process of the first service area in turn. Moreover, for the first account to issue the cross-region team creation request, the world process of the first service area needs to check the status of the first account.

[0095] Therefore, the first account sending a cross-region team creation request to the cross-region team formation process can be done in the following ways: the first account sends the creation request to the first scene process of the first service region; the first scene process sends the creation request to the first world process of the first service region; and when the first world process determines that the first account has passed the status check, the first world process sends the creation request to the cross-region team formation process of the cross-region service region. Based on this, this application provides a possible implementation, where S1 may include, for example, the following S1a-S1c (not shown in the figure).

[0096] S1a: Receives the creation request sent by the first account through the first scenario process; the first scenario process belongs to the first service area.

[0097] S1b: Receives the creation request sent by the first scenario process through the first world process.

[0098] S1c: If the first account passes the status check of the first world process, it receives the creation request sent by the first world process through the cross-region team process.

[0099] Among them, the first scenario process is the process that carries the scenario in the first service area.

[0100] In the aforementioned S1a-S1c scenarios, where the first account belongs to the first service area, the cross-region team-up process belongs to the cross-region service area, and the interaction between the first account and the cross-region team-up process requires sequentially passing through the first scene process and the first world process of the first service area, the first account sequentially passes through the first scene process and the first world process. When the first world process checks the status of the first account and determines that the first account can create a team, it accurately sends a cross-region team creation request to the cross-region team-up process. This ensures the data synchronization, data consistency, and data accuracy of the first scene process and the first world process of the first service area, as well as the cross-region team-up process of the cross-region service area, in the cross-region team creation request sent by the first account. This, in turn, guarantees the security and stability of the first account's interaction with the cross-region team-up process to create a cross-region team.

[0101] As an example of S1a-S1c, based on the examples of S1-S2 above, the first scene process of the computer device is scene process A; then the computer device receives the creation request sent by player account x through scene process A of service area A; the computer device receives the creation request sent by scene process A through world process A; if player account x passes the status check of world process A, the computer device receives the creation request sent by world process A through cross-region team process.

[0102] In this embodiment, considering the existence of different cross-region team-up processes forming a cross-region team-up process set to reduce the team-up load of a single cross-region team-up process, the cross-region team-up process in S1c is determined by the first world process from the cross-region team-up process set. For example, the first world process selects a cross-region team-up process from the cross-region team-up process set according to the account identifier of the first account, or the first world process selects a cross-region team-up process from the cross-region team-up process set sequentially, or the first world process randomly selects a cross-region team-up process from the cross-region team-up process set. Based on this, this application provides a possible implementation method, and the step of determining the cross-region team-up process may include, for example, the following S3 (not shown in the figure) or S4 (not shown in the figure).

[0103] S3: Determine the cross-region team formation process from the cross-region team formation process set based on the account identifier of the first account through the first world process.

[0104] S4: Determine the cross-region team formation process sequentially from the cross-region team formation process set through the first world process.

[0105] The account identifier for the first account is used to uniquely identify the first account.

[0106] In practical applications, determining the cross-region team formation process from the cross-region team formation process set by the first world process based on the account identifier of the first account can be done by determining the cross-region team formation process from the cross-region team formation process set by the first world process based on the remainder between the account identifier of the first account and the number of processes in the cross-region team formation process set.

[0107] The aforementioned S3 first-world process selects cross-region team-up processes from the cross-region team-up process set according to the account identifier of the first account, so that the cross-region team-up processes are related to the account identifier of the first account, and the first account interacts with a fixed cross-region team-up process. This method can not only balance the team-up load of different cross-region team-up processes in the cross-region team-up process set, but also ensure that the same account interacts with the same cross-region team-up process in the cross-region team-up process set. The aforementioned S4 first-world process selects cross-region team-up processes from the cross-region team-up process set in sequence, so that different cross-region team-up processes in the cross-region team-up process set can be selected evenly. This method can better balance the team-up load of different cross-region team-up processes in the cross-region team-up process set.

[0108] As an example of S3, based on the above example, the computer device determines the cross-region team-up process from the cross-region team-up process set according to the account identifier of player account x through world process A. As an example of S4, based on the above example, the computer device determines the cross-region team-up process sequentially from the cross-region team-up process set through world process A.

[0109] See Figure 5 ,Should Figure 5This is a schematic diagram illustrating how a cross-region team creation process creates a cross-region team based on a cross-region team creation request sent by a first account, as provided in this application embodiment. Building upon the above example, service A deploys world process A and scene process A, service B deploys world process B and scene process B, and the cross-region service area deploys a cross-region team creation process. First, player account x sends a cross-region team creation request to scene process B, which then sends the request to world process B. When world process B determines that player account x has passed the status check, it determines a cross-region team creation process from the cross-region team creation process set according to player account x's account identifier and sends the creation request to that process. Then, the cross-region team creation process creates the cross-region team based on the creation request. Finally, the cross-region team creation process sends all the cross-region team's data to world process A. In addition, service area A deploys team formation process A, service area B deploys team formation process B, and cross-region service areas deploy cross-region world process, cross-region scene process, and cross-region recruitment process. The cross-region team formation process sends the cross-region team's profile data to the cross-region recruitment process so that other player accounts in service area B can see the cross-region team's profile data through the cross-region recruitment process.

[0110] Furthermore, in this embodiment, after the second account joins a cross-region team through the cross-region team-up process, the second account can also leave the cross-region team through the same process. When the second account sends a leave request to the cross-region team-up process, the cross-region team-up process removes the second account from the cross-region team based on the leave request. If the first and second service areas have already determined the team status of the second account joining the cross-region team, and if they also need to determine the second account leaving the cross-region team, the cross-region team-up process sends the leave data of the second account in the cross-region team to both the first and second world processes. This allows the first world process to send the leave data of the second account in the cross-region team to each scene process and the first account in the first service area, and the second world process to send the leave data of the second account in the cross-region team to each scene process and the second account in the second service area. Based on this, this application provides a possible implementation, and the method may further include S5-S6 (not shown in the figure).

[0111] S5: If a leave request for the cross-region team is received from a second account during the cross-region team formation process, the second account is removed from the cross-region team according to the leave request.

[0112] S6: Send the departure data of the second account in the cross-region team to the first world process and the second world process through the cross-region team formation process.

[0113] Among them, the leave request is the request of the second account to leave the cross-region team; the leave data of the second account in the cross-region team is the data of the second account leaving the cross-region team.

[0114] When the second account sends a request to leave the cross-region team to the cross-region team formation process, the cross-region team formation process removes the second account from the cross-region team based on the request. This allows the second account in the second service area to leave the cross-region team created by the first account in the first service area through the cross-region team formation process. In other words, after multiple accounts in different service areas complete the team formation through the cross-region team formation process, the accounts in the cross-region team can leave the team.

[0115] As an example of S5-S6, based on the example of S203 above, when player account y sends a request to leave the cross-region team to the cross-region team process, the computer device removes player account y from the cross-region team based on the request; the computer device sends the departure data of player account y in the cross-region team to world process A and world process B through the cross-region team process.

[0116] In this embodiment of the application, when the specific implementation of receiving the cross-region team departure request sent by the second account through the cross-region team formation process in the above-mentioned S5 is executed, the second account actually sends the cross-region team departure request to the cross-region team formation process. Considering that the second account belongs to the second service area, which deploys the world process and the scene process, and the cross-region team formation process belongs to the cross-region service area, when the second account interacts with the cross-region team formation process, it needs to go through the scene process and the world process of the second service area in sequence.

[0117] Therefore, the second account sending a cross-region team departure request to the cross-region team formation process can be done in the following ways: the second account sends the departure request to the second scene process of the second service area; the second scene process sends the departure request to the second world process of the second service area; or the second world process sends the departure request to the cross-region team formation process of the cross-region service area. Based on this, this application provides a possible implementation method in which the cross-region team formation process receives the cross-region team departure request sent by the second account in the above S5, for example, it can include the following S5a-S5c (not shown in the figure).

[0118] S5a: Receives a leave request sent by the second account through the second scenario process; the second scenario process belongs to the second service area.

[0119] S5b: Receives the leave request sent by the second scenario process through the second world process.

[0120] S5c: Receives leave requests sent by the second-world process through the cross-region team process.

[0121] Among them, the second scenario process is the process that carries the scenario in the second service area.

[0122] In the aforementioned S5a-S5c scenario, where the second account belongs to the second service area, the cross-region team-up process belongs to the cross-region service area, and the interaction between the second account and the cross-region team-up process requires sequentially passing through the second scene process and the second world process of the second service area, the second account accurately sends the cross-region team leave request to the cross-region team-up process through the second scene process and the second world process in sequence. This ensures the data synchronization, data consistency, and data accuracy of the cross-region team leave request sent by the second account among the second scene process and the second world process of the second service area, as well as the cross-region team-up process of the cross-region service area. This, in turn, guarantees the security and stability of the second account's interaction with the cross-region team-up process to leave the cross-region team.

[0123] As an example of S5a-S5c, based on the example of S5 above, the second scene process is scene process B; then the computer device receives the leave request sent by player account y through scene process B of service area B; the computer device receives the leave request sent by scene process B through world process B; if player account y passes the status check of world process B, the computer device receives the leave request sent by world process B through cross-region team process.

[0124] Furthermore, in this embodiment, after executing S5-S6 (receiving the second account's leave request for the cross-region team through the cross-region team formation process), removing the second account from the cross-region team based on the leave request, and sending the second account's leave data to the first and second world processes, it is necessary to further determine whether the second account is the last account to leave the cross-region team in the second service area. If so, it means that the second service area no longer needs to clarify the team status of the cross-region team. In this case, it is necessary to delete the team data of the cross-region team in the second world process belonging to the second service area. Based on this, this application provides a possible implementation method, which may also include S7 (not shown in the figure): if the second account is the last account to leave the cross-region team in the second service area, delete the team data of the cross-region team in the second world process.

[0125] In the case that the second account is the last account to leave the cross-region team in the second service area, the second service area no longer needs to clarify the team status of the cross-region team and delete the team data of the cross-region team in the second world process, so as to reduce the memory occupation of the team data of the cross-region team in the second service area.

[0126] As an example of S7, based on the examples of S5-S6 above, when player account x is the last account to leave the cross-region team in server B, the computer device deletes the team data of the cross-region team belonging to server B in world process B.

[0127] See Figure 6 ,Should Figure 6This illustration shows a method for removing a second account from a cross-region team based on a leave request sent by the second account, as provided in an embodiment of this application. Figure 4 Building upon the example above, firstly, player account y sends a request to leave the cross-server team to scene process B. Scene process B then sends this request to world process B, which in turn sends it to the cross-server team formation process. Based on this request, the cross-server team formation process removes player account y from the cross-server team. Next, the cross-server team formation process sends the departure data of player account y from the cross-server team to world process A and world process B. Furthermore, when player account y is the last account to leave the cross-server team in server B, the team data for the cross-server team is deleted from world process B.

[0128] Furthermore, in this embodiment, considering the potential anomalies in the cross-region team-up process, both the first-world process and the second-world process need to determine whether the cross-region team-up process is abnormal. Based on the existence of heartbeat packets between the cross-region team-up process and the first-world process, and between the cross-region team-up process and the second-world process, if the first-world process does not receive a heartbeat packet from the cross-region team-up process within a certain time period, it indicates that the cross-region team-up process is abnormal and unable to send a heartbeat packet to the first-world process. Similarly, if the second-world process does not receive a heartbeat packet from the cross-region team-up process within a certain time period, it indicates that the cross-region team-up process is abnormal and unable to send a heartbeat packet to the second-world process. In this case, the cross-region team-up process needs to be deleted from the cross-region team-up process set to prevent other accounts from creating cross-region teams through the cross-region team-up process, which could lead to anomalies.

[0129] To further consider the potential packet loss between the cross-region team formation process and the first-world and second-world processes, and based on the need for both the first and second service areas to clearly define the team status of cross-region teams, the following measures are taken: First, either the first-world or second-world process needs to send a detection packet for the cross-region team to the cross-region team formation process to determine if the cross-region team still exists. If not, the team data for the cross-region team in both the first and second-world processes is deleted. Second, the first-world process needs to send the first set of identifiers for existing objects in the cross-region team to the cross-region team formation process, and determine if the first set of identifiers matches the existing set of identifiers for existing objects in the cross-region team stored by the cross-region team formation process. If they do not match, the team data for the cross-region team in the second-world process is updated according to the existing set of identifiers. Alternatively, the second-world process needs to send the second set of identifiers for existing objects in the cross-region team to the cross-region team formation process, and determine if the second set of identifiers matches the existing set of identifiers for existing objects in the cross-region team stored by the cross-region team formation process. If they do not match, the team data for the cross-region team in the second-world process is updated according to the existing set of identifiers. This avoids inconsistencies in the data status of cross-region teams in the cross-region team formation process, the first-world process, and the second-world process.

[0130] Based on this, this application provides a possible implementation method, which may further include one or more of the following S8 (not shown in the figure), S9 (not shown in the figure), S10 (not shown in the figure), or S11 (not shown in the figure).

[0131] S8: If the first-world process or the second-world process does not receive a heartbeat packet from the cross-region team process within the first time period, it is determined that there is an anomaly in the cross-region team process.

[0132] S9: If the cross-region team does not exist, the team data of the cross-region team is deleted from the first world process or the second world process if the cross-region team detection packet received through the cross-region team formation process is determined.

[0133] S10: If the first identifier set of existing objects in the cross-region team is received by the cross-region team formation process from the first world process, and the first identifier set is inconsistent with the existing identifier set of existing objects in the cross-region team stored in the cross-region team formation process, update the team data of the cross-region team in the first world process according to the existing identifier set.

[0134] S11: If the second identifier set of existing objects in the cross-region team is received from the second world process through the cross-region team formation process, and the second identifier set is inconsistent with the existing identifier set, update the team data of the cross-region team in the second world process according to the existing identifier set.

[0135] Among them, the heartbeat packet sent by the cross-region team formation process is used to determine whether the cross-region team formation process is running normally; the cross-region team detection packet sent by the first-world process or the second-world process is used to determine whether there is a cross-region team in the cross-region team formation process; the first identifier set of existing objects in the cross-region team is used to identify existing objects in the cross-region team in the first-world process; the existing identifier set of existing objects in the cross-region team identifies existing objects in the cross-region team in the cross-region team formation process; and the second identifier set of existing objects in the cross-region team is used to identify existing objects in the cross-region team in the second-world process.

[0136] The S8 mechanism determines that the cross-region team-up process is abnormal when the first-world process or the second-world process does not receive a heartbeat packet from the cross-region team-up process within the first time period. This mechanism can detect abnormalities in the cross-region team-up process in a relatively timely manner, preventing other accounts from continuing to interact abnormally with the cross-region team-up process.

[0137] When the above-mentioned S9 determines that the cross-regional team does not exist through the detection packet of the cross-regional team sent by the first world process or the second world process received through the cross-regional team formation process, it means that the data status of the cross-regional team is inconsistent in the cross-regional team formation process, the first world process and the second world process. The team data of the cross-regional team in the first world process and the second world process is deleted to make the data status of the cross-regional team in the first world process and the second world process consistent with the data status of the cross-regional team in the cross-regional team formation process.

[0138] In step S10 above, if the first identifier set of existing objects in the cross-region team received by the first world process through the cross-region team formation process is inconsistent with the existing identifier set of existing objects in the cross-region team stored in the cross-region team formation process, it indicates that the team data of the cross-region team in the cross-region team formation process is inconsistent with the team data of the cross-region team in the first world process. The team data of the cross-region team in the first world process is updated according to the existing identifier set so that the data state of the cross-region team in the first world process is consistent with the data state of the cross-region team in the cross-region team formation process.

[0139] In step S11 above, if the second identifier set of existing objects in the cross-region team received by the second world process through the cross-region team formation process is inconsistent with the existing identifier set of existing objects in the cross-region team stored in the cross-region team formation process, it indicates that the team data of the cross-region team in the cross-region team formation process is inconsistent with the team data of the cross-region team in the second world process. The team data of the cross-region team in the second world process is updated according to the existing identifier set so that the data state of the cross-region team in the second world process is consistent with the data state of the cross-region team in the cross-region team formation process.

[0140] As an example of S8, based on the above example, if the computer device does not receive a heartbeat packet sent by the cross-regional teaming process in world process A or world process B within the first time period, it is determined that there is an anomaly in the cross-regional teaming process.

[0141] As an example of S9, based on the above example, the computer device determines that the cross-regional team does not exist by receiving a cross-regional team detection packet sent by world process A or world process B through the cross-regional team formation process, and deletes the team data of the cross-regional team in world process A and world process B.

[0142] As an example of S10, based on the above example, the computer device receives a first set of identifiers of existing objects in the cross-regional team sent by the world process A through the cross-regional teaming process, and the first set of identifiers is inconsistent with the existing set of identifiers of existing objects in the cross-regional team stored by the cross-regional teaming process, and updates the team data of the cross-regional team in the world process A according to the existing set of identifiers.

[0143] As an example of S11, based on the above example, the computer device receives a second set of identifiers of existing objects in the cross-regional team sent by the world process B through the cross-regional teaming process, and the second set of identifiers is inconsistent with the existing set of identifiers of existing objects in the cross-regional team stored by the cross-regional teaming process, and updates the team data of the cross-regional team in the world process B according to the existing set of identifiers.

[0144] Furthermore, in this embodiment, since different cross-region teaming processes form a cross-region teaming process set to reduce the teaming load of a single cross-region teaming process, and considering that the teaming load of a cross-region teaming process cannot be too high, the number of processes in the cross-region teaming process set to which the cross-region teaming process belongs is adjusted according to the teaming load of the cross-region teaming process, further avoiding excessively high teaming load for the cross-region teaming process. Based on this, this application provides a possible implementation, and the method may further include, for example, S12 (not shown in the figure): adjusting the number of processes in the cross-region teaming process set to which the cross-region teaming process belongs according to the teaming load of the cross-region teaming process.

[0145] Among them, the team load of the cross-region team formation process is the team formation pressure and burden among multiple accounts carried by the cross-region team formation process.

[0146] The above-mentioned S12 dynamically adjusts the number of processes in the cross-regional teaming process set to which the cross-regional teaming process belongs according to the teaming load of the cross-regional teaming process. For example, when the teaming load of the cross-regional teaming process is high, the number of processes in the cross-regional teaming process set to which the cross-regional teaming process belongs is increased. For the parallel expansion of the cross-regional teaming process, the teaming load of the cross-regional teaming process can be avoided from being too high.

[0147] In summary, the cross-server team-up processing method provided in this application embodiment allows multiple player accounts in different service regions of a game to freely team up and participate in cross-server gameplay, improving interaction and communication between these accounts. Furthermore, when the cross-server team-up process encounters an anomaly, the team-up process deployed in each service region can still function normally, ensuring compatibility between multiple accounts in each service region to freely team up and participate in local gameplay, thus increasing the robustness of interaction and communication between multiple player accounts within the same service region. Therefore, the cross-server team-up processing method provided in this application embodiment offers good robustness and scalability for free team-up between multiple player accounts in multiple service regions of a game.

[0148] It should be noted that, based on the implementation methods provided in the above aspects, this application can be further combined to provide more implementation methods.

[0149] based on Figure 2 Corresponding to the cross-region team-up processing method provided in the embodiments, this application also provides a cross-region team-up processing device, see [link to relevant documentation]. Figure 7 ,Should Figure 7 This is a structural diagram of a cross-regional team-up processing device provided in an embodiment of the present application. The cross-regional team-up processing device 700 includes: a sending unit 701 and a joining unit 702.

[0150] The sending unit 701 is used to send a join request to the first account after creating a cross-region team belonging to the first account through the cross-region team-up process, if it receives a join request for the cross-region team sent by the second account through the cross-region team-up process; the first account belongs to the first service area, the second account belongs to the second service area, the cross-region team-up process belongs to the cross-region service area, and the first service area, the second service area, and the cross-region service area are different;

[0151] The joining unit 702 is used to add a second account to the cross-region team if it receives an agreement request for the joining request sent by the first account through the cross-region team forming process;

[0152] The sending unit 701 is also used to send the joining data of the second account in the cross-region team to the first world process through the cross-region team process, and to send the relevant data of the cross-region team to the second world process; the first world process belongs to the first service area, and the second world process belongs to the second service area.

[0153] In one possible implementation, the device further includes: a receiving unit;

[0154] The receiving unit is used for:

[0155] The second scenario process receives the join request sent by the second account; the second scenario process belongs to the second service area;

[0156] Receive the join request sent by the second scene process through the second world process;

[0157] If the second account passes the status check of the second world process, it will receive the join request sent by the second world process through the cross-region team-up process.

[0158] In one possible implementation, the device further includes: a receiving unit;

[0159] Transmitting unit 701, used for:

[0160] Send a join request to the first world process through the cross-region team formation process;

[0161] Send a join request to the first account via the first world process;

[0162] The receiving unit is used for:

[0163] The consent request sent by the first account is received through the first scenario process; the first scenario process belongs to the first service area;

[0164] Receive consent requests sent by the first scenario process through the first world process;

[0165] Receive consent requests sent by the first-world process through the cross-regional team formation process.

[0166] In one possible implementation, if the second account is the first account to join a cross-region team in the second service area, the relevant data of the cross-region team is the full data of the cross-region team; if the second account is the Mth account to join a cross-region team in the second service area, the relevant data of the cross-region team is the data of the second account joining the cross-region team; M is a positive integer, M≥2.

[0167] In one possible implementation, the apparatus further includes: a creation unit;

[0168] The creation unit is used to create a cross-region team if it receives a cross-region team creation request from the first account through the cross-region team formation process;

[0169] The sending unit 701 is also used to send the full data of the cross-region team to the first-world process through the cross-region team formation process.

[0170] In one possible implementation, the device further includes: a receiving unit;

[0171] The receiving unit is used for:

[0172] The first scenario process receives the creation request sent by the first account; the first scenario process belongs to the first service area.

[0173] Receive the creation request sent by the first scenario process through the first world process;

[0174] If the first account passes the status check of the first world process, it receives the creation request sent by the first world process through the cross-region team formation process.

[0175] In one possible implementation, the apparatus further includes: a determining unit;

[0176] The determining unit is used to determine the cross-region team-up process from the cross-region team-up process set based on the account identifier of the first account through the first world process; or,

[0177] The cross-region team formation process is determined sequentially from the cross-region team formation process set through the first world process.

[0178] In one possible implementation, the device further includes: a removal unit;

[0179] The removal unit is used to remove the second account from the cross-region team if a leave request for the cross-region team is received from the second account through the cross-region team formation process;

[0180] The sending unit 701 is also used to send the departure data of the second account in the cross-region team to the first world process and the second world process through the cross-region team process.

[0181] In one possible implementation, the apparatus further includes: a deletion unit;

[0182] The deletion unit is used to delete the team data of the cross-region team in the second world process if the second account is the last account to leave the cross-region team in the second service area.

[0183] In one possible implementation, the apparatus further includes: a determining unit;

[0184] Determine the unit, for one or more of the following:

[0185] If the first-world process or the second-world process does not receive a heartbeat packet from the cross-regional team-up process within the first time period, it is determined that there is an anomaly in the cross-regional team-up process.

[0186] If the cross-region team is determined not to exist by the detection packet of the cross-region team received by the first world process or the second world process, delete the team data of the cross-region team in the first world process and the second world process.

[0187] If the first set of identifiers of existing objects in the cross-region team is received by the cross-region team formation process from the first world process, and the first set of identifiers is inconsistent with the existing set of identifiers of existing objects in the cross-region team stored in the cross-region team formation process, the team data of the cross-region team in the first world process is updated according to the existing set of identifiers.

[0188] If the second identifier set of existing objects in the cross-region team is received from the second world process through the cross-region team formation process, and the second identifier set is inconsistent with the existing identifier set, the team data of the cross-region team in the second world process is updated according to the existing identifier set.

[0189] In one possible implementation, the device further includes: an adjustment unit;

[0190] The adjustment unit is used to adjust the number of processes in the cross-regional queuing process set to which the cross-regional queuing process belongs based on the queuing load of the cross-regional queuing process.

[0191] As can be seen from the above technical solution, for situations where the first account belongs to the first service area and the second account belongs to the second service area, and the first and second service areas are different, a cross-regional team-up process is deployed in a cross-regional service area that is different from the first and second service areas. This cross-regional team-up process carries the team-up function between multiple accounts in different service areas. A cross-regional team belonging to the first account is created through the cross-regional team-up process. When the second account sends a join request to the cross-regional team-up process, the join request is forwarded to the first account through the cross-regional team-up process. When the first account sends an acceptance request to the cross-regional team-up process, the second account is added to the cross-regional team based on the acceptance request. The first account in the first service area creates a cross-regional team through the cross-regional team-up process. Based on the cross-regional team-up process carrying the team-up function between multiple accounts in different service areas, the second account in the second service area (different from the first service area) can join the cross-regional team through the cross-regional team-up process, enabling multiple accounts in different service areas to complete team-up through the cross-regional team-up process. Building upon this, the cross-region team-up process sends the joining data of the second account in the cross-region team to the first-world process belonging to the first service region, and sends the relevant cross-region team data to the second-world process belonging to the second service region, thus enabling different service regions to clearly identify the team status of the cross-region team. Based on this, when multiple accounts in different service regions have a team-up need, a cross-region team-up process is deployed in a cross-region service region outside the different service regions to support the team-up function between multiple accounts in different service regions.

[0192] This application also provides a computer device, which may be a server, see [link to previous document]. Figure 8 ,Should Figure 8This application provides a structural diagram of a server 800. The server 800 can vary significantly due to different configurations or performance characteristics. It may include one or more processors, such as a central processing unit (CPU) 822, and a memory 832, as well as one or more storage media 830 (e.g., one or more mass storage devices) for storing application programs 842 or data 844. The memory 832 and storage media 830 can be temporary or persistent storage. The program stored in the storage media 830 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the server. Furthermore, the CPU 822 may be configured to communicate with the storage media 830 and execute the series of instruction operations stored in the storage media 830 on the server 800.

[0193] Server 800 may also include one or more power supplies 826, one or more wired or wireless network interfaces 850, one or more input / output interfaces 858, and / or one or more operating systems 841, such as Windows Server. TM Mac OS X TM Unix TM Linux TM FreeBSD TM etc.

[0194] In this embodiment, the central processing unit 822 in the server 800 can execute the methods provided in the various optional implementations of the above embodiments.

[0195] The computer device provided in this application embodiment can also be a terminal, see [link to relevant documentation]. Figure 9 ,Should Figure 9 This is a structural diagram of a terminal provided in an embodiment of this application. Taking a smartphone as an example, the smartphone includes components such as a radio frequency (RF) circuit 910, a memory 920, an input unit 930, a display unit 940, a sensor 950, an audio circuit 960, a wireless Fidelity (WiFi) module 970, a processor 980, and a power supply 990. The input unit 930 may include a touch panel 931 and other input devices 932, the display unit 940 may include a display panel 941, and the audio circuit 960 may include a speaker 961 and a microphone 962. Those skilled in the art will understand that... Figure 9 The smartphone structure shown does not constitute a limitation on smartphones and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0196] The memory 920 can be used to store software programs and modules. The processor 980 executes various functions and data processing of the smartphone by running the software programs and modules stored in the memory 920. The memory 920 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created based on the use of the smartphone (such as audio data, phonebook, etc.). In addition, the memory 920 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0197] The processor 980 is the control center of the smartphone, connecting various parts of the smartphone via various interfaces and lines. It performs various functions and processes data by running or executing software programs and / or modules stored in the memory 920, and by accessing data stored in the memory 920. Optionally, the processor 980 may include one or more processing units; preferably, the processor 980 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 980.

[0198] In this embodiment, the processor 980 in the smartphone can execute the methods provided in the various optional implementations of the above embodiments.

[0199] According to one aspect of this application, a computer-readable storage medium is provided for storing a computer program that, when run on a computer device, causes the computer device to perform the methods provided in various optional implementations of the above embodiments.

[0200] According to one aspect of this application, a computer program product is provided, comprising a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to perform the methods provided in various optional implementations of the above embodiments.

[0201] The descriptions of the processes or structures corresponding to the above figures each have their own emphasis. For parts of a process or structure that are not described in detail, please refer to the relevant descriptions of other processes or structures.

[0202] The terms "first," "second," etc., used in this application's specification and the foregoing drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0203] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0204] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0205] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0206] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing computer programs, such as USB flash drives, portable hard drives, read-only memory (ROM), RAM, magnetic disks, or optical disks.

[0207] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0208] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for handling cross-regional team formation, characterized in that, The method includes: After creating a cross-region team belonging to the first account through the cross-region team-up process, if the cross-region team-up process receives a join request from the second account, the join request is sent to the first account; the first account belongs to the first service region, the second account belongs to the second service region, the cross-region team-up process belongs to the cross-region service region, and the first service region, the second service region, and the cross-region service region are different; If the first account receives an agreement request for joining the team through the cross-regional team formation process, the second account is added to the cross-regional team according to the agreement request; The cross-region team-up process sends the joining data of the second account in the cross-region team to the first world process, and sends the relevant data of the cross-region team to the second world process; the first world process belongs to the first service area, and the second world process belongs to the second service area.

2. The method according to claim 1, characterized in that, The step of receiving the cross-region team joining request sent by the second account through the cross-region team forming process includes: The second scenario process receives the join request sent by the second account; the second scenario process belongs to the second service area; The second world process receives the joining request sent by the second scene process; If the second account passes the status check of the second world process, it receives the join request sent by the second world process through the cross-region team-up process.

3. The method according to claim 1, characterized in that, Sending the join request to the first account includes: The join request is sent to the first world process through the cross-region team formation process; The join request is sent to the first account through the first world process; The step of receiving the consent request for joining the group sent by the first account through the cross-regional team-up process includes: The consent request sent by the first account is received through the first scenario process; the first scenario process belongs to the first service area; The consent request sent by the first scenario process is received through the first world process; The cross-regional team-up process receives the consent request sent by the first world process.

4. The method according to claim 1, characterized in that, If the second account is the first account to join the cross-region team in the second service area, the relevant data of the cross-region team is the full data of the cross-region team; If the second account is the Mth account that joins the cross-region team in the second service area, the relevant data of the cross-region team is the joining data of the second account in the cross-region team; M is a positive integer, M≥2.

5. The method according to claim 1, characterized in that, The process of creating a cross-region team belonging to the first account through cross-region team formation includes: If the cross-region team creation request sent by the first account is received through the cross-region team formation process, the cross-region team is created according to the creation request; The cross-region team formation process sends the full data of the cross-region team to the first world process.

6. The method according to claim 5, characterized in that, The step of receiving the cross-region team creation request sent by the first account through the cross-region team formation process includes: The first scenario process receives the creation request sent by the first account; the first scenario process belongs to the first service area; The first world process receives the creation request sent by the first scene process; If the first account passes the status check of the first world process, it receives the creation request sent by the first world process through the cross-region team-up process.

7. The method according to claim 6, characterized in that, The steps for determining the cross-regional team formation process include: The cross-region team-up process is determined from the cross-region team-up process set based on the account identifier of the first account through the first world process; or, The cross-region team formation process is determined sequentially from the cross-region team formation process set through the first world process.

8. The method according to claim 1, characterized in that, The method further includes: If a leave request for the cross-region team is received from the second account through the cross-region team formation process, the second account is removed from the cross-region team according to the leave request; The departure data of the second account in the cross-region team is sent to the first world process and the second world process through the cross-region team formation process.

9. The method according to claim 1, characterized in that, The method further includes: If the second account is the last account to leave the cross-region team in the second service area, delete the team data of the cross-region team in the second world process.

10. The method according to claim 1, characterized in that, The method also includes one or more of the following: If the first world process or the second world process does not receive a heartbeat packet sent by the cross-regional team-up process within the first time period, it is determined that the cross-regional team-up process is abnormal. If the detection packet of the cross-region team received by the cross-region team formation process and sent by the first world process or the second world process determines that the cross-region team does not exist, the team data of the cross-region team in the first world process and the second world process is deleted. If the first set of identifiers of existing objects in the cross-region team is received by the cross-region team formation process from the first world process, and the first set of identifiers is inconsistent with the existing set of identifiers of existing objects in the cross-region team stored by the cross-region team formation process, the team data of the cross-region team in the first world process is updated according to the existing set of identifiers. If the second identifier set of existing objects in the cross-region team is received by the second world process through the cross-region team formation process, and the second identifier set is inconsistent with the existing identifier set, the team data of the cross-region team in the second world process is updated according to the existing identifier set.

11. The method according to claim 1, characterized in that, The method further includes: Adjust the number of processes in the cross-regional teaming process set to which the cross-regional teaming process belongs based on the teaming load of the cross-regional teaming process.

12. A cross-regional team processing device, characterized in that, The device includes: a transmitting unit and a receiving unit; The sending unit is configured to, after creating a cross-region team belonging to the first account through the cross-region team-up process, if it receives a join request for the cross-region team from the second account through the cross-region team-up process, send the join request to the first account; the first account belongs to the first service area, the second account belongs to the second service area, the cross-region team-up process belongs to the cross-region service area, and the first service area, the second service area, and the cross-region service area are different; The joining unit is configured to, if it receives an agreement request for the joining request sent by the first account through the cross-regional team-up process, add the second account to the cross-regional team according to the agreement request; The sending unit is further configured to send the joining data of the second account in the cross-region team to the first world process through the cross-region team formation process, and send the relevant data of the cross-region team to the second world process; the first world process belongs to the first service area, and the second world process belongs to the second service area.

13. A computer device, characterized in that, The computer device includes a processor and memory: The memory is used to store computer programs and to transfer the computer programs to the processor; The processor is configured to execute the method according to any one of claims 1-11 according to instructions in the computer program.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer device, causes the computer device to perform the method according to any one of claims 1-11.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is run on a computer device, it causes the computer device to perform the method according to any one of claims 1-11.

Images