CN110381333B

CN110381333B - Account matching method, device, equipment and storage medium

Info

Publication number: CN110381333B
Application number: CN201910775167.8A
Authority: CN
Inventors: 林晓鑫; 李维; 王宏明; 文赫
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-08-21
Filing date: 2019-08-21
Publication date: 2021-04-09
Anticipated expiration: 2039-08-21
Also published as: CN110381333A

Abstract

The application discloses an account matching method, device, equipment and storage medium, and relates to the field of application programs. The method comprises the following steps: receiving a first matching request sent by an anchor client through a live broadcast platform, wherein the first matching request comprises a bidding condition; sending bidding notification information to the viewer client according to the first matching request; receiving a second matching request sent by the audience client, wherein the second matching request comprises bidding information; and when the bidding information meets the bidding conditions, matching accounts corresponding to the anchor client and the audience client to the same network room on the target platform for activities. According to the method, the account numbers respectively corresponding to the anchor client and the audience client are directly matched with the same network room on the target platform for activity, the anchor user and the audience user do not need to establish a social friend relationship and perform team formation after account numbers are exchanged, and the man-machine interaction efficiency is improved.

Description

Account matching method, device, equipment and storage medium

Technical Field

The present application relates to the field of application programs, and in particular, to an account matching method, apparatus, device, and storage medium.

Background

In the process of live game, the interaction between the audience users and the anchor user can be realized by sending a bullet screen or brushing a gift, and the anchor user feedbacks to the audience users and then invites the audience users to participate in the game together.

Because some games have limits on the number of participating users, and the number of audience users is far greater than the specified number of participating users, the anchor user usually makes corresponding rules and selects audience users participating in the games together according to the made rules; for example, the anchor user specifies that spectator users present a specified gift participate in the game together. After determining the spectator users participating in the game, the anchor user and the spectator users participating in the game need to establish a social friend relationship and exchange game accounts, so as to be able to form a team game.

The process that the anchor user and the audience users participate in the game together is complicated, the anchor user and the audience users participate in the game, and the anchor user and the audience users participate in the game after establishing a social friend relationship and exchanging game accounts, so that the anchor user and the audience users can form a team to enter the game, and the man-machine interaction efficiency is reduced.

Disclosure of Invention

The embodiment of the application provides an account matching method, device, equipment and storage medium, and can solve the problems that the process of co-participating in a game by a main player user and audience users is complicated, and the man-machine interaction efficiency is reduced. The technical scheme is as follows:

according to one aspect of the application, an account matching method is provided, and the method is applied to a server of a live broadcast platform, and comprises the following steps:

receiving a first matching request sent by an anchor client, wherein the first matching request comprises a bidding condition;

sending bidding notification information to the viewer client according to the first matching request;

receiving a second matching request sent by the viewer client, wherein the second matching request is sent to the server by the viewer client according to the bidding notification information; the second matching request comprises bidding information;

and when the bidding information meets the bidding conditions, matching accounts corresponding to the anchor client and the audience client to the same network room on the target platform for activities.

According to another aspect of the present application, an account matching method is provided, which is applied to a first terminal, where a anchor client and a target client operate in the first terminal, and the method includes:

displaying a first user interface of the anchor client, wherein the first user interface comprises a matching control;

setting a bidding condition according to a first trigger operation received on the matching control;

when the bidding information of the audience client side meets the bidding conditions, starting a target client side;

and displaying a second user interface of the target client, wherein the second user interface is an interface when account numbers corresponding to the anchor client and the audience client are matched with the same network room on the target platform for activities.

According to another aspect of the present application, there is provided an account matching method applied in a second terminal, in which a viewer client and a target client operate, the method including:

displaying a fourth user interface of the audience client, wherein the fourth user interface is an interface for displaying the bidding conditions of the anchor client and the bidding information of the audience client, and the fourth user interface comprises a bidding control;

setting bidding information according to a third trigger operation received on the bidding control;

when the bidding information accords with the bidding conditions of the anchor client, starting the target client;

According to another aspect of the present application, there is provided an account matching apparatus, including:

the receiving module is used for receiving a first matching request sent by the anchor client, wherein the first matching request comprises a bidding condition;

the sending module is used for sending bidding notification information to the viewer client according to the first matching request;

the receiving module is used for receiving a second matching request sent by the audience client, wherein the second matching request is sent to the server by the audience client according to the bidding notification information; the second matching request comprises bidding information;

and the matching module is used for matching accounts corresponding to the anchor client and the audience client to the same network room on the target platform for activities when the bidding information meets the bidding conditions.

According to another aspect of the present application, there is provided an account matching apparatus having an anchor client and a target client operating therein, the apparatus including:

the display module is used for displaying a first user interface of the anchor client, and the first user interface comprises a matching control;

the setting module is used for setting bidding conditions according to the first triggering operation received on the matching control;

the starting module is used for starting the target client when the bidding information of the audience client meets the bidding conditions;

and the display module is used for displaying a second user interface of the target client, and the second user interface is an interface when account numbers corresponding to the anchor client and the audience client are matched with the same network room on the target platform for activities.

According to another aspect of the present application, there is provided an account matching apparatus having a viewer client and a target client operating therein, the apparatus including:

the display module is used for displaying a fourth user interface of the audience client, the fourth user interface is an interface for displaying the bidding conditions of the anchor client and the bidding information of the audience client, and the fourth user interface comprises a bidding control;

the setting module is used for setting bidding information according to a third trigger operation received on the bidding control;

the starting module is used for starting the target client when the bidding information accords with the bidding conditions of the anchor client;

According to another aspect of the present application, there is provided an electronic device including:

a memory;

a processor coupled to the memory;

the processor is configured to load and execute executable instructions to implement the account matching method according to the first aspect and the optional embodiments thereof, or the account matching method according to the second aspect and the optional embodiments thereof, or the account matching method according to the third aspect and the optional embodiments thereof.

According to another aspect of the present application, there is provided a computer-readable storage medium having at least one instruction, at least one program, code set, or instruction set stored therein, where the at least one instruction, at least one program, code set, or instruction set is loaded and executed by a processor to implement the account matching method according to the first aspect and the optional embodiments thereof, or the account matching method according to the second aspect and the optional embodiments thereof, or the account matching method according to the third aspect and the optional embodiments thereof.

The beneficial effects brought by the technical scheme provided by the embodiment of the application at least comprise:

receiving a first matching request sent by an anchor client through a live broadcast platform, wherein the first matching request comprises a bidding condition; sending bidding notification information to the viewer client according to the first matching request; receiving a second matching request sent by the audience client, wherein the second matching request is sent to the live broadcast platform by the audience client according to the bidding notification information; the second matching request comprises bidding information; when the bidding information meets the bidding conditions, matching accounts corresponding to the anchor client and the audience client to the same network room on the target platform for activities; wherein the anchor client and the audience client are in the same live broadcast room.

The account matching method matches accounts corresponding to a anchor client and an audience client respectively on a live broadcast platform in a bidding mode without making rules by an anchor user; the method also directly matches the account numbers respectively corresponding to the anchor client and the audience client to the same network room on the target platform for activity, and does not need to establish a social friend relationship between the anchor user and the audience user and perform team formation after exchanging the account numbers; the man-machine interaction efficiency is improved, the accuracy of the anchor user and the audience user entering the same network room is improved, and the user experience is also improved. In addition, the account matching method improves the interest and the active participation degree of the user in an auction mode.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a block diagram of a computer system provided in an exemplary embodiment of the present application;

FIG. 2 is a block diagram of a communication system provided in an exemplary embodiment of the present application;

fig. 3 is a flowchart of an account matching method according to an exemplary embodiment of the present application;

fig. 4 is an interface diagram of an account matching method according to an exemplary embodiment of the present application;

fig. 5 is a flowchart of an account matching method according to another exemplary embodiment of the present application;

fig. 6 is a flowchart of an account matching method according to another exemplary embodiment of the present application;

fig. 7 is a flowchart of an account matching method according to another exemplary embodiment of the present application;

fig. 8 is an interface diagram of an account matching method according to another exemplary embodiment of the present application;

fig. 9 is an interface diagram of an account matching method according to another exemplary embodiment of the present application;

FIG. 10 is a logic block diagram of an account matching method provided in an exemplary embodiment of the present application;

fig. 11 is an interface diagram of an account matching method according to another exemplary embodiment of the present application;

FIG. 12 is a flow diagram of a cast client initiating a race as provided by an exemplary embodiment of the present application;

FIG. 13 is a flow chart of a viewer client engaging in bidding as provided by an exemplary embodiment of the present application;

FIG. 14 is a flow diagram of a bid result presentation provided by an exemplary embodiment of the present application;

FIG. 15 is a flow chart of consuming virtual currency for bidding provided by an exemplary embodiment of the present application;

FIG. 16 is a flow chart of consuming virtual currency for bidding provided by another exemplary embodiment of the present application;

FIG. 17 is a flow chart of consuming virtual currency for bidding provided by another exemplary embodiment of the present application;

fig. 18 is an interface diagram of an account matching method according to another exemplary embodiment of the present application;

fig. 19 is an interface diagram of an account matching method according to another exemplary embodiment of the present application;

fig. 20 is a block diagram of an account matching apparatus provided in an exemplary embodiment of the present application;

fig. 21 is a block diagram of an account matching apparatus according to another exemplary embodiment of the present application;

fig. 22 is a block diagram of an account matching apparatus according to another exemplary embodiment of the present application;

FIG. 23 is a schematic diagram of an electronic device provided in an exemplary embodiment of the present application;

fig. 24 is a schematic structural diagram of a server according to an exemplary embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

Several nouns to which this application relates are briefly described:

live platform: the live broadcasting system is a network live broadcasting platform, the anchor client can carry out real-time rebroadcasting on the video and the audio recorded in the live scene on the live broadcasting platform through a network, and the audience client can watch and listen to the video and the audio rebroadcast by the anchor client on the live broadcasting platform in real time.

A target platform: the service platform is a service platform supporting a plurality of accounts to perform activities in the same network room. Optionally, the target platform may be a service platform of the same type as the live broadcast platform, and may even be the same service platform as the live broadcast platform; the service platform may be a service platform different from a live broadcast platform, for example, the service platform may be a game platform, and the game platform may be a service platform supporting at least one of a virtual reality application program, a three-dimensional map program, a military simulation program, a Third-person Shooting game (TPS), a First-person Shooting game (FPS), a Multiplayer Online Battle game (MOBA), and a Multiplayer gunfight living game.

The terminal in the present application may be a desktop computer, a laptop computer, a mobile phone, a tablet computer, an e-book reader, an MP3(Moving Picture Experts Group Audio Layer III, mpeg compression standard Audio Layer 3) player, an MP4(Moving Picture Experts Group Audio Layer IV, mpeg compression standard Audio Layer 4) player, and so on. The terminal comprises an operating system and an application program.

