Data pushing method and device, computer device, storage medium and computer program product

Abstract

Embodiments of the present application provide a data pushing method and device, computer equipment, a storage medium and a computer program product, and relate to the technical field of big data. The method comprises: receiving a service client sending a service handling request for a to-be-handled service, and obtaining a target area code contained in the service handling request; if a target area corresponding to the target area code exists in a pushing area list, obtaining a service category identifier contained in the service handling request; if a service category corresponding to the service category identifier exists in a pushing service category list of a service front-end system, generating service handling information of the to-be-handled service; and pushing the service handling information to a service system. The method improves the timeliness of data pushing and service handling.

Description

Technical Field

[0001] This application relates to the field of big data technology, and in particular to a data push method, apparatus, computer equipment, storage medium, and computer program product. Background Technology

[0002] When the business service system provides services to various regions, users at each region level need to push their business application information to the business service system. During this data push process, there are certain requirements regarding the timeliness and standardization of the data.

[0003] Currently, the technology for pushing business application information from different regions to the business service system requires each region to connect with the system using its own regional interface. This process necessitates establishing data links between each region and the business service system. Furthermore, when multiple regions are pushing business application information to the system, the entire process becomes time-consuming and costly. Therefore, current data push technologies between different regions and the business service system suffer from low data push and business processing timeliness issues. Summary of the Invention

[0004] Therefore, it is necessary to provide a data push method, apparatus, computer equipment, storage medium, and computer program product to address the aforementioned technical problems.

[0005] Firstly, this application provides a data push method. The method includes:

[0006] Receive a service processing request sent by a service client for a service to be processed, and obtain the target area code contained in the service processing request;

[0007] If the target region corresponding to the target region code exists in the push region list of the pre-built business front-end system, then obtain the business category identifier contained in the business processing request;

[0008] If the business category corresponding to the business category identifier exists in the list of pushed business categories of the business front-end system, then the business processing information of the business to be processed is generated;

[0009] The business application information is pushed to the business service system; wherein, the target area corresponds to the first area level; the business front-end system and the business service system correspond to the second area level; the first area level is lower than the second area level.

[0010] In one embodiment, before the receiving service client sends a service processing request for the pending service, the method further includes: determining multiple regions corresponding to the service front-end system; the multiple regions belonging to the first region level; obtaining push permission information for each of the multiple regions; if the push permission information indicates that the corresponding region has enabled push permission, then adding the region to the push region list; the push permission indicates permission to push the service processing information of the pending service in the region to the service service system through the service front-end system.

[0011] In one embodiment, before the receiving service client sends a service processing request for the pending service, the method further includes: obtaining the regional service category of the push area in the push area list; obtaining the service category corresponding to the service front-end system; determining the association between the regional service category and the service category; and constructing the push service category list of the service front-end system based on the association.

[0012] In one embodiment, generating the business case information of the pending business includes: obtaining basic business information corresponding to the business processing request based on the business processing request; generating business processing information corresponding to the business processing request; generating the business case information corresponding to the business processing request based on the basic business information and the business processing information; storing the business case information in the push business category list, and marking the stored business case information as unpush information.

[0013] In one embodiment, pushing the business application information to the business service system includes: obtaining the push time contained in the business processing request; the push time being the push time for the business application information; according to the push time, obtaining the business tag information marked as the unpushed information corresponding to the business processing request from the push business category list; and pushing the business application information to the business service system according to the push time.

[0014] In one embodiment, after pushing the business application information to the business service system, the method further includes: if the push result of the business application information is a push failure, displaying a push failure prompt through the business client; receiving a re-push request sent by the business client based on the push failure prompt; retrieving the business application information from the push business category list based on the re-push request; and performing the step of pushing the business application information to the business service system.

[0015] In one embodiment, the method further includes: obtaining business query information for the business application information based on a processing information query request sent by the business client; obtaining processing flow information for the business application information based on the business query information; and displaying the processing flow information for the business application information through the business client.

[0016] Secondly, this application provides a data push device. The device includes:

[0017] The information acquisition module is used to receive business processing requests sent by the information receiving business client for the business to be processed, and to obtain the target area code contained in the business processing request;

[0018] The first judgment module is used to obtain the business category identifier contained in the business processing request if the target area corresponding to the target area code exists in the push area list of the pre-built business front-end system.

[0019] The second judgment module is used to generate the business processing information of the pending business if the business category corresponding to the business category identifier exists in the push business category list of the business front-end system.

[0020] The push module is used to push the business application information to the business service system; wherein, the target area corresponds to the first area level; the business front-end system and the business service system correspond to the second area level; the first area level is lower than the second area level.

