Method, device, equipment and storage medium for processing live component information

Abstract

The present application provides a method, device, equipment and computer-readable storage medium for processing live broadcast component information; the method includes: obtaining component information of functional components in a live broadcast interface corresponding to a live broadcast; based on the component information, generating group update information of functional components in the live broadcast interface; wherein the update information indicates that there is an update of component content, and is used to update the component content in the live broadcast interface; calling a component service interface, pushing the update information to a live broadcast client corresponding to the live broadcast, so as to update the component content of the live broadcast interface in the live broadcast client based on the update information. Through the present application, the processing performance of live broadcast component information can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, equipment and computer-readable storage medium for processing live broadcast component information. Background Art

[0002] With the development of computer technology and network technology, online live broadcasting has been widely popularized. The anchor can broadcast live through the live broadcast client, and the audience can enter the live broadcast room of interest through the live broadcast client to watch the live broadcast content of the anchor. In the live broadcast interface of the existing live broadcast room, there is generally a function of presenting functional components, such as active widgets in show live broadcasts, bubbles and shopping bags in e-commerce live broadcasts, etc.

[0003] In the related art, the update of component content in the live broadcast interface is usually achieved through polling, that is, the client periodically requests the latest data from the server, which is equivalent to maintaining a heartbeat from the client to the server, resulting in a waste of bandwidth and server resources, and making the processing performance of the live broadcast component information low. Summary of the invention

[0004] The embodiments of the present application provide a method, device and computer-readable storage medium for processing live broadcast component information, which can improve the processing performance of live broadcast component information.

[0005] The technical solution of the embodiment of the present application is implemented as follows:

[0006] The present application embodiment provides a method for processing live broadcast component information, including:

[0007] Get the component information of the functional components in the live broadcast interface corresponding to the live broadcast;

[0008] Based on the component information, generating update information of the functional components in the live broadcast interface;

[0009] The update information indicates that there is an update of the component content, and is used to update the component content in the live broadcast interface;

[0010] The component service interface is called to push the update information to the live broadcast client corresponding to the live broadcast, so as to update the component content of the live broadcast interface in the live broadcast client based on the update information.

[0011] The embodiment of the present application provides a device for processing live broadcast component information, including:

[0012] An acquisition module, used to acquire component information of functional components in a live broadcast interface corresponding to the live broadcast;

[0013] A generating module, used to generate update information of functional components in the live broadcast interface based on the component information;

[0014] The update information indicates that there is an update of the component content, and is used to update the component content in the live broadcast interface;

[0015] The push module is used to call the component service interface to push the update information to the live broadcast client corresponding to the live broadcast.

[0016] Based on the update information, the component content of the live broadcast interface in the live broadcast client is updated.

[0017] In the above scheme, the acquisition module is also used to receive component information of functional components in the live broadcast interface corresponding to the set live broadcast in accordance with at least one dimension, and the dimension includes at least one of the following: global, platform, live broadcast client, and live broadcast room.

[0018] In the above scheme, the device also includes:

[0019] A storage module, for, when there is component information of at least two functional components, using each of the dimensions as a key and using the corresponding component information as a value;

[0020] Obtaining a weight of each of the functional components, wherein the weight is used to indicate a storage order of component information of the corresponding functional component;

[0021] The component information of the at least two functional components is stored in a key-value pair storage manner based on a storage order indicated by the weight of each functional component.

[0022] In the above solution, the acquisition module is also used to obtain the expiration time of the component information;

[0023] storing the component information and the expiration time of the component information;

[0024] When it is determined based on the current time and the expiration time that the component information is in an expired state, the component information is deleted.

[0025] In the above scheme, the acquisition module is also used to receive component information of functional components in the live broadcast interface corresponding to the live broadcast set by the third-party platform based on the platform as a service interface.

[0026] In the above scheme, the acquisition module is further used to compare the acquired component information with the component information corresponding to the current component content in the live broadcast interface, and obtain the partial information of the acquired component information that has changed relative to the component information corresponding to the current component content;

[0027] The changed part of information is taken as update information.

[0028] In the above solution, the push module is also used to push the component version number corresponding to the update information to the live broadcast client corresponding to the live broadcast;

[0029] The component version number is used by the live broadcast client to update the component content in the live broadcast interface when the live broadcast client determines that the component version number is inconsistent with the current component version number.

[0030] In the above solution, the push module is further used to compress the update information to obtain a compressed file corresponding to the update information;

[0031] Push a compressed file corresponding to the update information to a live broadcast client corresponding to the live broadcast.

[0032] In the above solution, the push module is further used to merge the at least two pieces of update information to obtain merged update information when there are at least two pieces of update information;

[0033] Push the merged update information to the live broadcast client corresponding to the live broadcast.

[0034] In the above solution, the push module is further used to obtain the number of failed pushes of the update information when receiving a prompt message indicating that the push failed;

[0035] Determining a backoff time according to the number of failed pushes of the update information;

[0036] When the backoff time arrives, the update information is pushed again to the live broadcast client corresponding to the live broadcast.

[0037] In the above solution, the push module is also used to push the update time corresponding to the update information to the live broadcast client corresponding to the live broadcast;

[0038] The update time is used by the live broadcast client to update the component content in the live broadcast interface when the update time arrives.

[0039] In the above solution, the push module is also used to push the preload duration corresponding to the update information to the live broadcast client corresponding to the live broadcast;

[0040] The preloading duration is used for the live broadcast client to obtain component content corresponding to the update information within the preloading duration.

[0041] An embodiment of the present application provides a computer device, including:

[0042] A memory for storing executable instructions;

[0043] The processor is used to implement the method for processing live broadcast component information provided in an embodiment of the present application when executing the executable instructions stored in the memory.

[0044] An embodiment of the present application provides a computer-readable storage medium storing executable instructions for causing a processor to execute and implement the method for processing live broadcast component information provided by the embodiment of the present application.

[0045] The embodiments of the present application have the following beneficial effects:

