Content publishing method and device, equipment and storage medium

Abstract

The invention relates to a content publishing method and device, equipment and a storage medium, and the method comprises the steps: obtaining product configuration data of a to-be-published product, the product configuration data comprising target publishing time; storing the product configuration data into a target database, and generating a target event message for the product configuration data; product description information of the to-be-released product is also stored in the target database; sending the target event message to a publishing end, so that the publishing end publishes the push content according to the target publishing time in response to the target event message; wherein the push content is generated by the product configuration data extracted from the target database by the publishing end and the product description information of the to-be-published product. By adopting the method, the content publishing efficiency can be improved.

Description

Technical Field

[0001] This application relates to the field of content publishing technology, and in particular to a content publishing method, apparatus, device, and storage medium. Background Technology

[0002] With the development of internet technology, users are increasingly demanding timely information delivery. Various service platforms need an efficient and flexible content publishing mechanism to ensure that the latest service content can be delivered to users in a timely and accurate manner.

[0003] However, in traditional content publishing methods, systems typically rely on periodic batch tasks to process and synchronize content information. This approach suffers from a fixed configuration process, causing the information perceived by the user to lag behind the actual configuration. Furthermore, the configuration process often requires modifications to the configuration code to address ad-hoc needs, increasing costs and impacting content publishing efficiency. Summary of the Invention

[0004] Therefore, it is necessary to provide a content publishing method, apparatus, device, and storage medium to address the aforementioned technical problems, thereby improving content publishing efficiency.

[0005] Firstly, this application provides a method for enabling publication, including:

[0006] Obtain the product configuration data for the product to be released, including the target release time.

[0007] Product configuration data is stored in the target database, and target event messages for the product configuration data are generated; the target database also stores product description information for products to be released.

[0008] Send the target event message to the publisher so that the publisher responds to the target event message and publishes the push content according to the target publication time;

[0009] The push content is generated by the publishing end from the product configuration data extracted from the target database and the product description information of the product to be published.

[0010] In one embodiment, obtaining product configuration data of the product to be released includes: obtaining at least one product configuration parameter of the product to be released; generating structured configuration data based on a preset configuration template and according to the at least one product configuration parameter; and using the structured configuration data as the product configuration data of the product to be released.

[0011] In one embodiment, generating a target event message for product configuration data includes: validating the product configuration data; and if the validity verification passes, generating a target event message based on the product configuration data.

[0012] In a second aspect, the present application provides a content publishing method, comprising:

[0013] receiving a target event message sent by a configuration end, the target event message being generated according to product configuration data of a product to be published obtained by the configuration end; the product configuration data comprising a target publishing time; the product configuration data being stored into a target database by the configuration end, and product description information of the product to be published also being stored in the target database;

[0014] extracting the product configuration data and the product description information from the target database in response to the target event message;

[0015] generating push content according to the product configuration data and the product description information;

[0016] publishing the push content according to the target publishing time.

[0017] In one embodiment, the generating of the push content according to the product configuration data and the product description information comprises: determining a push strategy according to the product configuration data; the push strategy comprising at least one of a push user type, a product publishing period, a shelf rule and a product push combination; and generating the push content according to the push strategy and the product description information.

[0018] In one embodiment, the product to be published comprises a target product and a candidate product; the product configuration data comprises a target sales volume of the target product; and the publishing of the push content according to the target publishing time comprises: publishing push content corresponding to the target product according to the target publishing time; obtaining an actual sales volume of the target product; and switching the push content corresponding to the target product to push content corresponding to the candidate product in a case where the actual sales volume reaches the target sales volume.

[0019] In a third aspect, the present application provides a content publishing device configured in a configuration end, comprising:

[0020] a first obtaining module configured to obtain product configuration data of a product to be published, the product configuration data comprising a target publishing time;

[0021] a first generating module configured to store the product configuration data into a target database, and to generate a target event message for the product configuration data; the target database also storing product description information of the product to be published;

[0022] a sending module configured to send the target event message to a publishing end, so that the publishing end publishes push content according to the target publishing time in response to the target event message;

[0023] The push content is generated by the publishing end from the product configuration data and the product description information of the product to be published extracted from the target database.

