Game matching time prediction method and device, equipment and storage medium
By predicting matchmaking time based on game type and player skill level, the system solves the problem of inaccurate matchmaking time in existing technologies, improving the accuracy of matchmaking time prediction and player experience.
Patent Information
- Application Number
- CN202210238372.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-11
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-03-11
AI Technical Summary
Existing methods for predicting game matchmaking times cannot provide accurate predictions, causing anxiety among players while waiting for matchmaking, especially for high-ranking players who experience longer wait times, thus impacting their gaming experience.
The server predicts the current player's matchmaking time based on the player's target game type, skill level, and historical matchmaking time data, and then sends the result to the client for display.
It improves the accuracy of matchmaking time prediction, reduces players' waiting anxiety, and enhances the gaming experience.
Smart Images

Figure CN116764239B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, device, and storage medium for predicting game matchmaking time. Background Technology
[0002] For some multiplayer games, it's necessary to match players of similar skill levels, and this matchmaking process takes time. Estimating an accurate matchmaking time can help players understand the process, reduce anxiety, and increase the probability of successfully matching into a game.
[0003] However, current matchmaking time prediction methods typically set a default value and then adjust it based on the actual matchmaking situation, using the adjusted default value as the current player's matchmaking time. This approach fails to achieve accurate matchmaking time prediction. Summary of the Invention
[0004] This application provides a method, apparatus, device, and storage medium for predicting game matchmaking time, so as to improve the accuracy of matchmaking time prediction.
[0005] In a first aspect, embodiments of this application provide a method for predicting game matchmaking time, applied to a server, comprising:
[0006] In response to a game matchmaking request sent by the client for the current player, the target game type selected by the current player and the current player's skill level score in the target game are determined, and the game matchmaking request is used to request a matchmaking time for the current player;
[0007] Based on the target game type, the player's skill level score, and historical player matchmaking time data, predict the current player's matchmaking time.
[0008] The predicted match time for the current player is sent to the client for display.
[0009] In some embodiments, the historical matching time data is updated periodically.
[0010] In some embodiments, the game matchmaking request includes the current player's identification information, and the step of determining the target game type selected by the current player and the current player's skill level score in the target game in response to the game matchmaking request sent by the client includes:
[0011] Based on the current player's identification information, determine the target game type selected by the current player, and the current player's skill level score in the target game.
[0012] In some embodiments, determining the target queue type selected by the current player includes:
[0013] If the game matchmaking request includes the target queue type selected by the current player, then the target queue type selected by the current player can be obtained by parsing the game matchmaking request.
[0014] In some embodiments, the matchmaking time data of the historical players is the matchmaking time data when the historical players were matched into a game.
[0015] In some embodiments, the game matching request includes the current player's identification information, the server determining the target game type selected by the current player based on the current player's identification information, and the current player's skill level score in the target game.
[0016] In some embodiments, the game matchmaking request includes the target queue type selected by the current player.
[0017] Secondly, embodiments of this application provide a method for predicting game matchmaking time, using an application client, including:
[0018] In response to the current player's game matchmaking action, a game matchmaking request is sent to the server, the game matchmaking request being used to request a matchmaking time for the current player;
[0019] The system receives the matchmaking time of the current player sent by the server. The matchmaking time of the current player is predicted based on the target game type selected by the current player, the current player's skill level score in the target game, and historical player matchmaking time data.
[0020] Displays the current player's matchmaking time.
[0021] Thirdly, embodiments of this application provide a game matchmaking time prediction device, applied to a server, comprising:
[0022] The determining unit is configured to, in response to a game matchmaking request sent by the client, determine the target game type selected by the current player and the current player's skill level score in the target game, wherein the game matchmaking request is used to request a matchmaking time for the current player;
[0023] The prediction unit is used to predict the match time of the current player based on the target game type, the player's skill level score, and historical player match time data.
[0024] The processing unit is used to send the predicted match time of the current player to the client for display.
[0025] Fourthly, embodiments of this application provide a device for predicting game matchmaking time, applied to a client, comprising:
[0026] The sending unit is used to send a game matchmaking request to the server in response to the current player's game matchmaking operation. The game matchmaking request is used to request the matchmaking time for the current player.
[0027] The receiving unit is used to receive the match time of the current player sent by the server. The match time of the current player is predicted based on the target game type selected by the current player, the current player's skill level score in the target game, and historical player match time data.
[0028] The display unit is used to display the current player's matchmaking time.
[0029] Fifthly, an electronic device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to invoke and run the computer program stored in the memory to perform the methods of any one of the first or second aspects or their respective implementations.
[0030] Sixthly, a chip is provided for implementing the methods of any one of the first or second aspects or their respective implementations. Specifically, the chip includes a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the methods of any one of the first or second aspects or their respective implementations.
[0031] In a seventh aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the methods of any one of the first or second aspects or their implementations.
[0032] Eighthly, a computer program product is provided, including computer program instructions that cause a computer to perform the methods in any one of the first or second aspects or their respective implementations.
[0033] Ninthly, a computer program is provided that, when run on a computer, causes the computer to perform the methods of any one of the first or second aspects or their respective implementations.
[0034] In summary, in response to the current player's game matchmaking operation, the client sends a game matchmaking request to the server, which requests the current player's matchmaking time. The server, in response to the client's game matchmaking request, determines the target game type selected by the current player and the player's skill level in that target game. Then, based on the target game type, skill level, and historical player matchmaking time data, the server predicts the current player's matchmaking time and sends the predicted matchmaking time to the client for display. That is, in this embodiment, the influence of game type and skill level on matchmaking time is fully considered when determining the current player's matchmaking time, thereby improving the accuracy of matchmaking time prediction. Attached Figure Description
[0035] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0036] Figure 1 This is a schematic diagram illustrating an application scenario according to an embodiment of this application;
[0037] Figure 2 A schematic flowchart of a game matchmaking time prediction method provided in an embodiment of this application;
[0038] Figure 3 This is a schematic diagram of an interface according to an embodiment of this application;
[0039] Figure 4 This is a schematic diagram of an interface according to an embodiment of this application;
[0040] Figure 5 This is a schematic diagram of an interface according to an embodiment of this application;
[0041] Figure 6 This is a schematic diagram of an interface according to an embodiment of this application;
[0042] Figure 7 This is a schematic diagram of an interface according to an embodiment of this application;
[0043] Figure 8 A schematic flowchart of a game matchmaking time prediction method provided in an embodiment of this application;
[0044] Figure 9 This is a schematic diagram of an interface according to an embodiment of this application;
[0045] Figure 10 A schematic diagram of the structure of a game matchmaking time prediction device provided in an embodiment of this application;
[0046] Figure 11A schematic diagram of the structure of a game matchmaking time prediction device provided in an embodiment of this application;
[0047] Figure 12 This is a schematic block diagram of the electronic device provided in the embodiments of this application. Detailed Implementation
[0048] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.
[0049] The embodiments of this application are applied to the technical field of maps and other similar fields.
[0050] It should be understood that, in the embodiments of the present invention, "B corresponding to A" means that B is associated with A. In one implementation, B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.
[0051] In the description of this application, unless otherwise stated, "a plurality of" means two or more.
[0052] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.
[0053] The embodiments of this application involve various game processing solutions, such as mobile games, PC games, and web games.
[0054] In some embodiments, the present application relates to cloud gaming processing solutions.
[0055] Cloud gaming is an online gaming technology based on cloud computing. It enables thin clients with relatively limited graphics processing and data processing capabilities to run high-quality games. In cloud gaming, the game does not run on the player's terminal but on a cloud server. The cloud server renders the game scene as video and audio streams and transmits these streams to the player's terminal via a communication network. The player's terminal does not need powerful graphics processing and data processing capabilities; it only needs basic streaming media playback capabilities and the ability to receive player input and send it to the cloud server.
[0056] Cloud computing is a computing model that distributes computing tasks across a resource pool composed of a large number of computers, enabling various application systems to obtain computing power, storage space, and information services as needed. The network providing these resources is called the "cloud." From the user's perspective, the resources in the "cloud" are infinitely scalable and can be accessed, used on demand, scaled at any time, and paid for based on usage. As the foundational providers of cloud computing capabilities, they establish cloud resource pools (referred to as cloud platforms), generally called IaaS (Infrastructure as a Service) platforms. Various types of virtual resources are deployed within these cloud resource pools for external customers to choose from. The cloud resource pool mainly includes: computing devices (virtualized machines containing operating systems), storage devices, and network devices. Logically, a PaaS (Platform as a Service) layer can be deployed on top of the IaaS layer, and a SaaS (Software as a Service) layer can be deployed on top of the PaaS layer. Alternatively, SaaS can be directly deployed on top of IaaS. PaaS is a platform for running software (such as databases, web containers, etc.). SaaS refers to various types of business software (such as web portals, bulk SMS senders, etc.). Generally speaking, SaaS and PaaS are upper-layered compared to IaaS.
[0057] Figure 1 This is a schematic diagram of an application scenario involved in an embodiment of this application, including a terminal device 101, a game client 102, a server 103, and a player 104.
[0058] In this context, terminal device 101 can refer to a device that has the game installed; this device may include, but is not limited to, PCs (Personal Computers), PDAs (Tablet PCs), mobile phones, wearable smart devices, etc. The device is often equipped with a display device, which may also be a monitor, display screen, touch screen, etc. The touch screen may also be a touch screen, touch panel, etc. The display device can be used to display game screens, etc.
[0059] Server 103 can be one or more. When there are multiple servers 103, at least two servers 103 are used to provide different services, and / or at least two servers 103 are used to provide the same service, such as providing the same service in a load-balanced manner. This application embodiment does not limit this. The aforementioned server 103 can be an independent physical server 103, or a server cluster or distributed system composed of multiple physical servers 103, or a cloud server 103 providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Server 103 can also be a node in a blockchain.
[0060] The terminal device 101 and the server 103 can be directly or indirectly connected through wired or wireless communication, and this application does not impose any restrictions on this.
[0061] In this embodiment of the application, a game client 102 is installed and runs in the terminal device 101. At least one game can run in the game client 102. When player 104 clicks on the game client 102 to start the target game, the terminal device 101 can send account information to the server 103 via signaling. The account information includes the current player's user identifier and the terminal device 101's device identifier. The current player's user identifier may include the current player's game account, such as the login account used to log in to the target game. The terminal device 101's device identifier includes a device number, etc., and is used to indicate the type of operating system deployed in the terminal device 101. The operating system type may include Android and iOS operating systems.
[0062] After receiving the account information sent by the terminal device 101, the server 103 determines the game data corresponding to the account information and sends the game data to the terminal device 101. The game client 102 on the terminal device 101 displays the game data.
[0063] In some multiplayer games, matching players of similar skill levels into matches takes time. Having a precise estimated matchmaking time reduces player anxiety. Without it, players don't know how long they'll have to wait; a match might be ready in a second, but a long wait can lead to them giving up and canceling the match. This is especially true for higher-ranked players, who typically have longer matchmaking times due to the smaller number of players. Estimated matchmaking times minimize waiting time, allowing players to do other things while waiting and improving their overall gaming experience.
[0064] In games that require player matchmaking, the game client 102 first displays a matchmaking interface, which includes options to indicate whether to proceed with matchmaking. If the current player confirms matchmaking and triggers the matchmaking option, the game client 102 sends a game matchmaking request to the server 103. Based on this matchmaking request, the server 103 executes the method of this embodiment to predict the current player's matchmaking time and sends this time to the game client 102 for display. In this way, the current player can choose to wait or cancel matchmaking based on the matchmaking time displayed on the current interface of the game client 102, avoiding aimless waiting and thus improving the player's gaming experience.
[0065] It should be noted that the application scenarios of this application embodiment include, but are not limited to, those of other applications. Figure 1 As shown.
[0066] The technical solutions of the embodiments of this application will be described in detail below through some examples. The following embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.
[0067] Figure 2 This is a schematic flowchart of a game matchmaking time prediction method provided in an embodiment of this application. The execution entity of this embodiment can be... Figure 1 The server and client are shown.
[0068] like Figure 2 As shown, the game matchmaking time prediction method of this application embodiment includes the following steps:
[0069] S201. In response to the current player's game matchmaking operation, the client sends a game matchmaking request to the server.
[0070] The game matchmaking request is used to request the matchmaking time for the current player.
[0071] In this embodiment, a game client is installed on the current player's terminal device. When the current player triggers the client, it includes the target game. Optionally, the client may include other games besides the target game; this embodiment does not impose any restrictions on this.
[0072] When the current player triggers the target game, the client launches the target game and simultaneously sends the current player's user information to the server. This user information includes the current player's identification information, and optionally, it may also include the device type of the terminal device, such as the system type. The server sends the matchmaking interface data to the client based on the user information, and the client displays the current player's matchmaking interface based on the matchmaking interface data sent by the server.
[0073] In one example, the current player's matchmaking screen looks like this: Figure 3 As shown, this includes matchmaking options. If the current player wants to be matched into a game, they can trigger this matchmaking option. At this time, the client sends a game matchmaking request to the server. This game matchmaking request is used to request the current player's matchmaking time.
[0074] In some embodiments, the game matching request is also used to request the server to match the current player with other online players of similar skill level and form a game.
[0075] Currently, players can log in to the target game via social media apps like WeChat, therefore, the server can obtain the player's friend information. At this point, if... Figure 3 In addition to matching options, the matchmaking interface also displays one or more of the current player's friends. These friends are either those who have registered for the target game or those who have registered for the target game and are currently online.
[0076] S202. The server responds to the game matchmaking request sent by the client for the current player, determines the target game type selected by the current player, and the current player's skill level score in the target game.
[0077] After receiving a game matchmaking request from the client, the server responds by determining the target game type selected by the current player and the player's skill level score in that target game.
[0078] In this embodiment of the application, the server determines the target game type selected by the current player in the following ways, including but not limited to:
[0079] Method 1: The client sends the player's selected game type to the server. For example, the client includes the player's selected game type in the game matchmaking request. The server parses the game matchmaking request to obtain the player's selected game type.
[0080] Method Two: The game matchmaking request includes the current player's identification information. The server parses the matchmaking request to obtain the current player's identification information and determines the type of game the current player has selected based on this information. For example, when the current player logs into a target game, the client sends the current player's user information and the target game's identification information to the server. In other words, the server stores the correspondence between the current player's identification information and the target game. Therefore, when the game matchmaking request includes the current player's identification information, the server can determine the type of game the current player has selected based on this information.
[0081] In this embodiment of the application, the methods by which the server determines the current player's skill level score in the target game include, but are not limited to, the following:
[0082] Method 1: The client sends the current player's skill level score in the target game to the server. For example, the client includes the current player's skill level score in the game matchmaking request and sends it to the server. The server parses the game matchmaking request to obtain the current player's skill level score in the target game.
[0083] Method Two: The game matchmaking request includes the current player's identification information. The server parses the matchmaking request to obtain the current player's identification information and determines the current player's skill level score in the target game based on this information. For example, the server stores the current player's skill level score in the target game. This score could be the player's most recent score in the target game, or optionally, it could be a weighted average of the player's most recent scores in the target game. When the server receives a game matchmaking request from the client, it parses the request to obtain the current player's identification information and then uses this information to query the current player's skill level score in the target game.
[0084] It should be noted that the server can also determine the type of target game currently selected by the player, as well as the player's skill level score in that target game type, through other methods. This application does not impose any restrictions on this.
[0085] This application does not limit the type of the target game.
[0086] In some embodiments, game types include normal matchmaking, ranked matchmaking, AI matchmaking, ARAM matchmaking, and URF matchmaking. The target game type in this application embodiment can be one of the game types currently selected by the player.
[0087] Optionally, the skill level score in this application embodiment can be an Elo rating. The Elo rating system is named after its promoter, Professor Elo. It is a numerical system that converts level differences into scores or winning probabilities, and vice versa. Most competitive sports rating systems today are based on the Elo system.
[0088] S203. The server predicts the matchmaking time for the current player based on the target game type, the current player's skill level score, and historical matchmaking time data.
[0089] In this embodiment of the application, the matchmaking time of different historical players under different game types is saved to form matchmaking time data of historical players.
[0090] Optionally, the matchmaking time data for historical players refers to the matchmaking time data when a historical player was matched into a game.
[0091] In one example, historical player matchmaking time data can be stored on a server.
[0092] In another example, historical player match time data can be stored in other storage devices, such as a database, from which the server can read the historical player's match time data.
[0093] The historical player matchmaking time data in this application embodiment includes the matchmaking times of different players accessing different types of games in historical time. Thus, when the server receives a game matchmaking request from the client for the current player, it can determine the target game type selected by the current player and the current player's skill level score in that target game according to the steps described above. The server then retrieves the matchmaking time corresponding to the target game type and the current player's skill level score from the historical player matchmaking time data and determines that matchmaking time as the current player's matchmaking time.
[0094] In some embodiments, S203 above includes the following steps:
[0095] S203-A: In the historical player matchmaking time data, query the target matchmaking time data corresponding to the target game type and player skill score;
[0096] S203-B: Determine the current player's match time based on the target match time data.
[0097] In this embodiment, the server queries the historical matchmaking time data for the target game type and the current player's skill level score. Then, the server determines the current player's matchmaking time based on the target matchmaking time data. In other words, in this embodiment, the server considers that players of the same game type may have different skill levels when predicting matchmaking time, and thus predicts the current player's matchmaking time based on the target game type and skill level score, thereby improving the accuracy of matchmaking time prediction.
[0098] In some embodiments, the historical player matchmaking time data of this application includes the historical player's matchmaking time and skill level score in each of the N game types.
[0099] For example, historical player matchmaking time data is shown in Table 1:
[0100] Table 1
[0101]
[0102] As shown in Table 1 above, in some embodiments, the present application embodiments can store the matching time and skill score of different historical players in different game types. For example, the matching time 23 and score 23 of player 23 in game 2 can be stored.
[0103] When predicting matchmaking time, the server can predict the current player's matchmaking time based on the historical player matchmaking time data stored in Table 1. Specifically, when the server receives a game matchmaking request from the client for the current player, it first determines the target game type selected by the current player and the current player's skill level score in that target game, following the steps described above. Next, based on the target game type and the current player's skill level score, the server queries Table 1 for matchmaking times where the game type matches the target game type and the skill level score matches the current player's skill level score. These matchmaking times are used as the target matchmaking time data, and the average or median of these matchmaking times is determined as the current player's matchmaking time.
[0104] For example, suppose the current player selects Game 2 as their target game, and their skill level score in Game 2 is 21. In Table 1 above, for Game 2, the matching times corresponding to a skill level score of 21 are found to be Matching Time 21 and Matching Time 22. Therefore, the average of Matching Time 21 and Matching Time 22 can be determined as the current player's matching time.
[0105] Optionally, the matchmaking time for the current player can be determined based on the matchmaking time corresponding to the skill level score within a preset range of 21 ± (plus or minus) in Game 2 saved in Table 1. For example, the average matchmaking time corresponding to the skill level score within the range of 21 ± 5 in Game 2 saved in Table 1 can be used as the matchmaking time for the current player.
[0106] In some cases, if Table 1 does not store a player's skill level score that is the same as the current player's skill level score, the matchmaking time for the current player can be determined based on the matchmaking time corresponding to a player's skill level score that is similar to the current player's skill level score in the target game type in Table 1.
[0107] In some embodiments, the historical player matchmaking time data of this application includes the matchmaking time of historical players in M skill level score ranges for each of the N game types.
[0108] For example, historical player matchmaking time data is shown in Table 2:
[0109] Table 2
[0110]
[0111] Table 2 above shows the match time data for each of the M skill level intervals [a0,a1], [a1,a2], ..., [aM-1,aM] for each of the N games.
[0112] In other words, in this embodiment of the application, when a historical player is matched into a game, the matching time of that historical player is stored in Table 2 above, based on the game type selected by the historical player and the historical player's skill level score. For example, if historical player c selected game type 2 and historical player c's skill level score in game 2 is a11, which is located in the skill level score range [a1, a2], then the matching time of historical player c can be stored in data 22 of Table 2.
[0113] When predicting matchmaking time, the server can perform predictions based on the historical player matchmaking time data stored in Table 2. Specifically, when the server receives a game matchmaking request from the client for the current player, it first determines the target game type selected by the current player and the player's skill level in that target game, following the steps described above. Next, based on the target game type and the player's skill level, the server determines the target matchmaking time data for the score range in Table 2 where the target game type is listed and the player's skill level falls within that range. Finally, the server determines the current player's matchmaking time based on this target matchmaking time data.
[0114] For example, suppose the target game selected by the current player is Game 2, and the current player's skill level score in the target game is a11, with the score range of skill level score a11 being [a1, a2]. The matching time data 22 corresponding to the score range of [a1, a2] for Game 2 in Table 2 above is determined as the target matching time data. The current player's matching time is then determined based on data 22.
[0115] This application embodiment does not limit the type of matching time data included in Table 2 above.
[0116] Example 1: The matching time data mentioned above includes the matching times of each historical player. In this case, determining the current player's matching time based on data 22 could be done by taking the average of the matching times of each historical player in data 22 as the current player's matching time.
[0117] Example 2: The matching time data includes the total matching time and total number of successful matches for each historical player. In this embodiment, the historical player matching time data includes the total matching time and total number of successful matches for each historical player within a preset time period, across different skill level ranges in different game types.
[0118] For example, taking N game types and M skill level ranges as an example, the historical player matchmaking time data of this application embodiment is shown in Table 3:
[0119] Table 3
[0120]
[0121]
[0122] Table 3 above shows the total match time and total number of successful matches for historical players in N games across M skill score intervals [a0,a1], [a1,a2], ..., [aM-1,aM].
[0123] As shown in Table 3, this embodiment of the application accumulates the matching time of different players at the same skill level in the same game and saves it as a total matching time. At the same time, it saves a total number of successful matches, saving two sets of data, which greatly reduces the amount of data that needs to be saved, thereby reducing the storage cost of matching time data.
[0124] Based on Table 3 above, S203-A includes the following steps:
[0125] S203-A11. In the historical player match time data, query the match time data corresponding to the target game type;
[0126] S203-A12. The total first match time and the total number of successful first matches within the match time range corresponding to the current player's skill level score in the match time data for the target game type are determined as the target match time data.
[0127] For example, suppose the current player selects Game 2 as their target game type, and their skill level in Game 2 is a11. The server first queries the historical player match time data (Table 3 above) for the match time data corresponding to the target game type (i.e., Game 2). Next, based on the current player's skill level score (a11) in the target game, the server determines the skill level range [a1, a2]. Then, it queries the match time data corresponding to the target game type (i.e., Game 2) for the total match time N2 within [a1, a2], and the total number of successful matches N2. For ease of description, this embodiment refers to the total match time N2 as the first total match time and the total number of successful matches N2 as the first total match count.
[0128] Correspondingly, in S203-B above, determining the current player's matching time based on the target matching time data can be achieved by using the ratio of the first total matching time to the first total number of matches as the current player's matching time. For example, the current player's matching time = total matching time N2 / total number of successful matches N2.
[0129] In this embodiment, the historical player matchmaking time data is further divided based on the number of players in the team after team formation. Specifically, in some embodiments, the historical player matchmaking time data includes matchmaking time data for different game types and queue types within a preset time period. The matchmaking time data for each combination includes the total matchmaking time and the total number of successful matches across different skill level ranges.
[0130] This application does not limit the type of team.
[0131] In some embodiments, team types include single-player teams, two-player teams, three-player teams, four-player teams, and five-player teams, etc.
[0132] Example 1: Taking N game types, K team types, and M skill level ranges as an example, the historical player matchmaking time data in this embodiment of the application is shown in Table 4:
[0133] Table 4
[0134]
[0135]
[0136] Table 4 above shows the total matching time and total number of successful matches for historical players across N different game combinations and K different queue combinations, for each of the M different skill level score ranges.
[0137] As shown in Table 4, this embodiment of the application accumulates the matching time of different players in the same game, the same queue type, and the same level score, and saves it as a total matching time. At the same time, it saves a total number of successful matches, saving two data sets in total, which greatly reduces the amount of data that needs to be saved, thereby reducing the storage cost of matching time data.
[0138] Table 4 above is only one way to store historical player matchmaking time data. In some embodiments, game type and team type can be combined before storage. Assume that the game types in this embodiment include normal matchmaking, ranked, AI matchmaking, ARAM matchmaking, and URF matchmaking; and the team types include solo teams, duo teams, trio teams, quad teams, and quintuplets. Since ARAM and URF matchmaking do not limit the number of teams, the combinations of different games and different queues in this embodiment include: solo teams, duo teams, trio teams, quad teams, quintuplets, ranked solo teams, ranked duo teams, ranked trio teams, ranked quad teams, ranked quintuplets, AI matchmaking, ARAM matchmaking, and URF matchmaking. In this case, the historical player matchmaking time data in this embodiment is shown in Table 5:
[0139] Table 5
[0140]
[0141]
[0142] Table 5 above shows the total match time and total number of successful matches for historical players across M different skill level score ranges under different game types and different queue type combinations.
[0143] In some embodiments, the historical player matchmaking time data shown in Tables 1 to 5 above may also include a default average value, which is a default matchmaking wait time set by the server for historical players. For example, if the data stored in Table 5 for the skill score range [a0, a1] in a ranked three-player team is limited or nonexistent, the server will determine the default average value as the matchmaking time for the current player in a ranked three-player team. That is, the default average value is a preset value, or it is the average matchmaking time for different game types and different queue types.
[0144] Based on Table 4 or 5 above, S203-A includes the following steps S203-A21 to S203-A24:
[0145] S203-A21. Determine the target queue type selected by the current player;
[0146] S203-A22. In the historical player match time data, query the match time data corresponding to the target game type;
[0147] S203-A23. In the matching time data corresponding to the target game type, query the matching time data corresponding to the target game type;
[0148] S203-A24. The total first match time and the total number of successful first matches within the match time range corresponding to the current player's skill level score in the match time data for the target game type are determined as the target match time data.
[0149] In this embodiment of the application, the server determines the target queue type selected by the current player in several ways, including but not limited to the following:
[0150] Method 1: The client sends the target queue type selected by the current player to the server. For example, the client includes the target queue type selected by the current player in the game matchmaking request and sends it to the server. The server obtains the target queue type selected by the current player by parsing the game matchmaking request.
[0151] Method Two: The game matchmaking request includes the current player's identification information. The server parses the matchmaking request to obtain the current player's identification information and determines the target queue type selected by the current player based on this information. For example, when the current player logs into a target game, the client sends the current player's user information and the target queue's identification information to the server. In other words, the server stores the correspondence between the current player's identification information and the target queue. Thus, when the game matchmaking request includes the current player's identification information, the server can determine the target queue type selected by the current player based on this information.
[0152] After determining the target queue type selected by the current player using the above method, the server first queries the historical matchmaking time data for the target game type, based on the player's selected target game type. Next, it queries the matchmaking time data for the target team type, based on the player's selected team type. Then, it determines the player's skill level score within the target game type and target queue type, and the corresponding skill level score range. Finally, it determines the total first match time and the total number of successful first matches within the player's skill level score range from the matchmaking time data corresponding to the target game type, as the target matchmaking time data.
[0153] Correspondingly, in S203-B above, determining the current player's matching time based on the target matching time data can be achieved by taking the ratio of the first total matching time to the first total number of matching attempts as the current player's matching time.
[0154] S204. The server sends the predicted match time for the current player to the client for display.
[0155] S205. The client displays the current player's matchmaking time.
[0156] For example, assuming the current player selects a normal matchmaking game and a single-player queue team, the server, based on Table 5 above and the player's skill level in single-player matchmaking, predicts the current player's matchmaking time. Figure 4 As shown, the matching time is expected to be 25 seconds.
[0157] For example, suppose the current player selects a normal matchmaking game and a duo queue team. Based on Table 5 above, the server predicts the current player's matchmaking time according to their skill level in duo matchmaking. Figure 5 As shown, the matching time is expected to be 17 seconds.
[0158] For example, suppose the current player selects ranked mode as their target game type and solo queue as their target team type. Based on Table 5 above, the server predicts the current player's matchmaking time according to their skill level in solo ranked games. Figure 6 As shown, the matching time is expected to be 23 seconds.
[0159] In some embodiments, if the target game type selected by the current player is AI matchmaking, ARAM matchmaking, or URF matchmaking, it indicates that there are many people in the queue and the number of people is not fixed. In this case, it is not necessary to determine the target team type of the current player, and the matchmaking time of the current player can be determined directly based on the target game type.
[0160] For example, assuming the current player's selected game type is ARAM (All Random All Mid), the server, based on Table 5 above and the player's skill score in ARAM, predicts the current player's matchmaking time. Figure 7 As shown, the matching time is expected to be 15 seconds.
[0161] The game matchmaking time prediction method provided in this application involves a client responding to a player's game matchmaking operation by sending a game matchmaking request to a server. This request requests the player's matchmaking time. The server, in response to the client's request, determines the target game type selected by the player and the player's skill level in that game. Then, based on the target game type, skill level, and historical player matchmaking time data, the server predicts the player's matchmaking time and sends this prediction to the client for display. In other words, this application embodiment fully considers the impact of game type and skill level on matchmaking time when determining the current player's matchmaking time, thereby improving the accuracy of matchmaking time prediction.
[0162] The prediction process for matching time has been introduced above. The following section describes the process of saving matching time using specific examples.
[0163] Figure 8 This is a schematic flowchart of a game matchmaking time prediction method provided in an embodiment of this application, as shown below. Figure 8 As shown, it includes:
[0164] S301. In response to the current player's game matchmaking operation, the client sends a game matchmaking request to the server.
[0165] S302. The server responds to the game matchmaking request sent by the client for the current player, determines the target game type selected by the current player, and the current player's skill level score in the target game.
[0166] S303: The server predicts the matchmaking time for the current player based on the target game type, the current player's skill level score, and historical matchmaking time data.
[0167] S304. The server sends the predicted matchmaking time for the current player to the client for display.
[0168] S305. The client displays the current player's matchmaking time.
[0169] The processes described in S301 to S305 above are the same as those described in S201 to S205 above, and will not be repeated here.
[0170] S306. The client responds to the current player's matchmaking request by sending a matchmaking success message to the server.
[0171] This successful match message indicates that the current player has been successfully matched.
[0172] like Figures 4 to 7 As shown, the server predicts the current player's matchmaking time using the method described above and sends this time to the client for display. In addition to displaying the matchmaking time, the client also displays a "Cancel Matchmaking" option. If the current player clicks the "Cancel Matchmaking" option, matchmaking fails, and the current player's matchmaking time is not saved.
[0173] If the current player does not click the cancel match option, but instead waits for the entire matchmaking process to finish, such as Figure 9 As shown, after the matchmaking process is complete, a confirmation option to accept the match is displayed on the interface. If the current user clicks this confirmation option, the client responds to the current player's acceptance of the matchmaking by sending a matchmaking success message to the server. This message indicates that the current player has successfully matched with a match.
[0174] S307. The server responds to the match success message and saves the current player's match time.
[0175] After receiving the match success message from the client, the server saves the predicted match time for the current player.
[0176] In some embodiments, when a client reports a match time, it needs to report the match time based on the game type and team type. When reporting, the game type is converted into different prefixes, and the team type is suffixed. In this way, the data reported each time will fall into different statistical intervals.
[0177] For example, the conversion is first performed based on game type, with different game types corresponding to different prefixes and different team types corresponding to different suffixes. This way, based on the player's selected target game type, a prefix is added before the player's match time, and based on the player's selected target team type, a suffix is added after the player's match time. The server can then determine the target game type based on the prefix of the player's match time and the target team type based on the suffix, and finally store the match time in the statistical interval under the target game type and target team type.
[0178] In some embodiments, the client may also include the current player's identifier information in the match success message. This allows the server to determine, based on the current player's identifier information, the game type corresponding to the match time as the target game type and the team type as the target team type, and then store the match time in the statistical interval under the target game type and target team type.
[0179] In some embodiments, as shown in Table 4 or Table 5, the historical player matchmaking time data includes matchmaking time data for historical players under different game types and different queue types within a preset time period. Thus, after determining the target game type and target team type corresponding to the current player's matchmaking time, as well as the current player's skill level score under the target game type and target team type, based on the above steps, the first total matchmaking time and the first total number of matchmaking attempts within the skill level score range of the target game type, target team type, and current player's skill level score can be determined. Next, the current player's matchmaking time is added to this first total matchmaking time, and the first total number of successful matchmaking attempts is incremented by one.
[0180] For example, assuming the current player has selected a solo match, the server stores the player's matchmaking time within the matchmaking time data corresponding to their skill level score (e.g., Elo rating) in the solo match. For instance, if the maximum Elo rating is 5000, with each 100-point segment resulting in 50 segments (5000 / 100 = 50), and the current player's Elo rating is 150, the server stores the player's matchmaking time within the Elo rating range of 101-200. This means the player's matchmaking time is accumulated within the total matchmaking time for the 101-200 range, and the total number of successful matches is incremented by 1.
[0181] In some embodiments, to reduce data storage costs and improve the accuracy of matching time prediction, this application embodiment only saves matching time data within a recent preset time period. That is, the historical matching time data in this application embodiment is updated periodically. For example, it is updated every 5 minutes, saving matching time data from the last 5 minutes.
[0182] This application embodiment can separately calculate the estimated time required for each player match based on game type and team type. When expanding in parallel, the code changes are minimal. Only adding a new game type is needed to calculate the estimated match time for the new game mode, reducing the maintenance cost for developers and making it easy to expand.
[0183] This application embodiment can be applied to waiting and queuing scenarios involving different types of data. By statistically analyzing past data, classifying the past data, taking the average value over a period of time, and obtaining an estimated time for that type of data within the same period of time.
[0184] In this embodiment of the application, the client responds to the current player's receiving match operation by sending a match success message to the server. The server saves the current player's match time based on the match success message. For example, it adds the current player's match time to the first total match time and increments the first total number of successful matches by one.
[0185] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application.
[0186] It should also be understood that, in the various method embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0187] The above text combined Figures 2 to 9 The method embodiments of this application are described in detail below, in conjunction with... Figures 10 to 12 The following describes in detail the device embodiments of this application.
[0188] Figure 10This is a schematic diagram of a game matchmaking time prediction device provided in an embodiment of this application. The prediction device is applied to a server.
[0189] like Figure 10 As shown, the prediction device 10 includes:
[0190] The determining unit 11 is used to respond to the game matching request sent by the client for the current player, determine the target game type selected by the current player, and the current player's skill level score in the target game, wherein the game matching request is used to request the current player's matching time;
[0191] The prediction unit 12 is used to predict the match time of the current player based on the target game type, the skill level score, and the historical match time data of the players.
[0192] The processing unit 13 is used to send the predicted match time of the current player to the client for display.
[0193] In some embodiments, the prediction unit 12 is specifically used to query the target match time data corresponding to the target game type and the skill level score from the historical player match time data; and determine the match time of the current player based on the target match time data.
[0194] In some embodiments, the historical player matching time data includes the total matching time and total number of successful matches for historical players in each different skill level score range of different game types within a preset time period. The prediction unit 12 is specifically used to query the matching time data corresponding to the target game type from the historical player matching time data; and to determine the first total matching time and the first total number of successful matches in the skill level score range where the current player's skill level score is located in the matching time data corresponding to the target game type as the target matching time data.
[0195] In some embodiments, the historical player matching time data includes matching time data of historical players under different game types and different queue types within a preset time period. The matching time data under each combination includes the total matching time and the total number of successful matches under different skill level score ranges. The prediction unit 12 is specifically used to determine the target queue type selected by the current player; query the matching time data corresponding to the target game type from the historical player matching time data; query the matching time data corresponding to the target game type from the matching time data corresponding to the target game type; and determine the first total matching time and the first total number of successful matches under the skill level score range where the current player's skill level score is located in the matching time data corresponding to the target game type as the target matching time data.
[0196] In some embodiments, the prediction unit 12 is specifically used to determine the current player's matching time as the ratio of the first total matching time to the first total number of successful matches.
[0197] In some embodiments, the processing unit 13 is further configured to receive a matching success message sent by the client, the matching success message indicating that the current player has been successfully matched; and in response to the matching success message, to save the matching time of the current player.
[0198] In some embodiments, the processing unit 13 is specifically used to add the current player's matching time to the first total matching time, and to increment the first total number of successful matches by one.
[0199] In some embodiments, the historical matching time data is updated periodically.
[0200] In some embodiments, the game matching request includes the current player's identification information, and the determining unit 11 is specifically used to determine the target game type selected by the current player and the current player's skill level score in the target game based on the current player's identification information.
[0201] In some embodiments, the determining unit 11 is specifically used to obtain the target queue type selected by the current player by parsing the game matching request if the game matching request includes the target queue type selected by the current player.
[0202] In some embodiments, the matchmaking time data of the historical players is the matchmaking time data when the historical players were matched into a game.
[0203] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 10 The apparatus shown can perform the embodiments of the above-described methods, and the foregoing and other operations and / or functions of each module in the apparatus are respectively for implementing the method embodiments corresponding to the server. For the sake of brevity, they will not be described in detail here.
[0204] Figure 11 This is a schematic diagram of a game matchmaking time prediction device provided in an embodiment of this application. The prediction device is applied to a client-side application.
[0205] like Figure 11 As shown, the prediction device 20 includes:
[0206] Sending unit 21 is used to send a game match request to the server in response to the current player's game match operation, wherein the game match request is used to request the current player's match time;
[0207] The receiving unit 22 is used to receive the match time of the current player sent by the server. The match time of the current player is predicted based on the target game type selected by the current player, the current player's skill level score in the target game, and historical player match time data.
[0208] Display unit 23 is used to display the matchmaking time of the current player.
[0209] In some embodiments, the historical player matching time data includes the total matching time and total number of successful matches for historical players in each different skill level score range of different game types within a preset time period.
[0210] Wherein, the current player's matchmaking time is the ratio of the first total matchmaking time and the first total number of successful matchmakings corresponding to the target game type and the current player's skill level score in the historical player matchmaking time data.
[0211] In some embodiments, the historical player matching time data includes the historical player matching time data under different game types and different queue types within a preset time period. The matching time data under each combination includes the total matching time and the total number of successful matches under different skill level score ranges.
[0212] Wherein, the current player's matchmaking time is the ratio of the total first matchmaking time and the total number of first successful matchmakings corresponding to the target game type, the target queue type selected by the current player, and the current player's skill level score in the historical player matchmaking time data.
[0213] In some embodiments, the sending unit 21 is further configured to send a matching success message to the server in response to the current player's receiving match operation, the matching success message being used to indicate that the current player has successfully matched.
[0214] In some embodiments, the game matching request includes the current player's identification information, the server determining the target game type selected by the current player based on the current player's identification information, and the current player's skill level score in the target game.
[0215] In some embodiments, the game matchmaking request includes the target queue type selected by the current player.
[0216] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 11 The apparatus shown can perform the embodiments of the above-described methods, and the foregoing and other operations and / or functions of each module in the apparatus are respectively for implementing the method embodiments corresponding to the client. For the sake of brevity, they will not be described in detail here.
[0217] The apparatus of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in this application can be completed by integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the method disclosed in this application embodiment can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.
[0218] Figure 12 This is a schematic block diagram of an electronic device provided in an embodiment of this application. The electronic device can be a server or a terminal device, used to execute the above-described method embodiments.
[0219] like Figure 12 As shown, the electronic device 40 may include:
[0220] Memory 41 and memory 42 are provided. Memory 41 is used to store computer programs and to transfer the program code to memory 42. In other words, memory 42 can call and run computer programs from memory 41 to implement the methods in the embodiments of this application.
[0221] For example, the memory 42 can be used to execute the above-described method embodiments according to instructions in the computer program.
[0222] In some embodiments of this application, the memory 42 may include, but is not limited to:
[0223] General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
[0224] In some embodiments of this application, the memory 41 includes, but is not limited to:
[0225] Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).
[0226] In some embodiments of this application, the computer program may be divided into one or more modules, which are stored in the memory 41 and executed by the memory 42 to perform the method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the video production device.
[0227] like Figure 12 As shown, the electronic device 40 may further include:
[0228] Transceiver 40, transceiver 43 can be connected to memory 42 or memory 41.
[0229] The memory 42 can control the transceiver 43 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 43 may include a transmitter and a receiver. The transceiver 43 may further include antennas, and the number of antennas can be one or more.
[0230] It should be understood that the various components in the video production equipment are connected through a bus system, which includes not only a data bus, but also a power bus, a control bus, and a status signal bus.
[0231] According to one aspect of this application, a computer storage medium is provided that stores a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, embodiments of this application also provide a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.
[0232] According to another aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computing device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computing device to perform the method of the above-described method embodiments.
[0233] In other words, when implemented using software, it can be implemented wholly or partially in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).
[0234] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0235] 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 modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules 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 through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.
[0236] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.
[0237] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for predicting game matchmaking time, characterized in that, Applied to servers, including: In response to a game matchmaking request sent by the client for the current player, the target game type selected by the current player and the current player's skill level score in the target game are determined, and the game matchmaking request is used to request a matchmaking time for the current player; Based on the target game type, the player's skill level score, and historical player matchmaking time data, predict the current player's matchmaking time. The predicted match time for the current player is sent to the client for display. The step of predicting the matchmaking time of the current player based on the target game type, the skill level score, and historical player matchmaking time data includes: querying the target matchmaking time data corresponding to the target game type and the skill level score from the historical player matchmaking time data; and determining the matchmaking time of the current player based on the target matchmaking time data. The historical player matchmaking time data includes the total matchmaking time and total number of successful matches for each different skill level range in different game types within a preset time period. The step of querying the target matchmaking time data corresponding to the target game type and skill level score from the historical player matchmaking time data includes: querying the matchmaking time data corresponding to the target game type from the historical player matchmaking time data; and determining the first total matchmaking time and the first total number of successful matches within the skill level range where the current player's skill level score is located as the target matchmaking time data from the matchmaking time data corresponding to the target game type. Or The historical player matchmaking time data includes matchmaking time data for historical players under different game types and different queue types within a preset time period. The matchmaking time data for each combination includes the total matchmaking time and the total number of successful matches under different skill level score ranges. The step of querying the target matchmaking time data corresponding to the target game type and the skill level score from the historical player matchmaking time data includes: determining the target queue type selected by the current player; querying the matchmaking time data corresponding to the target game type from the historical player matchmaking time data; querying the matchmaking time data corresponding to the target queue type from the matchmaking time data corresponding to the target game type; and determining the first total matchmaking time and the first total number of successful matches within the skill level score range where the current player's skill level score is located in the matchmaking time data corresponding to the target queue type as the target matchmaking time data.
2. The method according to claim 1, characterized in that, Determining the current player's match time based on the target match time data includes: The ratio of the first total matching time to the first total number of successful matches is determined as the matching time for the current player.
3. The method according to claim 2, characterized in that, The method further includes: Receive a matching success message sent by the client, the matching success message being used to indicate that the current player has been successfully matched; In response to the successful match information, the match time of the current player is saved.
4. The method according to claim 3, characterized in that, The step of saving the current player's match time in response to the successful match information includes: The current player's matchmaking time is added to the first total matchmaking time, and the first total number of successful matches is incremented by one.
5. A method for predicting game matchmaking time, characterized in that, Application clients, including: In response to the current player's game matchmaking action, a game matchmaking request is sent to the server, the game matchmaking request being used to request a matchmaking time for the current player; The system receives the matchmaking time of the current player sent by the server. The matchmaking time of the current player is predicted based on the target game type selected by the current player, the current player's skill level score in the target game, and historical player matchmaking time data. Displays the current player's matchmaking time; The historical player matchmaking time data includes the total matchmaking time and total number of successful matches for each player in different skill level ranges across different game types within a preset time period; wherein, the current player's matchmaking time is the ratio of the first total matchmaking time and the first total number of successful matches corresponding to the target game type and the current player's skill level in the historical player matchmaking time data; or The historical player matchmaking time data includes matchmaking time data for historical players under different game types and different queue types within a preset time period. The matchmaking time data for each combination includes the total matchmaking time and the total number of successful matches under different skill level score ranges. The current player's matchmaking time is the ratio of the first total matchmaking time and the first total number of successful matches corresponding to the target game type, the target queue type selected by the current player, and the skill level score of the current player in the historical player's matchmaking time data.
6. The method according to claim 5, characterized in that, The method further includes: In response to the current player's accept match operation, a match success message is sent to the server, which indicates that the current player has been successfully matched.
7. A device for predicting game matchmaking time, characterized in that, Applied to servers, including: The determining unit is configured to, in response to a game matchmaking request sent by the client, determine the target game type selected by the current player and the current player's skill level score in the target game, wherein the game matchmaking request is used to request a matchmaking time for the current player; The prediction unit is used to predict the match time of the current player based on the target game type, the player's skill level score, and historical player match time data. The processing unit is used to send the predicted match time of the current player to the client for display; The prediction unit is specifically used to query the target match time data corresponding to the target game type and the skill level score from the historical player match time data; and determine the match time of the current player based on the target match time data. The historical player matchmaking time data includes the total matchmaking time and total number of successful matches for each different skill level range in different game types within a preset time period. The prediction unit is specifically used to query the matchmaking time data corresponding to the target game type from the historical player matchmaking time data; and to determine the first total matchmaking time and the first total number of successful matches within the skill level range of the current player in the matchmaking time data corresponding to the target game type as the target matchmaking time data; or The historical player matchmaking time data includes matchmaking time data for different game types and queue types within a preset time period. The matchmaking time data for each combination includes the total matchmaking time and total number of successful matches across different skill level ranges. The prediction unit is specifically used to determine the target queue type selected by the current player; query the matchmaking time data corresponding to the target game type from the historical player matchmaking time data; query the matchmaking time data corresponding to the target queue type from the matchmaking time data corresponding to the target game type; and determine the first total matchmaking time and the first total number of successful matches within the skill level range where the current player's skill level falls within the matchmaking time data corresponding to the target queue type as the target matchmaking time data.
8. The apparatus according to claim 7, characterized in that, The prediction unit is specifically used for: The ratio of the first total matching time to the first total number of successful matches is determined as the matching time for the current player.
9. The apparatus according to claim 8, characterized in that, The processing unit is also used for: Receive a matching success message sent by the client, the matching success message being used to indicate that the current player has been successfully matched; In response to the successful match information, the match time of the current player is saved.
10. The apparatus according to claim 9, characterized in that, The processing unit is specifically used for: The current player's matchmaking time is added to the first total matchmaking time, and the first total number of successful matches is incremented by one.
11. A device for predicting game matchmaking time, characterized in that, Applied to the client side, including: The sending unit is used to send a game matchmaking request to the server in response to the current player's game matchmaking operation. The game matchmaking request is used to request the matchmaking time for the current player. The receiving unit is used to receive the match time of the current player sent by the server. The match time of the current player is predicted based on the target game type selected by the current player, the current player's skill level score in the target game, and historical player match time data. The display unit is used to display the current player's matchmaking time; The historical player matchmaking time data includes the total matchmaking time and total number of successful matches for each player in different skill level ranges across different game types within a preset time period; wherein, the current player's matchmaking time is the ratio of the first total matchmaking time and the first total number of successful matches corresponding to the target game type and the current player's skill level in the historical player matchmaking time data; or The historical player matchmaking time data includes matchmaking time data for historical players under different game types and different queue types within a preset time period. The matchmaking time data for each combination includes the total matchmaking time and the total number of successful matches under different skill level score ranges. The current player's matchmaking time is the ratio of the first total matchmaking time and the first total number of successful matches corresponding to the target game type, the target queue type selected by the current player, and the skill level score of the current player in the historical player's matchmaking time data.
12. The apparatus according to claim 11, characterized in that, The transmitting unit is further configured to: In response to the current player's accept match operation, a match success message is sent to the server, which indicates that the current player has been successfully matched.
13. An electronic device, characterized in that, include: Memory, processor; The memory is used to store computer programs; The processor is configured to execute the computer program to implement the method as described in any one of claims 1 to 4 or 5 to 6.
14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 4 or 5 to 6.
15. A computer program product comprising a computer program and / or instructions, characterized in that, When the computer program and / or instructions are executed by a processor, they implement the method as described in any one of claims 1 to 4 or the method as described in any one of claims 5 to 6.
Citation Information
Patent Citations
Online game match beginning time prediction method and online game match beginning time prediction device
CN105956209A
