U.S. Pat. No. 9,149,725

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments of the disclosure, which are illustrated in the accompanying drawings.

FIG. 12shows an environment incorporating certain aspects of the present invention. As shown inFIG. 12, environment1200may include a terminal1204, a server1206, and the Internet1202. The terminal1204may access the server1206through the Internet1202for certain personalized services provided by the server1206. Although only one server1206and one terminal1204is shown in the environment1200, any number of terminals1204or servers1206may be included, and other devices may also be included.

The Internet1202may include any appropriate type of communication network for providing network connections to the terminal1204and server1206or among multiple terminals1204and servers1206. For example, Internet1202may include the Internet or other types of computer networks or telecommunication networks, either wired or wireless.

A terminal, as used herein, may refer to any appropriate user terminal with certain computing capabilities, such as a personal computer (PC), a work station computer, a server computer, a hand-held computing device (tablet), a smart phone or mobile phone, or any other user-side computing device. In certain embodiments, terminal1204may be a wireless terminal, such as a smart phone, a tablet computer, or a mobile phone, etc. Terminal1204may be implemented on any appropriate computing platform. For example, the terminal1204may run a browser or a gaming software program to play a computer game online with other players/terminals.

A server, as used herein, may refer one or more server computers configured to provide certain web server functionalities to provide certain team battle matching services. A server may also include one or more processors to execute computer programs in parallel.

FIG. 13shows a block diagram of an exemplary computer system1300capable of implementing the system for team battle matching (e.g., terminal, server, etc.).

As shown inFIG. 13, computer system1300may include a processor1302, a storage medium1304, a monitor1306, a communication module1308, a database1310, and peripherals1312. Certain devices may be omitted and other devices may be included.

Processor1302may include any appropriate processor or processors. Further, processor1302can include multiple cores for multi-thread or parallel processing. Storage medium1304may include memory modules, such as ROM, RAM, flash memory modules, and erasable and rewritable memory, and mass storages, such as CD-ROM, U-disk, and hard disk, etc. Storage medium1304may store computer programs for implementing various processes, when executed by processor1302.

Further, peripherals1312may include I/O devices such as keyboard and mouse, and communication module1308may include network devices for establishing connections through the communication network. Database1310may include one or more databases for storing certain data and for performing certain operations on the stored data, such as database searching.

In operation, terminal1204and/or server1206may implement a PVP team battle matching process to perform certain functions for team battle matching.FIG. 1illustrates a flow chart of an exemplary process for team battle matching consistent with the disclosed embodiments. As shown inFIG. 1, the process may include the following steps.

Step101: for all registered teams that participate in a battle, the teams of equal size are allocated to the same matching queue.

PVP is a type of multiplayer interactive conflict within a game between two or more live participants. The term ‘team’ refers to a participating group of players. The number of players in the registered teams that participate in the battle can be 1, 2, 4, etc. There is no limitation for the number of players in the teams in the present embodiment. For example, four teams are registered to participate in the battle. The number of players of team 1, team 2, team 3, and team 4 are 4, 3, 2 and 2, respectively.

Further, one or more matching queues are created for team battle matching, and each matching queue may contain one or more teams of equal size. In the above example, the four teams may be assigned into three matching queues, where queue 1 is allocated with team 1 (4 players); queue 2 is allocated with team 2 (3 players); and queue 3 is allocated with team 3 and team 4 (both with 2 players).

Step102: randomly selecting one team from a queue allocated for teams with the maximum number of players.

For another example, if there are total three queues, Queue 1 is allocated with team 1 with 4 players and team 2 with 4 players; Queue 2 is allocated with team 3 with 3 players; and Queue 3 is allocated with team 4 with 2 players. At this time, a team is selected from the queue allocated with the maximum number of teams, which may be team 1 or team 2 in Queue 1.

Step103: whether the number of players in the team is equal to a preset number is determined.

The preset number is the number of players required for each battle camp in a battle mode. For example, the preset number is 8 in an 8 vs.8 mode; and the preset number is 16 in a 16 vs.16 mode. The number of players of the team selected may then be obtained and compared with the preset number to determine whether the number of players of the selected team is equal to the preset number.

Step104: if the number of players in the team is equal to the preset number, the team is allocated to one battle camp.

For example, if the current battle is an 8 vs.8 mode, and if it is determined that the number of players of the selected team is 8, the selected team may be allocated as one camp in the 8 vs.8 mode, and the other camp is selected from the remainder teams according to the above described steps.

