CN112169312A

CN112169312A - Queuing scheduling method, device, equipment and storage medium for cloud game service

Info

Publication number: CN112169312A
Application number: CN202011030787.8A
Authority: CN
Inventors: 杜晶; 林顺
Original assignee: Xiamen Yaji Software Co Ltd
Current assignee: Xiamen Yaji Software Co Ltd
Priority date: 2020-09-27
Filing date: 2020-09-27
Publication date: 2021-01-05

Abstract

The application relates to the technical field of computers, and discloses a queuing and scheduling method, device, equipment and storage medium for cloud game services. When the central server is not dispatched to the game server, the method applied to the user side comprises the following steps: receiving a cloud game response which is sent by a central server and contains at least one piece of regional server information used for queuing and a request identifier of a cloud game request; establishing connection with a regional server corresponding to at least one regional server information, and sending a queuing scheduling request comprising a request identifier to each regional server; receiving queuing scheduling information sent by each regional server; after determining that each queuing scheduling information is position updating information, updating the corresponding queuing position; and after determining that each queuing scheduling information contains the game server information, establishing connection with a game server corresponding to the game server information. The method and the system realize automatic and continuous scheduling of the game server for the user side in a queuing scheduling mode, and enable the user to know the queuing progress in time.

Description

Queuing scheduling method, device, equipment and storage medium for cloud game service

Technical Field

The present application relates to the field of computer technologies, and in particular, to a queuing scheduling method, apparatus, device, and storage medium for cloud game services.

Background

The cloud game is implemented by moving a game instance originally running at a user side to a cloud server to run, and the user side only transmits the operation of the user side to the cloud server in real time through a network, so that the game instance of the cloud server responds to the operation, the running result of the game is transmitted to the user side in real time, and pictures and sound are displayed on the user side. In the implementation of cloud games, the service resource scheduling of the cloud server needs to be completed first. Since the Game instance actually provides the cloud Game Service to the user terminal through a Game Service component ((GS), also called a Game server) running on the cloud server, the Service resource scheduling is to schedule an available GS for the user.

The service resource scheduling mode of the cloud server mainly comprises the following steps: the method comprises the following steps that firstly, a cloud server selects an available GS to be dispatched to a user side according to the load condition of each GS; and secondly, listing the load condition and the network quality of each GS on a display interface of the user side, and enabling the user to select one GS for connection. In any service resource scheduling manner, the cloud server may be in a full load state, and the available GS cannot be scheduled for the user side.

At present, the processing method for the situation that the available GS cannot be scheduled for the ue is as follows: and the user is prompted to fail in service resource scheduling or directly finish the cloud game, so that the user experience is poor.

Disclosure of Invention

The purpose of the present application is to solve at least one of the above technical drawbacks, and to provide the following solutions:

in a first aspect, a queuing and scheduling method for cloud game services is provided, where the method is applied to a user side, and after the user side sends a cloud game request to a central server side, each regional server side selected by the central server side is not scheduled to a game server side, and the method includes:

receiving a cloud game response sent by the central server, wherein the cloud game response comprises at least one piece of area server information used for queuing and a request identifier of the cloud game request;

establishing connection with at least one corresponding regional server based on the information of the at least one regional server, and sending a queuing scheduling request to each regional server establishing the connection, wherein the queuing scheduling request comprises the request identifier;

receiving queuing scheduling information sent by each regional server for establishing connection, wherein the queuing scheduling information comprises position updating information or game server information;

after determining that each queuing scheduling information is position updating information, updating a corresponding queuing position; or after determining that each piece of queuing scheduling information contains the game server information, selecting one piece of game server information, and establishing connection with the game server corresponding to the selected piece of game server information.

In some embodiments, after the connection is established with the corresponding at least one regional service end, the connection state is maintained with each regional service end that establishes the connection, and the queuing scheduling information sent by each regional service end that establishes the connection is received.

In some embodiments, the connection is established with the corresponding at least one regional service end in a timing mode, and the connection is disconnected after the queuing scheduling information of the corresponding regional service end is received.

In some embodiments, after selecting the game server information, the method further includes:

and sending a queue quitting request to each regional service end for establishing connection, wherein the queue quitting request is used for indicating the regional service end to remove the request identifier from the corresponding queue.

In a second aspect, an interaction method for cloud game service scheduling is provided, where the method is applied to a central server, and after the central server receives a cloud game request sent by a user, each regional server selected by the central server is not scheduled to a game server, where the cloud game request includes a channel identifier, and the method includes:

generating a request identification of the cloud game request;

selecting at least one regional server for queuing based on a channel identifier in the cloud game request;

acquiring regional server information of the at least one regional server;

and sending a cloud game response to the user side, wherein the cloud game response comprises at least one piece of regional server information used for queuing and the request identifier.

In some embodiments, said selecting at least one regional server for queuing based on the channel identification in the cloud game request comprises:

and selecting at least one regional service end, wherein the at least one regional service end has a queuing function, and the channel identifier of the at least one regional service end is the same as the channel identifier in the cloud game request.

In some embodiments, said selecting at least one regional server for queuing based on a channel identification contained in the cloud game request comprises:

performing first selection on a regional server meeting a preset condition, wherein the preset condition is that the regional server has a queuing function, and a channel identifier of the regional server is the same as a channel identifier in the cloud game request;

based on the region information and the operator information of the user side, performing priority sequencing on the result of the first selection;

and performing second selection based on the priority sequence to obtain at least one regional service end.

In a third aspect, an interactive method for cloud game service scheduling is provided, where the method is applied to a regional server, the regional server is selected by a central server to perform game server scheduling, and the regional server is not scheduled to a game server, and the regional server has a queuing function and maintains a queuing queue, and the method includes:

establishing connection with the user side, and receiving a queuing scheduling request sent by the user side, wherein the queuing scheduling request comprises a request identifier of a cloud game request;

determining a queuing position of the user side based on the request identifier and the queuing queue, wherein the queuing queue is a sequence formed by different request identifiers;

scheduling a game server based on the request identifier and the queuing position, and generating queuing scheduling information based on a scheduling result, wherein the queuing scheduling information comprises position updating information of the request identifier in the queuing queue or game server information of the scheduled game server;

and sending the queuing scheduling information to the user side.

In some embodiments, the method further comprises:

and circularly scheduling the queuing queue.

In some embodiments, the method further comprises:

and if any request identifier in the queue is dispatched to a game server, deleting the corresponding request identifier from the queue.

In some embodiments, the method further comprises:

and after receiving a queue exit request sent by the user side, deleting a request identifier corresponding to the user side from the queue.

In a fourth aspect, an interactive device for cloud game service scheduling is provided, where the device is configured at a user side, and after the user side sends a cloud game request to a central server side, none of regional server sides selected by the central server side is scheduled to a game server side, and the device includes:

the cloud game response receiving module is used for receiving a cloud game response sent by the central server, and the cloud game response comprises at least one piece of area server information used for queuing and a request identifier of the cloud game request;

the regional service end connection module is used for establishing connection with at least one corresponding regional service end based on the information of the at least one regional service end and sending a queuing scheduling request to each regional service end for establishing connection, wherein the queuing scheduling request comprises the request identifier;

the queuing scheduling information receiving module is used for receiving queuing scheduling information sent by each regional server for establishing connection, wherein the queuing scheduling information comprises position updating information or game server information;

a queuing position updating module, configured to update a corresponding queuing position after determining that each of the queuing scheduling information is position updating information;

and the game server connecting module is used for selecting one piece of game server information after determining that each piece of queuing scheduling information contains the game server information, and establishing connection with the game server corresponding to the selected game server information.

In some embodiments, the regional service connection module is further configured to:

and after the connection with the corresponding at least one regional service end is established, the connection state is kept with each regional service end of which the connection is established.

establishing connection with at least one corresponding regional server at regular time;

correspondingly, the apparatus further comprises a disconnection module for:

and disconnecting after receiving the queuing scheduling information of the corresponding regional service terminal.

In some embodiments, the apparatus further comprises an exit queued request sending module to:

and after the information of one game server is selected, sending a queue quitting request to each area server which establishes the connection, wherein the queue quitting request is used for indicating the area servers to remove the request identification from the corresponding queue.

