Task processing method, electronic device, storage medium and computer program product

Abstract

This disclosure provides a task processing method, an electronic device, a storage medium, and a computer program product. The task processing method includes: obtaining a content generation task issued by a first device, the content generation task including a region template identifier of a functional area to be processed in a first page of the first device, the content generation task being used to drive the generation of target content information in the functional area to be processed; invoking a processing unit corresponding to the region template identifier to execute the content generation task, obtaining target view data, the target view data being rendered to display the target content information; and responding to receiving a read request containing a region template identifier issued by a second device, synchronizing the target view data to the second device, causing the second device to render the target view data, and displaying the target content information on a second page of the second device.

Description

Technical Field

[0001] This disclosure relates to the technical fields of computer software, and more particularly to a task processing method, electronic device, storage medium, and computer program product. Background Technology

[0002] In multi-device collaboration scenarios, if two devices need to collaboratively display the same content (e.g., one device is operated by the seller, and the other is viewed by the buyer), the traditional approach is to develop independent page rendering logic for each device. Even if one end has completed page configuration, data filtering, and calculation, the other end still needs to repeat the same processing flow to present consistent results. This not only leads to redundant development of page functions and high maintenance costs, but also easily causes inconsistencies in display due to differences in implementation or calculation errors caused by the dispersed logic. In addition, when adding functional modules to the page, code needs to be modified on each end separately, resulting in poor scalability and low iteration efficiency. Summary of the Invention

[0003] This disclosure provides a task processing method, an electronic device, a storage medium, and a computer program product.

[0004] According to one aspect of this disclosure, a task processing method is provided, comprising: obtaining a content generation task issued by a first device, the content generation task including a region template identifier of a functional area to be processed in a first page of the first device, the content generation task being used to drive the generation of target content information in the functional area to be processed; invoking a processing unit corresponding to the region template identifier to execute the content generation task to obtain target view data, the target view data being able to display the target content information through rendering; and responding to receiving a read request containing the region template identifier issued by a second device, synchronizing the target view data to the second device, causing the second device to render the target view data to display the target content information on a second page of the second device.

[0005] According to one technical solution, this task processing method decouples business logic from multi-terminal rendering by introducing a region template identifier as a unified data contract: the content generation task is triggered by the first device, the backend calls the corresponding processing unit to generate structured target view data and stores it in a shared database, and the second device only needs to send a read request with the same region template identifier to reuse the same data for adaptive rendering; thus avoiding the problems of repeated development, inconsistent calculation logic and high maintenance costs in traditional solutions, ensuring "one-time generation, consistent across multiple terminals", and significantly improving the system's maintainability, scalability and cross-terminal collaboration efficiency.

[0006] In some implementations, before invoking the processing unit corresponding to the region template identifier to execute the content generation task, the method includes: identifying the region template identifier indicated in the content generation task; and determining the processing unit corresponding to the region template identifier based on a first mapping table, the first mapping table recording the correspondence between region template identifiers and processing units, wherein the processing unit is capable of processing region template data with the region template identifier and displaying target content information in the corresponding functional area.

[0007] According to one technical solution, this step introduces a first mapping table, giving the system high flexibility and scalability. When adding a new functional area, only the new area template data needs to be registered, the corresponding processing unit developed, and the association established in the first mapping table, without modifying the core scheduling logic. Secondly, the identifier-driven lookup mechanism ensures the accuracy and efficiency of task distribution, avoids hard coding or logical branch judgments, and improves system robustness. More importantly, this design guarantees the consistency of functional semantics: each area template identifier clearly corresponds to a processing unit that can realize its business capabilities, eliminating the risk of mismatch between "template definition" and "logic execution" from the source, and laying a reliable foundation for multiple terminals to share the same target view data.

[0008] In some implementations, after receiving a read request containing the region template identifier from a second device, the method further includes: determining the terminal type that initiated the read request, the terminal type including a first device type and a second device type; determining a display rule applicable to the terminal type based on a second mapping table, the second mapping table recording the correspondence between terminal types and display rules; and processing the display portion of the target view data according to the display rules to form customized target view data, the customized target view data being rendered to present the target content information in a manner conforming to the display rules.

[0009] According to one technical solution, by identifying the terminal type of the second device and dynamically applying display rules adapted to its characteristics based on the second mapping table, only the display part of the target view data is customized and adjusted, while the content part remains unchanged. This ensures data consistency across multiple terminals and flexibly meets the differentiated needs of different terminals (such as PAD and H5) in terms of layout, interaction, and functional presentation. At the same time, this mechanism decouples the display logic from the business logic. When adding a new terminal type, only the display rules need to be configured, without modifying the core processing flow, which significantly improves the maintainability, scalability, and cross-terminal collaboration efficiency of the system.