Thus, a team battle matching method is provided. For teams that participate in a battle, the teams of equal size are allocated to the same queue. Then, any one team is selected from the queue allocated with the teams with the maximum number of players. Further, whether the number of players in the team is equal to a preset number is determined. If the number of players in the team is equal to the preset number, the team is allocated to one battle camp. Compared with the existing methods, the method can reduce a false matching rate and improve efficiency of team battle matching.

FIG. 2illustrates a flow chart of another exemplary process of team battle matching consistent with the disclosed embodiments. As shown inFIG. 2, the process may include the following steps.

Step201: for all registered teams that participate in a PVP battle, the teams of equal size are allocated to the same matching queue.

The number of players in the registered teams that participate in the PVP battle can be any number, such as 4, 8, 9, etc. Further, one or more matching queues are created for team battle matching, and each matching queue may contain one or more teams of equal size.

For example, 6 teams are registered to participate in the battle. The number of players of team 1, team 2, team 3, team 4, team 5 and team 6 are 8, 8, 8, 4, 3, and 3, respectively. All the teams are divided into three matching queues, where queue 1 is allocated with team 1, team 2, and team 3; queue 2 is allocated with team 4; queue 3 is allocated with team 5 and team 6.

Step202: the teams of each matching queue are sorted according to the time the teams registered, from the earliest to the latest.

For example, if there are 3 teams in a matching queue, including team 1, team 2, and team 3, when the order of registration of the three teams is team 3, team 1, and team 2, a sort order of the three teams is team 3, team 1, and team 2 in the matching queue.

Step203: a team with the earliest registration time is selected from the matching queue allocated with the teams with the maximum number of players.

The earliest registration team is given priority for the battle matching by selecting the team with the earliest registration time, further enhancing the user experience.

Step204: whether the number of players in the team is equal to a preset number is determined.

Step205: if the number of players in the team is equal to the preset number, the team is allocated to one battle camp.

Alternatively, in Step205, if the number of players in the team is less than the preset number, again, a matching queue with the teams with the maximum number of players is selected from the matching queues including unselected teams. Then, a team is selected from the matching queue allocated with the teams with the maximum number of players. A total number of players in all selected teams is then obtained. If the total number of players in the selected teams is equal to the preset number, the selected teams are allocated to the same battle camp.

Also, when selecting the team from the matching queue allocated with the teams with the maximum number of players, the earliest registration team may be given priority for the team battle matching, i.e., selecting the team with the earliest registration order again may be selected, further enhancing the user experience.

Further, if the number of players in the selected team or teams is greater than the preset number, the last selected team is unselected from (or reallocated to) the corresponding matching queue. Then, from the matching queues including the teams with the number of players less than the number of players of the last selected team, a matching queue with the teams with the maximum number of players is selected. A team is then selected from the selected matching queue allocated with the teams with the maximum number of players. A total number of players in the selected teams is obtained. If the number of players in the selected teams is equal to the preset number, the selected teams are allocated to one battle camp.

Further, after the team is selected from the selected matching queue allocated with the teams with the maximum number of players, if the number of players in the selected teams is still greater than the preset number, the last selected team is unselected from (or reallocated to) the corresponding matching queue, and the second-to-last selected team is also unselected from (or reallocated to) the corresponding matching queue. Then, from the matching queues with the teams with the number of players less than the number of players in the second-to-last selected team, the matching queue with the maximum number of players of the teams is selected. A team is then selected from the matching queue allocated with the teams with the maximum number of the players. A total number of players in the selected teams is again obtained. If the number of players in the selected teams is equal to the preset number, the selected teams are allocated to one battle camp. Thus, the success rate of the team battle matching can be further improved by the backing up selection.

Optionally, after obtaining the total number of players in the various selected teams, an accumulated number of times for obtaining the total number of players in the various selected teams is recorded. If the accumulated number of times is greater than or equal to a preset threshold, team battle matching process is terminated and the registered teams that participate in the team battle are updated. For example, the registered teams may be notified that team battle matching is failed, and the one or more team may request another team battle matching when new team(s) registered for the team battle.

Thus, the problem that the teams cannot be successfully matched over a long time period can be avoided by setting the preset threshold of the accumulated number of times for obtaining the total number of players, and the server may adjust team matching method in time, improving the matching efficiency of PVP team battle.

For example, the preset threshold of the accumulated number of times for obtaining the total number of players may be 200. Because each time for obtaining the number of players may cost probably 0.01 ms, if the accumulated number of times for obtaining the total number of players is greater than 200, the total length of matching time is more than 2 ms. At this time, matching efficiency is relatively low. Therefore, the accumulated number of times for obtaining the total number of players can be set to 200 to ensure a high efficiency of team battle matching.