In a fifth aspect, an interactive device for cloud game service scheduling is provided, where the device is configured at a central server, and after the central server receives a cloud game request sent by a user, each local server selected by the central server is not scheduled to a game server, where the cloud game request includes a channel identifier, and the device includes:

the request identifier generation module is used for generating a request identifier of the cloud game request;

the regional server selection module is used for selecting at least one regional server for queuing based on the channel identifier in the cloud game request;

the regional server information acquisition module is used for acquiring regional server information of the at least one regional server;

and the cloud game response sending module is used for sending a cloud game response to the user side, wherein the cloud game response comprises at least one piece of regional service side information used for queuing and the request identifier.

In some embodiments, the regional service end selection module is specifically configured to:

In a sixth aspect, an interactive device for cloud game service scheduling is provided, where the device is configured at a local server, the local server is selected by a central server to perform game server scheduling, and the local server is not scheduled to a game server, and the local server has a queuing function and maintains a queuing queue, and the device includes:

the queuing and scheduling request receiving module is used for establishing connection with the user side and receiving a queuing and scheduling request sent by the user side, wherein the queuing and scheduling request comprises a request identifier of a cloud game request;

a queuing position determining module, configured to determine a queuing position of the user side based on the request identifier and the queuing queue, where the queuing queue is a sequence formed by different request identifiers;

a queuing scheduling information generating module, configured to schedule a game server based on the request identifier and the queuing position, and generate queuing scheduling information based on a scheduling result, where the queuing scheduling information includes position update information of the request identifier in the queuing queue or game server information of the scheduled game server;

and the queuing scheduling information sending module is used for sending the queuing scheduling information to the user side.

In some embodiments, the apparatus further comprises a round robin scheduling module to:

and circularly scheduling the queuing queue.

In some embodiments, the apparatus further comprises a request identification deletion module to:

In some embodiments, the request identification deletion module is further to:

In a seventh aspect, an electronic device is provided, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the computer program, the processor implements any embodiment of the queuing scheduling method for cloud game services described above.

In an eighth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements any of the embodiments of the queuing scheduling method for cloud game services described above.

According to the queuing and scheduling method of the cloud game service, under the condition that each regional server selected by the central server is not scheduled to the game server, the user side receives cloud game responses sent by the central server, wherein the cloud game responses comprise at least one regional server information with a queuing function and a request identifier of a cloud game request; then, establishing connection with the regional service end corresponding to the regional service end information, and sending a queuing scheduling request containing the request identifier to the connected regional service end; and then, receiving queuing scheduling information sent by each regional service end, updating the queuing position of the user end based on the queuing scheduling information, or selecting game service end information based on the queuing scheduling information, and establishing connection with the game service end corresponding to the selected game service end information. The method and the device have the advantages that in the service scheduling process of the cloud games, the game server is continuously scheduled for the user side in a queuing scheduling mode, so that the process that the user frequently operates the cloud game connection due to the fact that the user is directly prompted to fail in scheduling or quit the cloud games can be avoided, the user can timely know the queuing progress of the service scheduling, and user experience is improved.

Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.

Drawings

The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

fig. 1 is a schematic diagram of a cloud game network architecture according to an embodiment of the present disclosure;

fig. 2 is a block diagram of a cloud server according to an embodiment of the present disclosure;

fig. 3 is a block diagram of a queuing and scheduling apparatus for cloud game services configured at a user end according to an embodiment of the present application;

fig. 4 is a block diagram of a queuing and scheduling apparatus for cloud game services configured at a central server according to an embodiment of the present application;

fig. 5 is a block diagram of a queuing and scheduling apparatus for cloud game services configured at a local server according to an embodiment of the present application;

fig. 6 is an interaction flowchart of queuing scheduling of a cloud game service according to an embodiment of the present application;

fig. 7 is a block diagram of an electronic device according to an embodiment of the present application;

fig. 8 is a flowchart of a queuing scheduling method applied to a cloud game service at a user end according to an embodiment of the present application;

fig. 9 is a flowchart of a queuing scheduling method applied to a cloud game service at a central server according to an embodiment of the present application;

fig. 10 is a flowchart of a queuing scheduling method applied to a cloud game service at a regional service end according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to the embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application.

As used herein, the singular forms "a", "an", "the" and "the" include plural referents unless the context clearly dictates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items. Relational terms such as "first" and "second," and the like, may be used herein only to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.

The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. To make the objects, technical solutions and advantages of the present application clearer, embodiments of the present application will be described below with reference to the accompanying drawings.

The following examples refer to the following main terms:

the center server side: namely, the Business Service component (BS), can be understood as a global scheduling server in the Service resource scheduling process of the cloud server, which corresponds to the overall cloud Service resource of the cloud game, and is at least used for providing an external access entry of the cloud server and managing each regional server inside the cloud server.

The regional service end: namely, a Domain Service component (DS), can be understood as a local scheduling server in the Service resource scheduling process, which corresponds to the cloud Service resource of a local area of a cloud game and is at least used for managing one or more game servers belonging to an area corresponding to the local scheduling server or a game channel. The game channel is used for distinguishing different ways for users to acquire and use the cloud game, for example, the vendor (such as different mobile phone brands) to which the user terminal device belongs may be/belongs to a certain channel. The whole network may have a plurality of regional service end DSs.

The game server side: namely, a Game Service component (GS) for controlling Game instances and providing cloud Game services to the user terminal. The game server is managed by the region server to which the game server belongs.

At present, when a user requests to schedule a game server GS of a cloud game, if there is no available GS to schedule, a user side can only feed back a result of scheduling failure or cloud game quitting to the user, and the user can only frequently send scheduling requests, which results in poor user experience. In order to solve the problem, the embodiment of the application provides a queuing scheduling scheme for cloud game services, which is implemented in a process that a cloud server schedules a game server GS for a user end, and the game server is continuously scheduled for the user end in a queuing scheduling manner, so that a process that a user frequently operates cloud game connections is avoided, the user can timely know the queuing progress of service scheduling, and user experience is improved.

In some embodiments, the queuing scheduling scheme of the cloud game service provided in the embodiments of the present application may be applied to a cloud game network. Fig. 1 is a cloud game network architecture according to an embodiment of the present disclosure. As shown in fig. 1, a cloud gaming network architecture may include: multiple clients, one or more cloud servers 100, and other devices involved in the cloud gaming service. In some embodiments, data interaction is performed between the user side and the cloud server 100 through a network, which may be a 4G network, a 5G network, or other networks for data interaction.

The User end (UA) may be any device capable of accessing the cloud server 100, for example, any device installed with software for accessing the cloud server 100, where the software for accessing the cloud server 100 may also be understood as software implementation of the User end. In some embodiments, the user side may include, but is not limited to: thin clients, general purpose computers, special purpose computers, gaming consoles, personal computers, laptop computers, tablet computing devices, mobile computing devices, portable gaming devices, cellular phones, smart phones, head-mounted displays, smart wearable devices, set-top boxes, streaming media interfaces/devices, smart televisions or networked displays, and the like. In some embodiments, the user side is at least configured to access a cloud game of the cloud server 100, receive a game operation input by a user, generate a corresponding operation instruction, and upload the operation instruction to the cloud server 100. The user can access the cloud game list of the cloud server 100 through the user side, and select the cloud game needing to schedule the service resource. In some embodiments, when there are multiple cloud servers 100, the multiple cloud servers 100 are distributed in different areas, and the user accesses the cloud server 100 corresponding to the area where the user is located through the user side.

The cloud server 100 may be any device capable of running a cloud game program, for example, any device installed with a cloud game program and software providing a cloud game service, where the software providing the cloud game service may also be understood as a software implementation of the cloud server 100. In some examples, the cloud server 100 may be a single server or a cluster of servers. In some embodiments, cloud server 100 may be a remote server, virtual computer, cloud gaming server, cloud application server, remote application server, digital media server, server for providing a game developer/game sponsor storefront (storefront), website server, terminal server, console server, or the like.

