Matching request sending method and device, storage medium and electronic equipment

Abstract

The invention discloses a matching request sending method and device, a storage medium and electronic equipment. The method comprises the steps that an interaction interface associated with an interaction account group is displayed in a first application, and the interaction interface is used for displaying interaction information sent by interaction accounts in the interaction group; a target interaction list is displayed in the interaction interface, the target sequence is determined according to target parameters corresponding to the multiple interaction accounts, and the target parameters are account operation parameters of task accounts bound with the interaction accounts in the second application; and under the condition that the target account identifier in the target interaction list is selected, a matching request is sent to a target interaction account indicated by the target account identifier, and the matching request is used for establishing a matching relationship between a current task account bound with the current interaction account and a target task account bound with the target interaction account in the second application. The technical problem that the sending mode of the matching request is tedious in operation is solved.

Description

Technical Field

[0001] The present invention relates to the field of computers, and in particular, to a method and device for sending a matching request, a storage medium, and an electronic device. Background Art

[0002] In various types of interactive applications, it is usually supported that multiple accounts jointly complete interactive tasks. For example, in a game task, multiple user accounts are supported to form a team to complete the game task.

[0003] For users, jointly completing interactive tasks with other users in the game can obtain a better gaming experience. Therefore, users are more inclined to find other users who can match to jointly complete the game task. The existing matching methods usually can only send a matching request to a stranger in the game application, or after establishing a friend relationship through the account identifier of the user account, then send a matching request to complete the matching. It can be seen that the existing method for sending a matching request is usually limited to within the interactive application. If a user wants to add a friend in another application to match and jointly complete the game task, they can only find the corresponding user by searching for the account identifier in the interactive application, and then send a matching request to complete the matching.

[0004] That is to say, the existing method for sending a matching request has the technical problem of cumbersome operation. For the above problems, no effective solution has been proposed yet. Summary of the Invention

[0005] Embodiments of the present invention provide a method and device for sending a matching request, a storage medium, and an electronic device, so as to at least solve the technical problem of cumbersome operation of the method for sending a matching request.

[0006] According to one aspect of an embodiment of the present invention, there is provided a method for sending a matching request, including: displaying an interaction interface associated with an interaction account group in a first application, where the interaction account group includes multiple interaction accounts, and the interaction interface is used to display interaction information sent by the interaction accounts; displaying a target interaction list in the interaction interface, where the target interaction list includes multiple account identifiers arranged in a target order, and the multiple account identifiers respectively indicate one of the interaction accounts, and the target order is determined according to target parameters respectively corresponding to the multiple interaction accounts, and the target parameter is an account operation parameter of a task account bound to the interaction account in a second application, and the account operation parameter is used to indicate the operation performance of the task account in an operation task in the second application; when a target account identifier in the target interaction list is selected, sending a matching request to the target interaction account indicated by the target account identifier, where the matching request is used to establish a matching relationship between a current task account bound to the current interaction account and a target task account bound to the target interaction account in the second application, and when the matching relationship is established between the current task account and the target task account, the current task account and the target task account are used to jointly complete the operation task in the second application.

[0007] According to another aspect of an embodiment of the present invention, there is also provided a device for sending a matching request, including: a first display unit, configured to display an interaction interface associated with an interaction account group in a first application, where the interaction account group includes multiple interaction accounts, and the interaction interface is used to display interaction information sent by the interaction accounts; a second display unit, configured to display a target interaction list in the interaction interface, where the target interaction list includes multiple account identifiers arranged in a target order, and the multiple account identifiers respectively indicate one of the interaction accounts, and the target order is determined according to target parameters respectively corresponding to the multiple interaction accounts, and the target parameter is an account operation parameter of a task account bound to the interaction account in a second application, and the account operation parameter is used to indicate the operation performance of the task account in an operation task in the second application; a sending unit, configured to send a matching request to the target interaction account indicated by the target account identifier when a target account identifier in the target interaction list is selected, where the matching request is used to establish a matching relationship between a current task account bound to the current interaction account and a target task account bound to the target interaction account in the second application, and when the matching relationship is established between the current task account and the target task account, the current task account and the target task account are used to jointly complete the operation task in the second application.

[0008] Optionally, the sending device for the above matching request further includes: a first sending unit, configured to send the above matching request to the target task account bound to the above target interaction account through the above current task account bound to the above current interaction account in the above second application.

[0009] Optionally, the sending device for the above matching request further includes at least one of the following: a third display unit, configured to display a first matching prompt message when the above target interaction account accepts the above matching request; and in response to a confirmation operation on the above first matching prompt message, jump to display the application interface of the above second application; a fourth display unit, configured to display a first matching prompt message in the above first application when the above target task account in the above second application accepts the above matching request; and in response to a confirmation operation on the above first matching prompt message, jump to display the application interface of the above second application; wherein, the above first matching information is used to indicate that in the above second application, the above current task account and the above target task account have established the above matching relationship, and the above application interface is used to display the task scenario in which the above current task account and the above target task account jointly complete the above operation task.

[0010] Optionally, the sending device for the above matching request further includes: a fifth display unit, configured to display a second matching prompt message in the above first application when the current account identifier displayed in the above target interaction list is selected by a first interaction account, wherein, the above current account identifier is used to indicate the above current interaction account, and the above second matching prompt message is used to indicate the above matching request sent by the above first interaction account; a jump unit, configured to, in response to a confirmation operation on the above second matching prompt message, jump to display the application interface of the above second application, wherein, the above application interface is used to display the task scenario in which the above current task account and a first task account jointly complete the above operation task, and the above first task account is the interaction account bound to the above first interaction account in the above second application.

[0011] Optionally, the above fifth display unit further includes at least one of the following: a first display module, configured to, in response to a trigger operation on a first top-listed matching control displayed in the above interaction interface, display the current account identifier of the above current interaction account in the above target interaction list in a target style, wherein, the current account identifier displayed in the above target style indicates that the above current interaction account is in a pending matching state; a second display module, configured to, in response to a trigger operation on a second top-listed matching control displayed in the above interaction interface, display the current account identifier of the above current interaction account at the top of the above target interaction list, wherein, the current account identifier displayed at the top indicates that the above current interaction account is in a pending matching state.

[0012] Optionally, the above-mentioned sending unit includes: a display module, configured to display a matching prompt message in response to a selection operation on the above-mentioned target account identifier, where the above-mentioned matching prompt message indicates that the above-mentioned selection operation is used to send the above-mentioned matching request to the above-mentioned target interaction account; a confirmation module, configured to determine that the above-mentioned target account identifier is selected in response to a confirmation operation on the above-mentioned matching prompt message.

[0013] Optionally, the above-mentioned sending unit is configured to, when the selected above-mentioned target account identifiers are multiple and the selected matching mode is the first matching mode, send the above-mentioned matching requests to the above-mentioned target interaction accounts respectively indicated by the multiple above-mentioned target account identifiers; when the multiple above-mentioned target interaction accounts all accept the above-mentioned matching requests, determine that in the above-mentioned second application, a matching relationship is established between the above-mentioned current task account bound to the above-mentioned current interaction account and the above-mentioned target task accounts respectively bound to the multiple above-mentioned target interaction accounts, where the account set composed of the above-mentioned current task account and the multiple above-mentioned target task accounts is used to jointly complete the above-mentioned operation task in the above-mentioned second application; when the selected above-mentioned target account identifiers are multiple and the selected matching mode is the second matching mode, send the above-mentioned matching requests to the above-mentioned target interaction accounts respectively indicated by the multiple above-mentioned target account identifiers; when the second interaction account among the multiple above-mentioned target interaction accounts accepts the above-mentioned matching request, cancel the above-mentioned matching request sent to the third interaction account among the above-mentioned target interaction accounts, where the above-mentioned third interaction account is the above-mentioned target interaction account other than the above-mentioned second interaction account among the multiple above-mentioned target interaction accounts; determine that in the above-mentioned second application, a matching relationship is established between the above-mentioned current task account bound to the above-mentioned current interaction account and the second task account bound to the above-mentioned second interaction account, where the above-mentioned current task account and the above-mentioned second task account are used to jointly complete the above-mentioned operation task in the above-mentioned second application.

[0014] Optionally, the above-mentioned second display unit includes: an acquisition module, configured to acquire game operation parameters of game task accounts respectively bound to multiple above-mentioned interaction accounts in the above-mentioned interaction account group when the above-mentioned second application is a game application; a determination module, configured to display the above-mentioned account identifiers of the multiple above-mentioned interaction accounts in the above-mentioned target order determined according to the above-mentioned game operation parameters in the above-mentioned target interaction list.

[0015] Optionally, the above-mentioned second display unit is further configured to: when reference operation parameters of a reference game account among the above-mentioned game task accounts are updated, acquire the updated above-mentioned reference operation parameters; adjust the display position of the reference account identifier of the reference game account in the above-mentioned target interaction list according to the updated above-mentioned reference operation parameters.

[0016] Optionally, the second display unit is configured to: when there are multiple game task accounts bound to the interactive account, obtain the group type of the interactive account group, where the multiple game task accounts respectively correspond to one game application; determine a target game application from the multiple game applications according to the group type; obtain the game operation parameters of the target game task accounts respectively bound to the multiple interactive accounts, where the target game task accounts are task accounts in the target game application.

[0017] Optionally, the second display unit is further configured to: when the first application is a live broadcast application, obtain the space type corresponding to the current live broadcast space, where the interactive account group includes the viewer interactive accounts in the current live broadcast space, and the space type is determined according to the media content pushed by the host account that creates the live broadcast space; determine the group type of the interactive account group according to the space type.

[0018] Optionally, the sending unit is configured to perform at least one of the following: in response to a first editing operation on the target interaction list, adjust the display mode of the target interaction list in the interaction interface; in response to a second editing operation on the target interaction list, update the display content in the target interaction list.

[0019] Optionally, the sending unit is configured to perform at least one of the following: in response to selecting a target sorting method from multiple sorting methods, update the display content in the target interaction list according to the target sorting method; when there are multiple game task accounts bound to the interactive account, in response to selecting a target game application from the multiple game applications, obtain target game operation parameters associated with the target game application, where the multiple game task accounts respectively correspond to one game application; update and display the account identifiers of the multiple interactive accounts respectively according to the target order determined by the target game operation parameters.

[0020] Optionally, the sending device for the matching request further includes: a first live broadcast display unit, configured to, when the first application is a live broadcast application and the second application is a game application, in response to selecting the target account identifier in the target interaction list, display the matching request information in the form of bullet chat interaction information on the live broadcast interaction page; a second live broadcast display unit, configured to, when the target interactive account accepts the matching request indicated by the matching request information, display the matching success information in the form of the bullet chat interaction information on the live broadcast interaction page.

[0021] According to another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the above-mentioned method for sending a matching request when running.

