Bullet screen battle method, storage medium and electronic equipment

Abstract

The invention discloses a bullet screen battle method and device, a storage medium and electronic equipment. The method comprises the steps that under the condition that a target account participates in a bullet screen battle, a first identifier is distributed to the target user account, and the first identifier is used for indicating the session information of the bullet screen battle; under the condition that the target account selects to support the target battle camp in the bullet screen battle process, a second identifier is distributed to the target user, and the second identifier is used for indicating the battle camp supported by the target user in the bullet screen battle process; and according to the first identifier and the second identifier, obtaining an accumulated number corresponding to bullet screens of a target support type sent by the target account in a bullet screen battle process, the bullet screens of the target support type being bullet screens supporting the target battle camp, and the accumulated number being used for representing a support degree of the target account to the target battle camp. The technical problem that bullet screen battle effectiveness is low is solved.

Description

Technical Field

[0001] The present application relates to the field of computers, and more specifically, to a bullet screen battle method, device, storage medium, and electronic device. Background Art

[0002] In the battle (PK) scenario, although users can choose a camp to support, the barrage function is limited to sending ordinary messages and lacks interactive special effects between camps. This is mainly because the diversity of barrage content makes it difficult for the system to accurately identify the camp supported by the user, thus affecting the effectiveness of the barrage in the battle. Therefore, there is a problem of low effectiveness of barrage battles.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a barrage battle method, device, storage medium and electronic device to at least solve the technical problem of low effectiveness of barrage battle.

[0005] According to one aspect of an embodiment of the present application, a barrage battle method is provided, including: when a target account participates in a barrage battle, a first identifier is assigned to a target user account, wherein the first identifier is used to indicate the match information of the barrage battle; when the target account chooses to support a target battle camp during the barrage battle, a second identifier is assigned to the target user, wherein the second identifier is used to indicate the battle camp supported by the target user during the barrage battle; according to the first identifier and the second identifier, a cumulative number of barrages of a target supported type issued by the target account during the barrage battle is obtained, wherein the barrage of the target supported type is a barrage indicating support for the target battle camp, and the cumulative number is used to indicate the degree of support of the target account for the target battle camp.

[0006] According to another aspect of an embodiment of the present application, a barrage battle device is also provided, including: a first allocation unit, for allocating a first identifier to a target user account when the target account participates in a barrage battle, wherein the first identifier is used to indicate the match information of the barrage battle; a second allocation unit, for allocating a second identifier to the target user when the target account chooses to support a target battle camp during the barrage battle, wherein the second identifier is used to indicate the battle camp supported by the target user during the barrage battle; a first acquisition unit, for acquiring, according to the first identifier and the second identifier, a cumulative number of barrages of a target supported type issued by the target account during the barrage battle, wherein the barrage of the target supported type is a barrage indicating support for the target battle camp, and the cumulative number is used to indicate the degree of support of the target account for the target battle camp.

[0007] As an optional solution, the above-mentioned first acquisition unit includes: a statistical module, which is used to use the above-mentioned first identifier and the above-mentioned second identifier as statistical conditions, and count the barrages of the above-mentioned target supported type issued by the above-mentioned target account in the above-mentioned barrage battle process in the barrage database to obtain the above-mentioned cumulative number.

[0008] As an optional solution, the above-mentioned statistical module includes: an indexing sub-module, which is used to use the above-mentioned first identifier and the above-mentioned second identifier as index conditions to index multiple barrages of the above-mentioned target supported type issued by the above-mentioned target account during the above-mentioned barrage battle in the above-mentioned barrage database; a removal sub-module, which is used to remove the barrages that meet the abnormal barrage conditions from the above-mentioned multiple barrages to obtain the removed barrages; a statistical sub-module, which is used to count the number of barrages corresponding to the above-mentioned removed barrages to obtain the above-mentioned cumulative number.

[0009] As an optional solution, the above-mentioned device also includes: a second acquisition unit, which is used to obtain a third identifier associated with the above-mentioned first identifier after the above-mentioned first identifier is assigned to the target user account, when the above-mentioned target account sends a barrage of the above-mentioned target supported type during the above-mentioned barrage battle, wherein the above-mentioned third identifier is used to indicate the barrage material required in the above-mentioned barrage battle process; a third acquisition unit, which is used to obtain the barrage material of the above-mentioned target supported type according to the above-mentioned third identifier after the above-mentioned first identifier is assigned to the target user account.

[0010] As an optional solution, the above-mentioned device also includes: a first display unit, which is used to display a special effect of a collision between at least one barrage of the above-mentioned target supported type and at least one barrage of other supported types after obtaining the barrage material of the above-mentioned target supported type according to the above-mentioned third identifier, wherein the barrage of other supported types refers to the barrage of other camps outside the above-mentioned target battle camp that supports the special effect, and the special effect material of the special effect of the collision includes the barrage material of the above-mentioned target supported type.

[0011] As an optional solution, the above-mentioned device also includes: a fourth acquisition unit, which is used to obtain a fourth identifier associated with the above-mentioned second identifier after the above-mentioned target user is assigned the second identifier, when the above-mentioned target account sends a barrage of the above-mentioned target supported type during the above-mentioned barrage battle process, wherein the above-mentioned fourth identifier is used to indicate the camp materials required in the above-mentioned barrage battle process; a fifth acquisition unit, which is used to obtain the camp materials of the above-mentioned target battle camp according to the above-mentioned fourth identifier after the above-mentioned target user is assigned the second identifier.

[0012] As an optional solution, the above-mentioned device also includes: a second display unit, which is used to display a special effect of a battle between at least one virtual element belonging to the above-mentioned target battle camp and at least one virtual element belonging to its battle camp after obtaining the camp material of the above-mentioned target battle camp according to the above-mentioned fourth identifier, wherein the above-mentioned battle camp is a camp other than the above-mentioned target battle camp, and the special effect material of the special effect of the above-mentioned battle includes the camp material of the above-mentioned target battle camp.

[0013] As an optional scheme, the above-mentioned device also includes at least one of the following: a third display unit, used to display the remaining time of the above-mentioned barrage battle in the process of obtaining the cumulative number of barrages of the target supported type issued by the above-mentioned target account during the above-mentioned barrage battle according to the above-mentioned first identifier and the above-mentioned second identifier, wherein the above-mentioned barrage battle is set to end when the above-mentioned remaining time is reset to zero; a fourth display unit, used to display the battle progress of the above-mentioned barrage battle in the process of obtaining the cumulative number of barrages of the target supported type issued by the above-mentioned target account during the above-mentioned barrage battle according to the above-mentioned first identifier and the above-mentioned second identifier, wherein the above-mentioned battle progress is used to indicate the relationship between the various battle camps participating in the above-mentioned barrage battle. Win-lose relationship; a fifth display unit, for displaying the number of barrages corresponding to any support type issued during the barrage battle process, in the process of obtaining the cumulative number of barrages of the target support type issued by the target account during the barrage battle process according to the first identifier and the second identifier, wherein the any support type includes the target support type; a sixth display unit, for displaying the number of accounts that choose any battle camp during the barrage battle process, in the process of obtaining the cumulative number of barrages of the target support type issued by the target account during the barrage battle process according to the first identifier and the second identifier, wherein the any battle camp includes the target battle camp.

[0014] According to another aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the above bullet screen battle method.

[0015] According to another aspect of an embodiment of the present application, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the barrage battle method through the computer program.