Specifically, an application scenario can be shown below for illustrative purposes. A server obtains registration information for 6 teams registered to participate in an 8 vs. 8 PVP battle mode. The order of registration of the teams is P1(4), P2(3), P3(2), P4(2), P5(3), and P6(2), where ‘i’ in Pi(x) indicates the team number, and x is the number of players in each team.FIG. 5illustrates a schematic diagram 1 of an exemplary team battle matching consistent with the disclosed embodiments.

As shown inFIG. 5, at the beginning, according to the number of players in each team, the server allocates P1(4) to queue 1; the server allocates P2(3) and P5(3) to queue 2; the server allocates P3(2), P4(2) and P6(2) to queue 3. Further, the team P1(4) is selected from the queue allocated with the teams with the maximum number of players.

FIG. 6illustrates a schematic diagram 2 of an exemplary team battle matching consistent with the disclosed embodiments. As shown inFIG. 6, when it is determined that the number of players in P1(4) is less than 8, and currently, the queue with the teams with the maximum number of players is queue 2, P2(3) with the earliest registration time is selected from queue 2.

FIG. 7illustrates a schematic diagram 3 of an exemplary team battle matching consistent with the disclosed embodiments. As shown inFIG. 7, a total number players of the selected P1(4) and P2(3) is 7. At this time, it is determined that the total number of players is less than 8, and the queue with the teams with the maximum number of players is queue 2 among the queues including unselected teams. P5(3) is then selected from the queue 2.

FIG. 8illustrates a schematic diagram 4 of an exemplary team battle matching consistent with the disclosed embodiments. As shown inFIG. 8, at this time, the total number of players is 10 and it is greater than 8. The server replaces P5(3) by any one team in queue 3. The total number of players is still greater than 8. At this time, the server reallocates back the last selected team to queue 3; the server reallocates back the second-to-last selected team P2(3) to queue 2. Then, P3(2) is selected from queue 3. The number of players in the teams of queue 3 is less than the number of players in the teams of queue 2.

FIG. 9illustrates a schematic diagram 5 of an example team battle matching consistent with the disclosed embodiments. As shown inFIG. 9, the total number of players in the selected teams is 6 and it is less than 8. Therefore, the server continues to select P4(2) from queue 3.

FIG. 10illustrates a schematic diagram 6 of an exemplary team battle matching consistent with the disclosed embodiments. As shown inFIG. 10, the total number of players in the selected teams is 8 and it meets the requirement. P1(4), P3(2) and P4(2) are formed into one battle camp. Similarly, the teams are selected from the remaining P2 (3), P5 (3) and P6 (2) to form the other battle camp.

Thus, after repeating the selection steps, the entire battle team matching process is completed.FIG. 11illustrates a schematic diagram 7 of an exemplary team battle matching consistent with the disclosed embodiments. The final matching result is shown inFIG. 11. That is, one battle camp is P1(4), P3(2) and P4(2), and the other battle camp is P2 (3), P5(3) and P6(2).

Thus, the disclosed embodiments provide a method for team battle matching. For registered teams that participate in a battle, the teams of equal size are allocated to the same queue. Then, the teams of each queue are sorted according to the time the teams registered, from the earliest to the latest. A team with the earliest registration is selected from the queue allocated with the teams with the maximum number of players. Further, whether the number of players in the team is equal to a preset number is determined. If the number of players of the team is equal to the preset number, the team is allocated to one battle camp. Compared with the existing methods, the method can reduce a false matching rate and improve efficiency of team battle match.

FIG. 3illustrates a structure diagram of an exemplary server for team battle matching consistent with the disclosed embodiments. As shown inFIG. 3, the server may include an allocation unit31, a selection unit32, and a determination unit33.

The allocation unit31is configured to, for teams to participate in a team battle, allocate teams having equal of players to a same matching queue.

The selection unit32is configured to select one team from the matching queue allocated with one or more teams having the maximum number of players through the allocation unit31.

The determination unit33is configured to determine whether a total number of players in the selected team by the selection unit32is equal to a preset number.

The allocation unit31is also configured to, when the determination unit33determines that the total number of players of the selected team is equal to the preset number, allocate the team to a battle camp.

FIG. 4illustrates a structure diagram of another exemplary server for team battle matching consistent with the disclosed embodiments. As shown inFIG. 4, the server may include an allocation unit41, a selection unit42, a determination unit43, an obtaining unit44, a counting unit45, a termination unit46, an updating unit47and an arrangement unit48.