[0022] According to another aspect of the embodiments of the present application, there is provided a computer program product, which includes computer programs / instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer programs / instructions from the computer-readable storage medium, and the processor executes the computer programs / instructions, so that the computer device executes the method for sending a matching request as described above.

[0023] According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to execute the above-mentioned method for sending a matching request through the computer program.

[0024] In the embodiments of the present invention, an interaction interface associated with an interaction account group is displayed in a first application, where the interaction account group includes multiple interaction accounts, and the interaction interface is used to display interaction information sent by the interaction accounts; a target interaction list is displayed in the interaction interface, where the target interaction list includes multiple account identifiers arranged in a target order, and each of the multiple account identifiers indicates an interaction account. The target order is determined according to target parameters respectively corresponding to the multiple interaction accounts, and the target parameter is an account operation parameter of a task account bound to the interaction account in a second application. The account operation parameter is used to indicate the operation performance of the task account in the operation task in the second application; when a target account identifier in the target interaction list is selected, a matching request is sent to the target interaction account indicated by the target account identifier, where the matching request is used to establish a matching relationship between the current task account bound to the current interaction account and the target task account bound to the target interaction account in the second application. When the matching relationship is established between the current task account and the target task account, the current task account and the target task account are used to jointly complete an operation task in the second application, thus realizing a method for sending a matching request across applications.

[0025] Through the above embodiments of the present application, in the first application, an interactive account group can be included, and by displaying a target interaction list in the interactive interface to indicate the level sorting of the task operation levels of the task accounts bound to each interactive account in the interactive account group. Furthermore, in the above first application, an interactive account can quickly determine a matchable account based on the task operation level of the task account bound to each interactive account, and by selecting a target account identifier in the target interaction list in the first application, a matching request can be conveniently and quickly sent to the target interactive account to invite the target task account bound to the target interactive account and the current task account bound to the current interactive account to jointly complete an operation task in the second task, solving the technical problem that the existing method for sending a task matching request is relatively cumbersome. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The drawings described herein are used to provide a further understanding of the present invention, form a part of this application, and the illustrative embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0027] Figure 1 is a schematic diagram of the hardware environment of an optional method for sending a matching request according to an embodiment of the present invention;

[0028] Figure 2 is a flowchart of an optional method for sending a matching request according to an embodiment of the present invention;

[0029] Figure 3 is a schematic diagram of an optional method for sending a matching request according to an embodiment of the present invention;

[0030] Figure 4 is a schematic diagram of another optional method for sending a matching request according to an embodiment of the present invention;

[0031] Figure 5 is a schematic diagram of yet another optional method for sending a matching request according to an embodiment of the present invention;

[0032] Figure 6 is a schematic diagram of yet another optional method for sending a matching request according to an embodiment of the present invention;

[0033] Figure 7 is a schematic diagram of yet another optional method for sending a matching request according to an embodiment of the present invention;

[0034] Figure 8 is a schematic diagram of yet another optional method for sending a matching request according to an embodiment of the present invention;

[0035] Figure 9 is a flowchart of another optional method for sending a matching request according to an embodiment of the present invention;

[0036] Figure 10 is a timing diagram of an optional method for sending a matching request according to an embodiment of the present invention;

[0037] Figure 11 is a timing diagram of another optional method for sending a matching request according to an embodiment of the present invention;

[0038] Figure 12 is a schematic structural diagram of an optional device for sending a matching request according to an embodiment of the present invention;

[0039] Figure 13 is a schematic structural diagram of an optional electronic device according to an embodiment of the present invention. Detailed implementation manners

[0040] In order to enable those skilled in the art to better understand the solution of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0041] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to describe a specific order or sequence. It should be understood that such data used in appropriate cases can be interchanged so that the embodiments of the present invention described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those clearly listed steps or units, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0042] It should be noted that in the relevant embodiments of the present application, the acquisition methods of various operation data all comply with the regulations of relevant normative documents, and before obtaining relevant operation data, the permission and authorization of relevant objects need to be obtained.

[0043] According to one aspect of the embodiments of the present invention, a method for sending a matching request is provided. As an optional implementation manner, the above method for sending a matching request can be but is not limited to being applied to, for example, Figure 1A sending system for matching requests in the shown hardware environment, where the sending system for matching requests may include, but is not limited to, terminal device 102, network 104, server 106, database 108, and terminal devices 110 and 112. The target clients of the first application are respectively running on terminal device 102 and terminal device 110 (as Figure 1 shown, taking this target client as a live broadcast client as an example). Specifically, the first client for logging in to the current interaction account may be running on the above-mentioned terminal device 102, and the current interaction account may specifically be a viewer account. The second client for logging in to the target interaction account may be running on terminal device 110, and the third client for logging in to the reference interaction account may be running on terminal device 112. It can be understood that the first client, the second client, and the third client are all clients of the viewer side of the above-mentioned live broadcast application. The above-mentioned terminal device 102, terminal device 110, and terminal device 112 respectively include a human-computer interaction screen, a processor, and a memory. The human-computer interaction screen is used to display the application interface and the interaction operation result (such as the application interface shown in Figure 1 ), and is also used to provide a human-computer interaction interface to receive various interaction operations of the user, including drag operations. The processor is used to generate interaction instructions in response to the above-mentioned human-computer interaction operations and send the interaction instructions to the server. The memory is used to store relevant attribute data. Among them, a first client for logging in to the current interaction account is running on terminal device 102, and the current interaction account can select the account identifier in the target interaction list through the above-mentioned first client to send a matching request to the interaction account indicated by the selected account identifier.

[0044] In addition, the server 106 includes a processing engine, and the processing engine is used to perform storage or reading operations on the database 108. Specifically, the processing engine reads the account attribute information of each interaction account from the database 108.

[0045] Suppose Figure 1 terminal device 102 in is the terminal device used for logging in to the current interaction account, and terminal device 110 is the terminal device used for logging in to the target interaction account. The specific process of this embodiment is as follows: As in step S102, in terminal device 102, an interaction interface associated with the interaction account group is displayed in the first application, where the interaction account group includes multiple interaction accounts, and the interaction interface is used to display the interaction information sent by the interaction accounts; it can be understood that in the case where the above-mentioned first application is a live broadcast application, the above-mentioned interaction account group may be an account set composed of viewer accounts in the same live broadcast room, the above-mentioned interaction interface may be the live broadcast interface of the above-mentioned live broadcast application, and the above-mentioned interaction information may be the live broadcast interaction information sent by the above-mentioned viewer accounts in the above-mentioned live broadcast room, such as comment information, bullet screen information, etc.

[0046] Next, as in steps S104 and S106, a target interaction list is displayed in the interaction interface. The target interaction list includes multiple account identifiers arranged in a target order. The multiple account identifiers respectively indicate an interaction account. The target order is an arrangement order determined according to the account operation parameters of the task accounts respectively bound to the multiple interaction accounts in the second application. The account operation parameters are used to indicate the operation performance of the task accounts in the operation tasks in the second application. When the target account identifier in the target interaction list is selected, a matching request is sent to the target interaction account indicated by the target account identifier. The matching request is used to establish a matching relationship between the current task account bound to the current interaction account and the target task account bound to the target interaction account in the second application. The current task account and the target task account with the established matching relationship are used to jointly complete the operation task in the second application. Next, as in step S108, the matching request is sent to the terminal device 110 through the network 104. Optionally, the above-mentioned matching request can also be sent to the server 106 through 104, and after being processed by the server 106, it is then forwarded to the above-mentioned terminal device 110.

[0047] Next, the terminal device 110 executes step S110 and sends a confirmation message to the terminal device 102 through the network 104.

[0048] Finally, step S112 is executed on the terminal device 102 to display a matching success indication message, which is used to indicate that a matching relationship has been established between the current task account and the target task account in the second application.

[0049] Optionally, in this embodiment, the above-mentioned terminal device can be a terminal device configured with a target client, and can include but are not limited to at least one of the following: mobile phone (such as Android mobile phone, iOS mobile phone, etc.), laptop computer, tablet computer, handheld computer, MID (Mobile Internet Devices), PAD, desktop computer, smart TV, etc. The target client can be a live broadcast client, video client, instant messaging client, browser client, education client, etc., which support providing account interaction operations. The above-mentioned network can include but are not limited to: wired network, wireless network. Among them, the wired network includes: local area network, metropolitan area network and wide area network, and the wireless network includes: Bluetooth, WIFI and other networks that implement wireless communication. The above-mentioned server can be a single server, or a server cluster composed of multiple servers, or a cloud server. The above is only an example, and this embodiment does not make any limitation thereto.

[0050] In an embodiment of the present invention, an interactive interface associated with an interactive account group is displayed in a first application, where the interactive account group includes multiple interactive accounts, and the interactive interface is used to display interactive information sent by the interactive accounts; a target interactive list is displayed in the interactive interface, where the target interactive list includes multiple account identifiers arranged in a target order, and the multiple account identifiers respectively indicate an interactive account, and the target order is an arrangement order determined according to the account operation parameters of the task accounts respectively bound to the multiple interactive accounts in a second application, and the account operation parameters are used to indicate the operation performance of the task accounts in the operation tasks in the second application; when a target account identifier in the target interactive list is selected, a matching request is sent to the target interactive account indicated by the target account identifier, where the matching request is used to establish a matching relationship between the current task account bound to the current interactive account and the target task account bound to the target interactive account in the second application, and the current task account and the target task account with the established matching relationship are used to jointly complete the operation task in the second application, thereby implementing a method for sending a matching request across applications.

[0051] Through the above implementation manner of the present application, the first application may include an interactive account group, and by displaying a target interactive list in the interactive interface to indicate the level sorting of the task operation levels of the task accounts bound to each interactive account in the interactive account group, furthermore, in the above first application, the interactive accounts can quickly judge the matchable accounts according to the task operation levels of the task accounts bound to each interactive account, and by selecting the target account identifier in the target interactive list in the first application, a matching request can be conveniently and quickly sent to the target interactive account to invite the target task account bound to the target interactive account and the current task account bound to the current interactive account to jointly complete the operation task in the second task, solving the technical problem that the existing method for sending a task matching request is relatively cumbersome.

[0052] As an alternative implementation manner, as Figure 2 shown, the above method for sending a matching request can be applied to a live broadcast client logged in by a host account, and includes the following steps:

[0053] S202, display an interactive interface associated with an interactive account group in a first application, where the interactive account group includes multiple interactive accounts, and the interactive interface is used to display interactive information sent by the interactive accounts;

[0054] S204. Display a target interaction list in the interaction interface. The target interaction list includes multiple account identifiers arranged in a target order. Each of the multiple account identifiers indicates an interaction account. The target order is determined according to target parameters respectively corresponding to the multiple interaction accounts. The target parameter is an account operation parameter of the task account bound to the interaction account in the second application. The account operation parameter is used to indicate the operation performance of the task account in the operation task in the second application.