[0016] In an embodiment of the present application, when the target account participates in a barrage battle, a first identifier is assigned to the target user account, wherein the first identifier is used to indicate the match information of the barrage battle; when the target account chooses to support the target battle camp during the barrage battle, a second identifier is assigned to the target user, wherein the second identifier is used to indicate the battle camp supported by the target user during the barrage battle; based on the first identifier and the second identifier, the cumulative number of barrages of the target supported type issued by the target account during the barrage battle is obtained, wherein the barrage of the target supported type is a barrage indicating support for the target battle camp, and the cumulative number is used to indicate the degree of support of the target account for the target battle camp.

[0017] First, this embodiment assigns a first identifier to the target user account, which carries the information of the barrage battle. In this way, the system can clearly track and classify the barrage data in different sessions, providing a basis for subsequent data analysis and processing. This step ensures the organization and traceability of the barrage information and improves the efficiency of data management.

[0018] Secondly, when the target account chooses to support a certain camp in the barrage battle, this embodiment assigns a second identifier to it. This identifier clearly indicates the battle camp supported by the user in the barrage battle. Through this measure, the camp identification problem caused by the diversity of barrage content is solved. The system can now accurately identify the camp supported by the user through the barrage, which lays the foundation for the subsequent barrage classification, statistics and interactive effects.

[0019] Finally, by combining the first identifier and the second identifier, this embodiment can accurately obtain the number of bullet screens that support a specific camp issued by the target account during the bullet screen battle. This cumulative number not only reflects the user's support for the target battle camp, but also provides a data basis for quantitative analysis of user behavior for this embodiment, thereby achieving the purpose of improving the accuracy of identifying the camp supported by the bullet screen, thereby achieving the technical effect of improving the effectiveness of the bullet screen battle, and thus solving the technical problem of low effectiveness of the bullet screen battle. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1 is a schematic diagram of an application environment of an optional barrage battle method according to an embodiment of the present application;

[0022] Figure 2is a schematic diagram of a process of an optional barrage battle method according to an embodiment of the present application;

[0023] Figure 3 is a schematic diagram of an optional barrage battle method according to an embodiment of the present application;

[0024] Figure 4 is a schematic diagram of another optional barrage battle method according to an embodiment of the present application;

[0025] Figure 5 is a schematic diagram of another optional barrage battle method according to an embodiment of the present application;

[0026] Figure 6 is a schematic diagram of an optional barrage battle device according to an embodiment of the present application;

[0027] Figure 7 It is a schematic diagram of the structure of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0029] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] According to one aspect of the embodiments of the present application, a bullet screen battle method is provided. Optionally, as an optional implementation, the bullet screen battle method can be but is not limited to being applied to: Figure 1In the environment shown, the environment may include, but is not limited to, a user device 102 and a server 112 . The user device 102 may include, but is not limited to, a display 104 , a processor 106 , and a memory 108 . The server 112 includes a database 114 and a processing engine 116 .

[0031] The specific process can be as follows:

[0032] Step S102, the user device 102 obtains relevant requests triggered when the target account participates in a barrage battle, such as a barrage battle participation request, a barrage battle barrage sending request, etc.;

[0033] Step S104, sending the relevant request to the server 112 via the network 110;

[0034] Steps S106-S110, the server 112 assigns a first identifier to the target user account and a second identifier to the target user through the processing engine 116, and further obtains the cumulative number of bullet comments of the target supported type issued by the target account during the bullet comment battle process according to the first identifier and the second identifier;

[0035] Step S112 , the accumulated number is sent to the user device 102 via the network 110 , and the user device 102 displays the accumulated number on the display 104 via the processor 106 , and stores the accumulated number in the memory 108 .

[0036] remove Figure 1 In addition to the examples shown, the terminal device can be a terminal device configured with a target client, which can include but is not limited to at least one of the following: a mobile phone (such as an Android phone, an iOS phone, etc.), a laptop, a tablet computer, a PDA, a MID (Mobile Internet Devices), a PAD, a desktop computer, a smart TV, etc. The target client can be a video client, an instant messaging client, a browser client, an education client, etc. The network can include but is not limited to: a wired network, a wireless network, wherein the wired network includes: a local area network, a metropolitan area network and a wide area network, and the wireless network includes: Bluetooth, WIFI and other networks that realize wireless communication. The 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 no limitation is made to this in this embodiment.

[0037] Optionally, as an optional implementation, as Figure 2 As shown, the bullet screen battle method can be executed by an electronic device, and the electronic device can be, for example, Figure 1 The user device or server shown in the figure comprises:

[0038] S202, when the target account participates in a barrage battle, assigning a first identifier to the target user account, wherein the first identifier is used to indicate the session information of the barrage battle;

[0039] S204, when the target account chooses to support the target battle camp during the barrage battle, assigning a second identifier to the target user, wherein the second identifier is used to indicate the battle camp supported by the target user during the barrage battle;

[0040] S206, based on the first identifier and the second identifier, obtain the cumulative number of barrages of the target supported type issued by the target account during the barrage battle process, wherein the barrage of the target supported type is a barrage indicating support for the target battle camp, and the cumulative number is used to indicate the degree of support of the target account for the target battle camp.

[0041] In an optional embodiment, the above-mentioned barrage battle method can be but is not limited to being applied in multiple scenarios, such as a live broadcast scenario with a barrage function, or a video playback scenario with a barrage function, etc.

[0042] Specifically, in a live broadcast of a popular game, two game teams are fighting. The audience can cheer for the team they support through barrages, and fight with fans of other teams. When the audience enters the live broadcast room, the system assigns a first identifier (match information) and a second identifier (supported team). The audience sends barrages to support their own team, and the system automatically recognizes and classifies these barrages into the corresponding team. In a specific area of ​​the live broadcast interface, the number of barrages supporting the two teams is displayed in real time. A "barrage battle progress bar" or "support scoreboard" can be designed to dynamically update the progress or score based on the number of barrages on both sides. Set a time interval (such as every minute), determine the result of the battle based on the number of barrages within this time, and announce the winning team on the live broadcast interface. Fans of the winning team can receive some virtual rewards, such as medals and points in the live broadcast platform. After the live broadcast ends, the total score of the barrage battle of the entire live broadcast can be displayed to enhance the sense of competition and participation among fans.

[0043] Another example is that in the video playback page of a popular anime, the fan groups of the two main characters engage in a barrage battle. Selecting a camp and assigning an identifier: The user selects the character camp they support and obtains the corresponding second identifier. The user sends barrages to support their own camp, and the system classifies and counts them according to the first identifier and the second identifier. The video playback page sets up a "barrage battle scoreboard" to display the number of barrages and support for the two camps in real time. After each episode of the anime is played, the winning camp of the barrage battle of that episode is announced based on the number of barrages. Fans of the winning camp can obtain specific identifiers or medals, which will be displayed on their personal homepage or comment area. Based on the results of the barrage battle, the anime officials can provide special benefits to fans of the winning camp, such as limited edition peripheral products, character autographs, etc.

[0044] In an optional embodiment, the first identifier: This is a specific mark, which is mainly used to indicate the session information of the bullet screen battle that the user participated in. In other words, it helps the system identify and track in which specific bullet screen battle session the user was active.

[0045] In an optional embodiment, the second mark: This mark is used to clarify the battle camp that the user chooses to support during the bullet screen battle. For example, in a battle between two teams, the user can choose to support team A or team B, and the second mark will reflect the user's choice.

[0046] To further illustrate, let's assume that there is a live broadcast of an e-sports match, with the two teams being the red team and the blue team. When Xiao Ming enters this live broadcast room and participates in the bullet screen battle, the system will assign him a first identifier, indicating that he is watching and participating in the bullet screen battle of this specific e-sports match live broadcast. If Xiao Ming chooses to support the red team, the system will assign him a second identifier, indicating that he supports the red team.