In some embodiments, a cloud gaming facilitator may deploy a cloud game in a cloud game service cluster, on which a node server may run a cloud game program, to which a plurality of cloud servers 100 shown in fig. 1 belong. In this embodiment, a user may access the cloud server 100 through a user side, and schedule a node server corresponding to a region where the user is located for the user side to log in a cloud game, and the user performs a game operation on the user side, so that the user side may upload a corresponding operation instruction to the node server. Then, the node server can calculate and generate a game picture by combining the operation instruction based on the execution logic of the cloud game program, and then feed the game picture back to the user side for display.

In some embodiments, the client sends a cloud game request to the cloud server 100 over a network. After receiving the cloud game request, the cloud server 100 may schedule a suitable game server GS for the user terminal according to the cloud game request, and feed back information of the scheduled game server GS to the user terminal through the network, so that the user terminal is connected to the game server GS. In some embodiments, the scheduled game service GS is at least used to handle the cloud game, encode video frames and audio frames of the cloud game, and stream the encoded video frames and audio frames to the user side for rendering and user interaction.

Fig. 2 is a block diagram of a cloud server 200 according to an embodiment of the present disclosure. In some embodiments, the cloud server 200 may be implemented as the cloud server 100 in fig. 1 or a part of the cloud server 100, and is used to provide cloud game services, such as running a cloud game program.

As shown in fig. 2, the cloud server 200 may be divided into a plurality of servers with different functions, for example, the servers may include: a central server 201, a regional server 202, a game server 203, and other servers involved in cloud game services. The cloud server 200 includes one or more central servers 201, each central server 201 manages one or more regional servers 202, and each regional server 202 manages one or more game servers 203.

The central server 201 is configured to receive a cloud game request sent by a user to the cloud server 200; and is used for managing each regional server 202 in the cloud server 200. In some embodiments, the central server 201 maintains the server information and status information of each regional server 202 it manages. In some embodiments, there may be a plurality of central servers 201. In this embodiment, a first-level load balancing LBS server may be added between the plurality of central service terminals 201 and the user terminal, and LBS is a mature technical scheme in the prior art, and can well complete selecting a suitable one from the plurality of central service terminals 201, and finally provide scheduling service for the user terminal. Moreover, the server information and the state information of all the regional servers 202 can be synchronized and stored in the same cloud database in real time, so that a plurality of central servers 201 can obtain the server information and the state information of the regional servers 202 from the database at the same time, and the regional servers 202 can be scheduled and managed by the central servers 201 in parallel. In some embodiments, the server information of the regional server 202 maintained by the central server 201 includes, but is not limited to, a channel identifier and a game identifier of a game channel supported by the regional server, and regional information and operator information corresponding to the regional server. The channel identification is information capable of uniquely representing a channel; the game identification is a unique representation of the cloud game. In some embodiments, the central server 201 may be a software device, a hardware device, or a combination of software and hardware.

In some embodiments, the regional service 202 may correspond to one region or a plurality of game channels, and one game channel may also correspond to a plurality of regional service 202. In some embodiments, the regional service 202 configures, before starting (through an operation and maintenance system or a person), a channel identifier of a game channel supported by the regional service, regional information of a region to which the regional service belongs and operator information corresponding to the regional service, and a game identifier list of a cloud game supported by the regional service, and registers and reports the DS information and the status information to the central service 201 when starting (by the operation and maintenance system or the person). In some embodiments, the regional server 202 maintains server information and status information of each game server 203 it manages, so that the game server 203 can be scheduled for the user side. In some embodiments, the server information of the game server 203 maintained by the regional server 202 includes, but is not limited to: the method comprises the following steps that channel identification of a game channel supported by the game server, a game identification list of cloud games supported by the game server, regional information of a region to which the game server belongs and operator information corresponding to the regional information are obtained; the status information includes whether the gaming server is idle or occupied. In some embodiments, the regional service provider 202 can be a software device, a hardware device, or a combination of software and hardware.

The game server 203 is used for controlling game instances, providing cloud service resources for the user side to control the cloud game, encoding video frames and audio frames of the cloud game, and streaming the encoded video frames and audio frames to the cloud game client side for rendering and user interaction. In some embodiments, the game server 203 is configured to at least obtain an operation instruction uploaded by the cloud game client, calculate and generate a game screen in combination with the operation instruction based on execution logic of the cloud game program, and then feed the game screen back to the cloud game client for display. In some embodiments, the game server 203 configures, before starting (by the operation and maintenance system or a person), the area server 202 to which the game server belongs, the channel identifiers of the game channels supported by the game server, the area information of the area to which the game server belongs and the corresponding operator information, and the game identifier list of the cloud games supported by the game server, and registers and reports the GS information and the state information to the area server 202 to which the game server belongs when being started (by the operation and maintenance system or the person). In some embodiments, the game server 203 may be a software device, a hardware device, or a combination of software and hardware.

Fig. 3 is a block diagram of a queuing and scheduling apparatus 300 for cloud game services configured at a user end according to an embodiment of the present application. In some embodiments, the queuing scheduling device 300 of the cloud game service configured at the user end can be implemented as the user end or a part of the user end in fig. 1.

As shown in fig. 3, the queuing scheduling apparatus 300 for cloud game services configured at the user end may include, but is not limited to, the following modules: the system comprises a cloud game response receiving module 301, a region server side connecting module 302, a queuing scheduling information receiving module 303, a queuing position updating module 304 and a game server side connecting module 305. The modules are described in detail as follows:

the cloud game response receiving module 301 is configured to receive a cloud game response sent by a center server, where the cloud game response includes at least one piece of queued area server information and a request identifier of a cloud game request. Specifically, after the user side UA sends the cloud game request to the central server BS, and the BS starts the queuing scheduling policy when the available game server GS is not found based on the cloud game request, the cloud game response receiving module 301 receives the cloud game response returned by the BS, which includes but is not limited to: at least one area server DS information for queuing a GS for the UA, and a request identification of the cloud game request of the UA. It is understood that each DS corresponding to the at least one DS information has a queuing function. The DS information is related information describing a corresponding DS, and may be, for example, a DS identifier, a channel list supported by the DS, a queue corresponding to the DS, and the like. The request identification of the cloud game request is a globally unique request identification generated by the BS for the cloud game request. In some embodiments, the relevant information of any cloud game request of any UA is stored in the database with its request identifier as a key, where the relevant information of the cloud game request includes but is not limited to: the request identification, the session identification connected with each end, the UA identification, the IP address of the UA, the channel identification of the cloud game selected by the UA, the game identification, the territorial information and the operator information of the UA and the like. In the subsequent process, the DS performs queuing scheduling for the UA according to a certain request identifier of the UA.

In some embodiments, if a GS to be connected is specified in the cloud game request and the BS determines that the state of the GS is non-idle or abnormal, then the BS determines that an available GS is not found. In some embodiments, the GS is not specified in the cloud game request, but rather the BS is requested to schedule any available GS, then the BS determines that an available GS is not found when none of the DSs selected by the BS are scheduled to an available GS.

In some embodiments, if the cloud game response received by the cloud game response receiving module 301 includes null information, which indicates that the BS does not select the DS for queuing, the UA needs to exit the queuing scheduling process of the cloud game service and give a prompt message that the user cannot perform queuing scheduling.

The regional service end connection module 302 is configured to establish a connection with at least one corresponding regional service end based on the at least one piece of regional service end information, and send a queuing scheduling request to each regional service end that establishes the connection. Specifically, the regional service connection module 302 determines each DS according to at least one DS information in the cloud game response; then, the UA establishes connection with each determined DS; then, the regional service connection module 302 sends the queuing scheduling request to each DS establishing connection, so that the corresponding DS performs queuing scheduling GS for the UA. The queuing and scheduling request is a request for triggering the DS to perform the queuing and scheduling GS based on the request identifier, and at least includes the request identifier. In some embodiments, the queued scheduling request may be sent by calling a preset DS scheduling interface, or sending a request for obtaining the latest queued position as a queued scheduling request to the DS.

In some embodiments, the regional service connection module 302 ensures that the UA maintains a connection status with each DS establishing a connection after the UA establishes a connection with each determined DS. In this embodiment, a long connection is established between the UA and each DS, and the UA communicates with the corresponding DS in real time. In this embodiment, the regional service connection module 302 only needs to send a queuing scheduling request once after the long connection is established, and each DS can actively perform timing scheduling according to the queuing scheduling request.