[0021] In one embodiment, the information acquisition module is further configured to determine multiple regions corresponding to the business front-end system; the multiple regions belong to the first region level; acquire push permission information for each of the multiple regions; if the push permission information indicates that the corresponding region has enabled push permission, then add the region to the push region list; the push permission indicates permission to push the business application information of the pending business in the region to the business service system through the business front-end system.

[0022] In one embodiment, the information acquisition module is further configured to: acquire the regional business category of the push area in the push area list; acquire the business service category corresponding to the business front-end system; determine the association between the regional business category and the business service category; and construct the push business category list of the business front-end system based on the association.

[0023] In one embodiment, the second determining module is further configured to: obtain basic business information corresponding to the business processing request based on the business processing request; generate business processing information corresponding to the business processing request; generate business case information corresponding to the business processing request based on the basic business information and the business processing information; store the business case information in the push business category list, and mark the stored business case information as unpush information.

[0024] In one embodiment, the push module is further configured to: obtain the push time contained in the business processing request; the push time is the push time for the business application information; according to the push time, obtain the business tag information marked as the non-pushed information corresponding to the business processing request from the push business category list; and push the business application information to the business service system according to the push time.

[0025] In one embodiment, the push module is further configured to: if the push result of the business application information is a push failure, display a push failure prompt through the business client; receive a re-push request sent by the business client based on the push failure prompt; retrieve the business application information again from the push business category list based on the re-push request; and execute the step of pushing the business application information to the business service system.

[0026] In one embodiment, the information acquisition module is further configured to: acquire business query information for the business application information based on the processing information query request sent by the business client; acquire the processing flow information of the business application information based on the business query information; and display the processing flow information of the business application information through the business client.

[0027] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0028] Receive a service processing request sent by a service client for a service to be processed, and obtain the target area code contained in the service processing request;

[0029] If the target region corresponding to the target region code exists in the push region list of the pre-built business front-end system, then obtain the business category identifier contained in the business processing request;

[0030] If the business category corresponding to the business category identifier exists in the list of pushed business categories of the business front-end system, then the business processing information of the business to be processed is generated;

[0031] The business application information is pushed to the business service system; wherein, the target area corresponds to the first area level; the business front-end system and the business service system correspond to the second area level; the first area level is lower than the second area level.

[0032] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0033] Receive a service processing request sent by a service client for a service to be processed, and obtain the target area code contained in the service processing request;

[0034] If the target region corresponding to the target region code exists in the push region list of the pre-built business front-end system, then obtain the business category identifier contained in the business processing request;

[0035] If the business category corresponding to the business category identifier exists in the list of pushed business categories of the business front-end system, then the business processing information of the business to be processed is generated;

[0036] The business application information is pushed to the business service system; wherein, the target area corresponds to the first area level; the business front-end system and the business service system correspond to the second area level; the first area level is lower than the second area level.

[0037] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0038] Receive a service processing request sent by a service client for a service to be processed, and obtain the target area code contained in the service processing request;

[0039] If the target region corresponding to the target region code exists in the push region list of the pre-built business front-end system, then obtain the business category identifier contained in the business processing request;

[0040] If the business category corresponding to the business category identifier exists in the list of pushed business categories of the business front-end system, then the business processing information of the business to be processed is generated;

[0041] The business application information is pushed to the business service system; wherein, the target area corresponds to the first area level; the business front-end system and the business service system correspond to the second area level; the first area level is lower than the second area level.

[0042] In the aforementioned data push method, apparatus, computer equipment, storage medium, and computer program product, the business front-end system can receive a business processing request sent by a business client for a pending business, and obtain the target area code contained in the business processing request; if the target area corresponding to the target area code exists in the pre-built push area list of the business front-end system, then obtain the business category identifier contained in the business processing request; if the business category corresponding to the business category identifier exists in the push business category list of the business front-end system, then generate business processing information for the pending business; subsequently, the business processing information can be pushed to the business service system; wherein, the first area level of the target area is lower than the second area level of the corresponding business service system; the business front-end system belongs to the second area level. In the method provided in this application embodiment, a business front-end system belonging to the second region level is set up between the business service system of the first region level and the business service system of the second region level. All regions of the first region level belonging to the second region level can transmit data between the business front-end system and the business service system. In the process of pushing business case information of the first region level region to the business service system through the business front-end system, the target region and business category corresponding to the business case information can be identified to determine whether the business case information can be pushed. While ensuring the accuracy of data push, the timeliness of data push and business processing is improved. Attached Figure Description

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

[0044] Figure 1 An application environment diagram of a data push method provided in an embodiment of this application;

[0045] Figure 2 A flowchart illustrating a data push method provided in an embodiment of this application;