[0047] Through these two identifiers, the system can accurately track and count the user's behavior in the barrage battle, especially the barrage they posted for the camp they support. The system can accurately know in which barrage battle each user was active and which camp they supported. These identifiers provide rich dimensions for data analysis, helping to reveal key information such as user preferences and behavior patterns. Users can express their support more clearly and interact with other users in a more targeted manner. Based on this data, content providers and advertisers can develop more precise marketing strategies to increase user engagement and conversion rates.

[0048] In addition to the basic identification allocation function, the system can also perform more advanced data analysis and user behavior tracking based on these two identifications. For example, the system can analyze the changes in the number of supporters of each camp within a certain period of time, or the duration and intensity of a user's support for a specific camp. These data are of great value to content providers, advertisers, and platform operators, and can help them better understand user preferences and behavior patterns.

[0049] It should be noted that this embodiment describes a mechanism of user identification and barrage counting in a barrage battle system. Through the first identification and the second identification, it is possible to track not only which barrage battle the user participated in, but also which camp they support, and measure the user's support level by counting the number of barrages.

[0050] To further illustrate, optionally Figure 3As shown, suppose there is a barrage battle event, which is divided into two camps: Camp A and Camp B. Users can choose to join one of the camps and support their own camp by sending barrages in the video being played. The system measures the user's support for the camp based on the number of barrages sent by the user to support the camp (such as the current number of barrages for Camp A is 81, and the current number of barrages for Camp B is 47). When a user (target account) participates in this barrage battle, the system first assigns a first identifier to the user. This identifier may be a combination of "match ID + user ID", such as "20230425_Match01_UserID123", which is used to uniquely identify the barrage battle in which the user participates.

[0051] Next, the user chooses to support Camp A before the barrage battle begins. The system then assigns a second identifier to the user, such as "RedTeam_UserID123", which indicates that the user supports Camp A in the barrage battle. As the barrage battle progresses, users begin to send barrages in support of Camp A, such as "Come on!", "We can always support you", etc. Based on the user's first and second identifiers, the system identifies that these barrages are from UserID123 who supports Camp A, and are sent in the specific match "20230425_Match01". The system begins to accumulate the number of barrages supporting Camp A. For example, if the user sends a total of 10 barrages supporting Camp A, then the cumulative number is 10.

[0052] In addition, as the barrage battle progresses, the barrage associated with camp A and the barrage associated with camp B can collide with each other. At the same time, the battle situation between the two camps will be reflected according to the collision effect. For example, if camp A is currently ahead of camp B, the collision effect will reflect that camp A is ahead of camp B, and the position of the collision effect is closer to the edge of the barrage area where camp B is located. Through such a mechanism, the barrage battle system can not only enhance the interaction and competitiveness between users, but also quantify the degree of user support for the camp through specific numbers, thereby providing users with a more intuitive and fulfilling participation experience.

[0053] Through the embodiments provided by the present application, when the target account participates in a barrage battle, a first identifier is assigned to the target user account, wherein the first identifier is used to indicate the match information of the barrage battle; when the target account chooses to support the target battle camp during the barrage battle, a second identifier is assigned to the target user, wherein the second identifier is used to indicate the battle camp supported by the target user during the barrage battle; based on the first identifier and the second identifier, the cumulative number of barrages of the target supported type issued by the target account during the barrage battle is obtained, wherein the barrage of the target supported type is a barrage indicating support for the target battle camp, and the cumulative number is used to indicate the degree of support of the target account for the target battle camp.

[0054] First, this embodiment assigns a first identifier to the target user account, which carries the information of the barrage battle. In this way, the system can clearly track and classify the barrage data in different sessions, providing a basis for subsequent data analysis and processing. This step ensures the organization and traceability of the barrage information and improves the efficiency of data management.

[0055] Secondly, when the target account chooses to support a certain camp in the barrage battle, this embodiment assigns a second identifier to it. This identifier clearly indicates the battle camp supported by the user in the barrage battle. Through this measure, the camp identification problem caused by the diversity of barrage content is solved. The system can now accurately identify the camp supported by the user through the barrage, which lays the foundation for the subsequent barrage classification, statistics and interactive effects.

[0056] Finally, by combining the first identifier and the second identifier, this embodiment can accurately obtain the number of bullet comments that support a specific camp issued by the target account during the bullet comment battle. This cumulative number not only reflects the user's support for the target battle camp, but also provides a data basis for quantitative analysis of user behavior for this embodiment, thereby achieving the purpose of improving the accuracy of identifying the bullet comment support camp, thereby achieving the technical effect of improving the effectiveness of the bullet comment battle.

[0057] As an optional solution, according to the first identifier and the second identifier, obtaining the cumulative number of barrages of the target supported type issued by the target account during the barrage battle process includes:

[0058] The first identifier and the second identifier are used as statistical conditions to count the target supported type of barrages sent by the target account in the barrage database during the barrage battle to obtain a cumulative number.

[0059] In an optional embodiment, in addition to simple quantitative statistics, the system can further analyze the content, sending time, frequency, etc. of these bullet comments to more comprehensively understand the user's participation and support attitude. For example, by analyzing the content of the bullet comments, you can understand the user's common expression methods and emotional tendencies; by sending time and frequency, you can judge the user's activeness and continuity in participating in the bullet comment battle. These data are of great significance for improving user participation, optimizing the bullet comment battle mechanism, and formulating more accurate marketing strategies.

[0060] It should be noted that in order to quantify the user's support for a specific camp in a barrage battle, the system will use the user's first identifier (indicating the match information of the barrage battle) and the second identifier (indicating the battle camp supported by the user) as screening conditions to count and analyze the number of barrages sent by the user in the barrage database that support the camp selected by the user. This number, namely the "cumulative number", is an intuitive reflection of the user's support for a certain camp.

[0061] To further illustrate, let's take a bullet screen battle in a game live broadcast as an example. Suppose user Xiao Zhang chooses to support "Team A" in this live broadcast and actively participates in the bullet screen interaction. The system will retrieve and count all the bullet screens supporting "Team A" sent by Xiao Zhang during the live broadcast based on his first identifier (the bullet screen battle in this game live broadcast) and second identifier (supporting Team A). The final cumulative number represents the degree of support Xiao Zhang has for "Team A" in this bullet screen battle.

[0062] By combining the first identifier and the second identifier to count the number of barrages of the target supported type issued by the target account during the barrage battle, the system can achieve the following effects:

[0063] Accurately quantify support: The cumulative number directly reflects the degree of user support for a specific camp, providing an objective measurement standard for platforms and content providers.

[0064] Enrich data analysis dimensions: In addition to quantitative statistics, the detailed content of the barrage and other related indicators can be further analyzed to provide more comprehensive data support for platform operations and user behavior research.

[0065] Optimize user interaction experience: By understanding users' support and interaction habits, the platform can adjust the barrage battle mechanism to make it more in line with user preferences and improve user engagement.

[0066] Guide marketing strategy formulation: Based on the analysis of cumulative numbers and other relevant data, advertisers and content providers can formulate more precise marketing strategies to improve user conversion rates and satisfaction.

[0067] In summary, by using the first identifier and the second identifier to count and analyze the barrage data, the system can have a deeper understanding of the user's behavior and support in the barrage battle, and provide valuable data support and decision-making basis for all parties.

[0068] As an optional solution, the first identifier and the second identifier are used as statistical conditions to count the target supported type of barrages issued by the target account in the barrage database during the barrage battle, and the cumulative number is obtained, including:

[0069] S1-1, using the first identifier and the second identifier as index conditions, indexing multiple barrages of target supported types issued by the target account during the barrage battle in the barrage database;

[0070] S1-2, removing the barrages that meet the abnormal barrage condition from the multiple barrages to obtain the removed barrages;

[0071] S1-3, counting the number of barrages corresponding to the removed barrages to obtain a cumulative number.

[0072] In an optional embodiment, the determination of abnormal bullet comments can be based on a variety of factors, such as the length of the bullet comment content, the special characters contained, the sending frequency, etc. The system can automatically identify and remove these abnormal bullet comments by setting algorithms or rules to ensure the authenticity and reliability of the statistical data. In addition, machine learning and artificial intelligence technologies can be used to continuously optimize the detection and removal process of abnormal bullet comments.

[0073] It should be noted that when using the first identifier and the second identifier as statistical conditions to count the number of barrages of the target supported type issued by the target account in the barrage battle process in the barrage database, several key steps are involved. First, using these two identifiers as index conditions, all barrages supporting the selected camp issued by the target account in a specific barrage battle are quickly located and extracted from the barrage database. Then, in order to ensure the accuracy and validity of the data, the system will check and eliminate those barrages that are judged to be abnormal. Finally, the number of barrages after the abnormalities are eliminated is counted to obtain the cumulative number of users supporting the camp.

[0074] To further illustrate, let's assume that in a bullet screen battle of an animated series, user Xiao Li chose to support the "protagonist group". The system first uses Xiao Li's first identifier (the bullet screen battle identifier of the animated series) and the second identifier (the identifier of supporting the "protagonist group") to extract all the bullet screens that he sent in support of the "protagonist group" in that session from the bullet screen database. The system then checks these bullet screens and excludes abnormal bullet screens that are repeated, garbled, or contain inappropriate content. In the end, the number of valid bullet screens that remain is the cumulative number of Xiao Li's support for the "protagonist group" in the bullet screen battle of the series.

[0075] By using the first identifier and the second identifier as index conditions and combining the abnormal barrage elimination mechanism to count the number of barrages, the system can achieve the following effects:

[0076] Improved data accuracy: By eliminating abnormal comments, the authenticity and accuracy of statistical data can be ensured, avoiding interference from false or invalid data.

[0077] Improved analysis quality: Accurate data provides a solid foundation for subsequent user behavior analysis, trend prediction, etc., and helps improve the quality and effectiveness of analysis.

[0078] Enhanced system robustness: The mechanism for handling abnormal data makes the system more robust and stable in the face of various complex situations, and able to cope with more challenges and changes.

[0079] Improved user experience: Accurate barrage statistics can more truly reflect the user's willingness and support, thereby enhancing user participation and satisfaction.

[0080] In summary, this statistical method that combines the first identification, the second identification and the abnormal barrage removal mechanism can significantly improve the accuracy and analysis quality of barrage data, and provide strong support for platform operation and user research.

[0081] As an optional solution, after allocating the first identifier to the target user account, the method further includes:

[0082] S2-1, when the target account sends a barrage of the target supported type during the barrage battle, obtaining a third identifier associated with the first identifier, wherein the third identifier is used to indicate the barrage material required during the barrage battle;

[0083] S2-2, according to the third identifier, obtain the barrage material of the target supported type.

[0084] In an optional embodiment, the barrage material may include barrage frames of different colors, shapes, and animation effects, as well as special fonts, icons, etc. These materials can not only enhance the visual effect of the barrage, but also allow users to more intuitively express their support camps and emotional tendencies. The system can provide a rich variety of barrage materials for users to choose from according to different barrage battle themes or occasions.

[0085] It should be noted that in the barrage battle system, when a user (target user account) participates in a barrage battle and selects a supported camp (target support type), the system will assign a first identifier to the user. After that, when the user sends a barrage that supports the selected camp, the system will further obtain a third identifier associated with the first identifier. This third identifier is used to indicate the barrage material required during the barrage battle, that is, which visual element the user can choose to display his barrage. Based on this third identifier, the system can obtain the barrage material corresponding to the camp selected by the user.

[0086] To further illustrate, let's assume that user Xiao Wang chooses to support the "blue team" in the barrage battle, and the system assigns him a first identifier representing the barrage battle and the selected camp. When Xiao Wang sends a barrage supporting the blue team, the system will look for a third identifier associated with this first identifier. This third identifier may point to a series of blue-themed barrage materials, such as blue bubbles, blue fonts, etc. Based on this third identifier, the system automatically selects a suitable blue barrage material for Xiao Wang to display his barrage.

[0087] By introducing a third identifier to indicate and obtain bullet comment materials, the system achieves the following effects:

[0088] Personalized expression: Users can choose unique barrage materials to express their opinions based on their preferences and the camps they support, enhancing the personalized experience.

[0089] Visual richness: The diverse barrage materials make the barrage battle interface more colorful and enhance the user's visual enjoyment.

[0090] Interactive fun: Different barrage materials can arouse users' interest and curiosity, prompting them to participate in barrage battles more actively, increasing the fun of interaction.

[0091] Sense of belonging to a camp: Using barrage materials of a specific camp can make users feel more strongly that they belong to a certain camp, thus enhancing the sense of belonging to the camp.

[0092] In summary, the mechanism of obtaining barrage materials through the third identifier not only enriches the visual effects of the barrage battle system, but also enhances the user's sense of participation and belonging, making the barrage battle more interesting and attractive.

[0093] As an optional solution, after obtaining the bullet screen material of the target supported type according to the third identifier, the method further includes:

[0094] Display a special effect of a collision between at least one target supported type of barrage and at least one other supported type of barrage, wherein the other supported types of barrage refer to barrages representing other camps outside the target opposing camp, and the special effect material of the special effect of the collision includes the target supported type of barrage material.

[0095] In an optional embodiment, in addition to simple color collision, the collision special effect design can also introduce sound effects, dynamic images, and even 3D animations to further enhance the user's sense of immersion and participation. In addition, the system can also dynamically adjust the intensity and duration of the special effect according to factors such as the speed, size, and density of the bullet screen to achieve a more natural and realistic collision effect.

[0096] It should be noted that in the barrage battle system, when a user sends a barrage that supports his selected camp (target support type) and obtains the corresponding barrage material based on the third identifier, the system will further process the display method of the barrage. Specifically, when the barrage sent by the target user (representing the camp he supports) and the barrage sent by other users representing other camps (barrages of other supported types) meet on the screen, the system will trigger a special visual effect, namely the "collision special effect". This special effect is designed to enhance the fun and visual impact of the barrage battle. At the same time, the material of the special effect will include the barrage material of the camp (target support type) selected by the user to ensure that the special effect is consistent with the user's choice.

[0097] To further illustrate, in the optional bullet screen battle, user Xiaohong chooses to support the "Red Team" and sends a bullet screen. At this time, the system obtains the red-themed bullet screen material based on Xiaohong's choice. At the same time, another user Xiaolan chooses the "Blue Team" and sends a blue bullet screen. When Xiaohong's red bullet screen and Xiaolan's blue bullet screen cross on the screen, the system triggers a collision effect, which may appear as red and blue sparks, or two colors of bullet screen frames collide and bounce off each other. This special effect not only attracts the user's attention, but also enhances the interactivity and entertainment of the bullet screen battle.

[0098] By introducing collision effects, the barrage battle system achieves the following effects:

[0099] Enhanced visual impact: Collision effects show the interaction between different camps' bullet screens in an intuitive and eye-catching way, enhancing the visual impact.

[0100] Improved interactivity and entertainment: Users can more intuitively feel the "competition" between themselves and other users' barrages on the screen, which improves interactivity and entertainment.

