Data processing method, electronic device, and computer program product

Abstract

The present disclosure provides a data processing method, an electronic device and a computer program product. The data processing method of the present disclosure comprises: generating configuration information according to an interface parameter of a data maintenance system, the configuration information recording a data routing configuration item and a feedback processing configuration item suitable for the interface parameter; sending the data to be reported to the data maintenance system according to the data routing configuration item; and in response to receiving a reporting state of the data to be reported from the data maintenance system, generating a processing scheme suitable for the reporting state based on the feedback processing configuration item.

Description

Technical Field

[0001] This disclosure relates to the technical fields of data processing, and in particular to a data processing method, electronic device, and computer program product. Background Technology

[0002] In real estate services, agents need to register with the developer before showing a property to a client and obtain a viewing certificate before they can proceed. The current registration process relies on manual intermediaries from the developer's staff, who manually enter the necessary data into the system and then synchronize the registration results and viewing certificate to the agent. This model suffers from data transmission delays and inability to process data outside of working hours, impacting viewing efficiency. Summary of the Invention

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

[0004] According to one aspect of this disclosure, a data processing method is provided, comprising: generating configuration information based on interface parameters of a data maintenance system, the configuration information recording data routing configuration items and feedback processing configuration items applicable to the interface parameters; sending data to be reported to the data maintenance system according to the data routing configuration items; and, in response to receiving a reporting status from the data maintenance system regarding the data to be reported, generating a processing scheme applicable to the reporting status based on the feedback processing configuration items.

[0005] According to one technical solution, by abstracting the interface parameters of the data maintenance system into configuration information, and defining data delivery rules and status response logic with data routing configuration items and feedback processing configuration items respectively, a configuration-driven data reporting process is achieved. Compared with the fixed docking mode that relies on manual relay in the existing technology, this method, on the one hand, can flexibly adapt to the differentiated interface requirements of different data maintenance systems through the scalability of configuration information, and can complete the access of new systems without modifying the underlying processing logic, thus reducing maintenance costs; on the other hand, based on the preset feedback processing configuration items, it can automatically generate corresponding processing solutions for different reporting statuses, eliminating manual judgment and manual operation links, realizing full-link automation from data sending, status confirmation to subsequent processing, and effectively improving the efficiency and accuracy of data reporting.

[0006] In some implementations, configuration information is generated based on the interface parameters of the data maintenance system, including: generating a data routing configuration item that records the correspondence between the reportable items of the data maintenance system and the permission information of the reporter, based on the project mapping rules in the interface parameters; generating a feedback processing configuration item that records the correspondence between the reporting status and the processing scheme, based on the data processing rules in the interface parameters; and obtaining the configuration information containing the data routing configuration item and the feedback processing configuration item.

[0007] According to one technical solution, the project mapping rules solidify the correspondence between the reporter's permissions and the projects that can be reported as configuration items, solving the permission routing problem when interfacing with heterogeneous systems. The data processing rules solidify the correspondence between the reporting status and the processing solution as configuration items, solving the problem of different systems needing to execute differentiated responses to the same status. Both are integrated through unified configuration information, enabling the data delivery logic and status processing logic to be configured and flexibly adjusted independently, while also operating collaboratively as a whole, demonstrating the scalability and maintainability advantages of a configuration-based architecture.

[0008] In some implementations, in response to receiving the reporting status of the data maintenance system regarding the data to be reported, a processing scheme suitable for the reporting status is generated based on the feedback processing configuration item, including: based on the feedback processing configuration item, when the reporting status is a successful status, generating a storage instruction for the data to be reported and generating a first display request for the successful status, wherein the requested party of the first display request is the reporter of the data to be reported.

[0009] In some implementations, in response to receiving the reporting status of the data to be reported from the data maintenance system, a processing scheme suitable for the reporting status is generated based on the feedback processing configuration item, including: based on the feedback processing configuration item, when the reporting status is a first type of failure status, generating a completion request for user characteristics in the data to be reported, a second display request for the first type of failure status, or a manual processing prompt message, wherein the requested parties of the completion request and the second display request are both the reporter of the data to be reported.

[0010] In some implementations, in response to receiving the reporting status of the data to be reported from the data maintenance system, a processing scheme suitable for the reporting status is generated based on the feedback processing configuration item, including: based on the feedback processing configuration item, when the reporting status is a second type of failure status, generating a third display request or manual processing prompt information for the second type of failure status, wherein the requested party of the third display request is the reporter of the data to be reported.

