Content publishing method and device, electronic equipment and storage medium

Abstract

The invention provides a content publishing method and device, electronic equipment and a storage medium, and relates to the technical field of data processing and artificial intelligence. The specific implementation scheme is as follows: receiving content publishing request information; obtaining an alternative field set for content generation according to the request information and a field registry; according to the request information, determining a directed acyclic graph (DAG) for content publishing, the DAG comprising nodes corresponding to components participating in content publishing and edges between the nodes, the edges between the nodes representing a dependency relationship between the components participating in content publishing; and generating target content according to the DAG and the alternative field set, and publishing the target content.

Description

Technical Field

[0001] This disclosure relates to the fields of data processing and artificial intelligence, and in particular to a content publishing method, apparatus, electronic device, and storage medium. Background Technology

[0002] The efficiency and stability of a content publishing system directly impact the smoothness of business operations. Currently, the lack of unified standards and specifications for field definition and usage in content publishing systems increases learning and usage costs, and leads to data misuse and loss. Furthermore, the complex interaction logic among multiple components in content publishing systems significantly affects page loading speed and user experience. Summary of the Invention

[0004] This disclosure provides a method, apparatus, electronic device, and storage medium for content publishing.

[0005] According to one aspect of this disclosure, a content publishing method is provided, comprising: receiving content publishing request information; obtaining a set of candidate fields for content generation based on the request information and a field registry; determining a directed acyclic graph (DAG) for content publishing based on the request information, the DAG including nodes corresponding to components participating in content publishing and edges between nodes, the edges between nodes representing dependencies between the components participating in content publishing; generating target content based on the DAG and the set of candidate fields, and publishing the target content.

[0006] According to another aspect of this disclosure, a content publishing apparatus is provided, comprising: a receiving module for receiving content publishing request information; an obtaining module for obtaining a set of candidate fields for content generation based on the request information and a field registry; a determining module for determining a directed acyclic graph (DAG) for content publishing based on the request information, the DAG including nodes corresponding to components participating in content publishing and edges between nodes, the edges between nodes representing dependencies between the components participating in content publishing; and a generating module for generating target content based on the DAG and the set of candidate fields, and publishing the target content.

[0007] According to another aspect of this disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the content publishing method described in one aspect of the above-described embodiment.

[0008] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions thereon, wherein the computer instructions are used to cause the computer to perform the content publishing method described in the above-mentioned embodiment.

[0009] According to another aspect of this disclosure, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the content publishing method described in one aspect of the above-described embodiments.

[0010] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0011] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein: Figure 1 A flowchart illustrating a content publishing method provided in an embodiment of this disclosure; Figure 2 A flowchart illustrating another content publishing method provided in this embodiment of the disclosure; Figure 3 A flowchart illustrating another content publishing method provided in this embodiment of the disclosure; Figure 4 A flowchart illustrating the state transition relationship of nodes provided in this embodiment of the disclosure; Figure 5 This is a flowchart illustrating the content publishing system provided in an embodiment of the present disclosure. Figure 6 A schematic diagram of the component execution flow provided in the embodiments of this disclosure; Figure 7 This is a schematic diagram of the structure of a content publishing device provided in an embodiment of the present disclosure; Figure 8 This is a block diagram of an electronic device used to implement the content publishing method of the embodiments of this disclosure. Detailed Implementation

[0012] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0013] The following description, with reference to the accompanying drawings, outlines a content publishing method, apparatus, electronic device, and storage medium according to embodiments of this disclosure.

[0014] Artificial intelligence (AI) is the study of enabling computers to simulate certain human thought processes and intelligent behaviors (such as learning, reasoning, thinking, and planning). It involves both hardware and software technologies. AI hardware technologies generally include computer vision, speech recognition, natural language processing, and related technologies such as deep learning, big data processing, and knowledge graphs.

[0015] Figure 1 This is a flowchart illustrating a content publishing method provided in an embodiment of this disclosure.

[0016] like Figure 1 As shown, this content publishing method may include: S101, Receive content publishing request information.

[0017] It should be noted that the execution entity of the content publishing method in this disclosure embodiment can be a hardware device with data processing capabilities and / or the necessary software to drive the hardware device. Optionally, the execution entity may include a server, a user terminal, and other smart devices. Optionally, the user terminal includes, but is not limited to, mobile phones, computers, smart voice interaction devices, etc. Optionally, the server includes, but is not limited to, a network server, an application server, or a server of a distributed system, or a server combined with blockchain, etc. This disclosure embodiment does not impose specific limitations.

[0018] In some embodiments, the subject of this disclosure may be an electronic device equipped with a content publishing system.

[0019] In some embodiments, the system can receive content publishing request information sent by a client and content publishing request information sent by a server. Here, "client" and "server" refer to electronic devices that are different from the entity executing this disclosure.

[0020] It should be noted that the executing entity in this disclosure is an electronic device, which can be either a client or a server. The electronic device can receive request information from other clients or other servers. Here, "other clients" and "other servers" refer to clients and servers that are different from the executing entity.

[0021] For example, taking a client sending request information as an example, the client can generate different input parameters based on the user's input information, with each input parameter being a field, and generate request information based on different fields, thereby receiving the request information sent by the client. Optionally, the input information can also be used as request information, and after receiving the request information, the different fields can be determined by parsing the request information.

[0022] In some embodiments, the user's input information may be text content to be published. The user can input text content on the client and generate content publishing request information based on the text content. Furthermore, the user can receive request information sent by the client.

[0023] S102, based on the request information and the field registry, obtain a set of alternative fields for content generation.

[0024] In some embodiments, a field registry refers to a field registry obtained by pre-defining information such as field names, field types, application scope, and field uses for different parameters. The field registry can be used to validate the fields of input parameters in request information to verify the validity of the fields.