[0101] Personalized experience: Since the special effects materials contain elements of the camp selected by the user, each user can enjoy a personalized experience that matches their choice.

[0102] Increased system attractiveness: The unique collision effects may become a highlight of the barrage battle system, attracting more users to participate and experience it.

[0103] In summary, the introduction of collision effects not only enriches the visual effects and user experience of the barrage battle system, but also improves the interactivity and entertainment of the system, making it more attractive and competitive.

[0104] As an optional solution, after allocating the second identifier to the target user, the method further includes:

[0105] S3-1, when the target account sends a barrage of the target supported type during the barrage battle, obtaining a fourth identifier associated with the second identifier, wherein the fourth identifier is used to indicate the camp material required during the barrage battle;

[0106] S3-2, according to the fourth identifier, obtaining the camp material of the target opposing camp.

[0107] In an optional embodiment, the camp material may include various visual elements, such as the camp's logo pattern, theme color, dynamic background, etc. These materials can not only be used to display the bullet screen, but also be applied to the user's personal avatar, nickname decoration, etc., to enhance the user's camp identity in the bullet screen battle. In addition, the system can also unlock more advanced camp materials as rewards based on the user's activity and contribution, to encourage users to participate more actively in the bullet screen battle.

[0108] It should be noted that during the barrage battle, when the system assigns the target user a second identifier representing the camp he supports, the barrage sent by the user will be associated with the camp he chooses. In order to enhance the user's sense of belonging to the camp and visual experience, the system will further obtain a fourth identifier associated with the second identifier. This fourth identifier is used to indicate the camp materials required to display the characteristics of the camp to which the user belongs during the barrage battle. Based on this fourth identifier, the system can obtain the corresponding camp materials of the camp selected by the user, such as the camp's logo, color, pattern, etc., so as to visually highlight the user's camp selection.

[0109] To further illustrate, it is optional to assume that user Xiao Ming chooses to join the "Flame Camp" in the barrage battle, and the system assigns him a second identifier representing this camp. When Xiao Ming sends a barrage supporting the Flame Camp, the system looks for a fourth identifier associated with the second identifier. This fourth identifier may point to the exclusive icon, background pattern, or specific color configuration of the Flame Camp. Based on the fourth identifier, the system obtains the materials of the Flame Camp, such as a flame-shaped barrage frame, a red background, etc., to display Xiao Ming's barrage, so that his barrage visually reflects the characteristics of the Flame Camp.

[0110] By introducing the fourth mark and faction material mechanism, the bullet screen battle system achieves the following effects:

[0111] Strengthening the sense of belonging to the camp: The barrage sent by users has obvious camp characteristics, which enhances the user's sense of belonging and identification with the selected camp.

[0112] Improved visual recognition: The bullet screens of different camps are visually distinguished, which improves the recognition and aesthetics of the bullet screen battle interface.

[0113] Improved user engagement: Rich faction materials and visual effects stimulate users' interest and motivation to participate more actively in barrage battles.

[0114] Enhanced system interactivity: Users can judge each other's camp by observing the other party's camp materials, thereby increasing the opportunities for interaction and communication between users.

[0115] In summary, the introduction of the fourth logo and faction materials not only enhances the visual experience and user participation of the barrage battle system, but also strengthens the user's sense of belonging to the faction and the interactivity of the system.

[0116] As an optional solution, after obtaining the camp material of the target opposing camp according to the fourth identifier, the method further includes:

[0117] Display at least one virtual element belonging to a target battle camp, and a special effect of a battle occurring between the virtual element and at least one virtual element belonging to its battle camp, wherein the battle camp is a camp other than the target battle camp, and special effect materials of the special effect of the battle include camp materials of the target battle camp.

[0118] In an optional embodiment, the design of the battle special effects can be customized according to the characteristics of different camps and story backgrounds. For example, a camp that is incompatible with water and fire may trigger a special effect of water and fire interweaving, and a camp that is opposed to science and magic may show a visual effect of machinery and spells colliding. In addition, the intensity and duration of the special effects can also be dynamically adjusted according to the intensity of the "battle" between virtual elements, providing users with a more realistic battle experience.

[0119] It should be noted that in the barrage battle system, when the user selects a specific camp (target battle camp) and sends a barrage, the system will find the associated fourth identifier based on the user's second identifier, and obtain the camp material of the target battle camp accordingly. Next, the system will display at least one virtual element representing the camp selected by the user (target battle camp) on the screen, such as a character, a marker, or a symbolic pattern. When these virtual elements representing the target battle camp meet virtual elements representing other camps (battle camps), a special battle special effect will be triggered. The material of this special effect will be integrated into the camp material of the target battle camp to reflect the confrontation and conflict between different camps.

[0120] To further illustrate, let's assume that the user has selected the "Light Camp", whose camp materials may include sacred symbols of light and shining light effects. During the barrage battle, the virtual elements representing the "Light Camp" (such as a bright warrior or a sacred totem) and the virtual elements representing the "Dark Camp" (such as a shadow monster or a dark symbol) meet on the screen. At this time, the system will trigger battle effects, such as a battle animation of radiant light and interlaced shadows. This special effect incorporates the light symbols and light effects of the "Light Camp", making the battle more vivid and camp-specific.

[0121] Through the introduction and display of battle special effects, the barrage battle system achieves the following effects:

[0122] Enhanced immersion: Through the display of battle special effects, users can feel the fierce confrontation between their chosen camp and other camps more immersively, thus enhancing the immersion of the game.

[0123] Improve visual appeal: Rich and diverse battle effects can attract users' attention and make the barrage battle process more exciting and fascinating.

[0124] Strengthen the characteristics of the camp: The camp materials of the target opposing camp are integrated into the special effects materials, making the battle special effects an important window for displaying the characteristics of the camp, deepening the user's impression and sense of identity with the camp.

[0125] Increase the fun of the game: As a form of visual expression in the game, the battle effects increase the fun and interactivity of the barrage battle, allowing users to enjoy the game process more.

[0126] In summary, through the introduction and display of battle special effects, the barrage battle system not only improves the user's gaming experience, but also further enhances the camp characteristics and the fun of the game.

[0127] As an optional solution, in the process of obtaining, according to the first identifier and the second identifier, the cumulative number of barrages of the target supported type issued by the target account during the barrage battle, the method further includes at least one of the following:

[0128] S4-1, displaying the remaining time of the barrage battle, wherein the barrage battle is set to end when the remaining time is reset to zero;

[0129] S4-2, displaying the battle progress of the barrage battle, wherein the battle progress is used to indicate the win-loss relationship between the various battle camps participating in the barrage battle;

[0130] S4-3, displaying the number of barrages corresponding to barrages of any supporting type issued during the barrage battle, wherein any supporting type includes a target supporting type;

[0131] S4-4, displays the number of accounts that select any battle camp during the barrage battle, where any battle camp includes the target battle camp.

[0132] It should be noted that in the bullet chat battle system, when a user participates in a bullet chat battle and sends bullet chats that support the camp he or she has selected, the system will record and count the number of bullet chats sent by the user based on the user's first identifier and second identifier. In this process, the system can also provide a variety of information display functions to enhance the user's battle experience and game perception. These functions include at least one of the following:

[0133] Display the remaining time of the barrage battle: The system will display the remaining time of the barrage battle. When this time is reset to zero, the barrage battle will end.

[0134] Display the battle progress of the barrage battle: The system uses some form (such as progress bar, percentage, etc.) to display the progress of the current barrage battle and the win-loss relationship between the various camps participating in the battle.