In some embodiments, the regional service connection module 302 monitors a timing period, and if the timing period arrives, the UA establishes a connection with the corresponding at least one DS. In this embodiment, a short connection is established between the UA and each DS, and the UA and the corresponding DS can communicate only after the short connection is established. Then, after each short connection is established, the regional service connection module 302 needs to send a queuing scheduling request to the corresponding DS, and each DS can only feed back queuing scheduling information to the UA after each short connection is established. In this embodiment, the queuing scheduling apparatus 300 for cloud game service configured at the user end further includes a disconnection module, and the disconnection module disconnects the connection between the UA and the corresponding DS after determining that the queuing scheduling information receiving module 303 receives the queuing scheduling information of the corresponding DS.

A queuing scheduling information receiving module 303, configured to receive queuing scheduling information sent by each regional server that establishes a connection, where the queuing scheduling information includes location update information or game server information. Specifically, after receiving the queuing scheduling request sent by the regional service end connection module 302, the DS of each queuing scheduling schedules queues and schedules the GS for the UA, and sends queuing scheduling information to the UA when a certain condition is met, so that the queuing scheduling information receiving module 303 may receive the queuing scheduling information returned by each DS. If the DS schedules UA to GS, then the queuing scheduling information is GS information. If the DS does not schedule to the GS for the UA, then the queued scheduling information is location update information identified by the request.

And a queuing position updating module 304, configured to update the corresponding queuing position after determining that each piece of queuing scheduling information is position updating information. Specifically, when detecting that there is no GS information in each received queuing scheduling information, the queuing position update module 304 updates the queuing position of the UA in the corresponding DS using the location update information as long as the location update information(s) is received. In some embodiments, the UA may display the queuing position, such as displaying the DS information that is the most forward of the queuing position and its queuing position, or, for example, displaying all DS information and queuing positions in the corresponding DS.

The game server connection module 305 is configured to select one piece of game server information after determining that each piece of queuing scheduling information includes the game server information, and establish connection with a game server corresponding to the selected game server information. Specifically, if the game server side connection module 305 detects that each queuing scheduling information received by the queuing scheduling information receiving module 303 contains at least one GS information, one GS information is selected; then, the UA establishes a connection with the GS corresponding to the selected GS information to run the cloud game. In some embodiments, the game server connection module 305 may randomly select one GS message. In some embodiments, the game server connection module 305 may select the GS information according to relevant information in the cloud game request sent by the UA. For example, the GS information in which the channel identification in the GS information is the same as the channel identification in the cloud game request is selected. For another example, on the basis of selecting the GS information with the same channel identifier, determining the priority and the sequence of the selected GS information according to whether the UA region information is the same as the region information in the GS information and/or whether the UA operator information is the same as the operator information in the GS information, and finally selecting the GS information with the highest priority to ensure that the GS with the best network quality is scheduled.

In some embodiments, for the GS information and the cloud game request, if the region information and the operator information of both are the same, the priority is the highest first priority; if only the region information or the operator information is the same, the priority is a second medium priority; and if the region information and the operator information of the two are different, the priority is the lowest third priority. In other embodiments, for the case that the region information and the operator information are the same only one, the priority level that the operator information is the same is further determined as a fourth priority level that is relatively higher, and the priority level that the region information is the same is determined as a fifth priority level that is relatively lower. It is understood that the first priority, the fourth priority, the fifth priority and the third priority are sequentially lower.

In some embodiments, the queue scheduling apparatus 300 for cloud game services configured at the user end further includes a queue exit request sending module, configured to send a queue exit request to each DS for establishing a connection after determining that the game service end connection module 305 selects one GS information. Specifically, if the UA determines that a connection is to be established with a GS (i.e., GS information is selected), then, in order to save resources and avoid scheduling errors, each DS does not need to queue and schedule the UA, and at this time, the dequeue request sending module sends a dequeue request to each DS that establishes a (past) connection, where the dequeue request is used to instruct the corresponding DS to remove the request identifier of the cloud game request corresponding to the UA from the corresponding queue. It should be noted that each DS for queuing maintains a queue, which is a sequence of different request identifiers. In specific implementation, a queuing queue in a DS adds a request identifier that is not duplicated to each original request identifier in the queuing queue to a list formed at the end of the queue according to the sequence in which the DS receives queuing scheduling requests sent by each UA.

In some embodiments, the dequeue request sending module is further configured to send a dequeue request to any DS that establishes a connection at any time. For example, if the user does not want to wait and triggers an active dequeue operation, the dequeue request sending module sends a dequeue request to all connected DSs (or DS selected by the user). For another example, when the exit queue request sending module detects that some DS queues too slowly, it may also send an exit queue request to the corresponding DS.

Fig. 4 is a block diagram of a queuing and scheduling apparatus 400 configured in a cloud game service at a central server according to an embodiment of the present application. In some embodiments, the queuing and scheduling apparatus 400 of the cloud game service configured in the central server may be implemented as the central server 201 or a part of the central server 201 in fig. 2.

As shown in fig. 4, the queuing and scheduling apparatus 400 of the cloud game service configured at the central server may include, but is not limited to, the following modules: the cloud game system comprises a request identifier generation module 401, a region server selection module 402, a region server information acquisition module 403 and a cloud game response sending module 404. The modules are described in detail as follows:

the request identifier generating module 401 is configured to generate a request identifier of a cloud game request after receiving the cloud game request sent by the UA. The cloud game request at least comprises a channel identifier of the cloud game selected by the UA.

A regional server selection module 402, configured to select at least one regional server for queuing based on the channel identifier in the cloud game request. Specifically, in the case where the BS determines the scheduled GS for the cloud game request for the first time, but does not find an available GS, the BS executes a queuing scheduling policy. Then, the regional service end selection module 402 selects at least one DS from the DSs managed by the BS, the selected DSs are used for queuing and scheduling GS for the UA, and the channel identifier in the DS information of the DSs is the same as the channel identifier in the cloud game request. The queuing and scheduling device 400 of the cloud game service configured at the central server maintains DS information of each DS under jurisdiction, where the DS information at least includes identifiers of each channel supported by the corresponding DS.

In some embodiments, when the regional service end selection module 402 selects at least one DS, all the DSs with the queuing function need to be screened out first. Then, one or more DSs having the same channel identification as that in the cloud game request in the DS information are selected from the DSs having the queuing function. As for the determination manner of whether the DS has the queuing function, in some embodiments, each DS information managed by the BS includes an attribute of whether the DS has the queuing function, and the area service side selection module 402 determines whether the corresponding DS has the queuing function by querying a value of the attribute; in other embodiments, the DS may report to the BS whether it has a queuing function after starting, and the regional service end selection module 402 determines whether the corresponding DS has the queuing function according to the reporting result.

In some embodiments, the process of the regional service selection module 402 selecting a DS may be: performing first selection on a DS meeting a preset condition, wherein the preset condition is that the DS has a queuing function, and a channel identifier of the DS is the same as a channel identifier in the cloud game request; based on the territory information and the operator information of the UA, the priority ranking is carried out on the result of the first selection; a second selection is made based on the priority ranking resulting in at least one DS. Specifically, the regional service selection module 402 first selects (i.e., first selects) one or more DSs from the DSs with a queuing function and targeting that the channel identifier in the DS information is the same as the channel identifier in the cloud game request. And then, determining the priority of each DS according to whether the area information of the UA is the same as the area information in the DS information and/or whether the operator information of the UA is the same as the operator information in the DS information, and sequencing the selected DSs according to the priority. This process can be seen in the prioritization process in the game server connection module 305. And finally, according to the service requirements (such as the lowest priority of the requirements, the minimum number of the DSs required and the like) of the service scheduling, selecting (namely, second selecting) the DSs again from the selected DSs to obtain the required at least one DS. Therefore, the DS matched with the UA region and the operator can be selected, and the adaptability of the dispatched DS is improved.