[0011] In some implementations, sending the data to be reported to the data maintenance system according to the data routing configuration item includes: determining, based on the reporting person's permission information, the target project for which the reporting person can report data in the data routing configuration item, wherein the permission information includes the reporting person's identity information and an interface key for the target project; and after determining the target project, sending the data to be reported to the data maintenance system according to the data receiving address for the target project in the data routing configuration item.

[0012] In some implementations, the method further includes: when receiving data to be updated regarding user characteristics, generating an update request for user characteristics and / or business metrics associated with the data identifier in the data to be updated, wherein the requestee of the update request is the data maintenance system.

[0013] In some implementations, it further includes: a settings page that provides configuration information, the settings page including acquisition controls for the data routing configuration item and acquisition controls for the feedback processing configuration item.

[0014] In some implementations, the method further includes: providing a pending prompt control, the pending prompt control displaying at least one of manual processing prompt information, a reporting status option key, and a forwarding key, wherein the manual processing prompt information includes a failure reason.

[0015] 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 data processing method according to any embodiment of this disclosure.

[0016] According to another aspect of this disclosure, a readable storage medium is provided, wherein executable instructions are stored therein, which, when executed by a processor, are used to implement a data processing method according to any embodiment of this disclosure.

[0017] 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 data processing method described in any embodiment of this disclosure. Attached Figure Description

[0018] 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.

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

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

[0021] Figure 3 This is a flowchart illustrating the process of determining configuration information according to an embodiment of this disclosure.

[0022] Figure 4 This is a schematic diagram of a settings page according to an embodiment of the present disclosure.

[0023] Figure 5 This is a flowchart of the processing scheme generated according to the embodiments of this disclosure.

[0024] Figure 6 This is a schematic diagram of a pending prompt control according to an embodiment of the present disclosure.

[0025] Figure 7 This is a schematic diagram of a filing certificate according to an embodiment of the present disclosure.

[0026] Figure 8 This is a flowchart of the routing process according to an embodiment of the present disclosure.

[0027] Figure 9 This is a schematic block diagram of the structure of a data processing apparatus according to an embodiment of the present disclosure.

[0028] Figure 10 This is a schematic block diagram of an electronic device according to one embodiment of the present disclosure. Detailed Implementation

[0029] 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.

[0030] 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.

[0031] In real estate service scenarios, before a real estate agent can show a property to a client, they need to register with the developer first. The current registration process heavily relies on manual intermediaries: the agent submits their authorization information, user characteristics, and other registration data to on-site staff, who then manually enter it into the developer's system. Once the developer's system confirms successful registration, the registration result and supporting documentation are synchronized back to the agent.

[0032] The manual model suffers from significant efficiency bottlenecks. Data transmission relies entirely on manual operation, resulting in significant delays in information flow. Furthermore, the lack of timely processing outside of working hours directly impacts the progress of property viewings. When submitted user characteristics are incomplete or limited, automatic responses are impossible, requiring brokers to repeatedly communicate with intermediary staff and submit supplementary information, increasing communication costs and time expenditure.

[0033] Manual operation involves dealing with multiple different system interfaces and processes, resulting in high learning costs and a high risk of errors. Different developers use different systems with inconsistent integration standards, requiring business personnel to understand the usage methods and processes of various system interfaces, incurring significant learning costs and limiting the flexibility of business expansion.

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

[0035] Figure 1 This is a schematic diagram illustrating an application scenario of the data processing method according to embodiments of this disclosure. For example... Figure 1 As shown, in this application scenario, a server 100 and a terminal device 200 may be included. 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, television, projector, mobile phone, or tablet. The server 100 can receive requests from the terminal device 200 and execute the data processing method disclosed herein.

[0036] Figure 2 This is a flowchart of a data processing method according to an embodiment of this disclosure. For example... Figure 2 As shown, this disclosure proposes a data processing method M200, which generates corresponding configuration information for the data maintenance system based on the interface parameters, and executes an automated data forwarding and processing scheme generation logic based on the configuration information, thereby eliminating manual transfer links, improving reporting efficiency, and adapting to the differences of different systems, with good scalability and efficiency.

[0037] Step S210: Generate configuration information based on the interface parameters of the data maintenance system.

[0038] A data maintenance system is a system used to receive, store, and maintain data to be reported. It can determine whether the data to be reported is duplicated and provide feedback on the reporting status based on the determination.