[0055] S206. When the target account identifier in the target interaction list is selected, send a matching request to the target interaction account indicated by the target account identifier. The matching request is used to establish a matching relationship between the current task account bound to the current interaction account and the target task account bound to the target interaction account in the second application. When the matching relationship is established between the current task account and the target task account, the current task account and the target task account are used to jointly complete the operation task in the second application.

[0056] In the above step S202, the first application is an application program that can provide interaction operations between multiple object accounts, and can include, but is not limited to, audio and video type applications, communication type applications, information type applications, etc. Specifically, the above video type applications can specifically be music player applications, short video applications, live broadcast applications, streaming media applications, etc. The communication type applications can specifically be instant messaging applications, and the information type applications can specifically be a kind of information flow application.

[0057] Corresponding to different types of the first application, the composition method of the above interaction account group, the specific function of the interaction interface, and the specific type of interaction information can be different.

[0058] When the first application is an audio and video type application, the above interaction account group can be an account set composed of object accounts associated with the same media resource. Correspondingly, the above interaction interface can be an interaction display area associated with the above media resource, and the above interaction information can be an interaction message sent by the object account based on the above media resource. For example, when the first application is a video application, the above interaction account group can be an account set composed of accounts that have browsed the same video resource, or an account set composed of accounts that have performed interaction operations (such as comment operations, bullet screen operations, favorite operations, etc.) under the same video resource. Further, the above interaction interface can be the playing area and / or comment area of the above video resource, and the above interaction information can be the bullet screen information displayed in the above playing area and / or the comment information displayed in the above comment area.

[0059] In the case where the first application is a communication-type application, the interactive account group may be a set of accounts composed of object accounts with virtual social relationships. Correspondingly, the interactive interface may be an interactive area associated with the account set, and the interactive information may be interactive messages sent by the object accounts in the interactive area. For example, in the case where the first application is an instant messaging application, the interactive account group may be a set of accounts composed of interactive accounts in a chat group, the interactive area may be the group chat interface corresponding to the chat group, and the interactive information may be the interaction information displayed in the group chat interface;

[0060] In the case where the first application is an information-type application, the interactive account group may be a set of accounts composed of object accounts associated with the same information resource. Correspondingly, the interactive interface may be an interactive area associated with the information resource, and the interactive information may be interactive messages sent based on the information resource. For example, in the case where the first application is a news application, the interactive account group may be a set of accounts composed of interactive accounts in the comment area under the same news. Further, the interactive interface may be the comment area under the news resource, and the interactive information may be news comment information sent based on the news resource.

[0061] The above description of the first application in step S202 is only an example and does not limit the actual type of the first application.

[0062] In step S204, a target interaction list may be displayed in the interactive interface to display the account identifiers arranged in the target order in the target interaction list. It can be understood that the target order is the arrangement order determined according to the account operation parameters of the task accounts bound to the respective interactive accounts, and the task accounts are object accounts in the second application. That is, through step S204, the account performance of the task accounts bound to the respective interactive accounts in the second application can be efficiently displayed in the interactive interface of the first application.

[0063] It should be noted that the second application may be an application program for providing various operation tasks. For example, it may include but is not limited to a collaborative office application, a simulated social application, a game application, etc. Corresponding to different types of second applications, the task type of the operation task and the content indicated by the account operation parameters may be different.

[0064] In the case where the second application is a collaborative office application, a collaborative office platform can be provided to organize multiple object accounts to jointly complete office tasks. For example, the second application can be a development platform. Correspondingly, the operation task is a software development task, and the account operation parameter can be used to indicate parameters such as the task processing duration and task volume of the task account that has historically executed the software development task in the above office application;

[0065] In the case where the second application is a simulated social application, a social platform can be provided to organize multiple object accounts to jointly complete virtual social tasks. For example, the second application can be a dating software. Correspondingly, the operation task can be a virtual social task, and the account operation parameter can be used to indicate parameters such as the account level, social frequency, and online duration of the task account in the above social application.

[0066] In the case where the second application is a game application, it is possible to organize multiple game accounts to jointly complete virtual game tasks. Correspondingly, the operation task is a virtual task in the game, and the account operation parameter can be used for the game account level of the above game account in the above game task, recent game operation parameters such as the average number of kills per game and the average number of deaths per game.

[0067] When the second application mentioned above is a game terminal application (Application, abbreviated as APP), it can specifically be a virtual confrontation game application in a Multiplayer Online Battle Arena (abbreviated as MOBA) application; the above confrontation game task can be, but is not limited to, a game task completed by the current player controlling a virtual object in a virtual scene through a human-computer interaction virtual object and interacting with virtual objects controlled by other players; the above method for controlling a virtual object can also be applied to a terminal application of a Multiplayer Online Role-Playing Game (abbreviated as MMORPG). In this type of game, the current player can complete social game tasks in the game from the first perspective of a virtual object in the form of role-playing. For example, complete game tasks together with other virtual objects. Here, the social game tasks can be, but are not limited to, running in an application (such as a non-standalone game APP) in the form of a plugin or a small program, or running in an application (such as a standalone game APP) in a game engine. The types of the above game applications can include, but are not limited to, at least one of the following: Two Dimension (abbreviated as 2D) game application, Three Dimension (abbreviated as 3D) game application, Virtual Reality (abbreviated as VR) game application, Augmented Reality (abbreviated as AR) game application, Mixed Reality (abbreviated as MR) game application. The above is only an example, and this embodiment does not make any limitations on this.

[0068] It should be noted that the binding relationship between the above interactive account and the above task account can be established in advance. Specifically, when the target user creates a first interactive account in the above first application and a first task account in the above second application, the binding between the above first interactive account and the above first task account can be completed through the same identity identifier.

[0069] Further, in the case of displaying the operation performance of the task accounts in the second application through the target interaction list in S204 above, further as in step S206 above, in the first application, the current interaction account can select the interaction account it wants to match according to the sorting of the operation levels of the task accounts bound to each interaction account in the second application, so as to send a matching message to the selected target interaction account, so as to jointly complete the operation task through the current task account and the target task account in the second application. It can be understood that the above-mentioned current task account is the object account in the second application that has a binding relationship with the current interaction account in the first application, and the above-mentioned target task account is the object account in the second application that has a binding relationship with the selected target interaction account in the first application.

[0070] In a specific implementation manner, when the first application is an instant messaging application and the second application is a game application, the above-mentioned interaction interface can be the chat interface corresponding to the chat group in the above-mentioned instant messaging application. In the above-mentioned chat interface, the above-mentioned target interaction list can be displayed to display the account identifiers of the communication accounts bound to each game account in the game application in the order of arrangement of the operation data of each game account in the above-mentioned target interaction list. Furthermore, when the current communication account selects a target communication account from the target interaction list, a game matching request is sent to the target communication account, so as to establish a matching relationship between the current game account bound to the current communication account and the target game account bound to the target communication account in the game application to jointly complete the game task.

[0071] The following combines Figure 3 to illustrate another optional specific implementation manner. When the first application is a live broadcast application and the second application is a game application, as Figure 3 shown, the interaction interface 301 is the live broadcast interface of the target live broadcast room in the above-mentioned live broadcast application, which displays the live broadcast object 302, that is, the user object corresponding to the live broadcast account that created the above-mentioned target live broadcast room. In this implementation manner, the above-mentioned interaction interface is used to display the live broadcast interaction information sent by the audience accounts in the above-mentioned target live broadcast room, such as the interaction information 303, that is, the virtual gift sent by a certain audience account. In the above-mentioned interaction interface 301, a target interaction list 304 is displayed, in which a plurality of account identifiers are displayed in the order of ranking of the account levels of the game accounts bound to each audience account in the game application. It can be understood that in response to the selection operation of the audience account "Aaa" in the target interaction list 304, that is, a matching request is sent from the current audience account to the target audience account "Aaa", so as to establish a matching relationship between the current game account bound to the current audience account and the target game account bound to the target audience account in the game application, and then jointly complete the game task in the game application.

[0072] In an embodiment of the present invention, an interaction interface associated with an interaction account group is displayed in a first application. The interaction account group includes multiple interaction accounts, and the interaction interface is used to display interaction information sent by the interaction accounts. A target interaction list is displayed in the interaction interface. The target interaction list includes multiple account identifiers arranged in a target order. Each of the multiple account identifiers indicates an interaction account. The target order is an arrangement order determined according to the account operation parameters of the task accounts respectively bound to the multiple interaction accounts in a second application. The account operation parameters are used to indicate the operation performance of the task accounts in the operation tasks in the second application. When a target account identifier in the target interaction list is selected, a matching request is sent to the target interaction account indicated by the target account identifier. The matching request is used to establish a matching relationship between the current task account bound to the current interaction account and the target task account bound to the target interaction account in the second application. The established current task account and target task account are used to jointly complete an operation task in the second application, thereby implementing a method for sending a matching request across applications.

[0073] Through the above implementation manner of the present application, the first application may include an interaction account group, and by displaying a target interaction list in the interaction interface to indicate the level sorting of the task operation levels of the task accounts bound to each interaction account in the interaction account group. Furthermore, in the above first application, the interaction accounts can quickly determine the matchable accounts according to the task operation levels of the task accounts bound to each interaction account, and by selecting the target account identifier in the target interaction list in the first application, a matching request can be conveniently and quickly sent to the target interaction account to invite the target task account bound to the target interaction account and the current task account bound to the current interaction account to jointly complete an operation task in a second task, solving the technical problem that the existing method for sending a task matching request is relatively cumbersome.

[0074] In an alternative implementation manner, when the matching request is sent to the target interaction account indicated by the target account identifier in the case of selecting the target account identifier in the target interaction list, it further includes: in the second application, sending a matching request from the current task account bound to the current interaction account to the target task account bound to the target interaction account.

[0075] It can be understood that in this implementation manner, while sending a matching request from the current interaction account to the target interaction account in the first application, a matching request can be synchronously sent from the current task account to the target interaction account in the second application to ensure that the sent matching request can be received in time by the target interaction account or its bound target task account.

[0076] The above embodiments are described in conjunction with specific implementation manners. When the target interactive account is currently in the operating state of the first application (for example, when it is in the state of watching the target live broadcast room in the live broadcast application), sending a matching request to the above target interactive account through the current interactive account can be received by the target interactive account in a timely manner; and when the target interactive account is currently in the hanging state of the first application and the target task account is in the operating state, a matching request can be sent to the target task account in the second application through the current task account at the same time to ensure that the matching request is accepted by the target task account. For example, the target user logs in to the live broadcast application through the target live broadcast account and is located in the target live broadcast room, but actually does not watch the target live broadcast room (the live broadcast account is in the hanging state), and at the same time logs in to the game application through the game account bound to the live broadcast account, then a matching request sent by the current task account can be received in the game application, and the matching request can be responded to in a timely manner to achieve fast matching.

