System and method for content distribution engine and computing device

Abstract

The invention provides a system and a method for a content distribution engine and computing equipment, and the system comprises a cross-page global state manager which operates at a front end and is used for cross-page communication so as to share state data of each page; the node management module runs at the front end and generates an initialized node tree based on node group configuration configured at the rear end; the node matching module runs at the front end and is used for carrying out real-time matching of the node type and the state data on at least one node submitted by a user and any node on the node tree and judging whether the node group is hit or not; and the distribution module runs at the front end and is used for querying the strategy bound with the node group and the material associated with the strategy after the node group is hit so as to form a corresponding distribution means and distribute the material. According to the technical scheme provided by the invention, cross-page communication and data sharing are realized, and the compatible logic of each page is reduced.

Description

Technical Field

[0001] This invention relates to the field of website operation and deployment, specifically to a system and method for a content distribution engine and a computing device. Background Technology

[0002] A website may contain countless pages representing numerous different work lines. These pages present various dynamic work scenarios that require methods and measures to guide or enhance the user's intended learning. These different pages are assigned to different work lines, personnel, and technologies, and the technical solutions provided for these pages vary considerably.

[0003] In order to provide the same technical solution in these complex operational scenarios while reducing the different impacts on various work lines, there is an urgent need for a cross-page-level operation and deployment solution for centralized convergence and maintenance.

[0004] Therefore, a technical solution is needed to enable cross-page communication and data sharing, reducing the compatibility logic between different pages. Summary of the Invention

[0005] The present invention aims to provide a system, method and computing device for a content distribution engine, enabling cross-page communication and data sharing, and reducing compatibility logic between pages.

[0006] According to one aspect of the present invention, a system for a content distribution engine is provided, comprising:

[0007] A global state manager that runs across pages and is used for cross-page communication to share state data across pages;

[0008] The node management module running on the front end generates an initialized node tree based on the node group configuration configured on the back end. The nodes on the node tree have different node types and status data. The nodes represent the user's movement or operation in the application scenario. The node group includes at least one node connected in series and supports cross-page operation.

[0009] The node matching module running on the front end is used to perform real-time matching of at least one node submitted by the user with any node in the node tree based on the node type and the status data, and to determine whether the node group is matched.

[0010] The distribution module running on the front end is used to query the strategy bound to the node group and the material associated with the strategy after the node group is hit, form a corresponding distribution method and distribute the material, wherein the strategy is the content module for distributing the material.

[0011] According to some embodiments, the global state manager is configured to maintain state data for each page.

[0012] According to some embodiments, when any page updates its state data, the global state manager is notified to update its state.

[0013] When any page needs to obtain the latest status data, it notifies the global status manager to obtain the corresponding status data.

[0014] According to some embodiments, the node matching module performs real-time matching processing based on a streaming engine and supports multiple event combinations based on sequence patterns.

[0015] According to some embodiments, the node matching module running at the front end can be switched to a back end matching mechanism at any time.

[0016] According to some embodiments, the node matching module is further configured as follows:

[0017] Enable and run the page's triggers based on the returned node group configuration;

[0018] If the node group configuration includes the configuration of the operation of the first element, then determine whether the first element exists on the page;

[0019] If the first element exists, the global delegate event determines the operation status of the first element;

[0020] After the operation state of the first element generates a trigger event, the trigger activates the real-time matching.

[0021] According to some embodiments, the backend configuration module running in the backend is used for:

[0022] Generate the node group configuration; and

[0023] Configure the whitelist page. The page will only issue the required node group configuration if there are policy-related options on the page.

[0024] According to some embodiments, the attributes of the strategy include one or more of the following: online time, object group control, traffic allocation, fatigue control, and resource slots.

[0025] According to some embodiments, a pluggable technical service SPI provides the capability to process any stage required.

[0026] According to some embodiments, a data tracking module is used to track data during strategy deployment, and the data tracking has a unified classification at the platform level.

[0027] According to some embodiments, the attributes of the data embedding points include one or more of the following: strategy identifier, experiment identifier, material identifier, SPI service identifier, and matching rules.

[0028] According to another aspect of the present invention, a method for content distribution is provided, comprising:

[0029] Collect and share status data across pages through cross-page communication;

[0030] The node tree is generated based on the node group configuration configured on the backend. The nodes in the node tree have different node types and state data. The nodes represent the user's movement or operation in the application scenario. The node group includes at least one node connected in series and supports cross-page operation.

[0031] The system performs real-time matching of at least one node submitted by the user with any node in the node tree based on the node type and the status data, and determines whether the node group is matched.

[0032] After the node group is hit, the strategy bound to the node group and the material associated with the strategy are queried, a corresponding distribution method is formed and the material is distributed, wherein the strategy is the content module for distributing the material.

[0033] According to another aspect of the present invention, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the method as described in any of the preceding claims.

[0034] According to another aspect of the present invention, a computing device is provided, comprising:

[0035] Processor; and

[0036] A memory storing a computer program that, when executed by the processor, causes the processor to perform the method described in any of the preceding methods.