The operating system is the base software that provides applications with secure access to the computer hardware. The application includes a host client that supports live functionality or a viewer client that supports live viewing functionality. The application program further comprises a target client supporting multi-person online, and the target client further supports a plurality of accounts to move in the same network room. For example, the target client may be any one of a virtual reality application program, a three-dimensional map program, a military simulation program, a TPS game, an FPS game, an MOBA game, and a multi-player gunfight live game. Alternatively, the target client may be a stand-alone application, such as a stand-alone 3D game program, or an online application.

Referring to fig. 1, a block diagram of a computer system according to an exemplary embodiment of the present application is shown. The computer system includes: a first terminal 120, a server 140, and a second terminal 160.

The first terminal 120 is installed and operated with a main broadcasting client supporting a live broadcasting function; the anchor client can realize real-time rebroadcasting of the video and audio recorded in the live scene through a network. The first terminal 120 is also installed and operated with a target client which supports multiple persons to be online and supports multiple accounts to move in the same network room. The target client can be any one of a virtual reality application program, a three-dimensional map program, a military simulation program, a TPS game, an FPS game, an MOBA game and a multi-player gunfight living game. The first terminal 120 is a device used by the first user who uses the first terminal 120 to record and relay live events. The first user also uses the first terminal 120 to control the corresponding first account to perform activities in the same network room; for example, the target client is a TPS game, where a first account is registered in the TPS game, the first account includes a first virtual object, and the first user may use the first terminal 120 to control the first virtual object located in the virtual environment to perform an activity with other virtual objects under other accounts, where the activity includes but is not limited to: adjusting at least one of body posture, crawling, walking, running, riding, jumping, driving, picking, shooting, attacking, throwing; among them, the other account is a second account registered in the TPS game installed and operated on the second terminal 160. Illustratively, the first virtual object may be a first virtual character, such as a simulated character or an animated character.

The first terminal 120 is connected to the server 140 through a wireless network or a wired network.

The server 140 includes at least one of a server, a plurality of servers, a cloud computing platform, and a virtualization center. The server 140 is configured to provide a background service for the anchor client or the audience client, that is, provide a background service of a live broadcast platform for live broadcast users and audience users; the method is also used for providing background services for the application programs which support multiple people to be online and support multiple accounts to perform activities in the same network room, namely providing background services of a target platform for live users and audience users, wherein the live users and the audience users can create and enter the network room through the first account or the second account on the target platform, and can perform activities in the network room. The server providing background service for the anchor client or the audience client is a first server, the server providing background service for an application program which supports multi-person online and supports a plurality of accounts to move in the same network room is a second server, and the first server and the second server can be the same server or a server cluster or different servers or server clusters. Alternatively, the server 140 undertakes primary computational work and the first and second terminals 120, 160 undertake secondary computational work; alternatively, the server 140 undertakes the secondary computing work and the first terminal 120 and the second terminal 160 undertakes the primary computing work; alternatively, the server 140, the first terminal 120, and the second terminal 160 perform cooperative computing by using a distributed computing architecture.

The second terminal 160 is connected to the server 140 through a wireless network or a wired network.

The second terminal 160 is installed and operated with a viewer client supporting a live viewing function. The viewer client can view live video and audio on the live platform that the anchor client relays in real time. The second terminal 160 is also installed and operated with a target client which supports multiple persons to be online and supports multiple accounts to move in the same network room. The target client can be any one of a virtual reality application program, a three-dimensional map program, a military simulation program, a TPS game, an FPS game, an MOBA game and a multi-player gunfight living game. The second terminal 160 is a device used by a second user who uses the second terminal 160 to view live video and audio relayed by the anchor client in real-time. The second user also uses the second terminal 160 to control the corresponding second account to perform activities in the same network room; for example, the target client is a TPS game, a second account is registered in the TPS game, the second account includes a second virtual object, and the second user may use the second terminal 160 to control the second virtual object located in the virtual environment to perform an activity together with other virtual objects under other accounts, where the activity includes but is not limited to: adjusting at least one of body posture, crawling, walking, running, riding, jumping, driving, picking, shooting, attacking, throwing; the other accounts may include a first account logged in a TPS game installed and executed on the first terminal 120, and may also include other second accounts logged in a TPS game installed and executed on the other second terminals 160.

Illustratively, the second virtual object may be a second virtual character, such as a simulated character or an animated character. Wherein the first virtual object and the second virtual object are in the same virtual environment. Optionally, the first virtual object and the second virtual object may belong to the same team, the same organization, have a friend relationship, or have temporary communication rights. Alternatively, the first virtual object and the second virtual object may belong to different teams, different organizations, or two groups with enemy.

It should be noted that the target clients installed and running on the first terminal 120 and the second terminal 160, which support multiple users online and support multiple accounts to perform activities in the same network room, are the same. Alternatively, the anchor client installed and running on the first terminal 120 and the viewer client installed and running on the second terminal 160 may be the same application or different applications.

Alternatively, the systems for installing and running the application programs on the first terminal 120 and the second terminal 160 may be the same control system platform, or may be different control system platforms. For example, the first terminal 120 and the second terminal 160 both support installation and operation of an application program by using an Android system; alternatively, the first terminal 120 and the second terminal 160 support the installation and the running of the application program by using an android system and an Apple (Apple) system, respectively.

The first terminal 120 may refer to one of a plurality of devices, and the second terminal 160 may refer to at least one of the plurality of devices, in this embodiment, only the first terminal 120 and the second terminal 160 are taken as an example, and the types of devices of the first terminal 120 and the second terminal 160 are the same or different, and the types of devices include: at least one of a desktop computer, a smartphone, a tablet computer, an e-book reader, an MP3 player, an MP4 player, and a laptop portable computer. The following embodiments are illustrated with the device being a smartphone.

Referring to fig. 2, a block diagram of a communication system provided by an exemplary embodiment of the present application is shown, which may be applied to the computer system shown in fig. 1; the communication system includes a live platform 220, a target platform 240, an anchor client 260, and a viewer client 280.

The communication system realizes the account matching method provided by the application through the communication between the live broadcast platform 220, the target platform 240, the anchor client 260 and the audience client 280. Illustratively, the anchor client 260 requests the live platform 220 to create a web room and starts bidding;

the live platform 220 accesses the target platform 240 according to the request of the anchor client 260; the target platform 240 takes the anchor client 260 as a creator, creates a web room on the target platform 240, and feeds back web room information to the live platform 220;

meanwhile, the live broadcast platform 220 starts bidding according to the request of the anchor client 260 and sends bidding notification information to the viewer client 280; the viewer client 280 sends bid information to the live broadcast platform 220 according to the bid notification message; after the audience client 280 successfully bids, the live broadcast platform 220 issues network room information to the anchor client 260 and the audience client 280, wherein the network room information comprises a network address of a network room; the anchor client 220 and the viewer client 280 enter the web-room by obtaining the web-address of the web-room.

The communication system provided in this embodiment is an illustration of information interaction between the live broadcast platform 220, the target platform 240, the anchor client 260, and the audience client 280 in the account matching method provided in this embodiment, and for a detailed implementation process of the account matching method provided in this embodiment, reference is made to the following embodiments.

Referring to fig. 3, it is a flowchart of an account matching method according to an exemplary embodiment shown in the present application, and taking application of the method to the computer system shown in fig. 1 as an example to explain, the method includes:

step 301, displaying a first user interface of the anchor client on the first terminal.

The method comprises the steps that a first terminal is provided with and runs an anchor client, a first user interface of the anchor client is displayed on the first terminal, and the first user interface comprises a matching control; the match control is used to open a bid.

Step 302, the first terminal receives a first trigger operation on the matching control.

Illustratively, the first trigger operation may include any one of a click operation, a slide operation, and a long press operation, and the first trigger operation may also be another trigger operation, and the trigger mode of the first trigger operation is not limited in this embodiment. And the anchor client in the first terminal receives a first trigger operation triggered on the matching control.

And step 303, the first terminal sets a bidding condition according to the first trigger operation received on the matching control.

Optionally, the bidding condition includes a bid price for prompting a spectator user using the spectator client to conduct a bidding auction with the bid price as a starting price; the first terminal sets a starting price according to the first trigger operation. It should be noted that the auction transaction is performed on the live platform using virtual currency, such as virtual gold, virtual diamond, etc. Alternatively, the start beat price may be a custom start beat price set by the anchor user. Illustratively, as shown in fig. 4, the interface diagram of the first user interface 11 is shown, where the first user interface 11 includes a starting price input control 12 and a matching control 13, and before the first terminal receives a first trigger operation on the matching control 13, the anchor user may input a starting price in the starting price input control 12 to set the starting price; and when the first terminal receives a first trigger operation on the matching control 13, sending a first matching request to the live broadcast platform.

Optionally, the bidding condition further includes a bidding period, and the bidding period includes a bidding start time, a bidding end time, and a bidding duration. That is, the viewer client may participate in bidding for a bidding duration from the bid start time to the bid end time; and closing the bidding channel outside the bidding period, and ending the bidding, wherein the client of the audience can not participate in the bidding. Optionally, the bidding duration may be a custom duration set by the anchor user, or a bidding duration preset in the live platform, or a bidding duration used by default in the live platform.

And step 304, the first terminal sends a first matching request to the live broadcast platform according to the first trigger operation.

After a first terminal receives a first trigger operation on a matching control, firstly, an anchor client in the first terminal generates a first matching request, wherein the first matching request comprises a bidding condition; secondly, the anchor client in the first terminal sends a first matching request to the live broadcast platform through a wireless network or a wired network.

Optionally, the first matching request includes a first account corresponding to the anchor client, where the first account is an account logged in the target platform. Optionally, the account that the same user logs in on the live platform and the account that logs in on the target platform are the same account; or the account number logged in by the same user on the live broadcast platform and the account number logged in by the target platform are different account numbers with a binding relationship. That is to say, the account registered by the anchor client may be the first account, or may be a different account having a binding relationship with the first account.

In step 305, a server (i.e., a server in a live platform) receives a first matching request sent by an anchor client.

The server runs a live broadcast platform, and the live broadcast platform receives a first matching request sent by the anchor client.

The server sends a bid notification message to the viewer client based on the first match request, step 306.

The anchor client is in the same live room as the viewer client. After receiving the first matching request, a server in the live broadcast platform accesses a target platform, and a network room is created on the target platform by the target platform; meanwhile, the live broadcast platform also starts bidding and sends bidding notification information to the audience client side in the same live broadcast room with the anchor client side.