[0024] Fourthly, this application also provides a content publishing device, configured on a publishing end, comprising:

[0025] The receiving module is used to receive target event messages sent by the configuration terminal. The target event messages are generated based on the product configuration data of the product to be published obtained by the configuration terminal. The product configuration data includes the target release time. The product configuration database is stored by the configuration terminal into the target database. The target database also stores the product description information of the product to be published.

[0026] The extraction module is used to extract product configuration data and product description information from the target database in response to target event messages;

[0027] The second generation module is used to generate push content based on product configuration data and product description information;

[0028] The publishing module is used to publish push content based on the target publishing time.

[0029] Fifthly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the methods of the first and second aspects described above under various possible implementations.

[0030] In a sixth aspect, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the methods of the first and second aspects described above under various possible implementations.

[0031] In a seventh aspect, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the methods of the first and second aspects described above under various possible implementations.

[0032] The aforementioned content publishing method, apparatus, equipment, and storage medium, by acquiring the product configuration data of the product to be published, transform the publishing task from a fixed process to parameterized control, providing a data foundation for the generation of subsequent published content. Simultaneously, by introducing a target publishing time into the product configuration data, a clear time scheduling basis is established. By storing the product configuration data in the target database and generating target event messages for the product configuration data, the state change of updating the product configuration data is transformed into a technical signal that can be processed asynchronously, decoupling the publishing process from configuration data updates and improving response speed. By sending the target event message to the publishing end, the publishing end responds to the target event message and publishes push content according to the target publishing time. The push content is generated by the publishing end from the product configuration data extracted from the target database and the product description information of the product to be published, thus realizing an event-driven asynchronous publishing mechanism. This achieves a rapid response from configuration completion to publishing readiness, improving content publishing efficiency. Furthermore, by dynamically acquiring the latest product configuration data and product information from the target database to generate push content, the accuracy and completeness of the published content are ensured. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 This is an application environment diagram of a content publishing method in one embodiment;

[0035] Figure 2 This is a flowchart illustrating a content publishing method in one embodiment;

[0036] Figure 3 This is a flowchart illustrating the content publishing method in another embodiment;

[0037] Figure 4 This is an interactive diagram of a content publishing method in one embodiment;

[0038] Figure 5 This is a sequence diagram of a content publishing method in one embodiment;

[0039] Figure 6 This is a structural block diagram of a content publishing device in one embodiment;

[0040] Figure 7 This is a structural block diagram of a content publishing device in another embodiment;

[0041] Figure 8 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0043] The content publishing method provided in this application embodiment can be applied to, for example, Figure 1 In the application environment shown, the configuration terminal 102 and the publishing terminal 104 can communicate via a network.

[0044] For example, configuration terminal 102 can be a terminal device or a configuration server. The terminal device can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and IoT devices. The configuration server can be a standalone physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server providing cloud computing services.

[0045] For example, the publishing end 104 can be a publishing server. The publishing server can be a standalone physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server providing cloud computing services. The publishing server can be configured with a business system for processing business data, publishing content, and interacting with other terminal devices or servers.

[0046] In one exemplary embodiment, such as Figure 2 As shown, a content publishing method is provided, which can be applied to... Figure 1 Taking configuration terminal 102 as an example, the following steps are included:

[0047] S210. Obtain the product configuration data of the product to be released, including the target release time.

[0048] The products to be released may include physical products or virtual service products. This application does not limit the specific product type of the products to be released.

[0049] Among them, product configuration data can be understood as configuration data specific to the product to be released and associated with the release content.

[0050] Optionally, product configuration data may include at least one of display configuration data, rule configuration data, scheduling configuration data, and strategy configuration data. For example, display configuration data may include at least one of the following: image data, description data, and prompt data of the product to be published. Rule configuration data may include target user tags associated with the product to be published. Scheduling configuration data may include at least one of the following: push cycle, target release time, scheduled listing or delisting rules, and inventory limits. Strategy configuration data may include a combination of multi-dimensional parameters parsed based on a strategy combiner, such as binding target display content and target user groups to specific time periods, or associating different products to be published with product attributes for recommendation.