[0046] The present application generates update information of the component in the live broadcast interface based on the component information; wherein the update information indicates that there is an update to the component content and is used to update the component content in the live broadcast interface; calls the component service interface to push the update information to the live broadcast client corresponding to the live broadcast, so as to update the component content of the live broadcast interface in the live broadcast client based on the update information; in this way, since the present application is that the server actively pushes the update information to the live broadcast client without the need for polling by the live broadcast client, the number of heartbeats between the client and the server can be reduced, avoiding the waste of bandwidth and server resources, thereby improving the processing performance of the live broadcast component information. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 It is a schematic diagram of the architecture of a system 100 for processing live broadcast component information provided in an embodiment of the present application;

[0048] Figure 2 is a schematic diagram of the structure of the server 200 provided in an embodiment of the present application;

[0049] Figure 3 It is a flowchart of a method for processing live broadcast component information provided by an embodiment of the present application;

[0050] Figure 4 This is a schematic diagram of the live broadcast interface of entertainment live broadcast in an embodiment of the present application;

[0051] Figure 5 This is a schematic diagram of the live broadcast interface of the e-commerce live broadcast provided in the embodiment of the present application;

[0052] Figure 6 It is a schematic diagram of component update information push provided in an embodiment of the present application;

[0053] Figure 7 It is a flowchart of a method for processing live broadcast component information provided by an embodiment of the present application;

[0054] Figure 8 It is a schematic diagram of the software system architecture for implementing the method for processing live broadcast component information provided in the embodiment of the present application;

[0055] Fig. 9 It is a schematic diagram of the processing flow of the management background provided in the embodiment of the present application;

[0056] Fig.10 It is a schematic diagram of the composition structure of the device for processing live broadcast component information provided in an embodiment of the present application. DETAILED DESCRIPTION

[0057] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of this application.

[0058] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0059] In the following description, the terms "first\second\third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0060] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0061] Before further describing the embodiments of the present application in detail, the nouns and terms involved in the embodiments of the present application are explained. The nouns and terms involved in the embodiments of the present application are subject to the following interpretations.

[0062] 1) Live broadcast, which is a way of publishing information on the Internet with a two-way flow process, by producing and publishing information simultaneously with the occurrence and development of events on site.

[0063] 2) Functional components, also known as widgets, are used to present live broadcast information during the live broadcast, including active widgets, shopping bags, bubbles, etc.; the component content of functional components will change dynamically as the live broadcast progresses. For example, in e-commerce live broadcasts, as the live broadcast progresses, the content of the bubbles changes dynamically according to the products displayed in the live broadcast.

[0064] 3) Interface refers to the application program interface, which is a set of predefined functions or agreements for connecting different components of a software system. It is used to provide a set of routines that applications and developers can access based on certain software or hardware without having to access the source code or understand the details of the internal working mechanism.

[0065] 4) Push refers to the server actively pushing messages to the client.

[0066] See also Figure 1 , Figure 1 It is an architectural diagram of a system 100 for processing live component information provided in an embodiment of the present application. To support an exemplary application, a terminal 400 (terminal 400-1 and terminal 400-2 are shown as examples) is connected to a server 200 via a network 300. The network 300 may be a wide area network or a local area network, or a combination of the two.

[0067] In actual application, the terminal 400 is provided with a live broadcast client, the anchor can broadcast live through the live broadcast client, and the audience can enter the live broadcast room of interest through the live broadcast client to watch the content of the anchor's live broadcast.

[0068] Terminal 400 is used to present the live broadcast interface of the live broadcast room through the live broadcast client and present components in the live broadcast interface.

[0069] Server 200 is used to obtain functional component information of functional components in a live broadcast interface corresponding to the live broadcast; based on the component information, generate update information of the components in the live broadcast interface; wherein the update information indicates that there is an update of the component content, and is used to update the component content in the live broadcast interface; call the component service interface to push the update information to the live broadcast client corresponding to the live broadcast.

[0070] Terminal 400 is used to update the component content of the live broadcast interface in the live broadcast client.

[0071] In some embodiments, the server 200 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks (CDN, Content Delivery Network), and big data and artificial intelligence platforms. The terminal may be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited thereto. The terminal and the server may be directly or indirectly connected via wired or wireless communication, which is not limited in the embodiments of the present application.

[0072] See also Figure 2 , Figure 2 is a schematic diagram of the structure of the server 200 provided in an embodiment of the present application, Figure 2 The server 200 shown includes: at least one processor 210, a memory 250, at least one network interface 220 and a user interface 230. The various components in the server 200 are coupled together via a bus system 240. It is understood that the bus system 240 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 240 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the bus system 240 is not described in detail. Figure 2 Various buses are labeled as bus system 240 .

[0073] The processor 210 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0074] The user interface 230 includes one or more output devices 231 that enable presentation of media content, including one or more speakers and / or one or more visual display screens. The user interface 230 also includes one or more input devices 232, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0075] The memory 250 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard disk drives, optical disk drives, etc. The memory 250 may optionally include one or more storage devices that are physically remote from the processor 210.

[0076] The memory 250 includes a volatile memory or a non-volatile memory, and may also include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), and the volatile memory may be a random access memory (RAM). The memory 250 described in the embodiments of the present application is intended to include any suitable type of memory.

[0077] In some embodiments, memory 250 can store data to support various operations, examples of which include programs, modules, and data structures, or a subset or superset thereof, as exemplarily described below.

[0078] Operating system 251, including system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;

[0079] A network communication module 252, used to reach other computing devices via one or more (wired or wireless) network interfaces 220, exemplary network interfaces 220 include: Bluetooth, Wireless Compatibility Certification (WiFi), and Universal Serial Bus (USB);

[0080] a presentation module 253 for enabling presentation of information via one or more output devices 231 (e.g., display screen, speaker, etc.) associated with the user interface 230 (e.g., a user interface for operating peripherals and displaying content and information);

[0081] The input processing module 254 is used to detect one or more user inputs or interactions from one of the one or more input devices 232 and translate the detected inputs or interactions.