Optionally, the bid notification information includes a bid condition of the anchor client, for example, the bid notification information includes a bid price, and the viewer client may perform a bid auction with the bid price as a reference price. For another example, the bid notification message further includes a bidding period, and the viewer client can bid effectively with reference to the bidding period.

In step 307, the second terminal displays a fourth user interface of the viewer client.

And the second terminal is provided with and operates a spectator client, receives bidding notification information sent by a server in the live broadcast platform, and displays a fourth user interface of the spectator client according to the bidding notification information. The fourth user interface is an interface for displaying bidding conditions of the anchor client and bidding information of the audience client; the bidding notification information is sent to the audience client by the live broadcast platform after receiving a first matching request sent by the anchor client, and comprises bidding conditions of the anchor client and bidding information of the audience client.

It should be noted that the server sends the bid notification information to the second terminal for the first time, where the bid notification information includes the bid conditions of the anchor client; in the bidding process, the server sends continuously updated bidding notification information to the second terminal, wherein the updated bidding notification information comprises the bidding conditions of the anchor client and the bidding information of the audience client. The bidding information of the viewer client may include the bidding information of the viewer client at the local end and the bidding information of other viewer clients.

Optionally, a starting price is displayed on a fourth user interface of the spectator client; alternatively, a bidding period is displayed.

The fourth user interface of the audience client also comprises a bidding control; the bid control is used to set bid information.

And 308, the second terminal sets bidding information according to the third triggering operation received on the bidding control.

The second terminal receives a third trigger operation on the bidding control; and setting bidding information according to a third triggering operation. Optionally, the bid information includes a start price. Optionally, the bidding information may also include a bidding period.

Illustratively, the second terminal sets the attack price according to the third triggering operation, as shown in fig. 4, which is not described herein again. The third trigger operation may be any one of a click operation, a long-press operation, and a slide manipulation, and the third trigger operation may also be another trigger operation, and the trigger mode of the third trigger operation is not limited in this embodiment.

And 309, the second terminal sends a second matching request to a server in the live broadcast platform according to the third trigger operation.

After receiving the third trigger operation, the audience client in the second terminal generates a second matching request and sends the second matching request to a server in the live broadcast platform; the second match request includes bid information. Optionally, the bid information includes a bid of the viewer client, which is a bid set by the viewer user.

Alternatively, the bid may be a price for the spectator user to bid on a bid with the start price as a reference price.

Optionally, the bidding information further includes a bidding time, which is used to determine whether the current bid is an effective bid within the bidding time period specified in the bidding condition.

Optionally, the second matching request includes a second account corresponding to the viewer client, where the second account is an account logged in the target platform. Optionally, the account that the same user logs in on the live platform and the account that logs in on the target platform are the same account; or the account number logged in by the same user on the live broadcast platform and the account number logged in by the target platform are different account numbers with a binding relationship. That is, the account registered by the viewer client may be the second account, or may be a different account having a binding relationship with the second account.

In step 310, the server receives a second matching request sent by the viewer client.

The second match request is sent by the viewer client to a server in the live platform based on the bid notification information. And after the second client receives the bidding notification information, the audience client participates in bidding and sends a second matching request to a server in the live broadcast platform, and the server receives the second matching request sent by the audience client.

And 311, when the bidding information meets the bidding conditions, the server matches the accounts corresponding to the anchor client and the audience client to the same network room on the target platform for activity.

The live broadcast platform in the server judges whether the bidding information of the audience client side meets the bidding conditions of the anchor client side; and when the bidding information of the audience client side meets the bidding conditions of the anchor client side, the server in the live broadcast platform matches account numbers corresponding to the anchor client side and the audience client side to the same network room on the target platform for activity.

Optionally, the server first determines whether the bidding time of the viewer client belongs to a bidding period; and when the bidding time of the client side of the audience belongs to the bidding period, determining the current bidding as effective bidding, and continuing the judgment of other bidding conditions.

It should be noted that, target clients are also installed and operated in the first terminal and the second terminal, respectively. Optionally, when the bidding information of the audience client meets the bidding condition of the anchor client, the server matches the first account and the second account with the same network room on the target platform for activity through an Application Program Interface (API) of the target client in the target platform.

Optionally, after the account numbers corresponding to the anchor client and the audience client are successfully matched, the server further receives a starting request sent by the anchor client; and sending the network addresses of the network rooms to the anchor client and the audience client according to the starting request, controlling the anchor client and the audience client to start the target client through an API (application programming interface), transmitting the network addresses to the target client through the API, and opening the network addresses through the target client to enter the network rooms.

It should be further noted that, when the bidding information of the spectator client does not meet the bidding condition of the anchor client, the server continues to determine whether the bidding information of the next spectator client meets the bidding condition of the anchor client, that is, continues to execute step 311.

In summary, in the account matching method provided in this embodiment, a first matching request sent by a host client is received through a live broadcast platform, where the first matching request includes a bidding condition; sending bidding notification information to the viewer client according to the first matching request; receiving a second matching request sent by the audience client, wherein the second matching request is sent to the live broadcast platform by the audience client according to the bidding notification information; the second matching request comprises bidding information; when the bidding information meets the bidding conditions, matching accounts corresponding to the anchor client and the audience client to the same network room on the target platform for activities; wherein the anchor client and the audience client are in the same live broadcast room.

Taking a target platform as a game platform as an example, the account matching method determines audience users participating in the game through a bidding method, and pulls the game account of the live broadcast user and the game account of the audience users participating in the game to the same game room, so that the problem that the process of the main broadcast user and the audience users participating in the game together is complicated is solved, the man-machine interaction efficiency is improved, and the user experience is improved.

In some embodiments, the number of spectator clients entering the same network room for activity is also specified, for example, in a game, a group of 5 accounts is grouped into a game room for activity. Optionally, the bidding condition includes that the bid of the viewer client is the largest bid of the top n ranked bids among the bids of at least two viewer clients, n is the number of matches, and n is a positive integer. Therefore, when the bidding information of the audience client accords with the bidding information of the anchor client, the server matches the accounts corresponding to the anchor client and the audience client to the same network room on the target platform for activity, which may include the following exemplary steps:

a) and when the bidding price of the audience client side is the maximum bidding price ranked in the top n, the server matches the accounts corresponding to the anchor client side and the audience client side to the same network room on the target platform for activity.

For example, the matching number is 3, and 10 audience clients participate in bidding started by the anchor client; and arranging 10 bids given by 10 clients from large to small, and determining the audience clients corresponding to the 3 bids ranked in the top 3, wherein the accounts corresponding to the determined 3 audience clients and the account corresponding to the anchor client are matched to the same network room on the target platform together for activity.

Optionally, in the bidding process, the number of the viewing clients meeting the bidding condition may be less than n; therefore, when the number of the watching clients meeting the bidding conditions of the anchor client is less than n, the server determines the audience client corresponding to the maximum bidding from the at least two unsuccessfully matched audience clients; and stopping matching the account number of the audience client with the account number of the anchor client by the live broadcast platform until the number of the matched audience clients is equal to the matching number.

It should be noted that, the server stores the bidding information bid by the viewer client into the database, optionally, the database may be a redis database, the bidding information of the viewer client is stored in the redis database in a list form according to the order of the bidding from large to small, and the server may obtain n viewer clients located in the front of the list from the redis database; or the bidding information of the audience client sides is stored in the redis database in a list form according to the sequence of bidding from small to large, and the server can acquire n audience client sides positioned at the tail part of the list from the redis database; and the server matches the obtained accounts corresponding to the n audience clients and the account corresponding to the anchor client to the same network room on the target platform for activity.

In some embodiments, the bidding conditions during the bidding process may further include at least one of a level of the first account being a preset level and the viewer client being in a state of guard for the anchor client; before a server in a live broadcast platform matches accounts corresponding to a main broadcast client and an audience client to the same network room on a target platform for activity, bidding information of the audience client also needs to meet the following bidding conditions:

a) the bidding condition comprises that the grade of the first account is a preset grade, and the preset grade is set according to the grade requirement of the anchor user on the first account corresponding to the audience client. The bid information of the viewer client includes a rating of the first account.

And when the grade of the first account corresponding to the audience client is a preset grade, the server executes the step of matching the accounts corresponding to the anchor client and the audience client to the same network room on the target platform for activities.

When the level of the first account corresponding to the audience client is not the preset level, the server determines that the first account of the audience client does not have the permission of matching the second account of the anchor client to the same network room on the target platform for activities.

b) The bidding condition further includes that the audience client is in a guard state for the anchor client, the guard state information is used for indicating that the audience client is in the guard state for the anchor client, and the guard state is used for indicating that the audience client is a special honored guest (VIP) of the anchor client; alternatively, the spectator client is in a non-daemon state with respect to the anchor client. The bidding information of the viewer client comprises the guard state information of the viewer client.

When the guard state information of the audience client indicates that the audience client is in a guard state of the anchor client, the server executes the step of matching the account numbers respectively corresponding to the anchor client and the audience client to the same network room on the target platform for activity.

When the viewer client's daemon state information indicates that the viewer client is in a non-daemon state for the anchor client, the server determines that the viewer client is not eligible for successful bidding. Optionally, when the guard state information of the viewer client indicates that the viewer client is in a non-guard state with respect to the anchor client, the server sends a prompt message to the viewer client, where the prompt message is used to prompt the viewer client to start the guard state with respect to the anchor client. Optionally, the mode of opening the watching state of the audience client to the anchor client may be to charge virtual money into an account of the audience client and open a dedicated VIP.

The two bidding conditions can screen out a large number of the viewer clients when the number of the viewer clients is large, so that the bidding efficiency can be improved.

It should be noted that the live platform also needs to determine whether the corresponding anchor client has the right to create a web room and open a bid before opening a bid, and illustratively, steps 401 to 403 are added before step 303, as shown in fig. 5, and the steps are as follows:

step 401, the first terminal sends an authority request to the server.

An authority request sent by a main broadcast client in a first terminal to a server in a live broadcast platform, wherein the authority request comprises an account number logged in by the main broadcast client on the live broadcast platform, and the authority request is used for requesting the live broadcast platform to confirm that the main broadcast client has matching authority; that is, the anchor client has the right to create a web room indirectly through the live platform and to open a bid through the live platform.

In step 402, the server receives a permission request sent by the anchor client.

In step 403, when the account information logged on the live platform by the anchor client belongs to the white list, the server determines that the anchor client has the matching authority.

The server stores a white list, and the anchor client corresponding to the account number in the white list has matching authority. And when the account number logged in by the anchor client on the live broadcast platform belongs to the white list, the server determines that the anchor client has the matching authority.

When the account number of the anchor client logged on the live broadcast platform does not belong to the white list, the server determines that the anchor client does not have the matching authority, and refuses the anchor client to create a network room and start a bidding request.

