Live broadcast forecast generation method and device, equipment, medium and program product
By integrating a preview release page into the live broadcast preview generation method, preview content is automatically generated and released, and a reservation entry is embedded. This solves the problems of cumbersome and inefficient live broadcast preview processes, achieving efficient one-click operation and improved user experience.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-28
- Publication Date
- 2026-04-14
AI Technical Summary
In existing technologies, the creation and publishing process of live broadcast announcements is separated from the live broadcast configuration, which is cumbersome, error-prone, and lacks an automatic association mechanism, resulting in low publishing efficiency and poor user experience.
A method for generating live broadcast previews is provided. By displaying a publishing page containing live broadcast previews and publishing confirmation controls on the broadcaster's end, preview content is automatically generated and the publishing time is set. The live broadcast reservation entry is embedded in the preview page, realizing one-click generation and publishing.
It enables one-click generation and publishing of live broadcast schedules from pre-broadcast subjects to scheduleable live broadcast announcements, reducing operation jumps, ensuring that the content of the announcement is consistent with the live broadcast subject, and improving the efficiency of live broadcast preparation and user experience.
Smart Images

Figure CN121864997A_ABST
Abstract
Description
Technical Field
[0001] This specification relates to the field of online live streaming technology, and in particular to a live stream preview generation method, apparatus, device, medium, and program product. Background Technology
[0002] With the rapid development of short videos and live-streaming e-commerce, content creators and merchants generally rely on tools provided by platforms for live-streaming preparation and user outreach. Among these, live-streaming announcements, as a key pre-live-streaming step to attract user reservations and increase viewership, are usually released in the form of text, images, or short videos before the live stream begins, along with specific live-streaming session information, to guide users to make reservations in advance and watch on time.
[0003] However, in existing technologies, the creation and publishing process of live stream previews is often separated from the configuration of the target live stream. Users need to create the live stream session first, then manually enter a separate preview editing page to re-enter information such as title, time, and cover image, and may even need to manually bind the live stream link. This process is not only cumbersome and fragmented, but also prone to mismatches between preview content and the actual live stream due to inconsistent information. In addition, there is no automatic association mechanism between the preview and the live stream reservation entry after the preview is published, requiring additional configuration of redirection logic, which reduces publishing efficiency and user experience. Summary of the Invention
[0004] In view of the above, embodiments of this specification provide a method for generating live broadcast previews. One or more embodiments of this specification also relate to a live broadcast preview generation apparatus, a computing device, a computer-readable storage medium, and a computer program product, to address the technical deficiencies existing in the prior art.
[0005] According to a first aspect of the embodiments of this specification, a live broadcast preview generation method is provided, applied to a broadcaster's end, including: In response to the determination of the backup broadcast object for the target live broadcast, a live broadcast preview publishing page is displayed. The live broadcast preview publishing page includes at least one live broadcast preview and at least one live broadcast preview publishing confirmation control. At least one live broadcast preview is generated based on the determined backup broadcast object, and the publishing confirmation control is used to determine the publishing time of at least one live broadcast preview. In response to identifying a target live stream preview in at least one live stream preview, the target live stream preview is published based on the publication time, wherein the display page of the target live stream preview includes a live stream reservation entry for the target live stream.
[0006] According to a second aspect of the embodiments of this specification, a live broadcast preview generation method is provided, applied to a server, including: In response to the host's operation of determining the backup broadcast object for the target live broadcast, obtain the backup broadcast object; Generate live broadcast schedules based on the backup broadcast targets; Obtain the release time determined by the broadcaster for the target live stream announcement; Publish target live stream previews based on the release time, and configure a live stream reservation entry on the target live stream preview display page.
[0007] According to a third aspect of the embodiments of this specification, a live broadcast preview generation device is provided, applied to a broadcaster's end, comprising: The display module is configured to display a live broadcast preview publishing page in response to the determination operation of the backup broadcast object that has completed the target live broadcast. The live broadcast preview publishing page includes at least one live broadcast preview and at least one live broadcast preview publishing confirmation control. At least one live broadcast preview is generated based on the determined backup broadcast object, and the publishing confirmation control is used to determine the publishing time of at least one live broadcast preview. The publishing module is configured to publish the target live stream preview based on the publication time in response to identifying the target live stream preview in at least one live stream preview, wherein the display page of the target live stream preview includes the live stream reservation entry for the target live stream.
[0008] According to a fourth aspect of the embodiments of this specification, a live broadcast preview generation apparatus is provided, applied on a server, comprising: The first acquisition module is configured to acquire the backup broadcast object in response to the confirmation operation of the backup broadcast object after the broadcaster completes the target live broadcast. The generation module is configured to generate live broadcast schedules based on the backup broadcast objects. The second acquisition module is configured to acquire the release time determined by the broadcaster for the target live broadcast preview; The configuration module is configured to publish target live stream previews based on the release time, and to configure a live stream reservation entry on the target live stream preview display page.
[0009] According to a fifth aspect of the embodiments of this specification, a computing device is provided, comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor, they implement the steps of the above-described live broadcast preview generation method.
[0010] According to a sixth aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores a computer program / instructions that, when executed by a processor, implement the steps of the above-described live broadcast preview generation method.
[0011] According to a seventh aspect of the embodiments of this specification, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described live broadcast preview generation method.
[0012] One embodiment of this specification implements a live broadcast preview publishing page in response to the determination of a backup broadcast object for the target live broadcast. The live broadcast preview publishing page includes at least one live broadcast preview and at least one live broadcast preview publishing confirmation control. The at least one live broadcast preview is generated based on the determined backup broadcast object, and the publishing confirmation control is used to determine the publishing time of the at least one live broadcast preview. In response to determining the target live broadcast preview among the at least one live broadcast preview, the target live broadcast preview is published based on the publishing time. The display page of the target live broadcast preview includes a live broadcast reservation entry for the target live broadcast.
[0013] After the target live stream is identified, a live stream preview release page is displayed, containing at least one automatically generated live stream preview based on that preview and a corresponding release confirmation control. This allows users to confirm the preview content and set the release time on the same interface. In response to selecting a target live stream preview, the system automatically releases the preview according to the set release time, and the display page naturally includes a live stream reservation entry point pointing to the target live stream. This achieves one-click generation and release from the target live stream to the available live stream preview, reducing operation jumps and manual configuration steps, ensuring consistency between the preview content and the live stream content, and directly connecting the preview display and user reservation path, improving live stream preparation efficiency and the continuity of the user conversion process. Attached Figure Description
[0014] Figure 1 This is a flowchart illustrating a live broadcast preview generation method provided in one embodiment of this specification; Figure 2 This is a flowchart of another live broadcast preview generation method provided in one embodiment of this specification; Figure 3 This is a flowchart illustrating the processing steps of a live broadcast preview generation method provided in one embodiment of this specification. Figure 4 This is one of the schematic diagrams of a front-end display interface for generating live broadcast previews provided in one embodiment of this specification; Figure 5 This is a second schematic diagram of a front-end display interface for generating live broadcast previews, provided in one embodiment of this specification. Figure 6 This is the third schematic diagram of a front-end display interface for generating live broadcast previews, provided in one embodiment of this specification. Figure 7 This is the fourth schematic diagram of a front-end display interface for generating live broadcast previews, provided in one embodiment of this specification. Figure 8 This is a schematic diagram of the structure of a live broadcast preview generation device provided in one embodiment of this specification; Figure 9 This is a schematic diagram of another live broadcast preview generation device provided in one embodiment of this specification; Figure 10 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation
[0015] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.
[0016] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.
[0017] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."
[0018] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.
[0019] First, the terms and concepts used in one or more embodiments of this specification will be explained.
[0020] Content posted: refers to the structured information units created and publicly shared by the host on the platform. It usually includes multimedia elements such as titles, body text, pictures or videos, and is used to convey content such as live broadcast topics, product information or life scenarios to the audience. It is the basic carrier for carrying preview information and user interaction.
[0021] Preparation stage: This refers to the stage in which merchants prepare before the live broadcast begins.
[0022] Live streaming traffic generation: This refers to the methods merchants use to increase traffic to their live streaming rooms before the live stream, such as using attractive cover images, titles, pre-release content, and configuring live stream reservation entrances.
[0023] The new full-link traffic acquisition system integrates independent traffic acquisition functions such as live stream cover title generation, pre-heating content creation and release, and live stream reservation configuration into a continuous workflow.
[0024] Intelligent Generation Engine: An algorithm module that automatically generates cover images, titles, and published content based on multi-dimensional information such as product materials, user characteristics, and platform data.
[0025] Theme-based preview content: Unlike simple product introductions, this type of preview content aggregates multiple live-streaming products around a specific theme (such as "good home goods under 100 yuan") and creates content based on dimensions such as scenarios, functions, and value. It aims to systematically generate interest and preview live-streaming events.
[0026] Optimal release time: Based on historical content release data, popular time periods on the platform, and competitor release patterns, the optimal time for content push is predicted.
[0027] Automatic activation of live stream reservations: In this manual, it means that after completing the basic information settings (such as time, product, title), the system will automatically associate and display the live stream reservation entrance and preview information in all relevant locations on the platform (such as product release content, theme release content, personal homepage, etc.) with one click, upgrading the reservation from simply "creating" an event page to "activating" comprehensive preview exposure.
[0028] Identify existing published content and enable live stream reservation with one click: In this manual, it refers to identifying the historical published content of the product based on the product selection for this live stream and linking these published contents to the live stream reservation portal with one click.
[0029] With the deepening development of the digital economy, live-streaming e-commerce has become one of the core scenarios connecting merchants and consumers. Across all product categories, including apparel, home furnishings, and cosmetics, merchants widely rely on live-streaming for product display and instant conversion. To improve the effectiveness of their broadcasts, platforms typically require merchants to release pre-broadcast announcements (such as cover images, titles, and pre-release content) to attract user reservations and build up traffic. This process not only affects the exposure of a single live stream but also directly impacts overall operational efficiency and sales conversion rates.
[0030] However, in the current live streaming ecosystem, small and medium-sized businesses often lack professional operation teams, making it difficult to efficiently create and distribute high-quality content for attracting traffic. Although platforms offer various traffic-generating tools, these functions are scattered across different modules, with fragmented operation paths. This forces businesses to repeatedly switch between multiple interfaces, wasting a lot of time and increasing the risk of errors. Furthermore, due to a lack of data-driven content generation capabilities, the preview content created by businesses themselves often fails to align with user interests or the platform's recommendation mechanisms, further weakening the traffic-generating effect.
[0031] Existing live broadcast preparation processes typically employ a sequential model of "first creating a live broadcast session, then manually configuring the preview": Merchants first fill in basic data such as the broadcast time and product information in the live broadcast management backend, then are redirected to a separate preview editing page to re-upload the cover, write the title, compose the pre-release content, and manually select the release time; finally, they also need to enter the reservation settings module to separately enable the reservation switch for each channel. The entire process consists of multiple isolated steps, relying on manual judgment and operation.
[0032] The aforementioned backup broadcast method has significant drawbacks: First, the operation is highly fragmented, requiring merchants to repeatedly input the same information, making the process lengthy and prone to overlooking key steps; second, the preview content relies entirely on manual creation, and small and medium-sized merchants, limited by their creativity and experience, find it difficult to produce highly attractive materials; third, the release time is subjectively set by the user and cannot be automatically aligned with peak platform traffic; fourth, live broadcast reservations require explicit configuration, and if not actively enabled, the reservation entry cannot be displayed in key touchpoints such as recommendation slots and follow pages, resulting in lost traffic opportunities.
[0033] To address the aforementioned issues, this specification proposes an interactive method for automatically generating the entire livestream traffic acquisition path: After a merchant determines the target livestream's backup audience, the system automatically generates at least one livestream preview associated with it. This preview includes a cover image, title, and pre-launch theme content intelligently generated based on multi-dimensional data. Through the integrated livestream preview release page, merchants can confirm the release time with one click, and the system will then automatically push the preview to the optimal time slot. Simultaneously, the target livestream preview display page naturally embeds a livestream reservation entry, achieving full-channel reservation coverage without additional configuration. This integrates the originally fragmented and inefficient manual process into a continuous, intelligent, and automatic one-stop traffic acquisition closed loop within the backup stage.
[0034] This specification provides a method for generating live broadcast previews, and also relates to a live broadcast preview generation apparatus, a computing device, and a computer-readable storage medium, which will be described in detail in the following embodiments.
[0035] See Figure 1 , Figure 1 This is a flowchart of a live broadcast preview generation method provided in one embodiment of this specification, specifically including the following steps 102-104.
[0036] Step 102: In response to the determination of the backup broadcast object for the target live broadcast, the live broadcast preview release page is displayed. The live broadcast preview release page includes at least one live broadcast preview and at least one live broadcast preview release confirmation control. At least one live broadcast preview is generated based on the determined backup broadcast object, and the release confirmation control is used to determine the release time of at least one live broadcast preview.
[0037] The backup broadcast object is the basic data unit used to generate live broadcast previews. It contains structured information related to the target live broadcast, such as product identifiers, core selling point text, main image materials, and applicable scenario tags.
[0038] Live broadcast previews are automatically generated content entities based on the live broadcast target and can be published on the platform. They include cover images, title text, pre-broadcast copy, and related product information, such as a preview for a "niche gift special".
[0039] The live broadcast preview page is the interactive interface on the broadcaster's end used to preview, edit, and confirm live broadcast previews. It can be a webpage or application interface that includes preview cards, time controls, and operation buttons.
[0040] The publish confirmation control is an interactive component that sets the publish time of a live broadcast announcement, such as a toggle button, a date picker, or a list of time slot options.
[0041] In practical applications, after the system detects that the broadcaster has completed the operation of identifying the backup broadcast objects for the target live stream, it automatically triggers a preview generation task. Based on the materials and feature data in the backup broadcast objects, it synthesizes at least one live stream preview and loads it onto the live stream preview publishing page for display. This page also renders the corresponding publishing confirmation control, allowing the broadcaster to specify the publishing time of the preview. The system can generate one or more differentiated previews based on the number or classification dimensions of the backup broadcast objects. Each preview is independently bound to a publishing confirmation control, allowing the publishing time to be set separately. After the broadcaster selects a specific date and time period through the control, the system records the time parameter and associates it with the corresponding preview, providing a scheduling basis for subsequent scheduled publishing.
[0042] For the step "Display the live broadcast preview release page", one option is to have the front-end framework dynamically render a page containing preview cards and time controls after the broadcaster submits the backup broadcast object; another option is to have the server pre-generate a page template, fill in the preview content, and then return it to the client for display. This is not limited here.
[0043] For example, on a content sharing platform with live streaming capabilities, after the broadcaster completes the selection of backup broadcast targets, the system automatically generates multiple live streaming previews with different themes based on the materials of the associated products and user characteristics. After entering the preview release page, the previews are displayed side by side in the form of cards, and each card is equipped with a preset release time option. When the broadcaster enables a specific time period switch for a preview, the system triggers the time selection interface, receives the specific release time specified by the user, and binds the time only to the selected preview, while the other previews remain in an unreleased state, realizing independent configuration and on-demand release of multiple previews.
[0044] Furthermore, the release determination control includes candidate release times, and the live broadcast preview includes at least one of preview content and cover title; the live broadcast preview release page includes at least one of the following: displaying a candidate release time area, wherein the candidate release time area is used to display at least one candidate content release time; displaying a preview content editing area, wherein the preview content editing area is used to display the preview content of the target live broadcast; and displaying a cover title display area, wherein the cover title display area is used to display the cover image and title text of the target live broadcast.
[0045] The release confirmation control is a collection of interactive components used by broadcasters to set the release time of live broadcast announcements. Its core components include one or more candidate release time options.
[0046] The candidate release time is a specific time point recommended or preset by the system that can be used to release the announcement, such as "10:00 3 days before the live broadcast" or "18:00 2 days before the live broadcast".
[0047] A live broadcast preview is a preview content entity generated based on the backup broadcast object. Its components include at least one of the preview content, cover image and title text.
[0048] The preview content consists of text or image information describing the target live stream theme, products, or scenario, such as "18 great items under 100 yuan, niche yet practical".
[0049] The cover image is the main visual for the live stream preview, usually generated from the product's main image or a scene image.
[0050] The title text is a short summary of the live stream's theme, such as "Camping Ceiling Gear Checklist".
[0051] The candidate release time area is a UI block used to display candidate release times, such as a time period switch list or a calendar pop-up entry.
[0052] The preview content editing area is the interface area that displays and supports editing preview content, such as rich text input boxes or graphic cards.
[0053] The cover title display area is a visual area that presents the cover image and title text side by side, such as a top banner or card-style preview area.
[0054] In practical applications, when displaying the live broadcast preview release page, the system dynamically renders at least one of the following areas based on the function configuration: When rendering the candidate release time area, this area displays one or more candidate content release times in the form of a toggle button, drop-down menu, or calendar icon, allowing the broadcaster to quickly select; when rendering the preview content editing area, this area loads the preview content of the target live broadcast, allowing the broadcaster to view or further edit the text and images; when rendering the cover title display area, this area displays the cover image and title text side by side or overlaid, ensuring visual and textual consistency; each area can exist independently or be presented in combination, depending on the interaction granularity required by the current task; the system ensures that all displayed content originates from the generated live broadcast previews and maintains semantic association with the target broadcast.
[0055] For the step "Display live broadcast preview release page", one option is: the front end dynamically constructs the DOM structure of three areas based on the preview data returned by the server; another option is: the server pre-renders a page template containing area placeholders, and the client fills in the content as needed, which is not limited here.
[0056] In the embodiments described in this specification, the live broadcast preview publishing page uses a structured area division to allow the selection of the publishing time and the content preview to be completed on the same interface, which improves the efficiency of the broadcaster configuration and the intuitiveness of the operation.
[0057] For example, in the preview release interface of a live streaming platform, after loading the live stream preview data, the system structurally renders three core functional areas on the page: the top cover title display area presents a cover image composed of multiple product materials and corresponding title text; the middle preview content editing area displays structured description text automatically generated based on the backup broadcast object and related topic tags, supporting the broadcaster to make partial modifications; the bottom candidate release time area provides multiple preset time slot options, presented in the form of a switch and highlighting the recommended time slot by default; the data in each area all originates from the same preview entity, and users can complete the collaborative configuration of the cover, copy, and release time within a single page.
[0058] Furthermore, the candidate release time area includes at least one of a preset time period option, a calendar component, and a recommended release time prompt; displaying the candidate release time area includes at least one of the following: displaying a preset time period option, in response to a selection operation of any time period option, determining the corresponding candidate content release time, and displaying a live broadcast preview containing the candidate content release time on the live broadcast preview release page; displaying a calendar component, in response to a selection operation of a specific date in the calendar component, determining the candidate content release time in combination with a time selection control, and displaying a live broadcast preview containing the candidate content release time on the live broadcast preview release page; displaying a recommended release time prompt, in response to a confirmation operation of the recommended release time prompt, determining the candidate content release time, and displaying a live broadcast preview containing the candidate content release time on the live broadcast preview release page.
[0059] The candidate release time area is an interface module used to display and select the release time of the live broadcast preview.
[0060] The preset time slot options are several predefined combinations of release times, usually presented in the form of "X days before the live broadcast + popular time slots", such as "10:00 3 days before the live broadcast" or "18:00 2 days before the live broadcast".
[0061] The calendar component is a graphical control that supports date selection. It is usually displayed in a month view and allows users to click on specific dates.
[0062] The time selection control is an hour and minute selector used in conjunction with the calendar component, such as a scroll wheel or drop-down time input box.
[0063] The recommended release time suggestion is a suggested release time calculated based on historical interaction data and platform distribution patterns, and is usually marked with a "Recommended" label or highlighted.
[0064] In practical applications, when the system renders the candidate release time area on the live broadcast preview release page, it includes at least one of the following: preset time period options, calendar components, and recommended release time prompts. When the preset time period options are displayed, the system lists multiple fixed release times in the form of buttons or cards. After the broadcaster clicks any option, the system immediately records that time as the candidate content release time and updates the time information in other areas of the page (such as the bottom of the preview card). When the calendar component is displayed, the system simultaneously loads the corresponding time selection control. The broadcaster first selects the target date in the calendar and then sets the specific time through the time selection control. The combination of the two constitutes the complete candidate content release time, and the system then refreshes the time synchronously on the page. When the recommended release time prompts are displayed, the system prominently displays one or more recommended times (such as "Recommendation: December 24, 19:00"). After the broadcaster clicks the "Confirm" or "Use Recommendation" button, the time is adopted as the candidate content release time and reflected in the live broadcast preview.
[0065] For the step "Display candidate release time range", one option is: the front end dynamically selects the display format based on the device type, prioritizing the display of preset time slot options on mobile devices and expanding the calendar component by default on desktop devices; another option is: the system automatically determines which interaction method to promote based on the broadcaster's historical behavior preferences, for example, broadcasters who frequently use recommended times will be shown recommended release time prompts by default, which is not limited here.
[0066] In the embodiments of this specification, the candidate release time area adapts to different user habits through various interactive forms, which not only reduces the operation threshold, but also guides the broadcaster to choose a more suitable release time.
[0067] For example, the system provides multiple release time configuration methods on the preview release page: by default, it displays several preset time slot options based on the live broadcast time offset, one of which is marked as recommended; after the user selects any preset option, the corresponding specific release time is synchronized to the preview display area in real time; at the same time, it provides a custom time entry, which expands the calendar and time selection control after clicking. After the user selects a specific date and time, the system deselects the preset option and applies the custom time to the preview; in addition, the page also dynamically displays the intelligent recommended release time calculated based on the user's fan activity data, which can be overridden by the user after confirmation; all time changes are updated in real time to the preview, realizing seamless switching and instant feedback of multiple time configuration modes.
[0068] Furthermore, the live broadcast preview release page displays a preview content editing area, including at least one of the following: displaying topic category tags on the live broadcast preview release page, responding to a click operation on the topic category tags, matching and displaying preview content under the corresponding topic, and displaying a live broadcast preview containing the preview content on the live broadcast preview release page; displaying an editable title input box and content text area on the live broadcast preview release page, responding to editing operations on the input box and text area, generating and displaying preview content, and displaying a live broadcast preview containing the preview content on the live broadcast preview release page; displaying an image selection area on the live broadcast preview release page, responding to the upload or selection of multiple images, combining the images and displaying them as preview content, and displaying a live broadcast preview containing the preview content on the live broadcast preview release page.
[0069] The preview content editing area is an interface module used to display, edit, or reconstruct the main text of the live broadcast preview.
[0070] Thematic category tags are identifiers for preview content categories divided according to preset dimensions, such as "Scenario-based", "Price-based", and "Function-based".
[0071] The title input box is a text input component used to enter or modify the title of the live broadcast preview.
[0072] The content text area is a multi-line text area used to edit the preview text, supporting rich text or plain text formats.
[0073] The image selection area is an interactive block that supports uploading or selecting multiple images from the resource library, and is usually presented in the form of a grid or gallery.
[0074] In practical applications, when the system renders the preview content editing area on the live broadcast preview release page, it includes at least one of the following forms: When displaying topic category tags, the system lists multiple topic categories in the form of tabs or button groups. After the broadcaster clicks on a tag (such as "Scene Category"), the system matches the preset text structure and keyword combination under that topic from the content template library, automatically generates the corresponding preview content and fills it into the editing area, while updating the display status of the entire live broadcast preview; When displaying an editable title input box and content text area, the system loads the initial title and body of the current preview. The broadcaster can directly modify the text content. Each input or paste operation triggers a content update, and the system synchronizes the new content to the preview view of the live broadcast preview in real time; When displaying an image selection area, the system provides a local upload entry and a historical material library browsing panel. The broadcaster can select multiple images, and the system combines the selected images into text and image content according to preset layout rules (such as horizontal splicing and main and secondary image layout), and embeds it as part of the preview content into the live broadcast preview.
[0075] Regarding the step "Display the preview content editing area on the live broadcast preview release page", one option is that the system automatically recommends the default editing mode based on the attributes of the target audience. For example, product live broadcasts prioritize displaying theme category tags, while event live broadcasts enable text editing by default. Another option is that the broadcaster can manually switch editing modes, with all three modes coexisting in the same area and switching between them via tabs. This is not limited here.
[0076] In the embodiments of this specification, the preview content editing area supports multimodal interaction, enabling the broadcaster to quickly generate preview content that matches the tone of the live broadcast, thereby improving content diversity and expression efficiency.
[0077] For example, the system supports multiple release time configuration modes on the preview release page: by default, it provides multiple preset time slot options based on the live broadcast start time offset, and identifies one of them as recommended; after the user selects any preset option, the system immediately parses its corresponding specific release time and synchronously updates the time information in the preview; at the same time, it provides a custom time entry, which displays a calendar component and a time selection control after activation. After the user completes the date and time selection, the system automatically clears the selected state of the preset option and binds the selected custom time to the current preview; in addition, the page also dynamically generates intelligent recommended release times based on the historical activity data of the streamer's fans. After the user confirms the recommendation, the system uses it as the new release time to overwrite the current value; all operations trigger real-time data updates to ensure that the preview always reflects the latest configuration.
[0078] Furthermore, the cover title display area includes a cover image preview area, a title text input box, and multiple cover style templates; displaying the cover title display area on the live broadcast preview release page includes: displaying a cover image preview area on the live broadcast preview release page, and replacing and displaying the cover image in response to a cover image replacement operation; displaying a title text input box on the live broadcast preview release page, and generating and displaying a recommended title in response to an editing operation of the input box; and displaying multiple cover style templates on the live broadcast preview release page, and updating the cover image based on the target cover style template in response to a selection operation of the target cover style template.
[0079] The cover title display area is an interface module used to centrally present and support adjustments to the cover image and title text.
[0080] The cover image preview area is a visual block that displays the current cover image, usually located at the top or left of the page.
[0081] The title text input box is a single-line text input component used to enter or modify the title of the live broadcast preview.
[0082] The cover style template is a preset visual layout scheme, including fonts, color schemes, graphic layouts and decorative elements, such as styles like "minimalist", "promotional red", and "scene illustration".
[0083] In practical applications, when the system renders the cover title display area on the live broadcast preview page, it simultaneously loads the cover image preview area, the title text input box, and multiple cover style templates. The cover image preview area initially displays a cover image automatically generated by the system based on the broadcast target. The broadcaster can upload a local image or select a new image from the material library by clicking the "Change Cover" button. After receiving the new image, the system immediately replaces the content of the preview area and updates the associated data. The title text input box is initially filled with a recommended title. When the broadcaster edits it, the system captures the input content in real time and triggers title optimization suggestions (such as keyword completion or length prompts) after the input is paused. At the same time, the latest title is synchronized to the preview view. Multiple cover style templates are arranged horizontally in the form of thumbnails. When the broadcaster clicks on any template (such as "Promotional Red"), the system re-renders the cover image according to the layout rules of that template, including adjusting the background color, text position, font style, and decorative graphics, generating a cover that conforms to the new style and refreshing the preview area.
[0084] For the step "Display the cover title display area on the live broadcast preview release page", one option is to render the cover style template by dynamically switching the front-end CSS theme; another option is to have the system call the server-side image compositing interface to regenerate a cover image with watermark or text overlay based on the selected template, which is not limited here.
[0085] In the embodiments of this specification, the cover title display area supports the linkage adjustment of images, text and visual style, enabling broadcasters to quickly produce high-quality covers that meet the platform's aesthetics and user preferences.
[0086] For example, the system integrates image preview, title editing, and style template switching functions in the cover title display area: the initial cover is generated based on the product main image and the default template, the title text can be edited in real time, the system simultaneously verifies the word count and provides prompts; multiple cover style templates are displayed side by side in the form of thumbnails, after the user selects any template, the system immediately re-renders the cover according to the visual rules of the template (including color scheme, font, layout and decorative elements); if the user further uploads a custom image, the system uses the new image as the background, while retaining the text style and component structure of the current template, and dynamically synthesizes a new cover; all operations are completed locally or in real time through a lightweight service, the preview area is refreshed instantly, without the need for page jumps or waiting for loading.
[0087] Furthermore, the live stream preview release page also includes a reservation selection control. This control is used to select the live stream display page from which to add a live stream reservation entry. The reservation selection control includes a first switch control, a second switch control, and a list selection area. The live stream display page includes the streamer's personal homepage, preview content, and historical content associated with the target live stream. Displaying the live stream preview release page includes: displaying the target live stream preview and its corresponding release confirmation control on the live stream preview release page, and displaying the first switch control on the live stream preview release page, where the first switch control is used to display the live stream reservation entry on the streamer's personal homepage; displaying the target live stream preview and its corresponding release confirmation control on the live stream preview release page, and displaying the second switch control on the live stream preview release page, where the second switch control is used to display the live stream reservation entry in the preview content; displaying the target live stream preview and its corresponding release confirmation control on the live stream preview release page, and displaying a list selection area on the live stream preview release page, where the list selection area is used to display historical content. In response to the selection of historical content, the historical content is set as the target display page where the reservation entry can be displayed.
[0088] The reservation selection control is a collection of interactive components used to configure the display area of the live broadcast reservation entry, including a first switch control, a second switch control, and a list selection area.
[0089] The first switch control is a two-state switch that controls whether to display the live broadcast reservation entrance on the streamer's personal homepage.
[0090] The second switch control is a two-state switch that controls whether the live broadcast reservation entrance is displayed on the current preview content page.
[0091] The list selection area is an interactive block used to display and select related historically published content, usually presented in the form of a card list.
[0092] The live stream display page is a front-end page type that can carry the live stream reservation entry, including the streamer's personal homepage, the current preview content page, and the historical content page associated with the target live stream.
[0093] Historical content refers to content or content items previously published by the same broadcaster that have a semantic or identifieral association with the current broadcast target.
[0094] In practical applications, the system displays the live broadcast preview and corresponding confirmation control on the live broadcast preview release page, and also simultaneously renders the reservation selection control. The first switch control is presented as a "Homepage Display [Next Session Reservation]" label. After the broadcaster activates it, the system records that the reservation entry for this live broadcast should be displayed in a prominent position on the broadcaster's personal homepage (such as a top banner or live broadcast card). The second switch control exists as a "Preview Content Display [Next Session Reservation]" label. When activated, the live broadcast reservation entry will be automatically embedded in the currently released preview content page during rendering. The list selection area retrieves historically released content associated with the current broadcast target from the content library. Each item consists of a thumbnail, title text, and release time, forming a card-style entry. The broadcaster can select any historically released content, and the system, in response, marks that content as a "target display page that can display the reservation entry" and injects the reservation component into subsequent visits. The state of all controls is bound to the preview metadata in real time for the server to call during the release and configuration phases.
[0095] For the step "Display live broadcast preview release page", one option is to render the content of the list selection area locally after the front end calls the historical content interface to filter by object identifier; another option is to pre-calculate the associated historical content on the server side and return it along with the page data, which is not limited here.
[0096] In the embodiments of this specification, the appointment selection control enables the broadcaster to authorize multiple types of pages to automatically display appointment entry points with one click, without having to edit historical content one by one, which significantly improves the breadth of appointment coverage and configuration efficiency.
[0097] For example, the system provides multi-dimensional reservation entry configuration capabilities on the preview release page: the first switch control controls whether to embed the reservation entry of the current live broadcast on the broadcaster's personal homepage, and the second switch control controls whether newly released preview content automatically carries the reservation function; at the same time, the list selection area displays the historical release content associated with the current broadcast target, and users can select some of the items; all selected items (including the homepage, new previews and specified historical content) are uniformly marked as the reservation display page for this live broadcast after submission; when viewers visit any marked page later, the system will dynamically inject a consistent live broadcast reservation entry to achieve reservation access across content scenarios, and the entire configuration process is completed within a single page, with status changes reflected in real time.
[0098] Furthermore, the historical published content displayed in the list selection area includes thumbnails, publication time, and historical content titles; after displaying the list selection area on the live broadcast preview release page, it also includes: highlighting the selected historical published content in the list selection area with a check mark; removing the highlighted status of the historical published content from the scheduled display list in response to the unchecking operation of the selected historical published content; and highlighting the unselected historical published content with a check mark in response to the checking operation of the unselected historical published content.
[0099] Historical content refers to content items previously published by the same streamer that are related to the current target live stream, and is used as a potential reservation entry page.
[0100] Thumbnails are small preview images of the cover or main image of historically published content, used to quickly identify the content's theme.
[0101] The release time is the timestamp of the first time the previously released content was publicly launched, such as "2025-12-01".
[0102] The title of historical content is the main title text of historically published content, used to summarize its core information.
[0103] Checkmarks are visual markers used to indicate whether historically published content is selected, such as checkmarks in checkboxes, border highlights, or corner icons.
[0104] In practical applications, when the system renders the list selection area on the live broadcast preview release page, it displays each historical release in the form of a card containing a thumbnail, release time, and historical content title. When the broadcaster selects an unselected historical release (e.g., by clicking a checkbox or card area), the system immediately overlays a checkmark on that card, such as displaying a green checkmark icon in the upper left corner or adding a blue border to the entire card, visually distinguishing it from other unselected items. This content is also added to the internally maintained reservation display list. When the broadcaster deselects a selected historical release, the system removes its checkmark, restores the default style, and removes it from the reservation display list. All status changes are synchronized to the page data model in real time, ensuring that subsequent submissions only include the currently selected historical release as the deployment target for reservation entry.
[0105] For the step "Display historical published content in the list selection area", one option is to dynamically switch the check mark using a front-end CSS class; another option is for the system to re-render the entire list item component after each check operation, which is not limited here.
[0106] In the embodiments described in this specification, the selection status of historically published content is visualized in real time by using a checkmark, which effectively avoids configuration confusion and improves the reliability of batch authorization of multiple contents.
[0107] For example, the system displays historical published content associated with the current live stream in the list selection area in the form of cards. Each item includes a thumbnail, publication time, and title. Initially, all items are unselected. When a user clicks any checkbox, the system immediately overlays a visual checkmark (such as a color block with a checkmark or a highlighted background) on the card, indicating that it has been included in the reservation entry configuration. If the user deselects an item, the system removes the corresponding mark and restores the default style. When finally submitted, only the historical published content that is currently selected is marked as a valid reservation display page, ensuring that the selected content is semantically consistent with the current live stream topic and avoiding irrelevant pages being misassigned to reservation entries.
[0108] Furthermore, the live broadcast preview page also displays a preview area of the reservation configuration results; the method also includes: displaying a simulated user interface in the preview area of the reservation configuration results, wherein the user interface includes a layout diagram of the target live broadcast display page; displaying a simulated location of the live broadcast reservation entrance in the user interface, wherein the simulated location is consistent with the location of the live broadcast reservation entrance in the target live broadcast display page; and refreshing and updating the content in the preview area of the reservation configuration results in real time in response to the modification operation of the reservation selection control in the live broadcast preview page.
[0109] The reservation configuration result preview area is a visualization block used to display the deployment effect of the reservation portal in real time.
[0110] The user interface is a simplified illustration of the target live stream display page that viewers see on their terminal devices.
[0111] The target live stream display page is the type of front-end page that actually carries the live stream reservation entry, including the streamer's personal homepage, the preview content page, and the associated historical content page.
[0112] The simulated location of the live stream reservation entrance is the reservation component location marked as a placeholder, icon, or button on the user interface, and its layout coordinates are consistent with those on the actual page.
[0113] In practical applications, in addition to functional controls, the system renders an independent preview area for reservation configuration results on the live broadcast preview page. This area initially loads a default user interface simulation image, such as a simplified layout of the broadcaster's personal homepage, including an avatar, nickname, follow button, and content flow area. When the broadcaster activates the first switch control via the reservation selection control, the system overlays a simulated "Reserve Live Broadcast" button on the top banner or live broadcast card position of the user interface. When the second switch control is activated, the system switches the user interface to the layout of the preview content page and displays the same simulated reservation entry position below the main text. When a historical post is selected in the list selection area, the system can display the simulated interface of that historical post in a carousel or paginated manner, and render the reservation entry in its corresponding position (such as below the title or above the comment section). All simulated positions strictly follow the platform's actual UI specifications to ensure that the preview is consistent with the actual effect. Whenever the broadcaster performs a modification operation on any reservation selection control (such as switching the switch or changing the selection), the system immediately recalculates the set of display pages that take effect and simultaneously refreshes the user interface and reservation entry position in the reservation configuration result preview area.
[0114] For the step "Display the simulated user interface in the reservation configuration result preview area", one option is to dynamically replace the reservation entry status in the preview area using a static SVG template; another option is to render the component tree of different page types in real time using a lightweight front-end framework, which is not limited here.
[0115] In the embodiments of this specification, the reservation configuration result preview area synchronizes the control status with the simulation interface in real time, enabling the broadcaster to intuitively verify the deployment effect of the reservation entry and reduce rework and adjustments after release.
[0116] For example, the system integrates a real-time reservation configuration preview area into the preview release page, dynamically reflecting the deployment effect of the reservation entry through a simulated interface within the device outline; initially, a simplified layout of the anchor's personal homepage is displayed; when the user enables the homepage reservation switch, the preview interface immediately renders a reservation banner in the corresponding position, with a style consistent with the real client; when the user selects a historically published piece of content, the preview area automatically switches to the page simulation view of that content, and overlays the reservation entry component in its standard interactive area; if the user disables the reservation switch for the preview content, the preview area removes the reservation element of that page or switches back to the view of another selected page; all control state changes trigger an instant update of the preview area without manual refresh, ensuring that the anchor can intuitively verify the position and status of the reservation entry in different display pages.
[0117] Furthermore, the live broadcast preview generation method also includes: displaying a live broadcast plan management page in response to a management operation on a published live broadcast preview; displaying a list of each live broadcast preview associated with the target live broadcast and its corresponding interaction data on the live broadcast plan management page; and configuring an enhanced distribution strategy for the specific live broadcast preview in response to a promotion operation triggered on the list for the specific live broadcast preview.
[0118] A published live stream announcement refers to a live stream announcement content entity that has been released, triggered at the designated time, and is publicly visible on the platform.
[0119] Management operations are commands initiated by the broadcaster on the client to view or operate published announcements, such as clicking the "My Live Schedule" entry.
[0120] The live stream schedule management page is a backend interface used to centrally display and manage all related live stream announcements.
[0121] Interactive data refers to the behavioral feedback metrics generated by viewers in response to live stream announcements, including but not limited to impressions, click-through rates, number of reservations, and number of shares.
[0122] Promotional actions are enhanced distribution requests initiated by the broadcaster for specific live stream previews, such as clicking the "Increase Recommendation" button.
[0123] Enhanced distribution strategies are additional traffic support rules configured by the system for specific live broadcast previews, such as increasing the weight of the information flow, adding it to the hot pool, and extending the exposure period.
[0124] In practical applications, the system responds to the broadcaster's management operations on published live stream announcements (such as entering the "Live Stream Plan" menu), loading and displaying the live stream plan management page. This page presents all live stream announcements associated with the target live stream in a list format. Each announcement item includes a cover thumbnail, title text, publication time, and corresponding interaction data (such as "Exposure: 12,500 | Clicks: 860 | Reservations: 324"). The list is sorted by publication time or interaction effect and supports filtering and searching. When the broadcaster performs a promotion operation on a specific live stream announcement in the list (such as clicking the "Promote" button on its right), the system receives the instruction and configures an enhanced distribution strategy for the announcement. This includes increasing its initial weight in the recommendation algorithm, adding it to the platform's short-term popular content pool, or extending its effective exposure time in the information flow. This strategy is applied in real time by the server-side distribution engine and does not require re-editing or republishing the announcement content.
[0125] For the step "Configure an enhanced distribution strategy for a specific live broadcast preview", one option is for the system to directly modify the priority field of the preview in the content distribution database; another option is to write the preview ID into the high-priority task queue and have the scheduling service periodically inject additional traffic, which is not limited here.
[0126] In the embodiments of this specification, the preview content is visualized and tracked and promoted with one click through the live broadcast plan management page, enabling the broadcaster to dynamically optimize the allocation of distribution resources based on real interaction data.
[0127] For example, the system displays published previews associated with the target live stream in a list format on the live stream plan management page. Each item includes a content identifier and key interaction data (such as impressions and number of reservations). The streamer can select high-potential previews based on data performance and trigger promotion operations. After the system responds, a confirmation prompt pops up. Once the user confirms, the corresponding preview is bound to an enhanced distribution strategy (such as increasing the weight of the information flow, adding it to the regional recommendation pool, or extending the exposure period). This strategy takes effect in real time on the server side without modifying the preview content itself. Subsequently, the distribution system dynamically adjusts traffic allocation according to the new strategy to achieve precise promotion of high-quality previews. The entire process is completed through the management interface, making the operation lightweight and the effect traceable.
[0128] Furthermore, the live broadcast preview release page also includes a live broadcast preview area, which is used to display preview content of at least one live broadcast preview in sequence or side by side; after displaying the live broadcast preview release page, it also includes: in response to a trigger operation on any preview content in the live broadcast preview preview area, loading and displaying the corresponding live broadcast preview in the editing area of the live broadcast preview release page for editing.
[0129] The live stream preview area is a section of the interface used to centrally display one or more thumbnail views of live stream previews.
[0130] The preview content is a simplified presentation of the live stream announcement, including a cover image, title text, and a partial summary of the main content.
[0131] The trigger action is the interactive behavior performed by the broadcaster on the preview content, such as clicking, long-pressing, or selecting.
[0132] The editing area is used to input and display detailed information about the live broadcast preview, including a title input box, a content text area, and an image selection area.
[0133] In practical applications, after displaying the live broadcast preview release page, the system renders a live broadcast preview preview area on one side or top of the page. This area displays preview content of at least one live broadcast preview sequentially or side-by-side in a horizontal sliding card, vertical list, or grid layout. Each preview content includes a cover image, title text, and a brief description, forming a recognizable content snapshot. When the broadcaster performs a trigger operation on any preview content (such as clicking the card), the system immediately recognizes the corresponding complete live broadcast preview data and loads the preview's title, body text, associated images, and release time into the editing area on the page. The editing area is then updated to the editable state of the currently selected preview, allowing the broadcaster to directly modify the title, adjust the text, or change the accompanying images. All changes only apply to that preview instance and do not affect other unselected preview content. The preview area remains visible at all times, supporting broadcasters to quickly switch between and iterate on multiple previews.
[0134] For the step "triggering an operation for any preview content in the live broadcast preview area", one option is to capture the click coordinates through the front-end event listener and map them to the preview ID; another option is to bind a unique identifier to each preview content and pass it to the editing module through routing parameters when clicked, which is not limited here.
[0135] In the embodiments of this specification, the linkage mechanism between the live broadcast preview area and the editing area enables the broadcaster to quickly switch between multiple versions of content and make precise edits, significantly improving the flexibility and efficiency of the preview configuration.
[0136] For example, the system sets up a preview area on the preview release page, displaying multiple automatically generated live broadcast previews in the form of horizontally scrollable cards. Each card includes a cover thumbnail and a title summary. When a user clicks on any preview card, the editing area on the page immediately loads the complete content of that preview (including title, body text, and related media materials), which can be directly modified. After saving, the data of the selected preview is updated synchronously. When switching to other preview cards, the editing area is automatically replaced with the corresponding content, realizing seamless switching and comparison editing between multiple versions. The preview area remains visible at all times, ensuring that users can efficiently complete content evaluation, adjustment, and confirmation in the same view without having to jump or reload the page.
[0137] Furthermore, at least one live broadcast announcement includes the main content to be released, a set of media materials associated with the target audience, and a release status indicator.
[0138] The main content to be released consists of the core text information presented to the audience in the live broadcast preview, including the title, pre-broadcast text, hashtags, and structured descriptions, which are used to convey the theme and value of the live broadcast.
[0139] The media material collection is a set of visual or multimedia resources associated with the target of the broadcast, including cover images, main product images, scene illustrations, video clips, etc., used to enhance the visual appeal of the trailer.
[0140] The release status identifier is a status label used to mark the current stage of the live broadcast announcement process, such as "not released", "scheduled", "released", "cancelled", etc.
[0141] In practical applications, when generating at least one live broadcast preview, the system constructs a structured data object for each preview. This object first contains the main content, synthesized by the intelligent generation engine based on the attributes and user characteristics of the preview object, covering the title text and body paragraphs. Secondly, it contains a set of media materials, in which the system extracts original materials (such as a list of product main image URLs) from the preview object and combines them with derivative images (such as composite images and cropped images) needed to generate the cover. Finally, it contains a release status identifier, initially set to "not released", which is automatically updated to "scheduled" or "released" based on the broadcaster's actions or scheduling tasks. These three components together constitute a complete live broadcast preview entity for front-end display, editing, previewing, and server-side scheduling. The system ensures that the materials of any preview are semantically consistent with its main content, and the status identifier reflects its lifecycle stage in real time.
[0142] Step 104: In response to identifying a target live stream preview in at least one live stream preview, publish the target live stream preview based on the publication time, wherein the display page of the target live stream preview includes the live stream reservation entry for the target live stream.
[0143] The target live stream preview is a preview content entity selected by the host from at least one automatically generated live stream preview for official release. For example, the host selects "100 Yuan Goodies Special" from three previews: "Scenario", "Price", and "Function" as the final release version.
[0144] The release time is the time when the preview content specified by the broadcaster through the release control goes live, such as 18:00 on December 24, 2025.
[0145] The display page is the front-end interface presented to the audience on the platform for the target live broadcast preview, such as the content details page, information flow card, or search results page.
[0146] The live stream reservation entry is an interactive component embedded in the display page, allowing viewers to reserve and watch the target live stream in advance, such as a "Reserve Live Stream" button or a countdown bar.
[0147] In practical applications, when the system detects that a broadcaster confirms a broadcast announcement on the live broadcast announcement page (such as clicking "Use this announcement" or checking the box and submitting), it identifies the announcement as the target live broadcast announcement. The system then reads the release time associated with the announcement and submits the content data of the target live broadcast announcement (including cover, title, text, and associated products) to the content distribution task queue. When the system clock reaches the release time, it automatically publishes the target live broadcast announcement to the platform content library and generates the corresponding display page. During the generation of the display page, the system simultaneously injects the live broadcast reservation entry component. This component is initialized based on the target live broadcast start time, live broadcast room ID, and other metadata, ensuring that viewers can directly see and operate the reservation function when visiting the page. The entire process does not require the broadcaster to configure a reservation link or create an activity page separately, achieving seamless integration of announcements and reservations.
[0148] For the step "Publish the target live broadcast preview based on the publication time", one option is: the system writes the preview content and publication time into the scheduled task scheduler, and the backend service triggers the publication interface at the specified time; another option is: the frontend immediately calls the publication interface when the broadcaster confirms and temporarily saves the content as a draft, and the server automatically converts it to public status according to the publication time. This is not limited here.
[0149] For example, after the set release time of the target live broadcast announcement arrives, the system automatically delivers it to the information stream in the form of structured content and generates a unique display page. When the page is rendered, the reservation entry component is dynamically injected based on the associated live broadcast metadata (such as broadcast time and live room ID), which is usually located below the main text or in the cover area. The reservation entry is interactive by default, and viewers can complete the reservation by clicking it. The system simultaneously establishes the reservation relationship between the user and the live broadcast session and triggers a reminder when the broadcast starts. The entire process does not require the broadcaster to manually configure the reservation link or create a separate activity page. The reservation function is automatically activated and takes effect when the announcement content is released.
[0150] Furthermore, in response to identifying a target live broadcast preview in at least one live broadcast preview, the method includes: in response to a batch selection operation of multiple previews in at least one live broadcast preview on the live broadcast preview publishing page, identifying the selected multiple previews as the target live broadcast preview; or, in response to a selection operation of a single live broadcast preview and subsequent content editing operation, identifying the edited preview as the target live broadcast preview.
[0151] A target live stream preview is a live stream preview that will be used for official release after being confirmed by the streamer, and can be one or more.
[0152] Batch selection is an interactive behavior that allows broadcasters to select multiple previews simultaneously on the live broadcast preview release page, such as checking checkboxes or using multi-select gestures.
[0153] The selected action is a confirmation click performed by the broadcaster on a single trailer, such as the "Use this trailer" button.
[0154] Content editing refers to the actions taken by the broadcaster to modify the title, text, or images of a preview.
[0155] In practical applications, the system responds to the broadcaster's actions on the live broadcast preview publishing page to determine whether the target live broadcast preview has been determined: When the broadcaster performs a batch selection operation, such as checking the checkboxes of two or more preview cards in the preview area and clicking the "Batch Publish" button, the system marks all selected previews as target live broadcast previews and binds them to a publishing time or a unified scheduling strategy; When the broadcaster performs a selection operation on a single live broadcast preview (such as clicking "Edit and Use"), the system loads the preview into the editing area, and the broadcaster then performs content editing operations (such as modifying the title, adjusting the text, or changing the image). After saving or submitting, the system determines the edited preview as the target live broadcast preview; the two paths are mutually exclusive but coexist on the same page, and the system dynamically switches the processing logic according to the operation type to ensure that the determined target live broadcast preview reflects both the original generated result and accommodates human optimization intentions.
[0156] For the step "in response to determine the target live broadcast preview in at least one live broadcast preview", one possible approach is to achieve batch selection by maintaining a list of selected IDs on the front end and passing it to the server when submitting; another possible approach is to generate a new version of the preview and replace the original object each time it is saved in single edit mode, which is not limited here.
[0157] In the embodiments of this specification, by supporting both batch selection and single editing and confirmation, the broadcaster can choose the configuration path of efficient distribution or multi-round optimization as needed, thereby improving the flexibility and applicability of the preview release.
[0158] For example, the system supports two target preview determination modes on the preview release page: one is the batch selection mode, where users can select multiple automatically generated previews and trigger a batch release operation. The system will uniformly mark the selected options as target live previews and supports configuring the release time for each preview independently; the other is the single-preview editing and confirmation mode, where users perform editing operations on a preview (such as modifying the title or changing the accompanying image), save it, and then confirm the updated version as the only target preview. The original version will no longer participate in the release. The two modes coexist on the same interface. The system dynamically identifies the intent based on the user's interaction path (batch selection vs. single-preview editing + confirmation) and generates the corresponding set of target previews, realizing flexible and efficient multi-scenario release strategy configuration.
[0159] See Figure 2 , Figure 2This is a flowchart of another live broadcast preview generation method provided in one embodiment of this specification, specifically including the following steps 202-208.
[0160] Step 202: In response to the host's operation of determining the backup target for the target live broadcast, obtain the backup target.
[0161] The backup broadcast object is a core structured data set used to drive the generation of live broadcast previews. It includes object identifiers, material information, attribute tags and contextual features associated with the target live broadcast, such as product ID, main image URL, core selling point text, and applicable scenario classification.
[0162] The process of determining the backup broadcast targets for the target live stream on the broadcaster's end involves the broadcaster selecting or confirming the content related to the live stream on the client interface, such as clicking the "Complete Product Selection" button, submitting the product list, or saving the backup broadcast plan.
[0163] In practical applications, the system identifies the backup broadcast object that has completed the target live broadcast by listening to event signals or interface calls sent by the broadcaster. This signal can be represented as an HTTP request, a message queue message, or an internal event bus notification. After receiving the signal, the server immediately extracts the complete backup broadcast object data from the request body, message payload, or associated session context. The backup broadcast object is usually encapsulated in JSON or Protobuf format, containing one or more object entries, each carrying a unique identifier and associated attributes. The server performs legality verification on the obtained data, including field integrity checks, identifier validity verification, and permission matching confirmation, to ensure that the backup broadcast object belongs to the current broadcaster and has not been tampered with. After the verification is successful, the system persists the backup broadcast object to the task context or cache for subsequent generation modules to call.
[0164] For the step "obtain the backup object", one option is that the server receives the backup object data packet submitted by the broadcaster through a RESTful API; another option is that the server subscribes to the "backup completion" event topic in the message middleware and parses the backup object from the event payload. This is not limited here.
[0165] For example, in the server-side processing flow of a live streaming platform, after the broadcaster completes the pre-broadcast operation on the client and submits confirmation, the client sends a structured request containing a list of pre-broadcast objects to the server. After receiving the request, the server gateway routes it to the preview generation service. This service performs a validity check on each pre-broadcast object in the request body, including verifying whether the object identifier belongs to the authorized resource of the current broadcaster and checking whether the necessary fields (such as ID, title, material address, etc.) are complete. After the verification is passed, the complete set of pre-broadcast objects is stored in the cache system with a unique task key (such as rehearsal:live_{date}_{id}) and the preview generation process in the asynchronous task queue is triggered, providing structured input for subsequent content construction.
[0166] Step 204: Generate a live broadcast schedule based on the backup broadcast objects.
[0167] The backup broadcast object is a structured data set containing objects associated with the target live broadcast, such as product identifiers, main images, selling point text, scene tags, and user profile features.
[0168] A live stream preview is a complete preview content entity automatically generated by the system and available for publication. It includes a cover image, title text, pre-event copy, and related object information, such as a preview for a "camping equipment special".
[0169] In practical applications, after acquiring the objects to be broadcast, the system first parses the object identifiers and attribute fields to extract core materials such as the main image URL, selling point keywords, and category tags. Then, it calls the multi-source data fusion module to construct a content generation feature vector by combining the object's historical user interaction characteristics (such as the age distribution and regional preferences of high-click audiences) and the platform's current popular keyword library. Based on this feature vector, the intelligent content generation engine executes cover generation, title generation, and pre-broadcast copy generation tasks respectively: the cover generation module uses an image processing model to crop, optimize the color scheme, and overlay text on the main image, outputting a cover image adapted to the platform size; the title generation module uses a natural language processing model to combine scene words, selling point words, and hot words to generate multiple candidate titles; the pre-broadcast copy generation module, based on preset theme categories (such as functional, price, and scene categories), logically organizes the selling points of multiple objects into coherent paragraphs and matches them with graphic and text layout templates; finally, the system integrates the cover, title, copy, and associated object IDs into one or more structured live broadcast preview data packages for subsequent release scheduling.
[0170] For the step "Generate live broadcast preview based on the backup broadcast object", one option is: the server calls the locally deployed generation model to synchronously complete the content construction; another option is: push the backup broadcast object to the asynchronous task queue, which is processed by the dedicated content generation service cluster and the results are written back. This is not limited here.
[0171] For example, in a server-side task on a live streaming platform, the system receives a list of three outdoor products for broadcast: a tent, a sleeping bag, and a stove, all tagged with "camping," "lightweight," and "windproof." The system calls the user feature interface to obtain profiles of users who have interacted with these products highly in the past 30 days, finding that they are mainly concentrated in the 25-35 age group and in first-tier and new first-tier cities. At the same time, the system queries the platform's hot keyword library to obtain rising keywords such as "camping ceiling" and "lightweight travel." The cover generation module uses the tent image as a base, overlays the text "camping ceiling," and adjusts the color tone using the Morandi color scheme favored by users. The title generation module outputs "Lightweight camping three-piece set! Windproof and lightweight, easy for beginners to use." The copywriting generation module organizes the content according to the "scenario-function-price" structure, describing how the three products meet the needs of solo camping. Finally, a complete live stream preview is generated, including the cover image URL, title, body text, and three product IDs, and stored in the preview content pool to await the release time.
[0172] Furthermore, based on the backup broadcast objects, a live broadcast preview is generated, including: extracting object materials and user feature data from the backup broadcast objects; generating scenario-based description content based on the object materials and user feature data; matching cover materials and titles to the scenario-based description content according to scenario classification rules; and integrating the scenario-based description content, cover materials, and titles into a live broadcast preview.
[0173] The target material refers to the structured media or text resources contained in the target material that are directly related to the live broadcast content, such as the main product image, core selling points, functional parameters, and target audience tags.
[0174] User characteristic data refers to user behavior or profile information related to the historical interactions of the target audience, such as the age distribution, regional preferences, usage scenario tags, or high-interaction periods of typical users.
[0175] Contextualized descriptions are pre-launch copy generated by integrating object materials and user characteristics, and have specific life scenarios, such as "During winter at home, this humidifier makes the air more humid and comfortable."
[0176] The scene classification rules are preset content organization logics used to map live streaming themes to specific life or consumption scenarios, such as categories like "home life", "outdoor camping", "holiday gifts", and "good things under 100 yuan".
[0177] The cover material consists of visual resources used to create the cover of the live broadcast announcement, including background images, decorative elements, color schemes, and text layout templates.
[0178] The title is a short, attractive statement summarizing the theme of the live stream, usually generated from a combination of keywords.
[0179] In practical applications, the system first parses and extracts object materials from the acquired pre-broadcast objects, including product image URLs, selling point text, and attribute tags. Simultaneously, it calls the user profiling service to obtain user characteristic data associated with the object, such as the geographic concentration of highly interactive users in first-tier and new first-tier cities within the past 30 days, their age range of 25-35, and their preference for tags like "practical" and "aesthetically pleasing." Subsequently, the intelligent content generation engine semantically fuses the object materials with the user characteristic data to generate one or more scenario-based descriptive content segments, such as combining "portable coffee machine" with the scenario of "commuting to work." The system outputs the message "Can you still have freshly ground coffee while rushing to catch the subway in the morning? This portable coffee machine makes a cup in 30 seconds." Next, the system categorizes the generated content according to preset scenario classification rules. If it's identified as a "convenient commuting" scenario, it matches the corresponding cover image (e.g., subway background + image of someone holding a coffee) and title template (e.g., "Essential for commuters! XX gadget lets you XX"). Finally, the system integrates the scenario-based description, the matched cover image, and the generated title into a complete live broadcast preview data package, including the cover image path, title text, body content, and associated object ID, for subsequent release scheduling.
[0180] For the step "Generate contextualized descriptive content based on object materials and user feature data", one possible approach is to generate copy by inputting a pre-trained language model and fusing feature vectors; another possible approach is to retrieve the most matching sentence from the template library and fill in dynamic parameters, which is not limited here.
[0181] In the embodiments described in this specification, the process of generating live broadcast previews deeply integrates object attributes, user preferences, and life scenarios, making the content more immersive and platform-adaptable.
[0182] For example, in a server-side task on a live streaming platform, the pre-broadcast items include three products: a "folding electric kettle," a "portable coffee machine," and a "travel storage bag." The system extracts their selling points as "1L capacity," "30-second rapid heating," and "food-grade silicone," and obtains user characteristics showing that the main audience is working professionals aged 25-35 who frequently travel for work. Based on this, the generation engine outputs a scenario-based description: "No more need to drink hot water when staying in a hotel during a business trip? This folding electric kettle fits easily in your backpack and boils a cup of water in 30 seconds." The system categorizes it into the "Travel Essentials" scenario based on the keywords "business trip" and "portable." It then matches the cover material for this scenario—an airport background + suitcase elements + blue main color scheme—and generates the title "A boon for business travelers! 3 small, high-energy gadgets." Finally, the cover image, title, and text are integrated into a complete live stream preview and stored in the content pool, awaiting the release time.
[0183] Step 206: Obtain the release time determined by the broadcaster for the target live broadcast preview.
[0184] The target live stream preview is a specific preview content entity selected by the streamer from multiple automatically generated previews for release, such as a preview on the theme of "Good Home Goods for 100 Yuan".
[0185] The release time is the time when the target live broadcast announcement specified by the broadcaster through the client interface is publicly launched on the platform, such as 18:00 on December 24, 2025.
[0186] In practical applications, after the broadcaster selects the target live broadcast preview on the broadcaster's end, the system monitors their actions on the release confirmation control. When the broadcaster sets a specific release time through the calendar component, time slot switch, or time input box and submits a confirmation command, the client encapsulates the release time along with the unique identifier of the target live broadcast preview and sends it to the server via a network request. After receiving the request, the server parses the timestamp field and verifies its format validity (e.g., whether it conforms to the ISO 8601 standard), logical rationality (e.g., whether it is later than the current time and earlier than the live broadcast start time), and permission consistency (e.g., whether the preview belongs to the current broadcaster). After successful verification, the system establishes a binding relationship between the release time and the target live broadcast preview ID and stores it in the task scheduling database or cache as the triggering basis for subsequent scheduled release tasks. This release time information is also recorded in the preview metadata for auditing and status tracking.
[0187] For the step "obtain the release time determined by the broadcaster for the target live broadcast preview", one possible approach is for the server to receive the release time parameter in real time through a synchronous API interface; another possible approach is for the client to write the release time to a message queue, and the server to obtain the release time asynchronously by consuming the event stream. This approach is not limited here.
[0188] For example, in the server-side processing flow of the live streaming platform, when the broadcaster selects a target preview and sets the release time on the preview release page, the client encapsulates the preview ID and the specified release time into a structured request and submits it to the server through a scheduling interface (such as PUT / api / v1 / preview / schedule); the gateway routes the request to the preview scheduling service; this service parses the release time field, verifies whether it is a future time, whether it is earlier than the start time of the corresponding live stream, and verifies whether the preview ID belongs to the current broadcaster; after the verification is successful, the scheduling record is persisted to the database, including the preview ID, release time and status (such as "scheduled"); the background scheduled task scans the scheduling table at a fixed frequency (such as every minute), and once it detects that the current time matches the release time of a certain record, it triggers the release process of the corresponding preview and completes the content launch.
[0189] Step 208: Publish the target live stream preview based on the release time, and configure the live stream reservation entry on the display page of the target live stream preview.
[0190] The target live stream preview is a complete preview content entity with a selected release time, including cover, title, text and related object information.
[0191] The display page is the interface that presents the target live stream preview to the audience on the platform's front end, such as the content details page, information flow card, or search results item.
[0192] The live stream reservation entry is an interactive component embedded in the display page, used to guide viewers to reserve the target live stream in advance, such as a "Reserve Live Stream" button or a countdown bar.
[0193] In practical applications, the system automatically triggers a content publishing task when the target live stream announcement's release time arrives. This task first writes the structured data of the target live stream announcement (including cover image URL, title text, body content, and a list of associated objects) into the platform's content library and generates a unique display page identifier. Subsequently, the system calls the page rendering service to dynamically inject the live stream reservation entry component when building the front-end template of the display page. The initialization parameters of this component come from the target live stream's metadata, including the start time, live stream ID, and streamer identifier, ensuring that the reservation behavior can be accurately associated with the corresponding session. The location, style, and interaction logic of the reservation entry are uniformly controlled by the platform and are usually placed below the announcement text or in the cover image overlay area. After publication, the display page is visible to the audience, and any user who visits the page can directly operate the reservation entry to complete the reservation without additional redirection or configuration.
[0194] For the step "Publish the target live broadcast preview based on the publication time and configure the live broadcast reservation entry in the display page of the target live broadcast preview", one possible approach is: the server calls the page template engine at the same time as publishing the content and embeds the reservation entry as a fixed block into the HTML structure; another possible approach is: after the content is published, the front-end framework dynamically mounts the reservation component at runtime based on the page metadata, which is not limited here.
[0195] For example, in the server-side scheduling process of a content platform, the system executes a publishing task on time at 10:00 on December 25, 2025, writing the "Winter Skincare List" preview with ID prev_98765 into the content database and generating the display page URL https: / / example.com / note / 98765; simultaneously, the system obtains the start time of the live stream from the live streaming metadata service as 20:00 on December 26, 2025, and the live stream room ID as live_abc123; when constructing the response data for the note / 98765 page, the server adds the fields "reservation_enabled": true, "live_start_time": "2025-12-26T20:00:00+08:00", and "live_id": true to the JSON payload. "live_abc123"; After receiving this data, the front-end rendering engine automatically renders a blue "Reserve Live Stream" button below the main text area, with the button text displaying "Live Stream starts at 20:00 on December 26th"; When the user clicks the button, the front-end calls the reservation interface to submit the live_id and complete the reservation relationship binding; The whole process does not require the server to create a separate reservation activity page, and the reservation capability takes effect naturally with the release of the announcement.
[0196] Furthermore, based on the backup broadcast objects, a live broadcast preview is generated, including: extracting object materials and user feature data from the backup broadcast objects; generating scenario-based description content based on the object materials and user feature data; matching cover materials and titles to the scenario-based description content according to scenario classification rules; and integrating the scenario-based description content, cover materials, and titles into a live broadcast preview.
[0197] The object material refers to the basic resources contained in the prepared broadcast object for content generation, including structured information such as the main product image, core selling point text, functional parameters, and target audience tags.
[0198] User characteristic data is a profile of user groups that have historical interactions with the target audience, such as the age range, geographical distribution, preferred keywords, or high-frequency usage scenarios of typical users.
[0199] Contextualized descriptions are pre-launch copy generated by combining object characteristics with user life situations. They have a clear usage background and emotional guidance, such as "It's the perfect time for weekend camping, and this lightweight tent opens in 3 seconds."
[0200] The scene classification rules are a pre-defined content organization logic system used to map live streaming themes to specific life or consumption scene categories, such as "home life", "outdoor sports", "holiday gifts", and "good things under 100 yuan".
[0201] The cover material is a collection of visual elements that make up the live broadcast preview cover, including background images, color schemes, decorative graphics, and text layout templates.
[0202] The title is a short and attractive statement that summarizes the core value of live streaming, usually composed of scene words, selling point words and platform hot words.
[0203] In practical applications, the system first parses and extracts object materials from the prepared broadcast objects, obtaining product images, selling point descriptions, and attribute tags. Simultaneously, it calls the user profiling interface to obtain user characteristic data associated with the object, such as high-interaction users being mainly concentrated in the 25-35 age group and preferring tags like "practical," "aesthetically pleasing," and "portable." Subsequently, the content generation module semantically fuses the object materials with user characteristics to generate one or more scenario-based descriptive content pieces with everyday life contexts. For example, combining "portable coffee machine" with "commuting scenario" to output, "Can you even have freshly ground coffee while rushing to catch the subway in the morning? This..." The system first introduces a portable coffee maker that dispenses coffee in 30 seconds. Then, it categorizes the generated content according to preset scenario classification rules. If the scenario is identified as "Travel Convenience," it matches corresponding cover materials (such as airport backgrounds, suitcase icons, and a blue color scheme) and title templates (such as "Essential for Business Travelers! XX Gadget Makes You XX") from the material library and generates a complete title. Finally, the system integrates the scenario-based description, the matched cover materials, and the title into a structured live stream preview, including the cover image path, title text, body content, and associated object identifiers, forming a publishable preview entity.
[0204] For the step "matching cover materials and titles for scenario-based descriptions based on scenario classification rules", one possible approach is for the system to match scenario tags and material library indexes through a rule engine; another possible approach is to use vector similarity calculation to embed the generated content into a vector space and then retrieve the most similar cover and title templates, which is not limited here.
[0205] In the embodiments described in this specification, the process of generating live broadcast previews organically integrates object attributes, user preferences, and life scenarios, making the content more relevant to users' real needs and enhancing their willingness to click.
[0206] For example, in the live broadcast preview generation process, the system extracts the core selling points of the products based on the target audience and performs semantic fusion with associated user feature data (such as typical user profiles or usage scenarios) to generate scenario-based descriptive copy with a life context. Subsequently, the copy is categorized according to preset scenario classification rules to identify its content scenario (such as "travel essentials"). Based on this, the system matches the corresponding cover visual template (such as airport background, color scheme) and title generation strategy from the material library to produce a structured title. Finally, the generated title, scenario-based text and matched cover material are integrated into a complete live broadcast preview data object, containing all necessary fields, for subsequent release scheduling and reservation entry configuration.
[0207] Furthermore, based on user interaction data and platform content distribution patterns, at least one recommended release period is calculated, including: dividing user interaction data into time periods to obtain corresponding interaction data indicators within each time period; identifying time periods where the interaction data indicators exceed a preset threshold and determining them as candidate interaction periods; comparing the candidate interaction periods with time periods exceeding a preset distribution indicator in the platform content distribution patterns to obtain overlapping time periods; and matching the overlapping time periods with a preset set of conflicting time periods to exclude time periods included in the preset set of conflicting time periods from the overlapping time periods, thereby obtaining at least one recommended release period.
[0208] User interaction data is a record of historical viewer behavior in response to the streamer's content, including timestamps of interactive events such as clicks, likes, comments, and reservations.
[0209] The content distribution pattern of a platform refers to the intensity of content recommendation or the characteristics of traffic distribution in different time periods within a 24-hour period. It is usually quantified by distribution indicators (such as information flow exposure and recommendation pool capacity).
[0210] Interaction data metrics are statistical values that measure user activity levels over a specific period of time, such as the average number of interactions or interaction rate per unit of time.
[0211] The preset threshold is a baseline value used to filter high-activity periods, and is set by the system based on historical averages or business objectives.
[0212] Candidate interaction periods are the time intervals during which interaction data indicators exceed preset thresholds, such as "19:00–21:00".
[0213] The preset distribution metric is a threshold used to identify high-traffic periods in the platform's content distribution rules, such as the recommendation pool capacity being greater than 120% of the daily average during a certain period.
[0214] The overlapping period is the intersection of the candidate interaction period and the platform's high distribution period on the timeline.
[0215] The preset conflict time period set is a list of time periods that need to be actively avoided, which usually includes the time periods when top live streamers in the same category have recently released a large amount of content.
[0216] The recommended release time slot is the optimized time window that is suitable for releasing live broadcast announcements, after being filtered from multiple dimensions.
[0217] In practical applications, the system first divides user interaction data into time periods at hourly or half-hourly granularity, and calculates interaction data metrics within each time period, such as the average number of appointments or click-through rate per hour. Then, it identifies time periods where the interaction data metrics exceed preset thresholds and marks them as candidate interaction periods. Next, the system obtains platform content distribution pattern data, extracts high-traffic periods where distribution metrics exceed preset distribution metrics, and compares the candidate interaction periods with these high-traffic periods on a timeline, calculating the overlap to form overlapping periods. Then, the system loads a preset set of conflicting time periods (e.g., "20:00–21:00" concentratedly posted by major influencers in the same category within the past 7 days), matches the overlapping periods with this set, and eliminates all conflicting time periods that overlap. Finally, the remaining non-conflicting overlapping time periods are determined as at least one recommended release time period for broadcasters to select on the preview release page.
[0218] For the step "comparing the candidate interaction time period with the time period exceeding the preset distribution index in the platform's content distribution pattern", one possible approach is to calculate the overlapping part using a time interval intersection algorithm; another possible approach is to convert the two sets of time periods into Boolean time vectors and then perform a logical AND operation, which is not limited here.
[0219] In the embodiments of this specification, the calculation of the recommended release time period takes into account three factors: user activity, platform traffic dividends, and competitor avoidance, which effectively improves the initial exposure quality of the preview content.
[0220] For example, in a server-side task of a live streaming platform, the system analyzes the interaction data of the streamer over the past 30 days and finds that the average reservation rates for the two time slots "18:00–20:00" and "21:00–22:00" are 8.2% and 7.5% respectively, both exceeding the preset threshold of 6.0%, and are marked as candidate interaction time slots. At the same time, the platform's distribution pattern shows that "19:00–21:30" is the high-traffic window of the day, with a distribution index reaching 130% of the daily average. After comparing the two sets of time slots, the overlapping time slots are "19:00–20:00" and "21:00–21:30". The system further queries the preset conflict time slot set and finds that "21:00–21:30" has been used intensively by three top streamers in the same category in the past 3 days, so it is excluded. Finally, the system outputs the unique recommended release time slot "19:00–20:00" and presents it to the streamer in the form of "Recommended: 19:30" on the preview release page.
[0221] Furthermore, before configuring the live stream reservation entry on the target live stream preview display page, the process also includes: retrieving historical published content containing the object identifier from the content library based on the object identifier of the backup broadcast object; generating a display page containing the historical published content and sending the display page to the broadcaster; receiving the selection results returned by the broadcaster based on the display page, wherein the selection results indicate the historical published content for which the live stream reservation entry needs to be added.
[0222] The object identifier is a structured key-value pair used to uniquely identify the object to be broadcast, such as a product ID, content tag, or category code.
[0223] Historical published content refers to previously published content, videos, or text / image content items on the platform that contain the object's identifier.
[0224] The display page is a front-end interface used to present selectable historical content to the broadcaster, and it is usually organized in the form of lists or cards.
[0225] The selection result is the instruction data returned by the broadcaster after checking or confirming on the display page, clearly indicating which historically published content needs to be embedded in the live broadcast reservation portal.
[0226] In practical applications, before configuring the live stream reservation entry for the target live stream preview, the system first extracts the object identifier (such as product ID "prod_88765") from the backup broadcast object; then, it performs a search task in the platform's content library to filter out all historical content published by the same broadcaster whose metadata contains the object identifier; the system sorts the search results in reverse chronological order of publication time or by interaction popularity, generates a display page containing thumbnails, titles, publication time, and object association identifiers, and sends it to the broadcaster's client through an interface or message channel; after the broadcaster loads the page, they can browse and select one or more of the content as the page to carry the reservation entry; after the broadcaster completes the selection, the client submits the selection result (such as a list of selected content IDs) back to the server; the system receives the selection result and determines accordingly which historical content display pages need to be injected with the live stream reservation entry.
[0227] For the step "Based on the object identifier of the backup broadcast object, retrieve the historical content published by the broadcaster that contains the object identifier in the content library", one possible approach is to perform an exact match query through the database index field (such as the object_ids array); another possible approach is to use a full-text search engine to perform semantic matching on the content text or tags, which is not limited here.
[0228] In the embodiments of this specification, by introducing a mechanism for the selection and confirmation of historical content by the broadcaster, irrelevant content is prevented from being misassigned to the reservation entry, thus ensuring the relevance of the reservation scenario and the consistency of user experience.
[0229] For example, in the server-side process of the live streaming platform, before configuring the reservation entry, the system retrieves historical content published by the streamer within a specified time range that contains the same identifier based on the object identifier in the backup broadcast object from the content library; generates a display page in the form of a structured card list of the matching results and pushes it to the streamer's client; after browsing on the client, the streamer can select some highly relevant content for confirmation; the client submits the selected content ID list as the selection result back to the server; the server dynamically injects the live streaming reservation entry into the corresponding display page only for these selected historical published content, thereby ensuring that the reservation touchpoint accurately covers content strongly related to the current live streaming topic and avoids interference from irrelevant pages.
[0230] One embodiment of this specification describes a live stream preview publishing page that, after the target live stream is determined, displays at least one automatically generated live stream preview based on the target stream and a corresponding publishing confirmation control. This allows users to confirm the preview content and set the publishing time on the same interface. In response to selecting a target live stream preview, the system automatically publishes the preview according to the set publishing time, and the display page naturally includes a live stream reservation entry pointing to the target live stream. This achieves one-click generation and publishing from the target stream to the reservable live stream preview, reducing operation jumps and manual configuration steps, ensuring consistency between the preview content and the live stream subject, and directly connecting the preview display and user reservation path, improving live stream preparation efficiency and the continuity of the user conversion process.
[0231] The following is in conjunction with the appendix Figure 3 Taking the application of the live broadcast preview method provided in this specification in live broadcast traffic generation on a content publishing platform as an example, the live broadcast preview method will be further explained. Specifically, Figure 3 The present specification illustrates a flowchart of a live broadcast preview generation method according to an embodiment, which includes the following steps.
[0232] Step 302: Intelligently generate the live stream cover title.
[0233] Specifically, after receiving the target live stream's backup subject, the system first extracts its corresponding subject matter, including the main image, core selling point text, and structured attribute information. Simultaneously, the system acquires user characteristic data related to the subject's historical interactions, including typical user age distribution, geographic preferences, and usage scenario tags. This data is then combined with the platform's current popular keyword library for fusion analysis, constructing a multi-dimensional content generation feature vector. Based on this feature vector, the system automatically generates a cover image adapted to the platform's display size using an intelligent content generation engine. The cover image's visual style is dynamically adjusted based on user-preferred color schemes, and highly attractive copywriting elements generated from keyword combinations are overlaid. Simultaneously, the system generates multiple candidate titles. Each title uses a natural language processing model to semantically combine scene words, subject selling point words, and platform hot words, ensuring it aligns with both user interests and the platform's recommendation algorithm's semantic rules. Finally, the cover image and title text, as core components of the live stream preview, are integrated into the pre-release preview content for the broadcaster to preview or use directly.
[0234] Step 304: Intelligent generation of multiple live stream topic previews + automatic release at the best time.
[0235] Specifically, after generating the cover and title, the system further clusters the target audience for the live stream according to preset scenario classification rules (such as home life, affordable goods, functional skincare, etc.), forming one or more thematic dimensions. For each thematic dimension, the system automatically matches the corresponding content template and structures the selling points of all objects under that theme according to dimensions such as scenario, function, and price, generating pre-launch content with a systematic seeding logic, including text and image layout, paragraph copy, and image suggestions. Based on this, the system activates an optimal release time calculation model. This model comprehensively analyzes user interaction data from the streamer's historical content releases to identify high-interaction periods; it also accesses platform-wide content distribution data to obtain traffic activity curves for each time period within 24 hours; in addition, the system monitors recent large-scale content releases in the same product category to identify potential peak release times for competitors. By cross-referencing these three types of data, the model selects the optimal release time as one that falls within the user activity window while avoiding the concentrated release of competitors. The system automatically injects the release time into the scheduling parameters of the preview content, and after the broadcaster confirms, automatically completes the platform release of the preview content at the specified time, thereby achieving more accurate and timely content delivery.
[0236] Step 306: Identify the published content corresponding to the products in this live stream and link it to the live stream reservation with one click.
[0237] Specifically, during the preparation phase, the system parses all backup objects associated with the target live stream and extracts a unique identifier for each object. Then, based on this identifier, the system retrieves all previously published content from the content library by the same broadcaster, filtering out content containing the same or related object identifiers. This previously published content is considered a potential traffic-driving touchpoint semantically related to the current live stream. The system pushes this previously published content as a configurable item to the broadcaster's interface, allowing the broadcaster to authorize its inclusion in the live stream's reservation linkage with a single confirmation. Once confirmed, the system automatically populates the live stream's reservation information—including the start time, live stream title, and entry link—into the display pages of these previously published contents and calls the platform interface to display the live stream reservation entry by default when users visit these historical pages. This process eliminates the need for broadcasters to manually create or configure reservation components individually, achieving a model upgrade from "creating a reservation activity page" to "enabling full-channel preview exposure," significantly improving the completeness of reservation coverage and operational efficiency.
[0238] See Figure 4 As shown, Figure 4 This is one of the front-end display interface diagrams for generating live broadcast previews provided in one embodiment of this specification. The diagram illustrates the core elements of live broadcast room operation and the layout of the mobile interface, with each part's text information and functions interconnected. The upper left corner clearly marks the three main modules: "Live Broadcast Cover Title," "Live Broadcast Pre-heating Content," and "Live Broadcast Preview." The specific text of the live broadcast title, as shown in the diagram, attracts users. Below, the "Live Broadcast Cover" uses a 3x3 table to visually display "Product 1 to Product 9," achieving a structured presentation of the products. The "Pre-heating Content Live Broadcast Preview" next to the "Cover Title" in the upper right corner highlights the cover's functional attributes. In the mobile interface, the navigation bar "Follow," "Discover," and "Nearby" along with the search icon constitute the basic interactive entry points, while the "Recommended" section's "Live Broadcasts, Short Dramas, Fashion, Travel Anime" guides users to explore content. The accompanying text for "Cover A" (such as...) Figure 4 As shown, the table on the right (corresponding to "Products 1 to 9") conveys an emotional theme, while the table on the right corresponds to "Products 1 to 9" (linking with the product table in the upper left corner). "Cover B" and "Cover C" serve as examples of covers with different themes, covering diverse scenarios for live stream pre-event promotion and user attraction. The results button at the bottom of the page constructs the operational system, comprehensively covering the entire process from setting the live stream title, delivering pre-event content, designing the cover, displaying products, and interacting with users, clearly presenting the pre-live stream preparation logic and user reach path.
[0239] See Figure 5 As shown, Figure 5This is the second schematic diagram of a front-end display interface for generating live broadcast previews, provided in one embodiment of this specification. It demonstrates the entire process of generating and previewing live broadcast preview content: the left navigation bar uses "Live Broadcast Cover Title," "Live Broadcast Pre-sale Content," and "Live Broadcast Preview" categories; the toggle buttons at the top of the middle function area (such as "Publish 3 days before live broadcast") are used to set the time period for automatic publication of pre-sale content; the "Content Theme" section below offers multiple category options; the "Image Content" area displays images a to f (including upload entry); the "Content Title" and "Text Content" are used to edit the title and description (including product descriptions ① to ④); the "#Topic" and emoji / refresh buttons are used to enrich content tags; the "Match Products" area associates the products corresponding to images c to f (including "Add Product" entry); the right preview area displays "Cover Title: Pre-heating Content Live Broadcast Preview" at the top, with "Anchor ID" and "Follow Now" buttons in the middle, and "Image a" and complete text content (including title, description, topic, etc.) at the bottom, displaying the generated live broadcast preview effect in real time, assisting users in confirming content and achieving automatic publication before the live broadcast.
[0240] See Figure 6 As shown, Figure 6 This is the third schematic diagram of a front-end display interface for generating live broadcast previews, provided in one embodiment of this specification. It illustrates the module division and full-process display logic of the live broadcast reservation function.
[0241] The left panel features "Livestream Cover Title," "Livestream Pre-event Content," and "Livestream Preview" as its core modules. The “Live Stream Cover Title” corresponds to the “Cover Title Pre-heating Content Live Stream Preview” on the right, indicating that the cover title needs to carry pre-heating information and be displayed in the form of a “Live Stream Preview”. The "Live Stream Pre-Show Content" is presented through "Live Stream Dynamics: Schedule All Live Streams," including the start time (e.g., "Live Stream Starts at 20:00 on June 26th"), the reservation button, the theme "Meet for Exquisite Home Furnishings Special," and data feedback such as "1224 people have already made reservations."
[0242] The "Live Broadcast Preview" feature has two switches: After enabling "Show [Next Session Reservation] on Homepage", the live stream reservation function will be activated on your personal homepage; After enabling "Preview Content Display [Next Session Reservation]", the newly released preview content page will display the reservation function for that live stream.
[0243] The feature "Showcase of Historical Product Releases Related to This Livestream [Next Session Reservation]" will be enabled. Once enabled, the historical product releases associated with this livestream (a card-style layout with two columns, each card containing a "cover", title, and release time) will be displayed, allowing users to choose which parts of the content to display.
[0244] The reservation portal is displayed in two places: The "Live Stream Reservation Entry on Personal Homepage" displays the streamer's information and the live stream time "Tomorrow at 21:30"; The "Live Stream Reservation Entry Below the Announcement" includes the streamer's ID, the live stream time "December 25th, 21:30", the number of reservations "99 people have reserved" and the "Reserved" status, and clearly states the operation path "Users can click to reserve your live stream".
[0245] The entire map achieves full coverage of the live broadcast reservation process from pre-heating to reservation through module linkage, switch control, content association and entry differentiation, and all text information (such as theme, time, data and operation prompts) is presented in a structured manner.
[0246] See Figure 7 As shown, Figure 7 This is the fourth schematic diagram of a front-end display interface for generating live broadcast previews, provided in one embodiment of this specification. Figure 7 yes Figure 5 Clicking "Publish x days before the live stream" will bring up a detailed time configuration page. The left navigation bar indicates that you are currently in the "Live Stream Pre-heat Content" module; the top of the middle area displays "Generate 3 pre-heat content articles for you, automatically published during popular time slots 3 days before the live stream," and below are three toggle buttons ("Publish 3 days before the live stream," "Publish 2 days before the live stream," and "Publish 1 day before the live stream"), used to set the publication time of the pre-heat content; when the user selects a time slot, the system will pop up this time selection interface, which includes a calendar component displaying the specific date, supporting switching between months using the left and right arrows, and allowing users to click on specific dates to select; the right side is a time selector, providing numerical input for hours, minutes, and seconds; the lower right corner has "Cancel" and "Save" buttons for confirming or discarding time settings.
[0247] Corresponding to the above method embodiments, this specification also provides embodiments of a live broadcast preview generation device. Figure 8 This is a schematic diagram of a live broadcast preview generation device provided in one embodiment of this specification. Figure 8 As shown, the device includes: Display module 802 is configured to display a live broadcast preview publishing page in response to a determination operation of a backup broadcast object that has completed the target live broadcast. The live broadcast preview publishing page includes at least one live broadcast preview and at least one live broadcast preview publishing determination control. At least one live broadcast preview is generated based on the determined backup broadcast object, and the publishing determination control is used to determine the publishing time of at least one live broadcast preview. The publishing module 804 is configured to publish the target live broadcast preview based on the publication time in response to identifying a target live broadcast preview in at least one live broadcast preview, wherein the display page of the target live broadcast preview includes the live broadcast reservation entry for the target live broadcast.
[0248] Optionally, the release determination control includes candidate release times, and the live broadcast preview includes at least one of preview content and cover title; the display module 802 is further configured to display a candidate release time area, wherein the candidate release time area is used to display at least one candidate content release time; display a preview content editing area, wherein the preview content editing area is used to display the preview content of the target live broadcast; and display a cover title display area, wherein the cover title display area is used to display the cover image and title text of the target live broadcast.
[0249] Optionally, the candidate release time area includes at least one of a preset time period option, a calendar component, and a recommended release time prompt; the display module 802 is further configured to display the preset time period option, and in response to the selection operation of any time period option, determine the corresponding candidate content release time, and display a live broadcast preview containing the candidate content release time on the live broadcast preview release page; display the calendar component, and in response to the selection operation of a specific date in the calendar component, determine the candidate content release time in combination with the time selection control, and display a live broadcast preview containing the candidate content release time on the live broadcast preview release page; display a recommended release time prompt, and in response to the confirmation operation of the recommended release time prompt, determine the candidate content release time, and display a live broadcast preview containing the candidate content release time on the live broadcast preview release page.
[0250] Optionally, the display module 802 is further configured to display topic category tags on the live broadcast preview release page, and in response to a click operation on the topic category tags, match and display the preview content under the corresponding topic, and display the live broadcast preview containing the preview content on the live broadcast preview release page; display an editable title input box and content text area on the live broadcast preview release page, and in response to editing operations on the input box and text area, generate and display preview content, and display the live broadcast preview containing the preview content on the live broadcast preview release page; display an image selection area on the live broadcast preview release page, and in response to uploading or selecting multiple images, combine the images and display them as preview content, and display the live broadcast preview containing the preview content on the live broadcast preview release page.
[0251] Optionally, the cover title display area includes a cover image preview area, a title text input box, and multiple cover style templates; the display module 802 is further configured to display the cover image preview area on the live broadcast preview release page, and in response to a cover image replacement operation, replace and display the cover image; display the title text input box on the live broadcast preview release page, and in response to an editing operation on the input box, generate and display a recommended title; and display multiple cover style templates on the live broadcast preview release page, and in response to a selection operation on a target cover style template, update the cover image based on the target cover style template.
[0252] Optionally, the live broadcast preview release page also includes a reservation selection control. The reservation selection control is used to select the live broadcast display page to add the live broadcast reservation entry. The reservation selection control includes a first switch control, a second switch control, and a list selection area. The live broadcast display page includes the broadcaster's personal homepage, preview content, and historical content associated with the target live broadcast. The display module 802 is further configured to display the live broadcast preview of the target live broadcast and the corresponding release confirmation control on the live broadcast preview release page, and to display the first switch control on the live broadcast preview release page, wherein the first switch control is used to display the live broadcast reservation entry on the broadcaster's personal homepage; to display the live broadcast preview of the target live broadcast and the corresponding release confirmation control on the live broadcast preview release page, and to display the second switch control on the live broadcast preview release page, wherein the second switch control is used to display the live broadcast reservation entry in the preview content; to display the live broadcast preview of the target live broadcast and the corresponding release confirmation control on the live broadcast preview release page, and to display the list selection area on the live broadcast preview release page, wherein the list selection area is used to display historical content, and in response to the selection operation of historical content, the historical content is set as the target display page that can display the reservation entry.
[0253] Optionally, the historical published content displayed in the list selection area includes a thumbnail, publication time, and historical content title; the display module 802 is further configured to highlight the selected historical published content in the list selection area by a check mark; in response to the deselection operation of the selected historical published content, remove the highlighted state of the historical published content in the scheduled display list; in response to the check operation of the unselected historical published content, highlight the historical published content by a check mark.
[0254] Optionally, the live broadcast preview release page also displays a preview area of the reservation configuration results; the live broadcast preview generation device also includes a preview module, configured to display a simulated user interface in the reservation configuration result preview area, wherein the user interface includes a layout diagram of the target live broadcast display page; display a simulated location of the live broadcast reservation entry in the user interface, wherein the simulated location is consistent with the location of the live broadcast reservation entry in the target live broadcast display page; and refresh and update the content in the reservation configuration result preview area in real time in response to modification operations on the reservation selection control in the live broadcast preview release page.
[0255] Optionally, the live broadcast preview generation device also includes a live broadcast management module, configured to display a live broadcast plan management page in response to management operations on published live broadcast previews; the live broadcast plan management page displays a list of each live broadcast preview associated with the target live broadcast and its corresponding interactive data; and in response to a promotion operation triggered on a specific live broadcast preview in the list, configure an enhanced distribution strategy for the specific live broadcast preview.
[0256] Optionally, the live broadcast preview publishing page also includes a live broadcast preview area, which is used to display preview content of at least one live broadcast preview in sequence or side by side; the live broadcast preview generating device also includes an editing module, which is configured to load and display the corresponding live broadcast preview for editing in the editing area of the live broadcast preview publishing page in response to a trigger operation on any preview content in the live broadcast preview preview area.
[0257] Optionally, at least one live broadcast announcement includes the main content to be released, a set of media materials associated with the target audience, and a release status indicator.
[0258] Optionally, the publishing module 804 is further configured to, in response to a batch selection operation of multiple previews in at least one live preview on the live preview publishing page, determine the selected multiple previews as the target live preview; or, in response to a selection operation of a single live preview and subsequent content editing operation, determine the edited preview as the target live preview.
[0259] Applied to this live broadcast preview generation device, the display module 802 responds to the backup broadcast object determination operation and displays a publishing page containing at least one intelligently generated live broadcast preview and a publishing confirmation control; after the user selects the target live broadcast preview, the publishing module 804 triggers the publishing process based on the selected publishing time, ensuring that the display page of the target live broadcast preview automatically includes a live broadcast reservation entry, realizing a lightweight operation of "one-click confirmation for publishing + reservation".
[0260] Figure 9 This is a schematic diagram of another live broadcast preview generation device provided in one embodiment of this specification. Figure 9 As shown, the device includes: The first acquisition module 902 is configured to acquire the backup broadcast object in response to the confirmation operation of the backup broadcast object that the broadcaster has completed the target live broadcast. Generation module 904 is configured to generate live broadcast schedules based on the backup broadcast object; The second acquisition module 906 is configured to acquire the release time determined by the broadcaster for the target live broadcast preview; Configuration module 908 is configured to publish target live stream previews based on the release time, and to configure a live stream reservation entry on the target live stream preview display page.
[0261] Optionally, the generation module 904 is further configured to extract object materials and user feature data from the pre-broadcast objects; generate scenario-based description content based on the object materials and user feature data; match cover materials and titles for the scenario-based description content according to scenario classification rules; and integrate the scenario-based description content, cover materials, and titles into a live broadcast preview.
[0262] Optionally, the live broadcast preview generation device also includes a time period determination module, configured to acquire user interaction data corresponding to historical published content associated with the broadcaster; calculate at least one recommended release time period based on the user interaction data and the platform's content distribution rules; and update the release time of at least one recommended release time period.
[0263] Optionally, the time period determination module is further configured to divide user interaction data into time periods to obtain the corresponding interaction data indicators within each time period; identify the time periods where the interaction data indicators exceed a preset threshold and determine them as candidate interaction time periods; compare the candidate interaction time periods with the time periods in the platform's content distribution rules that exceed a preset distribution indicator to obtain overlapping time periods; and match the overlapping time periods with a preset set of conflicting time periods to exclude the time periods included in the preset set of conflicting time periods from the overlapping time periods to obtain at least one recommended release time period.
[0264] Optionally, the live broadcast preview generation device also includes a display module, which is configured to retrieve historical published content containing object identifiers from the content library based on the object identifiers of the backup broadcast objects; generate a display page containing the historical published content and send the display page to the broadcaster; and receive the selection results returned by the broadcaster based on the display page, wherein the selection results indicate the historical published content for which a live broadcast reservation entry needs to be added.
[0265] Applied to this live broadcast preview generation device, the first acquisition module 902 receives the backup broadcast object, and the generation module 904 generates the live broadcast preview accordingly; the second acquisition module 906 acquires the release time submitted by the broadcaster, and the configuration module 908 executes the timed release and automatically embeds the live broadcast reservation entrance in the display page of the target live broadcast preview, completing the back-end closed-loop processing from content generation to full-link exposure.
[0266] The above is an illustrative scheme of a live broadcast preview generation device according to this embodiment. It should be noted that the technical solution of this live broadcast preview generation device and the technical solution of the live broadcast preview generation method described above belong to the same concept. For details not described in detail in the technical solution of the live broadcast preview generation device, please refer to the description of the technical solution of the live broadcast preview generation method described above.
[0267] Figure 10 A structural block diagram of a computing device 1000 according to one embodiment of this specification is shown. The components of the computing device 1000 include, but are not limited to, a memory 1010 and a processor 1020. The processor 1020 is connected to the memory 1010 via a bus 1030, and a database 1050 is used to store data.
[0268] The computing device 1000 also includes an access device 1040, which enables the computing device 1000 to communicate via one or more networks 1060. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 1040 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.
[0269] In one embodiment of this specification, the above-described components of the computing device 1000 and Figure 10 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 10 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.
[0270] The computing device 1000 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 1000 can also be a mobile or stationary server.
[0271] The processor 1020 is used to execute the following computer program / instruction, which, when executed by the processor, implements the steps of the above-mentioned live broadcast preview generation method.
[0272] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on its differences from other embodiments. In particular, the computing device embodiments are basically similar to the live broadcast preview generation method embodiments, so the description is relatively simple; relevant parts can be referred to in the description of the live broadcast preview generation method embodiments.
[0273] An embodiment of this specification also provides a computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the above-described live broadcast preview generation method.
[0274] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the computer-readable storage medium embodiment is described simply because it is substantially similar to the live broadcast preview generation method embodiment; relevant parts can be referred to in the description of the live broadcast preview generation method embodiment.
[0275] An embodiment of this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described live broadcast preview generation method.
[0276] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the above-described live broadcast preview generation method belong to the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the above-described live broadcast preview generation method.
[0277] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.
[0278] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.
[0279] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.
[0280] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0281] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.
Claims
1. A method for generating live broadcast previews, characterized in that, Applied to the broadcaster's end, including: In response to the determination of the backup broadcast object for the target live broadcast, a live broadcast preview release page is displayed. The live broadcast preview release page includes at least one live broadcast preview and a release determination control for the at least one live broadcast preview. The at least one live broadcast preview is generated based on the determined backup broadcast object, and the release determination control is used to determine the release time of the at least one live broadcast preview. In response to identifying a target live stream preview in the at least one live stream preview, the target live stream preview is published based on the publication time, wherein the display page of the target live stream preview includes a live stream reservation entry for the target live stream.
2. The method according to claim 1, characterized in that, The release confirmation control includes candidate release times; the live stream preview includes at least one of preview content and cover title; the display of the live stream preview release page includes at least one of the following: Display candidate publication time areas, wherein the candidate publication time areas are used to display the publication time of at least one candidate content; The preview content editing area is used to display the preview content of the target live stream; The cover title display area is used to display the cover image and title text of the target live stream.
3. The method according to claim 2, characterized in that, The candidate release time area includes at least one of the following: preset time period options, calendar component, and recommended release time prompt; the display of the candidate release time area includes at least one of the following: The preset time period options are displayed. In response to the selection operation of any time period option, the corresponding candidate content release time is determined, and a live broadcast preview containing the candidate content release time is displayed on the live broadcast preview release page. The calendar component is displayed, and in response to the operation of selecting a specific date in the calendar component, the release time of the candidate content is determined in combination with the time selection control, and a live broadcast preview containing the release time of the candidate content is displayed on the live broadcast preview release page; The system displays the recommended release time prompt, and in response to the confirmation operation of the recommended release time prompt, determines the release time of the candidate content, and displays a live broadcast preview containing the release time of the candidate content on the live broadcast preview release page.
4. The method according to claim 2, characterized in that, The provision of displaying the preview content editing area on the live broadcast preview release page includes at least one of the following: The live broadcast preview release page displays topic category tags. In response to the click operation of the topic category tags, the preview content under the corresponding topic is matched and displayed, and the live broadcast preview containing the preview content is displayed on the live broadcast preview release page. An editable title input box and content text area are displayed on the live broadcast preview release page. In response to the editing operation of the input box and text area, preview content is generated and displayed, and a live broadcast preview containing the preview content is displayed on the live broadcast preview release page. The live broadcast preview release page displays an image selection area. In response to the upload or selection of multiple images, the images are combined and displayed as preview content. The live broadcast preview containing the preview content is then displayed on the live broadcast preview release page.
5. The method according to claim 2, characterized in that, The cover title display area includes a cover image preview area, a title text input box, and multiple cover style templates; displaying the cover title display area on the live broadcast preview release page includes: The cover image preview area is displayed on the live broadcast preview release page, and the cover image is replaced and displayed in response to the cover image replacement operation; The title text input box is displayed on the live broadcast preview release page, and a recommended title is generated and displayed in response to the editing operation of the input box; The multiple cover style templates are displayed on the live broadcast preview release page, and the cover image is updated based on the target cover style template in response to the selection operation of the target cover style template.
6. The method according to any one of claims 1-5, characterized in that, The live stream preview release page also includes a reservation selection control, which is used to select the live stream display page to add a live stream reservation entry. The reservation selection control includes a first switch control, a second switch control, and a list selection area. The live stream display page includes the broadcaster's personal homepage, the preview content, and historical content associated with the target live stream. Displaying the live stream preview release page includes: The live broadcast preview and corresponding release confirmation control of the target live broadcast are displayed on the live broadcast preview release page, and the first switch control is displayed on the live broadcast preview release page. The first switch control is used to display the live broadcast reservation entrance on the anchor's personal homepage. The live broadcast preview and corresponding release confirmation control of the target live broadcast are displayed on the live broadcast preview release page, and the second switch control is displayed on the live broadcast preview release page. The second switch control is used to display the live broadcast reservation entrance in the preview content. The live broadcast preview and corresponding release confirmation control for the target live broadcast are displayed on the live broadcast preview release page. The list selection area is also displayed on the live broadcast preview release page. The list selection area is used to display the historical release content. In response to the selection operation of the historical release content, the historical release content is set as the target display page where the reservation entry can be displayed.
7. The method according to claim 6, characterized in that, The historical content displayed in the list selection area includes thumbnails, publication time, and titles of historical content; after the list selection area is displayed on the live broadcast preview release page, it also includes: In the list selection area, the selected historical posts are highlighted by checking the boxes; In response to the unchecking operation of the selected historical published content, the highlighted status of the historical published content in the scheduled display list is removed; In response to the selection of unselected historical posts, the historical posts are highlighted by a checkmark.
8. The method according to claim 1, characterized in that, The live broadcast preview page also displays a preview area for the reservation configuration results; the method further includes: A simulated user interface is displayed in the reservation configuration result preview area, wherein the user interface includes a layout diagram of the target live broadcast display page; The simulated location of the live stream reservation entrance is displayed on the user interface, wherein the simulated location is consistent with the location of the live stream reservation entrance on the target live stream display page; In response to modifications made to the reservation selection control on the live broadcast preview page, the content in the reservation configuration result preview area is refreshed and updated in real time.
9. The method according to claim 1, characterized in that, The method further includes: In response to management actions related to published live stream announcements, the live stream schedule management page is displayed; The live streaming plan management page displays a list of each live streaming preview associated with the target live stream and their corresponding interactive data. In response to a promotional action triggered for a specific live stream preview in the list, an enhanced distribution strategy is configured for that specific live stream preview.
10. The method according to claim 1, characterized in that, The live broadcast preview page also includes a live broadcast preview area, which is used to display the preview content of the at least one live broadcast preview in sequence or side by side. Following the display of the live stream preview release page, the following is also included: In response to a triggered operation on any preview content in the live broadcast preview area, the corresponding live broadcast preview is loaded and displayed in the editing area of the live broadcast preview publishing page for editing.
11. The method according to claim 1, characterized in that, The at least one live broadcast announcement includes the main content to be published, a set of media materials associated with the prepared broadcast object, and a publication status identifier.
12. The method according to claim 1, characterized in that, The response to determine the target live broadcast preview in the at least one live broadcast preview includes: In response to a batch selection operation of multiple previews from at least one live broadcast preview on the live broadcast preview release page, the selected multiple previews are identified as the target live broadcast preview; or, In response to the selection of a single live broadcast preview and subsequent content editing, the edited preview is designated as the target live broadcast preview.
13. A method for generating live broadcast previews, characterized in that, Applied to the server side, including: In response to the operator's operation of determining the backup broadcast object for the target live broadcast, the backup broadcast object is obtained; Based on the prepared broadcast objects, a live broadcast schedule is generated; Obtain the release time determined by the broadcaster for the target live stream preview; The target live stream preview is published based on the published time, and a live stream reservation entry is configured on the display page of the target live stream preview.
14. The method according to claim 13, characterized in that, The step of generating a live broadcast schedule based on the prepared broadcast object includes: Extract the object materials and user feature data from the prepared broadcast objects; Based on the object material and the user feature data, generate contextualized description content; According to the scene classification rules, cover material and title are matched for the scene-based description content; The contextual description, the cover image, and the title are integrated into a live stream preview.
15. The method according to claim 13, characterized in that, Before publishing the target live stream preview based on the published time, the method further includes: Obtain user interaction data corresponding to historically published content associated with the broadcaster's client; Based on the user interaction data and the platform's content distribution patterns, at least one recommended release period is calculated; Update the publication time with the at least one recommended publication period.
16. The method according to claim 15, characterized in that, Based on the user interaction data and platform content distribution patterns, at least one recommended release period is calculated, including: The user interaction data is divided into time periods to obtain the corresponding interaction data indicators for each time period. Identify time periods where the interactive data indicators exceed a preset threshold and determine them as candidate interactive time periods; The candidate interaction time periods are compared with the time periods in the platform's content distribution rules that exceed the preset distribution index to obtain the overlapping time periods; Based on the matching of the overlapping time period with the preset conflict time period set, the time periods included in the preset conflict time period set are excluded from the overlapping time period to obtain the at least one recommended release time period.
17. The method according to claim 13, characterized in that, Before configuring the live stream reservation entry on the target live stream preview display page, the following is also included: Based on the object identifier of the backup broadcast object, retrieve historical published content containing the object identifier published by the broadcaster in the content library; Generate a display page containing the historically published content, and send the display page to the broadcaster's terminal; The system receives the selection results returned by the broadcaster from the display page, wherein the selection results indicate the historical content for which a live broadcast reservation entry needs to be added.
18. A live broadcast preview generation device, characterized in that, Applied to the broadcaster's end, including: The display module is configured to display a live broadcast preview release page in response to a determination operation of a backup broadcast object that has completed the target live broadcast. The live broadcast preview release page includes at least one live broadcast preview and a release determination control for the at least one live broadcast preview. The at least one live broadcast preview is generated based on the determined backup broadcast object, and the release determination control is used to determine the release time of the at least one live broadcast preview. The publishing module is configured to, in response to determining a target live broadcast preview in the at least one live broadcast preview, publish the target live broadcast preview based on the publishing time, wherein the display page of the target live broadcast preview includes a live broadcast reservation entry for the target live broadcast.
19. A live broadcast preview generation device, characterized in that, Applied to the server side, including: The first acquisition module is configured to acquire the backup broadcast object in response to the determination operation of the backup broadcast object that the broadcaster has completed the target live broadcast. The generation module is configured to generate live broadcast schedules based on the prepared broadcast objects; The second acquisition module is configured to acquire the release time determined by the broadcaster for the target live broadcast preview; The configuration module is configured to publish the target live stream preview based on the publication time, and to configure a live stream reservation entry on the display page of the target live stream preview.
20. A computing device, characterized in that, include: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the live broadcast preview generation method according to any one of claims 1-17.
21. A computer-readable storage medium, characterized in that, It stores a computer program / instruction that, when executed by a processor, implements the steps of the live broadcast preview generation method according to any one of claims 1-17.
22. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the steps of the live broadcast preview generation method according to any one of claims 1-17.