[0077] Through the above implementation manner of the present application, while sending a matching request to the target interactive account through the current interactive account in the first application, a matching request is synchronously sent to the target interactive account through the current task account in the second application to ensure that the sent matching request can be received by the target interactive account or its bound target task account in a timely manner. The user avatar can be directly clicked on the live platform leaderboard for game teaming and invitation. After the leaderboard user clicks to agree, a teaming invitation can be directly popped up in the game, without manually searching for information such as the inviter's room number and account in the game. It can realize real-time synchronization of the game leaderboard of the audience account authorized by the live platform live broadcast room to the live platform, and there is no need to manually upload personal battle records for the operation to sort out the leaderboard information for users by manual identification, and notify users of teaming information through in-site messages, etc., improving the account matching efficiency.

[0078] In an optional implementation manner, after sending a matching request to the target interactive account indicated by the target account identifier when the target account identifier in the target interactive list is selected, at least one of the following is further included:

[0079] Method 1: When the target interactive account accepts the matching request, display the first matching prompt message; in response to the confirmation operation on the first matching prompt message, jump to display the application interface of the second application;

[0080] Method 2: When the target task account in the second application accepts the matching request, display the first matching prompt message in the first application; in response to the confirmation operation on the first matching prompt message, jump to display the application interface of the second application;

[0081] Among them, the first matching information is used to indicate that in the second application, a matching relationship has been established between the current task account and the target task account, and the application interface is used to display the task scenario in which the current task account and the target task account jointly complete the operation task.

[0082] It can be understood that in this embodiment, when the target interaction account in the first application accepts the above matching request, and / or when the target task account in the second application accepts the above matching request, the above first matching prompt information can be displayed in the application interface of the current interaction account to indicate that the current task account and the target task account have completed matching in the second application.

[0083] In this embodiment, a one-key jump method between applications is also provided. Specifically, through the confirmation operation of the above first matching prompt information, the second application can be launched with one key, and the task interface in which the current task account and the target task account jointly execute the operation task is displayed in the second application.

[0084] In the case where the first application is a live application and the second application is a game application, as Figure 4 shown in figure (a), when the target interaction account in the first application accepts the above matching request, and / or when the target task account in the second application accepts the above matching request, the first matching prompt information 401 "Aaa has accepted your matching invitation. Let's start playing the game together quickly!" is displayed in the interaction interface to indicate that a matching relationship has been established between the current task account and the target task account in the second application. Furthermore, in response to the trigger operation on the "Confirm" control in the first matching prompt information 401, Figure 4 as shown in figure (b), the game application is launched and run on the terminal, and the current task object 402 controlled by the current task account and the target task object 403 controlled by the target task account are displayed in the game task scenario in the game application, so as to enable the current task account and the target task account to jointly complete the game task in the game scenario by controlling their respective virtual objects. It can be understood that in response to the trigger operation on the "Cancel" control in the first matching prompt information 401, the matching relationship between the current task account and the target task account in the second application can be cancelled.

[0085] Through the above embodiments of the present application, when the target interaction account in the first application accepts the above matching request, and / or when the target task account in the second application accepts the above matching request, by displaying the first matching prompt information and in response to the confirmation operation on the first matching prompt information, a quick jump is made to the application interface corresponding to the matching of the two task accounts in the second application, thereby improving the matching efficiency of account matching.

[0086] In an alternative embodiment, when the interactive interface associated with the interactive account group is displayed in the first application, it further includes:

[0087] S1. When the current account identifier displayed in the target interaction list is selected by the first interactive account, display a second matching prompt message in the first application, where the current account identifier is used to indicate the current interactive account, and the second matching prompt message is used to indicate the matching request sent by the first interactive account;

[0088] S2. In response to the confirmation operation on the second matching prompt message, jump to display the application interface of the second application, where the application interface is used to display the task scenario in which the current task account and the first task account jointly complete the operation task, and the first task account is the interactive account bound to the first interactive account in the second application.

[0089] In this embodiment, when the current interactive account is the interactive account receiving the matching request, a second matching prompt message can be displayed in the first application to indicate that the current interactive account has received the matching request sent by the first interactive account. Furthermore, in response to the confirmation operation on the second matching prompt message, the application interface of the second application can be directly jumped to display to show the task scenario in which the current task account and the first task account jointly complete the operation task.

[0090] As Figure 5 shown, when the current interactive account receives the matching request sent by the first interactive account "Sunshine Rainbow", display the second matching prompt message 501 "Sunshine Rainbow invites you to play together. Do you accept?" It can be understood that when the current interactive account triggers the "confirm" control in the above second matching prompt message 501, the matching relationship between the first task account and the target task account can be established in the second application, and the virtual task scenario in which the first task account and the target task account in the game application control their respective virtual objects to jointly complete the game task can be jumped to display.

[0091] Through the above embodiment of the present application, when the current account identifier displayed in the target interaction list is selected by the first interactive account; in response to the confirmation operation on the second matching prompt message, jump to display the application interface of the second application, thereby realizing the quick jump to display the application interface of the second application when receiving and accepting the matching request, and improving the matching efficiency of account matching.

[0092] In an alternative embodiment, before displaying the second matching prompt message in the first application interface, it further includes at least one of the following:

[0093] Method 1: In response to a trigger operation on the first listed matching control displayed in the interactive interface, the current account identifier of the current interactive account is displayed in the target interactive list in the target style, where the current account identifier displayed in the target style indicates that the current interactive account is in a pending matching state;

[0094] Method 2: In response to a trigger operation on the second listed matching control displayed in the interactive interface, the current account identifier of the current interactive account is displayed at the top in the target interactive list, where the current account identifier displayed at the top indicates that the current interactive account is in a pending matching state.

[0095] It can be understood that in this embodiment, the display method of the account identifier of the current interactive account in the target interactive list, in addition to being arranged and displayed in the target order, can also have various ways to improve the display effect of the account identifier of the current interactive account, so as to attract other interactive accounts to initiate a matching request to the current interactive account.

[0096] In the above Method 1, through the trigger operation on the first listed matching control, the current account identifier of the current interactive account can be displayed in the target interactive list in the target style, that is, the current account identifier is prominently displayed. The above target style can include, but is not limited to, a display style that highlights the current account identifier, or a display style that adds decorative elements to the current account identifier, so as to prominently display the current account identifier in the target interactive list;

[0097] In the above Method 2, through the trigger operation on the second listed matching control, the current account identifier can be displayed at the top in the target interactive list, so as to facilitate other interactive accounts to initiate a matching request to the current interactive account.

[0098] It can be understood that the above Method 1 and Method 2 can also be combined, that is, two different controls are provided to prominently display the current account identifier in different ways. In an optional embodiment, different prominent display methods can be configured according to the account level of the current interactive account. For example, for high-level interactive accounts, both the above Method 1 and Method 2 are configured as prominent display methods, and for low-level interactive accounts, only the prominent display method shown in the above Method 1 is configured.

[0099] In an optional embodiment, when the reference interactive account selects the current account identifier prominently displayed by the above Method 1 or Method 2, the current task account bound to the current interactive account can be directly matched with the reference task account bound to the reference interactive account in the second application, and the task interface in the second application is jumped to and displayed.

[0100] Such as Figure 6As shown in Figure (a) below, when the first application is a live broadcast application, while the target interaction list 603 is displayed in the live broadcast interface, the first ranked matching control 601 "Cool Display" and the second ranked matching control 602 "Top Display" can be displayed. When the account identifier of the current interaction account is "Two-dimensional mid laner", in response to the trigger operation on the first ranked matching control 601 "Cool Display", the interface is displayed as shown in Figure 6 Figure (b) below. The account identifier "Two-dimensional mid laner" is highlighted in the original position in the target interaction list in a highlighted style; in response to the trigger operation on the first ranked matching control 602 "Top Display", the interface is displayed as shown in Figure 6 Figure (c) below. The account identifier "Two-dimensional mid laner" is highlighted at the top position in the target interaction list.

[0101] Through the above implementation manners of the present application, in response to the trigger operation on the first ranked matching control displayed in the interaction interface, the current account identifier of the current interaction account is displayed in the target interaction list in a target style, and / or, in response to the trigger operation on the second ranked matching control displayed in the interaction interface, the current account identifier of the current interaction account is displayed at the top in the target interaction list, so as to highlight the current account identifier and improve the account matching efficiency.

[0102] In an alternative implementation manner, the above-mentioned sending a matching request to the target interaction account indicated by the target account identifier when the target account identifier in the target interaction list is selected includes:

[0103] S1. In response to the selection operation on the target account identifier, a matching prompt message is displayed, where the matching prompt message indicates that the selection operation is used to send a matching request to the target interaction account;

[0104] S2. In response to the confirmation operation on the matching prompt message, it is determined that the target account identifier is selected.

[0105] As shown in Figure 7 Figure (a) below, in response to the click operation on the target interaction account 701 "Aaa", the interface is displayed as shown in Figure 7 Figure (b) below. The matching prompt message 702 "Do you want to send a matching invitation to Aaa?" is displayed in the interaction interface. In response to the trigger operation on the "Confirm" control, it is determined that the above-mentioned target interaction account 701 is selected.

[0106] In an alternative implementation manner, the above-mentioned sending a matching request to the target interaction account indicated by the target account identifier when the target account identifier in the target interaction list is selected includes:

[0107] Method 1: When multiple selected target account identifiers are present and the selected matching mode is the first matching mode, send matching requests to the target interaction accounts respectively indicated by the multiple target account identifiers; when all the multiple target interaction accounts accept the matching requests, determine that in the second application, a matching relationship is established between the current task account bound to the current interaction account and the target task accounts respectively bound to the multiple target interaction accounts, where the account set composed of the current task account and the multiple target task accounts is used to jointly complete an operation task in the second application;

[0108] Method 2: When multiple selected target account identifiers are present and the selected matching mode is the second matching mode, send matching requests to the target interaction accounts respectively indicated by the multiple target account identifiers; when the second interaction account among the multiple target interaction accounts accepts the matching request, cancel the matching request sent to the third interaction account among the target interaction accounts, where the third interaction account is the target interaction account other than the second interaction account among the multiple target interaction accounts; determine that in the second application, a matching relationship is established between the current task account bound to the current interaction account and the second task account bound to the second interaction account, where the current task account and the second task account are used to jointly complete an operation task in the second application.

[0109] It can be understood that in this embodiment, two methods of sending matching requests to multiple interaction accounts are provided. In the first method above, when the matching mode is the first matching mode, multiple account identifiers can be selected in the target interaction list, and matching requests are sent to the target interaction accounts and target task accounts respectively corresponding to the multiple account identifiers, and when the target interaction accounts or target task accounts respectively corresponding to the multiple account identifiers all accept the above matching requests, it is determined that the account set composed of the multiple target task accounts and the above current task account is successfully matched.

[0110] Obviously, in the first method above, the first matching mode can be a multi-row task mode, indicating that three or more task accounts form an account team to jointly complete the above operation task.