It should be noted that, the server executes the above-mentioned step of "receiving the first matching request sent by the anchor client" according to the matching authority.

And after determining that the anchor client has the matching authority, the server sends feedback information to the anchor client, and feeds back the authority requested by the anchor client to the anchor client through the feedback information. And then, the server executes the step of receiving the first matching request sent by the anchor client according to the matching authority.

It should be further noted that in some embodiments, the live platform may further determine whether the anchor client has the matching authority by the number of people interested by the anchor client, and illustratively, the step 403 is replaced with a step 4032, as shown in fig. 6, where the steps are as follows:

step 4032, when the number of people concerned by the anchor client is greater than the threshold number of people concerned, the server determines that the anchor client has the matching authority.

And the live broadcast platform stores an attention number threshold which is used for determining whether the anchor client has the matching authority.

The authority request of the anchor client comprises the attention number of the anchor client, and the live broadcast platform judges whether the attention number of the anchor client is greater than an attention number threshold value; when the attention number of the anchor client is larger than the attention number threshold, the server determines that the anchor client has the matching authority.

And when the attention number of the anchor client is less than or equal to the attention number threshold, the live broadcast platform determines that the anchor client does not have the matching authority, refuses the anchor client to create a network room and starts bidding.

The live broadcast platform can effectively control the bidding security by controlling the matching authority of the anchor client.

In some embodiments, after account matching between the anchor client and the viewer client is completed, the live user and the viewer user may enter the same network room on the target platform for activity, based on fig. 3, add step 501 to step 507 after step 311, as shown in fig. 7, which includes the following exemplary steps:

step 501, the server sends matching success information to the anchor client and the audience client.

The matching success information is a message sent by the server to the anchor client and the audience client when the bidding information of the audience client accords with the bidding condition of the anchor client; the message is that account numbers corresponding to the anchor client and the audience client are matched with the same network room on the target platform for activity.

Optionally, the matching success information includes account information of the anchor client and account information of the viewer client. Optionally, the account information of the anchor client may include an account head portrait and an account name of the anchor client, and the account information of the viewer client may include an account head portrait and an account name of the viewer client; or the account information of the anchor client comprises the head portrait and the name of the first account, and the account information of the audience client comprises the head portrait and the name of the second account.

Step 502, the first terminal receives matching success information sent by a server in the live broadcast platform.

In step 503, when the bidding information of the viewer client meets the bidding condition, the first terminal starts the target client.

Optionally, the first terminal launching the target client includes the following exemplary steps:

1) displaying a third user interface of the anchor client on the first terminal.

Wherein the third user interface is an interface for displaying the bidding condition of the spectator client; the bidding conditions can include bidding conditions of the anchor client, bidding information of the viewer client, and account matching conditions between the anchor client and the viewer client.

2) And when the bidding information of the audience client accords with the bidding condition of the anchor client, displaying a starting control on a third user interface.

3) And the first terminal receives a second trigger operation on the starting control.

Optionally, the second trigger operation may include any one of a click operation, a slide operation, and a long press operation, and the second trigger operation may further include other trigger operations, and a trigger operation manner on the start control in this embodiment is not limited.

4) And the first terminal starts the target client according to the second trigger operation.

After receiving the second trigger operation, the first terminal generates a starting request, wherein the starting request is used for requesting account numbers corresponding to the anchor client and the audience client to enter the same network room on the target platform for activities; sending a starting request to the server according to the second triggering operation; receiving a network address of a network room sent by the server according to the starting request; and calling the API of the target client to start the target client, transmitting the network address to the target client through the API, and opening the network address through the target client to enter the network room.

Step 504, the first terminal displays a second user interface of the target client.

The second user interface is an interface when account numbers corresponding to the anchor client and the audience client are matched with the same network room on the target platform for activities.

Illustratively, as shown in fig. 8, a first user interface 21 of the anchor client is displayed on the first terminal, a starting price 10 is input in a starting price input control 22, and when the first terminal receives a first trigger operation on a matching control 23, an auction is initiated. And displaying a second user interface 24 of the anchor client on the first terminal, wherein account information of the anchor client and account information of the successfully matched audience client are displayed on the second user interface 24. In some embodiments, when the number of matched viewer clients is less than the number of matched viewer clients, the start control on the second user interface cannot be triggered; for example, in fig. 8, the number of the spectator clients on the second user interface 24 is 2, and the matching number of the spectator clients is 4, so that the start control 25 on the second user interface 24 cannot be triggered, and prompts that "waiting for a water friend to join", that is, waiting for the joining of the spectator clients; when the number of spectator clients is 4, the launch control 25 on the second user interface 26 can be triggered and prompt "start game".

And 505, the second terminal receives matching success information sent by a server in the live broadcast platform.

Step 506, when the bidding information meets the bidding conditions of the anchor client, the second terminal starts the target client.

Optionally, the second terminal receives a network address of a network room sent by a server in the live broadcast platform; the network address is sent to the audience client after the server receives a starting request sent by the anchor client; and calling the API of the target client to start the target client, transmitting the network address to the target client through the API, and opening the network address through the target client to enter the network room.

Step 507, the second terminal displays a second user interface of the target client.

Optionally, the second user interface includes account information of the anchor client and account information of the viewer client; the account information of the viewer client may include account information of the viewer client itself, and may also include account information of other viewer clients.

Illustratively, as shown in fig. 9, when the matching of the spectator clients in the second terminal is successful, a second user interface 31 is displayed on the second terminal, where the second user interface 31 is a user interface displayed by the spectator client when the number of the matched spectator clients is less than the matching number of the spectator clients, and "waiting for other friends to join" is indicated on the second user interface 31; when the number of matched spectator clients satisfies the number of matched spectator clients, a second user interface 32 is displayed on the second terminal, on which second user interface 32 "waiting to start the game" is indicated, that is, waiting for the anchor client to determine to start the game.

It should be noted that when the client of the viewer in the second terminal is not matched or is not successfully matched, the viewer participates in bidding, for example, as shown in fig. 9, the fifth user interface 33 includes a bidding control 34 and a bidding control 35, the viewer user can determine bidding through the bidding control 35, determine participation in bidding through the bidding control 34, and when the second terminal receives a trigger operation on the bidding control 34, send a second matching request to the live broadcast platform.

It should be noted that, the account matching method shown in fig. 3 to 9 is described by taking a target platform as a game event platform (competition platform), as shown in fig. 10, the account matching method can be summarized into three parts, namely a competition management service 601, a competition participating service 602, and a payment gateway service 603;

the game management service 601 comprises three service logics of a game creation logic 6011, a game callback logic 6012 and a game settlement logic 6013; wherein creating the tournament logic 6011 comprises creating a network room for the tournament on the tournament platform; the match callback logic 6012 includes controlling account numbers corresponding to the anchor client and the audience client to enter a network room of a match respectively, and performing the match; the game settlement logic 6013 includes settlement of bids for spectator clients participating in the game and settlement of bids for spectator clients that have failed bids.

The participating tournament service 602 includes a service that binds the participating tournament account 6021 and the tournament bid 6022. The binding of the bidding participating account 6021 includes binding the bidding participating account when the second account is not the same account as the account logged in the viewer client, for example, fig. 11 shows a user interface 41 for account binding, the user interface 41 includes an account input control 42, the second account to be bound is input in the account input control 42, and the binding of the bidding participating account is completed after receiving the trigger operation on the binding confirmation control 43. In addition, a region service information input control 44 is further included in the user interface 41, and is used for inputting a region server where the second account is located. And when the second account is bound, inputting a region server where the second account is located so as to accurately acquire account information of the second account from the region server where the second account is located.

The game bidding 6022 includes a process of determining the spectator client participating in the game from the spectator client in a bidding manner, and after the bidding is completed, the second account corresponding to the spectator client participating in the game is matched to the network room of the created game.

The payment gateway service 603 includes three services of frozen amount 6031, confirmed payment 6032, and expired defrosted 6033. Wherein freezing the amount 6031 comprises freezing an amount to participate in the bidding; confirming the payment 6032 includes transferring the amount of the bid from the account of the spectator client participating in the race to the account of the anchor client after the race is over; expiration freeze 6033 involves unfreezing the amount of money of spectator clients participating in the game when the game is not successfully played.

It should be further noted that, in the match management service 601 and the match participation service 602 provided by the live broadcast platform for the anchor client and the audience client, two logic services, i.e., the match flow state torsion logic 6014 and the bypass repair compensation logic 6015, are included. The race process state torsion logic 6014 is used to update the state of the race process in the database, for example, when the race process is in the bidding stage, the bidding information is updated and stored in the database; for another example, the match process is at a stage when the matching of the account numbers respectively corresponding to the audience client and the anchor client is successful, and the team formation information of the matched audience client and the anchor client is updated and stored in the database. Alternatively, the database may be a Cloud MEMcache (CMEM) database.

Bypass repair compensation logic 6015 includes unfreezing frozen amounts for spectator clients that are not participating in the game and are participating in a bid, and frozen amounts for spectator clients that are participating in the game and fail the game to open.

The above three services enable the live broadcast platform to support the implementation of the account matching method, and for the implementation of the account matching method, it can be further described from the aspects of initiating a match by a main broadcast client and participating in bidding by an audience client, please refer to the following embodiments.

Referring to fig. 12, a flowchart of a cast client initiating a race, provided by an exemplary embodiment of the present application, is shown, which includes the following steps:

step 701, the anchor client sends an authority request to the live broadcast platform.

The anchor client sends an authority request to the live broadcast platform; wherein, the permission request includes account information of the anchor client.

After receiving the permission request, the live broadcast platform can match account information of the anchor client with a white list stored in the live broadcast platform in advance, and when the matching result is that the white list comprises the account information of the anchor client, the anchor client is determined to have permission to initiate a match.

Or the direct broadcast platform stores the attention number of the anchor client; after receiving the permission request, the live broadcast platform can acquire the attention number of the anchor client, which is stored in the live broadcast platform correspondingly, according to the account information of the live broadcast platform. A threshold value of the number of people concerned is also preset in the live broadcast platform; and when the attention number of the anchor client is larger than the attention number threshold, determining that the anchor client has the permission to initiate the competition.

And after the live broadcast platform determines that the anchor client has the authority to initiate the competition, the authority is returned to the anchor client.

At step 702, the anchor client initiates a race.

And the anchor client initiates a match according to the returned permission and sends a match initiation request to the live broadcast platform. The competition initiation request comprises a first account corresponding to the anchor client, and the first account is an account logged in on a competition platform.

Step 703, the live broadcast platform sends a segment position information request to the competition platform.

After receiving a competition initiation request sent by a main broadcasting client, a live broadcasting platform sends a segment information request to a competition platform, wherein the segment information request comprises a first account. The segment information request is used for requesting to acquire segment information of the first account in the competition.