[0039] In practical applications, a data maintenance system can be a business platform that requires centralized management of data to be reported. For example, in a real estate service scenario, the data maintenance system can specifically be a developer's business system used to record user characteristics submitted by various viewing channels and to maintain business metrics (such as the number of viewings) for each viewing channel.

[0040] Different data maintenance systems have varying interface parameters due to differences in the business needs or hardware characteristics of their maintenance entities. For example, project mapping rules and data processing rules may differ. Therefore, using a fixed set of logic to interface with all data maintenance systems would be incompatible with their individual requirements. To address this, this solution generates and maintains corresponding configuration information for each data maintenance system based on its individual interface parameters. This enables adaptive access to heterogeneous systems within a unified processing framework. Compared to hard-coding, configurable interface parameters offer greater flexibility, universality, and scalability when integrating with different data maintenance systems. Furthermore, it reduces maintenance costs for iterating interface parameters when maintaining existing systems.

[0041] Configuration information is the result of organizing and recording data routing rules and feedback processing rules in a configurable form based on the interface parameters of the data maintenance system. Compared to hard-coding, configuration information can be visually managed and dynamically adjusted through a settings page. It can adapt to the personalized requirements of different data maintenance systems without modifying the underlying program, reducing system maintenance costs and providing good scalability.

[0042] Step S220: Send the data to be reported to the data maintenance system according to the data routing configuration items.

[0043] Data routing configuration items are determined according to data routing rules. They record the correspondence between reportable items in the data maintenance system and the permission information of the reporter, and are used to determine which specific project management unit in the data maintenance system the data to be reported should be sent to. A configuration message can contain multiple data routing configuration items, each corresponding to at least one type of permission information for a reportable item. The permission information includes the reporter's identity information and the interface key of the target project to be reported.

[0044] For example, if a reportable project X allows brokers from the first channel to show the project, then the data routing configuration item would be "Reportable Project X: Source is the first channel". When a reporter's permission information records "Source is the first channel", the reportable project X can be used as the reporter's target project, and then the data to be reported provided by the reporter will be sent to the data receiving address of the reportable project X.

[0045] It should be noted that the list of reportable items is determined based on the items that the maintenance entity of the data maintenance system intends to maintain, and the number of items maintained by different maintenance entities may vary. The data maintenance system can be subdivided into multiple management units according to the reportable items. Each management unit can independently maintain a database for its corresponding item to store the relevant data. These management units can have a unique data receiving address to ensure accurate storage of the data to be reported. Of course, if the data maintenance system does not configure management units for each item, then the data receiving address can share the same entry address of the data maintenance system without restriction.

[0046] Data to be reported refers to data submitted by the reporter and required to be reported to the data maintenance system. This data contains at least two parts: first, the reporter's permission information, including their identity information (e.g., role, source) and the interface key for the target project, used by the data maintenance system for identity verification and permission checks; second, user characteristics, which may include unique identifiers for user confirmation and recording by the data maintenance system. The data to be reported serves as the initial input for the subsequent automated forwarding and processing flow of this method, and its format can be adapted according to the interface parameters of the data maintenance system.

[0047] Step S230: In response to receiving the reporting status of the data to be reported from the data maintenance system, a processing scheme suitable for the reporting status is generated based on the feedback processing configuration items.

[0048] The reporting status refers to the result identifier returned by the data maintenance system after verifying the data to be reported. It includes at least a success status, a first-type failure status, and a second-type failure status. A success status indicates that the data to be reported has been recorded by the data maintenance system. A first-type failure status indicates that the user characteristics in the data to be reported are the same as the user characteristics already existing in the data maintenance system, but these user characteristics are incomplete due to limited information, and therefore cannot be effectively confirmed. A second-type failure status indicates that the complete and authentic user characteristics provided in the data to be reported are consistent with the user characteristics already recorded in the data maintenance system, indicating that the user is an existing user, not an incremental user.

[0049] The feedback processing configuration items are determined according to the data processing rules. They record the correspondence between the reporting status returned by the data maintenance system and the processing scheme to be executed based on that status. This is used to indicate that differentiated responses should be automatically made when feedback results of different reporting statuses are received. A configuration message can contain multiple feedback processing configuration items, each corresponding to a reporting status and at least one applicable processing scheme.