[0111] In the second method above, when the matching mode is the second matching mode, multiple account identifiers can be selected in the target interaction list, and matching requests are sent to the target interaction accounts and target task accounts respectively corresponding to the multiple account identifiers, and when any one of the target interaction accounts or target task accounts respectively corresponding to the multiple account identifiers accepts the above matching request, it is determined that the target task account that has accepted the above matching request and the above current task account are successfully matched.

[0112] Obviously, in the above second method, the above second matching mode may be a double-row task mode, indicating that after two task accounts form an account team, they jointly complete the above operation task. Therefore, when any one of the target interaction accounts or target task accounts accepts the above matching request, the matching requests sent to other accounts are cancelled.

[0113] Optionally, before selecting multiple target account identifiers, one can long-press any account identifier in the above target interaction list to trigger the entry into the multi-selection mode;

[0114] Optionally, when multiple target account identifiers are selected, two matching mode selection controls can be further provided in the displayed matching prompt information to determine whether the current matching mode is the first matching mode or the second matching mode.

[0115] Through the above implementation manners of the present application, two methods for mass-sending matching requests are provided. In the above first method, an account set can be formed to jointly complete an operation task when all the mass-sent matching requests are accepted; in the above second method, when any one of the mass-sent matching requests is accepted, it is directly determined that two task accounts are successfully matched, thereby improving the diversity of the matching mode and also improving the account matching efficiency.

[0116] In an optional implementation manner, the above display of the target interaction list in the interaction interface includes:

[0117] S1. When the second application is a game application, obtain the game operation parameters of the game task accounts bound to multiple interaction accounts in the interaction account group;

[0118] S2. Display the account identifiers of multiple interaction accounts in the target interaction list in the target order determined according to the game operation parameters.

[0119] It can be understood that in this implementation manner, the arrangement order of each account identifier can be determined through the obtained game operation parameters. The above game operation parameters may include, but are not limited to, the game account level, account rank, historical game operation data, such as the historical average number of defeats per game, the historical average damage value, etc. In this implementation manner, the parameter type of the above game operation parameters is not limited.

[0120] Optionally, when obtaining the game operation parameters of each game task account, the account status of each game task account can be further obtained to indicate whether the corresponding game task account is currently in a game task. For example, the above game task status may be "idle", indicating that the corresponding game task account is not currently in a game battle; the above game task status may also be "in battle", indicating that the corresponding game task account is currently in a game battle.

[0121] The following is a description of a display method for a target interaction list. As Figure 8 shown, in the target interaction list 801, the arrangement order of each account identifier can be determined according to the account level of the game account bound to each interaction account. In addition, the interaction account information corresponding to each account identifier can be included in the above target interaction list. Taking the interaction account information 802 as an example, it may include the ranking information "NO.3" of the interaction account, indicating the third place, the avatar identifier of the interaction account, the account identifier "Sunshine Rainbow", the account level "Level 96" of the corresponding task account, and the game task status "In the game". Figure 8 In addition, a binding control 803 is also displayed in the target interaction list 801. It can be understood that in this embodiment, it is necessary to obtain the account operation data of the game account bound to the interaction account to perform the arrangement and display. Therefore, if the current interaction account has not performed the account binding operation, the binding control 803 can be triggered to perform the account binding, and after the account binding is completed, the arrangement and display are performed according to the game operation data of the current task account bound to the current interaction account.

[0122] Through the above embodiments of the present application, when the second application is a game application, the game operation parameters of the game task accounts bound to multiple interaction accounts in the interaction account group are obtained; the account identifiers of the multiple interaction accounts are displayed in the target interaction list in the target order determined according to the game operation parameters, so that the account identifiers are arranged and displayed according to the game account operation data of the game accounts bound to each account in the second application, thereby enabling each interaction account to conveniently and quickly determine the interaction account to be matched according to the arrangement result, and further improving the account matching efficiency.

[0123] In an alternative embodiment, when the target interaction list is displayed in the interaction interface, it further includes:

[0124] S1. When the reference operation parameter of the reference game account in the game task account is updated, obtain the updated reference operation parameter;

[0125] S2. Adjust the display position of the reference account identifier of the reference game account in the target interaction list according to the updated reference operation parameter.

[0126] S2. Adjust the display position of the reference account identifier of the reference game account in the target interaction list according to the updated reference operation parameter.

[0127] It can be understood that, in this embodiment, the game operation parameters of the game task accounts bound to each interactive account can be obtained in real time. Furthermore, when the game operation parameters obtained in real time are updated, the display order of each account identifier in the above target interaction list can be adjusted in real time according to the updated data in the target interaction list.

[0128] In an alternative embodiment, when the second application is a game application, obtaining the game operation parameters of the game task accounts bound to multiple interactive accounts in the interactive account group includes:

[0129] S1, when there are multiple game task accounts bound to the interactive account, obtain the group type of the interactive account group, where the multiple game task accounts respectively correspond to a game application;

[0130] S2, determine the target game application from multiple game applications according to the group type;

[0131] S3, obtain the game operation parameters of the target game task accounts bound to multiple interactive accounts, where the target game task accounts are task accounts in the target game application.

[0132] It can be understood that, in this embodiment, each interactive account in the above interactive account group may be bound to multiple game task accounts, and each game task account corresponds to a game task respectively. For example, the first interactive account in the interactive account group is bound to three game task accounts, corresponding to Game A, Game B, and Game C respectively; the second interactive account is bound to two game task accounts, corresponding to Game A and Game B respectively; the third interactive account is bound to three game task accounts, corresponding to Game A and Game C respectively; the fourth interactive account is bound to three game task accounts, corresponding to Game A, Game C, and Game D respectively.

[0133] That is to say, there are multiple copies of game operation data corresponding to each interactive account. In this embodiment, the group type corresponding to the current interactive account group can be determined first, and then the game operation data of the corresponding type can be obtained according to this type for the display of the target interaction list. For example, when the game application corresponding to the group type of the current interactive account group is Application A, the game operation data of Game A corresponding to the above first interactive account, second interactive account, third interactive account, and fourth interactive account can be obtained for the display of the target interaction list; another example is that when the game application corresponding to the group type of the current interactive account group is Application C, the game operation data of Game C corresponding to the above first interactive account, third interactive account, and fourth interactive account can be obtained for the display of the target interaction list.

[0134] The determination method of the above group type may vary according to the above first application type. For example, when the above first application is an instant messaging application, correspondingly, the above interactive account group is a chat group, and the corresponding game type can be determined according to the group identifier of the above chat group. For example, when the group identifier is "A game communication group", the game type of the above chat group can be determined as "A game", and then it can be matched with the A game; in another way, the corresponding game type can also be determined according to the interaction content of the chat group in the past period of time. For example, when the interaction content of the chat group today is mainly related to "A game", the game type of the above chat group can be determined as "A game", and then it can be matched with the A game.

[0135] For another example, when the above first application is a video application, correspondingly, the above interactive account group is an account set composed of interactive accounts in the comment area or bullet screen area of the same video resource. Furthermore, the group type of the above interactive group can be determined according to the resource type of the above video resource. For example, when the above video resource is a strategy video of "A game", the game type of the above interactive group can be determined as "A game", and then it can be matched with the A game.

[0136] Through the above implementation manners of the present application, when there are multiple game task accounts bound to the interactive account, the group type of the interactive account group is obtained; the target game application is determined from multiple game applications according to the group type; the game operation parameters of the target game task accounts bound to the multiple interactive accounts are obtained, and then the target game application is determined from multiple game applications to display the target interaction list, improving the accuracy of the display of the interactive account.

[0137] In an optional implementation manner, before determining the target game application from multiple game applications according to the group type, it further includes:

[0138] S1, when the first application is a live broadcast application, obtain the space type corresponding to the current live broadcast space, where the interactive account group includes the viewer interactive accounts in the current live broadcast space, and the space type is determined according to the media content pushed by the host account that creates the live broadcast space;

[0139] S2, determine the group type of the interactive account group according to the space type.

[0140] It can be understood that in this embodiment, when the first application is a live broadcast application, the corresponding group type can be determined according to the space type of the current live broadcast space. For example, the above space type can be determined according to the content currently being broadcast by the host object. When the content currently being broadcast by the host object is a game live broadcast of Game A, it can be determined that the space type of the above live broadcast space is "Game A", and further determine that the group type of the audience account group associated with this live broadcast room is also "Game A" (indicating that the audience accounts in the audience account group associated with this live broadcast room are all interested in Game A), and then the game accounts of Game A bound to each audience account can be obtained and displayed in ranking in the live broadcast room.

[0141] Through the above embodiments of the present application, when the first application is a live broadcast application, the space type corresponding to the current live broadcast space is obtained; the group type of the interactive account group is determined according to the space type, so that the sorting basis and display content of the target interactive list to be displayed in the current live broadcast room can be determined according to the type of the live broadcast room, and the interactive effect between each audience account can be improved through the interactive effect of the live broadcast room.

[0142] In an alternative embodiment, the displaying the target interactive list in the interactive interface includes at least one of the following:

[0143] Method 1: In response to a first editing operation on the target interactive list, adjust the display mode of the target interactive list in the interactive interface;

[0144] Method 2: In response to a second editing operation on the target interactive list, update the display content in the target interactive list.

[0145] It can be understood that in this embodiment, the current object account can perform various display adjustment operations on the target interactive list displayed in the current interactive interface.

[0146] In the above first method, the display mode of the target interactive list can be adjusted through the first editing operation. The adjustment methods of the above display mode can include but are not limited to dragging the target interactive list to adjust the display position; zooming in or out on the target interactive list to adjust the display size; updating the display pattern, display style, and display elements of the above target interactive list, etc. In this embodiment, the specific operation type of the above first editing operation is not limited.

[0147] In the above second method, the display content in the above target interactive list can be adjusted. Specifically, the updating the display content in the target interactive list in response to the second editing operation on the target interactive list includes at least one of the following:

[0148] Method 1: In response to selecting a target sorting method from multiple sorting methods, update the display content in the target interaction list according to the target sorting method;

[0149] Method 2: When there are multiple game task accounts bound to the interaction account, in response to selecting a target game application from multiple game applications, obtain the target game operation parameters associated with the target game application, where each of the multiple game task accounts corresponds to one game application; update the display of the account identifiers of each interaction account according to the target order determined by the target game operation parameters.

[0150] It can be understood that in this embodiment, the above two methods for adjusting the display content are provided. In Method 1 above, the sorting method of each account identifier in the target interaction list can be adjusted. Specifically, the sorting basis of each account identifier can be adjusted. For example, when the initial sorting basis is "game account level", the above sorting basis can be changed to "average number of defeats per game in the past week", and then in response to the adjustment of the sorting basis, update the arrangement order of each account identifier in the target interaction list;