[0037] According to embodiments of the present invention, a system for a content distribution engine is provided. The system includes: a cross-page global state manager running on the front end, a node management module, a node matching module, and a distribution module. The global state manager is used for cross-page communication to share state data across pages; the node management module generates an initialized node tree based on node group configurations configured in the backend; the node matching module performs real-time matching of user-submitted nodes with any node in the node tree based on node type and state data to determine whether a node group is matched; the distribution module, upon matching a node group, queries the policies bound to the node group and the materials associated with the policies, forms corresponding distribution methods, and distributes the materials. The system of the present invention enables cross-page communication and data sharing, reducing compatibility logic between pages. This solution reduces this intrusion through a more advanced data integration method, making deployment simpler. Compared to existing platforms, the present invention provides a more secure data processing and interface call method, reduces risks, and pays more attention to user experience, achieving more detailed fatigue management at the cross-page level.

[0038] According to some embodiments, this solution's group management system is more mature, possessing a more complete group management system that supports more flexible and precise target group definitions. It enables intelligent adjustment of operational strategies across multiple pages, and employs a higher level of abstraction in terms of decoupling, resulting in better separation of material management and operational logic, thus enhancing the system's flexibility and maintainability.

[0039] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit the invention. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0041] Figure 1 A schematic diagram of a system for a content distribution engine is shown according to an example embodiment.

[0042] Figure 2 A schematic diagram of the overall framework design according to an example embodiment is shown.

[0043] Figure 3 A schematic diagram of a backend service engine according to an example embodiment is shown.

[0044] Figure 4 A flowchart of a method for content distribution according to an example embodiment is shown.

[0045] Figure 5 A block diagram of a computing device according to an exemplary embodiment is shown. Detailed Implementation

[0046] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that the invention will be thorough and complete, and the concept of the exemplary embodiments will be fully conveyed to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0047] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a full understanding of embodiments of the invention. However, those skilled in the art will recognize that the technical solutions of the invention can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of the invention.

[0048] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0049] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0050] It should be understood that although the terms first, second, third, etc., may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another. Therefore, the first component discussed below may be referred to as the second component without departing from the teachings of the present invention. As used herein, the term "and / or" includes all combinations of any one and more of the associated listed items.

[0051] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this invention are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0052] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of exemplary embodiments, and the modules or processes in the drawings are not necessarily essential for implementing the present invention, and therefore cannot be used to limit the scope of protection of the present invention.

[0053] In practical applications, a website contains countless pages across numerous work lines. These pages present many dynamic work scenarios that require methods and measures to guide and enhance users' intended goals. These different pages are assigned to different work lines, personnel, and technologies, and the technical solutions provided for each page vary significantly. To provide a consistent technical solution across these complex work scenarios while minimizing the impact on different work lines, a cross-page-level operational deployment plan is urgently needed for centralized convergence and maintenance.

[0054] To address this, this invention proposes a system and method for content distribution engines, which improves user conversion rates and platform stickiness on e-commerce platforms through precise content strategies and efficient resource allocation. Based on practical experience in intelligent ad delivery, it utilizes data-driven and dynamic adjustments, as well as multi-scenario coverage and synergistic effects.

[0055] Compared with existing technologies, the method of using user-driven offline operation strategies aims to solve problems arising in different operational and technical contexts, and has unique advantages and differences compared with existing platforms.

[0056] Compared to the solution of this invention, existing platforms require additional task tracking by the operator to identify real-time crowds, which increases the complexity and maintenance cost of the system. Existing platforms can only place task interfaces within task materials, potentially posing security risks, and their fatigue management design across pages is inadequate. The existing platform's grouping system is immature, lacking a basic group concept and unable to implement complex exclusion logic. Existing platforms are also incomplete in their cross-page solutions, making it difficult to implement differentiated fatigue management for different pages, and the materials are highly dependent on the task interface, resulting in low decoupling.

[0057] This solution reduces intrusion through more advanced data integration methods, making deployment simpler. In comparison, it offers more secure data processing and API call methods, reducing risk; and it pays greater attention to user experience, achieving more granular fatigue management at the cross-page level. This solution's group management system is more mature, possessing a more comprehensive group management system that supports more flexible and precise target group definitions. It enables intelligent adjustments to operational strategies across multiple pages, and in terms of decoupling, it employs a higher level of abstraction, resulting in better separation of material management and operational logic, enhancing system flexibility and maintainability.

[0058] In summary, this invention innovates a cross-page user flow solution and a backend material and task interface separation solution, which are not found in the industry before. Compared with other platform solutions, it provides a suitable ending solution for each user, taking user satisfaction into consideration.

[0059] Before describing the embodiments of the present invention, some terms or concepts involved in the embodiments of the present invention will be explained.

[0060] SPI (Serial Peripheral Interface Bus) is a Java extension mechanism used to implement modular development.

[0061] An API (Application Programming Interface) is a set of rules and protocols that define how software communicates with each other. Through APIs, different software applications can interact with each other and share data.