After the competition platform receives the segment information request sent by the live broadcast platform, the competition platform returns the segment information of the first account to the live broadcast platform. After receiving the segment bit information of the first account, the live broadcast platform determines that the first account has the permission to participate in the game, and then determines that the game is successfully initiated.

Step 704, the live platform writes the storage.

The live broadcast platform writes the state of successful match initiation into a CMEM database; after the state of successful match initiation is successfully written into the CMEM database, the CMEM database returns the information of successful writing to the live broadcast platform; and the live broadcast platform returns the information of successful match initiation to the anchor client.

The method comprises the steps that a live broadcast platform polls each state in the process of initiating a match, periodically updates each state in the process to a CMEM database, and periodically sends state notifications to a main broadcast client and an audience client to update user interfaces displayed on the main broadcast client and the audience client, so that a live broadcast user and the audience user respectively know the process of initiating the match from the user interfaces of the main broadcast client and the audience client, for example, the audience client receives the notification to pop up a bubble popup window, and enters a bidding process by receiving triggering operation on the bubble popup window.

It should be noted that, after the match is successfully initiated, the account numbers corresponding to the anchor client and the audience client respectively match in the same network room on the match platform.

Step 705, the live broadcast platform performs a match call back.

After the live broadcast platform initiates a match, a match room is created on the match platform, so that account numbers corresponding to the anchor client and the audience client can enter the match room to match.

And the account numbers corresponding to the anchor client and the audience client are respectively used for competition in a competition room on a competition platform, and the live broadcast platform recalls the competition state in the competition process.

Step 706, the live platform modifies the game status.

The live broadcast platform modifies the match state in the CMEM database according to the recalled match state; for example, at the first moment, five members in the competition are in the fighting state, and the fighting states of the five members are written into the CMEM database; at the second moment, three members in the competition are in a fighting state, two members are in an elimination outgoing state, the state of five members is modified into the state that three members are in the fighting state, and two members are in the elimination outgoing state.

And after the match state in the CMEM database is modified, the CMEM database returns the modified information to the live broadcast platform.

In step 707, the live platform writes a global game list.

After the match is finished, the live broadcast platform writes the match result of the match into a global match list of a redis database for recording.

Referring to fig. 13, a flow chart of a viewer client participating in bidding provided by an exemplary embodiment of the present application is shown, which comprises the following steps:

in step 801, a viewer client binds an account.

When the account of the audience client is different from the second account logged in the competition platform, the audience client needs to log in and bind the second account.

It should be noted that, in the process of binding the account, it is detected whether a match client is installed and running in a second terminal corresponding to the viewer client; and if the match client is not installed in the second terminal, prompting the audience user to install the match client. If a competition client is installed and operated in the second terminal, detecting whether a second account is logged in the competition client; when a second account is logged in the competition client, executing step 802; and when the second account is not logged in the competition client, prompting the audience user to log in the second account.

At step 802, the viewer client queries for user information.

The audience client sends a user information query request to the live broadcast platform, wherein the user information query request is used for requesting the live broadcast platform to query user information. Optionally, the user information comprises a balance under an account of the viewer client.

Step 803, the live platform queries the balance.

The method comprises the steps that a live broadcast platform sends a balance inquiry request to a payment platform, wherein the balance inquiry request comprises account information of a spectator client; the payment platform correspondingly inquires the balance of the audience client according to the account information and returns the balance to the live broadcast platform; the balance is returned to the viewer client by the live platform.

Optionally, the live broadcast platform stores the start price sent by the anchor client, and when the balance is less than the start price, the live broadcast platform returns information of insufficient balance to the audience client, and prompts the audience user to recharge the account of the audience client, and step 804 is executed.

In step 804, the viewer client recharges the account.

And the audience client recharges the account number with the virtual currency through the payment platform, and returns recharging success information to the audience client after the payment platform recharges the account number of the audience client successfully.

At step 805, the viewer client initiates a round of bidding.

A spectator client sends a bidding request to a live broadcast platform; the bid request includes a bid.

Step 806, the live platform queries the segment bit information.

After receiving a bidding request of a viewer client, the live broadcast platform sends a segment information request to the competition platform to request to acquire segment information of a second account; the segment information is used to determine that the second account has the right to participate in the game. And the competition platform correspondingly obtains the segment information of the second account according to the second account and returns the segment information of the second account to the live broadcast platform.

The live broadcast platform determines whether the segment information of the second account number matches a preset segment set by the anchor client, and executes step 807 when the segment information of the second account number matches the preset segment.

The live platform checks the viewer client's daemon of the anchor client, step 807.

The live broadcast platform acquires the guard state information of the audience client, and executes step 809 when the guard state information indicates that the audience client is in a guard state of the anchor client; when the daemon state information indicates that the spectator client is in a non-daemon state for the anchor client, step 808 is performed.

Step 808, opening daemon on the live broadcast platform.

The live broadcast platform prompts the user side to open the guard of the audience client side to the anchor client side. Illustratively, the audience user can open the guard of the audience client to the anchor client in a recharging mode. After the daemon is opened, that is, when the audience client is in the state of daemon on the anchor client, the live broadcast platform executes step 809.

Step 809, the live platform queries the balance.

The anchor client sends a balance inquiry request to the payment platform, wherein the balance inquiry request comprises account information of the audience client; and the payment platform correspondingly obtains the balance under the account of the audience client according to the account information of the audience client.

When the balance under the account of the audience client is greater than or equal to the bid, the live broadcast platform executes step 810; and when the balance is less than the bidding price, the live broadcast platform prompts the audience user to recharge the account of the audience client.

Step 810, the live platform freezes the balance through the payment platform.

Optionally, the live platform freezes the same amount in the balance as the bid through the payment platform.

Step 811, the live broadcast platform updates the price list.

The live broadcast platform updates the bidding information of the audience client to a bidding list of a redis database; in the bid list, the bid information of each viewer client is stored in the order of bids from high to low. And the direct broadcast platform sends the bidding information of the audience client to a redis database, and the redis database updates the bidding information of the audience client to a bidding list according to the bidding in the bidding information of the audience client.

If the matching number of the audience client sides is r, the redis database returns the bidding ranks of the first r audience client sides in the updated bidding list to the live broadcast platform; for example, r is 4, and the redis database returns the bid ranks of the top four viewer clients in the updated bid list to the live platform. The redis database also returns the bid ranking of the viewer client to the live platform.

In step 812, the live platform writes a bidding success event.

When the bidding ranking of the audience client is the first r, the audience client successfully bids to obtain the permission to participate in the match, and the live broadcast platform writes the successful bidding event of the audience client into a redis database.

After the bidding success event is written successfully by the redis database, returning the successfully written information to the live broadcast platform; and after receiving the information of successful writing returned by the redis database, the live broadcast platform returns information of completing one round of bidding to the audience client.

It should be noted that when the returned bid ranks of the viewer client are not r, the viewer client receives information of bid failure returned by the live broadcast platform; when the bidding is not finished, the client side of the audience can continue to participate in the bidding, each bidding needs to be higher than the starting price, and the current bidding needs to be higher than the previous bidding. Thus, the viewer client may initiate a bid round, … …, or even an n bid round before bidding has not ended. Wherein r is a positive integer, and n is a positive integer greater than 2.

Referring to FIG. 14, a flow chart of a bid result presentation provided by an exemplary embodiment of the present application is shown, the steps being as follows:

step 901, the anchor client polls the live platform.

At step 902, the viewer client polls the live platform.

In the process of competition bidding, live users and audience users need to know bidding conditions in real time, and therefore the anchor client and the audience client poll the live platforms respectively to obtain the real-time bidding conditions. Illustratively, the bidding situation may include an account avatar and account name of the second account of the successfully bidding viewer client, the bidding of the successfully bidding viewer client, and so on.

The bidding scenario may also include a bid end time, and if the anchor client and the viewer client obtain the bid end time, step 903 is performed.

In step 903, the live broadcast platform queries the bid ending time.

The live broadcast platform requests a redis database to inquire the bidding ending time, the redis database returns the bidding ending time to the live broadcast platform after obtaining the bidding ending time, and the live broadcast platform returns the bidding ending time to the anchor client and the audience client.

At step 904, the anchor client obtains the viewer client that has successfully bid.

And after bidding is finished, the anchor client sends an acquisition request of the audience client for acquiring successful bidding to the live broadcast platform.

Step 905, the live broadcast platform queries the audience client with successful bidding.

And after receiving the acquisition request of the anchor client, the live broadcast platform sends an inquiry request of the audience client for inquiring successful bidding to a redis database according to the acquisition request. And after receiving the query request, the redis database queries the audience client with successful bid price, returns the audience client with successful bid price obtained by query to the live broadcast platform, and returns the audience client with successful bid price to the anchor client by the live broadcast platform.

The live broadcast platform also stores a network address of a competition room which is created on the competition platform by the anchor client side; and the live broadcast platform returns the audience client end with successful bidding to the anchor client end and also returns the network address of the competition room to the anchor client end.

Illustratively, the successfully matched audience client terminals are the first four of the price list in the redis database; after receiving a query request sent by a live broadcast platform, the redis database acquires the first four audience clients in the bid list, returns the four audience clients to the live broadcast platform, and returns the four audience clients to the audience clients through the live broadcast platform.

At step 906, the spectator client obtains the spectator client with successful bidding.

And after the bidding is finished, the audience client sends an acquisition request of the audience client with successful bid acquisition to the live broadcast platform.

Step 907, the live broadcast platform queries the viewer clients with successful bidding.

And after receiving an acquisition request of the audience client, the live broadcast platform sends an inquiry request of the audience client for inquiring successful bidding to a redis database according to the acquisition request. And after receiving the query request, the redis database queries the audience client with successful bid price, returns the audience client with successful bid price obtained by query to the live broadcast platform, and returns the audience client with successful bid price to the audience client by the live broadcast platform.

At step 908, the anchor client jumps to the network address of the tournament room.

The tournament room is a web room that the anchor client requests to create on the tournament platform. And the anchor client enters the competition room to participate in the competition through a first account corresponding to the anchor client.

For example, the anchor client enters the target client through the API of the target client, opens a network address through the target client, and enters a network room.

In step 909, the live platform asynchronously recalls the network address of the game room.

In step 910, the live broadcast platform sends the network address of the match room to the audience client.

At step 911, the spectator client jumps to the network address of the tournament room.

And skipping to the network address of the competition room by the audience client, and entering the competition room in which the first account is located through a second account corresponding to the audience client to participate in the competition.

For example, the viewing client enters the target client through the API of the target client, opens a network address through the target client, and enters a network room.

Referring to fig. 15, a flow chart of the virtual currency consumed by bidding provided in an exemplary embodiment of the present application is shown, and the virtual currency is taken as an example of a virtual diamond, in the following embodiments, the virtual diamond is simply referred to as a diamond, and the steps are as follows:

step 1001, the live platform freezes diamonds that bid for consumption.

The live broadcast platform performs pre-payment on the diamonds for bidding consumption, firstly, the live broadcast platform requests the CMEM database to freeze the diamonds for bidding consumption through the payment client, and the steps 1002 to 1006 are executed.

And step 1002, locking.

Before the pre-payment process is completed, the diamond under the account number of the audience client is locked, so that other payment processes cannot operate the diamond.

In step 1003, the CMEM database freezes the diamonds that are consumed on a bid.

The CMEM database stores the number of the diamonds which can be consumed under the account number of the audience client; and when the CMEM database receives a freezing request of the live broadcast platform for the diamond which is consumed in bidding, the CMEM database freezes the diamond which is consumed in bidding and returns a message of completing freezing to the payment client.

At step 1004, the payment client queries the diamond number.

And the payment client sends a query request to the CMEM database to query the total diamond number recorded in the payment platform under the account number of the audience client. The inquiry request of the diamond number under the account number of the audience client comprises the account number information of the audience client, and the payment platform acquires the total diamond number under the account number of the audience client according to the account number information of the audience client and returns the total diamond number to the payment client.

Step 1005, the payment client updates the frozen records in the CMEM database.

And the payment client updates the frozen records in the CMEM database according to the frozen total diamond number.

And step 1006, unlocking.

The payment client unlocks the diamond under the account of the spectator client so that other payment processes can operate on the unconsumed diamond. Wherein, the payment client can calculate the number of unconsumed diamonds according to the total number of diamonds and the frozen total number of diamonds. After unlocking, the payment client returns a message that the freezing is completed to the live broadcast platform.

Step 1007, the live platform consumes diamonds.

When the match is completed, the anchor client initiates settlement and the live platform pays for the diamonds consumed by the spectator clients participating in the match, steps 1008-1012.

And step 1008, locking.

Before the payment process is completed, the diamonds under the account number of the audience client are locked, so that other payment processes cannot operate the diamonds.

At step 1009, the payment client queries the diamond number.

Please refer to step 1004, which will not be described herein.

At step 1010, the payment client queries the number of freezes.

And the payment client inquires the frozen number of the diamond bid from the frozen record of the CMEM database.

At step 1011, the payment client deducts the consumed diamond.

The payment client sends a deduction request for the consumed diamonds to the payment platform, the payment platform deducts the number of the diamonds frozen in the current bidding price from the account of the audience client participating in the competition according to the deduction request, and returns a deduction completion message to the payment client, and the payment client returns a consumption completion message to the live broadcast platform.

And step 1012, unlocking.

The payment client unlocks the diamond under the account of the spectator client so that other payment processes can operate on the unconsumed diamond. Wherein, the payment client can calculate the number of unconsumed diamonds according to the total number of diamonds, the deducted number of diamonds and the frozen number of diamonds. And after unlocking, the payment client returns a deduction completion message to the live broadcast platform.

Step 1013, the live platform queries the number of consumable diamonds.

The live platform requests the payment client to inquire the number of consumable diamonds and executes steps 1014 to 1015.

In step 1014, the payment client queries the diamond count.

Please refer to step 1004, which will not be described herein.

At step 1015, the payment client queries the number of freezes.

The payment client inquires the number of the frozen diamonds in the frozen records of the CMEM database, the payment client can subtract the number of the frozen diamonds according to the number of the diamonds under the account number of the audience client, calculate the number of the diamonds consumable under the audience client and return the number of the diamonds consumable under the account number of the audience client to the live broadcast platform.

It should be noted that the above-described process of consuming virtual money is to consume virtual money when the viewer client successfully bids, and based on fig. 15, steps 1007 to 1012 are replaced with steps 1016 to 1019, and consumption of virtual money when the viewer client fails to bid is described, as shown in fig. 16, the exemplary steps are as follows:

at step 1016, the live platform unfreezes the diamonds for bid consumption.

The live platform requests the payment client to unfreeze the diamonds for bid consumption, and steps 1017 to 1019 are executed.

And step 1017, locking.

At step 1018, the payment client unfreezes the diamonds that bid for consumption.

And the payment client requests the CMEM database to unfreeze the diamonds for bidding consumption, the CMEM database unfreezes the diamonds for bidding consumption, and a message of unfreezing completion is returned to the payment client.

And step 1019, unlocking.

The payment client unlocks the diamond under the account of the spectator client so that other payment processes can operate on the unconsumed diamond. Wherein, the payment client can calculate the number of unconsumed diamonds according to the total number of diamonds, the number of unfrozen diamonds and the number of frozen diamonds. And after unlocking, the payment client returns a message of thawing completion to the live broadcast platform.

It should be further noted that the situation that the anchor client fails to start the game may include two situations, that is, the first situation is a streaming game, that is, the matching between the first account and the second account is unsuccessful; secondly, the bidding result is shown, and the game is failed to open, that is, the first account and the second account are successfully matched, but the game is failed to open.

The thawing process for diamonds for both of the above situations is shown in fig. 17, with the following schematic steps:

step 1101, the live platform queries the match information.

The live broadcast platform queries the current match information from the CMEM database, wherein the current match information comprises a bidding status, and the bidding status comprises a bidding result, a streaming game result and a match starting failure.

Step 1102, the live broadcast platform determines whether a bypass is repaired.

Bypass repair refers to the processing logic for the two bidding states of the current game and the bidding status that the bidding result is out and the competition opening fails. When the live broadcast platform judges that the bypass is repaired, executing a step 1103; and when the live broadcast platform judges that no bypass is repaired, finishing the judgment and returning a message of repairing completion.

Step 1103, the live broadcast platform determines the status of the bid.

And when the bidding status is in bidding, ending the judgment and returning a message of ending the repair.

When the bidding state is the streaming game, the live broadcast platform acquires a bidding list of the audience client participating in bidding from the redis database, returns the audience client in the bidding list to the live broadcast platform, and executes step 1104.

And when the bidding status is that the bidding result is shown and the match starting fails, the live broadcast platform acquires the audience client end successfully bidding from the redis database, returns the audience client end successfully bidding to the live broadcast platform, and executes step 1104.

And step 1104, the live broadcast platform acquires order number information.

And the live broadcast platform acquires order number information corresponding to the audience client in the bidding list from the CMEM database, or acquires order number information corresponding to the audience client with successful bidding.

Step 1105, the live broadcast platform unfreezes the amount of money.

The live broadcast platform requests the payment platform to unfreeze the frozen amount corresponding to the order number information; and after receiving the unfreezing request sent by the live broadcast platform, the payment platform unfreezes the frozen amount corresponding to the order number information. Wherein the frozen amount is a bid by the viewer client.

And step 1106, the live broadcast platform eliminates the audience client with unfrozen money from the bid list.

The live broadcast platform requests a redis database to remove the audience client with unfrozen money; and after receiving a removing request of the live broadcast platform, the redis database removes the audience client with unfrozen money from the bid list.

Step 1107, the live platform determines whether there are any more spectator clients that need to be thawed.

Because there may be a plurality of audience clients needing to be unfrozen, the live broadcast platform judges whether there are any audience clients needing to be unfrozen; when there are more audience clients needing to be unfrozen, the live broadcast platform returns to execute the step 1104; otherwise, ending the judgment and returning the message of ending the repair.

It should be further noted that the CMEM database further stores matching information between the audience client and the anchor client participating in the game, and when the audience client or the anchor client needs to view the information, the audience client or the anchor client may pull the matching information from the CMEM database. Illustratively, in the settlement process of the anchor client, matching information between the audience client and the anchor client participating in the game needs to be checked, the anchor client pulls matching information corresponding to account information of the anchor client from the CMEM database, selects a group of matching information to be settled, as shown in fig. 18, a user interface 51 of the anchor client includes three groups of matching information, selects matching information 52, and settles when receiving a trigger operation on a settlement control 53. As shown in fig. 19, two sets of matching information 62 in which the viewer client participates are included in the user interface 61 of the viewer client. The spectator user may view the matching information for the participating games in the user interface 61.

In summary, the logics shown in fig. 11 to fig. 19 implement the account matching method provided by the present application, and match the accounts respectively corresponding to the anchor client and the audience client on the live broadcast platform in a bidding manner, without the anchor user making rules by himself; the method also directly matches the account numbers respectively corresponding to the anchor client and the audience client to the same network room on the target platform for activity, and does not need to establish a social friend relationship between the anchor user and the audience user and perform team formation after exchanging the account numbers; the man-machine interaction efficiency is improved, the accuracy of the anchor user and the audience user entering the same network room is improved, and the user experience is also improved. In addition, the account matching method improves the interest and the active participation degree of the user in an auction mode.

Referring to fig. 20, an account matching apparatus provided in an exemplary embodiment shown in the present application may implement a part or all of a server through software, hardware, or a combination of the two, and includes:

a receiving module 1201, configured to receive a first matching request sent by a host client, where the first matching request includes a bidding condition;

a sending module 1202, configured to send bid notification information to the viewer client according to the first matching request;

a receiving module 1201, configured to receive a second matching request sent by the viewer client, where the second matching request is sent by the viewer client to the server according to the bid notification information; the second matching request comprises bidding information;

a matching module 1203, configured to match accounts corresponding to the anchor client and the audience client to a same network room on the target platform for activity when the bidding information meets the bidding condition;

wherein the anchor client and the audience client are in the same live broadcast room.

In some embodiments, the first matching request includes a first account corresponding to the anchor client, and the second matching request includes a second account corresponding to the viewer client;

a matching module 1203, configured to match the first account and the second account to the same network room on the target platform through an application program interface API of a target client in the target platform to perform an activity.

In some embodiments, the first account and the second account are accounts logged in the target platform;

the account number of the same user logged in the live broadcast platform and the account number of the same user logged in the target platform are the same account number; or the account number logged in by the same user on the live broadcast platform and the account number logged in by the target platform are different account numbers with a binding relationship.

In some embodiments of the present invention, the,

a receiving module 1201, configured to receive a start request sent by a anchor client;

and a matching module 1203, configured to send network addresses of the network rooms to the anchor client and the viewer client according to the start requests, control the anchor client and the viewer client to start the target client through an API, transmit the network addresses to the target client through the API, and open the network addresses through the target client to enter the network rooms.

In some embodiments, the bidding conditions include that the bids of the viewer clients are the top n maximum bids ranked among the bids of the at least two viewer clients; the bidding information comprises the bidding of the audience client, and n is the matching number;

and a matching module 1203, configured to match, when the bids of the audience clients are the top-n ranked maximum bids, accounts corresponding to the anchor client and the audience clients respectively to the same network room on the target platform for activity.