In some embodiments, if the DS cannot be selected by the regional service selection module 402 according to any of the above processes, the null information is used as a cloud game response of the BS to a cloud game request sent by the UA.

A regional server information obtaining module 403, configured to obtain regional server information of at least one regional server. Specifically, after the regional service side selection module 402 selects at least one DS, the regional service side information acquisition module 403 needs to acquire DS information of the selected DS from a relevant database of the DS managed by the BS. The acquired DS information is used as a cloud game response by the BS to a cloud game request sent by the UA.

A cloud game response sending module 404, configured to send the determined cloud game response to the UA. In some embodiments, the cloud game response includes null information that indicates to the UA to end the queuing scheduling process. In some embodiments, the cloud game response includes at least one of DS information and request identification for queuing. The DS information is used to indicate the UA to establish a connection with a corresponding DS, and the request identifier is to be used as information carried by the UA when sending the queuing scheduling request, so that the DS queries the relevant information of the cloud game request according to the request identifier.

Fig. 5 is a block diagram of a queuing and scheduling apparatus 500 for cloud game services configured at a local server according to an embodiment of the present application. In some embodiments, the queuing and scheduling apparatus 500 of the cloud game service configured in the local server can be implemented as the local server 202 or a part of the local server 202 in fig. 2. The DS in this embodiment of the application is selected by the BS for scheduling by the GS, but the DS is not scheduled to the GS, and the DS has a queuing function, and a queuing queue is maintained therein. The queuing queue here is a sequence of different request identifications.

As shown in fig. 5, the queuing scheduling apparatus 500 of the cloud game service configured in the local server may include, but is not limited to, the following modules: a queuing scheduling request receiving module 501, a queuing position determining module 502, a queuing scheduling information generating module 503 and a queuing scheduling information transmitting module 504. The modules are described in detail as follows:

a queuing scheduling request receiving module 501, configured to receive a queuing scheduling request sent by the UA after the DS establishes a connection with the UA, where the queuing scheduling request includes a request identifier of a cloud game request.

A queuing position determining module 502, configured to determine a queuing position of the UA based on the request identifier and the queuing queue. Specifically, the queue position determining module 502 first determines whether the request identifier is identical to the request identifier already in the queue. And if so, determining the position of the same request identifier in the queuing queue as the queuing position of the UA. If the same request identification does not exist in the queuing queue, the request identification is added to the tail of the queuing queue, and the position of the tail of the queue is the queuing position of the UA.

And a queuing scheduling information generating module 503, configured to schedule a GS based on the request identifier and the queuing position, and generate queuing scheduling information based on the scheduling result. Specifically, if the queuing scheduling information generating module 503 determines that the queuing position of the request identifier is the first of the queuing queue, it schedules a GS for the UA. When the scheduling is performed to the GS, the GS information of the GS is used as queuing scheduling information. And if the request is not scheduled to the GS, identifying the position updating information of the request in the queuing queue as queuing scheduling information. In some embodiments, if the queuing scheduling information generating module 503 determines that the queuing position identified by the request is not the first of the queuing queue, the GS information of the GS will not be used as the queuing scheduling information, but the position update information will be used as the queuing scheduling information even if the GS is scheduled for the request. The GS information is specified from GS information of GS under the control of the DS. Location update information includes, but is not limited to: the request identifies the current queue position in the queue, the estimate of the length of time to wait, the length of the queue, etc.

In some embodiments, the process of the queuing scheduling information generating module 503 scheduling a GS for the UA is: and searching the channel identification, the game identification, the UA region information, the operator information and other related information in the cloud game request according to the request identification. Then, one GS is selected from the GS according to the inquired information and the GS information of each GS governed by the DS. For example, the selected GS can run the cloud game selected by the user by selecting the GS in which the channel identifier in the GS information is the same as the channel identifier in the cloud game request and the game identifier list in the GS information includes the game identifier in the cloud game request. Then, the GS whose state information is free in the GS information is selected again from the selected GS, and the available load is secured. Finally, one GS is randomly selected from the selected multiple GS. For another example, on the basis of the result selected according to the channel identifier, the game identifier, and the idle state information, the priority and the order of each selected GS may be further determined according to the region information and the operator information of the UA, and the region information and the operator information of each GS. This process can be seen in the prioritization process in the game server connection module 305. Finally, the highest priority GS is selected. So that the DS can schedule the optimal GS for the UA.

In some embodiments, the queuing and scheduling apparatus 500 for cloud game service configured in the local server further includes a round-robin scheduling module for: and circularly scheduling the queuing queue. In this embodiment, as long as there is a request identifier not scheduled to the GS in the queuing queue, the round-robin scheduling module triggers the DS to schedule the GS periodically and cyclically for each request identifier in the queuing queue. As long as the request identification is in the queue, the DS will schedule GS for its round robin. The process of the circular scheduling is irrelevant to whether a queuing scheduling request sent by the UA corresponding to the request identifier in the queuing queue is received or not, is irrelevant to whether a certain request identifier in the queuing queue is scheduled to the GS or not, and is also irrelevant to communication modes such as long connection, short connection and the like between the DS and the UA.

A queuing scheduling information sending module 504, configured to send queuing scheduling information to the UA.

In some embodiments, a short connection is established between the DS and the UA. In this embodiment, although the DS may identify the round-robin scheduling for each request, when the UA is not connected to the DS, the queuing scheduling information sending module 504 cannot send the scheduled GS information or location update information of the GS to the UA in time. And if the GS information cannot be sent to the UA, the available GS can continuously participate in the scheduling of the subsequent request identifier until the UA corresponding to the first request identifier of the queuing queue is connected with the DS, and the DS schedules the request identifier to the GS, the queuing scheduling of one request identifier is completed, and the queuing list is updated. Although the queuing scheduling method of the short connection will increase some unnecessary communication overhead and waste of DS resources, it can still automatically and continuously queue and schedule GS for the UA.

In some embodiments, a long connection is established between the DS and the UA. In this embodiment, in the process of circularly scheduling the queuing queue by the DS, as long as the DS schedules the GS for the corresponding UA, the queuing scheduling information sending module 504 can send the queuing scheduling information including the GS information of the GS to the UA in time, so that the UA can be connected to the GS in time; or, as long as the position of the request identifier corresponding to the UA in the queuing queue is updated, the queuing scheduling information sending module 504 can send the queuing scheduling information containing the latest position update information corresponding to the UA in time, so that the UA updates the queuing position in time, and user experience is improved. In this embodiment, the queuing scheduling information sending module 504 may further control the frequency of sending the queuing scheduling information to the UA, so as to optimize the consumption of network and system resources connected to the entire queuing queue.

In some embodiments, the queuing and scheduling apparatus 500 of the cloud game service configured in the regional service terminal further includes a request identifier deleting module configured to: and for any request identifier in the queue, if the request identifier is scheduled to the GS, deleting the corresponding request identifier from the queue. Specifically, when detecting that the queuing scheduling information generation module 503 schedules a certain request identifier to the GS, the request identifier deletion module deletes the request identifier from the queuing table, so as to avoid cloud resource waste caused by repeated queuing.

In some embodiments, the request identification deletion module is further to: and after receiving a queue exit request sent by the UA, deleting a request identifier corresponding to the UA from the queue. Specifically, the request identifier deleting module may passively receive a request for exiting from the queue sent by the UA in addition to actively deleting the request identifier, and further delete the request identifier corresponding to the UA from the queue.

In some embodiments, in the case of a long connection established between the DS and the UA, the DS may instantly detect the active state of the UA over the long connection. If a certain UA exits in the queuing and scheduling process, the request identifier deleting module can delete the request identifier corresponding to the UA from the queuing and scheduling process, so that an invalid queuing and scheduling process is avoided, and the waste of cloud resources is reduced.

In some embodiments, no matter how the request identifier deleting module deletes a certain request identifier from the queuing queue, the deleting operation may cause the queuing positions of other request identifiers in the queuing queue to be updated, the queuing scheduling information generating module 503 needs to generate queuing scheduling information containing position update information (i.e. position update information of other request identifiers) for the other request identifiers, and the queuing scheduling information sending module 504 sends the queuing scheduling information to the corresponding UA.