[0151] In Method 2 above, when there are multiple game task accounts bound to each interaction account, the account operation data of each game task account in each game application can be obtained simultaneously, and according to the selection of the target application among multiple game applications, display the sorting content of the corresponding game application.

[0152] Continuing with the example where the first interaction account in the interaction account group has three game task accounts bound to it, corresponding to Game A, Game B, and Game C respectively; the second interaction account has two game task accounts bound to it, corresponding to Game A and Game B respectively; the third interaction account has three game task accounts bound to it, corresponding to Game A and Game C respectively; and the fourth interaction account has three game task accounts bound to it, corresponding to Game A, Game C, and Game D respectively. In this embodiment, the account data of the game accounts bound to each interaction account in the above Game A, Game B, Game C, and Game D can be obtained simultaneously, and the corresponding identifier sorting results can be generated based on the game account data of the above four games. In this embodiment, in response to the selection operation of any one of the above games, the identifier sorting result corresponding to the selected game application can be switched and displayed.

[0153] Optionally, when the account types of the current interactive accounts are different, different adjustment methods can be configured for the current interactive accounts. For example, when the current interactive account is a host account, the above two editing display methods, i.e., the first editing operation and the second editing operation, can be configured for the host account; when the current interactive account is an audience account, the editing display adjustment method corresponding to the above first editing operation can be configured for the audience account.

[0154] Through the above implementation manners of the present application, in response to the first editing operation on the target interactive list, the display manner of the target interactive list is adjusted in the interactive interface; in response to the second editing operation on the target interactive list, the display content in the target interactive list is updated, so as to facilitate the current interactive account to adjust the display manner and the display content, and further improve the display flexibility of the above target interactive list.

[0155] In an optional implementation manner, after the target interactive list is displayed in the interactive interface, the following is further included:

[0156] S1. When the first application is a live broadcast application and the second application is a game application, in response to selecting the target account identifier in the target interactive list, the matching request information is displayed in the form of bullet chat interactive information on the live broadcast interactive page;

[0157] S2. When the target interactive account accepts the matching request indicated by the matching request information, the matching success information is displayed in the form of bullet chat interactive information on the live broadcast interactive page.

[0158] It can be understood that in this implementation manner, when the first application is a live broadcast application and the second application is a game application, the matching requests and the matching success information between each account can be displayed in the live broadcast room in the form of live broadcast room bullet chats or live broadcast room comments, so as to improve the enthusiasm of the matching interaction between each interactive account.

[0159] The following combines Figure 9 to specifically illustrate the specific implementation manners of the above implementation manners.

[0160] As Figure 9 shown, the above implementation manner at least includes the following processes:

[0161] S902. Character frame initialization;

[0162] S904. Binding / switching account process;

[0163] S906. Binding / switching character process.

[0164] Specifically, to enable the live application accounts on the live platform side to obtain the ranking information of game data in the live room environment, the middle - tier application can be used to obtain the game account information corresponding to each live application account, and then, based on the game account information, notify the game application to synchronize the player game data.

[0165] For this purpose, the middle - tier application needs to develop a game account binding intermediate page, which is invoked by the live application account. The live platform directly passes the user identifier of the live application account on the platform side to the account binding intermediate page of the middle - tier application without processing or modification. At this point, the account binding intermediate page of the middle - tier application has the information of the live platform, and then it instructs the user to log in to the game - side game account information on the account binding intermediate page, so as to obtain the game account information. Finally, the mapping relationship between the live platform account and the game account is saved to the middle - tier application.

[0166] The following combines Figure 10 to illustrate the interaction process among the above - mentioned live platform, middle - tier application, and game application during the display process of the target interaction list.

[0167] S1002, the live platform pushes the user identifier of the live platform of the user on the list to the middle - tier application;

[0168] S1004, the middle - tier application pushes the white - listed user account identifier & role identifier & live platform identifier to the game application;

[0169] S1006, the game application returns the white - listing result return status parameter & user account identifier & role identifier & live platform identifier;

[0170] S1008, the middle - tier application returns the white - listing result return status parameter & live platform user identifier to the live platform;

[0171] S1010, the game application pushes the game real - time data status parameter & user account identifier & role identifier & time to the live platform;

[0172] S1012, the middle - tier application generates the ranking list user identifier & ranking list according to the live platform configuration;

[0173] S1014, the middle - tier application pushes the platform status parameter & ranking list user identifier & ranking list to the live platform;

[0174] S1016, the live platform confirms the receipt of the status parameter & ranking list user identifier & ranking list.

[0175] Specifically, in the above process, according to the information configured by the live streaming platform in the middle - tier application, the middle - tier application will receive the live streaming account information of the live streaming bound user, convert it into game account information, and push it to the game. After the game whitelisting is successful, that is, the game sets the account in the push data whitelist on the game side, the game will return a confirmation message to the middle - tier application. When the live streaming player plays the corresponding game, the player's real - time data information is pushed to the middle - tier application. The middle - tier application will receive the player's real - time data information and generate a leaderboard according to the leaderboard configuration information configured by the live streaming platform in the middle - tier application. If there are changes in the leaderboard data, the live streaming platform data receiving service will be called to synchronize the leaderboard information to the live streaming platform. After receiving the information, the live streaming platform will display the latest leaderboard.

[0176] The following combines Figure 11 to illustrate the interaction process among the above - mentioned live streaming platform, middle - tier application, and game application during the matching and team - forming process.

[0177] S1102, the live streaming platform sends team - forming request information of live streaming users to the middle - tier application;

[0178] S1104, the middle - tier application pushes team - forming & PK information to the game application, which can include but is not limited to user account identification, character identification, live streaming platform identification, leaderboard user account identification, leaderboard character identification, etc.;

[0179] S1106, the game application returns status parameters to the middle - tier application for the request result;

[0180] S1108, the middle - tier application returns status parameters and live streaming platform user identification to the live streaming platform for the game whitelisting result.

[0181] In the above - mentioned embodiment, the middle - tier application will receive the team - forming request of the live streaming bound user, convert it into game account information, and push it to the game. According to the requested information, the game will display the corresponding requested information for the leaderboard users in the game.

[0182] In the above - mentioned embodiment of the present application, in order to achieve account interoperability between the live streaming platform and the game application, a standardized access service is provided through the middle - tier application, and the middle - tier application is responsible for compatible with the account systems of different games.

[0183] First, the game application configures the account information to the middle - tier application side and grants the middle - tier application the permission to query the account information interface. The middle - tier application provides a pull - up service interface for the live streaming platform, and the live streaming platform transmits the live streaming user identification to the middle - tier application according to the protocol. When the live streaming user clicks on account binding on the live streaming platform, the middle - tier application receives the user identification transmitted by the live streaming platform and binds the game account information selected by the live streaming user.

[0184] After the binding is completed, the middleware application synchronizes the game account information to the game and synchronizes the leaderboard configuration information configured by the platform to the game. The game starts to monitor the leaderboard information required by the game account and synchronizes the game leaderboard information to the middleware application. The middleware application generates a leaderboard based on the leaderboard information configured by the live platform and synchronizes the information to the live platform after generating the leaderboard. When a fan on the live platform clicks on the binding list and selects a team, the live platform sends teaming information to the middleware application. The live middleware synchronizes this information to the game application. If the invited player clicks to agree within the game, they will enter a game room with the inviting player to play in a team.

[0185] In the existing live broadcast scenarios, viewers can send bullet screen messages to interact with the anchor, ask questions, express opinions, or send gifts. The anchor can also set up interactive sessions, such as lucky draws and quizzes, to interact with the viewers. That is to say, the existing live broadcast scenarios often achieve the interaction between the anchor and the viewers. Viewers can only participate in the activities set by the anchor and cannot achieve the interaction between viewers. However, in this application, the game leaderboards of the viewer accounts authorized in the live broadcast room are synchronized to the live platform in real time. Viewers can see the real-time displayed leaderboard and directly click on the user avatar to interact for teaming, chatting, and other interactive operations, thereby achieving fast matching of accounts.

[0186] Through the above implementation manners of this application, it is possible to synchronize the game leaderboards of the viewer accounts authorized in the live broadcast room of the live platform to the live platform in real time, without the need for additional work by the operation, and the user avatar can be clicked on the leaderboard for game teaming and invitation. After the user on the leaderboard clicks to agree, a teaming invitation can directly pop up in the game without manually searching for the inviter's room number, account, and other information in the game, thereby improving the matching efficiency of account matching.

[0187] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0188] According to another aspect of the embodiments of the present invention, there is also provided a matching request sending device for implementing the above-mentioned matching request sending method. As Figure 12 shown, the device includes:

[0189] The first display unit 1202 is configured to display an interaction interface associated with an interaction account group in a first application. The interaction account group includes a plurality of interaction accounts, and the interaction interface is configured to display interaction information sent by the interaction accounts.

[0190] The second display unit 1204 is configured to display a target interaction list in the interaction interface. The target interaction list includes a plurality of account identifiers arranged in a target order. Each of the plurality of account identifiers indicates one of the interaction accounts. The target order is determined according to target parameters respectively corresponding to the plurality of interaction accounts. The target parameter is an account operation parameter of a task account bound to the interaction account in a second application, and the account operation parameter is used to indicate an operation performance in an operation task of the task account in the second application.

[0191] The sending unit 1206 is configured to send a matching request to a target interaction account indicated by the target account identifier when the target account identifier in the target interaction list is selected. The matching request is used to establish a matching relationship between a current task account bound to the current interaction account and a target task account bound to the target interaction account in the second application. When the matching relationship is established between the current task account and the target task account, the current task account and the target task account are used to jointly complete the operation task in the second application.

[0192] Optionally, the sending device of the matching request further includes: a first sending unit, configured to send the matching request to the target task account bound to the target interaction account through the current task account bound to the current interaction account in the second application.

[0193] Optionally, the sending device of the matching request further includes at least one of the following: a third display unit, configured to display a first matching prompt message when the target interaction account accepts the matching request; in response to a confirmation operation on the first matching prompt message, jump to display the application interface of the second application; a fourth display unit, configured to display a first matching prompt message in the first application when the target task account in the second application accepts the matching request; in response to a confirmation operation on the first matching prompt message, jump to display the application interface of the second application. The first matching information is used to indicate that the matching relationship has been established between the current task account and the target task account in the second application, and the application interface is used to display a task scenario in which the current task account and the target task account jointly complete the operation task.

[0194] Optionally, the sending device for the above matching request further includes: a fifth display unit, configured to display second matching prompt information in the first application interface when the current account identifier displayed in the above target interaction list is selected by a first interaction account, where the above current account identifier is used to indicate the above current interaction account, and the above second matching prompt information is used to indicate the above matching request sent by the above first interaction account; a jump unit, configured to, in response to a confirmation operation on the above second matching prompt information, jump to and display the application interface of the above second application, where the above application interface is used to display a task scenario in which the above current task account and a first task account jointly complete the above operation task, and the above first task account is an interaction account bound to the above first interaction account in the above second application.