[0082] In some embodiments, the device provided in the embodiments of the present application can be implemented in software. Figure 2 A processing device 255 for the live broadcast component information stored in the memory 250 is shown, which can be software in the form of programs and plug-ins, etc., including the following software modules: an acquisition module 2551, a generation module 2552 and a push module 2553. These modules are logical, and therefore can be arbitrarily combined or further split according to the functions implemented.

[0083] The functions of each module will be described below.

[0084] In other embodiments, the device provided in the embodiments of the present application can be implemented in hardware. As an example, the device provided in the embodiments of the present application can be a processor in the form of a hardware decoding processor, which is programmed to execute the method for processing live component information provided in the embodiments of the present application. For example, the processor in the form of a hardware decoding processor can adopt one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field programmable gate arrays (FPGAs) or other electronic components.

[0085] The method for processing live component information provided in the embodiment of the present application will be explained in combination with the exemplary application and implementation of the system for processing live component information provided in the embodiment of the present application.

[0086] See also Figure 3 , Figure 3 is a flowchart of a method for processing live component information provided by an embodiment of the present application, which will be combined with Figure 3 The steps shown are explained.

[0087] Step 301: The server obtains component information of functional components in the live broadcast interface corresponding to the live broadcast.

[0088] Here, the functional component is used to present the live broadcast information during the live broadcast process. In practical applications, the live broadcast component information processing method of the present application can be applied to entertainment live broadcast scenarios, and can also be applied to e-commerce live broadcast scenarios. The specific live broadcast scenarios are not limited here, that is, as long as the live broadcast interface includes a functional component, the live broadcast component information processing method of the present application can be used.

[0089] For example, taking the entertainment live broadcast scene as an example, the functional component here can be an activity widget. After the user enters the live broadcast room, the live broadcast client will obtain the component information of the activity widget in the live broadcast interface of the live broadcast room, and display the activity widget in the corresponding position to operate the activity, for example, Figure 4 This is a schematic diagram of the live broadcast interface of the entertainment live broadcast of the embodiment of the present application, see Figure 4 , display the activity widget of the "Peak Showdown" activity in the live broadcast interface, and display the countdown information of the activity through the activity widget. The live broadcast widget information processing method provided in this application can process the activity widget.

[0090] For example, in the case of e-commerce live broadcast, the functional components here can be bubbles or shopping bags. In e-commerce live broadcast, bubbles and shopping bags are important carriers for product recommendations, where bubbles are used to display product images and shopping bags are used to display the number of product types. When a user enters the live broadcast room, the live broadcast client will obtain the component information of bubbles and shopping bags in the live broadcast interface of the live broadcast room, and display the bubbles and shopping bags in the corresponding positions. Figure 5 , Figure 5 This is a schematic diagram of the live broadcast interface of an e-commerce live broadcast provided by an embodiment of the present application. Bubbles and shopping bags are presented in the live broadcast interface. The method for processing live broadcast component information provided by the present application can process the active component. Here, the e-commerce live broadcast room provides a function of pre-occupying a place, that is, when the content of the bubble or the content of the shopping bag is not obtained, the position of the bubble or the shopping bag is vacated first, and other content is not displayed at this position.

[0091] It should be noted that whether it is the activity components in entertainment live broadcasts or the bubbles and shopping bags in e-commerce live broadcasts, they are all a form of presentation of functional components.

[0092] Here, component information changes dynamically as the live broadcast progresses. For example, in an entertainment live broadcast, the countdown information in the activity widget changes in real time, and after the countdown ends, the content of the activity widget will also change, such as presenting a gift box; in an e-commerce live broadcast, the content of the bubble and the quantity in the shopping bag will change dynamically as the live broadcast progresses.

[0093] In some embodiments, the component information of the functional component acquired by the server includes content information, location information, size information, etc. of the functional component.

[0094] In some embodiments, the component information of the functional component obtained by the server may include at least one of the following information: list information of picture + uniform resource locator (URL), list information of icon + URL + quantity, and component list information, that is, a functional component may be composed of pictures, icons, or multiple sub-functional components. It should be noted that the types of functional components are not limited to the above three types, and other component types may also be supported.

[0095] Among them, in the list information of picture+URL, the URL corresponds to the picture, and the corresponding picture can be obtained from the picture server through the URL; correspondingly, in the list information of icon+URL+quantity, the URL corresponds to the icon, and the corresponding icon can be obtained from the icon server through the URL.

[0096] In some embodiments, the server can obtain component information of functional components in the live broadcast interface corresponding to the live broadcast in the following manner: corresponding to at least one dimension, component information of functional components in the live broadcast interface corresponding to the set live broadcast is received, and the dimension includes at least one of the following: global, platform, live broadcast client, and live broadcast room.

[0097] In actual implementation, the component information of the functional components can be set from one or more dimensions to meet the customized requirements of different businesses. For example, different component information can be set for different platforms or for different clients. Here, the platform refers to the system platform, such as the Android platform, the iOS platform, etc.

[0098] It should be noted that the component information of the functional components in the live broadcast interface corresponding to the live broadcast set here can be set by the developer during the development process, and can also be set by the user during use. For example, the anchor can set the component information of the functional components in the live broadcast interface of his live broadcast room during the live broadcast.

[0099] In actual applications, a visual interface for component information settings can be provided to developers or users to facilitate them in setting component information. The visual interface here can be provided by the live broadcast client or by other clients, such as a client dedicated to managing functional components.

[0100] In some embodiments, when there is component information of at least two functional components, each dimension is used as a key and the corresponding component information is used as a value; the weight of each functional component is obtained, and the weight is used to indicate the storage order of the component information of the corresponding functional component; a key-value pair storage method is adopted to store the component information of at least two functional components based on the storage order indicated by the weight of each functional component.

[0101] Here, when there is component information of at least two functional components, the server may use an ordered set data structure to store the acquired component information, such as a zset data structure. In actual implementation, the order of members in the ordered set is determined by the weight of the functional component, wherein the higher the weight, the higher the storage order. The weight here is set by the developer or user when setting the component information.