[0135] Display the number of bullet comments of any supported type: The system will count and display the number of bullet comments of each supported type (including the target supported type selected by the user) sent by the user.

[0136] Display the number of accounts that have selected any battle camp: The system will count and display the number of user accounts that have selected each battle camp (including the target battle camp selected by the user).

[0137] These information display functions not only provide basic information and real-time dynamics of the battle, but also help users better understand the battle situation and make more informed decisions. For example, by checking the remaining time, users can adjust their barrage sending strategy; by looking at the battle progress, users can determine which camp is currently in an advantageous position; the display of the number of barrages and the number of accounts allows users to feel the intensity and participation of the battle.

[0138] To further illustrate, an optional remaining time display: there is a countdown clock above the barrage battle interface, which displays "Remaining time: 60 seconds", meaning that the barrage battle will end in 60 seconds.

[0139] Battle progress display: There is a progress bar on the interface, which is divided into red and blue parts, representing the "sphere of influence" of the two opposing camps respectively. The red part occupies most of the progress bar, indicating that the red camp is currently in the lead.

[0140] Number of barrages displayed: In a corner of the interface, the system displays "Red barrage: 1200, blue barrage: 850", indicating that users in the red camp sent a total of 1,200 barrages, while users in the blue camp sent 850.

[0141] Account quantity display: The system prompts "Red camp number: 500, blue camp number: 400", indicating that currently 500 users have chosen the red camp and 400 users have chosen the blue camp.

[0142] By introducing diversified display elements, the barrage battle system achieves the following effects:

[0143] Improved transparency: These information display features increase the transparency of barrage battles, allowing users to more clearly understand the current status and overall situation of the battle.

[0144] Enhanced strategy: Users can adjust their strategies based on the information provided, such as speeding up or slowing down the speed of sending barrages, or changing the support method.

[0145] Improve participation: Through real-time feedback of the number of barrages and accounts, users can feel the importance of their participation and its impact on the overall battle situation, thereby improving participation and investment.

[0146] Increase tension and fun: The display of remaining time and changes in battle progress can increase the tension and fun of the battle, making users more engaged and enjoying the battle process.

[0147] As an optional solution, for ease of understanding, the above-mentioned barrage battle method is applied to a competitive live broadcast scenario. When two parties PK, the current interactive methods include the popularity of the two parties. Support the camp you support by voting to select the camp. The client also only displays the number of supporters on both sides to show the progress of the PK. As for the barrage, only ordinary barrage can be sent, and there is no interactive effect of the barrage of the two camps. The live broadcast effect is not intuitive enough. This embodiment provides a method for providing support for your own camp by selecting a barrage camp and sending barrage. A barrage collision effect and count of the two camps is realized. Create a tense and exciting atmosphere. Increase the fun of live broadcasts and improve user activity and user stickiness.

[0148] To further illustrate, the optional implementation process of the above method of selecting a barrage camp and providing support to one's own camp by sending barrage is as follows: Figure 4 As shown,

[0149] S402, background configuration of PK session information: First, the specific session information of the PK activity is set in the background.

[0150] S404, sending PK match information: sending the configured PK match information to the relevant system or front-end interface.

[0151] S406, background delivery of PK bullet comments: According to the information sent, the background starts to deliver PK-related bullet comments, and generates a PK panel, a PK bar, and a bullet comment counter.

[0152] S408, determine whether the user has selected a camp: After viewing the PK panel, the user can choose to join a camp. If the user chooses to join a camp ("yes"), S310 is further executed. If the user does not choose to join a camp ("no"), S308 is re-executed. For example, the system can repeatedly display the PK panel, PK bar and barrage counter to prompt the user to make a choice.

[0153] S410, sending bullet comments and effect display: if the user selects a camp, the bullet comments are sent and participate in the PK, the system displays the bullet comment confrontation effect, and displays the result after the PK is over. Also, after the bullet comments are sent, the system updates the bullet comment counter in real time.

[0154] S412, end of barrage and settlement: After the PK activity ends, the system settles and displays the final barrage count and PK results.

[0155] In an optional embodiment, the above method of selecting a bullet screen camp and providing support to one's own camp by sending bullet screens can be implemented by a bullet screen system, wherein the bullet screen system can be as follows: Figure 5As shown, it is composed of a background configuration module, a configuration delivery module, a barrage sending module, a camp barrage counting module, and a message push module, which interact with the client to jointly implement the above method of selecting a barrage camp and providing support for one's own camp by sending barrages, as follows:

[0156] Optionally, the background configuration module is used to configure the PK barrage material and PK camp information of the live broadcast room. The PK barrage configuration information acts on the live broadcast room. The configuration of each PK information generates an id, recorded as pk_id. Under this PK, the special effect material of the PK barrage will be configured, and the material will be bound to an id, which is the material id, recorded as material_id. Under each PK information, camp information will be configured. Each camp is bound to an id, recorded as camp_id. Camp information includes camp posters, camp names, camp barrage directions and other information.

[0157] Optionally, the main function of the configuration and delivery module is to deliver the PK match information of the live broadcast room. The PK match information of the live broadcast room is obtained when the user enters the live broadcast room. When the user enters the live broadcast room, the PK match information will be delivered through the http protocol of the configuration and delivery module. All PK match information under the configured position is obtained. Including PK special effects materials and related information of the camp. In this way, the user obtains all the PK match information under the live broadcast room. When the user switches the live broadcast room. All PK match information of the switched live broadcast room will be obtained.

[0158] Optionally, the main function of the barrage sending module is to send PK barrage. After the user sends the barrage, in addition to basic verification, the server verifies whether the pk_id and camp_id exist for the PK barrage. In addition to the information of ordinary barrage, the PK barrage also needs to carry pk_id to identify the session in which the PK barrage was sent. Camp_id is required to identify which camp the user has selected.

[0159] Optional, the camp barrage count is mainly used for barrage sending count. After the user sends the barrage and passes the verification, the barrage count will be counted. The main information of the barrage sending module includes barrage content, user id, live broadcast room id, session id (pk_id), and camp id (camp_id). The barrage count mainly includes the barrage number count and the barrage number count. The barrage number count is used to count the number of barrages sent by each camp in each PK. The number of barrage counts is +1 for each PK barrage sent. The barrage number count is used to count the number of barrages sent by each camp in each PK. For a PK, the user cannot switch camps after selecting a camp. After the user sends the barrage for the first time, the number of barrage counts is +1, and the count does not increase if the same person sends it multiple times.

[0160] Optionally, the main function of the message push module is to push barrage related information in real time. The main messages pushed are: PK barrage trigger message, PK barrage barrage message, camp barrage count message, and PK barrage end message. PK barrage trigger message: PK barrage start message is mainly used to trigger the PK barrage start signal (pk_id) of the specified session. After the client receives the trigger signal, the client begins to appear PK panel, PK bar and barrage counter and other rendering effects. It also carries the PK barrage duration, which is used to control the countdown during the entire PK process. The PK barrage trigger message is pushed in the form of a heartbeat, once per second, and the countdown it carries is also decremented per second. The barrage message of PK barrage is a barrage message sent by the user. In addition to the basic barrage content and user information, the message also carries PK session information (pk_id) and camp information (camp_id), which is used to distinguish the camp selected by the user. After receiving the barrage content information, the client displays the barrage content in different camp areas. Camp barrage count message is used to push the number of barrages and the number of people in each camp. After receiving the barrage count, the client displays the count in the barrage counter area. PK barrage end message mainly triggers the barrage end message. When the barrage trigger message countdown ends, the barrage end message is pushed. In addition to the trigger end, the barrage end message also carries settlement information, that is, the count. After the user PK ends, the settlement information (the number of barrages sent by each camp and the number of people in the barrage, the winning and losing information of the camp supported by the user, etc.) is displayed.