[0195] Optionally, the above fifth display unit further includes at least one of the following: a first display module, configured to, in response to a trigger operation on a first top-listed matching control displayed in the above interaction interface, display the current account identifier of the above current interaction account in the above target interaction list in a target style, where the current account identifier displayed in the above target style indicates that the above current interaction account is in a pending matching state; a second display module, configured to, in response to a trigger operation on a second top-listed matching control displayed in the above interaction interface, display the current account identifier of the above current interaction account at the top of the above target interaction list, where the current account identifier displayed at the top indicates that the above current interaction account is in a pending matching state.

[0196] Optionally, the above sending unit 1206 includes: a display module, configured to, in response to a selection operation on the above target account identifier, display matching prompt information, where the above matching prompt information prompts that the above selection operation is used to send the above matching request to the above target interaction account; a confirmation module, configured to, in response to a confirmation operation on the above matching prompt information, determine that the above target account identifier is selected.

[0197] Optionally, the above-mentioned sending unit 1206 is configured to, when the selected target account identifiers are multiple and the selected matching mode is the first matching mode, send the above-mentioned matching requests to the target interaction accounts respectively indicated by the multiple above-mentioned target account identifiers; when the multiple above-mentioned target interaction accounts all accept the above-mentioned matching requests, determine that in the above-mentioned second application, establish the above-mentioned matching relationship between the current task account bound to the current interaction account and the target task accounts respectively bound to the multiple above-mentioned target interaction accounts, where the account set composed of the current task account and the multiple above-mentioned target task accounts is used to jointly complete the above-mentioned operation task in the above-mentioned second application; when the selected target account identifiers are multiple and the selected matching mode is the second matching mode, send the above-mentioned matching requests to the target interaction accounts respectively indicated by the multiple above-mentioned target account identifiers; when the second interaction account among the multiple above-mentioned target interaction accounts accepts the above-mentioned matching request, cancel the above-mentioned matching request sent to the third interaction account among the above-mentioned target interaction accounts, where the third interaction account is the target interaction account other than the second interaction account among the multiple above-mentioned target interaction accounts; determine that in the above-mentioned second application, establish the above-mentioned matching relationship between the current task account bound to the current interaction account and the second task account bound to the second interaction account, where the current task account and the second task account are used to jointly complete the above-mentioned operation task in the above-mentioned second application.

[0198] Optionally, the above-mentioned second display unit 1204 includes: an obtaining module, configured to obtain the game operation parameters of the game task accounts respectively bound to the multiple above-mentioned interaction accounts in the interaction account group when the above-mentioned second application is a game application; a determining module, configured to display the above-mentioned account identifiers of the multiple above-mentioned interaction accounts in the above-mentioned target interaction list in the above-mentioned target order determined according to the above-mentioned game operation parameters.

[0199] Optionally, the above-mentioned second display unit 1204 is further configured to: when the reference operation parameters of the reference game account in the above-mentioned game task accounts are updated, obtain the updated above-mentioned reference operation parameters; adjust the display position of the reference account identifier of the reference game account in the above-mentioned target interaction list according to the updated above-mentioned reference operation parameters.

[0200] Optionally, the second display unit 1204 is configured to: when there are multiple game task accounts bound to the interactive account, obtain the group type of the interactive account group, where the multiple game task accounts respectively correspond to one game application; determine a target game application from the multiple game applications according to the group type; obtain the game operation parameters of the target game task accounts respectively bound to the multiple interactive accounts, where the target game task accounts are task accounts in the target game application.

[0201] Optionally, the second display unit 1204 is further configured to: when the first application is a live broadcast application, obtain the space type corresponding to the current live broadcast space, where the interactive account group includes the viewer interactive accounts in the current live broadcast space, and the space type is determined according to the media content pushed by the host account that creates the live broadcast space; determine the group type of the interactive account group according to the space type.

[0202] Optionally, the sending unit 1206 is configured to perform at least one of the following: in response to a first editing operation on the target interaction list, adjust the display mode of the target interaction list in the interaction interface; in response to a second editing operation on the target interaction list, update the display content in the target interaction list.

[0203] Optionally, the sending unit 1206 is configured to perform at least one of the following: in response to selecting a target sorting method from multiple sorting methods, update the display content in the target interaction list according to the target sorting method; when there are multiple game task accounts bound to the interactive account, in response to selecting a target game application from the multiple game applications, obtain the target game operation parameters associated with the target game application, where the multiple game task accounts respectively correspond to one game application; update and display the account identifiers of the multiple interactive accounts respectively according to the target order determined by the target game operation parameters.

[0204] Optionally, the sending device for the matching request further includes: a first live broadcast display unit, configured to, when the first application is a live broadcast application and the second application is a game application, in response to selecting the target account identifier in the target interaction list, display the matching request information in the form of bullet screen interaction information on the live broadcast interaction page; a second live broadcast display unit, configured to, when the target interactive account accepts the matching request indicated by the matching request information, display the matching success information in the form of the bullet screen interaction information on the live broadcast interaction page.

[0205] Optionally, in this embodiment, for the implementation manners to be implemented by the above respective unit modules, reference may be made to the above respective method embodiments, which will not be elaborated herein.

[0206] According to another aspect of the embodiments of the present invention, there is also provided an electronic device for implementing the above method for sending a matching request. The electronic device may be Figure 13 the terminal device or the server shown in the figure. This embodiment takes the electronic device as the terminal device as an example for illustration. As Figure 13 shown in the figure, the electronic device includes a memory 1302 and a processor 1304. A computer program is stored in the memory 1302, and the processor 1304 is configured to execute the steps in any one of the above method embodiments through the computer program.

[0207] Optionally, in this embodiment, the above electronic device may be at least one of multiple network devices in a computer network.

[0208] Optionally, in this embodiment, the above processor may be configured to execute the following steps through the computer program:

[0209] S1. Display an interaction interface associated with an interaction account group in a first application, where the interaction account group includes multiple interaction accounts, and the interaction interface is used to display interaction information sent by the interaction accounts;

[0210] S2. Display a target interaction list in the interaction interface, where the target interaction list includes multiple account identifiers arranged in a target order, and the multiple account identifiers respectively indicate an interaction account. The target order is determined according to target parameters respectively corresponding to the multiple interaction accounts. The target parameter is an account operation parameter of a task account bound to the interaction account in a second application, and the account operation parameter is used to indicate the operation performance in an operation task of the task account in the second application;

[0211] S3. When a target account identifier in the target interaction list is selected, send a matching request to the target interaction account indicated by the target account identifier, where the matching request is used to establish a matching relationship between a current task account bound to the current interaction account and a target task account bound to the target interaction account in the second application. When the matching relationship is established between the current task account and the target task account, the current task account and the target task account are used to jointly complete an operation task in the second application.

[0212] Optionally, those of ordinary skill in the art can understand that Figure 13The structure shown is only schematic. The electronic device or electronic equipment can also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a personal digital assistant, and terminal devices such as Mobile Internet Devices (MID), PAD, etc. Figure 13 It does not limit the structure of the above-mentioned electronic device or electronic equipment. For example, the electronic device or electronic equipment may further include more or fewer components (such as a network interface, etc.) than those shown Figure 13 in the figure, or have a different configuration from that Figure 13 shown in the figure.

[0213] Among them, the memory 1302 can be used to store software programs and modules, such as the program instructions / modules corresponding to the method and device for sending a matching request in the embodiments of the present invention. The processor 1304 executes various functional applications and data processing by running the software programs and modules stored in the memory 1302, that is, implements the above-mentioned method for sending a matching request. The memory 1302 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, a flash memory, or other non-volatile solid-state memories. In some instances, the memory 1302 may further include a memory remotely set relative to the processor 1304, and these remote memories can be connected to the terminal through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof. Among them, the memory 1302 can specifically but not limitedly be used to store various elements in the scene picture, information such as the sending information of the matching request, etc. As an example, as Figure 13 shown, the above-mentioned memory 1302 may include, but is not limited to, the first display unit 1202, the second display unit 1204, and the sending unit 1306 in the above-mentioned device for sending a matching request. In addition, it may also include, but is not limited to, other module units in the above-mentioned device for sending a matching request, which will not be elaborated in this example.

[0214] Optionally, the above-mentioned transmission device 1306 is used to receive or send data via a network. Specific examples of the above-mentioned network may include a wired network and a wireless network. In one instance, the transmission device 1306 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers through a network cable, so as to communicate with the Internet or a local area network. In one instance, the transmission device 1306 is a Radio Frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0215] In addition, the above-mentioned electronic device further includes: a display 1308 for displaying a virtual scene in the interface; and a connection bus 1310 for connecting each module component in the above-mentioned electronic device.

[0216] In other embodiments, the above-mentioned terminal device or server may be a node in a distributed system, where the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting the multiple nodes in a network communication manner. Among them, the nodes may form a peer-to-peer (Peer To Peer) network, and any form of computing device, such as an electronic device like a server or a terminal, can become a node in the blockchain system by joining the peer-to-peer network.

[0217] According to one aspect of the present application, there is provided a computer program product, which includes computer programs / instructions, and the computer programs / instructions contain program codes for executing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part, and / or installed from a removable medium. When the computer program is executed by a central processing unit, it executes various functions provided by the embodiments of the present application.

[0218] The serial numbers of the above-mentioned embodiments of the present invention are only for description and do not represent the superiority or inferiority of the embodiments.

[0219] According to one aspect of the present application, there is provided a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above-mentioned method of the sender of the matching request.

[0220] Optionally, in this embodiment, the above-mentioned computer-readable storage medium may be set to store a computer program for executing the following steps:

[0221] S1, display an interaction interface associated with an interaction account group in a first application, where the interaction account group includes multiple interaction accounts, and the interaction interface is used to display interaction information sent by the interaction accounts;

[0222] S2, display a target interaction list in the interaction interface, where the target interaction list includes multiple account identifiers arranged in a target order, and the multiple account identifiers respectively indicate an interaction account, and the target order is determined according to target parameters corresponding to the multiple interaction accounts respectively. The target parameter is an account operation parameter of a task account bound to the interaction account in a second application, and the account operation parameter is used to indicate the operation performance in the operation task of the task account in the second application;

[0223] S3. When the target account identifier in the target interaction list is selected, send a matching request to the target interaction account indicated by the target account identifier. The matching request is used to establish a matching relationship between the current task account bound to the current interaction account and the target task account bound to the target interaction account in the second application. When a matching relationship is established between the current task account and the target task account, the current task account and the target task account are used to jointly complete an operation task in the second application.

[0224] In other embodiments, the above terminal device or server can be a node in a distributed system. The distributed system can be a blockchain system, which can be a distributed system formed by connecting multiple nodes through network communication. Among them, the nodes can form a peer-to-peer (Peer To Peer) network, and any form of computing device, such as a server, a terminal, and other electronic devices, can become a node in the blockchain system by joining the peer-to-peer network.