[0050] For example, the processing solution for a successful status could be to generate a storage instruction for the data to be reported, or to generate a first display request for the successful status. Of course, in the settings interface, the processing solution for a successful status can be expressed in a more concise way, and the form of the corresponding data collection control is not limited.

[0051] It should be noted that the aforementioned storage instruction is responded to by the system executing the data processing method, not by the data maintenance system. The requested party for the first display request can be the terminal device corresponding to the reporter, used to display the reporting status to the reporter as proof of successful reporting, so that the reporter can view it on a mobile device or use it as valid proof for on-site inspection.

[0052] A processing scheme refers to the task determined and executed by the system based on the received reporting status and the feedback processing configuration items in the configuration information. The processing scheme is not a fixed logic but is dynamically determined by the preset correspondence in the configuration information. The same reporting status can correspond to different processing schemes in the configuration information of different data maintenance systems. This on-demand configurable mechanism demonstrates the flexibility advantage of this solution in addressing differentiated needs.

[0053] Figure 3 This is a flowchart illustrating the process of determining configuration information according to embodiments of this disclosure. For example... Figure 3 As shown, this disclosure proposes a process for determining configuration information.

[0054] In this embodiment, steps 301 to 303 are proposed, namely: generating a data routing configuration item that corresponds to the reportable items of the record data maintenance system and the permission information of the reporter according to the project mapping rules in the interface parameters; generating a feedback processing configuration item that corresponds to the record reporting status and the processing scheme according to the data processing rules in the interface parameters; and obtaining configuration information containing the data routing configuration item and the feedback processing configuration item.

[0055] Project mapping rules refer to the rules in the interface parameters that define the correspondence between the permission information of the reporter and the projects that can be reported in the data maintenance system. They serve as the basis for generating data routing configuration items. Project mapping rules are set according to the scope of projects that the maintenance entity of the data maintenance system expects to manage, specifying which reporters have the permission to report to which projects. Since different maintenance entities maintain different numbers of projects and different organizational methods, the specific content of project mapping rules also varies. This solution manages them through configuration, thereby achieving flexible adaptation to heterogeneous systems.

[0056] Data processing rules refer to the rules in the interface parameters used to define the correspondence between reporting status and processing solutions. They serve as the basis for generating feedback processing configuration items. Data processing rules are set according to the processing requirements of the maintenance subjects of the data maintenance system for the verification results of the reported data. They specify the appropriate response operations to be performed when the reporting status is successful, a first-type failure status, or a second-type failure status. Since different maintenance subjects may expect different processing methods for the same reporting status, the specific content of the data processing rules also varies. This solution manages them through configuration to execute the processing logic required by different data maintenance systems.

[0057] Figure 4 This is a schematic diagram of a settings page according to an embodiment of this disclosure. For example... Figure 4 As shown, this demonstrates a visual representation of the settings page.

[0058] This settings page is displayed on the screen of the terminal device, which can be... Figure 1 Terminal equipment 200.

[0059] The settings page provides a visual configuration channel for data routing and feedback handling configuration items. The settings page consists of two parts: the first part is the configuration area for data routing at the top of the page; the second part is the configuration area for feedback handling at the bottom of the page.

[0060] The configuration area of ​​the data routing configuration item contains a data collection control for permission information of reportable items A to X, where the number of reportable items is unlimited. Based on the characteristics of the data routing configuration item, this data collection control can be in the form of a text box. When no valid permission information is entered, the data collection control is in its first display state, i.e., the text box displays the words "Permission Information" in gray font, prompting relevant business personnel to configure it. The specific content of the permission information corresponding to the reportable items is filled in according to the data routing rules and is not restricted here.

[0061] The configuration area for feedback processing includes control over the collection of various reporting statuses, such as success, first-type failure, and second-type failure. These control options are presented as choices. Specifically, for success, there are push and store options; for first-type failure, there are auto-completion, confirm failure, and transfer to manual processing options; and for second-type failure, there are confirm failure and transfer to manual processing options. When relevant personnel select the corresponding option based on the processing rules for each reporting status, the option changes from a grayed-out pending second-type display to a blue selected third-type display.

[0062] Additionally, the push option corresponds to a processing scheme for generating storage instructions for the data to be reported; the storage option corresponds to a processing scheme for generating the first display request for a successful status. The auto-completion option corresponds to a processing scheme for generating a completion request for user characteristics in the data to be reported; the failure to report option corresponds to a processing scheme for a second display request for the first type of failure status, or a third display request for the second type of failure status; and the transfer to manual processing option corresponds to a processing scheme for generating manual prompts.