[0025] In some embodiments, input parameters are obtained from request information and validated based on a field registry to determine the fields existing in the field registry from the input parameters, and a set of candidate fields is generated based on the fields.

[0026] In some embodiments, the fields in the field registry are registered fields. When it is determined that the field corresponding to the request information exists in the field registry, the field corresponding to the request information can be verified based on the information of the registered fields to verify the completeness, legality, etc. of the field corresponding to the request information.

[0027] In some embodiments, fields that pass validation can be determined from the fields corresponding to the request information, and a set of alternative fields for user content generation can be generated based on the fields that pass validation.

[0028] In some embodiments, the fields corresponding to the request information can be validated based on information such as the field name and field type of the registered fields. If the field name and field type of the field corresponding to the request information are the same as the field name and field type of the registered fields, it can be determined that the field passes the validation.

[0029] In some embodiments, if there are fields that fail validation, alarm information for those fields can be generated, thereby locating the erroneous fields, preventing data contamination, and improving the maintainability and security of the content publishing system.

[0030] S103, Based on the request information, determine the directed acyclic graph (DAG) for content publishing.

[0031] It should be noted that a Directed Acyclic Graph (DAG) consists of nodes and directed edges, and there are no paths that start from a vertex and return to that vertex; that is, there are no closed cycles in a DAG. Directed edges represent unidirectional relationships between nodes.

[0032] The DAG in this embodiment can be generated based on the components participating in content publishing. That is, the DAG includes the nodes corresponding to the components participating in content publishing and the edges between the nodes. The edges between the nodes represent the dependencies between the components participating in content publishing.

[0033] In some embodiments, a component is a reusable, independent module responsible for performing a specific function, such as data reading, content generation, format conversion, and storage.

[0034] In some embodiments, different DAGs can be generated in advance based on different components, and the DAG for content publishing can be determined from the different DAGs according to the request information.

[0035] In some embodiments, when a DAG is applied to content publishing, the DAG can be associated with a publishing template used during content publishing. In other words, there is a correspondence between the DAG and the publishing template.

[0036] In some embodiments, the publishing template for content publishing can be determined based on the request information, and the DAG used for content publishing can be determined based on the above correspondence.

[0037] S104: Generate target content based on DAG and the set of alternative fields, and publish the target content.

[0038] It should be noted that publishing target content involves the collaborative execution of multiple components. The components participating in content publishing can be determined based on the DAG and scheduled so that the components participating in content publishing can process the set of candidate fields to obtain the target content.

[0039] In some embodiments, the processing of the candidate field set by the component involved in content publishing refers to the component involved in content publishing reading and writing fields in the candidate field set to generate the target content.

[0040] In some embodiments, the components involved in content publishing have an execution order. That is, when processing the set of candidate fields, the components involved in content publishing must process the set of candidate fields according to their execution order. If the execution order is incorrect, it may lead to missing data or logical errors.

[0041] In some embodiments, the execution order of components participating in content publishing can be determined based on the dependencies between components represented by the edges between nodes in the DAG.

[0042] For example, according to the DAG, the components involved in content publishing include component A, component B, component C, and component D. Their corresponding execution order is component A, component C, component B, and component D. Then, component A processes the candidate field set first, component C processes the processing result of component A, component B processes the processing result of component C, and component D processes the processing result of component B to obtain the target content.

[0043] It's understandable that components are reusable functional modules, while instances are the specific objects of those components at runtime. Instances of components participating in content publishing can process the set of candidate fields.

[0044] In some embodiments, components participating in content publishing can be instantiated using a constructor to obtain instances of those components. Alternatively, component instances can be dynamically created and managed using a component factory to obtain pre-created instances of components participating in content publishing.

[0045] In some embodiments, by inputting a set of candidate fields into an instance of a component participating in content publishing, the instance of the component participating in content publishing processes the set of candidate fields to obtain the target content.

[0046] In some embodiments, fields in the candidate field set can be formatted to the format to be published, thereby obtaining the target content. Alternatively, multiple fields can be aggregated to obtain new fields, and the target content can be generated based on these new fields.

[0047] Optionally, the target content can be generated from the field using any of the relevant technologies for generating content from the field, and there is no limitation thereto.

[0048] In some embodiments, after obtaining the target content, it can be sent to the client, enabling the client to publish the target content. Alternatively, the location for content publication can be determined, and the target content can be published at that location.

[0049] It should be noted that the executing entity of this disclosure may be an electronic device equipped with a content publishing system. The content publishing system receives request information and generates a set of candidate fields and determines the DAG within the content publishing system. Based on the set of candidate fields and the DAG, the target content is generated and published by the content publishing system.

[0050] According to the content publishing method provided in this disclosure, a content publishing request information is received, and a set of candidate fields for content generation is obtained based on the request information and a field registry. A Directed Acyclic Graph (DAG) for content publishing is determined, and target content is generated and published based on the DAG and the set of candidate fields. Therefore, this solution can filter the set of candidate fields based on the field registry, which improves the accuracy and consistency of the set of candidate fields, helps improve the accuracy of generating target content based on the set of candidate fields, and avoids interference from invalid fields. Generating target content based on the directionality of the DAG can improve the system's execution efficiency and response speed, thereby enhancing user experience and content publishing efficiency.

[0051] Figure 2 This is a flowchart illustrating another content publishing method provided in an embodiment of this disclosure.

[0052] like Figure 2 As shown, this content publishing method may include: S201, Receive content publishing request information.

[0053] The details of step S201 can be found in the above embodiments and will not be repeated here.

[0054] S202, parse the request information and extract input parameters from different components of the request information to obtain a parameter set.

[0055] In some embodiments, by parsing the request information according to its structure, the request information can be parsed into different components. These different components may include: request header, request path, request query, and request body.

[0056] In some embodiments, different input parameters can be extracted by extracting parameters from the request information of different constituent departments. For example, request header parameters can be extracted from the Header, path parameters from the Path, and query parameters from the Query.