[0010] In some implementations, after obtaining the target view data, the process includes: writing the target view data into a shared database, which can be accessed by the first device and the second device.

[0011] According to one technical solution, the target view data is written into a shared database, enabling both the first and second devices to read and render based on the same data source, avoiding the problems of repeated calculations and data inconsistency across multiple devices. At the same time, this mechanism realizes "generation once, reuse multiple times", which not only improves system performance and response efficiency, but also provides a unified and reliable data foundation for cross-device collaboration, link sharing and subsequent expansion (such as multi-level forwarding, offline viewing).

[0012] In some implementations, before acquiring the content generation task issued by the first device, the method includes: responding to the first device initiating a page display request, determining a region template combination based on the business category associated with the page display request, the region template combination including multiple region template data related to the business category, the region template data being able to realize at least one business display function of the business category through rendering; and displaying the first page on the first device, the first page having functional areas corresponding to the region template data.

[0013] According to one technical solution, before the content generation task is triggered, the business category is identified based on the page display request of the first device, and a matching combination of area templates is dynamically loaded, thereby pre-setting a complete functional area layout in the first page. This not only ensures that the page structure is highly consistent with the business scenario, but also provides a context-consistent interaction basis for subsequent user operations, avoids missing or redundant functions, and improves the efficiency of system initialization and the consistency of user experience.

[0014] In some implementations, displaying the first page on the first device includes: in response to a loading instruction initiated by the first device, displaying one or more functional areas on the first page according to a rendering method indicated by the loading instruction, wherein the rendering method includes rendering templates one by one and rendering templates in batches.

[0015] According to one technical solution, by supporting the dynamic selection of template rendering one by one or batch rendering based on loading instructions, one or more functional areas can be flexibly presented on the first page, balancing performance and user experience: for scenarios with strong dependencies or those that need to prioritize the display of core modules, one-by-one rendering can speed up the first screen response; while for businesses where each area is independent and needs to be presented as a whole, batch rendering reduces interaction latency and improves page integrity, thereby achieving the optimal loading strategy and user-perceived efficiency under different business needs.

[0016] In some implementations, the method further includes: configuring a region template identifier and a processing unit for the region template data; and binding the region template identifier and the processing unit to generate a first mapping table.

[0017] According to one technical solution, by configuring a unique regional template identifier for each regional template data and binding it to the corresponding processing unit, a first mapping table with a clear structure is generated, realizing the explicit association between functional definition and business logic. This not only enables the system to accurately and efficiently schedule processing units to generate target view data, but also significantly improves the maintainability and scalability of the modules. For example, when adding or modifying functions, only the mapping relationship needs to be updated, without changing the core process, thereby supporting flexible combination, rapid iteration and consistent business rendering capabilities across multiple terminals.

[0018] According to another aspect of this disclosure, an electronic device is provided, comprising: a memory storing execution instructions; and a processor executing the execution instructions stored in the memory, causing the processor to perform a task processing method according to any embodiment of this disclosure.

[0019] According to one aspect of this disclosure, a readable storage medium is provided that stores executable instructions, which, when executed by a processor, implement the task processing method described in any embodiment of this disclosure.

[0020] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the task processing method described in any embodiment of this disclosure. Attached Figure Description

[0021] The accompanying drawings illustrate exemplary embodiments of the present disclosure and, together with the description thereof, serve to explain the principles of the present disclosure. These drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this specification.

[0022] Figure 1 This is a schematic diagram illustrating an application scenario of the task processing method according to the embodiments of this disclosure.

[0023] Figure 2 This is a flowchart of a task processing method according to an embodiment of the present disclosure.

[0024] Figure 3 This is a flowchart of the multi-party interaction process according to the embodiments of this disclosure.

[0025] Figure 4 This is a flowchart of the processing unit positioning process according to an embodiment of the present disclosure.

[0026] Figure 5This is a schematic diagram of the first page according to an embodiment of the present disclosure.

[0027] Figure 6 This is a schematic diagram of the second page according to an embodiment of the present disclosure.

[0028] Figure 7 This is a schematic block diagram of the structure of a task processing apparatus according to an embodiment of the present disclosure.

[0029] Figure 8 This is a block diagram illustrating the structure of an electronic device according to one embodiment of the present disclosure. Detailed Implementation

[0030] The present disclosure will now be described in further detail with reference to the accompanying drawings and examples. It should be understood that the specific examples described herein are for illustrative purposes only and are not intended to limit the scope of the disclosure. Furthermore, it should be noted that, for ease of description, only the parts relevant to the present disclosure are shown in the accompanying drawings.