[0046] Figure 3 A schematic diagram illustrating a process for constructing a list of push service categories, provided as an embodiment of this application;

[0047] Figure 4 This application provides a schematic diagram of a process for generating business application information.

[0048] Figure 5 A flowchart illustrating another data push method provided in an embodiment of this application;

[0049] Figure 6 A structural block diagram of a data push device provided in an embodiment of this application;

[0050] Figure 7 This is an internal structural diagram of a computer device provided in an embodiment of this application. Detailed Implementation

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

[0052] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. The acquisition, transmission, storage, use, and processing of data in this application comply with the relevant provisions of national laws and regulations. In the embodiments of this application, certain software, components, models, and other existing solutions in the industry may be mentioned. These should be considered as exemplary, and their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or necessarily used such a solution.

[0053] The data push method provided in this application embodiment can be applied to, for example, Figure 1 The application environment shown may include at least one business client, a business front-end system, and a business service system. The at least one business client corresponds to a first-level region, while the business front-end system and business service system correspond to a second-level region. The first-level region is lower than the second-level region; it should be understood that regions at the first-level region are under the management scope of the second-level region. One second-level region can correspond to multiple first-level regions.

[0054] The business client allows applicants to register and log in to the business front-end system. Applicants can trigger a login request on the client, which will display a login interface where they can enter their username and password. The login method for the business front-end system can include, but is not limited to, applications, official accounts, mini-programs, and web pages; this application does not impose any restrictions. Upon successful login, applicants can trigger a business processing request for the pending service through the business processing interface on the client. The client will then send the request to the business front-end system's server.

[0055] The business front-end system receives a business processing request from a business client. It retrieves the target region code from the request and compares it with a pre-built list of push regions. If the target region exists in the list, it retrieves the business category identifier. Next, it compares this identifier with the list of push business categories. If the business category exists, it generates business processing information. The business service system then pushes this information to the business service system. The target region corresponds to a first region level, while the business front-end system and business service system correspond to a second region level. The first region level is lower than the second region level.

[0056] The business service system can process the information of the pending business, obtain the processing process information and processing result information associated with the business information, and transmit the processing process information and processing result information associated with the business information to the business front-end system, which will then store them in the system database.

[0057] The business clients can be, but are not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle systems, and projection devices. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted displays. Head-mounted displays can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. The system server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0058] In one exemplary embodiment, such as Figure 2 As shown, a data push method is provided. This embodiment illustrates the application of this method to a system server in a business front-end system. It is understood that this method can also be applied to terminals, and to systems including terminals and servers, and is implemented through interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0059] Step 202: Receive a business processing request sent by the business client for the business to be processed, and obtain the target area code contained in the business processing request.

[0060] In this application, the business client corresponds to a first-level region, while the business front-end system and business service system correspond to a second-level region. The first-level region is lower than the second-level region; therefore, it should be understood that regions at the first-level region fall under the management scope of the second-level region. One second-level region can correspond to multiple first-level regions. Each of these multiple first-level regions can have a corresponding region code. The first-level region where the business client is located can be identified as the target region. Business applicants can register and log in to the business front-end system on the business client. The business applicant can trigger a login request on the business client, which, in response, displays a login interface where the applicant can enter their username and password to log in. The login methods for the business front-end system can include, but are not limited to, applications, official accounts, mini-programs, and web pages; this application does not impose any restrictions on these methods. Upon successful login, the business applicant can trigger a business processing request for the pending business through the business processing interface of the business client. The business client, in response to this request, can send the request to the system server of the business front-end system. This service processing request can be used to request processing of a pending service. This request may include, but is not limited to, the basic information of the pending service, the target area code, the service category identifier, and the push time. Therefore, the system server of the front-end system can obtain the target area code corresponding to the pending service from the service processing request. This target area code indicates the region corresponding to the service processing request.

[0061] Step 204: If the target region corresponding to the target region code exists in the push region list of the pre-built business front-end system, then obtain the business category identifier contained in the business processing request.

[0062] The system database of this front-end system stores a pre-built list of push regions. This list can contain multiple push regions, and these multiple push regions must meet the following three conditions:

[0063] (1) The region level corresponding to the multiple push regions is the first region level; (2) The multiple push regions are within the associated scope of the business front-end system; (3) The multiple push regions have push permission enabled. Push permission means that the business application information of the pending business in the region is authorized to be pushed to the corresponding business service system through the business front-end system. When the target region code corresponding to the business processing request is obtained, the target region code can be compared with the region codes of multiple push regions in the push region list to determine whether the target region has push permission enabled. If the target region corresponding to the target region code exists in the push region list of the pre-built business front-end system, it indicates that the target region has push permission enabled. In this case, the business category identifier contained in the business processing request can be obtained. If the target region corresponding to the target region code does not exist in the push region list of the pre-built business front-end system, it indicates that the target region has not push permission enabled. Therefore, the business application information of the pending business cannot be generated through the business front-end system, and the business application information of the pending business in the target region cannot be pushed to the corresponding business service system.