[0057] Furthermore, by structuring the extracted input parameters and storing them in the form of fields, a parameter set can be obtained.

[0058] S203, Based on the field registry, identify the fields in the parameter set to obtain a set of candidate fields.

[0059] In some embodiments, a field registry is obtained by pre-defining parameters and registering them as fields, wherein the field registry includes registered fields. Parameters can be obtained from a parameter library containing different parameters, and the parameters can be defined and registered.

[0060] In some embodiments, information such as field name, field type, field scope, field category, and field purpose can be defined. The field scope indicates the type of resource in which the field is used, such as text / images, videos, short videos, or dynamic content.

[0061] Field categories represent the classification of fields. Their purpose is to group fields for easier management and to avoid excessive clutter caused by flattening all fields. Examples include basic general information about the content, information about the content publisher, and information about the publishing device.

[0062] In some embodiments, it can also be defined whether a field is mandatory. Mandatory means the parameter must be included in the request. If the request information does not include the field corresponding to the parameter, an error is reported. It can also be defined whether a field undergoes strict validation. If so, an error is reported if validation fails; otherwise, it is ignored and a zero value is assigned.

[0063] In some embodiments, all fields in the parameter set can be identified according to the field registry. By identifying whether the fields in the parameter set correspond to the registered fields in the field registry, the fields in the parameter set can be verified according to the field description information of the registered fields, and finally a candidate field set can be obtained.

[0064] In this embodiment, field validation based on the field description information of the registered fields can improve data accuracy, reduce invalid requests, and further avoid content generation failures due to incorrect fields, thereby improving the efficiency of content publishing.

[0065] In some embodiments, by iterating through the fields in the parameter set and mapping the currently traversed field to the field registry, the registered field corresponding to the currently traversed field is determined from the field registry.

[0066] By obtaining information such as the field name, field type, field application scope, field category, and field purpose of the registered fields as field description information, the currently traversed fields can be validated based on the field description information of the registered fields to obtain a set of candidate fields.

[0067] In some embodiments, it can be verified whether the description information of the currently traversed field is consistent with the description information of the registered field. If they are consistent, it can be determined that the currently traversed field has passed the verification. If they are inconsistent, it can be determined that the currently traversed field has failed the verification.

[0068] In some embodiments, in response to the current traversed field failing the validation, the current traversed field is determined to be a field in the error field set, and the error field set is recorded and / or an error alarm is triggered.

[0069] In some embodiments, if the field corresponding to the currently traversed field does not exist in the field registry, the field may be recorded and / or an error alarm may be triggered.

[0070] In other words, in response to the absence of a registered field corresponding to the currently traversed field in the field registry, the currently traversed field is determined to be an unknown field, and the unknown field is recorded and / or monitored and alarmed.

[0071] In this embodiment, by recording and / or alerting the error field and location field, clear error feedback can be provided to help users correct the request information, thereby improving the user experience.

[0072] For example, the parameter set includes field 1, field 2, and field 3. If fields 1 and 2 can be identified from the field registry as corresponding registered fields 1 and 2, then field description information 1 and field description information 2 for each of registered fields 1 and 2 can be obtained. If no registered field corresponding to field 3 exists in the field registry, then field 3 can be determined to be an unknown field.

[0073] If field 1 passes the validation of field description information 1, field 1 can be determined to be a field in the candidate field set; if field 2 fails the validation of field description information 2, field 2 can be determined to be a field in the error field set.

[0074] S204, Based on the request information, determine the DAG used for content publishing.

[0075] S205: Generate target content based on the DAG and the set of alternative fields, and publish the content.

[0076] The details of steps S204-S205 can be found in the above embodiments and will not be repeated here.

[0077] According to the content publishing method provided in this disclosure, by parsing the request information, the input parameters in the request information can be obtained, and a parameter set can be generated based on the input parameters. The fields in the parameter set can be identified based on the field registry to obtain a set of candidate fields for content generation. This method can verify the fields in the parameter set and use the fields that pass the verification as fields in the set of candidate fields, thereby improving the consistency and accuracy of the fields.

[0078] Figure 3 This is a flowchart illustrating another content publishing method provided in an embodiment of this disclosure.

[0079] like Figure 3 As shown, this content publishing method may include: S301, Receive content publishing request information.

[0080] S302, Based on the request information and the field registry, obtain a set of alternative fields for content generation.

[0081] The details of steps S301-S302 can be found in the above embodiments and will not be repeated here.

[0082] S303, Based on the request information, determine the DAG used for content publishing.

[0083] In some embodiments, different DAGs can be generated in advance based on different components and the dependencies between different components, and the DAG for content publishing can be determined from the different DAGs according to the request information.

[0084] In some embodiments, the DAG is associated with the publishing template used when publishing content. That is, there is a correspondence between the DAG and the publishing template. By obtaining the correspondence between the DAG and the publishing template, and querying this correspondence based on the publishing template used when publishing content, the DAG used for content publishing can be determined.

[0085] In some embodiments, determining the DAG for content publishing based on the publishing template enables the use of different components in different scenarios to generate published content, thereby improving the adaptability of content publishing.

[0086] In some embodiments, the content publishing type can be determined based on the request information, and the corresponding publishing template can be determined based on the content publishing type. Optionally, request information can be generated based on the content publishing type. For example, by monitoring user operations, if it is detected that the user selects type 1 for content publishing, type 1 can be determined as the content publishing type, and type 1 and the text information to be published can be used as the request information.

[0087] In some embodiments, the correspondence between publishing templates and DAGs is predetermined, so that the DAG for content publishing can be determined based on the corresponding publishing template. That is, the correspondence is queried based on the corresponding publishing template to determine the DAG for content publishing.

[0088] S304. Determine the topological order of components participating in content publishing based on their dependencies.