In some embodiments, the bidding condition further includes the viewer client being in a state of guard for the anchor client; the bidding information also comprises the guard state information of the audience client;

a matching module 1203, configured to execute the step of matching account numbers corresponding to the anchor client and the audience client to a same network room on the target platform for activity when the daemon state information indicates that the audience client is in a daemon state for the anchor client.

In some embodiments of the present invention, the,

a receiving module 1201, configured to receive an authority request sent by a anchor client, where the authority request includes an account number logged in by the anchor client on a live broadcast platform;

a determining module 1204, configured to determine that the anchor client has a matching right when the account belongs to the white list;

a receiving module 1201, configured to execute, according to the matching permission, the step of receiving the first matching request sent by the anchor client.

In summary, the account matching apparatus provided in this embodiment receives a first matching request sent by the anchor client, where the first matching request includes a bidding condition; sending bidding notification information to the viewer client according to the first matching request; receiving a second matching request sent by the audience client, wherein the second matching request is sent to the live broadcast platform by the audience client according to the bidding notification information; the second matching request comprises bidding information; when the bidding information meets the bidding conditions, matching accounts corresponding to the anchor client and the audience client to the same network room on the target platform for activities; wherein the anchor client and the audience client are in the same live broadcast room.

The account matching device matches accounts corresponding to the anchor client and the audience client respectively in a bidding mode without making rules by the anchor user; the device also directly matches the accounts respectively corresponding to the anchor client and the audience client to the same network room on the target platform for activity, and does not need to establish a social friend relationship between the anchor user and the audience user and perform team formation after exchanging the accounts; the man-machine interaction efficiency is improved, the accuracy of the anchor user and the audience user entering the same network room is improved, and the user experience is also improved. Moreover, the account number matching device adopts an auction mode, and the interest and the active participation of the user are improved.

Referring to fig. 21, an account matching apparatus provided in an exemplary embodiment shown in the present application may implement a part or all of a terminal through software, hardware, or a combination of the two, where an anchor client and a target client operate, and the apparatus includes:

a display module 1301, configured to display a first user interface of the anchor client, where the first user interface includes a matching control;

a setting module 1302, configured to set a bidding condition according to a first trigger operation received on the matching control;

the starting module 1303 is used for starting the target client when the bidding information of the viewer client meets the bidding conditions;

a display module 1301, configured to display a second user interface of the target client, where the second user interface is an interface when account numbers corresponding to the anchor client and the audience client are respectively matched with a same network room on the target platform for activity;

In some embodiments of the present invention, the,

a sending module 1304, configured to send a first matching request to a server of a live broadcast platform according to a first trigger operation; the first matching request comprises a bidding condition;

a first receiving module 1305, configured to receive matching success information sent by the server; the matching success information is a message sent by the server to the anchor client when the bidding information of the audience client meets the bidding conditions;

and the starting module 1303 is configured to execute the step of starting the target client.

In some embodiments of the present invention, the,

the display module 1301 is configured to display a third user interface of the anchor client, where the third user interface is an interface that displays a bidding condition of the audience client; when the bidding information of the audience client side meets the bidding conditions, displaying a starting control on a third user interface;

a second receiving module 1306, configured to receive a second trigger operation on the start control;

and the starting module 1303 is configured to start the target client according to the second trigger operation.

In some embodiments of the present invention, the,

a sending module 1304, configured to send a start request to the server according to the second trigger operation;

a first receiving module 1305, configured to receive a network address of a network room sent by the server according to the start request;

and the starting module 1303 is used for calling the API of the target client to start the target client, transmitting the network address to the target client through the API, and opening the network address through the target client to enter the network room.

In summary, the account matching apparatus provided in this embodiment displays a first user interface of the anchor client, where the first user interface includes a matching control; setting a bidding condition according to a first trigger operation received on the matching control; when the bidding information of the audience client side meets the bidding conditions, starting a target client side; displaying a second user interface of the target client, wherein the second user interface is an interface when account numbers corresponding to the anchor client and the audience client are matched with the same network room on the target platform for activities; wherein the anchor client and the audience client are in the same live broadcast room.

Referring to fig. 22, an account matching apparatus provided in an exemplary embodiment shown in the present application may implement a part or all of a terminal through software, hardware, or a combination of the two, in which a viewer client and a target client operate, and the apparatus includes:

a display module 1401, configured to display a fourth user interface of the viewer client, where the fourth user interface is an interface that displays the bidding conditions of the anchor client and the bidding information of the viewer client, and the fourth user interface includes a bidding control;

a setting module 1402, configured to set bidding information according to a third trigger operation received on the bidding control;

a starting module 1403, configured to start the target client when the bidding information meets the bidding condition of the anchor client;

a display module 1401, configured to display a second user interface of the target client, where the second user interface is an interface when account numbers corresponding to the anchor client and the audience client are respectively matched with a same network room on the target platform for activity;

In some embodiments of the present invention, the,

a receiving module 1404, configured to receive bid notification information sent by a server in a live broadcast platform; the bidding notification information is sent to the audience client by the server after receiving the first matching request sent by the anchor client; the bidding notification information comprises bidding conditions of the anchor client and bidding information of the audience client;

a display module 1401, configured to display the fourth user interface according to the bid notification information.

In some embodiments of the present invention, the,

a sending module 1405, configured to send a second matching request to a server in the live broadcast platform according to a third trigger operation; the second matching request comprises bidding information;

a receiving module 1404, configured to receive matching success information sent by the server; the matching success information is a message sent by the server to the audience client when the bidding information meets the bidding condition of the anchor client;

a starting module 1403, configured to execute the step of starting the target client.

In some embodiments of the present invention, the,

a receiving module 1404, configured to receive a network address of a network room sent by a server in the live broadcast platform; the network address is sent to the audience client after the server receives a starting request sent by the anchor client;

a starting module 1403, configured to invoke an API of the target client to start the target client, transmit the network address to the target client through the API, and open the network address through the target client to enter the network room.

In summary, the account matching apparatus provided in this embodiment displays a fourth user interface of the viewer client, where the fourth user interface is an interface that displays the bidding conditions of the anchor client and the bidding information of the viewer client, and the fourth user interface includes a bidding control; setting bidding information according to a third trigger operation received on the bidding control; when the bidding information accords with the bidding conditions of the anchor client, starting the target client; displaying a second user interface of the target client, wherein the second user interface is an interface when account numbers corresponding to the anchor client and the audience client are matched with the same network room on the target platform for activities; wherein the anchor client and the audience client are in the same live broadcast room.

Referring to fig. 23, a block diagram of a terminal 1500 according to an exemplary embodiment of the present application is shown. The terminal 1500 may be: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4), a notebook computer, or a desktop computer. Terminal 1500 may also be referred to as user equipment, a portable terminal, a laptop terminal, a desktop terminal, or other names.

In general, terminal 1500 includes: a processor 1501 and memory 1502.

Processor 1501 may include one or more processing cores, such as a 4-core processor, an 8-core processor, or the like. The processor 1501 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). Processor 1501 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also referred to as a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 1501 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, processor 1501 may also include an AI (Artificial Intelligence) processor for processing computational operations related to machine learning.

The memory 1502 may include one or more computer-readable storage media, which may be non-transitory. The memory 1502 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in the memory 1502 is used to store at least one instruction for execution by the processor 1501 to implement the account matching method provided by the method embodiments herein.

In some embodiments, the terminal 1500 may further include: a peripheral interface 1503 and at least one peripheral. The processor 1501, memory 1502, and peripheral interface 1503 may be connected by buses or signal lines. Various peripheral devices may be connected to peripheral interface 1503 via buses, signal lines, or circuit boards. Specifically, the peripheral device includes: at least one of a radio frequency circuit 1504, a display 1505, an audio circuit 1506, a positioning assembly 1507, and a power supply 1508.

The peripheral interface 1503 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 1501 and the memory 1502. In some embodiments, the processor 1501, memory 1502, and peripheral interface 1503 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1501, the memory 1502, and the peripheral interface 1503 may be implemented on separate chips or circuit boards, which is not limited in this embodiment.

The Radio Frequency circuit 1504 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuitry 1504 communicates with communication networks and other communication devices via electromagnetic signals. The radio frequency circuit 1504 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1504 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 1504 can communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generation mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 1504 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.

The display screen 1505 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 1505 is a touch display screen, the display screen 1505 also has the ability to capture touch signals on or over the surface of the display screen 1505. The touch signal may be input to the processor 1501 as a control signal for processing. In this case, the display screen 1505 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, display 1505 may be one, providing the front panel of terminal 1500; in other embodiments, display 1505 may be at least one, respectively disposed on different surfaces of terminal 1500 or in a folded design; in some embodiments, display 1505 may be a flexible display disposed on a curved surface or a folded surface of terminal 1500. Even further, the display 1505 may be configured in a non-rectangular irregular pattern, i.e., a shaped screen. The Display 1505 can be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), and other materials.

The audio circuitry 1506 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 1501 for processing or inputting the electric signals to the radio frequency circuit 1504 to realize voice communication. For stereo capture or noise reduction purposes, multiple microphones may be provided, each at a different location of the terminal 1500. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 1501 or the radio frequency circuit 1504 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 1506 may also include a headphone jack.

The positioning component 1507 is used for positioning the current geographical position of the terminal 1500 to implement navigation or LBS (Location Based Service). The Positioning component 1507 may be a Positioning component based on the GPS (Global Positioning System) in the united states, the beidou System in china, the graves System in russia, or the galileo System in the european union.

A power supply 1508 is used to power the various components in terminal 1500. The power source 1508 may be ac, dc, disposable, or rechargeable. When the power source 1508 includes a rechargeable battery, the rechargeable battery may support wired charging or wireless charging. The rechargeable battery may also be used to support fast charge technology.

Those skilled in the art will appreciate that the configuration shown in fig. 23 is not intended to be limiting of terminal 1500 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.

Fig. 24 is a schematic structural diagram of a server according to an embodiment of the present application. The server is used for implementing the account matching method provided in the above embodiment. Specifically, the method comprises the following steps:

the server 1600 includes a Central Processing Unit (CPU)1601, a system memory 1604 that includes a Random Access Memory (RAM)1602 and a Read Only Memory (ROM)1603, and a system bus 1605 that connects the system memory 1604 and the central processing unit 1601. The server 1600 also includes a basic input/output system (I/O system) 1606, which facilitates transfer of information between devices within the computer, and a mass storage device 1607 for storing an operating system 1613, application programs 1614, and other program modules 1615.

The basic input/output system 1606 includes a display 1608 for displaying information and an input device 1609 such as a mouse, keyboard, etc. for user input of information. Wherein the display 1608 and input device 1609 are connected to the central processing unit 1601 by way of an input-output controller 1610 which is connected to the system bus 1605. The basic input/output system 1606 may also include an input-output controller 1610 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input-output controller 1610 may also provide output to a display screen, a printer, or other type of output device.