[0064] Step 206: If the business category corresponding to the business category identifier exists in the list of pushed business categories in the business front-end system, then generate the business application information for the pending business.

[0065] If the target region corresponding to the target region code exists in the pre-built push region list of the business front-end system, it indicates that push permission is enabled for that target region. In this case, the business category identifier contained in the business processing request can be obtained. The system database of the business front-end system stores a pre-built list of push business categories. In one possible implementation, the list of push business categories includes at least one first-region level region, at least one regional business category corresponding to each first-region level region, and a business service category. The list of push business categories may also include the association relationships between various regional business categories and various business service categories. Based on this, the business category identifier contained in the business processing request can be compared with the regional business category identifier of the regional business category associated with the target region in the push business category list to determine whether data push and business processing can be performed for the business to be processed. If the business category corresponding to the business category identifier exists in the list of pushed business categories of the business front-end system, it indicates that the business to be processed belongs to the business category that the business front-end system can push. In this case, the business processing information for the business to be processed can be generated. If the business category corresponding to the business category identifier exists in the list of pushed business categories of the business front-end system, it indicates that the business to be processed does not belong to the business category that the business front-end system can push. In this case, the business processing information for the business to be processed cannot be generated through the business front-end system, and the business processing information for the business to be processed cannot be pushed to the corresponding business service system. Regarding the business processing information for the business to be processed generated by the business front-end system, the business processing information can include basic business information and business processing information, such as application acceptance information, application process information, application result information, application correction information, collection registration information, special procedure information, data reconciliation mechanism, and material catalog information. In one possible implementation, the list of pushed business categories of the business front-end system can also include historical processing information corresponding to each regional business category. This historical processing information may include, but is not limited to, regional business category identifiers, business processing association information, and processing time information. Based on this, the business front-end system generates business case information for pending business transactions, and can store this business case information in the list of pushed business categories.

[0066] Step 208: Push the business application information to the business service system.

[0067] In this process, the first region level of the target area is lower than the second region level corresponding to the business service system; the business front-end system belongs to the second region level. In this step, the business processing request for the pending business may include a task identifier, which indicates the task type of the pending business. The task identifier may include an immediate task identifier and a scheduled task identifier. The business front-end system can obtain the task identifier of the pending task from the business processing request. If the task identifier is an immediate task identifier, it indicates that the pending business is an immediate task. In the case of an immediate task, the business front-end system can immediately push the business processing information of the pending business to the business service system. If the task identifier is a scheduled task identifier, it indicates that the pending business is a scheduled task. In the case of a scheduled task, the business front-end system can obtain the push time of the pending business from the business processing request, retrieve the pre-stored business processing information of the pending business from the push business category list of the business front-end system according to the push time, and push the business processing information to the business service system according to the push time.

[0068] In this embodiment, the business front-end system can receive a business processing request sent by a business client for a pending business, and obtain the target area code contained in the business processing request; if the target area corresponding to the target area code exists in the pre-built push area list of the business front-end system, then obtain the business category identifier contained in the business processing request; if the business category corresponding to the business category identifier exists in the push business category list of the business front-end system, then generate business processing information for the pending business; then, the business processing information can be pushed to the business service system; wherein, the target area corresponds to a first area level; the business front-end system and the business service system correspond to a second area level; the first area level is lower than the second area level. In the method provided in this application embodiment, a business front-end system belonging to the second region level is set up between the business service system of the first region level and the business service system of the second region level. All regions of the first region level belonging to the second region level can transmit data between the business front-end system and the business service system. In the process of pushing business case information of the first region level region to the business service system through the business front-end system, the target region and business category corresponding to the business case information can be identified to determine whether the business case information can be pushed. While ensuring the accuracy of data push, the timeliness of data push and business processing is improved.

[0069] In one exemplary embodiment, this application embodiment further includes the following steps for illustrating the construction of the push area list, the steps specifically including:

[0070] Identify multiple regions corresponding to the business front-end system; these regions belong to the first region level; obtain push permission information for each region among the multiple regions; if the push permission information indicates that the corresponding region has enabled push permission, then add the region to the push region list; push permission indicates permission to push the business application information of the region's pending business to the business service system through the business front-end system.