[0063] On the settings page, instead of displaying all the details of each processing solution, business users can choose and configure them using simple and intuitive options. This interaction method reduces the complexity of the configuration process, abstracting the diverse underlying processing logic into easy-to-understand options, thus improving configuration efficiency and readability.

[0064] It should be noted that the specific presentation of the data collection control can be set according to requirements, and can take the form of a drop-down selection box, radio button, or switch, etc. The data collection control only affects the interaction method of the configuration process and does not change the correspondence between it and the corresponding configuration items. This correspondence is determined by the interface parameters. The style and layout of the settings page can also be selected according to actual needs. This implementation method is only a feasible example.

[0065] Figure 5 This is a flowchart illustrating the process of generating a processing solution based on the embodiments of this disclosure. For example... Figure 5 The diagram illustrates the process of generating the processing solution.

[0066] In this embodiment, steps 501 to 502 are proposed, namely: determining whether the reporting status is a successful status; when the reporting status is a successful status, based on the feedback processing configuration item, generating a storage instruction for the data to be reported and generating a first display request for the successful status, wherein the requested party of the first display request is the reporter of the data to be reported.

[0067] The storage instruction is used to instruct the system executing the data processing method to locally store the data to be reported and its corresponding data identifier in the data maintenance system. This data identifier is returned by the data maintenance system after successful reporting and is used to uniquely identify the data to be reported within the system. Subsequent operations such as voucher retrieval and information updates can be performed based on this data identifier.

[0068] The first display request is a command sent to the reporting party's terminal device to display a successful status. The content carried in this request may include a success status message, or a data identifier corresponding to the data to be reported in the data maintenance system. This data identifier may be presented in the form of a QR code or other graphic code, used to locate the user characteristics or other changed business indicators stored in the data to be reported in the data maintenance system. Here, user characteristics may refer to the personalized characteristics of the users maintained by the reporting party.

[0069] The first display of the generated QR code and other information can serve as valid proof for the person reporting to show the data to the maintenance body of the data maintenance system, or it can simply serve as a status notification of successful reporting. The specific presentation format is not limited here.

[0070] Steps 503 to 504 are also proposed to determine whether the reporting status is a first type of failure status; based on the feedback processing configuration item, when the reporting status is a first type of failure status, a request to complete the user characteristics in the data to be reported, a second display request for the first type of failure status, or a manual processing prompt message are generated, wherein the requested party of the completion request and the second display request are both the reporter of the data to be reported.

[0071] When the reporting status is determined to be a first-type failure status, based on the preset processing scheme in the feedback processing configuration item, one of the following three processing methods can be selected: completion request, second display request, or generation of manual processing prompt information.

[0072] A completion request is a request instruction initiated by the reporter to obtain complete information about the user characteristics in the data to be reported. This request instructs the reporter to provide supplementary user characteristics that were not fully submitted previously due to restrictions, so that the system can repackage the data to be reported after obtaining the complete information and resend the reporting request to the data maintenance system.

[0073] In real estate service scenarios, the reporter can be a real estate agent, and the user characteristics in the data to be reported can include the user's mobile phone number, name, etc.; the identity information can be the company or store code to which the real estate agent belongs, or the real estate agent's job title, etc. The data maintenance system can be the developer's business system, and the target project can be a specific real estate project under the developer.

[0074] In this scenario, before showing a property to a client, the real estate agent needs to submit the client's phone number, name, and other user characteristics to the developer's system for registration. Registration is successful when the client is confirmed as a new user maintained by the developer; otherwise, if the user information has already been registered through other channels, it is considered an existing user and does not require re-registration, resulting in a failed registration.

[0075] The usual way to determine if a user is a new user is to compare whether the phone number provided by the user already exists in the developer's system. However, if the phone number submitted by the user is incomplete, for example, only the first three and last four digits are provided while the middle digits are hidden, and this number happens to partially match a user's phone number already in the system, this situation falls under the first type of failure state. In this case, a completion request needs to be generated to obtain the user's complete and accurate phone number for verification again. Conversely, if the user has provided a complete and accurate phone number, but it still matches a user's number already in the system, this falls under the second type of failure state. In this case, there is no need to trigger a completion request; it can be directly determined as a reporting failure or transferred to manual processing.