[0031] It should be noted that, where there is no conflict, the embodiments and features described in this disclosure can be combined with each other. The technical solutions of this disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0032] In multi-device collaboration scenarios, if two devices need to collaboratively display the same content, such as in a property sales scenario, the PAD (tablet computer) is used by asset managers to screen properties, calculate the total price of properties, and conduct comparative analysis of similar properties, while the H5 page on the mobile phone is used by the property owner to view the results through a mobile browser.

[0033] The traditional approach is to develop separate page rendering logic and backend interfaces for each platform. Even if the PAD platform has completed the full process of property filtering, price calculation, and comparative analysis, the H5 platform still needs to reimplement almost the same calculation logic and data assembly process to barely achieve content alignment. This not only causes a lot of redundant development—for example, the "property comparison" function requires writing one set of list rendering code on the native platform and another on the H5 platform—but also leads to discrepancies in results under the same input due to differences in the technology stack, data format, or calculation precision between the two platforms, causing trust issues. In addition, when the business needs to add a "tax estimation" module, the development team has to modify the frontend code of both the PAD and H5 platforms and adjust two sets of backend interfaces, resulting in high expansion costs, long deployment cycles, and high error risks. The fundamental problem is that the relevant technologies lack a unified data generation and terminal adaptation mechanism, resulting in fragmented core business logic, multiple data sources, and difficulty in achieving true consistency and efficient iteration.

[0034] Therefore, this disclosure proposes a task processing method.

[0035] Figure 1This is a schematic diagram illustrating an application scenario of the task processing method according to embodiments of this disclosure. For example... Figure 1 As shown, this application scenario may include a server 100 and a terminal device 200. The server 100 and the terminal device 200 can interact with each other via a network connection. The server 100 can be a cloud server or a physical server, and the terminal device 200 can be a smart device such as a computer, mobile phone, or tablet. The server 100 can receive requests from the terminal device 200 and execute the task processing method disclosed herein.

[0036] Figure 2 This is a flowchart of a task processing method according to an embodiment of the present disclosure. For example... Figure 2 As shown, this disclosure proposes a task processing method M200, in which a region template identifier serves as the interaction medium between the first device, the processing unit, and the second device, thus solving the problems of inconsistent content and high maintenance costs in the same functional area due to repeated development and distributed computing in multi-terminal collaboration.

[0037] Before detailing each step of the task processing method M200, it is important to understand that this method M200 is executed by a backend. The backend is a software program running on a server (such as server 100 mentioned earlier) capable of executing this method M200. The backend is configured with processing units capable of executing various tasks and associates the area template identifier, processing units, and device type, thus possessing the ability to respond to commands from the first or second device.

[0038] Step S210: Obtain the content generation task issued by the first device.

[0039] The first device is a terminal device with complete interactive and computing capabilities, such as a tablet, running a property management application that can be operated by the service provider (such as asset management personnel). The first device should be equipped with a display area to present the first page and multiple functional areas; and integrate an instruction receiving unit to support receiving input from the service provider via touch, voice, or physical buttons, enabling tasks such as property filtering and parameter configuration to be triggered, thereby displaying target content information, or initiating page display requests, content generation tasks, browsing links, and other business actions.

[0040] The content generation task drives the generation of target content information within the functional area to be processed. It includes the area template identifier and constraints of the functional area to be processed on the first page of the first device. Specifically, generation is triggered when the service provider operates on a functional area on the first page of the first device (e.g., clicking "Calculate Revenue," completing property filtering, or confirming parameter input). Its core purpose is to use the operated functional area as the area to be processed, driving the generation of target content information within that area. The content generation task contains at least two key elements: first, clearly defining the area template identifier corresponding to the functional area to be processed, instructing the backend to call the correct processing unit; second, providing constraints for the processing unit, such as the selected property identifier, rent range, loan ratio range, etc., providing a basis for the processing unit to perform calculations or data assembly. Through this structured task, the first device accurately transmits the interaction intent to the backend, ensuring that the generated target view data is consistent with the service provider's operational context.

[0041] Step S220: Invoke the processing unit corresponding to the region template identifier to perform the content generation task and obtain the target view data.

[0042] The area template identifier is a unique identifier configured for area template data. It is used to distinguish different area template data and serves as the basis for the first device, the second device, and the processing unit to identify and locate area template data.

[0043] The region template data is a view structure definition used to render the functional region. It does not contain specific field values, but specifies the layout, style and fields to be displayed for the functional region. The specific field values ​​are dynamically filled by the processing unit based on the actual business scenario and the content specified by the service provider through data retrieval, calculation or analysis.