[0071] The business front-end system and business service system correspond to the second regional level. Regions at the first regional level fall under the management scope of the second regional level. One second-region region can correspond to multiple first-region regions. Based on this, multiple regions corresponding to the business front-end system can be identified, and these multiple regions are multiple first-region level regions. Each of these multiple first-region level regions can be determined whether push notifications are enabled. The push notification information for each first-region level region indicates whether push notifications are enabled for that region. If the push notification information indicates that push notifications are enabled for the corresponding region, the region is added to the push region list; if the push notification information indicates that push notifications are not enabled for the corresponding region, the region cannot be added to the push region list. This push notification indicates permission to push the business processing information of pending business items in the region to the business service system through the business front-end system.

[0072] In the method of this embodiment, a push area list of the business front-end system can be pre-built. When a business processing request is received, it can be determined whether the data can be pushed according to the push area list, which improves the timeliness of data push.

[0073] In one exemplary embodiment, such as Figure 3 As shown, this application embodiment also includes the following steps to illustrate the construction of the push service category list, specifically steps 302 to 308. Wherein:

[0074] Step 302: Obtain the regional business category of the push area in the push area list.

[0075] Different push regions can have different regional business categories or the same regional business category, and each push region can correspond to at least one regional business category.

[0076] Step 304: Obtain the business service category corresponding to the business front-end system.

[0077] The business service category can be either the business type handled by the corresponding business service system or the business service category of the business service corresponding to the business front-end system.

[0078] Step 306: Determine the relationship between regional business categories and business service categories.

[0079] Step 308: Based on the association relationships, construct a list of push service categories for the business front-end system.

[0080] There is a correspondence between the regional business categories and the business service categories. Based on this, the correspondence between the regional business categories and the business service categories can be determined. In other words, when constructing the list of push business categories, it is necessary to determine the correspondence between the push region, the regional business category, the business service system, and the business service category. This relationship can be the correspondence shown here.

[0081] In the method of this embodiment, a list of push business categories of the business front-end system can be pre-built, which makes it easier to determine the business category of the business to be processed based on the list of push business categories, and to determine the business service system of the business to be processed, thereby improving the timeliness of data push.

[0082] In one exemplary embodiment, such as Figure 4 As shown, step 206 may include steps 402 to 406. Wherein:

[0083] Step 402: Based on the business processing request, obtain the basic business information corresponding to the business processing request.

[0084] Step 404: Generate the business processing information corresponding to the business processing request.

[0085] Step 406: Generate the business processing information corresponding to the business processing request based on the basic business information and business processing information.

[0086] Step 408: Store the business application information in the list of pushed business categories, and mark the stored business application information as unpushable information.

[0087] The information provided for this business application can include basic business information and processing information, such as application acceptance information, processing process information, processing result information, application correction information, collection registration information, special procedure information, data reconciliation mechanism, and material catalog information. The basic business information may include, but is not limited to, the regional code, business category identifier, and business material information for the application to be processed. The processing information can include the business process information and material information generated during the processing of the application to be processed, such as application acceptance information, processing process information, processing result information, application correction information, collection registration information, special procedure information, data reconciliation mechanism, application number, application batch, and processing time at each stage. The business category list pushed by the front-end system can also include historical processing information corresponding to each regional business category, which may include, but is not limited to, regional business category identifier, business processing association information, and processing time information. Based on this, the business front-end system generates business case information for pending business, which can be stored in the list of pushed business categories and marked as unpushable information. This unpushable information mark can be used to distinguish the business case information from historical processing information.

[0088] In the method of this embodiment, the business processing information of the business to be processed can be generated by the business front-end system, and the business processing information can be directly pushed to the corresponding business service system, thereby improving the timeliness of business processing in the business service system.

[0089] In one exemplary embodiment, step 208 may include:

[0090] Retrieve the push time contained in the business processing request; the push time is the time when the business processing information is pushed; according to the push time, retrieve the business tag information marked as not pushed information corresponding to the business processing request from the list of pushed business categories; according to the push time, push the business processing information to the business service system.

[0091] The service request for a pending service may include a task identifier, which indicates the task type of the pending service. The task identifier can include immediate task identifiers and scheduled task identifiers. The front-end system can obtain the task identifier from the service request. If the task identifier is an immediate task identifier, it indicates that the pending service is an immediate task. In the case of an immediate task, the front-end system, after determining the corresponding service system, can immediately push the service information of the pending service to that service system. If the task identifier is a scheduled task identifier, it indicates that the pending service is a scheduled task. In the case of a scheduled task, the front-end system can obtain the push time of the pending service from the service request, retrieve the pre-stored service information of the pending service from the push service category list of the front-end system according to the push time, and push the service information to the service system according to the push time.