[0102] In actual applications, when corresponding to multiple dimensions, when receiving component information of functional components in the live broadcast interface corresponding to the set live broadcast, a multi-level key is used, and each dimension corresponds to a key. For example, when receiving component information set based on the global, platform, live broadcast client and live broadcast room dimensions, the component information is stored in the form of 4 levels of keys, that is, global key: global_pendant_info_list, platform key: pendant_info_list_by_client_type_{client_type}, live broadcast client key: pendant_info_list_by_app_id_{app_id}, room key: pendant_info_list_by_room_id_{room_id}.

[0103] In some embodiments, the server may receive component information of functional components in a live broadcast interface corresponding to a live broadcast set by a third-party platform based on a platform as a service interface.

[0104] In actual implementation, in order to improve the scalability of the component information processing system, a Platform as a Service (PaaS) interface is provided to the third-party platform, so that the third-party platform can call the PaaS interface to set the component information of the functional components in the live broadcast interface corresponding to the live broadcast.

[0105] In some embodiments, the server may also obtain the expiration time of the component information; store the component information and the expiration time of the component information; and delete the component information when determining that the component information is expired based on the current time and the expiration time.

[0106] In actual implementation, in order to avoid wasting database resources, a validity period is set for the component information of each functional component, so that when the component information expires, the component information is deleted. Here, a timed expiration strategy, an inert expiration strategy, or a periodic expiration strategy can be adopted.

[0107] In actual applications, when a timed expiration strategy is adopted, a timer is created for each component information with a set validity period to delete the component information immediately after the validity period ends; when an inert expiration strategy is adopted, the current time and the expiration time are compared only when the component information is accessed to determine whether the component information has expired. If so, the component information is deleted; when a periodic expiration strategy is adopted, a certain amount of component information is scanned at regular intervals to compare the current time and the expiration time of the component information. When it is determined that the component information is expired, the component information is deleted.

[0108] In some embodiments, component information of functional components in the live broadcast interface corresponding to the live broadcast can be obtained periodically to reduce storage penetration.

[0109] Step 302: Generate component update information of functional components in the live broadcast interface based on the component information.

[0110] Among them, the update information indicates that there is an update of the component content and is used to update the component content in the live broadcast interface.

[0111] In actual implementation, the server will not push all component information, but only push the changed part of the information to reduce bandwidth resources.

[0112] In some embodiments, the server can generate update information of functional components in the live broadcast interface in the following manner: compare the acquired component information with the component information corresponding to the current component content in the live broadcast interface, and obtain the partial information that has changed relative to the component information corresponding to the current component content in the acquired component information; and use the changed partial information as update information.

[0113] In actual implementation, the partial information that changes may be newly added partial information, modified partial information, deleted partial information, etc.

[0114] For example, the current component content in the live broadcast interface includes picture A, picture B, and picture C, and the corresponding component information is the URL of picture A, picture B, and picture C. The obtained component information is the URL of picture A, picture B, picture C, and picture D. Then, the URL of picture D is used as the update information.

[0115] In some embodiments, the server may record the time of each component information push, and use the component information obtained during the time period between the last time the component information was pushed and the current time point as the update information of the functional component.

[0116] Step 303: Call the component service interface to push update information to the live broadcast client corresponding to the live broadcast.

[0117] Here, the server calls the component service interface and pushes the update information to the live broadcast client corresponding to the live broadcast, so that the live broadcast client updates the component content of the live broadcast interface based on the update information.

[0118] In actual implementation, after the live broadcast client obtains the update information, when the update information corresponds to new component content, the live broadcast client obtains the component content corresponding to the update information from the content server according to the update information.

[0119] In some embodiments, the server may periodically push update information to the live broadcast client corresponding to the live broadcast, such as once per second; in some embodiments, the server may push the acquired update information to the live broadcast client corresponding to the live broadcast immediately after acquiring the update information; in some embodiments, the update information may be pushed to the live broadcast client corresponding to the live broadcast after receiving a push instruction. For example, after the developer modifies the component content, an update instruction is triggered, so that the server acquires the corresponding update information and pushes it to the live broadcast client corresponding to the live broadcast. Here, there may be multiple opportunities for pushing update information, which are not limited here.

[0120] In some embodiments, the server may also push the component version number corresponding to the update information to the live broadcast client corresponding to the live broadcast; wherein the component version number is used for the live broadcast client to update the component content in the live broadcast interface when determining that the component version number is inconsistent with the current component version number.

[0121] In actual implementation, in order to allow the live broadcast client to perceive the update of the component content, a component version number of the update information can be pushed to the live broadcast client corresponding to the live broadcast. The live broadcast client can compare the component version number received this time with the component version number received last time. When the two component version numbers are inconsistent, the component content in the live broadcast interface is updated based on the currently received update information.

[0122] In some embodiments, the server may push the update information to the live broadcast client corresponding to the live broadcast in the following manner: compress the update information to obtain a compressed file corresponding to the update information; and push the compressed file corresponding to the update information to the live broadcast client corresponding to the live broadcast.

[0123] In actual implementation, since the update information includes some URL information, such as image URL, icon URL, etc., the network transmission capacity is large. Therefore, before pushing the update information, the update information will be compressed to obtain a compressed file corresponding to the update information. Here, compression is a mechanism to reduce the size of computer files through a specific algorithm, which can reduce the data size to save storage space and transmission time.

[0124] In some embodiments, the server may push update information to the live broadcast client corresponding to the live broadcast in the following manner: when there are at least two update information, merge the at least two update information to obtain merged update information; and push the merged update information to the live broadcast client corresponding to the live broadcast.

[0125] In actual implementation, when there are a large number of users online, since each user corresponds to a live broadcast client, when the server pushes update information, the push volume is too large, which in turn causes the server to be overloaded. For example, when 90,000 users are watching the live content in the same live broadcast room, the server needs to push update information to the live broadcast clients corresponding to 90,000 people. Assuming that 100 update information needs to be transmitted per second, there will be 9 million pushes per second.