[0051] The image data can be in multiple sizes, and this application does not impose any limitations on the specific image size. Target user tags can be bound to the product to be published; these tags may include, for example, tags for new users. The listing rules can be set according to actual circumstances, and this application does not impose any limitations on them. For example, the product can be listed at a first preset time and taken down at a second preset time, thereby achieving automatic control over the display of the published content. The push cycle can be a fixed time or a dynamic time; this application also does not impose any limitations on this.

[0052] Optionally, product configuration data may also include publishing attribute data. Publishing attribute data may include page attribute information corresponding to the content to be published. Page attribute information may include at least one of the following: page name, page area name, and page area configuration information. For example, by setting page area configuration information, the content to be published can be displayed independently in a target area of ​​the target display page, making it easier for users to focus on that target area.

[0053] In an optional embodiment, at least one product configuration parameter of the product to be released can be obtained; based on a preset configuration template, structured configuration data can be generated according to the at least one product configuration parameter; and the structured configuration data can be used as the product configuration data of the product to be released.

[0054] The preset configuration templates can correspond to different template types. These different template types can include general template types. Preset configuration templates can be configured with corresponding preset fields, such as product code, target release time, and inventory limit. By introducing parameterized preset configuration templates, zero-code configuration is achieved. New activities or adjustments to related parameters (such as changing product type or extending activity time) can be quickly deployed through the configuration interface without developer intervention, reducing the configuration cycle from days to minutes.

[0055] For example, at least one product configuration parameter can be dynamically rendered based on a preset configuration template through a graphical interface on the configuration side to generate structured configuration data. This generation of product configuration data can respond to configuration operations on the graphical interface. Configuration operations may include at least one of sorting and selection operations. The graphical interface can be understood as a page with a custom graphical layout.

[0056] Understandably, by introducing product data, the release process has been transformed from a fixed workflow to parameterized control, providing a data foundation for the generation of subsequent release content. Simultaneously, product configuration data for products to be released can be configured independently by staff, which helps reduce development costs and improve release flexibility.

[0057] In an optional embodiment, the configuration terminal can display a historical configuration data preview interface, allowing previewing of historical configuration periods to avoid configuration errors and achieve version control and rollback.

[0058] S220. Store the product configuration data into the target database and generate a target event message for the product configuration data; the target database also stores product description information of the product to be published.

[0059] In an optional embodiment, the product configuration data can be validated; if the validation passes, a target event message is generated based on the product configuration data.

[0060] Optionally, validity verification may include at least one of time conflict verification, product information verification, and compliance verification.

[0061] For example, first time-related information can be extracted from historical configuration data, which may include time information such as historical release time and historical push cycle; second time-related information can be extracted from the currently acquired product configuration data, which may include time information such as target release time and target push cycle; and conflict verification can be performed on the first time-related information and the second time-related information.

[0062] For example, product information of the product to be published can be extracted from product configuration data, and the product information can be verified. The product information may include at least one of the following: product name and product quantity.

[0063] In an optional embodiment, if the validity verification passes, a Kafka event message is generated based on the product configuration data; this Kafka event message is then used as the target event message. Kafka is a distributed event streaming platform primarily used for efficiently processing real-time data streams.

[0064] For example, the target event message may include at least one of the following: the product identifier of the product to be published and the storage address of the product configuration data.

[0065] In an optional embodiment, product configuration data can be written to the target cluster so that the subsequent publishing end can read the product configuration data, thereby achieving distributed cache synchronization. The target cluster is a distributed cluster that organizes multiple instances together to function as a single logical database. The target cluster can be a Redis cluster; this application does not limit the specific cluster type of the target cluster.

[0066] S230. Send the target event message to the publishing end so that the publishing end responds to the target event message and publishes the push content according to the target publication time; wherein, the push content is generated by the publishing end from the product configuration data extracted from the target database and the product description information of the product to be published.

[0067] The push content can be understood as a product card for the product to be published to the client. The product card can display configuration information related to the product to be published, such as product description information, price information, etc.

[0068] In an optional embodiment, the publisher can subscribe to and update the configuration in real time by triggering event messages through Kafka or a message broker (or message middleware) after the configuration is changed on the configuration side. This allows the publisher to generate push content based on the extracted product configuration data and the product description information of the product to be published.