Fig. 6 is an interaction flowchart of queuing scheduling of a cloud game service according to an embodiment of the present application. In some embodiments, the interactive flow of queuing scheduling for cloud gaming services may be implemented based on the cloud gaming network architecture in fig. 1 and the cloud gaming service end 200 in fig. 2. The execution subject in the interactive process at least includes a user side UA, a central server 201 and a regional server 202, and the interactive process includes the following steps 601 to 610:

601. the client sends a cloud game request to the central server 201. The cloud game request at least comprises a channel identifier and a game identifier of a cloud game selected by the UA, and territorial information and operator information of the UA.

602. The central server 201 generates a request identification of the cloud game request, and when no available game server is found, selects at least one regional server 202 for queuing based on a channel identification in the cloud game request.

603. The central server 201 obtains the regional server information of at least one regional server 202.

604. The central server 201 sends a cloud game response to the client. The cloud game response comprises at least one area server information and a request identification which are used for queuing.

605. The user side establishes a connection with at least one corresponding regional server 202 based on the information of at least one regional server, and sends a queuing scheduling request to each regional server 202 establishing the connection, wherein the queuing scheduling request includes a request identifier. Here, the connection established between the ue and the local server 202 can be a long connection (keep connection) or a short connection (disconnect after one communication).

606. The regional server 202 determines the queuing position of the user side based on the request identifier and the queuing queue maintained therein, schedules a game server 203 based on the request identifier and the queuing position, and generates queuing scheduling information based on the scheduling result. The queuing scheduling information includes the position update information of the request identifier in the queuing queue or the game server information of the scheduled game server 203.

607. The regional service 202 sends the queuing scheduling information to the user.

608. If the short connection is established between the ue and the local server 202 in step 605, the connection is disconnected.

609. And after determining that each queuing scheduling information is the position updating information, the user side updates the corresponding queuing position.

610. After determining that each queuing scheduling information contains the game server information, the user terminal selects one game server information and establishes connection with the game server 203 corresponding to the selected game server information.

An embodiment of the present application provides an electronic device, as shown in fig. 7, an electronic device 700 shown in fig. 7 includes: a processor 701 and a memory 703. The processor 701 is coupled to a memory 703, such as via a bus 702. Further, the electronic device 700 may also include a transceiver 704. It should be noted that the transceiver 704 is not limited to one in practical applications, and the structure of the electronic device 700 is not limited to the embodiment of the present application.

The processor 701 is applied to the embodiment of the present application to implement the function of the queuing and scheduling apparatus for the cloud game service configured at the user end shown in fig. 3, or to implement the function of the queuing and scheduling apparatus for the cloud game service configured at the central service end shown in fig. 4, or to implement the function of the queuing and scheduling apparatus for the cloud game service configured at the regional service end shown in fig. 5.

The processor 701 may be a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 701 may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others.

Bus 702 may include a path that transfers information between the above components. The bus 702 may be a PCI bus or an EISA bus, etc. The bus 702 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus.

The memory 703 may be, but is not limited to, ROM or other type of static storage device that can store static information and instructions, RAM or other type of dynamic storage device that can store information and instructions, EEPROM, CD-ROM or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

The memory 703 is used for storing application program codes for executing the present invention, and is controlled by the processor 701. The processor 701 is configured to execute application program codes stored in the memory 703 to implement the operation of the queuing and scheduling apparatus of the cloud game service configured at the user end shown in fig. 3, the operation of the queuing and scheduling apparatus of the cloud game service configured at the central service end shown in fig. 4, or the operation of the queuing and scheduling apparatus of the cloud game service configured at the regional service end shown in fig. 5.

The electronic device provided by the embodiment of the application comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, and when the processor executes the program, compared with the prior art, the electronic device can realize that: under the condition that each regional server selected by the central server is not dispatched to the game server, the user side receives a cloud game response sent by the central server, wherein the cloud game response comprises at least one regional server information with a queuing function and a request identifier of a cloud game request; then, establishing connection with the regional service end corresponding to the regional service end information, and sending a queuing scheduling request containing the request identifier to the connected regional service end; and then, receiving queuing scheduling information sent by each regional service end, updating the queuing position of the user end based on the queuing scheduling information, or selecting game service end information based on the queuing scheduling information, and establishing connection with the game service end corresponding to the selected game service end information. The method and the device have the advantages that in the service scheduling process of the cloud games, the game server is continuously scheduled for the user side in a queuing scheduling mode, so that the process that the user frequently operates the cloud game connection due to the fact that the user is directly prompted to fail in scheduling or quit the cloud games can be avoided, the user can timely know the queuing progress of the service scheduling, and user experience is improved.

Embodiments of the present application provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the steps of the embodiments of the queuing scheduling method for cloud game services. Compared with the prior art, under the condition that each regional server selected by the central server is not dispatched to the game server, the user side receives cloud game responses sent by the central server, wherein the cloud game responses comprise at least one regional server information with a queuing function and a request identifier of a cloud game request; then, establishing connection with the regional service end corresponding to the regional service end information, and sending a queuing scheduling request containing the request identifier to the connected regional service end; and then, receiving queuing scheduling information sent by each regional service end, updating the queuing position of the user end based on the queuing scheduling information, or selecting game service end information based on the queuing scheduling information, and establishing connection with the game service end corresponding to the selected game service end information. The method and the device have the advantages that in the service scheduling process of the cloud games, the game server is continuously scheduled for the user side in a queuing scheduling mode, so that the process that the user frequently operates the cloud game connection due to the fact that the user is directly prompted to fail in scheduling or quit the cloud games can be avoided, the user can timely know the queuing progress of the service scheduling, and user experience is improved.

Fig. 8 is a flowchart of a queuing scheduling method applied to a cloud game service at a user end according to an embodiment of the present application. The method comprises the following steps 801 to 805 that the execution main body is a user side UA, after the UA sends a cloud game request to a central server BS, all regional server DSs selected by the BS are not dispatched to a game server GS:

801. and receiving a cloud game response sent by the central server, wherein the cloud game response comprises at least one piece of area server information used for queuing and a request identifier of a cloud game request.

Specifically, after the UA sends the cloud game request to the BS, the BS starts a queuing scheduling policy when the BS does not find an available GS based on the cloud game request, and the reception by the UA of the cloud game response returned by the BS includes, but is not limited to: at least one area server DS information for queuing a GS for the UA, and a request identification of the cloud game request of the UA. It is understood that each DS corresponding to the at least one DS information has a queuing function. The DS information is related information describing a corresponding DS, and may be, for example, a DS identifier, a channel list supported by the DS, a queue corresponding to the DS, and the like. The request identification of the cloud game request is a globally unique request identification generated by the BS for the cloud game request. In some embodiments, the relevant information of any cloud game request of any UA is stored in the database with its request identifier as a key, where the relevant information of the cloud game request includes but is not limited to: the request identification, the session identification connected with each end, the UA identification, the IP address of the UA, the channel identification of the cloud game selected by the UA, the game identification, the territorial information and the operator information of the UA and the like. In the subsequent process, the DS performs queuing scheduling for the UA according to a certain request identifier of the UA.

In some embodiments, if the received cloud game response includes null information, which indicates that the BS does not select the DS for queuing, the UA needs to exit the queuing scheduling process of the cloud game service and give a prompt to the user that queuing scheduling cannot be performed.

802. And establishing connection with at least one corresponding regional service terminal based on the information of at least one regional service terminal, and sending a queuing scheduling request to each connected regional service terminal, wherein the queuing scheduling request comprises a request identifier.

Specifically, the UA determines each DS according to at least one DS information in the cloud game response; then, the UA establishes connection with each determined DS; then, the UA sends a queuing scheduling request to each DS establishing a connection, so that the corresponding DS performs queuing scheduling GS for the UA. The queuing and scheduling request is a request for triggering the DS to perform the queuing and scheduling GS based on the request identifier, and at least includes the request identifier. In some embodiments, the queued scheduling request may be sent by calling a preset DS scheduling interface, or sending a request for obtaining the latest queued position as a queued scheduling request to the DS.