[0126] Based on this, the present application merges and pushes the update information that needs to be pushed, that is, merges at least two pieces of update information to obtain merged update information, and pushes the merged update information to reduce the load on the server.

[0127] For example, the information that needs to be pushed within one second can be combined into one combined update message. That is, originally 100 update messages need to be transmitted per second, and these 100 update messages are combined into one combined update message. In this way, when 90,000 users are watching the live content in the same live broadcast room, the push volume per second is 90,000.

[0128] Figure 6 This is a schematic diagram of the update information push provided by the embodiment of the present application, see Figure 6 For a certain business, the update information is consistently hashed according to the component identifier, and then multiple update information are merged to push the merged update information once per second, so that the merged update information is pushed to the live broadcast client through the message channel. The live broadcast client synchronizes the information based on the received merged update information to update the component content in the live broadcast interface.

[0129] In some embodiments, after the server pushes component update information to the live broadcast client corresponding to the live broadcast, when a prompt message of push failure is received, the number of component update information push failures is obtained; based on the number of update information push failures, a backoff time is determined; when the backoff time is reached, the update information is pushed again to the live broadcast client corresponding to the live broadcast.

[0130] In actual implementation, in order to ensure that the update information can reach the live broadcast client, when a prompt message indicating that the push has failed is received, the update information will be pushed again to the live broadcast client corresponding to the live broadcast until the preset number of pushes is reached or the validity period has expired.

[0131] Here, the backoff time refers to the time point at which the component update information is pushed again. In actual implementation, the more times the push fails, the longer the waiting time is. Here, the backoff time is determined based on the waiting time. For example, after the first push fails, wait for 1 second and push the update information again; after the second push fails, wait for 5 seconds and push the update information again; after the third push fails, wait for 10 seconds and push the update information again, and so on.

[0132] In some embodiments, the server may also push the update time of the corresponding update information to the live broadcast client corresponding to the live broadcast; the update time is used for the live broadcast client to update the component content in the live broadcast interface when the update time arrives.

[0133] In actual implementation, the server pushes the update time of the update information to the live broadcast client corresponding to the live broadcast. After receiving the update information and the corresponding update time, the live broadcast client updates the component content in the live broadcast interface when the update time arrives. Here, the update time refers to a time point.

[0134] In some embodiments, the server may also push the update frequency of the component information to the live broadcast client corresponding to the live broadcast. The live broadcast client may determine the update time according to the update frequency, so as to update the component content in the live broadcast interface when the update time arrives.

[0135] In some embodiments, the server may also push the preloading duration corresponding to the update information to the live broadcast client corresponding to the live broadcast; the preloading duration is used for the live broadcast client to obtain the component content corresponding to the update information within the preloading duration.

[0136] In actual implementation, the server can also push the preloading duration corresponding to the update information to the live broadcast client corresponding to the live broadcast. After receiving the preloading duration, the live broadcast client obtains the component content corresponding to the update information at any time point within the preloading duration.

[0137] Here, when the live broadcast client obtains the component content corresponding to the update information, it needs to send a request to the content server. If the live broadcast clients corresponding to all online users send requests to the content server at the same time, it will cause pressure on the content server. However, the present application pushes the preloading duration corresponding to the update information to the live broadcast client corresponding to the live broadcast. After receiving the preloading duration, the live broadcast client obtains the component content corresponding to the update information at any time point within the preloading duration. In this way, the live broadcast clients corresponding to different users can send requests to the content server at different time points to obtain the corresponding component content, thereby reducing the pressure on the content server.

[0138] In some embodiments, the server obtains the update time of the update information by preloading the component content corresponding to the update information before the update time arrives. That is, the server pushes the update time of the update information to the live broadcast client corresponding to the live broadcast, and after receiving the update information and the corresponding update time, the live broadcast client obtains the component content corresponding to the update information from the content server at any time point before the update time arrives, and when the update time arrives, the component content in the live broadcast interface is updated according to the obtained component content.

[0139] In some embodiments, a web view (webview) can be used to load component information, that is, the component content is displayed and updated through the browser kernel of the live client. In this way, when a new functional component is released, it is not necessary to re-release it, which shortens the launch cycle of the new functional component.

[0140] The present application generates update information of components in a live broadcast interface based on component information; wherein the update information indicates that there is an update to the component content and is used to update the component content in the live broadcast interface; the component service interface is called to push the update information to the live broadcast client corresponding to the live broadcast, so as to update the component content of the live broadcast interface in the live broadcast client based on the update information; thus, since the present application is that the server actively pushes the update information to the live broadcast client without the need for polling by the live broadcast client, the number of heartbeats between the client and the server can be reduced, thus avoiding waste of bandwidth and server resources, and thereby improving the processing performance of the live broadcast component information.

[0141] The following uses the functional component as an active widget as an example to illustrate the method for processing live component information provided by the embodiment of the present application. In some embodiments, the method for processing live component information provided by the embodiment of the present application can be implemented by a terminal and a server system. Figure 7 , Figure 7 : is a flow chart of a method for processing live broadcast component information provided in an embodiment of the present application. The method for processing live broadcast component information provided in an embodiment of the present application includes:

[0142] Step 701: Corresponding to the four dimensions of global, platform, live broadcast client, and live broadcast room, the server receives the first widget information of the widget in the live broadcast interface corresponding to the set live broadcast.

[0143] Step 702: The server obtains the weight of each widget, where the weight is used to indicate the storage order of the widget information of the corresponding widget.

[0144] Step 703: The server stores the first widget information of at least two widgets and the corresponding expiration time in a key-value pair storage method based on the storage order indicated by the weight of each widget, using each dimension as a key and the corresponding first widget information as a value.

[0145] Step 704: In response to a click operation on the live broadcast room entrance, the terminal obtains the widget information of the widget in the live broadcast interface corresponding to the live broadcast from the server.

[0146] Step 705: The terminal presents the live broadcast interface, and displays the widget content corresponding to the widget information at a corresponding position in the live broadcast interface.

[0147] Step 706: Corresponding to the four dimensions of global, platform, live broadcast client, and live broadcast room, the server receives the second widget information of the widget in the live broadcast interface corresponding to the set live broadcast, and stores the second widget information.