[0092] In the method of this embodiment, real-time and timed push of business case information can be realized through the business front-end system, which improves the diversity and comprehensiveness of data push. Business case information can be directly stored in the push business category list, and the business case information in the push business category list can be directly retrieved according to the push time, which improves the timeliness of data push.

[0093] In one exemplary embodiment, this application embodiment further includes the following steps to illustrate the situation where the push of business application information fails. The steps may specifically include:

[0094] If the push result for the business application information is a push failure, a push failure message is displayed through the business client; a re-push request is received from the business client based on the push failure message; based on the re-push request, the business application information is retrieved again from the list of push business categories; and the business application information is pushed to the business service system again.

[0095] The failure to push the application information can be interpreted as the service system not receiving the application information for the pending application from the front-end system. Upon receiving the push failure notification from the service system, the front-end system can send this notification to the client application corresponding to the pending application and display the notification. The applicant can trigger a re-push request for the pending application on their client application. The client application will then send this re-push request to the front-end system's server. Upon receiving the re-push request, the server will retrieve the application category identifier from the request. Based on this identifier, the server can then retrieve the corresponding application information from the application category list and push it back to the service system.

[0096] In the method of this embodiment, the business front-end system has a push function. In the event that the push of business application information fails, a push failure prompt can be displayed and a push can be performed, thereby improving the accuracy of data push.

[0097] In one exemplary embodiment, this application embodiment further includes the following steps to illustrate the processing and querying of business application information, the steps specifically including:

[0098] Based on the processing information query request sent by the business client, obtain the business query information for the business application; obtain the processing flow information for the business application based on the business query information, and display the processing flow information for the business application through the business client.

[0099] In the process of processing business application information, the business service system can transmit the processing procedure information and application material information of the pending business to the business front-end system. The business front-end system can then store the received processing procedure information and application material information of the pending business in the list of pushed business categories. The transmission of the processing procedure information and required materials information for the pending business can adopt various transmission methods, and this application does not limit this. The following uses the proactive push from the business service system and the passive query from the business front-end system as examples. In one possible implementation, the business service system can push the processing procedure information and required materials information of the pending business to the business front-end system in real time. The business front-end system can store the received processing procedure information and required materials information of the pending business in the push business category list. The business front-end system can have a query function. The applicant can perform a query operation on the query page of the business client, triggering a processing information query request for the business case information. The business client responds to the processing information query request and sends a processing information query request to the business front-end system. The business front-end system obtains the business query information for the business case information based on the processing information query request sent by the business client; based on the business query information, it retrieves the processing procedure information and required materials information of the pending business from the push business category list, and displays the processing procedure information and required materials information of the business case information through the business client. In another possible implementation, the front-end system obtains business query information for the business application based on the processing information query request sent by the business client. Based on the business query information, it sends a query request to the business service system. Upon receiving the query request from the front-end system, the business service system obtains the processing flow information and required materials information for the application to be processed, and then sends this information back to the front-end system. The front-end system can then display the processing flow information and required materials information for the business application through the business client.

[0100] In the method of this embodiment, the business pre-processing system can have a query function. The business applicant can use the query function of the business pre-processing system to obtain the processing process information and the information of the materials required for the business application, thereby improving the convenience of business processing.

[0101] In another exemplary embodiment, such as Figure 5 As shown, a data push method is provided, which may include steps 502 to 528. Wherein:

[0102] This exemplary embodiment includes two parts. The first part includes constructing a list of push service categories, including steps 502 to 506. The second part includes data push between the service front-end system and the service system, including steps 506 to 528. Wherein:

[0103] Step 502: The business front-end system obtains the regional business category of the corresponding push area.

[0104] Step 504: The business front-end system obtains the business service category of the corresponding business service system.

[0105] Step 506: The business front-end system determines the relationship between regional business categories and business service categories, and constructs a list of push business categories for the business front-end system based on the relationship.

[0106] Step 508: The business front-end system receives a business processing request sent by the business client for the business to be processed, and obtains the target area code contained in the business processing request.

[0107] Step 510: Determine whether push permission is enabled in the target region corresponding to the target region code.

[0108] If push notifications are enabled in the target region, proceed to step 512; if push notifications are not enabled in the target region, proceed to step 514.

[0109] Step 512: The business front-end system obtains the business category identifier contained in the business processing request.

[0110] Step 514: The business front-end system returns a request failure message and the reason for failure to the business processing request and pushes it to the business client.

[0111] Step 516: Determine whether the service category identifier exists in the list of push service categories.

[0112] If the service category identifier exists in the push service category list, proceed to step 518; if the service category identifier does not exist in the push service category list, proceed to step 520.