[0089] In some embodiments, the edges in the DAG represent the dependencies between components participating in content publishing. The components participating in content publishing can be sorted according to the dependencies to obtain the topological order among the components participating in content publishing.

[0090] In some embodiments, the dependencies between components involved in content publishing can be one component depending on multiple components, or multiple components depending on one component. In such cases, the topological order determined by the dependencies is not unique, but the topological order satisfies the dependencies.

[0091] For example, if the nodes in the DAG include A, B, C, and D, and their dependencies are ABD and ACD, then the topological order among the components participating in content publishing is A, B, C, D or A, C, B, D.

[0092] S305 schedules components involved in content publishing from the component factory based on topology order.

[0093] In some embodiments, the component factory is used to dynamically create and manage component instances, enabling the monitoring and management of component performance and ensuring the stable operation of the system.

[0094] In some embodiments, the topology order can indicate the components participating in content publishing. The components to be scheduled for content publishing can be determined based on the topology order, and the components participating in content publishing can be scheduled from the component factory according to the topology order.

[0095] In some embodiments, in order to ensure the efficiency, reliability and smoothness of component execution, the components participating in content publishing can be scheduled when all components are in the ready state, which can avoid process interruption due to component abnormalities.

[0096] By identifying the state of the component to be scheduled for content publishing, and in response to the component being in a ready state, the component to be scheduled for content publishing is scheduled from the component factory.

[0097] In some embodiments, the state of the component currently scheduled to participate in content publishing is in the ready state, which means that the component on which the component currently scheduled to participate in content publishing depends is in the successful state.

[0098] In some embodiments, the other components that the component currently scheduled to publish the content depends on can be determined based on the dependency relationship. By monitoring the status of other components, in response to the fact that the status of the other dependent components is in a successful state, the status of the components participating in the content can be determined to be in a ready state.

[0099] In this context, the ready state of a component refers to the component meeting its own startup conditions, such as resources being ready and configuration loading being complete. The successful state of a component refers to the component completing as expected.

[0100] Understandably, after a component is executed, its state can be either a success state or a failure state. A success state indicates that the component has executed successfully, while a failure state indicates that the component has failed.

[0101] Taking the execution of task 1 as an example, if component 1 fails to complete task 1, the state of component 1 is changed to the failure state; if component 1 completes task 1, the state of component 1 is changed to the success state.

[0102] In some embodiments, the state of components involved in content publishing can be determined by monitoring the state of nodes in the DAG. During the generation of target content, the state of nodes in the DAG is monitored, and the state of nodes is switched according to the node state machine.

[0103] In some embodiments, by switching the state of a node and using that state as the state of the component participating in content publishing, flow control of the component can be achieved, ensuring that the component executes in a successful state, thereby improving the efficiency of target content generation.

[0104] Figure 4 This is a flowchart illustrating the state transition relationships of nodes provided in this embodiment of the disclosure. The node states include: Waiting, Ready, Doing, Successed, and Failed.

[0105] Specifically, for the node currently scheduled to participate in content publishing, if it is in Waiting, it means that it is waiting for the node it depends on to complete execution; if it is in Ready, it means that the node it depends on has completed but has not yet executed; if it is in Doing, it means that it is executing; if it is in Succeed, it means that its execution was ultimately successful; if it is in Failed, it means that its execution was ultimately unsuccessful.

[0106] Let node 1 be the node currently scheduled to participate in content publishing. When node 1 is in the Waiting state, it waits for the nodes it depends on to finish executing. After the nodes it depends on finish executing, node 1 is in the Ready state and can then execute. If node 1 executes successfully, its state is changed to Successed; if node 1 fails to execute, its state is changed to Failed.

[0107] S306, Generate instances of the scheduled components that participate in content publishing.

[0108] It should be noted that a component is a reusable functional module, while an instance is a specific object of the component at runtime.

[0109] In some embodiments, the scheduled component for content publishing can be instantiated through a constructor to obtain an instance of the scheduled component for content publishing.

[0110] In some embodiments, the component factory has the function of creating instances, and can also dynamically create component instances to obtain pre-created instances of components that are scheduled to participate in content publishing.

[0111] S307, execute an instance of the component participating in content publishing, process the set of candidate fields, and generate the target content.

[0112] In some embodiments, to enable components to interact with other components, interfaces can be defined for instances of components participating in content publishing to clarify the component's inputs and outputs. For example, the component's interface may include basic interfaces, functional interfaces, etc.

[0113] In some embodiments, in order for instances of components participating in content publishing to process the set of candidate fields, instance input parameters that meet the interface requirements can be generated based on the set of candidate fields, and the instance of the component participating in content publishing can process the instance input parameters, thereby decoupling data and components and reducing the complexity of component interaction.

[0114] In some embodiments, fields in the candidate field set can be encapsulated and abstracted to obtain instance input parameters that match the component participating in content publishing. The instance input parameters are then processed by executing an instance of the component participating in content publishing to obtain the execution result of the instance of the component participating in content publishing, which serves as the target content.

[0115] In some embodiments, instance input parameters must conform to the requirements of the component interface. This can be achieved by determining the interface corresponding to the component participating in content publishing, and by encapsulating and abstracting the fields in the candidate field set according to the interface corresponding to the component participating in content publishing, thereby obtaining instance input parameters that conform to the interface requirements.

[0116] In some embodiments, components participating in content publishing with the same topological order can also be identified from the topological order. Here, "same topological order" means that there are no dependencies between components, and the preceding component of each component depends on the same component.

[0117] For example, if there are components A, B, and C, and components B and C both depend on component A, but components B and C have no dependency relationship, it can be determined that components B and C have the same topological order.

[0118] In some embodiments, to improve resource utilization and the efficiency of content generation, components with the same topological order that participate in content publishing can be processed in parallel to ensure rapid generation of published content, thereby improving the user experience.