[0062] Decoupling refers to reducing the dependencies between different parts of a system, enabling each component of the system to be developed, maintained, and evolved relatively independently.

[0063] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention.

[0064] Figure 1 A schematic diagram of a system for a content distribution engine is shown according to an example embodiment.

[0065] See Figure 1 The system for a content distribution engine of the present invention includes: a cross-page global state manager 101 running on the front end, a node management module 103, a node matching module 105, and a distribution module 107.

[0066] According to some embodiments, a cross-page global state manager 101 running on the front end is used for cross-page communication to share state data between pages.

[0067] According to some embodiments, the global state manager 101 is configured to maintain state data for each page. When any page updates its state data, it notifies the global state manager 101 to update its state; when any page needs to obtain the latest state data, it notifies the global state manager 101 to obtain the corresponding state data.

[0068] According to some embodiments, the node management module 103 running on the front end generates an initialized node tree based on the node group (movement line) configuration configured on the back end. The nodes on the node tree have different node types and state data. The nodes represent the user's movement or operation in the application scenario. The node group includes at least one node connected in series and supports cross-page operation.

[0069] According to some embodiments, the node matching module 105 running at the front end is used to perform real-time matching of at least one node submitted by the user with any node on the node tree based on the node type and the status data, and to determine whether the node group is matched.

[0070] According to some embodiments, the node matching module 105 performs real-time matching processing based on a streaming engine and supports multiple event combinations based on sequence patterns. The node matching module 105 can switch to a backend matching mechanism at any time.

[0071] According to some embodiments, the node matching module 105 is further configured to: enable and register the page's triggers based on the returned node group configuration; if the node group configuration includes the configuration of the operation of the first element, determine whether the page contains the first element; if the first element exists, globally delegate an event to determine the operation state of the first element; after the operation state of the first element generates a trigger event, the trigger activates the real-time matching. The triggers include one or more of the following: page entry / exit triggers, embedded event triggers, DOM first exposure triggers, DOM exposure triggers, page scrolling triggers, and DOM click triggers.

[0072] According to some embodiments, the distribution module 107 running on the front end is used to query the strategy bound to the node group and the material associated with the strategy after the node group is hit, form a corresponding distribution method and distribute the material, wherein the strategy is a content module for distributing the material.

[0073] According to some embodiments, the attributes of the strategy include one or more of the following: online time, object group control, traffic allocation, fatigue control, and resource slots.

[0074] According to some embodiments, the system for the content distribution engine also includes a backend configuration module running on the backend for generating the node group configuration and configuring a whitelist page. The required node group configuration is only issued on the page when there are policy-related options.

[0075] According to some embodiments, the system for the content distribution engine also includes a pluggable technology service SPI, which provides the capabilities required at any stage.

[0076] According to some embodiments, a data tracking module is used to perform data tracking during strategy deployment. The data tracking points have a unified classification at the platform level. The attributes of the data tracking points include one or more of the following: strategy identifier, experiment identifier, material identifier, and SPI service identifier, as well as matching rules.

[0077] According to some embodiments, a user movement mechanism based on a cross-page data sharing scheme provides a highly available, loosely coupled, and accurate audience targeting solution. Under different page backgrounds, the basic data scheme cannot be shared, and data communication and interaction cannot be immediately used, resulting in a broken link in the user movement path. Therefore, this invention provides a system that allows cross-page communication and data sharing. This invention uses a front-end cross-page sharing scheme, establishing a communication bridge between various pages through an injected global state manager. The state of each page is maintained in this global state manager. When any page needs to update its state, it communicates with this global state manager to update the state. Simultaneously, it can also communicate with the global state manager to obtain the latest data when needed.

[0078] The system for a content distribution engine of this invention implements a more advanced data integration method, making deployment simpler, providing a more secure data processing and interface call method, and reducing risks. The system of this invention has a more complete group management system, supporting more flexible and precise target group definitions, and can intelligently adjust operational strategies across multiple pages, resulting in better separation of material management and operational logic, and enhancing the system's flexibility and maintainability.

[0079] Figure 2 A schematic diagram of the overall framework design according to an example embodiment is shown.

[0080] According to some embodiments, initialization is performed during the preparation phase to ensure that all necessary components and services are ready. Middleware is added to handle various triggers and perform validation, logging, and tool delivery. These trigger atoms include event trigger processing, message trigger processing, self-executing trigger processing, policy trigger processing, and policy strict validation processing. During the preparation phase, the content that the overall engine needs to process is registered and injected into various processors at different stages of operation. Each processor has its own internal logic, and different processors adapt to the call processing of each stage. Middleware is also added for mid-process control, allowing for direct monitoring of engine logs, input / output parameters, time consumption, validity, etc.

[0081] According to some embodiments, during the runtime phase, the user movement configuration is obtained from the backend. According to some embodiments, historical nodes can be processed synchronously, synchronizing historical node information to ensure data consistency. Atomic triggers can be added dynamically according to specific job requirements. Atomic triggers include page entry / exit triggers, pre-embedded event triggers, DOM exposure triggers, and pre-embedded scroll triggers, etc.