[0044] Regional template data defines the functional boundaries and interactive capabilities of the rendered functional areas through the semantics of the displayed fields. For example, regional template data supporting the "Property Display" function will declare the fields and styles to be displayed, such as property maps and property details, and provide function keys for property filtering. The implementation of these functions is not achieved by the template data itself, but rather by configuring processing units with property filtering and property detail data retrieval capabilities. Specifically, each regional template data is bound to one or more processing units. All actual functions such as data acquisition, logical calculation, and conditional filtering are executed by the corresponding processing units. The regional template data serves only as a functional contract and rendering blueprint, ensuring consistency between the front-end display and back-end logic across multiple platforms.

[0045] The processing unit is an independent execution module in the backend that encapsulates specific business logic. It is responsible for performing data querying, calculation, and assembly tasks based on the constraints in the content generation task, generating target view data that meets the constraints. Each processing unit is bound to a unique regional template data to implement the functions agreed upon by that regional template data (such as property filtering, revenue calculation, tax analysis, etc.), and is the core executor for function implementation.

[0046] Target view data is structured data used by the front-end to render and present target content information. It includes a content part and a display part. The content part is the result of the processing unit executing business logic, which is reflected in specific field values, calculated values, list items, or chart data, etc.; the display part contains meta-information such as layout structure, component type, and style hints, which guide the front-end on how to organize and present the content part.

[0047] Because the first and second devices differ in interaction methods, screen size, and user roles, their display requirements for the same functional area may differ. For example, a PAD needs to display editing controls, while an H5 page needs to embed a share button. Therefore, the backend can adaptively adjust the display based on the device type before returning the target view data. This can be done by dynamically adding or deleting components, hiding internal fields, or converting data formats, thereby achieving differentiated rendering across multiple devices while maintaining content consistency.

[0048] Step S230: In response to receiving a read request containing a region template identifier from the second device, the target view data is synchronized to the second device, so that the second device renders the target view data to display the target content information on the second page of the second device.

[0049] The second device is a terminal device used to receive and display target view data, capable of displaying a second page, such as a mobile H5 page. The service recipient (such as a homeowner, buyer, or tenant) reads the target content information on the second device through a browsing link shared by the first device. Therefore, the second device needs to have basic network communication and page rendering capabilities, be able to receive the browsing link from the first device, and send a read request to the backend; then, based on the received target view data, restore and display the target content information on the second page that is consistent with the operation result of the first device, and support mobile-friendly interaction methods (such as clicking and swiping). However, the second page of the second device generally does not have high-privilege operation capabilities such as data editing or task initiation.

[0050] A read request is a request initiated by the service recipient through a second device to obtain target content information, which includes the region template identifier corresponding to the functional area to be rendered, so that the backend can return the generated target view data accordingly.

[0051] It should be noted that the content generation task can simultaneously include processing instructions for multiple functional areas to be processed. The backend can then call the corresponding processing units in parallel to generate multiple target content information. Correspondingly, the shared browsing link can be associated with multiple area template identifiers. When the second device initiates a read request, it can also carry these multiple area template identifiers to obtain all target view data at once and fully restore the collaborative display content of multiple areas on the page.

[0052] Furthermore, the target view data is the instantiation result of the regional template data in a specific business scenario. That is, the regional template data defines the structure, fields, and display rules of the functional area and serves as the processing basis for the processing unit. The target view data, on the other hand, is the complete rendered data generated by the processing unit based on this template, combined with user operation parameters, and populated with actual content (such as specific property listings, calculated values, etc.). The rendering of the target view data is completed by either the first or second device. The first or second device converts the received target view data into visible page elements based on the content (such as field values ​​and calculation results) and display (such as layout structure and component types); this process is entirely executed on the first or second device.

[0053] Figure 3 This is a flowchart of the multi-party interaction process according to embodiments of this disclosure. For example... Figure 3 As shown below, the interaction process between the first device, the second device, and the backend is explained.

[0054] In step 301, the first device sends a page display request to the backend.

[0055] The page display request is initiated by the first device and includes the business type the service provider wants to access (such as "asset operation," "leasing management," or "investment analysis"). Based on this business type, the backend determines the matching combination of area templates. Because the display pages corresponding to different business types need to include functional areas that conform to their business context, the page display request serves as a key input, directly driving the backend to determine the corresponding combination of area templates, providing the structural foundation for generating the complete page. The area template data, through rendering, enables at least one business display function for each business category.

[0056] In step 302, the backend determines the region template combination.