[0148] Step 707: The server compares the first widget information and the second widget information, and uses the changed portion of the second widget information relative to the first widget information as widget update information.

[0149] Step 708: The server calls the widget service interface to push the widget update information, the widget version number of the widget update information, and the update time to the terminal.

[0150] Step 709: The terminal compares the currently acquired widget version number with the widget version number acquired last time. When the two widget version numbers are inconsistent, based on the currently received widget update information, the terminal acquires the widget content corresponding to the widget update information at any time before the update time arrives.

[0151] Step 710: When the update time arrives, the terminal updates the widget content of the live broadcast interface based on the widget content corresponding to the obtained widget update information.

[0152] The following is an exemplary application of the embodiment of the present application in an actual application scenario. In actual implementation, the method for processing live component information provided by the embodiment of the present application is applicable to both active widgets in the live interface of entertainment live broadcasts and bubbles and shopping bags in the live interface of e-commerce live broadcasts.

[0153] Figure 8is a schematic diagram of the software system architecture for implementing the method for processing live component information provided in the embodiment of the present application, see Figure 8 The software system provided by the embodiment of the present application includes: a live broadcast client, a browser kernel, a component service, a management backend, and a database. Among them, the live broadcast client has a built-in browser kernel.

[0154] First, the management backend is explained.

[0155] Fig. 9 This is a schematic diagram of the processing flow of the management background provided by the embodiment of the present application, see Fig. 9 , the management backend processing flow includes:

[0156] Step 901: The management backend receives component information of a functional component.

[0157] Here, component information includes content information, location information, etc., which can be set by developers during development or by users during use. In practical applications, a visual interface for component information setting can be provided to developers or users to facilitate them to set component information.

[0158] In order to meet the customization requirements of each business, this application supports setting the component information of functional components from different dimensions, including global, platform, live client, and live room. For example, different component positions can be configured for different platforms.

[0159] Step 902: Store the acquired configuration information.

[0160] Here, since this application supports configuration of the configuration information of functional components from four dimensions, the configuration information of this application can be stored in the form of 4-level keys, namely, global key: global_pendant_info_list, platform key: pendant_info_list_by_client_type_{client_type}, live client key: pendant_info_list_by_app_id_{app_id}, room key: pendant_info_list_by_room_id_{room_id}.

[0161] In actual implementation, the remote dictionary service (Redis) can be used as a database for storing configuration information, and the zset data structure can be used to store the configuration information. In the zset data structure, each element is associated with a score, and the weight of the functional component is used as the score of the corresponding configuration information.

[0162] Step 903: Push component information to the live broadcast client.

[0163] In actual implementation, the interface of the component service is called to push the component information to the live broadcast client.

[0164] Next, the component service is described. The component service mainly provides an interface for pulling component information, an interface for pushing component information changes, and an interface for pushing component data.

[0165] 1. Interface for pulling component information.

[0166] Here, the interface for pulling component information is mainly used to pull the following information: list information of pictures+uniform resource locators, list information of icons+URL+quantity, and component list information.

[0167] The above three types of information correspond to three different component types, for example, a functional component can be composed of pictures or icons. It should be noted that the component types are not limited to the above three types, and other component types can also be supported.

[0168] Since the component information includes URLs, such as picture URLs and icon URLs, the message capacity transmitted over the network is very large. Therefore, this application compresses the list information first and then transmits the data.

[0169] In addition, each component information contains the update frequency of the corresponding information.

[0170] In some embodiments, in order to improve the performance of the system, we will periodically pull component information of the global, platform, live client, and live room dimensions to reduce storage penetration. Since component information is stored in Redis, there will be more and more component information in Redis, resulting in a waste of Redis resources. Here, the strategy of read-after-update is adopted, that is, if the component information is found to be expired, the component information will be deleted.

[0171] 2. The interface for pushing component information changes.

[0172] The interface for pushing component information changes is used to push component update information, that is, only the partial information that has changed relative to the component information stored at the last push is pushed, instead of pushing the full component information, in order to reduce bandwidth resources.

[0173] In order to enable the live broadcast client to perceive the update of the component content, a component version number of the component update information can be pushed to the live broadcast client corresponding to the live broadcast. The live broadcast client can compare the component version number received this time with the component version number received last time. When the two component version numbers are inconsistent, the corresponding component content, such as a new picture, is obtained based on the currently received update information.

[0174] In actual implementation, when there are a large number of users online, since each user corresponds to a live client, when pushing update information, the push volume is too large, which in turn causes excessive system load. For example, when 90,000 users are watching the live content in the same live broadcast room, update information needs to be pushed to the live clients corresponding to 90,000 people. Assuming that 100 update information needs to be transmitted per second, there will be 9 million pushes per second.

[0175] Based on this, the present application merges and pushes the update information that needs to be pushed, that is, merges at least two pieces of update information to obtain merged update information, and pushes the merged update information to reduce the load on the server.

[0176] For example, the information that needs to be pushed within one second can be combined into one combined update message. That is, originally 100 update messages need to be transmitted per second, and these 100 update messages are combined into one combined update message. In this way, when 90,000 users are watching the live content in the same live broadcast room, the push volume per second is 90,000.

[0177] 3. Interface for pushing component data.

[0178] Here, the interface for pushing component data is used to push component data, and component data refers to data such as symbols, text, numbers, etc. in functional components, such as the number of items in a shopping bag.

[0179] When pushing update information or component data, if the push fails, you can use the backoff algorithm, that is, retry at intervals of 1s, 5s, 10s, 1 minute, etc. until the push succeeds. However, this involves the issue of message validity period. If the message deadline exceeds a certain time, the failed message will no longer be pushed.

[0180] In some embodiments, in order to improve the scalability of the component system, the component service of the present application also provides a PaaS interface for a third-party platform to set component information of the component.

[0181] Finally, the live broadcast client and browser kernel are explained. The browser kernel here refers to the browser kernel built into the live broadcast client.