[0082] According to some implementations, iframes can be registered for global communication, enabling cross-domain communication and ensuring data synchronization between pages. Initialization returns configuration information to the front-end after initialization is complete. A global user movement snapshot is obtained to provide a basis for subsequent judgments. iframe synchronization information is registered to ensure the accuracy of the global movement snapshot.

[0083] The runtime phase is used for engine state initialization. Engine data is acquired from cloud-based configurations and global state data transfers. Cloud-based configurations include a page whitelist; the required motion path configuration will only be issued to the current page if there are only policy-related page selections; otherwise, the data will not be provided. Global state data transfers are used to store the current node state. Some user action path planning configurations involve cross-page configurations, requiring the currently active user node state to be passed to the next potentially configured page.

[0084] According to some implementations, in the triggering phase, the user first visits page A, triggering the corresponding event. Upon entering page B or performing other operations, the user continues browsing other pages or performing other operations, and the system continuously monitors the process. The system then determines whether the user's actions and a global snapshot of the user's movement meet the delivery criteria. If the delivery criteria are met, the relevant content is distributed to the user.

[0085] During the triggering phase, the triggers on each page are started and registered according to the returned configuration. For example, if the cloud configuration has been issued for element clicks, the page will first check if the current element exists. If the element exists, the page will globally delegate the event to determine the element's click status. After the event is triggered, the corresponding element trigger will trigger the configuration and start the running node of the configuration.

[0086] Figure 3 A schematic diagram of a backend service engine according to an example embodiment is shown.

[0087] The backend design, beyond the basic configuration of materials and delivery strategies typically found in platforms, extracts more features and capabilities, including user flow management, delivery strategies, material management, page management, and a service marketplace. User flow refers to the user's movement path, the behavioral nodes that generate user lifecycle characteristics. The strategy section is the content expressed externally and the final deliverable to the task manager. Materials are the most direct content conveyed to the user, transmitting the platform's most authentic information. Page selection is both the entry point for strategy deployment and a source of stability assurance. The service marketplace carries the most common and reusable technical components and is a key indicator for improving efficiency.

[0088] User flow management controls the list of user behavior characteristics required to trigger operational decision-making strategies. A user flow represents the logic behind the operation targeting this group of users. For example, on a search page, it's necessary to obtain user behavior characteristics such as "what keywords the current user is searching for when they enter the search page." OD sharing parameters determine whether to distribute security coupons to users who have accessed private domain sharing, filtering out buyers who are actually sharing from the merchant's private domain. Sharing on core promotional pages distributes promotional coupons uniformly across multiple pages, while simultaneously checking for existing coupons to avoid multiple pop-ups.

[0089] The delivery strategy incorporates numerous detailed elements in the form configuration, while also emphasizing product experience design for overall platform consistency. The product delivery design is divided into four links and two delivery levels. The overall process consists of four steps: pre-configuration, strategy configuration, workflow configuration, preview, and release. Each step utilizes independent content module management to avoid overly lengthy modules that would result in excessive learning costs.

[0090] The campaign strategy is divided into basic and advanced functions. In the basic functions, the above-mentioned links, without being expanded, mostly consist of basic form content. Advanced functions are the convergence of server-side logic based on the original basic logic, and also expose public capabilities and methods, avoiding the need to add heavy burdens to the system's non-task attributes in some complex logic scenarios. These include filters, used to create complex filtering logic that cannot be satisfied by the target audience logic but is customized for specific tasks, such as filtering for consistency between product sharing ID and product ID; traffic splitters, used to adapt to different audiences while reusing other similar form configurations, such as audiences with different purchase amounts during promotional events; and executors, which extract service capabilities into executor capabilities and provide them to other materials, such as issuing red envelopes and combining images.

[0091] Creative management is crucial because the final product delivered to users is the creative material. However, what users receive may not necessarily be visible content; it could be something invisible, such as the distribution of a benefit. Therefore, it's essential to separate creative materials from operational service capabilities. Bundling creative materials with service capabilities would make the entire creative system too heavy, requiring iterative releases and turning what should be a simple creative material system into a cumbersome component system.

[0092] While ensuring flexible configuration of component assets, it also maintains the flexibility of dynamic schema. Furthermore, it allows observation of which strategies are applied and their version numbers at the component level, enabling faster and better feature upgrades and bug fixes if needed.

[0093] Page maintenance is used to maintain a list of all currently supported pages, which also serves as a whitelist of allowed pages for deployment. Each page manages its assigned domain; for example, an order page can be defined as part of a transaction chain.

[0094] The service marketplace carries the shared, reusable portions of service capabilities and provides external users with publicly exposed SPI methods. The interface marketplace primarily targets server-side users, enabling complex or simple server-side integrations such as the aforementioned traffic splitters, filters, and executors. The script marketplace primarily targets front-end users, providing asynchronous dynamic script delivery capabilities. It also securely controls internal scripts to prevent abnormal code from being submitted to users and potentially impacting platform security.