[0057] The backend parses the page display request to determine the corresponding business type, and then determines the area template combination bound to that business type. The area template combination consists of one or more area template identifiers. The backend retrieves the corresponding area template data based on these identifiers, and finally renders a first page containing multiple functional areas on the first device, fully supporting the display and interaction of all functions required for that business type.

[0058] Figure 4 This is a flowchart of the processing unit positioning process according to an embodiment of this disclosure. Figure 4 The diagram illustrates the process of determining the processing unit.

[0059] In step 401, a region template identifier and processing unit are configured for the region template data to form a first mapping table.

[0060] The first mapping table records the correspondence between regional template identifiers and processing units. Each regional template data, as an independent functional unit, is stored in the backend database. The regional template data are decoupled and independent of each other, exhibiting a high degree of modularity. After creating regional template data, a unique regional template identifier is assigned to it for accurate differentiation and location in a multi-template coexistence environment. Simultaneously, one or more processing units capable of implementing its business functions (such as data filtering, revenue calculation, chart generation, etc.) are registered for this template. These processing units are bound to the regional template identifier and written to the first mapping table in key-value pair format. This mechanism not only supports flexible function combination and reuse but also provides fundamental support for subsequent on-demand invocation, parallel processing, and consistent rendering across multiple platforms.

[0061] In step 402, the business type corresponding to the page display request is determined. The backend parses the page display request sent by the first device and extracts the business type (such as "asset operation" or "leasing management").

[0062] In step 403, the region template combination associated with the service type is determined. Based on the determined service type, the backend searches for its associated region template combination from the pre-configured service-template mapping relationship. This combination consists of one or more region template identifiers and is used to fully support all functional areas required by the service type.

[0063] In step 404, the processing unit corresponding to the template identifier of each region in the template combination is determined according to the first mapping table.

[0064] Based on the first mapping table, the backend parses each regional template identifier contained in the regional template combination to find its corresponding processing unit. Since different functional areas (such as asset overview, revenue calculation, and property filtering) rely on different business logic, each regional template identifier typically corresponds to a dedicated processing unit responsible for implementing the data acquisition, calculation, or assembly capabilities for that area. Through this mapping query process, the static template structure is precisely associated with the dynamic execution logic, laying the foundation for subsequent parallel or on-demand invocation of processing units and generation of target view data for complete pages.

[0065] In step 303, the backend returns the target view data to the first device for the first time.

[0066] It should be noted that the page display request also includes a loading instruction, which indicates how the target view data is returned. The backend determines whether to return all area template data at once or return it one by one according to the loading method specified by the loading instruction (such as batch loading or loading one by one), thereby adapting to different rendering strategies and user experience requirements.

[0067] Specifically, sequential rendering templates refer to requesting and rendering data for each functional area in order, which is suitable for scenarios where there are dependencies or where key modules need to be displayed first; batch rendering templates, on the other hand, obtain the target view data of all functional areas at once and render them uniformly, which is suitable for business pages where each area is independent and needs to be presented as a whole, thus flexibly balancing loading performance and user experience.

[0068] In step 304, the first page is displayed by the first device.

[0069] The first page is dynamically constructed based on a combination of regional templates and contains one or more functional areas. The content of each functional area is rendered based on the corresponding target view data, and the layout and interaction methods are adapted to the terminal characteristics of the first device (such as the touch page of a PAD), so as to fully present all the functions required for the current business type for the service provider to operate and view.

[0070] It should be noted that when the first page is loaded for the first time, the backend does not return empty area template data. Instead, it immediately calls the processing unit corresponding to each functional area to generate initial target view data for rendering based on default parameters. Subsequent user operations (such as filtering and calculation) trigger content generation tasks, which are based on specific area template identifiers, call the processing unit again with new operation parameters to generate updated target view data. Both are rendering data with the same structure, and the only difference is the triggering time, input parameters, and scope of application.

[0071] In step 305, the first device initiates a content generation task.

[0072] This task is triggered by the service provider's operation on a specific functional area on the first page (such as adjusting parameters, clicking calculation, or confirming filter conditions). It is used to request the update or generation of target content information for that functional area. The task includes the area template identifier of the selected functional area to be processed and the constraints generated based on the service provider's operation. The content generation task is the basis for the backend to call the processing unit and generate new target view data.

[0073] In step 306, the backend performs a content generation task to obtain target view data and stores the target view data in a shared database.

[0074] Specifically, after receiving the content generation task, the backend finds the corresponding processing unit in the first mapping table based on the region template identifier carried in the task, and obtains the associated region template data based on the identifier. Subsequently, the processing unit performs data query, calculation or combination processing according to the operation parameters (i.e. constraints) provided by the user to generate target view data that conforms to the region template structure, and stores the target view data in the shared database.