[0076] The second display request is a display instruction initiated by the reporting party's terminal device to display the first type of failure status and its cause. The display content carried by this request may include a prompt message indicating the failure status, as well as a detailed explanation of the reasons for the failure, such as incomplete user characteristics or limited information, so that the reporting party can understand the reason for the unsuccessful reporting and take appropriate measures.

[0077] The manual processing prompt message is a message initiated by the system-side business personnel executing this method to prompt for manual intervention. This message includes a brief description of the data to be reported, the reason for failure, etc., notifying the business personnel to manually confirm the reporting status or proceed with further processing. It is suitable for scenarios that cannot be resolved through automated process closure.

[0078] This implementation also proposes step 505, which, based on the feedback processing configuration item, generates a third display request or manual processing prompt information for the second type of failure status when the reporting status is a second type of failure status. The requested party for the third display request is the person who reported the data to be reported.

[0079] When the reporting status is determined to be a second type of failure status, based on the preset processing scheme in the feedback processing configuration item, one of the following two processing methods will be selected to execute: generate a third display request, or generate a manual processing prompt message.

[0080] The second type of failure status refers to a situation where the user characteristics provided in the data to be reported are complete and true, but after verification by the data maintenance system, it is found that the user characteristics are consistent with the existing user characteristics already recorded in the system. This indicates that the user is not a newly added incremental user, but an existing user who has been successfully reported, and therefore there is no need to report and register again.

[0081] The third display request is a display instruction initiated by the reporting user's terminal device to display the second type of failure status and its cause. The display content carried by this request may include a prompt message indicating the reporting failure, as well as a detailed explanation of the reason for the failure, such as "This user is an existing user and does not need to report again," so that the reporting user can understand the current reporting status.

[0082] Unlike the first type of failure, the second type of failure occurs because the user's characteristics are already complete and accurate; the failure is due to the user being confirmed as an existing user. In this scenario, there is no situation where user characteristics are incomplete or need to be supplemented, therefore, there is no need to trigger a completion request. The failure result only needs to be communicated to the reporting party in the form of a third-party display request, or a manual processing prompt message needs to be generated to notify business personnel for further follow-up.

[0083] In some implementations, this solution provides a pending prompt control, which displays at least one of the following: manual processing prompt information, a reporting status option key, and a forwarding key. The manual processing prompt information includes the reason for failure.

[0084] Figure 6 This is a schematic diagram of a pending prompt control according to an embodiment of the present disclosure. For example... Figure 6 As shown, this demonstrates a visual representation of the pending prompt control.

[0085] The screen of the terminal device displays a pending task notification control. This page can be a task processing page, which may contain both task notification controls and pending task notification controls. In this image, the task notification control is located at the top of the screen, and the pending task notification control is located at the bottom of the screen. Of course, the layout and style of both are not limited to this.

[0086] The task prompt control displays the number of tasks pending approval, for example, 1. It also records the number of tasks submitted today, for example, 38. This provides business personnel with a clear and easy-to-view prompt method.

[0087] The pending processing prompt control includes a manual processing prompt message, a reporting status selection button, and a forwarding button. The manual processing prompt message displays a summary of the currently pending data to business personnel. This summary may include details of the target project (e.g., community name), user characteristics (e.g., characteristic A, characteristic B), the reporter's identity information (e.g., role), and the reason for failure (e.g., duplicate user characteristics). The reporting status selection button offers two options: reporting failure and reporting success, allowing business personnel to choose according to the actual situation. Selecting reporting failure indicates that the reporting has failed in the manual processing stage; selecting reporting success indicates that the reporting has been successfully completed in the manual processing stage.

[0088] A successful status confirmed by manual processing can be used as a reporting status provided by the data maintenance system to determine subsequent processing measures. A failed status confirmed by manual processing will trigger a second or third display request, but will not trigger other processing measures.

[0089] In some implementations, when the processing scheme is a first display request, a poster page containing the reporting status can be generated. The rendering data of this poster page is then provided to the reporter as part of the first display request, allowing the reporter's terminal device to directly render and display the poster page. The rendering data of the poster page includes reporting credentials, i.e., the data identifier of the data to be reported in the data maintenance system; the poster page may also include user characteristics, relevant information about the target project, etc.

[0090] Figure 7 This is a schematic diagram of a filing certificate according to an embodiment of this disclosure. For example... Figure 7 As shown, this displays the visual form of the filing certificate.