[0069] In an optional embodiment, the publishing end can determine the push strategy based on product configuration data; the push strategy includes at least one of the following: push user type, product release cycle, listing rules, and product push combination; and generate push content based on the push strategy and product description information.

[0070] In an optional embodiment, the product to be released includes a target product and a candidate product; the publishing end can release the push content corresponding to the target product according to the target release time; obtain the actual sales volume of the target product; and when the actual sales volume reaches the target sales volume, switch the push content corresponding to the target product to the push content corresponding to the candidate product.

[0071] The target sales volume can be set by technical personnel based on their needs or experience, or determined through a large number of experiments; this application does not impose any restrictions on this.

[0072] The aforementioned content publishing method, by acquiring the product configuration data of the product to be published, transforms the publishing task from a fixed process to parameterized control, providing a data foundation for the generation of subsequent published content. Simultaneously, by introducing a target publishing time into the product configuration data, a clear time scheduling basis is established. By storing the product configuration data in the target database and generating target event messages for the product configuration data, the state change of updating the product configuration data is transformed into a technical signal that can be processed asynchronously, decoupling the publishing process from configuration data updates and improving response speed. By sending the target event message to the publishing end, the publishing end responds to the target event message and publishes push content according to the target publishing time. The push content is generated by the publishing end from the product configuration data extracted from the target database and the product description information of the product to be published, thus realizing an event-driven asynchronous publishing mechanism. This achieves a rapid response from configuration completion to publishing readiness, improving content publishing efficiency. Furthermore, by dynamically acquiring the latest product configuration data and product information from the target database to generate push content, the accuracy and completeness of the published content are ensured.

[0073] Based on the above embodiments, such as Figure 3 As shown, another content publishing method is provided, which can be applied to... Figure 1 Taking the 104 error message in the publishing terminal as an example, the steps are as follows:

[0074] S310. Receive the target event message sent by the configuration terminal. The target event message is generated based on the product configuration data of the product to be published obtained by the configuration terminal. The product configuration data includes the target release time. The product configuration database is stored by the configuration terminal into the target database. The target database also stores the product description information of the product to be published.

[0075] S320: In response to the target event message, extract product configuration data and product description information from the target database.

[0076] S330 generates push content based on product configuration data and product description information.

[0077] S340. Publish push content based on the target release time.

[0078] The details regarding product configuration data and target event messages have already been explained above and will not be repeated here.

[0079] In an optional embodiment, in response to a target event message, the latest product configuration data and corresponding product description information can be read from the target cluster to generate push content, thereby achieving distributed caching and reducing database pressure.

[0080] In an optional embodiment, a push strategy is determined based on product configuration data; the push strategy includes at least one of the following: push user type, product release cycle, listing rules, and product push combination; push content is generated based on the push strategy and product description information. The push strategy can be automatically generated based on a rules engine and the product configuration data.

[0081] In an optional embodiment, the product to be released includes a target product and a candidate product; the product configuration data includes the target sales volume of the target product; accordingly, push content corresponding to the target product can be released according to the target release time; the actual sales volume of the target product is obtained; when the actual sales volume reaches the target sales volume, the push content corresponding to the target product is switched to the push content corresponding to the candidate product.

[0082] In an optional embodiment, push content can be generated based on a rules engine, according to product configuration data and product description information.

[0083] For example, product attribute information of different products to be published can be extracted from product configuration data to obtain object tags of the target publishing object; based on product attribute information and object tags, the target product can be matched from different products to be published; and push content associated with the target product can be published to the target publishing object.

[0084] For example, target user tags corresponding to the product to be published can be extracted from the product configuration data; push content associated with the target product can be published to the target publishing objects that match the target user tags.

[0085] In an optional embodiment, push content corresponding to the target product can be published when the target publication time is reached at the current time.