[0161] Through the embodiments provided by the present application, during the competitive live broadcast, users can select a barrage camp and send barrages to support their own camp. This achieves a barrage collision effect and counts between the two camps. This creates a tense and exciting atmosphere. This increases the fun of the live broadcast and improves user activity and stickiness.

[0162] It is understandable that in the specific implementation of this application, related data such as user information is involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.

[0163] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0164] According to another aspect of the embodiment of the present application, a barrage battle device for implementing the above barrage battle method is also provided. Figure 6 As shown, the device comprises:

[0165] The first allocation unit 602 is used to allocate a first identifier to the target user account when the target account participates in the barrage battle, wherein the first identifier is used to indicate the session information of the barrage battle;

[0166] The second allocation unit 604 is used to allocate a second identifier to the target user when the target account chooses to support the target battle camp during the barrage battle process, wherein the second identifier is used to indicate the battle camp supported by the target user during the barrage battle process;

[0167] The first acquisition unit 606 is used to obtain the cumulative number of barrages of the target support type issued by the target account during the barrage battle process according to the first identifier and the second identifier, wherein the barrage of the target support type is a barrage indicating support for the target battle camp, and the cumulative number is used to indicate the degree of support of the target account for the target battle camp.

[0168] For specific implementation, please refer to the example shown in the above-mentioned barrage battle method, which will not be repeated here in this example.

[0169] As an optional solution, the first obtaining unit 606 includes:

[0170] The statistical module is used to use the first identifier and the second identifier as statistical conditions to count the target-supported barrages issued by the target account in the barrage database during the barrage battle to obtain a cumulative number.

[0171] For specific implementation, please refer to the example shown in the above-mentioned barrage battle method, which will not be repeated here in this example.

[0172] As an optional option, the Statistics module includes:

[0173] An indexing submodule, configured to use the first identifier and the second identifier as indexing conditions to index multiple barrages of target supported types issued by the target account in the barrage battle process in the barrage database;

[0174] The elimination submodule is used to eliminate the barrages that meet the abnormal barrage conditions from multiple barrages to obtain the eliminated barrages;

[0175] The statistics submodule is used to count the number of barrages corresponding to the removed barrages and obtain the cumulative number.

[0176] For specific implementation, please refer to the example shown in the above-mentioned barrage battle method, which will not be repeated here in this example.

[0177] As an optional solution, the device also includes:

[0178] A second acquisition unit is used to, after allocating the first identifier to the target user account, acquire a third identifier associated with the first identifier when the target account sends a barrage of the target supported type during the barrage battle, wherein the third identifier is used to indicate the barrage material required during the barrage battle;

[0179] The third acquisition unit is used to acquire the barrage material of the target supported type according to the third identifier after allocating the first identifier to the target user account.

[0180] For specific implementation, please refer to the example shown in the above-mentioned barrage battle method, which will not be repeated here in this example.

[0181] As an optional solution, the device also includes:

[0182] The first display unit is used to display a special effect of a collision between at least one barrage of the target supported type and at least one barrage of other supported types after obtaining the barrage material of the target supported type according to the third identifier, wherein the barrage of other supported types refers to the barrage of other camps outside the target battle camp, and the special effect material of the special effect of the collision includes the barrage material of the target supported type.

[0183] For specific implementation, please refer to the example shown in the above-mentioned barrage battle method, which will not be repeated here in this example.

[0184] As an optional solution, the device also includes:

[0185] a fourth acquisition unit, configured to acquire, after allocating the second identifier to the target user, a fourth identifier associated with the second identifier when the target account issues a barrage of the target supported type during the barrage battle, wherein the fourth identifier is used to indicate a camp material required during the barrage battle;

[0186] The fifth acquisition unit is used to acquire the camp material of the target opposing camp according to the fourth identifier after allocating the second identifier to the target user.

[0187] For specific implementation, please refer to the example shown in the above-mentioned barrage battle method, which will not be repeated here in this example.

[0188] As an optional solution, the device also includes:

[0189] The second display unit is used to display special effects of a battle between at least one virtual element belonging to the target battle camp and at least one virtual element belonging to its battle camp after acquiring the camp material of the target battle camp according to the fourth identifier, wherein the battle camp is a camp other than the target battle camp, and the special effects material of the special effects of the battle includes the camp material of the target battle camp.

[0190] For specific implementation, please refer to the example shown in the above-mentioned barrage battle method, which will not be repeated here in this example.

[0191] As an optional solution, the device further includes at least one of the following:

[0192] A third display unit is used to display the remaining time of the barrage battle in the process of obtaining the cumulative number of barrages corresponding to the target supported type issued by the target account during the barrage battle according to the first identifier and the second identifier, wherein the barrage battle is set to end when the remaining time is reset to zero;

[0193] a fourth display unit, configured to display a battle progress of the barrage battle in the process of obtaining, according to the first identifier and the second identifier, a cumulative number of barrages of the target supported type issued by the target account during the barrage battle, wherein the battle progress is used to indicate a win-loss relationship between various battle camps participating in the barrage battle;

[0194] A fifth display unit is used to display the number of barrages corresponding to any support type issued during the barrage battle, in the process of obtaining the cumulative number of barrages corresponding to the target support type issued by the target account during the barrage battle according to the first identifier and the second identifier, wherein any support type includes the target support type;

[0195] The sixth display unit is used to display the number of accounts that choose any battle camp during the barrage battle process, while obtaining the cumulative number of barrages of the target supported type issued by the target account during the barrage battle process based on the first identifier and the second identifier, wherein any battle camp includes the target battle camp.

[0196] For specific implementation, please refer to the example shown in the above-mentioned barrage battle method, which will not be repeated here in this example.

[0197] According to another aspect of the embodiment of the present application, an electronic device for implementing the above-mentioned bullet screen battle method is also provided. The electronic device can be but is not limited to being Figure 1 The user device 102 or the server 112 shown in FIG. 1 is used as an example to illustrate the electronic device as the user device 102. Figure 7As shown, the electronic device includes a memory 702 and a processor 704. The memory 702 stores a computer program, and the processor 704 is configured to execute the steps in any of the above method embodiments through the computer program.

[0198] In an optional embodiment, the electronic device may be located in at least one network device among a plurality of network devices of a computer network.

[0199] In an optional embodiment, the processor may be configured to perform the following steps through a computer program:

[0200] S1, when the target account participates in a barrage battle, assigning a first identifier to the target user account, wherein the first identifier is used to indicate the session information of the barrage battle;

[0201] S2, when the target account chooses to support the target battle camp during the barrage battle, assigning a second identifier to the target user, wherein the second identifier is used to indicate the battle camp supported by the target user during the barrage battle;

[0202] S3, based on the first identifier and the second identifier, obtain the cumulative number of barrages of the target supported type issued by the target account during the barrage battle process, wherein the barrage of the target supported type is a barrage indicating support for the target battle camp, and the cumulative number is used to indicate the degree of support of the target account for the target battle camp.

[0203] Alternatively, a person skilled in the art may understand that: Figure 7 The structure shown is for illustration only. Figure 7 The structure of the electronic device is not limited. Figure 7 More or fewer components (such as network interfaces, etc.) as shown in, or with Figure 7 Different configurations are shown.