The allocation unit41is configured to, for teams to participate in a team battle, allocate teams having equal of players to a same matching queue.

The selection unit42is configured to select one team from the matching queue allocated with one or more teams having the maximum number of players through the allocation unit41.

The determination unit43is configured to determine whether a total number of players in the selected team by the selection unit42is equal to a preset number.

The allocation unit41is also configured to, when the determination unit43determines that the total number of players of the selected team is equal to the preset number, allocate the team to a battle camp.

The selection unit42is also configured to, when the determination unit determines that the number of players of the team is less than the preset number, select a matching queue with one or more teams having a maximum number of players from the matching queues including one or more unselected teams.

The selection unit42is also configured to select one team from the matching queue allocated with the teams with the maximum number of players selected from the matching queues with the teams with the number of players less than the number of players in the last selected team.

The obtaining unit44is configured to obtain a total number of players in all selected teams. The allocation unit41is also configured to, when the total number of players in all selected teams is equal to the preset number, allocate all selected teams to the same battle camp.

The allocation unit41is also configured to, when the number of players in the selected team is greater than the preset number reallocate the last selected team to the corresponding queue.

The selection unit42is also configured to, from the matching queues with the teams with the number of players less than the number of players in the last selected team, select a matching queue with the team with a maximum number of players. The selection unit42is also configured to select any one team from the matching queue allocated with the teams with the maximum number of players.

The obtaining unit44is configured to obtain the total number of players in all selected teams. The allocation unit41is also configured to, when the total number of players in all selected teams is equal to the preset number, allocate all selected teams to the same battle camp.

The allocation unit41is also configured to, when one team is selected from the selected matching queue allocated with the teams with the maximum number of players and the total number of players in all selected teams is still greater than the preset number, reallocate a last selected team to its corresponding matching queue and reallocate a second-to-last selected team to the corresponding matching queue.

The selection unit42is also configured to, from the matching queues with one or more teams with the number of players less than the number of players in the second-to-last selected team, select a matching queue with one or more teams with the maximum number of players.

The selection unit42is also configured to select one team from the matching queue allocated with the teams with the maximum number of players selected from the matching queues with one or more teams with the number of players less than the number of players in the second-to-last selected team.

The obtaining unit44is also configured to obtain a total number of players in all selected teams. The allocation unit41is also configured to, when the total number of players in all selected teams is equal to the preset number, allocate all selected teams to the same battle camp. The counting unit45is configured to record an accumulated number of times for obtaining the total number of players in all selected teams.

The termination unit46is configured to, when the accumulated number of times is greater than or equal to a preset threshold, terminate the method for team battle matching. The updating unit47is configured to update the registered teams that participate in the team battle.

The arrangement unit48is configured to sort the teams of each queue according to the time the teams registered, from the earliest to the latest. The selection unit42is also configured to, when selecting a team from each queue, selecting a team with an earliest registration from the queue.

For teams to participate in a team battle, teams having equal of players are allocated to a same matching queue. Then, any one team is selected from the queue allocated with the teams having the maximum number of players. Further, whether the number of players in the team is equal to a preset number is determined. If the number of players in the team is equal to the preset number, the team is allocated to one battle camp. Compared with the existing methods, the method can reduce a false matching rate and improve efficiency of team battle matching.

Those skilled in the art should understand that all or part of the steps in the above method may be executed by relevant hardware instructed by a program, and the program may be stored in a computer-readable storage medium such as a read only memory, a magnetic disk, a Compact Disc (CD), and so on.

The embodiments disclosed herein are exemplary only and not limiting the scope of this disclosure. Without departing from the spirit and scope of this invention, other modifications, equivalents, or improvements to the disclosed embodiments are obvious to those skilled in the art and are intended to be encompassed within the scope of the present disclosure.

INDUSTRIAL APPLICABILITY AND ADVANTAGEOUS EFFECTS

Without limiting the scope of any claim and/or the specification, examples of industrial applicability and certain advantageous effects of the disclosed embodiments are listed for illustrative purposes. Various alternations, modifications, or equivalents to the technical solutions of the disclosed embodiments can be obvious to those skilled in the art and can be included in this disclosure.

By using the disclosed method and server for team battle matching, for teams to participate in a team battle, teams having equal of players are allocated to a same matching queue. Then, any one team is selected from the queue allocated with the teams having the maximum number of players. Further, whether the number of players in the team is equal to a preset number is determined. If the number of players in the team is equal to the preset number, the team is allocated to one battle camp. Compared with the existing methods, the method can reduce a false matching rate and improve efficiency of team battle matching.