[0119] In some embodiments, multiple components with the same topological order for participating in content publishing can be scheduled from the component factory based on topological order, and the candidate field set can be processed in parallel through instances of the multiple scheduled components for participating in content publishing.

[0120] It should be noted that parallel processing of the candidate field set also involves determining the instance input parameters that meet the requirements of the corresponding component interface based on the candidate field set, and then processing the instance input parameters by executing multiple instances of the components participating in content publishing with the same topological order in parallel to obtain the target content.

[0121] In some embodiments, during parallel processing, system resources can be allocated to instances of multiple components participating in content publishing through load balancing strategies, thereby achieving reasonable allocation of system resources, avoiding overload of a single component, and ensuring efficient operation of the system.

[0122] S308, Publish the target content.

[0123] The details of step S308 can be found in the above embodiments and will not be repeated here.

[0124] According to the content publishing method provided in this disclosure, the topological order of the components participating in content publishing is determined by the dependencies between them indicated in the DAG (Directed Acyclic Graph). Based on this topological order, the components participating in content publishing are scheduled from the component factory. Instances of the scheduled components are generated and executed to process a set of candidate fields, ultimately generating the target content. Determining the topological order based on the dependencies between the components and scheduling them accordingly efficiently and correctly manages the dependencies between multiple components, optimizes the correctness of the content publishing process, avoids data loss due to execution order issues, and improves the efficiency of content publishing.

[0125] Based on the above embodiments, a content publishing system can also be determined based on the content publishing method of the present disclosure embodiments. That is, the content publishing system can execute the content publishing method of the present disclosure embodiments to generate the target content.

[0126] For example, a content publishing system may include a DAG engine module, which is responsible for scheduling and executing different functional components. In order to ensure the efficient operation of the system, the components can also be monitored and optimized in real time to ensure the stability and reliability of the system operation.

[0127] In some embodiments, the performance of components in a content publishing system can be monitored, at least one performance parameter among the component's execution time, resource consumption, and call frequency can be obtained, and a performance report of the component can be generated based on at least one performance parameter.

[0128] Furthermore, performance optimization information can be generated based on the component's performance report, allowing for optimization of the content publishing system. This performance optimization information can include suggested optimization strategies.

[0129] In some embodiments, anomalies during component execution can also be monitored, and abnormal conditions of the components can be monitored in real time. In response to an anomaly, automatic recovery operations and / or alarm messages are executed on the component, thereby ensuring the stability and reliability of the system.

[0130] In some embodiments, in order to reflect the usage of fields and adjust and optimize them in a timely manner to improve the performance and data quality of the content publishing system, the field registry can also be monitored in real time.

[0131] In some embodiments, fields in the field registry can be monitored to obtain field usage data. Optionally, visualization tools can be used to visualize the field usage data to help users understand the field's usage.

[0132] In some embodiments, anomaly and redundancy monitoring can also be performed on the fields in the field registry. When an anomaly is detected in any field, an alert can be issued to adjust the field in a timely manner and avoid errors when determining the set of candidate fields based on the field registry in the future.

[0133] When redundant fields are detected, suggestions for cleanup and optimization are provided to improve system performance and data quality.

[0134] In some embodiments, the input and output of fields in the field registry can also be monitored to monitor the data integrity and consistency of the fields and avoid system errors caused by data anomalies.

[0135] Based on the above embodiments, the present disclosure embodiments can be used to explain and illustrate the content publishing system, wherein the content publishing system includes a field processing module and a DAG engine module.

[0136] The field processing module is the foundation of the content publishing system, responsible for managing, monitoring, and optimizing various fields submitted by developers. This module is mainly divided into two parts: field classification management and definition, and the implementation of field monitoring capabilities.

[0137] The field classification management and definition features can be developed using a flexible field classification mechanism, allowing developers to customize field types and attributes. This mechanism will support diverse application scenarios and meet the specific needs of different developers in their document publishing.

[0138] It also allows for dynamic configuration of field attributes, enabling developers to dynamically configure field attributes in different application scenarios, including field type, default value, constraints, etc., in order to better adapt to changing business needs.

[0139] The field category management and definition features can also introduce a hierarchical field category structure, making field categorization clearer and more intuitive. By dividing fields hierarchically through a tree structure, developers can easily manage and search them, and fields can be shared across different categories, providing a flexible field reuse mechanism, avoiding redundant definitions, and improving the efficiency of field management.

[0140] Field monitoring capabilities can be implemented through real-time monitoring, enabling real-time tracking of the usage of each field and providing information such as usage frequency and abnormal data. Visualization tools such as dashboards can then help developers understand field usage in a timely manner.

[0141] When an abnormality occurs in the use of a field, the system will automatically detect it and issue an alert, helping developers to adjust the field settings in a timely manner and prevent potential problems from occurring.

[0142] It can also rigorously monitor the input and output of fields to ensure the integrity and consistency of data in each field, avoiding system errors caused by data anomalies. By monitoring the frequency and content of field usage, redundant fields in the system can be identified, and suggestions for cleanup and optimization can be provided to improve system performance and data quality.

[0143] In some embodiments, the field processing module can also generate a field registry and determine a set of candidate fields based on the request information and the field registry. The process of determining the set of candidate fields can be found in the above embodiments and will not be repeated here.

[0144] The DAG engine module, as the core logic processing module of the content publishing system, is responsible for scheduling and executing various functional components in the content publishing process. The focus of this module is on component monitoring and the implementation of the DAG scheduling component.

[0145] The DAG engine module includes component monitoring and component scheduling capabilities.

[0146] Component monitoring capabilities allow for detailed monitoring of the performance of each component, generating performance analysis reports. These reports include component execution time, resource consumption, and call frequency, helping developers optimize performance.