[0075] The shared database grants read access to both the first and second devices. When the second device subsequently initiates a read request, it can directly obtain the generated target view data and adjust the display (such as layout and component visibility) only according to its own terminal characteristics, without recalculating or accessing the original data source. This ensures data consistency across multiple devices and avoids redundant calculations and logical discrepancies.

[0076] In step 307, the backend returns the target view data to the first device.

[0077] During this process, the backend will dynamically adjust the display part of the target view data according to the pre-configured display rules adapted to the device type of the first device—for example, retaining the editing controls, displaying internal fields, and using native UI component layout; while the content part (i.e. the actual business data) remains unchanged, and only the presentation format is customized for the terminal, thereby ensuring that the first device obtains rendering data that is both consistent with its interactive capabilities and strictly consistent with the original calculation results.

[0078] In step 308, the first device sends a browsing connection to the second device.

[0079] The browsing link embeds key information to identify the business context, including the business type of the page, the identifiers of one or more regional templates involved, and may also include access credentials for the target view data in the shared database. After the second device receives a click on this link from the service recipient, it will be redirected to the H5 entry page.

[0080] Further, in step 309, a read request is sent to the backend. The read request includes the region template identifier and may also include access credentials for the target view data in the shared database.

[0081] In step 310, the backend generates customized target view data.

[0082] In response to a read request, the backend retrieves the target view data corresponding to the region template identifier from the shared database and searches for a matching display rule in the second mapping table based on the type of the device from which the request originated. Subsequently, the display portion of the target view data is adapted according to this rule (e.g., hiding internal fields, adding sharing components, adjusting formatting, etc.) to generate customized rendering data for that device, while the content remains unchanged, ensuring data consistency across multiple devices and flexible display. Display rules can be designed according to actual display needs and are not restricted here. The second mapping table records the correspondence between terminal types and display rules.

[0083] Device types can be categorized based on the user's role and the technology used: by role, service provider devices and service recipient devices; by technology, native application clients and web clients, etc. Of course, other device types are also possible and are not limited here.

[0084] In step 311, the backend synchronizes the customized target view data to the second device. Further, the second device executes step 312, rendering the target content information on the second page.

[0085] When a new business display function needs to be added, only the corresponding regional template data needs to be independently written and assigned a unique regional template identifier. At the same time, a dedicated processing unit is developed to implement the business logic of this function. The entire process does not require modification or impact on any existing regional template data, processing units, or page structure. Integration can be completed simply by adding the binding relationship between the regional template identifier and the processing unit in the first mapping table. This highly decoupled design gives the system good scalability and maintainability, supports plug-and-play functionality, and significantly reduces iteration costs and error risks.

[0086] Figure 5 This is a schematic diagram of the first page according to an embodiment of the present disclosure.

[0087] Figure 5 This demonstrates a sample first page designed for a specific business scenario. The electronic device for which this page is applied is the first device, such as a tablet. The first page provides option tabs for three different business types: Business Type 1, Business Type 2, and Business Type 3, each corresponding to different application scenarios and service requirements. The current view highlights the page layout and functional modules after selecting "Business Type 1".

[0088] After selecting "Business Type 1", functional areas a and b will be displayed on the first page. These two areas are designed to meet the specific operational needs of this business scenario. Functional area a is further subdivided into two sub-functions: function a1 and function a2, which support more detailed operation processes respectively. The same design concept is also reflected in functional area b, which contains function b1 and function b2, providing users with a more comprehensive service experience.

[0089] It should be noted that functional areas A and B are rendered using independent area template data to generate corresponding target view data. Before displaying functional areas A and B, the backend first receives a page display request for business type 1. Then, it identifies and determines the template combination suitable for business type 1, i.e., selects the corresponding area template data for functional areas A and B. This process ensures that each functional area accurately presents content according to business requirements. After determining the most suitable template combination for business type 1, the corresponding processing unit is invoked to parse and process the selected area template data, thereby generating the final target view data for functional areas A and B.

[0090] To ensure clear information presentation, each functional area is equipped with an independent content display area to show the target content information generated after executing the corresponding sub-function. In functional area b, a convenient "confirm" button is provided. This button allows the service provider to submit all operations and generate the content task after completing a series of sub-function selections or edits.

[0091] Furthermore, to enhance the convenience of information sharing, the first page also features a "share button." Using this function, service providers can easily share the target content information from the first page as a link with the recipients who need it, making information transmission more efficient and faster. This design not only improves work efficiency but also greatly enhances the smoothness and satisfaction of the user experience.