[0095] This embodiment creates a highly flexible and configurable backend system applicable across all platforms, adaptable to complex operational strategy scenarios. The backend configuration blocks analyze user scenarios and delivery capabilities in a detailed and vivid way, providing multiple sets of product capabilities across various delivery scenarios while maintaining flexibility to avoid uniformity and formality. The flexible configuration point lies in how to ensure similar functions can be used at different stages; therefore, it provides SPI service capabilities. As long as any stage can plug and unplug this SPI service, it can be flexibly configured to any stage. For example, a judgment service can be provided, which can make judgments when entering a strategy, when selecting a component, or when the user clicks.

[0096] Figure 4 A flowchart of a method for content distribution according to an example embodiment is shown.

[0097] In S401, status data of each page is collected and shared through cross-page communication.

[0098] According to some embodiments, the purpose of global state data transmission is to store the current node state. Some configured user action path planning has cross-page configuration, and it is necessary to pass the state of the currently active user node to the next possible configured page.

[0099] According to some embodiments, a cross-page data sharing scheme can provide a consistent user behavior across different pages, while such a scheme does not require the involvement of the operator and reduces the cost of collaboration and communication between teams.

[0100] In S403, an initialized node tree is generated based on the node group configuration configured in the backend. The nodes in the node tree have different node types and state data. The nodes represent the user's movement or operation in the application scenario. The node group includes at least one node connected in series and supports cross-page operation.

[0101] According to some embodiments, a node core management module is initialized at the front end. This module can generate a node tree after configuration initialization. Each key node, after a series of orchestrations by the platform, is connected in series. As long as a user hits these connected nodes, it is considered that the user has hit the configured path. The two are mutually bound to form a mapping relationship, and different strategies can form network relationships with different paths.

[0102] In S405, at least one node submitted by the user is matched in real time with any node in the node tree based on the node type and the status data to determine whether the node group is matched.

[0103] According to some implementations, the matching of nodes is determined in the state of the node tree. The specific matching logic is that each node in the node tree has different types and data. The node is considered to be matched successfully only if the type and data of the node submitted by the user are successfully matched with any node in the node tree. If the type and data are inconsistent, it will be considered to be a failure.

[0104] According to some implementations, the selection and determination of the core modules of the matching mechanism, based on several commercially available technical solutions, are mostly divided into six types: rule engine matching, algorithm engine matching, streaming processing engine matching, state machine management engine matching, graph mining engine matching, and bucketing model engine matching. In the underlying runtime environment, the ability to add slots to any node is added, allowing for easy replacement with any algorithm model. It also provides the ability to call interfaces in real time, ensuring that the cloud-based matching mechanism can be switched at any time.

[0105] In S407, after the node group is hit, the strategy bound to the node group and the material associated with the strategy are queried, a corresponding distribution method is formed and the material is distributed, wherein the strategy is the content module for distributing the material.

[0106] According to some implementations, after determining the hit conditions based on traffic flow, a binding strategy query is performed to identify various hit conditions, match the corresponding traffic buckets, find the required operational materials, and form appropriate outreach methods. The success rate, call volume, time consumption, gray-scale status, coverage ratio, and error status of the materials are all monitored to ensure the correctness of the strategy and materials during the query.

[0107] According to some embodiments, this invention provides a process for creating materials. The process includes: creating components (assets) for gray-scale application overlay; creating components on the component list page; inputting form information for the components; and completing the required information to meet the requirements for component deployment. A real-time detection system is implemented, building a full-link detection system covering infrastructure (servers, network, storage), middleware (databases, message queues), application layer (interface responses, job logic), and user experience (page loading, API success rate). Real-time monitoring of core metrics such as CPU, memory, network latency, and request QPS is achieved. Centralized log analysis enables rapid anomaly localization, and key job nodes are monitored to ensure the health status of job logic is traceable. An intelligent alarm mechanism triggers tiered alarms based on threshold alarms and anomaly detection algorithms, reducing false positives and false negatives.

[0108] According to some implementations, during the component creation process, a draft strategy is created in the database (DB). The deployment is indicated by modifying the database status. In creating a new deployment strategy, the page list is first queried, the corresponding component is found in the resource slot database, the relevant fields of the strategy are configured, and the draft strategy is saved. The strategy status is then modified through a phased rollout to adjust the deployment ratio. Finally, the strategy is submitted to the approval interface. After approval, a message is received, the draft status of the strategy in the database is changed to online status, and the deployment ratio is adjusted for full deployment.

[0109] In modifying the strategy, first, a draft copy of the corresponding strategy is created. Then, the status is adjusted to online by calling the approval interface. Next, the proportion is adjusted to push the full proportion. The strategy in online status is deleted to achieve the purpose of going offline. Then, the online status is adjusted to offline to achieve the purpose of going offline. Finally, the obsolete status is adjusted to achieve the purpose of obsolescence.