In some embodiments, after the UA establishes a connection with each determined DS, the UA maintains a connection state with each DS that establishes a connection. In this embodiment, a long connection is established between the UA and each DS, and the UA communicates with the corresponding DS in real time. In this embodiment, the UA only needs to send a queuing scheduling request once after the long connection is established, and each DS may actively perform timing scheduling according to the queuing scheduling request.

In some embodiments, the UA monitors a timing period and, if the timing period arrives, the UA establishes a connection with the corresponding at least one DS. In this embodiment, a short connection is established between the UA and each DS, and the UA and the corresponding DS can communicate only after the short connection is established. Then, after each short connection is established, the UA needs to send a queuing scheduling request to the corresponding DS, and each DS can only feed back queuing scheduling information to the UA after each short connection is established. Accordingly, after receiving the queuing scheduling information of the corresponding DS, the UA disconnects the connection between the UA and the corresponding DS.

803. And receiving queuing scheduling information sent by each regional server for establishing connection, wherein the queuing scheduling information comprises position updating information or game server information.

Specifically, after receiving a queuing scheduling request sent by the UA, the DS of each queuing scheduling schedules the GS for the UA, and sends queuing scheduling information to the UA when a certain condition is met, so that the UA can receive the queuing scheduling information returned by each DS. If the DS schedules UA to GS, then the queuing scheduling information is GS information. The queuing scheduling information is location update information if the DS has not scheduled a UA to the GS.

804. And after determining that each queuing scheduling information is position updating information, updating the corresponding queuing position.

Specifically, when detecting that there is no GS information in each received queuing scheduling information, the UA updates the queuing position of the UA in the corresponding DS using the location update information as long as the location update information(s) is received. In some embodiments, the UA may display the queuing position, such as displaying the DS information that is the most forward of the queuing position and its queuing position, or, for example, displaying all DS information and queuing positions in the corresponding DS.

805. And after determining that each queuing scheduling information contains the game server information, selecting one game server information, and establishing connection with the game server corresponding to the selected game server information.

Specifically, if the UA detects that each received queuing scheduling information includes at least one GS information, one GS information is selected; then, the UA establishes a connection with the GS corresponding to the selected GS information to run the cloud game.

In some embodiments, the UA may randomly select one GS information. In some embodiments, the UA may select the GS information based on relevant information in a cloud game request sent by the UA. For example, the GS information in which the channel identification in the GS information is the same as the channel identification in the cloud game request is selected. For another example, on the basis of selecting the GS information with the same channel identifier, determining the priority and the sequence of the selected GS information according to whether the UA region information is the same as the region information in the GS information and/or whether the UA operator information is the same as the operator information in the GS information, and finally selecting the GS information with the highest priority to ensure that the GS with the best network quality is scheduled.

In some embodiments, the above method further comprises: after selecting a game server information, a request for quitting queuing is sent to each DS establishing connection. Specifically, if the UA determines that a connection is to be established with a GS (that is, GS information is selected), then, in order to save resources and avoid scheduling errors, each DS does not need to queue and schedule the UA, and at this time, the UA sends a dequeue request to each connected (past) DS, where the dequeue request is used to instruct the corresponding DS to shift the request identifier of the cloud game request corresponding to the UA out of the corresponding queue. It should be noted that each DS for queuing maintains a queue, which is a sequence of different request identifiers. In specific implementation, a queuing queue in a DS adds a request identifier that is not duplicated to each original request identifier in the queuing queue to a list formed at the end of the queue according to the sequence in which the DS receives queuing scheduling requests sent by each UA.

In some embodiments, the UA may issue a dequeue request to any DS that establishes a connection at any one time. For example, if the user does not want to wait and triggers an active dequeue operation, the UA sends a dequeue request to all connected DSs (or DS selected by the user). For another example, when the UA detects that some DS queues too slowly, it may also send a quit queuing request to the corresponding DS.

Fig. 9 is a flowchart of a queuing scheduling method applied to a cloud game service at a central server according to an embodiment of the present application. The method is characterized in that an execution main body is a central server BS, after the BS receives a cloud game request sent by a user side UA, all selected regional server DSs are not dispatched to a game server GS, and the method comprises the following steps 901 to 904:

901. a request identification of the cloud game request is generated.

Specifically, after receiving a cloud game request sent by the UA, the BS generates a request identifier of the cloud game request. The cloud game request at least comprises a channel identifier of the cloud game selected by the UA.

902. At least one regional server is selected for queuing based on the channel identification in the cloud game request.

Specifically, in the case where the BS determines the scheduled GS for the cloud game request for the first time, but does not find an available GS, the BS executes a queuing scheduling policy. Then the BS selects at least one DS from among its administered DSs, these selected DSs are used for queuing scheduling GS for the UA, and the channel identification in the DS information of these DSs is the same as the channel identification in the cloud game request. Wherein, the BS maintains DS information of each DS administered by the BS, and the DS information at least comprises each channel identifier supported by the corresponding DS.

In some embodiments, when the BS selects at least one DS, it first needs to screen all the DSs with queuing function. Then, one or more DSs having the same channel identification as that in the cloud game request in the DS information are selected from the DSs having the queuing function. As for the determination manner of whether the DS has the queuing function, in some embodiments, each DS information managed by the BS includes an attribute of whether the DS has the queuing function, and the BS determines whether the corresponding DS has the queuing function by querying a value of the attribute; in other embodiments, the DS may report to the BS whether it has a queuing function after starting, and the BS determines whether the corresponding DS has the queuing function according to the reporting result.

In some embodiments, the process of BS selecting DS may be: performing first selection on a DS meeting a preset condition, wherein the preset condition is that the DS has a queuing function, and a channel identifier of the DS is the same as a channel identifier in the cloud game request; based on the territory information and the operator information of the UA, the priority ranking is carried out on the result of the first selection; a second selection is made based on the priority ranking resulting in at least one DS. Specifically, the BS first selects (i.e., first selects) one or more DSs from among the DSs with a target that the BS has a queuing function and that the channel identifier in the DS information is the same as the channel identifier in the cloud game request. And then, determining the priority of each DS according to whether the area information of the UA is the same as the area information in the DS information and/or whether the operator information of the UA is the same as the operator information in the DS information, and sequencing the selected DSs according to the priority. This process can be referred to as the priority determination process in the above embodiments. And finally, according to the service requirements (such as the lowest priority of the requirements, the minimum number of the DSs required and the like) of the service scheduling, selecting (namely, second selecting) the DSs again from the selected DSs to obtain the required at least one DS. Therefore, the DS matched with the UA region and the operator can be selected, and the adaptability of the dispatched DS is improved.

In some embodiments, if the BS cannot select the DS according to any of the above procedures, the null information is used as a cloud game response to a cloud game request sent by the UA.

903. And acquiring regional server information of at least one regional server.

Specifically, after selecting at least one DS, the BS needs to acquire DS information of the selected DSs from a relational database, which it manages DSs. The acquired DS information is used as a cloud game response to a cloud game request sent by the UA.

904. And sending a cloud game response to the user terminal, wherein the cloud game response comprises at least one area server terminal information and a request identifier used for queuing.

In some embodiments, the cloud game response includes null information that indicates to the UA to end the queuing scheduling process. In some embodiments, the cloud game response includes at least one of DS information and request identification for queuing. The DS information is used to indicate the UA to establish a connection with a corresponding DS, and the request identifier is to be used as information carried by the UA when sending the queuing scheduling request, so that the DS queries the relevant information of the cloud game request according to the request identifier.

Fig. 10 is a flowchart of a queuing scheduling method applied to a cloud game service at a regional service end according to an embodiment of the present application. The main implementation of the method is a regional service end DS, the DS is selected by a BS to perform the scheduling of a GS, but the DS is not scheduled to the GS, and the DS has a queuing function, and a queuing queue is maintained inside the DS. The queuing queue here is a sequence of different request identifications. The method comprises the following steps 1001 to 1004:

1001. and establishing connection with a user terminal, and receiving a queuing scheduling request sent by the user terminal, wherein the queuing scheduling request comprises a request identifier of the cloud game request.

1002. And determining the queuing position of the user side based on the request identifications and a queuing queue, wherein the queuing queue is a sequence formed by different request identifications.