[0092] For example, when a user selects "Business Type 1" (such as "Asset Operation") on the PAD, the backend recognizes the request and loads the corresponding area template combination—including area template data for "Property Filtering and Comparison" and area template data for "Revenue Calculation." Subsequently, the processing units bound to these two template data are called respectively to generate target view data based on default parameters (such as all assets currently managed by the user). Finally, functional area a renders an interactive property list and filtering controls (including "Function a1: Map Positioning" and "Function a2: Condition Reset"), while functional area b displays the revenue calculation interface (including "Function b1: Parameter Settings," "Function b2: Historical Comparison," and a "Confirmation Button"). Together, they constitute a complete asset operation page, and the results can be sent to the owner via the "Share Button" at the top for viewing on the H5 platform.

[0093] Figure 6 This is a schematic diagram of the second page according to an embodiment of the present disclosure.

[0094] Figure 6 This is a second page (e.g., an H5 page) displayed on a second device (e.g., a mobile phone), for the service recipient (e.g., a property owner, tenant) to browse content shared by the first device. It includes a "forward button" at the top and two functional areas: functional area a and functional area b. Each functional area displays only "target content information," which is the target view data generated and stored in the shared database after the first device's operation. The content is complete but does not offer editing or interactive operations. A "Business Type 1" label is retained on the left to clearly indicate the current business scenario.

[0095] This page obtains the necessary information by parsing the browsing link shared by the first device. The backend retrieves the corresponding target view data from the shared database based on the region template identifier carried in the link, and adapts the display to the characteristics of the second device's terminal (such as an H5 browser), for example, by hiding the confirmation button, simplifying the layout, and adding a share button. Therefore, although the second page does not support complex operations, it can accurately reproduce the operation results of the first device, ensuring consistent display across multiple devices. The "share button" at the top allows users to share the current page again with others, realizing secondary dissemination of information.

[0096] After the asset manager completes the "Asset Operation" business operation on the first device—for example, filtering two high-quality properties through functional area A and entering parameters such as rent and loan ratio in functional area B to complete the return calculation—a browsing link (mainly containing the corresponding area template identifiers) will be generated, indicating the target view data for these two functional areas. When the property owner clicks this link on the second device, it is equivalent to sending a read request to the backend, thus entering… Figure 6 The page in the middle.

[0097] The second page displays a "forward button" at the top, allowing homeowners to easily share property listings and revenue analysis results with family members. The main page replicates functional areas A (such as the property list and map location) and B (such as annualized return A%, cash flow charts, etc.), with content identical to the first page on the first device, but only for viewing: all editing controls (such as parameter input boxes and confirmation buttons) are hidden, retaining only a static display. The backend, based on the characteristics of the second device, retrieves the generated target view data from the shared database and adapts the display (such as simplifying the layout and adapting to smaller screens), ensuring accurate information presentation without recalculation, truly achieving a one-time generation, consistent across multiple devices.

[0098] Figure 7 This is a schematic block diagram of the structure of a task processing apparatus according to an embodiment of the present disclosure. Figure 7 As shown, this disclosure proposes a task processing device 700, including: a task generation module 710, used to acquire a content generation task issued by a first device, the content generation task including a region template identifier of a functional area to be processed in a first page of the first device, the content generation task being used to drive the generation of target content information in the functional area to be processed; a task response module 720, used to call a processing unit corresponding to the region template identifier to execute the content generation task, obtain target view data, the target view data being rendered to display target content information; and a result sharing module 730, used to respond to receiving a read request containing a region template identifier issued by a second device, synchronize the target view data to the second device, so that the second device renders the target view data to display the target content information on a second page of the second device.

[0099] The task processing apparatus 800 disclosed herein may be in the form of computer software, and each module of the task processing apparatus 800 may be in the form of computer software modules.

[0100] The various modules of the task processing device 800 disclosed herein are set up to implement the various steps of the task processing method. Their execution principles and steps can be referred to the above text and will not be repeated here.

[0101] Figure 8 This is a schematic block diagram of an electronic device according to one embodiment of the present disclosure. Figure 8 As shown, this disclosure also provides an electronic device 1000, including: a processor 1200 and a memory 1300, the memory 1300 storing execution instructions; the processor 1200 executes the execution instructions stored in the memory 1300, causing the processor 1200 to perform a task processing method.

[0102] The hardware architecture of the electronic device 1000 can be implemented using a bus architecture. The bus architecture can include any number of interconnect buses and bridges, depending on the specific application of the hardware and overall design constraints. Bus 1100 connects various circuits, including one or more processors 1200, memory 1300, and / or hardware modules. Bus 1100 can also connect various other circuits 1400, such as peripheral devices, voltage regulators, power management circuits, external antennas, etc.