[0086] The aforementioned content publishing method, by introducing product configuration data, transforms the publishing task from a fixed process to parameterized control, providing a data foundation for the generation of subsequent published content. Simultaneously, by incorporating a target publishing time into the product configuration data, a clear time scheduling basis is established. By receiving target event messages from the configuration end and responding to these messages, product configuration data and product description information are extracted from the target database. This transforms the state change of updating product configuration data into a technical signal that can be processed asynchronously, decoupling the publishing process from configuration data updates. This enables a rapid response from configuration completion to publishing readiness, improving content publishing efficiency. Furthermore, by dynamically acquiring the latest product configuration data and product information from the target database to generate push content, the accuracy and completeness of the published content are ensured.

[0087] Based on the above embodiments, refer to Figure 4The diagram illustrates the interaction of the content publishing method. Product configuration parameters can be freely constructed or configured from multiple dimensions, such as product type, custom prompts, inventory limits, description images, and product priority. Based on a preset configuration template, structured configuration data is generated according to at least one product configuration parameter; this structured configuration data is then used as the product configuration data for the product to be published. The product configuration data is validated for validity; if validation passes, a Kafka event message is generated based on the product configuration data and sent to the configuration endpoint. The business system on the configuration endpoint, responding to the target event message, extracts the product configuration data and product description information from the target database; based on rule requests, it generates push content according to the product configuration data and product description information. The push content is then published to the client according to the target publication time.

[0088] Based on the above embodiments, such as Figure 5 The diagram shown is a sequence diagram of the content publishing method, which includes the following steps:

[0089] S501: The configuration terminal obtains at least one product configuration parameter of the product to be released.

[0090] S502: The configuration end generates structured product configuration data based on a preset configuration template and at least one product configuration parameter. The product configuration data includes the target release time.

[0091] S503: The configuration terminal stores the product configuration data into the target database and verifies the validity of the product configuration data.

[0092] S504: If the validity verification passes, the configuration end generates the target event message based on the product configuration data.

[0093] S505: The configuration end sends the target event message to the publishing end.

[0094] S506: The publishing end responds to the target event message and extracts product configuration data and product description information from the target database.

[0095] S507: Based on the rules engine, determine the push strategy according to the product configuration data.

[0096] The push strategy includes at least one of the following: push user type, product release cycle, listing rules, and product push combination.

[0097] S508. Generate push content based on the push strategy and product description information.

[0098] S509. Publish push content according to the target release time.

[0099] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0100] Based on the same inventive concept, this application also provides a content publishing apparatus for implementing the content publishing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more content publishing apparatus embodiments provided below can be found in the limitations of the content publishing method described above, and will not be repeated here.

[0101] In one exemplary embodiment, such as Figure 6 As shown, a content publishing device is provided, including: a first acquisition module 610, a first generation module 620, and a sending module 630, wherein:

[0102] The first acquisition module 610 is used to acquire product configuration data of the product to be released, including the target release time.

[0103] The first generation module 620 is used to store product configuration data into the target database and generate target event messages for the product configuration data; the target database also stores product description information of the product to be published.

[0104] The sending module 630 is used to send the target event message to the publishing end, so that the publishing end responds to the target event message and publishes push content according to the target publishing time;

[0105] The push content is generated by the publishing end from the product configuration data extracted from the target database and the product description information of the product to be published.

[0106] In one embodiment, the first acquisition module 610 includes: a first acquisition unit, configured to acquire at least one product configuration parameter of the product to be released; and a first generation unit, configured to generate structured configuration data based on a preset configuration template and according to the at least one product configuration parameter; and to use the structured configuration data as the product configuration data of the product to be released.

[0107] In one embodiment, the first generation module 620 includes: a verification unit for validating the product configuration data; and a second generation unit for generating a target event message based on the product configuration data if the validity verification passes.

[0108] In one exemplary embodiment, such as Figure 7 As shown, a content publishing device is provided, including: a receiving module 710, an extraction module 720, a second generation module 730, and a publishing module 740, wherein:

[0109] The receiving module 710 is used to receive target event messages sent by the configuration terminal. The target event messages are generated based on the product configuration data of the product to be published obtained by the configuration terminal. The product configuration data includes the target release time. The product configuration database is stored by the configuration terminal into the target database. The target database also stores the product description information of the product to be published.

[0110] The extraction module 720 is used to extract product configuration data and product description information from the target database in response to the target event message;