The mass storage device 1607 is connected to the central processing unit 1601 by a mass storage controller (not shown) connected to the system bus 1605. The mass storage device 1607 and its associated computer-readable media provide non-volatile storage for the server 1600. That is, the mass storage device 1607 may include a computer-readable medium (not shown) such as a hard disk or CD-ROM drive.

Without loss of generality, the computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media is not limited to the foregoing. The system memory 1604 and mass storage device 1607 described above may be collectively referred to as memory.

The server 1600 may also operate with remote computers connected to a network via a network, such as the internet, according to various embodiments of the present application. That is, the server 1600 may be connected to the network 1612 through the network interface unit 1611 coupled to the system bus 1605, or the network interface unit 1611 may be used to connect to other types of networks or remote computer systems (not shown).

The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. An account matching method is applied to a server of a live broadcast platform, and comprises the following steps:

sending bidding notification information to a viewer client according to the first matching request, wherein the bidding notification information comprises a starting price, and the viewer client carries out a bidding auction by taking the starting price as a reference price; in the bidding process, updating the bidding notification information to obtain updated bidding notification information, wherein the updated bidding notification information comprises the bidding conditions of the anchor client and the bidding information of the audience client;

receiving a second matching request sent by the audience client, wherein the second matching request is sent to the server by the audience client according to the updated bidding notification information; the second matching request comprises the bidding information;

when the bidding information meets the bidding conditions, receiving a starting request sent by the anchor client;

and sending network addresses of network rooms to the anchor client and the audience client according to the starting request, controlling the anchor client and the audience client to start a target client through an application interface program API (application program interface), and transmitting the network addresses to the target client through the API, wherein the target client is used for jumping to the network addresses to enter the network rooms for activities.

2. The method of claim 1, wherein the first matching request includes a first account corresponding to the anchor client, and wherein the second matching request includes a second account corresponding to the viewer client.

3. The method of claim 2, wherein the first account and the second account are accounts logged into the target platform;

the account number of the same user logged in the live broadcast platform and the account number of the same user logged in the target platform are the same account number;

or the like, or, alternatively,

the account number logged in by the same user on the live broadcast platform and the account number logged in by the target platform are different account numbers with a binding relationship.

4. The method of claim 1, wherein the bidding conditions include that the bids of the viewer clients are the top n maximum bids ranked among the bids of at least two viewer clients; the bidding information comprises the bidding of the audience client, and n is the matching number;

when the bidding information meets the bidding condition, receiving a starting request sent by the anchor client, wherein the starting request comprises the following steps:

receiving the initiation request sent by the anchor client when the bid of the viewer client is the top n-ranked maximum bid.

5. The method of claim 4, wherein the bidding condition further comprises the viewer client being in a state of guard for the anchor client; the bidding information also comprises the guard state information of the audience client;

sending the network address of the network room to the anchor client and the audience client according to the starting request, controlling the anchor client and the audience client to start a target client through an application interface program API, and transmitting the network address to the target client through the API, wherein the target client is used for jumping to the network address to enter the network room for activity, and the method further comprises the following steps:

and when the daemon state information indicates that the audience client is in a daemon state of the anchor client, executing a step of sending the network address of the network room to the anchor client and the audience client according to the starting request, controlling the anchor client and the audience client to start a target client through an application interface program (API), transmitting the network address to the target client through the API, and jumping to the network address by the target client to enter the network room for activity.

6. The method according to any of claims 1 to 5, wherein said receiving a first matching request sent by an anchor client, comprises:

receiving an authority request sent by the anchor client, wherein the authority request comprises an account number logged in by the anchor client on the live broadcast platform;

when the account belongs to a white list, determining that the anchor client has a matching authority;

and executing the step of receiving a first matching request sent by the anchor client according to the matching authority.

7. An account matching method is applied to a first terminal, wherein an anchor client and a target client operate in the first terminal, and the method comprises the following steps:

displaying a first user interface of the anchor client, the first user interface including a matching control;

setting a bidding condition according to a first trigger operation received on the matching control, wherein the bidding condition comprises a starting price;

when the bidding information of the audience client side meets the bidding conditions, starting the target client side; receiving updated bidding notification information in a bidding process, wherein the updated bidding notification information comprises bidding conditions of the anchor client and bidding information of the audience clients, and the bidding information of the audience clients comprises the bidding information of the audience clients at the local end and the bidding information of other audience clients;

and displaying a second user interface of the target client, wherein the second user interface is an interface for sending network addresses of network rooms to the anchor client and the audience client according to starting requests, controlling the anchor client and the audience client to start the target client through an application interface program API (application programming interface), transmitting the network addresses to the target client through the API, and jumping to the network addresses to enter the network rooms for activities.

8. The method of claim 7, wherein after setting the bidding condition according to the first trigger operation received on the matching control, further comprising:

sending a first matching request to a server of a live broadcast platform according to the first triggering operation; the bidding conditions are included in the first matching request;

receiving matching success information sent by the server; the matching success information is a message sent by the server to the anchor client when the bidding information of the viewer client meets the bidding condition;

and executing the step of starting the target client.

9. The method according to claim 7 or 8, wherein the starting the target client when the bidding information of the viewer client meets the bidding condition comprises:

displaying a third user interface of the anchor client, the third user interface being an interface displaying a bid condition of the spectator client;

displaying a start control on the third user interface when the bidding information of the viewer client meets the bidding condition;

receiving a second trigger operation on the starting control;

and starting the target client according to the second trigger operation.

10. The method of claim 9, wherein the starting the target client according to the second trigger operation comprises:

sending a starting request to the server according to the second triggering operation;

receiving the network address of the network room sent by the server according to the starting request;

calling an API of the target client to start the target client, transmitting the network address to the target client through the API, and opening the network address through the target client to enter the network room.

11. An account matching method is applied to a second terminal, wherein a viewer client and a target client operate in the second terminal, and the method comprises the following steps:

receiving bidding notification information sent by a server in a live broadcast platform; the bidding notification information is obtained after being updated by the server in the bidding process; the bid notification information is sent by the server to the viewer client after receiving a first match request sent by a anchor client; the bidding notification information comprises bidding conditions of the anchor client and bidding information of the audience client; the bidding information of the audience client comprises the bidding information of the audience client at the local end and the bidding information of other audience clients;

displaying a fourth user interface according to the bidding notification information, wherein the fourth user interface is an interface for displaying the bidding conditions of the anchor client and the bidding information of the audience client, and the fourth user interface comprises a bidding control;

when the bidding information meets the bidding conditions of the anchor client, starting the target client;

12. The method of claim 11, wherein setting the bid information according to a third trigger operation received on the bid control comprises:

sending a second matching request to a server in the live broadcast platform according to the third triggering operation; the second matching request comprises bidding information;

receiving matching success information sent by the server; the matching success information is a message sent by the server to the audience client when the bidding information meets the bidding condition of the anchor client;

and executing the step of starting the target client.

13. The method according to any of claims 11 to 12, wherein said initiating the target client comprises:

receiving a network address of the network room sent by a server in a live broadcast platform; the network address is sent to the audience client after the server receives a starting request sent by the anchor client;

14. An account matching apparatus, the apparatus comprising:

the receiving module is used for receiving a first matching request sent by an anchor client, wherein the first matching request comprises a bidding condition;

the sending module is used for sending bidding notification information to the audience client according to the first matching request, wherein the bidding notification information comprises a starting price, and the audience client carries out bidding auction by taking the starting price as a reference price; in the bidding process, updating the bidding notification information to obtain updated bidding notification information, wherein the updated bidding notification information comprises the bidding conditions of the anchor client and the bidding information of the audience clients, and the bidding information of the audience clients comprises the bidding information of the audience clients at the local end and the bidding information of the audience clients except the local end;

the receiving module is configured to receive a second matching request sent by the viewer client, where the second matching request is sent by the viewer client to a server according to the updated bid notification information; the second matching request comprises the bidding information;

the matching module is used for receiving a starting request sent by the anchor client when the bidding information meets the bidding conditions; and sending network addresses of network rooms to the anchor client and the audience client according to the starting request, controlling the anchor client and the audience client to start a target client through an application interface program API (application program interface), and transmitting the network addresses to the target client through the API, wherein the target client is used for jumping to the network addresses to enter the network rooms for activities.

15. An account matching apparatus, wherein an anchor client and a target client operate in the apparatus, the apparatus comprising:

the starting module is used for starting the target client when the bidding information of the audience client meets the bidding conditions; in the bidding process, the server receives updated bidding notification information, wherein the updated bidding notification information comprises the bidding conditions of the anchor client and the bidding information of the audience client, and the bidding information of the audience client comprises the bidding information of the audience client at the local end and the bidding information of other audience clients;

the display module is used for displaying a second user interface of the target client, the second user interface is used for sending network addresses of network rooms to the anchor client and the audience client according to starting requests, controlling the anchor client and the audience client to start the target client through an application interface program API (application programming interface), transmitting the network addresses to the target client through the API, and the target client is used for jumping to the network addresses to enter the network rooms to perform activities.

16. An account matching apparatus, wherein a viewer client and a target client operate in the apparatus, the apparatus comprising:

the display module is used for receiving bidding notification information sent by a server in the live broadcast platform; the bid notification information is sent by the server to the viewer client after receiving a first match request sent by a anchor client; the bidding notification information comprises bidding conditions of the anchor client and bidding information of the audience client; displaying a fourth user interface according to the bidding notification information, wherein the fourth user interface is an interface for displaying the bidding conditions of the anchor client and the bidding information of the audience client, and the fourth user interface comprises a bidding control;

the starting module is used for starting the target client when the bidding information accords with the bidding condition of the anchor client;

the display module is used for displaying a second user interface of the target client, the second user interface is used for sending network addresses of network rooms to the anchor client and the audience client according to starting requests, controlling the anchor client and the audience client to start the target client through an application interface program API (application programming interface), transmitting the network addresses to the target client through the API, and the target client is used for jumping to the network addresses to enter the network rooms for activities.

17. An electronic device, the electronic device comprising:

a memory;

a processor coupled to the memory;

wherein the processor is configured to load and execute executable instructions to implement an account matching method according to any one of claims 1 to 6, or an account matching method according to any one of claims 7 to 10, or an account matching method according to any one of claims 11 to 13.

18. A computer readable storage medium having stored therein at least one instruction, at least one program, set of codes, or set of instructions; the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded and executed by a processor to implement an account matching method according to any one of claims 1 to 6, or an account matching method according to any one of claims 7 to 10, or an account matching method according to any one of claims 11 to 13.