[0113] Step 518: The business front-end system generates business case information for the business to be processed and stores the business case information in the list of the pushed business categories.

[0114] Step 520: The business front-end system returns a request failure message and the reason for failure to the business processing request and pushes it to the business client.

[0115] Step 522: Obtain the push time contained in the business processing request.

[0116] Step 524: Based on the push time, retrieve the business processing information corresponding to the business processing request from the list of push business categories.

[0117] Step 526: Push the business processing information to the business service system.

[0118] In this embodiment, the business front-end system can receive a business processing request sent by a business client for a pending business, and obtain the target area code contained in the business processing request; if the target area corresponding to the target area code exists in the pre-built push area list of the business front-end system, then obtain the business category identifier contained in the business processing request; if the business category corresponding to the business category identifier exists in the push business category list of the business front-end system, then generate business processing information for the pending business; then, the business processing information can be pushed to the business service system; wherein, the target area corresponds to a first area level; the business front-end system and the business service system correspond to a second area level; the first area level is lower than the second area level. In the method provided in this application embodiment, a business front-end system belonging to the second region level is set up between the business service system of the first region level and the business service system of the second region level. All regions of the first region level belonging to the second region level can transmit data between the business front-end system and the business service system. In the process of pushing business case information of the first region level region to the business service system through the business front-end system, the target region and business category corresponding to the business case information can be identified to determine whether the business case information can be pushed. While ensuring the accuracy of data push, the timeliness of data push and business processing is improved.

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

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

[0121] In one embodiment, such as Figure 6 As shown, a data push device is provided, including: an information acquisition module 602, a first judgment module 604, a second judgment module 606, and a push module 608, wherein:

[0122] Information acquisition module 602 is used to receive a business processing request sent by the information receiving business client for a business to be processed, and to acquire the target area code contained in the business processing request;

[0123] The first judgment module 604 is used to obtain the business category identifier contained in the business processing request if the target area corresponding to the target area code exists in the push area list of the pre-built business front-end system.

[0124] The second judgment module 606 is used to generate the business processing information of the pending business if the business category corresponding to the business category identifier exists in the push business category list of the business front-end system.

[0125] The push module 608 is used to push the business application information to the business service system; wherein, the target area corresponds to the first area level; the business front-end system and the business service system correspond to the second area level; the first area level is lower than the second area level.

[0126] In one embodiment, the information acquisition module is further configured to: determine multiple regions corresponding to the business front-end system; the multiple regions belong to the first region level; acquire push permission information for each of the multiple regions; if the push permission information indicates that the corresponding region has enabled push permission, then add the region to the push region list; the push permission indicates permission to push the business application information of the pending business in the region to the business service system through the business front-end system.

[0127] In one embodiment, the information acquisition module is further configured to: acquire the regional business category of the push area in the push area list; acquire the business service category corresponding to the business front-end system; determine the association between the regional business category and the business service category; and construct the push business category list of the business front-end system based on the association.

[0128] In one embodiment, the second determining module is further configured to: obtain basic business information corresponding to the business processing request based on the business processing request; generate business processing information corresponding to the business processing request; generate business case information corresponding to the business processing request based on the basic business information and the business processing information; store the business case information in the push business category list, and mark the stored business case information as unpush information.

[0129] In one embodiment, the push module is further configured to: obtain the push time contained in the business processing request; the push time is the push time for the business application information; according to the push time, obtain the business tag information marked as the non-pushed information corresponding to the business processing request from the push business category list; and push the business application information to the business service system according to the push time.

[0130] In one embodiment, the push module is further configured to: display a push failure prompt through the business client if the push result of the business application information is a push failure; receive a re-push request sent by the business client based on the push failure prompt; retrieve the business application information again from the push business category list based on the re-push request; and execute the step of pushing the business application information to the business service system.

[0131] In one embodiment, the information acquisition module is further configured to: acquire business query information for the business application information based on the processing information query request sent by the business client; acquire the processing flow information of the business application information based on the business query information; and display the processing flow information of the business application information through the business client.

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

[0133] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 7As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores data related to data push. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a data push method.

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

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

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

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

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

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

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

Claims