[0111] The second generation module 730 is used to generate push content based on product configuration data and product description information;

[0112] The publishing module 740 is used to publish push content based on the target publishing time.

[0113] In one embodiment, the second generation module 730 includes: a first determining unit, configured to determine a push strategy based on product configuration data; the push strategy includes at least one of push user type, product release cycle, listing rules, and product push combination; and a third generation unit, configured to generate push content based on the push strategy and product description information.

[0114] In one embodiment, the product to be released includes a target product and a candidate product; the product configuration data includes the target sales volume of the target product; correspondingly, the release module includes: a release unit, used to release the push content corresponding to the target product according to the target release time; a second acquisition unit, used to acquire the actual sales volume of the target product; and a switching unit, used to switch the push content corresponding to the target product to the push content corresponding to the candidate product when the actual sales volume reaches the target sales volume.

[0115] Each module in the aforementioned content publishing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0116] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 8 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a content publishing method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0117] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0118] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0119] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0120] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0121] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0122] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0123] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A content publishing method, characterized in that, Applied to the configuration side, the method includes: Obtain the product configuration data of the product to be released, including the target release time; The product configuration data is stored in the target database, and a target event message is generated for the product configuration data; the target database also stores the product description information of the product to be published. The target event message is sent to the publishing end, so that the publishing end responds to the target event message and publishes push content according to the target publication time; The push content is generated by the publishing end from the target database using product configuration data and product description information of the product to be published.

2. The method according to claim 1, characterized in that, The process of obtaining the product configuration data for the product to be published includes: Obtain at least one product configuration parameter of the product to be published; Based on a preset configuration template, structured configuration data is generated according to at least one product configuration parameter; the structured configuration data is then used as the product configuration data for the product to be released.

3. The method according to claim 1 or 2, characterized in that, The generation of the target event message for the product configuration data includes: The validity of the product configuration data is verified. If the validity verification passes, a target event message is generated based on the product configuration data.

4. A content publishing method, characterized in that, Applied to the publishing end, the method includes: The system receives a target event message sent by the configuration terminal. The target event message is generated based on the product configuration data of the product to be released obtained by the configuration terminal. The product configuration data includes the target release time. The product configuration database is stored by the configuration terminal into the target database. The target database also stores the product description information of the product to be released. In response to the target event message, the product configuration data and product description information are extracted from the target database; Based on the product configuration data and the product description information, push content is generated; The push content is published according to the target publication time.

5. The method according to claim 4, characterized in that, The step of generating push content based on the product configuration data and the product description information includes: Based on the product configuration data, a push strategy is determined; the push strategy includes at least one of the following: push user type, product release cycle, listing rules, and product push combination; Based on the push strategy and the product description information, push content is generated.

6. The method according to claim 4 or 5, characterized in that, The products to be released include target products and candidate products; the product configuration data includes the target sales volume of the target product; correspondingly, the push content is released according to the target release time, including: Based on the target release time, the push content corresponding to the target product is released; Obtain the actual sales volume of the target product; If the actual sales volume reaches the target sales volume, the push content corresponding to the target product will be switched to the push content corresponding to the candidate product.

7. A content publishing device, characterized in that, Configured on the configuration terminal, the device includes: The first acquisition module is used to acquire product configuration data of the product to be released, the product configuration data including the target release time; The first generation module is used to store the product configuration data into the target database and generate a target event message for the product configuration data; the target database also stores product description information of the product to be published. The sending module is used to send the target event message to the publishing end, so that the publishing end responds to the target event message and publishes push content according to the target publishing time; The push content is generated by the publishing end from the target database using product configuration data and product description information of the product to be published.

8. A content publishing device, characterized in that, Configured on the publishing end, the device includes: The receiving module is used to receive target event messages sent by the configuration terminal. The target event messages are generated based on the product configuration data of the product to be published obtained by the configuration terminal. The product configuration data includes the target release time. The product configuration database is stored by the configuration terminal into the target database. The target database also stores the product description information of the product to be published. The extraction module is used to extract the product configuration data and product description information from the target database in response to the target event message; The second generation module is used to generate push content based on the product configuration data and the product description information; The publishing module is used to publish the push content according to the target publishing time.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images