[0110] According to some embodiments, the present invention is divided into four levels in the overall project design, including the operation layer, application layer, logic layer and basic layer.

[0111] According to some embodiments, at the operational level, the system of the present invention aims to solve various operational problems. For example, in search and selection scenarios, the massive amount of information makes it difficult to effectively absorb and transmit information; how to search for information on major promotional events; how to subscribe to new products; how to quickly find sources of similar products, etc.

[0112] According to some embodiments, the present invention organizes the cause-and-effect relationships and achieves the goal through specific means or approaches. For example, it delivers results through channels such as major promotional activities, recurring purchases, and product exchange programs, ultimately determining whether the goal of improving user experience has been achieved through data review.

[0113] According to some embodiments, at the application layer, when the system of the present invention is actually solving operational scenarios, it is divided into two major solution modules: strategy and movement path. The strategy refers to the content that the operation team directly interacts with and fills in during actual operational activities; it directly maintains the basic configurations such as how to display, what to display, and who should view it. The movement path, on the other hand, is the platform's arrangement of the user's actual movement path, which can detect each key node of the user. After a series of arrangements by the platform, these key nodes are connected. As long as the user hits these connected nodes, it is considered that the user has hit the configured movement path. The two are mutually bound, forming a mapping relationship. Different strategies can form network relationships with different movement paths, ultimately achieving a mutually reinforcing effect on operational goals within this network relationship. By checking whether the movement paths hit by the user match the actual operational indicators, the goal of complementary operational strategies and operational indicators is achieved.

[0114] According to some embodiments, in the logic layer, which describes the underlying behavior of the platform logic, when a user enters the site, the platform performs step-by-step judgments and ultimately delivers the advertising materials. The logic layer's workflow configuration is such that after the user enters the page, this configuration is retrieved, and then the internal script is initialized. Combined with the workflow executor, through the core module of the internal script initialization, a series of hit judgments determine the workflow hit logic. The strategy executor's function is to query the bound strategy after judging the workflow hit conditions, determine various hit conditions, hit the corresponding traffic bucket, find the corresponding required operational materials, and form appropriate outreach methods. Ultimately, different materials such as benefits, red envelopes, and guidance may be distributed to allow users to perceive the platform's intended purpose.

[0115] According to some implementation examples, at the foundational layer, the focus is on four key aspects: stability, reliability, flexibility, and security. Regarding stability, the stability of a platform is directly related to its core critical aspects; therefore, monitoring, control, early warning reporting, and anomaly alerts are implemented from various angles. From the success rate, stability, grayscale status, and coverage ratio of workflows, to the success rate, call volume, latency, grayscale status, and coverage ratio of strategies, and further to the success rate, call volume, latency, grayscale status, coverage ratio, and error occurrences of materials, every detail is meticulously monitored.

[0116] According to some implementation examples, during the delivery of any material, close attention is paid to the phased indicators of the strategy. This involves real-time tracking from various perspectives, including phased improvement of the target, breakdown of experimental variables, target quantification, and P-value calculation, forming a closed loop at the e-commerce platform level. In the design of the e-commerce platform, each element is atomically designed, allowing for different reuse and association of various stages and functionalities, greatly improving the flexibility of configuration. For example, the ability to distribute red envelopes can be bound to different materials, ensuring that red envelopes are not limited to a single format.

[0117] According to some implementations, the user hit policy requirements strictly limit the hit logic to prevent black market activities such as fraudulent transactions or attacks. It also blocks and intercepts API calls to prevent abnormal software access. In addition, it manages blacklists and whitelists to better limit the stability of the delivery.

[0118] According to some implementations, a series of designs are carried out at four different levels, and three different capabilities are used to improve the platform's capabilities and efficiency. Among them, the three-party operational dependencies include powerful group platforms, experimental platforms, rights platforms, etc., and the architecture design also uses industry-reviewed frameworks with the help of three-party technology dependencies.

[0119] The core objective of this invention's content distribution and delivery solution is to improve website user conversion rates and platform stickiness through precise content strategies and efficient resource allocation. Based on practical experience in intelligent delivery, it utilizes data-driven and dynamic adjustments to achieve multi-scenario coverage and synergistic effects.

[0120] In some implementations, data-driven and dynamic adjustments leverage big data analytics tools to monitor campaign performance in real time, such as click-through rate, conversion rate, and dwell time, and quickly adjust campaign strategies based on data feedback. For example, budgets may be reallocated to inefficient channels, or high-potential content may be amplified.

[0121] According to some implementation examples, multi-scenario coverage and synergy combine different functional modules of the website, such as homepage recommendations, search results pages, and product detail pages, to achieve end-to-end user reach. Simultaneously, cross-scenario content linkage enhances the consistency and coherence of the user experience.

[0122] For strategies primarily focused on empowering operational attributes, we have iterated and meticulously designed all aspects of data structure, platform design, process configuration, release control, and data analysis.