1. A data push method, characterized in that, Applied to a business front-end system, the method includes: Multiple regions corresponding to the business front-end system are identified; these multiple regions belong to the first region level. Obtain push permission information for each of the multiple regions; the push permission information for each of the multiple regions is determined based on whether push permission is enabled in each of the multiple regions. If the push permission information indicates that the corresponding region has enabled push permission, then the region is added to the push region list; the push permission indicates that the business processing information of the pending business in the region is authorized to be pushed to the business service system through the business front-end system. Obtain the regional service category of the push regions in the list of push regions; Obtain the business service category corresponding to the business front-end system; Determine the relationship between the regional business categories and the business service categories; Based on the aforementioned relationships, a list of push service categories for the business front-end system is constructed; The system receives a service processing request from a service client for a pending service and obtains the target region code contained in the service processing request; the target region code is determined based on the region where the service client is located. If the target region corresponding to the target region code exists in the push region list of the business front-end system, then obtain the business category identifier contained in the business processing request; If the business category corresponding to the business category identifier exists in the list of pushed business categories of the business front-end system, then the business processing information of the business to be processed is generated; The business application information is pushed to the business service system; wherein, the target area corresponds to the first area level; the business front-end system and the business service system correspond to the second area level; the first area level is lower than the second area level.

2. The method according to claim 1, characterized in that, The process of generating the application information for the pending business includes: Based on the business processing request, obtain the basic business information corresponding to the business processing request; Generate the business processing information corresponding to the business processing request; Based on the basic business information and the business processing information, generate the business application information corresponding to the business processing request; The business application information is stored in the list of pushed business categories, and the stored business application information is marked as not pushed information.

3. The method according to claim 2, characterized in that, The step of pushing the business application information to the business service system includes: Obtain the push time contained in the business processing request; the push time is the push time for the business processing information; According to the push time, retrieve the service application information marked as "not pushed information" corresponding to the service processing request from the list of push service categories; According to the push time, the business application information is pushed to the business service system.

4. The method according to claim 3, characterized in that, After pushing the business application information to the business service system, the process further includes: If the push result of the business application information is a push failure, a push failure prompt will be displayed through the business client; Receive the push request sent by the service client based on the push failure message. Based on the re-push request, the service application information is retrieved again from the list of push service categories. Perform the step of pushing the business application information to the business service system.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Based on the processing information query request sent by the business client for the business application information, obtain the business query information for the business application information; The processing flow information of the business application is obtained based on the business query information, and the processing flow information of the business application is displayed through the business client.

6. A data push device, characterized in that, The device, applied to a business front-end system, includes: The information acquisition module is used to receive a business processing request sent by the business client for a business to be processed, and to obtain the target area code contained in the business processing request; The first judgment module is used to obtain the business category identifier contained in the business processing request if the target area corresponding to the target area code exists in the push area list of the pre-built business front-end system. The second judgment module is used to generate the business processing information of the pending business if the business category corresponding to the business category identifier exists in the push business category list of the business front-end system. A business service system push module is used to push the business application information to the business service system; wherein, the target area corresponds to a first area level; the business front-end system and the business service system correspond to a second area level; the first area level is lower than the second area level; The information acquisition module is also used for: Multiple regions corresponding to the business front-end system are identified; these multiple regions belong to the first region level. Obtain push permission information for each of the multiple regions; the push permission information for each of the multiple regions is determined based on whether push permission is enabled in each of the multiple regions. If the push permission information indicates that push permission is enabled in the corresponding region, then the region is added to the push region list; the push permission indicates that the business processing information of the pending business in the region is authorized to be pushed to the business service system through the business front-end system. Obtain the regional service category of the push regions in the list of push regions; Obtain the business service category corresponding to the business front-end system; Determine the relationship between the regional business category and the business service category.

7. The apparatus according to claim 6, characterized in that, The second judgment module is also used for: Based on the business processing request, obtain the basic business information corresponding to the business processing request; Generate the business processing information corresponding to the business processing request; Based on the basic business information and the business processing information, generate the business application information corresponding to the business processing request; The business application information is stored in the list of pushed business categories, and the stored business application information is marked as not pushed information.

8. The apparatus according to claim 7, characterized in that, The push module is also used for: Obtain the push time contained in the business processing request; the push time is the push time for the business processing information; According to the push time, retrieve the service application information marked as "not pushed information" corresponding to the service processing request from the list of push service categories; According to the push time, the business application information is pushed to the business service system.

9. The apparatus according to claim 8, characterized in that, The push module is also used for: If the push result of the business application information is a push failure, a push failure prompt will be displayed through the business client; Receive the push request sent by the service client based on the push failure message; Based on the re-push request, the service application information is retrieved again from the list of push service categories. Perform the step of pushing the business application information to the business service system.

10. The apparatus according to any one of claims 6-9, characterized in that, The information acquisition module is also used for: Based on the processing information query request sent by the business client for the business application information, obtain the business query information for the business application information; The processing flow information of the business application is obtained based on the business query information, and the processing flow information of the business application is displayed through the business client.

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

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

13. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-5.

Images