[0091] If the reporting status is successful and the processing plan is to generate a first display request, a feedback interface containing the reporting credentials can be displayed to the reporting user's terminal device. On this feedback page, the reporting credentials record the data identifier of the data to be reported in the data maintenance system in the form of a QR code. Below the reporting credentials, user characteristics (e.g., characteristics A and B), target project name (e.g., XX community), and reporting event (e.g., October 22, 2025) are also recorded.

[0092] Of course, the feedback page can also have other layouts and styles, such as a poster style; this is just one possible example.

[0093] It should be noted that the feedback page may not include the reporting credentials and may only return the reporting status. Furthermore, the information related to the data to be reported included on the feedback page is not limited to this and can be configured according to requirements.

[0094] Figure 8 This is a flowchart of the routing process according to an embodiment of this disclosure. For example... Figure 8 The diagram illustrates the routing process for data to be reported.

[0095] In this embodiment, steps 801 to 802 are proposed, namely: based on the permission information of the person reporting the data to be reported, the target project that the person reporting the data can report is determined in the data routing configuration item, and the permission information includes the identity information of the person reporting the data and the interface key of the target project; and after determining the target project, the data to be reported is sent to the data maintenance system according to the data receiving address of the target project in the data routing configuration item.

[0096] The target project is a specific project identified from the reportable projects based on the reporter's permission information, which the reporter has the authority to report data on. "Having authority" means that the reporter's identity information matches the project's permission information, and the interface key provided by the reporter is consistent with the project's interface key. A reportable project refers to a business unit managed by the maintenance entity of the data maintenance system, such as a specific building complex. Each reportable project can have a unique project identifier and a data receiving channel (i.e., data receiving address) for receiving data to be reported.

[0097] Identity information refers to credentials used to identify the person submitting the data. These credentials are matched against the permission information configured for the data-submitting project to determine whether the submitter is qualified to submit data for that project. This information can include the submitter's role, source (e.g., company affiliation), etc.

[0098] An interface key is an access credential associated with a reportable project and is pre-assigned by the maintenance body of the data maintenance system. During the routing process, the interface key provided by the reporter is compared and verified with the interface key pre-set by the target project. Only when the two match can it be confirmed that the reporter has legitimate reporting authority for that project.

[0099] The data receiving address refers to the network access endpoint used by the target project in the data maintenance system to receive the data to be reported. It is recorded in the data routing configuration item and is used to instruct the system to send the data to be reported to the target project.

[0100] In some implementations, the method further includes: when receiving data to be updated regarding user characteristics, generating an update request for user characteristics and / or business metrics associated with the data identifier in the data to be updated, wherein the requestee of the update request is the data maintenance system.

[0101] Data to be updated refers to data provided by the reporter for updating user characteristics or related business metrics that have been successfully reported. For example, when user characteristics change or business metrics such as viewing volume change, and the user characteristics and corresponding business metrics have been recorded in the data maintenance system, the data to be updated submitted by the reporter can trigger an automatic synchronization update process to the data maintenance system.

[0102] In some implementations, the method further includes: receiving a change notification pushed by the data maintenance system when user characteristics recorded in the data maintenance system change; parsing the change content in the change notification; and sending a maintenance reminder to the reporter via instant messaging to prompt the reporter to promptly confirm and maintain the changed information. This method ensures the consistency of information between the reporter and the data maintenance system, avoiding business deviations caused by information asynchrony.

[0103] In some implementations, the method further includes using the expiration time of user characteristics recorded in the data maintenance system as the sole data benchmark for the protection period. If the current time exceeds the expiration time corresponding to the user characteristic in the data maintenance system, the user characteristic and related information are deleted. The system running this method only retains the function of displaying the expiration time and no longer maintains another set of time standards, thus avoiding time inconsistencies and human errors caused by the two systems maintaining their own time standards.

[0104] Figure 9 This is a schematic block diagram of the structure of a data processing apparatus according to embodiments of the present disclosure. For example... Figure 9 As shown, this disclosure proposes a data processing apparatus 900, comprising: a configuration module 910, used to generate configuration information according to interface parameters of a data maintenance system, the configuration information recording data routing configuration items and feedback processing configuration items applicable to the interface parameters; a reporting module 920, used to send data to be reported to the data maintenance system according to the data routing configuration items; and a feedback module 930, used to, in response to receiving a reporting status from the data maintenance system regarding the data to be reported, generate a processing scheme applicable to the reporting status based on the feedback processing configuration items. The data processing apparatus 900 disclosed herein may be in the form of computer software, and each module of the data processing apparatus 900 may be in the form of computer software modules.