[0147] It can also automatically identify system performance bottlenecks by monitoring component performance and provide optimization suggestions to ensure stable system operation under high load.

[0148] By establishing a comprehensive anomaly monitoring mechanism, various abnormal situations that may occur during component execution are monitored and recorded in real time. When an anomaly occurs, the system can automatically perform recovery operations and promptly send alarm notifications to operations and maintenance personnel, ensuring the stability and reliability of the system.

[0149] Component scheduling capabilities can employ a Directed Acyclic Graph (DAG) as the scheduling model to optimize the execution order and dependencies between components. The DAG model can intuitively describe the dependency chains between components, ensuring the correctness of task execution.

[0150] It also supports dynamic adjustment of the DAG structure, allowing optimization of the scheduling order and dependencies of components without affecting system operation.

[0151] Parallel processing of process components is achieved through DAG scheduling, maximizing system resource utilization and improving overall processing efficiency while ensuring data consistency. During parallel processing, a load balancing strategy is introduced to rationally allocate system resources, avoid overloading any single component, and ensure efficient system operation.

[0152] The generation of target content using the DAG scheduling component can be found in the above embodiments, and will not be repeated here.

[0153] In some embodiments, after the design and development of each module are completed, the modules can be integrated to perform overall system integration and testing. This allows for testing of interface compatibility, data consistency, and overall system performance between modules. Through rigorous testing processes, it ensures that the system can operate stably and efficiently under various usage scenarios.

[0154] Module interfaces can be integrated to ensure consistent interface standards and smooth, error-free data transmission between sub-modules. Interface testing verifies compatibility and data consistency between modules.

[0155] Furthermore, functional integration testing can be conducted to test the various functions of the integrated system, ensuring that each module can function properly within the overall system.

[0156] System testing can be performance testing. By conducting comprehensive performance tests on the system, we can evaluate its performance in scenarios such as high concurrency and massive data processing, and identify potential performance bottlenecks.

[0157] System testing can also be security testing. By conducting rigorous security tests, we can ensure that the system meets relevant standards and requirements in terms of data security and access control.

[0158] System testing can also be user experience testing. Through user experience testing, feedback from users on system operation processes, interface design, and other aspects can be collected, and reasonable adjustments can be made to improve user satisfaction.

[0159] Figure 5 A flowchart illustrating the content publishing system provided in this embodiment of the disclosure. Figure 5 It includes a user input module, a field processing module, a DAG engine module, and a log module.

[0160] The content input module can receive content publishing requests, and the field processing module can parse, validate, and construct parameters for the request information to generate a parameter set. Based on the field registry and the parameter set, a set of candidate fields can be determined.

[0161] By inputting the request information and the set of alternative fields into the DAG engine module, the DAG instance constructs a publishing template based on the request information, determines the DAG for content publishing, and determines the topological order of the components participating in content publishing based on the dependencies between the components participating in content publishing as indicated by the DAG. The components participating in content publishing are then scheduled from the component factory according to the topological order, and instances of the components that are scheduled to participate in content publishing are generated.

[0162] Figure 5 The components involved in content publishing include Component 1, Component 2, Component 3, and Component 4. Component 4 has dependencies on Component 1 and Component 2. Figure 5 The topological order in the data includes: Component 1-Component 4, Component 2-Component 4 and Component 3.

[0163] The target content is generated by processing the set of candidate fields by executing instances of Component 1, Component 2, Component 3, and Component 4 in topological order.

[0164] During the operation of the field processing module and the DAG engine module, the running data can be sent to the log module to generate the running log of the content publishing system.

[0165] Based on the above embodiments, the execution flow of the components can also be explained and illustrated in this disclosure. Figure 6 This is a schematic diagram of the component execution flow provided in the embodiments of this disclosure. Figure 6 It includes component 1, component 2, and component n, and its topological order is component 1-component 2-component n.

[0166] For component 1, it executes the preceding function 1, global rule processing, and rule processing 1 before reaching the synchronization point. After all other components' execution paths have reached this point, it continues with the subsequent process to ensure the consistency and synchronization of data or processing states. Then, it uniformly enters rule processing 2 and subsequent rule processing 1. When component 1 executes rule processing 1, it can exit the execution flow of component 1 and proceed with the execution flow of component 2.

[0167] For component 2, it is executed in the following order: pre-execution function 2, global rule processing, rule processing 3, rule processing 4, and subsequent rule processing 2. When component 2 executes rule processing 4, it can stop executing component 2 and end the entire topology sequential execution process.

[0168] For component n, it is executed according to the process of pre-execution function n, global rule processing, and rule processing n.

[0169] Corresponding to the content publishing methods provided in the above embodiments, one embodiment of this disclosure also provides a content publishing device. Since the content publishing device provided in this disclosure corresponds to the content publishing methods provided in the above embodiments, the implementation methods of the above content publishing methods are also applicable to the content publishing device provided in this disclosure, and will not be described in detail in the following embodiments.

[0170] Figure 7 This is a schematic diagram of the structure of a content publishing device provided in an embodiment of this disclosure.

[0171] like Figure 7As shown, the content publishing device 700 of this embodiment includes a receiving module 701, an acquiring module 702, a determining module 703, and a generating module 704.

[0172] Receiver module 701 is used to receive content publishing request information; The acquisition module 702 is used to acquire a set of candidate fields for content generation based on the request information and the field registry. The determination module 703 is used to determine a directed acyclic graph (DAG) for content publishing based on the request information. The DAG includes nodes corresponding to the components participating in content publishing and edges between the nodes. The edges between the nodes represent the dependencies between the components participating in content publishing. The generation module 704 is used to generate target content based on the DAG and the set of candidate fields, and to publish the target content.

[0173] In one embodiment of this disclosure, the acquisition module 702 is further configured to: parse the request information, extract input parameters from different components of the request information to obtain a parameter set; and identify fields in the parameter set according to the field registry to obtain the candidate field set.