[0123] According to some embodiments, CRUD operations on various data are performed at the user interface layer. The user interface layer refers to the pages configured in the platform backend. The web interface of the user interface layer is the entry point for users to interact with the system, providing a user-friendly interface that allows operators to easily perform page management, strategy configuration, and other operations.

[0124] According to some embodiments, the application service layer decomposes various tasks into several parts, such as page service, strategy service, component service, and resource placement service. The page service maintains a list of pages where the ad will be placed; the strategy service refers to the overall module of subsequent ad creatives, including launch time, audience control, traffic allocation, fatigue control, etc.; the component service refers to the content that users see after the ad is placed, which can be the content displayed in any position on the page; and the resource placement service refers to the specific slot occupied by the component, indicating which block the page displays.

[0125] According to some embodiments, the domain service layer integrates page services, strategy services, component services, and resource slot services. The page service manages the strategy domain, including querying, creating, and updating pages. For example, determining whether a page should be deployed is maintained at this layer. The page service can be understood as a page composed of multiple resource slots. The strategy service is responsible for the overall deployment process and status management, as well as resource slot management. The strategy service covers the entire lifecycle management of strategies, including creation, deployment, update, decommissioning, canary release control, status management, approval workflow management, and A / B testing management, ensuring the effectiveness and flexibility of strategies. The component service provides functions for creating, deploying, updating, managing the status of components, and querying them, allowing pages to be flexibly composed of multiple reusable components. The resource slot service manages the creation, querying, and updating of resource slots. Resource slots are the concrete carriers of strategy implementation, determining the display position of the strategy on the page; materials are a way of expressing the purchased resource slots.

[0126] The infrastructure layer provides necessary technical support for upper-layer services, including but not limited to distributed caching systems to improve data access speed; relational databases to store structured data; configuration centers to dynamically adjust system configurations; job workflow management systems to help automate complex job workflows; and log services to collect and analyze log information generated during system operation, facilitating troubleshooting and performance optimization.

[0127] According to this example embodiment, the system of the present invention can not only meet the policy customization requirements of job attributes, but also has high flexibility and scalability, and can continuously iterate and optimize in constantly changing job environments.

[0128] The data in this invention relies on the overall call log, distinguishing between two data sources. Combined with the experimental algorithm system, it ultimately produces overall data metrics. First-party data represents direct data accessible to the internal team, while second-party data represents indirect data from outside the team. Under normal circumstances, the data meets existing data visualization requirements, but some customized scenarios exist. Therefore, customized access points are provided for data visualization. As long as the metrics are easily accessible, no secondary development is needed, allowing for expansion within the dataset. This avoids the need for subsequent data development and maximizes efficiency.

[0129] This embodiment innovates with a cross-page user flow scheme and a backend material and task interface separation scheme, which are not found in the industry before. Compared with the other two platform solutions, it mainly considers three aspects: users, target audience, and developers, providing a suitable solution for each user under each different group, and taking user satisfaction into account.

[0130] On the front end, a cross-page data sharing solution provides a consistent user experience across different pages, eliminating the need for the task manager and reducing communication costs between teams. It also provides developers with independent task interfaces, facilitating customized scenarios and participation in various stages. Developers can participate in custom task filtering scenarios, such as those for users who have already received red envelopes, those matching new user characteristics, and those who have installed plugins; they can execute tasks before material distribution, such as distributing red envelopes, sending SMS notifications, emails, and application messages; and they can execute tasks during material distribution, such as distributing red envelopes to users (to prevent fraudulent activity) and providing user characteristic feedback. In the logic of this customized task interface, the interface is typically called from the server (unless there are special client-side call scenarios), which better mitigates the risk of abnormal interface calls related to web search traffic.

[0131] This invention delivers a highly flexible front-end node matching mechanism, avoiding intervention from the operator. This mechanism is typically used to determine various complex logic scenarios on the front-end, such as the current page state or whether a certain front-end attribute is met. Debugging and configuration can also be performed on the platform side; otherwise, the operator would need to develop the code and debug between platforms, significantly increasing the complexity of system-to-system debugging and maintenance. A core node management module is initialized on the front-end. This module generates a configured node tree and determines node matching based on the state of this tree. Specifically, each node in the tree has a different type and data. A node is considered a successful match only if the user-submitted node matches any node in the tree in terms of type and data. If any type or data mismatch occurs, the match is considered a failure.

[0132] This invention also provides users with smoother interaction and visual delivery capabilities, finely integrating and separating fields related to various tasks to make configuration interactions easier to understand. Furthermore, it transforms the initial technical fields from a technical perspective into more easily understandable low-code interactive configurations, categorizing technical and task-related capabilities as advanced and basic capabilities.

[0133] Figure 5 A block diagram of a computing device according to an exemplary embodiment of the present invention is shown.

[0134] like Figure 5 As shown, the computing device 30 includes a processor 12 and a memory 14. The computing device 30 may also include a bus 22, a network interface 16, and an I / O interface 18. The processor 12, memory 14, network interface 16, and I / O interface 18 can communicate with each other via the bus 22.