[0105] The various modules of the data processing apparatus 900 disclosed herein are set up to implement the various steps of the data processing method. Their execution principles and steps can be referred to the above text and will not be repeated here.

[0106] Figure 10 This is a schematic block diagram of an electronic device according to one embodiment of the present disclosure. Figure 10 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 execute a data processing method.

[0107] 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.

[0108] Bus 1100 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (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.

[0109] 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. The 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 readable storage media 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.

[0110] 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.

[0111] 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.

[0112] 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.

[0113] 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.

[0114] 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.

[0115] 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.

[0116] In the description of this specification, the references to the terms "an embodiment / mode," "some embodiments / modes," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, or characteristic described in connection with that embodiment / mode or example is 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. Furthermore, the specific features, structures, or characteristics described may be combined in any suitable manner in one or more embodiments / modes or examples. Moreover, 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.

[0117] 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 indicated technical features. 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, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0118] 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.

[0119] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0120] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0121] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0122] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0123] At the same time, it is understood that the data involved in this disclosed technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

Claims

1. A data processing method, characterized in that, include: Based on the interface parameters of the data maintenance system, configuration information is generated, which records data routing configuration items and feedback processing configuration items applicable to the interface parameters; According to the data routing configuration items, the data to be reported is sent to the data maintenance system; as well as In response to receiving the reporting status of the data to be reported from the data maintenance system, a processing scheme suitable for the reporting status is generated based on the feedback processing configuration item.

2. The data processing method according to claim 1, characterized in that, Based on the interface parameters of the data maintenance system, generate configuration information, including: Based on the project mapping rules in the interface parameters, a data routing configuration item is generated that records the correspondence between the reportable projects of the data maintenance system and the permission information of the reporter; Based on the data processing rules in the interface parameters, generate the feedback processing configuration item that records the correspondence between the reporting status and the processing scheme; and Obtain the configuration information, which includes data routing configuration items and feedback processing configuration items.

3. The method according to claim 1, characterized in that, In response to receiving a reporting status from the data maintenance system regarding the data to be reported, a processing scheme suitable for the reporting status is generated based on the feedback processing configuration items, including: Based on the feedback processing configuration item, when the reporting status is successful, a storage instruction for the data to be reported is generated, and a first display request for the successful status is generated. The recipient of the first display request is the reporter of the data to be reported.

4. The method according to claim 1, characterized in that, In response to receiving a reporting status from the data maintenance system regarding the data to be reported, a processing scheme suitable for the reporting status is generated based on the feedback processing configuration items, including: Based on the feedback processing configuration item, when the reporting status is a first type of failure status, a completion request for user characteristics in the data to be reported, a second display request for the first type of failure status, or a manual processing prompt message is generated, wherein the requested parties for the completion request and the second display request are both the reporter of the data to be reported.

5. The method according to claim 1, characterized in that, In response to receiving a reporting status from the data maintenance system regarding the data to be reported, a processing scheme suitable for the reporting status is generated based on the feedback processing configuration items, including: Based on the feedback processing configuration item, when the reporting status is a second type of failure status, a third display request or manual processing prompt information is generated for the second type of failure status, and the requested party of the third display request is the reporter of the data to be reported.

6. The method according to claim 1, characterized in that, According to the data routing configuration items, the data to be reported is sent to the data maintenance system, including: Based on the permission information of the person reporting the data to be reported, the target project for which the person reporting the data is authorized to report the data is determined in the data routing configuration item. The permission information includes the identity information of the person reporting the data and the interface key for the target project; and After the target project is determined, the data to be reported is sent to the data maintenance system according to the data receiving address of the target project in the data routing configuration item.

7. The method according to claim 1, characterized in that, Also includes: When data about user characteristics to be updated is received, an update request for user characteristics and / or business indicators associated with the data identifier in the data to be updated is generated based on the data identifier in the data to be updated. The requestee of the update request is the data maintenance system.

8. The data processing method according to claim 1, characterized in that, Also includes: A settings page that provides configuration information includes collection controls for the data routing configuration item and collection controls for the feedback processing configuration item.

9. 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 data processing method according to any one of claims 1 to 8.

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

Images