[0174] In one embodiment of this disclosure, the acquisition module 702 is further configured to: traverse the fields in the parameter set; map the currently traversed field to the field registry, determine the registration field corresponding to the currently traversed field from the field registry; and verify the currently traversed field according to the field description information of the registration field to obtain the candidate field set.

[0175] In one embodiment of this disclosure, the acquisition module 702 is further configured to: determine that the currently traversed field is a field in the error field set in response to the current traversed field failing the validation; and record and / or issue an error alarm for the error field set.

[0176] In one embodiment of this disclosure, the acquisition module 702 is further configured to: in response to the absence of a registered field corresponding to the currently traversed field in the field registry, determine that the currently traversed field is an unknown field, and record and / or monitor and alarm the unknown field.

[0177] In one embodiment of this disclosure, the determining module 703 is further configured to: determine the content publishing type based on the request information; determine the corresponding publishing template based on the content publishing type; and determine the DAG of the content publishing based on the corresponding publishing template.

[0178] In one embodiment of this disclosure, the generation module 704 is further configured to: determine the topological order of the components participating in content publishing based on the dependencies between the components participating in content publishing; schedule the components participating in content publishing from the component factory based on the topological order; generate an instance of the scheduled component participating in content publishing; and execute the instance of the component participating in content publishing to process the set of candidate fields to generate the target content.

[0179] In one embodiment of this disclosure, the generation module 704 is further configured to: encapsulate and abstract the fields in the candidate field set to obtain instance input parameters that match the component participating in content publishing; execute an instance of the component participating in content publishing, process the instance input parameters, and obtain the execution result of the instance of the component participating in content publishing.

[0180] In one embodiment of this disclosure, the generation module 704 is further configured to: determine the interface corresponding to the component participating in content publishing; and encapsulate and abstract the fields in the candidate field set according to the interface corresponding to the component participating in content publishing to obtain instance input parameters that meet the interface requirements.

[0181] In one embodiment of this disclosure, the generation module 704 is further configured to: schedule multiple components participating in content publishing with the same topological order from the component factory based on the topological order; and perform parallel processing on the candidate field set through instances of the multiple scheduled components participating in content publishing.

[0182] In one embodiment of this disclosure, the generation module 704 is further configured to: allocate system resources to instances of multiple components participating in content publishing through a load balancing strategy.

[0183] In one embodiment of this disclosure, the generation module 704 is further configured to: determine the component to be scheduled for participating in content publishing based on the topology order; identify the state of the component to be scheduled for participating in content publishing; and, in response to the component to be scheduled for participating in content publishing being in a ready state, schedule the component to be scheduled for participating in content publishing from the component factory.

[0184] In one embodiment of this disclosure, the generation module 704 is further configured to: determine, based on the dependency relationship, other components that the component currently scheduled to publish the participating content depends on; and, in response to the fact that the states of the other dependent components are all in a successful state, determine that the state of the respective components of the participating content is a ready state.

[0185] In one embodiment of this disclosure, the generation module 704 is further configured to: monitor the state of nodes in the DAG during the generation of the target content, and switch the state of the nodes according to the node state machine.

[0186] In one embodiment of this disclosure, the generation module 704 is further configured to: monitor the performance of components in the content publishing system, obtain at least one performance parameter among the component's execution time, resource consumption, and call frequency, and generate a performance report for the component based on the at least one performance parameter; generate performance optimization information for the component based on the component's performance report; monitor anomalies during the component's execution process and monitor the component's anomalies in real time; and, in response to an anomaly, perform automatic recovery operations and / or alarm information for the component.

[0187] In one embodiment of this disclosure, the generation module 704 is further configured to: monitor the fields in the field registry to obtain usage data of the fields; monitor the fields in the field registry for anomalies and redundancy; and monitor the input and output of the fields in the field registry.

[0188] According to the content publishing apparatus provided in this disclosure, a content publishing request information is received, and a set of candidate fields for content generation is obtained based on the request information and a field registry. A Directed Acyclic Graph (DAG) for content publishing is determined, and target content is generated and published based on the DAG and the set of candidate fields. Therefore, this solution can filter the set of candidate fields based on the field registry, which can improve the accuracy and consistency of the set of candidate fields, thus helping to improve the accuracy of generating target content based on the set of candidate fields and avoiding interference from invalid fields. Generating target content based on the directionality of the DAG can improve the system's execution efficiency and response speed, thereby enhancing user experience and content publishing efficiency.

[0189] The acquisition, storage, and application of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0190] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0191] Figure 8A schematic block diagram of an example electronic device 800 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0192] like Figure 8 As shown, device 800 includes a computing unit 801, which can perform various appropriate actions and processes based on computer programs / instructions stored in read-only memory (ROM) 802 or loaded into random access memory (RAM) 803 from storage unit 806. RAM 803 may also store various programs and data required for the operation of device 800. The computing unit 801, ROM 802, and RAM 803 are interconnected via bus 804. Input / output (I / O) interface 805 is also connected to bus 804.

[0193] Multiple components in device 800 are connected to I / O interface 805, including: input units 806 such as keyboard, mouse, etc.; output units 807 such as various types of displays, speakers, etc.; storage units 808 such as disks, optical disks, etc.; and communication units 809 such as network cards, modems, wireless transceivers, etc. Communication unit 809 allows device 800 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0194] The computing unit 801 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as content publishing methods. For example, in some embodiments, the content publishing method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 806. In some embodiments, part or all of the computer program / instructions may be loaded and / or installed on device 800 via ROM 802 and / or communication unit 809. When the computer program / instructions are loaded into RAM 803 and executed by the computing unit 801, one or more steps of the content publishing method described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the content publishing method by any other suitable means (e.g., by means of firmware).