[0182] When a user enters the live broadcast room, the client will pull the component information of the live broadcast room and display the component information in the corresponding position. Here, if the live broadcast client obtains the component information, it will request the content server to obtain the corresponding component content, which will cause the content server to be overloaded. For example, when there are 1 million users online, the content server (such as image CDN) will be caused 1 million requests / s, which exceeds the tolerance of the content server.

[0183] Based on this, after obtaining the component information, the application preloads the component content (such as pictures) asynchronously, that is, preloads the component content at any time within the update frequency range. And displays the component content, such as the number of products and countdown information, through the time passed by the background.

[0184] It should be noted that for e-commerce live broadcasts, this application provides the ability to reserve space in advance, that is, after the user starts the live broadcast, the space for bubbles or shopping bags will be left empty in the live broadcast interface without displaying other content at that position.

[0185] In actual applications, webview can be used to load component information, that is, the live client can send component update information to the browser kernel, and display and update component content through the browser kernel of the live client. In this way, when releasing new components, there is no need to re-release them, which shortens the launch cycle of new components.

[0186] The embodiments of the present application have the following beneficial effects:

[0187] 1. It is applicable to both live broadcast rooms for entertainment and live broadcast rooms for e-commerce;

[0188] 2. Each module performs its own functions, effectively improving the stability and versatility of the component information processing system.

[0189] 3. Provide a visual interface for functional component settings, facilitate the online and offline operation of functional components, and manage component information by hierarchical keys, effectively improving the processing performance of component information.

[0190] 4. By compressing component information before transmission, the data size is reduced to save storage space and transmission time;

[0191] 5. By merging and pushing multiple component update information, the pressure on downstream systems can be reduced, and when a large number of users are online, the pressure on third-party resources can be effectively reduced;

[0192] 6. Provide PaaS for third-party platforms, improving the scalability of the system;

[0193] 7. Improve system performance and user experience by asynchronously preloading component content.

[0194] Next, the exemplary structure of the live broadcast component information processing device 255 provided in the embodiment of the present application implemented as a software module is described. Fig.10 is a schematic diagram of the structure of the live broadcast component information processing device provided in the embodiment of the present application, such as Fig.10As shown, the apparatus for processing live component information provided in the embodiment of the present application includes:

[0195] The acquisition module 2551 is used to obtain component information of functional components in the live broadcast interface corresponding to the live broadcast;

[0196] A generating module 2552, configured to generate update information of components in the live broadcast interface based on the component information;

[0197] The update information indicates that there is an update of the component content, and is used to update the component content in the live broadcast interface;

[0198] Push module 2553 is used to call the component service interface to push the update information to the live broadcast client corresponding to the live broadcast.

[0199] Based on the update information, the component content of the live broadcast interface in the live broadcast client is updated.

[0200] In some embodiments, the acquisition module 2551 is also used to receive component information of functional components in the live broadcast interface corresponding to the set live broadcast corresponding to at least one dimension, and the dimension includes at least one of the following: global, platform, live broadcast client, and live broadcast room.

[0201] In some embodiments, the apparatus further comprises:

[0202] A storage module, for, when there is component information of at least two functional components, using each of the dimensions as a key and using the corresponding component information as a value;

[0203] Obtaining a weight of each of the functional components, wherein the weight is used to indicate a storage order of component information of the corresponding functional component;

[0204] The component information of the at least two functional components is stored in a key-value pair storage manner based on a storage order indicated by the weight of each functional component.

[0205] In some embodiments, the acquisition module 2551 is further used to acquire the expiration time of the component information;

[0206] storing the component information and the expiration time of the component information;

[0207] When it is determined based on the current time and the expiration time that the component information is in an expired state, the component information is deleted.

[0208] In some embodiments, the acquisition module 2551 is also used to receive component information of functional components in the live broadcast interface corresponding to the live broadcast set by the third-party platform based on the platform as a service interface.

[0209] In some embodiments, the acquisition module 2551 is further used to compare the acquired component information with the component information corresponding to the current component content in the live broadcast interface, and obtain the partial information of the acquired component information that has changed relative to the component information corresponding to the current component content;

[0210] The changed part of information is taken as update information.

[0211] In some embodiments, the push module 2553 is further used to push the component version number corresponding to the update information to the live broadcast client corresponding to the live broadcast;

[0212] The component version number is used by the live broadcast client to update the component content in the live broadcast interface when the live broadcast client determines that the component version number is inconsistent with the current component version number.

[0213] In some embodiments, the push module 2553 is further used to compress the update information to obtain a compressed file corresponding to the update information;

[0214] Push a compressed file corresponding to the update information to a live broadcast client corresponding to the live broadcast.

[0215] In some embodiments, the push module 2553 is further used to merge at least two pieces of update information of functional components to obtain merged update information when there are at least two pieces of update information of functional components;

[0216] Push the merged update information to the live broadcast client corresponding to the live broadcast.

[0217] In some embodiments, the push module 2553 is further used to obtain the number of update information push failures when receiving a push failure prompt message;

[0218] Determining a backoff time according to the number of failed pushes of the update information;

[0219] When the backoff time arrives, the update information is pushed again to the live broadcast client corresponding to the live broadcast.

[0220] In some embodiments, the push module 2553 is further used to push the update time corresponding to the update information to the live broadcast client corresponding to the live broadcast;

[0221] The update time is used by the live broadcast client to update the component content in the live broadcast interface when the update time arrives.

[0222] In some embodiments, the push module 2553 is further used to push the preload duration corresponding to the update information to the live broadcast client corresponding to the live broadcast;

[0223] The preloading duration is used for the live broadcast client to obtain component content corresponding to the update information within the preloading duration.

[0224] An embodiment of the present application provides a computer device, including:

[0225] A memory for storing executable instructions;

[0226] The processor is used to implement the method provided in the embodiment of the present application when executing the executable instructions stored in the memory.

[0227] An embodiment of the present application provides a computer-readable storage medium storing executable instructions for causing a processor to execute and implement the method for processing live broadcast component information provided by the embodiment of the present application.