[0103] Bus 1100 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Component (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, this diagram uses only one connection line, but this does not imply that there is only one bus or one type of bus.

[0104] This disclosure also provides a readable storage medium storing a computer program that, when executed by a processor, is used to implement the methods described above. A "readable storage medium" can be any means capable of containing, storing, communicating, propagating, or transmitting a program for use by or in conjunction with an instruction execution system, apparatus, or device. More specific examples of a readable storage medium include: an electrical connection with one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and portable read-only memory (CDROM), etc.

[0105] This disclosure also provides a computer program product, the methods of which can be implemented wholly or partially through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented wholly or partially as a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed, all or part of the processes or functions of this disclosure are performed.

[0106] Computer programs or instructions can be stored in a readable storage medium or transferred from one readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The readable storage medium can be any available medium capable of access, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video optical disc; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or it can include both volatile and non-volatile types of storage media.

[0107] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, electronic devices, readable storage media, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0108] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0109] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0110] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0111] In the description of this specification, the references to terms such as "one embodiment / mode," "some embodiments / modes," "example," "specific example," or "some examples," etc., refer to specific features, structures, or characteristics described in connection with that embodiment / mode or example, which are included in at least one embodiment / mode or example of this disclosure. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment / mode or example. Moreover, the specific features, structures, or characteristics described may be combined in any suitable manner in one or more embodiments / modes or examples. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments / modes or examples described in this specification, as well as the features of different embodiments / modes or examples.

[0112] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0113] Those skilled in the art should understand that the above embodiments are merely for illustrating the present disclosure and are not intended to limit the scope of the disclosure. Those skilled in the art can make other changes or modifications based on the above disclosure, and these changes or modifications still fall within the scope of the present disclosure.

Claims

1. A task processing method, characterized in that, include: Obtain a content generation task issued by a first device. The content generation task includes a region template identifier of a functional area to be processed in the first page of the first device. The content generation task is used to drive the generation of target content information in the functional area to be processed. The processing unit corresponding to the region template identifier is invoked to execute the content generation task, obtain target view data, and the target view data can be rendered to display the target content information; as well as In response to receiving a read request containing the region template identifier from the second device, the target view data is synchronized to the second device, so that the second device renders the target view data to display the target content information on the second page of the second device.

2. The task processing method according to claim 1, characterized in that, Before invoking the processing unit corresponding to the region template identifier to execute the content generation task, the following steps are included: Identify the region template identifier indicated in the content generation task; and Based on the first mapping table, a processing unit corresponding to the region template identifier is determined. The first mapping table records the correspondence between the region template identifier and the processing unit. The processing unit can process the region template data with the region template identifier and display the target content information in the corresponding functional area.

3. The task processing method according to claim 1, characterized in that, After receiving a read request containing the region template identifier from the second device, the method further includes: Determine the terminal type that initiated the read request, wherein the terminal type includes a first device type and a second device type; Based on the second mapping table, display rules applicable to the terminal type are determined, wherein the second mapping table records the correspondence between terminal types and display rules; and The display portion of the target view data is processed according to the display rules to form customized target view data. The customized target view data is rendered to present the target content information in a manner that conforms to the display rules.

4. The task processing method according to claim 1, characterized in that, After obtaining the target view data, the following is included: The target view data is written into a shared database, which can be accessed by the first device and the second device.

5. The task processing method according to claim 1, characterized in that, Before receiving the content generation task issued by the first device, the process includes: In response to a page display request initiated by the first device, a region template combination is determined based on the business category associated with the page display request. The region template combination includes multiple region template data related to the business category, and the region template data, through rendering, can realize at least one business display function for the business category. The first page is displayed on the first device, and the first page has functional areas corresponding to the area template data.

6. The task processing method according to claim 5, characterized in that, Displaying the first page on the first device includes: In response to a loading command initiated by the first device, one or more functional areas are displayed on the first page according to the rendering method indicated by the loading command. The rendering method includes rendering templates one by one and rendering templates in batches.

7. The task processing method according to claim 1, characterized in that, Also includes: Configure the region template identifier and processing unit for the region template data; as well as The region template identifier and the processing unit are bound together to generate a first mapping table.

8. An electronic device, characterized in that, include: The memory stores execution instructions; as well as A processor that executes execution instructions stored in the memory, causing the processor to perform the task processing method according to any one of claims 1 to 7.

9. A readable storage medium storing executable instructions, which, when executed by a processor, implement the task processing method of any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the task processing method according to any one of claims 1 to 7.

Images