[0195] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include: implementations in one or more computer programs / instructions that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transferring data and instructions to the storage system, the at least one input device, and the at least one output device.

[0196] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0197] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0198] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0199] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), the Internet, and blockchain networks.

[0200] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. The client-server relationship is created by computer programs / instructions running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0201] It should be understood that the various forms of processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this document does not impose any restrictions.

[0202] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A content publishing method, wherein, The method includes: Receive content publishing request information; Based on the request information and the field registry, obtain a set of candidate fields for content generation; Based on the request information, a directed acyclic graph (DAG) for content publishing is determined. The DAG includes nodes corresponding to the components participating in content publishing and edges between the nodes. The edges between the nodes represent the dependencies between the components participating in content publishing. Based on the DAG and the set of candidate fields, target content is generated and published.

2. The method according to claim 1, wherein, The step of obtaining a set of candidate fields for content generation based on the request information and the field registry includes: The request information is parsed, and input parameters are extracted from different components of the request information to obtain a parameter set; Based on the field registry, the fields in the parameter set are identified to obtain the candidate field set.

3. The method according to claim 2, wherein, The step of identifying fields in the parameter set according to the field registry to obtain the candidate field set includes: Iterate through the fields in the parameter set; Map the currently traversed field to the field registry, and determine the registration field corresponding to the currently traversed field from the field registry; Based on the field description information of the registered fields, the currently traversed fields are validated to obtain the set of candidate fields.

4. The method according to claim 3, wherein, The method further includes: In response to the fact that the currently traversed field fails the validation, it is determined that the currently traversed field is a field in the set of error fields; Record and / or alarm the error field set.

5. The method according to claim 3, wherein, The method further includes: In response to the absence of a registered field corresponding to the currently traversed field in the field registry, the currently traversed field is determined to be an unknown field, and the unknown field is recorded and / or monitored and alarmed.

6. The method according to claim 1, wherein, The step of determining the directed acyclic graph (DAG) for content publishing based on the request information includes: Based on the request information, determine the content publishing type; Based on the content publishing type, determine the corresponding publishing template; Based on the corresponding publishing template, determine the DAG for the content publishing.

7. The method according to any one of claims 1-6, wherein, The step of generating target content based on the DAG and the set of candidate fields includes: The topological order of the components participating in content publishing is determined based on the dependencies between them. Based on the aforementioned topological order, the components participating in content publishing are scheduled from the component factory; Generate instances of the components that participate in content publishing and are scheduled to be published; An instance of the component participating in content publishing is executed to process the set of candidate fields to generate the target content.

8. The method according to claim 7, wherein, The instance of the component that executes the content publishing process processes the set of candidate fields to generate the target content, including: The fields in the candidate field set are encapsulated and abstracted to obtain instance input parameters that match the components participating in content publishing; Execute an instance of the component that participates in content publishing, process the input parameters of the instance, and obtain the execution result of the instance of the component that participates in content publishing.

9. The method according to claim 8, wherein, The process of encapsulating and abstracting the fields in the candidate field set to obtain instance input parameters that match the components participating in content publishing includes: Determine the interface corresponding to the component participating in content publishing; Based on the interface corresponding to the component participating in content publishing, the fields in the candidate field set are encapsulated and abstracted to obtain instance input parameters that meet the interface requirements.

10. The method according to claim 7, wherein, The method further includes: Based on the topological order, multiple components with the same topological order participating in content publishing are scheduled from the component factory; The candidate field set is processed in parallel using instances of multiple components participating in content publishing that are scheduled.

11. The method according to claim 7, wherein, The method further includes: System resources are allocated to instances of multiple components participating in content publishing through a load balancing strategy.

12. The method according to claim 7, wherein, The process of scheduling the components participating in content publishing from the component factory based on the topological order includes: Based on the topological order, determine the component participating in content publishing that needs to be scheduled currently; The status of the component to be scheduled for content publishing is identified. In response to the component being scheduled for content publishing being in a ready state, the component to be scheduled for content publishing is scheduled from the component factory.

13. The method according to claim 12, wherein, The step of identifying the state of the component currently scheduled to participate in content publishing, in response to the component currently scheduled to participate in content publishing being in a ready state, includes: Based on the dependencies, determine the other components that the component currently scheduled to participate in content publishing depends on; In response to the fact that the status of the other components on which the content is depended is in a successful state, the status of the respective components involved in the content is determined to be in a ready state.

14. The method according to claim 7, wherein, The method further includes: During the generation of the target content, the state of the nodes in the DAG is monitored, and the state of the nodes is switched according to the node state machine.

15. The method according to claim 7, wherein, The method further includes at least one of the following operations: Monitor the performance of components in the content publishing system, obtain at least one performance parameter among the component's execution time, resource consumption, and call frequency, and generate a performance report for the component based on the at least one performance parameter; Based on the component's performance report, generate performance optimization information for the component; Monitor for anomalies during the execution of the component and monitor the abnormal conditions of the component in real time; In response to an anomaly, the component performs an automatic recovery operation and / or sends an alarm message.

16. The method according to claim 7, wherein, The method further includes at least one of the following operations: Monitor the fields in the registry to obtain usage data for those fields; Perform anomaly and redundancy monitoring on the fields in the registry. Monitor the input and output of the fields in the registry.

17. A content publishing device, wherein, The device includes: The receiving module is used to receive content publishing request information; The acquisition module is used to acquire a set of candidate fields for content generation based on the request information and the field registry. The determination module is used to determine a directed acyclic graph (DAG) for content publishing based on the request information. The DAG includes nodes corresponding to the components participating in content publishing and edges between the nodes. The edges between the nodes represent the dependencies between the components participating in content publishing. The generation module is used to generate target content based on the DAG and the set of candidate fields, and to publish the target content.

18. An electronic device comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method as described in any one of claims 1-16.

19. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-16.

20. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the method of any one of claims 1-16.

Images