[0228] The present application embodiment provides a computer-readable storage medium storing executable instructions, wherein the executable instructions are stored. When the executable instructions are executed by a processor, the processor will be caused to execute the method provided by the present application embodiment, for example, Figure 3 The method shown.

[0229] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface storage, optical disk, or CD-ROM; or it may be various devices including one or any combination of the above memories.

[0230] In some embodiments, executable instructions may be in the form of a program, software, software module, script or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment.

[0231] As an example, executable instructions may, but need not, correspond to a file in a file system, may be stored as part of a file that stores other programs or data, such as in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or code portions).

[0232] By way of example, executable instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one site, or on multiple computing devices distributed across multiple sites and interconnected by a communication network.

[0233] The above is only an embodiment of the present application and is not intended to limit the protection scope of the present application. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A method for processing live broadcast component information, characterized in that: The method comprises: Obtaining component information of functional components in a live broadcast interface corresponding to the live broadcast, wherein the component information changes dynamically as the live broadcast proceeds; Based on the component information, generating update information of the functional components in the live broadcast interface; The update information indicates that there is an update of the component content, and is used to update the component content in the live broadcast interface; Calling a component service interface to push the update information and the preloading duration and update time corresponding to the update information to a live broadcast client corresponding to the live broadcast, so as to update the component content of the live broadcast interface in the live broadcast client based on the update information; The preloading duration is used for the live broadcast clients corresponding to different users to obtain the component content corresponding to the update information at different time points within the preloading duration; the update time is used for the live broadcast clients corresponding to different users to update the component content in the live broadcast interface according to the obtained component content corresponding to the update information when the update time arrives; The step of pushing the update information to a live broadcast client corresponding to the live broadcast includes: When there are at least two pieces of update information, performing consistent hashing on the update information according to the component identifier to merge the at least two pieces of update information to obtain merged update information; Push the merged update information to the live broadcast client corresponding to the live broadcast.

2. The method according to claim 1, characterized in that The obtaining of component information of functional components in the live broadcast interface corresponding to the live broadcast includes: Corresponding to at least one dimension, component information of functional components in the live broadcast interface corresponding to the set live broadcast is received, and the dimension includes at least one of the following: global, platform, live broadcast client, and live broadcast room.

3. The method according to claim 2, characterized in that After obtaining the component information of the functional components in the live broadcast interface corresponding to the live broadcast, the method further includes: When there is component information of at least two functional components, each dimension is used as a key and the corresponding component information is used as a value; Obtaining a weight of each of the functional components, wherein the weight is used to indicate a storage order of component information of the corresponding functional component; The component information of the at least two functional components is stored in a key-value pair storage manner based on a storage order indicated by the weight of each functional component.

4. The method according to claim 1, characterized in that The method further comprises: Get the expiration time of component information; storing the component information and the expiration time of the component information; When it is determined based on the current time and the expiration time that the component information is in an expired state, the component information is deleted.

5. The method according to claim 1, characterized in that The obtaining of component information of functional components in the live broadcast interface corresponding to the live broadcast includes: Component information of functional components in a live broadcast interface corresponding to the live broadcast set by the third-party platform based on the platform as a service interface is received.

6. The method according to claim 1, characterized in that The step of generating update information of functional components in the live broadcast interface based on the component information includes: Compare the acquired component information with the component information corresponding to the current component content in the live broadcast interface to obtain partial information of the acquired component information that has changed relative to the component information corresponding to the current component content; The changed part of information is used as component update information.

7. The method according to claim 1, characterized in that The method further comprises: Pushing the component version number corresponding to the update information to the live broadcast client corresponding to the live broadcast; The component version number is used by the live broadcast client to update the component content in the live broadcast interface when the live broadcast client determines that the component version number is inconsistent with the current component version number.

8. The method according to claim 1, characterized in that The pushing the update information to the live broadcast client corresponding to the live broadcast includes: Compressing the update information to obtain a compressed file corresponding to the update information; Push a compressed file corresponding to the update information to a live broadcast client corresponding to the live broadcast.

9. The method according to claim 1, characterized in that The pushing the update information to the live broadcast client corresponding to the live broadcast includes: When there are at least two pieces of update information, merge the at least two pieces of update information to obtain merged update information; Push the merged update information to the live broadcast client corresponding to the live broadcast.

10. The method according to claim 1, characterized in that After pushing the update information to the live broadcast client corresponding to the live broadcast, the method further includes: When receiving a push failure prompt message, obtaining the number of update information push failures; Determining a backoff time according to the number of failed pushes of the update information; When the backoff time arrives, the update information is pushed again to the live broadcast client corresponding to the live broadcast.

11. A device for processing live broadcast component information, characterized in that: The device comprises: An acquisition module, used to acquire component information of components in the live broadcast interface corresponding to the live broadcast; A generating module, used for generating update information of components in the live broadcast interface based on the component information; The update information indicates that there is an update of the component content, and is used to update the component content in the live broadcast interface; A push module, used to call a component service interface, push the update information and the preloading duration and update time corresponding to the update information to the live broadcast client corresponding to the live broadcast, so as to update the component content of the live broadcast interface in the live broadcast client based on the update information; wherein the preloading duration is used for the live broadcast clients corresponding to different users to obtain the component content corresponding to the update information at different time points within the preloading duration; the update time is used for the live broadcast clients corresponding to different users to update the component content in the live broadcast interface according to the obtained component content corresponding to the update information when the update time arrives; The push module is also used to, when there are at least two pieces of update information, perform consistent hashing on the update information according to the component identifier to merge the at least two pieces of update information to obtain merged update information; and push the merged update information to the live broadcast client corresponding to the live broadcast.

12. A computer device, characterized in that: include: A memory for storing executable instructions; The processor is used to implement the method for processing live broadcast component information as described in any one of claims 1 to 10 when executing the executable instructions stored in the memory.

13. A computer-readable storage medium, characterized in that: Executable instructions are stored, which are used to implement the method for processing live broadcast component information as described in any one of claims 1 to 10 when executed by a processor.

Images