[0204] Among them, the memory 702 can be used to store software programs and modules, such as the program instructions / modules corresponding to the barrage battle method and device in the embodiments of the present application. The processor 704 executes various functional applications and data processing by running the software programs and modules stored in the memory 702, that is, realizing the above-mentioned barrage battle method. The memory 702 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 702 may further include a memory remotely located relative to the processor 704, and these remote memories may be connected to the electronic device via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. Among them, the memory 702 can be specifically, but not limited to, used to store information such as a first identifier, a second identifier, and a cumulative quantity. As an example, such as Figure 7 As shown, the memory 702 may include, but is not limited to, the first allocation unit 602, the second allocation unit 604, and the first acquisition unit 606 in the barrage battle device. In addition, it may also include, but is not limited to, other module units in the barrage battle device, which will not be repeated in this example.

[0205] Optionally, the transmission device 706 is used to receive or send data via a network. Specific examples of the network may include a wired network and a wireless network. In one example, the transmission device 706 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers via a network cable so as to communicate with the Internet or a local area network. In one example, the transmission device 706 is a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0206] In addition, the electronic device further includes: a display 708 for displaying information such as the first identifier, the second identifier and the accumulated quantity; and a connection bus 710 for connecting various module components in the electronic device.

[0207] In other embodiments, the user device or server may be a node in a distributed system, wherein the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting the multiple nodes through network communication. Among them, a peer-to-peer network may be formed between the nodes, and any form of computing device, such as a server, user device, or other electronic device, may become a node in the blockchain system by joining the peer-to-peer network.

[0208] According to one aspect of the present application, a computer program product is provided, the computer program product comprising a computer program / instruction, the computer program / instruction comprising a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication part, and / or installed from a removable medium. When the computer program is executed by a central processing unit, various functions provided by the embodiments of the present application are executed.

[0209] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0210] It should be noted that the computer system of the electronic device is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0211] The computer system includes a central processing unit (CPU), which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) or the program loaded from the storage part to the random access memory (RAM). In the random access memory, various programs and data required for system operation are also stored. The central processing unit, the read-only memory and the random access memory are connected to each other through a bus. The input / output interface (I / O interface) is also connected to the bus.

[0212] The following components are connected to the input / output interface: an input part including a keyboard, a mouse, etc.; an output part including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage part including a hard disk, etc.; and a communication part including a network interface card such as a local area network card, a modem, etc. The communication part performs communication processing via a network such as the Internet. A drive is also connected to the input / output interface as needed. Removable media, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., are installed on the drive as needed so that the computer program read therefrom is installed into the storage part as needed.

[0213] In particular, according to an embodiment of the present application, the process described in each method flow chart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer readable medium, and the computer program contains a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication part, and / or installed from a removable medium. When the computer program is executed by a central processing unit, various functions defined in the system of the present application are executed.

[0214] According to one aspect of the present application, a computer-readable storage medium is provided, and a processor of a 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 methods provided in the above-mentioned various optional implementations.

[0215] In an optional embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0216] S1, when the target account participates in a barrage battle, assigning a first identifier to the target user account, wherein the first identifier is used to indicate the session information of the barrage battle;

[0217] S2, when the target account chooses to support the target battle camp during the barrage battle, assigning a second identifier to the target user, wherein the second identifier is used to indicate the battle camp supported by the target user during the barrage battle;

[0218] S3, based on the first identifier and the second identifier, obtain the cumulative number of barrages of the target supported type issued by the target account during the barrage battle process, wherein the barrage of the target supported type is a barrage indicating support for the target battle camp, and the cumulative number is used to indicate the degree of support of the target account for the target battle camp.

[0219] Optionally, in the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories), or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0220] In an optional embodiment, a person of ordinary skill in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by instructing hardware related to the electronic device through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0221] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0222] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling one or more computer devices (which can be personal computers, servers or network devices, etc.) to execute all or part of the steps of the methods of each embodiment of the present application.

[0223] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0224] In the several embodiments provided in the present application, it should be understood that the disclosed user equipment can be implemented in other ways. Among them, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

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

[0226] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, 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 software functional units.

[0227] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A barrage battle method, characterized in that: include: In the case where the target account participates in a barrage battle, a first identifier is allocated to the target user account, wherein the first identifier is used to indicate the session information of the barrage battle; In the case where the target account chooses to support a target battle camp during the barrage battle, a second identifier is allocated to the target user, wherein the second identifier is used to indicate the battle camp supported by the target user during the barrage battle; According to the first identifier and the second identifier, the cumulative number of barrages of a target supported type issued by the target account during the barrage battle is obtained, wherein the barrage of the target supported type is a barrage indicating support for the target battle camp, and the cumulative number is used to indicate the degree of support of the target account for the target battle camp.

2. The method according to claim 1, characterized in that The step of obtaining, according to the first identifier and the second identifier, a cumulative number of barrages of a target supported type issued by the target account during the barrage battle, includes: The first identifier and the second identifier are used as statistical conditions to count the barrages of the target supported type issued by the target account in the barrage database during the barrage battle to obtain the cumulative number.

3. The method according to claim 2, characterized in that The using the first identifier and the second identifier as statistical conditions, counting the barrages of the target supported type issued by the target account in the barrage database during the barrage battle, and obtaining the cumulative number, comprises: Using the first identifier and the second identifier as index conditions, indexing in the barrage database a plurality of barrages of the target supported type issued by the target account during the barrage battle; Eliminating the barrages that meet the abnormal barrage condition from the multiple barrages to obtain eliminated barrages; The number of barrages corresponding to the removed barrages is counted to obtain the cumulative number.

4. The method according to claim 1, characterized in that: After allocating the first identifier to the target user account, the method further includes: When the target account issues a barrage of the target supported type during the barrage battle, obtaining a third identifier associated with the first identifier, wherein the third identifier is used to indicate the barrage material required during the barrage battle; According to the third identifier, obtain the barrage material of the target supported type.

5. The method according to claim 4, characterized in that After acquiring the bullet screen material of the target supported type according to the third identifier, the method further includes: Display a special effect of a collision between at least one barrage of the target supported type and at least one barrage of other supported types, wherein the barrage of other supported types refers to barrages representing support for other camps outside the target battle camp, and the special effect material of the special effect of the collision includes the barrage material of the target supported type.

6. The method according to claim 1, characterized in that After allocating the second identifier to the target user, the method further includes: When the target account issues a barrage of the target supported type during the barrage battle, obtaining a fourth identifier associated with the second identifier, wherein the fourth identifier is used to indicate a camp material required during the barrage battle; According to the fourth identifier, the camp material of the target opposing camp is obtained.

7. The method according to claim 6, characterized in that After acquiring the camp material of the target opposing camp according to the fourth identifier, the method further includes: Display at least one virtual element belonging to the target battle camp, and a special effect of a battle occurring between the virtual element and at least one virtual element belonging to its battle camp, wherein the battle camp is a camp other than the target battle camp, and the special effect material of the special effect of the battle includes the camp material of the target battle camp.

8. The method according to any one of claims 1 to 5, characterized in that In the process of obtaining, according to the first identifier and the second identifier, the cumulative number of barrages of the target supported type issued by the target account during the barrage battle, the method further includes at least one of the following: Display the remaining time of the barrage battle, wherein the barrage battle is set to end when the remaining time is reset to zero; Displaying the battle progress of the barrage battle, wherein the battle progress is used to indicate the win-loss relationship between various battle camps participating in the barrage battle; Display the number of barrages corresponding to barrages of any supporting type issued during the barrage battle, wherein any supporting type includes the target supporting type; The number of accounts that select any battle camp during the barrage battle is displayed, wherein any battle camp includes the target battle camp.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program executes the method according to any one of claims 1 to 8 when executed by an electronic device.

10. 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 8 through the computer program.

Images