[0225] According to one aspect of the present application, a computer program product is provided. The computer program product includes computer programs / instructions, and the computer programs / instructions contain program codes for executing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part, and / or installed from a removable medium. When the computer program is executed by the central processing unit, it executes various functions provided in the embodiments of the present application.

[0226] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0227] According to one aspect of the present application, a computer-readable storage medium is provided. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method of the sender of the above matching request.

[0228] Optionally, in this embodiment, the above computer-readable storage medium can be set to store a computer program for executing the following steps:

[0229] S1. Display a target object in the live broadcast screen of the target anchor account currently watched by the current viewer account.

[0230] S2. Display an interaction coefficient prompt control, where the interaction coefficient prompt control is used to indicate the currently accumulated live broadcast interaction coefficient of the target anchor account. The live broadcast interaction coefficient increases based on the interaction operations between the target viewer account watching the live broadcast screen and the target anchor account. The interaction operations include at least one of a gift-giving operation and a comment operation. The target viewer account includes the current viewer account.

[0231] S3. In response to the live interaction coefficient indicated by the interaction coefficient prompt control satisfying the object generation condition, display a reference object generated based on at least one object part of the target object.

[0232] Optionally, in this embodiment, those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the relevant hardware of the terminal device through a program, and this program can be stored in a computer-readable storage medium. The storage medium can include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc, etc.

[0233] If the integrated unit in the above embodiments is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in the above computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing one or more computer devices (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present invention.

[0234] In the above embodiments of the present invention, the descriptions of the various embodiments each have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0235] In the several embodiments provided in this application, it should be understood that the disclosed client can be implemented in other ways. Among them, the device embodiments described above are only illustrative. For example, the above unit division is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some interfaces. The indirect coupling or communication connection of units or modules can be in an electrical or other form.

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

[0237] In addition, in each embodiment of the present invention, each functional unit may be integrated into a processing unit, may exist physically alone for each unit, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0238] The above are only the preferred embodiments of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present invention, several improvements and modifications can be made, and these improvements and modifications should also be regarded as the protection scope of the present invention.

Claims

1. A method for sending a matching request, characterized in that: include: Displaying an interactive interface associated with the interactive account group in the first application, wherein the interactive account group includes a plurality of interactive accounts, and the interactive interface is used to display interactive information sent by the interactive accounts; Displaying a target interaction list in the interactive interface, wherein the target interaction list includes a plurality of account identifiers arranged in a target order, the plurality of account identifiers respectively indicating one of the interactive accounts, the target order being determined according to target parameters respectively corresponding to the plurality of interactive accounts, the target parameters being account operation parameters of a task account bound to the interactive account in the second application, the account operation parameters being used to indicate an operation performance of the task account in an operation task in the second application; When the target account identifier in the target interaction list is selected, a matching request is sent to the target interaction account indicated by the target account identifier, wherein the matching request is used to establish a matching relationship between a current task account bound to the current interaction account and a target task account bound to the target interaction account in the second application, and when a matching relationship is established between the current task account and the target task account, the current task account and the target task account are used to jointly complete the operation task in the second application.

2. The method according to claim 1, characterized in that When the target account identifier in the target interaction list is selected, sending a matching request to the target interaction account indicated by the target account identifier further includes: In the second application, the matching request is sent to the target task account bound to the target interactive account through the current task account bound to the current interactive account.

3. The method according to claim 2, characterized in that In the case where the target account identifier in the target interaction list is selected, after sending a matching request to the target interaction account indicated by the target account identifier, the method further includes at least one of the following: In the case where the target interactive account accepts the matching request, displaying first matching prompt information; in response to a confirmation operation on the first matching prompt information, jumping to display an application interface of the second application; When the target task account in the second application accepts the matching request, displaying first matching prompt information in the first application; In response to a confirmation operation on the first matching prompt information, jumping to display an application interface of the second application; Among them, the first matching information is used to indicate that in the second application, the current task account and the target task account have established the matching relationship, and the application interface is used to display the task scenario in which the current task account and the target task account jointly complete the operation task.

4. The method according to claim 2, characterized in that: When the interactive interface associated with the interactive account group is displayed in the first application, it also includes: When the current account identifier displayed in the target interaction list is selected by the first interaction account, second matching prompt information is displayed in the first application, wherein the current account identifier is used to indicate the current interaction account, and the second matching prompt information is used to indicate the matching request sent by the first interaction account; In response to the confirmation operation of the second matching prompt information, the application interface of the second application is jumped and displayed, wherein the application interface is used to display the task scenario in which the current task account and the first task account jointly complete the operation task, and the first task account is the interactive account bound to the first interactive account in the second application.

5. The method according to claim 4, characterized in that Before displaying the second matching prompt information in the first application interface, the method further includes at least one of the following: In response to a triggering operation on a first listed matching control displayed in the interactive interface, displaying a current account identifier of the current interactive account in the target interactive list according to a target style, wherein the current account identifier displayed according to the target style indicates that the current interactive account is in a pending matching state; In response to a triggering operation on a second listed matching control displayed in the interactive interface, the current account identifier of the current interactive account is displayed at the top in the target interactive list, wherein the current account identifier displayed at the top indicates that the current interactive account is in a pending matching state.

6. The method according to claim 1, characterized in that In the case where the target account identifier in the target interaction list is selected, sending a matching request to the target interaction account indicated by the target account identifier includes: In response to a selection operation on the target account identifier, displaying matching prompt information, wherein the matching prompt information prompts that the selection operation is used to send the matching request to the target interactive account; In response to a confirmation operation on the matching prompt information, it is determined that the target account identifier is selected.

7. The method according to claim 6, characterized in that In the case where a target account identifier in the target interaction list is selected, sending a matching request to a target interaction account indicated by the target account identifier includes: In the case where there are multiple selected target account identifiers and the selected matching mode is the first matching mode, the matching requests are respectively sent to the target interactive accounts indicated by the multiple target account identifiers; in the case where the multiple target interactive accounts all accept the matching requests, it is determined to establish, in the second application, the matching relationship between the current task account bound to the current interactive account and the target task accounts respectively bound to the multiple target interactive accounts, wherein the account set consisting of the current task account and the multiple target task accounts is used to jointly complete the operation task in the second application; When there are multiple target account identifiers selected and the selected matching mode is the second matching mode, the matching requests are respectively sent to the target interactive accounts indicated by the multiple target account identifiers; when the second interactive account among the multiple target interactive accounts accepts the matching request, the matching request sent to the third interactive account among the target interactive accounts is revoked, wherein the third interactive account is the target interactive account among the multiple target interactive accounts except the second interactive account; determine to establish the matching relationship between the current task account bound to the current interactive account and the second task account bound to the second interactive account in the second application, wherein the current task account and the second task account are used to jointly complete the operation task in the second application.

8. The method according to claim 1, characterized in that Displaying the target interaction list in the interactive interface includes: In the case where the second application is a game application, obtaining game operation parameters of game task accounts bound to each of the plurality of interactive accounts in the interactive account group; The account identifiers of the respective multiple interactive accounts are displayed in the target interaction list according to the target order determined by the game operation parameters.

9. The method according to claim 8, characterized in that When the target interaction list is displayed in the interaction interface, it also includes: When the reference operation parameters of the reference game account in the game task account are updated, obtaining the updated reference operation parameters; The display position of the reference account identifier of the reference game account is adjusted in the target interaction list according to the updated reference operation parameter.

10. The method according to claim 8, characterized in that In the case where the second application is a game application, obtaining the game operation parameters of the game task accounts bound to each of the plurality of interactive accounts in the interactive account group includes: In the case where there are multiple game task accounts bound to the interactive account, obtaining a group type of the interactive account group, wherein the multiple game task accounts correspond to one game application respectively; Determining a target game application from the plurality of game applications according to the group type; The game operation parameters of the target game task account bound to each of the plurality of interactive accounts are obtained, wherein the target game task account is a task account in the target game application.

11. The method according to claim 10, characterized in that Before determining the target game application from the plurality of game applications according to the group type, the method further includes: In the case where the first application is a live broadcast application, obtaining a space type corresponding to the current live broadcast space, wherein the interactive account group includes audience interactive accounts in the current live broadcast space, and the space type is determined according to the media content pushed by the anchor account that created the live broadcast space; The group type of the interactive account group is determined according to the space type.

12. The method according to claim 8, characterized in that Displaying the target interaction list in the interactive interface includes at least one of the following: In response to a first editing operation on the target interaction list, adjusting a display mode of the target interaction list in the interaction interface; In response to a second editing operation on the target interactive list, the displayed content in the target interactive list is updated.

13. The method according to claim 12, characterized in that In response to the second editing operation on the target interactive list, updating the displayed content in the target interactive list includes at least one of the following: In response to selecting a target sorting method from a plurality of sorting methods, updating the displayed content in the target interactive list according to the target sorting method; In the case that there are multiple game task accounts bound to the interactive account, in response to selecting a target game application from the multiple game applications, a target game operation parameter associated with the target game application is obtained, wherein the multiple game task accounts correspond to one game application respectively; and the account identification of each of the multiple interactive accounts is updated and displayed according to the target order determined by the target game operation parameter.

14. The method according to claim 1, characterized in that After the target interaction list is displayed in the interaction interface, the method further includes: When the first application is a live broadcast application and the second application is a game application, in response to selecting the target account identifier in the target interaction list, displaying the matching request information in the form of bullet screen interaction information in the live broadcast interaction page; When the target interactive account accepts the matching request indicated by the matching request information, matching success information is displayed in the live interactive page in the form of the barrage interactive information.

15. A device for sending a matching request, characterized in that: include: A first display unit, configured to display an interactive interface associated with an interactive account group in a first application, wherein the interactive account group includes a plurality of interactive accounts, and the interactive interface is configured to display interactive information sent by the interactive accounts; A second display unit is used to display a target interaction list in the interactive interface, wherein the target interaction list includes multiple account identifiers arranged in a target order, each of the multiple account identifiers indicates one of the interactive accounts, and the target order is determined according to target parameters corresponding to the multiple interactive accounts, respectively, and the target parameters are account operation parameters of the task account bound to the interactive account in the second application, and the account operation parameters are used to indicate the operation performance of the task account in the operation task in the second application; A sending unit is used to send a matching request to a target interactive account indicated by the target account identifier when a target account identifier in the target interactive list is selected, wherein the matching request is used to establish a matching relationship between a current task account bound to a current interactive account and a target task account bound to the target interactive account in the second application, and when a matching relationship is established between the current task account and the target task account, the current task account and the target task account are used to jointly complete the operation task in the second application.

16. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program executes the method described in any one of claims 1 to 14 when executed.

17. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the method according to any one of claims 1 to 14 are implemented.

18. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 14 through the computer program.

Images