[0135] The processor 12 may include one or more general-purpose CPUs (Central Processing Units), microprocessors, or application-specific integrated circuits, etc., for executing relevant program instructions.

[0136] Memory 14 may include a machine-readable medium in the form of volatile memory, such as random access memory (RAM), read-only memory (ROM), and / or cache memory. Memory 14 is used to store one or more programs containing instructions, as well as data. Processor 12 may read the instructions stored in memory 14 to perform the methods described above according to embodiments of the present invention.

[0137] The computing device 30 can also communicate with one or more networks via the network interface 16. The network interface 16 can be a wireless network interface.

[0138] Bus 22 can include address bus, data bus, control bus, etc. Bus 22 provides a path for exchanging information between components.

[0139] It should be noted that, in specific implementations, the computing device 30 may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the device described above may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.

[0140] The present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, DVDs, CD-ROMs, microdrives, as well as magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), network storage devices, cloud storage devices, or any type of medium or device suitable for storing instructions and / or data.

[0141] This invention also provides a computer program product comprising a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods described in the above method embodiments.

[0142] Those skilled in the art will clearly understand that the technical solutions of the present invention can be implemented by means of software and / or hardware. In this specification, "unit" and "module" refer to software and / or hardware capable of independently performing or cooperating with other components to perform a specific function, wherein the hardware may be, for example, a field-programmable gate array (FPGA), an integrated circuit, etc.

[0143] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the present invention is not limited to the described order of actions, because according to the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0144] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0145] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some service interface; the indirect coupling or communication connection between devices or units may be electrical or other forms.

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

[0147] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0148] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention.

[0149] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0150] Exemplary embodiments of the present invention have been specifically shown and described above. It should be understood that the present invention is not limited to the detailed structures, arrangements, or implementations described herein; rather, the present invention is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended provisions.

Claims

1. A system for a content distribution engine, characterized in that, include: A global state manager that runs across pages and is used for cross-page communication to share state data across pages; The node management module running on the front end generates an initialized node tree based on the node group configuration configured on the back end. The nodes on the node tree have different node types and status data. The nodes represent the user's movement or operation in the application scenario. The node group includes at least one node connected in series and supports cross-page operation. The node matching module running on the front end is used to perform real-time matching of at least one node submitted by the user with any node in the node tree based on the node type and the status data, and to determine whether the node group is matched. The distribution module running on the front end is used to query the strategy bound to the node group and the material associated with the strategy after the node group is hit, form a corresponding distribution method and distribute the material, wherein the strategy is the content module for distributing the material.

2. The system according to claim 1, characterized in that, The global state manager is configured to maintain state data for each page.

3. The system according to claim 2, characterized in that, When any page updates its state data, the global state manager is notified to update the state. When any page needs to obtain the latest status data, it notifies the global status manager to obtain the corresponding status data.

4. The system according to claim 1, characterized in that, The node matching module performs real-time matching based on a streaming engine and supports multiple event combinations based on sequence patterns.

5. The system according to claim 1, characterized in that, The node matching module running on the front end can be switched to a backend matching mechanism at any time.

6. The system according to claim 1, characterized in that, The node matching module is also configured to: Enable and run the page's triggers based on the returned node group configuration; If the node group configuration includes the configuration of the operation of the first element, then determine whether the first element exists on the page; If the first element exists, the global delegate event determines the operation status of the first element; After the operation state of the first element generates a trigger event, the trigger activates the real-time matching.

7. The system according to claim 1, characterized in that, Also includes: The backend configuration module, which runs on the backend, is used for: Generate the node group configuration; and Configure the whitelist page. The page will only issue the required node group configuration if there are policy-related options on the page.

8. The system according to claim 1, characterized in that, The attributes of the strategy include one or more of the following: online time, object group control, traffic allocation, fatigue control, and resource slots.

9. The system according to claim 1, characterized in that, Also includes: A pluggable technical service SPI that provides the capability to handle any stage of the process.

10. The system according to claim 1, characterized in that, Also includes: The event tracking module is used to track data during strategy deployment, and the data tracking points are uniformly categorized at the platform level.

11. The system according to claim 10, characterized in that, The attributes of the data embedding points include one or more of the following: strategy identifier, experiment identifier, material identifier, SPI service identifier, and matching rules.

12. A method for content distribution, characterized in that, include: Collect and share status data across pages through cross-page communication; The node tree is generated based on the node group configuration configured on the backend. The nodes in the node tree have different node types and state data. The nodes represent the user's movement or operation in the application scenario. The node group includes at least one node connected in series and supports cross-page operation. The system performs real-time matching of at least one node submitted by the user with any node in the node tree based on the node type and the status data, and determines whether the node group is matched. After the node group is hit, the strategy bound to the node group and the material associated with the strategy are queried, a corresponding distribution method is formed and the material is distributed, wherein the strategy is the content module for distributing the material.

13. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method as described in claim 12.

14. A computing device, characterized in that, include: processor; as well as A memory storing a computer program that, when executed by the processor, causes the processor to perform the method as described in claim 12.

Images