Specifically, the DS first determines whether the request identifier is duplicated with a request identifier already in the queue. And if so, determining the position of the same request identifier in the queuing queue as the queuing position of the UA. If the same request identification does not exist in the queuing queue, the request identification is added to the tail of the queuing queue, and the position of the tail of the queue is the queuing position of the UA.

1003. And scheduling a game server based on the request identifier and the queuing position, and generating queuing scheduling information based on the scheduling result, wherein the queuing scheduling information comprises position updating information of the request identifier in the queuing queue or game server information of the scheduled game server.

Specifically, if the DS determines that the queuing position of the request identifier is the first of the queuing queue, a GS is scheduled for the UA. When the scheduling is performed to the GS, the GS information of the GS is used as queuing scheduling information. And if the request is not scheduled to the GS, identifying the position updating information of the request in the queuing queue as queuing scheduling information. In some embodiments, if the DS determines that the queued position identified by the request is not the first of the queued queues, then even if the GS is scheduled for it, the GS information of the GS will not be used as the queued scheduling information, but instead the location update information will be used as the queued scheduling information. The GS information is specified from GS information of GS under the control of the DS. Location update information includes, but is not limited to: the request identifies the current queue position in the queue, the estimate of the length of time to wait, the length of the queue, etc.

In some embodiments, the process for the DS to schedule one GS for the UA is: and searching the channel identification, the game identification, the UA region information, the operator information and other related information in the cloud game request according to the request identification. Then, one GS is selected from the GS according to the inquired information and the GS information of each GS governed by the DS. For example, the selected GS can run the cloud game selected by the user by selecting the GS in which the channel identifier in the GS information is the same as the channel identifier in the cloud game request and the game identifier list in the GS information includes the game identifier in the cloud game request. Then, the GS whose state information is free in the GS information is selected again from the selected GS, and the available load is secured. Finally, one GS is randomly selected from the selected multiple GS. For another example, on the basis of the result selected according to the channel identifier, the game identifier, and the idle state information, the priority and the order of each selected GS may be further determined according to the region information and the operator information of the UA, and the region information and the operator information of each GS. This process can be referred to as the priority determination process in the above embodiments. Finally, the highest priority GS is selected. So that the DS can schedule the optimal GS for the UA.

In some embodiments, the above method further comprises: and circularly scheduling the queuing queue. In this embodiment, as long as there are request identifiers not scheduled to the GS in the queuing queue, the DS schedules the GS periodically and cyclically for each request identifier in the queuing queue. As long as the request identification is in the queue, the DS will schedule GS for its round robin. The process of the circular scheduling is irrelevant to whether a queuing scheduling request sent by the UA corresponding to the request identifier in the queuing queue is received or not, is irrelevant to whether a certain request identifier in the queuing queue is scheduled to the GS or not, and is also irrelevant to communication modes such as long connection, short connection and the like between the DS and the UA.

1004. And sending queuing scheduling information to the user side.

In some embodiments, a short connection is established between the DS and the UA. In this embodiment, although the DS identifies the round-robin scheduling for each request, when the UA is not connected to the DS, the DS cannot send the GS information or the location update information of the scheduled GS to the UA in time. And if the GS information cannot be sent to the UA, the available GS can continuously participate in the scheduling of the subsequent request identifier until the UA corresponding to the first request identifier of the queuing queue is connected with the DS, and the DS schedules the request identifier to the GS, the queuing scheduling of one request identifier is completed, and the queuing list is updated. Although the queuing scheduling method of the short connection will increase some unnecessary communication overhead and waste of DS resources, it can still automatically and continuously queue and schedule GS for the UA.

In some embodiments, a long connection is established between the DS and the UA. In this embodiment, in the process that the DS circularly schedules the queuing queue, as long as the DS schedules the GS for the corresponding UA, the DS can send the queuing scheduling information including the GS information of the GS to the UA in time, so that the UA can be connected with the GS in time; or, as long as the position of the request identifier corresponding to the UA in the queuing queue is updated, the DS may send the queuing scheduling information including the latest position update information corresponding to the UA in time to the UA, so that the UA updates the queuing position in time, and user experience is improved. In this embodiment, the DS may also control the frequency of sending queuing scheduling information to the UA, thereby optimizing the consumption of network and system resources connected to the entire queuing queue.

In some embodiments, the above method further comprises: and for any request identifier in the queue, if the request identifier is scheduled to the GS, deleting the corresponding request identifier from the queue. Specifically, when the DS schedules a certain request identifier to the GS, the request identifier is deleted from the queuing table, so that cloud resource waste caused by repeated queuing is avoided.

In some embodiments, the above method further comprises: and after receiving a queue exit request sent by the UA, deleting a request identifier corresponding to the UA from the queue. Specifically, the DS may passively receive a request to exit from the queue sent by the UA in addition to actively deleting the request identifier, and further delete the request identifier corresponding to the UA from the queue.

In some embodiments, in the case of a long connection established between the DS and the UA, the DS may instantly detect the active state of the UA over the long connection. If a UA exits in the queuing and scheduling process, the DS can delete the request identifier corresponding to the UA from the queuing and scheduling process, so that an invalid queuing and scheduling process is avoided, and the waste of cloud resources is reduced.

In some embodiments, no matter what reason the DS deletes a certain request identifier from the queuing queue, the deletion may cause the queuing position of other request identifiers in the queuing queue to be updated, and then the DS needs to generate queuing scheduling information containing position update information for other request identifiers and send the queuing scheduling information to the corresponding UA, so that each UA can update its queuing position in time.

It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. For example, step 608 in fig. 6 may not be performed, or may be performed after step 609 or step 610. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

The foregoing is only a partial embodiment of the present application, and it should be noted that, for those skilled in the art, several modifications and decorations can be made without departing from the principle of the present application, and these modifications and decorations should also be regarded as the protection scope of the present application.

Claims

1. A queuing and scheduling method for cloud game service is characterized in that the method is applied to a user side, after the user side sends a cloud game request to a central server side, all regional server sides selected by the central server side are not scheduled to a game server side, and the method comprises the following steps:

2. A queuing and scheduling method for cloud game services is characterized in that the method is applied to a central server, after the central server receives a cloud game request sent by a user end, all regional servers selected by the central server are not scheduled to a game server, wherein the cloud game request comprises a channel identifier, and the method comprises the following steps:

generating a request identification of the cloud game request;

acquiring regional server information of the at least one regional server;

3. The method of claim 2, wherein selecting at least one regional server for queuing based on the channel identification in the cloud game request comprises:

4. A queuing and scheduling method for cloud game service is characterized in that the method is applied to a regional service end, the regional service end is selected by a central service end to schedule a game service end, the regional service end is not scheduled to the game service end, the regional service end has a queuing function and maintains a queuing queue, and the method comprises the following steps:

and sending the queuing scheduling information to the user side.

5. The method of claim 4, further comprising:

and circularly scheduling the queuing queue.

6. A queuing and scheduling device for cloud game service is configured at a user side, and after the user side sends a cloud game request to a central server side, each regional server side selected by the central server side is not scheduled to a game server side, the device comprises:

7. A queuing and scheduling device for cloud game services is configured at a central server, and after the central server receives a cloud game request sent by a user end, each regional server selected by the central server is not scheduled to the game server, wherein the cloud game request comprises a channel identifier, and the device comprises:

8. A queuing and scheduling device for cloud game service is configured at a regional service end, the regional service end is selected by a central service end to perform scheduling of a game service end, the regional service end is not scheduled to the game service end, the regional service end has a queuing function and maintains a queuing queue, and the device comprises:

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the queuing scheduling method applied to the cloud game service of the user terminal according to claim 1, or implements the queuing scheduling method applied to the cloud game service of the center service terminal according to claim 2 or 3, or implements the queuing scheduling method applied to the cloud game service of the area service terminal according to claim 4 or 5 when executing the program.

10. A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when executed by a processor, the computer program implements the queuing scheduling method for cloud game services applied to a user side according to claim 1, or implements the queuing scheduling method for cloud game services applied to a central service side according to claim 2 or 3, or implements the queuing scheduling method for cloud game services applied to a regional service side according to claim 4 or 5.