A service processing method and device, electronic equipment and computer readable medium

Abstract

The application discloses a business processing method and device, electronic equipment and computer readable medium, relates to the technical field of big data data analysis, and the method comprises the steps that a business processing request is received, corresponding business data and a service identifier are acquired, and an evaluation terminal type is determined according to the service identifier; in response to the evaluation terminal type being a non-direct connection terminal, a timing push task is generated based on the business data and the evaluation terminal type; the business data is pushed to the evaluation terminal corresponding to the evaluation terminal type based on the timing push task, so as to generate a case number; and based on the case number, a request message is generated, so that the evaluation terminal executes corresponding business evaluation based on the request message, and obtains a business evaluation result. The combination degree of evaluation data and business is enhanced, and the expansion difficulty and workload are reduced.

Description

Technical Field

[0001] This application relates to the field of big data data analysis technology, and in particular to a business processing method, apparatus, electronic device and computer-readable medium. Background Technology

[0002] The "good and bad reviews" system was built using a provincially unified approach, with local cities and departments connecting their pages and interfaces according to the provincial platform standards. However, there are significant differences in government services across regions, with a wide variety of evaluation terminals and channels. Existing evaluation schemes offer limited channels, making it difficult to achieve a unified access solution given the differences in evaluation devices.

[0003] In the process of developing this application, the inventors discovered at least the following problems in the prior art:

[0004] The evaluation terminals and channels are diverse and vary greatly from place to place, making integration difficult. The evaluation data has a low degree of integration with business operations, making it difficult to support subsequent analysis and statistics to provide feedback for business optimization and updates. Summary of the Invention

[0005] In view of this, embodiments of this application provide a business processing method, apparatus, electronic device, and computer-readable medium, which can solve the problems of existing evaluation terminal equipment and evaluation channels being diverse, having large regional differences, being difficult to connect, having low integration of evaluation data with business, and being unable to support subsequent analysis and statistics to feed back into business optimization and updates.

[0006] To achieve the above objectives, according to one aspect of an embodiment of this application, a business processing method is provided, comprising:

[0007] Receive business processing requests, obtain corresponding business data and service identifiers, and then determine the evaluation terminal type based on the service identifiers;

[0008] In response to the evaluation terminal type being a non-directly connected terminal, a scheduled push task is generated based on business data and the evaluation terminal type.

[0009] Business data is pushed to the evaluation terminal corresponding to the evaluation terminal type based on the scheduled push task, so that the evaluation terminal can generate a case number based on the business data.

[0010] Based on the case number, a request message is generated so that the evaluation terminal can perform the corresponding business evaluation based on the request message and obtain the business evaluation result.

[0011] Optionally, before generating the scheduled push task based on business data and evaluation terminal type, the business processing method further includes:

[0012] Obtain the transaction identifier corresponding to the business processing request;

[0013] In response to the fact that the transaction identifier is not registered to the factory class, the corresponding evaluation service program is invoked according to the evaluation terminal type to extract the business evaluation elements from the business data.

[0014] Optionally, the business processing method also includes:

[0015] In response to the evaluation terminal type being a direct connection terminal, the user is redirected to a third-party evaluation page to generate a business evaluation result based on the business evaluation elements.

[0016] Establish and store the mapping relationship between business data and business evaluation results.

[0017] Optionally, business data is pushed to the evaluation terminal corresponding to the evaluation terminal type based on a scheduled push task, including:

[0018] Determine the push mode identifier corresponding to the scheduled push task, and then push the business evaluation elements in the business data to the evaluation terminal corresponding to the evaluation terminal type based on the push mode corresponding to the push mode identifier.

[0019] Optionally, before obtaining the corresponding business data, the method further includes:

[0020] Obtain the evaluation identifier carried in the business processing request. In response to the evaluation identifier being non-empty, execute the process of obtaining business data and service identifier.

[0021] Optionally, the business processing method also includes:

[0022] After obtaining the corresponding business data, a separate thread is started to register and process the business data.

[0023] Optionally, obtain the corresponding business data, including:

[0024] Obtain the evaluation data requirement information carried in the business processing request, and then inherit the corresponding base class based on the evaluation data requirement information to obtain the business data corresponding to the evaluation data requirement information.

[0025] Optionally, the business processing method also includes:

[0026] In response to the detection of an anomaly in the business evaluation results, the appeal review mechanism is invoked to review the business evaluation results.

[0027] In addition, this application also provides a business processing apparatus, including:

[0028] The receiving unit is configured to receive service processing requests, obtain corresponding service data and service identifiers, and then determine the evaluation terminal type based on the service identifiers.

[0029] The scheduled push task generation unit is configured to generate scheduled push tasks based on business data and the evaluation terminal type in response to the evaluation terminal type being a non-directly connected terminal.

[0030] The case number generation unit is configured to push business data to the evaluation terminal corresponding to the evaluation terminal type based on a timed push task, so that the evaluation terminal can generate a case number based on the business data.

[0031] The business processing unit is configured to generate a request message based on the case number, so that the evaluation terminal can perform the corresponding business evaluation based on the request message and obtain the business evaluation result.

[0032] Optionally, the service processing apparatus further includes an extraction unit configured to:

[0033] Obtain the transaction identifier corresponding to the business processing request;

[0034] In response to the fact that the transaction identifier is not registered to the factory class, the corresponding evaluation service program is invoked according to the evaluation terminal type to extract the business evaluation elements from the business data.

[0035] Optionally, the apparatus further includes a mapping relationship establishment unit, configured to:

[0036] In response to the evaluation terminal type being a direct connection terminal, the user is redirected to a third-party evaluation page to generate a business evaluation result based on the business evaluation elements.

[0037] Establish and store the mapping relationship between business data and business evaluation results.

[0038] Optionally, the case number generation unit is further configured to:

[0039] Determine the push mode identifier corresponding to the scheduled push task, and then push the business evaluation elements in the business data to the evaluation terminal corresponding to the evaluation terminal type based on the push mode corresponding to the push mode identifier.

[0040] Optionally, the receiving unit is further configured to:

[0041] Obtain the evaluation identifier carried in the business processing request. In response to the evaluation identifier being non-empty, execute the process of obtaining business data and service identifier.

[0042] Optionally, the device also includes a registration unit configured to:

[0043] After obtaining the corresponding business data, a separate thread is started to register and process the business data.

[0044] Optionally, the receiving unit is further configured to:

[0045] Obtain the evaluation data requirement information carried in the business processing request, and then inherit the corresponding base class based on the evaluation data requirement information to obtain the business data corresponding to the evaluation data requirement information.

[0046] Optionally, the business processing apparatus further includes a review unit, configured to:

[0047] In response to the detection of an anomaly in the business evaluation results, the appeal review mechanism is invoked to review the business evaluation results.

[0048] In addition, this application also provides a business processing electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, enable the one or more processors to implement the business processing method described above.

[0049] In addition, this application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the business processing method described above.

[0050] To achieve the above objectives, according to another aspect of the embodiments of this application, a computer program product is provided.

[0051] A computer program product according to an embodiment of this application includes a computer program that, when executed by a processor, implements the business processing method provided in the embodiment of this application.

[0052] One embodiment of the above invention has the following advantages or beneficial effects: This application receives a business processing request, obtains the corresponding business data and service identifier, and then determines the evaluation terminal type based on the service identifier; in response to the evaluation terminal type being a non-directly connected terminal, it generates a scheduled push task based on the business data and the evaluation terminal type; based on the scheduled push task, it pushes business data to the evaluation terminal corresponding to the evaluation terminal type, so that the evaluation terminal generates a case number based on the business data; based on the case number, it generates a request message, so that the evaluation terminal performs the corresponding business evaluation based on the request message and obtains the business evaluation result. The corresponding evaluation service program is called according to the evaluation terminal type to extract business data; when the evaluation terminal type is a non-directly connected terminal, the evaluation terminal generates a case number based on the business data, and then generates request information, so that the evaluation terminal performs business evaluation based on the generated request information. This enables compatibility with the evaluation needs of multiple transactions and multiple centers, reduces local differences and integration difficulties, enhances the integration of evaluation data and business, reduces expansion difficulty and workload, strongly supports subsequent analysis and statistics, and feeds back into business optimization and updates.

[0053] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0054] The accompanying drawings are provided to better understand this application and do not constitute an undue limitation thereof. Wherein:

[0055] Figure 1 This is a schematic diagram of the main flow of the business processing method according to the first embodiment of this application;

[0056] Figure 2 This is a schematic diagram of the main flow of the business processing method according to the second embodiment of this application;

[0057] Figure 3 This is a schematic diagram illustrating an application scenario of the business processing method according to the third embodiment of this application;

[0058] Figure 4 This is a schematic diagram of the direct connection terminal "good and bad review" system docking according to the business processing method of the fourth embodiment of this application;

[0059] Figure 5 This is a schematic diagram of the non-directly connected terminal "good / bad review" system interface according to the business processing method of the fifth embodiment of this application;

[0060] Figure 6 This is a schematic diagram of the main units of a service processing apparatus according to an embodiment of this application;

[0061] Figure 7 This is an exemplary system architecture diagram to which embodiments of this application can be applied;

[0062] Figure 8 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers in the embodiments of this application. Detailed Implementation

[0063] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description. The acquisition, storage, use, and processing of data in the technical solutions of this application all comply with relevant national laws and regulations.

[0064] Figure 1 This is a schematic diagram of the main flow of the business processing method according to the first embodiment of this application, as shown below. Figure 1 As shown, the business processing methods include:

[0065] Step S101: Receive a service processing request, obtain the corresponding service data and service identifier, and then determine the evaluation terminal type based on the service identifier.

[0066] In this embodiment, the entity executing the business processing method (e.g., a server) can receive business processing requests via wired or wireless connections. Business processing requests may, for example, be requests to evaluate services (e.g., housing provident fund services, catering services, etc.). Evaluation entities: Entities evaluating government services include natural persons, legal persons, and other organizations. Entities evaluating housing provident fund services include employees contributing to the housing provident fund and their employers' representatives. Evaluation objects: Governments at all levels and their departments with corresponding qualifications and exercising corresponding government service functions, departmental management agencies, units and organizations legally undertaking administrative management functions, departments listed in the Party and mass work organization sequence but legally undertaking administrative functions, and enterprises with public service functions. For the housing provident fund system, the evaluation object is the operator handling the business.

[0067] Specifically, before obtaining the corresponding business data, the method also includes: obtaining the evaluation identifier carried in the business processing request, and in response to the evaluation identifier being non-empty, executing the process of obtaining business data and service identifier.

[0068] After entering and submitting a business processing request, the executing entity can determine whether the corresponding business requires evaluation. Specifically, it can obtain the evaluation identifier carried in the business processing request. An empty evaluation identifier means no evaluation is needed, while a non-empty evaluation identifier means evaluation is required. If the executing entity determines that the evaluation identifier is non-empty, it indicates that evaluation is required, and then proceeds to obtain the business data and service identifier corresponding to the business processing request. Business data may include account opening transaction data, deposit transaction data, withdrawal transaction data, loan acceptance data, loan change data, and early repayment data, etc. The service identifier is used to identify whether the evaluation terminal is a directly connected terminal or a non-directly connected terminal.

[0069] As another implementation method, the evaluation flags include, but are not limited to, 0, 1, Y, and N. For example, 0 can represent no evaluation, 1 can represent evaluation, Y can represent evaluation, and N can represent no evaluation.

[0070] Specifically, the business processing method also includes: after obtaining the corresponding business data, starting an independent thread to register and process the business data.

[0071] After collecting the business data for evaluation, the executing entity can start a new independent thread to register the business data information to be evaluated, so as to avoid affecting the transaction entity and facilitate the subsequent collection and feedback of the business data for evaluation.

[0072] Specifically, obtaining the corresponding business data includes: obtaining the evaluation data requirement information carried in the business processing request, and then inheriting the corresponding base class based on the evaluation data requirement information to obtain the business data corresponding to the evaluation data requirement information.

[0073] For example, the factory class specifically creates a factory to generate objects of an implementation class based on given information. The execution entity can establish a factory class model to obtain general, basic business data, which can be automatically intercepted by the base class of the factory class. Each business module of the execution entity can choose to inherit from the base class in the factory class to obtain different business data based on its evaluation data requirements.

[0074] Step S102: In response to the evaluation terminal type being a non-directly connected terminal, a scheduled push task is generated based on the business data and the evaluation terminal type.

[0075] Non-directly connected terminals are those whose transmission channels are not directly connected. When the executing entity determines that the evaluation terminal type is a non-directly connected terminal, that is, when the transmission channel between the evaluation terminal and other terminals is not directly connected, the executing entity can assemble business data and evaluation terminal type information to generate a scheduled push task.

[0076] Step S103: Based on the scheduled push task, push business data to the evaluation terminal corresponding to the evaluation terminal type, so that the evaluation terminal can generate a case number based on the business data.

[0077] After generating a scheduled task, the executing entity can periodically poll the background service of the evaluation terminal. For example, it can poll the background service every 3 seconds (this embodiment does not specifically limit the polling interval) to determine whether the background service of the evaluation terminal has started executing business processing. When the executing entity determines that the background service of the evaluation terminal has started executing the business processing request, it can push business data to the background service of the evaluation terminal so that the background service of the evaluation terminal can generate a case number based on the business data. The case number is a number for the processed item, used to represent the order in which the corresponding business is processed at the corresponding evaluation terminal. For example, one case number corresponds to one business processing task of the evaluation terminal. The evaluation terminal performs business processing by executing business processing tasks.

[0078] Specifically, the process of pushing business data to evaluation terminals corresponding to the evaluation terminal type based on scheduled push tasks includes: determining the push mode identifier corresponding to the scheduled push task, and then pushing business evaluation elements from the business data to the evaluation terminals corresponding to the evaluation terminal type based on the push mode corresponding to the push mode identifier. Specifically, the business evaluation elements in the business data include, but are not limited to, business processing time, communication records between the operator and the user, negative review records, complaint records, business processing failure rate, and business processing success rate. The push mode identifier is used to characterize the method of pushing business data, such as air delivery or encrypted delivery. Encrypted delivery further includes encryption using method A, encryption using method B, ..., or encryption using method N before delivery.

[0079] Step S104: Based on the case number, generate a request message so that the evaluation terminal can perform the corresponding business evaluation based on the request message and obtain the business evaluation result.

[0080] The executing entity can call the saveComment method of the factory class to determine whether an HTTP request needs to be generated based on the case number. If so, an independent thread (in parallel with the main thread) is started to call the triggerComment method of the factory class to generate an HTTP request message and send it to the evaluation terminal, so that the evaluation terminal can perform the corresponding business evaluation based on the HTTP request message and obtain the business evaluation result.

[0081] Specifically, the business processing method also includes: in response to detecting an anomaly in the business evaluation result, invoking the appeal review mechanism to conduct an appeal review of the business evaluation result.

[0082] By establishing an appeal review mechanism, we can eliminate erroneous reviews and "malicious" negative reviews.

[0083] This embodiment receives business processing requests, obtains corresponding business data and service identifiers, and then determines the evaluation terminal type based on the service identifier. In response to a non-directly connected terminal, a scheduled push task is generated based on the business data and the evaluation terminal type. Business data is pushed to the evaluation terminal corresponding to the evaluation terminal type based on the scheduled push task, enabling the evaluation terminal to generate a case number based on the business data. A request message is generated based on the case number, allowing the evaluation terminal to perform the corresponding business evaluation and obtain the business evaluation result. The corresponding evaluation service program is invoked according to the evaluation terminal type to extract business data. When the evaluation terminal type is a non-directly connected terminal, the evaluation terminal generates a case number based on the business data, and then generates request information, enabling the evaluation terminal to perform business evaluation based on the generated request information. This approach can accommodate evaluation needs across multiple transactions and centers, reduce local differences and integration difficulties, enhance the integration of evaluation data and business, reduce expansion difficulty and workload, strongly support subsequent analysis and statistics, and provide feedback for business optimization and updates.

[0084] Figure 2 This is a schematic diagram of the main flow of the business processing method according to the second embodiment of this application, as follows: Figure 2 As shown, the business processing methods include:

[0085] Step S201: Receive a service processing request, obtain the corresponding service data and service identifier, and then determine the evaluation terminal type based on the service identifier.

[0086] Step S202: Obtain the transaction identifier corresponding to the business processing request.

[0087] In step S203, in response to the transaction identifier not being registered to the factory class, the corresponding evaluation service program is invoked according to the evaluation terminal type to extract the business evaluation elements from the business data.

[0088] Specifically, before generating the scheduled push task based on business data and evaluation terminal type, the business processing method also includes: obtaining the transaction identifier corresponding to the business processing request; and, in response to the transaction identifier not being registered to the factory class, calling the corresponding evaluation service program according to the evaluation terminal type to extract business evaluation elements from the business data. The transaction identifier is, for example, the transaction number.

[0089] When the executing entity determines that there is no transaction corresponding to the registered and acquired transaction identifier in the established factory class model, it can call the corresponding evaluation service program according to the evaluation terminal type. For example, it can call the corresponding evaluation service program in the background according to the evaluation terminal type corresponding to the service identifier ServiceId to extract the business evaluation elements in the business data.

[0090] Specifically, the business evaluation elements in the business data include, but are not limited to, business processing time, communication records between the operator and the user, negative review records, complaint records, business processing failure rate, and business processing success rate.

[0091] Step S204: In response to the evaluation terminal type being a non-directly connected terminal, a scheduled push task is generated based on the business evaluation elements and the evaluation terminal type.

[0092] Step S205: Based on the scheduled push task, push the business evaluation elements to the evaluation terminal corresponding to the evaluation terminal type, so that the evaluation terminal can generate a case number based on the business evaluation elements.

[0093] Step S206: Based on the case number, generate a request message so that the evaluation terminal can perform the corresponding business evaluation based on the request message and obtain the business evaluation result.

[0094] In step S207, in response to the evaluation terminal type being a direct connection terminal, the user is redirected to a third-party evaluation page to generate a business evaluation result based on the business evaluation elements.

[0095] A direct-connect terminal refers to a terminal whose transmission channel is directly connected to another terminal. Taking the type of business processing as evaluation business processing as an example, when the executing entity determines that the type of evaluation terminal is a direct-connect terminal, it can return the evaluation business URL and redirect to a third-party evaluation page or a system virtual evaluation business URL to complete the evaluation terminal mapping, actively trigger the evaluation system, and generate business evaluation results based on business evaluation elements.

[0096] Step S208: Establish and store the mapping relationship between business data and business evaluation results.

[0097] The implementing entity can establish a mapping relationship between evaluation business data and business evaluation results to facilitate further tracking, analysis and application of the evaluation data and promote business improvement.

[0098] Figure 3 This is a schematic diagram illustrating an application scenario of the business processing method according to the third embodiment of this application. The business processing method of this embodiment is applied to a scenario where users evaluate services. Figure 3 As shown, the overall backend logic of the business processing method in this application is as follows:

[0099] The first stage is initialization: When the executing entity detects that the application responsible for business processing has started, it can initialize the processors for each transaction. Then, the executing entity can register the processors for each transaction with the factory, ultimately completing the initialization of the Map member variables of the factory class. A Map is a special data structure, an unordered collection of element pairs, where one element in a pair is the key and the corresponding element is the value. For example, the key in the Map is ServiceId, and the value is the transaction processor. Then, the executing entity can obtain parameters (or configuration files), which may include: 1) the target URL of the HTTP request; 2) whether an HTTP request needs to be sent.

[0100] After the initialization phase is complete, the transaction phase begins. In the transaction phase: First, the execution entity receives the business submitted at the counter, enters the CommentHandler, and defines temporary variables to store various information items required for the evaluation processing logic. Then, it checks whether the factory class has registered a transaction corresponding to the counter submission. If so, it locates the corresponding transaction handler, calls the service's preInvokeService method before invoking it, extracts the business evaluation elements from the transaction input information, and then executes the process of calling the corresponding backend service (UCC) based on the ServiceId. If the factory class does not register a transaction corresponding to the business submitted at the counter, it directly executes the process of calling the corresponding backend service (UCC) based on the ServiceId. After returning the transaction, it re-enters the CommentHandler and continues to determine whether the factory class has registered the transaction. If not, it returns to the next handler to complete the business request processing. If it has, it locates the transaction handler corresponding to the transaction, calls the postInvokeService method to extract the business evaluation elements from the transaction output information, generates a case number based on the business evaluation elements extracted from the transaction output information, and then calls the saveComment method of the factory class to determine whether to generate an HTTP request. If so, it starts an independent thread (in parallel with the main thread), calls the triggerComment method of the factory to construct an HTTP request according to the requirements corresponding to the business processing request, and throws it out. After throwing, it returns to the next handler to complete the business request processing.

[0101] This application establishes a factory class model. General basic data can be automatically intercepted and obtained by the base class. Each business module can choose to inherit from the base class to collect different business data based on its evaluation data requirements. The factory class methods are called through filters, divided into preInvokeService and PostInvokeService. In addition to collecting the necessary business elements for evaluation, PostInvokeService needs to return whether to actively trigger a third-party evaluation service. After evaluation data collection, a new independent thread is started to register the information to be evaluated, avoiding impact on the transaction entity and facilitating subsequent evaluation data collection and feedback. It supports multiple evaluation schemes, including active and passive modes, and is compatible with different evaluation needs across multiple centers in various locations. It establishes a correlation between business data and evaluation data, facilitating the review and re-evaluation of evaluation results and improving the authenticity and satisfaction of evaluations. The entire process of evaluation data generation, collection, transmission, analysis, and feedback is online, addressing business pain points and difficulties and promoting business development. It supports the needs of different evaluation schemes across multiple centers in various locations, facilitating expansion. It facilitates the expansion of evaluation channels and strengthens the protection of the rights and interests of evaluators and those being evaluated. It supports multiple evaluation channels and methods, including SMS, WeChat mini-programs, and evaluators. Establish a mapping relationship between evaluation processes and evaluation results to facilitate further tracking, analysis, and application of evaluation data, thereby promoting business improvement. Make good use of evaluation results. Strengthen the rectification of negative service reviews, and establish a mechanism for investigating, verifying, urging rectification, and providing feedback on negative reviews and complaints. Enhance the comprehensive analysis and application of evaluation data, promptly identify bottlenecks and difficulties in government services, and promote the refinement of service delivery. Establish a mechanism for the generation, collection, transmission, analysis, and feedback of "good and bad reviews" data, connecting various online and offline evaluation channels. Guarantee the right of evaluators to voluntarily and independently evaluate, and establish and improve the system for protecting evaluator information. Establish an appeal and review mechanism to eliminate erroneous and "malicious" negative reviews.

[0102] Figure 4 This is a schematic diagram illustrating the direct connection of a "good / bad review" system to a terminal according to the business processing method of the fourth embodiment of this application. Figure 4 The diagram shows the proactive evaluation mode. In the core system, the executing entity enters and submits a business request, determines whether the request requires evaluation, and terminates the process if not. If evaluation is required, the entity registers the business information (default value), assembles the URL of the business to be evaluated, calls the open area system to initialize the evaluation terminal device, displays user evaluations, submits user evaluations, and registers user evaluations in the core system. The executing entity can also download user evaluations from the core system. Furthermore, the executing entity can submit "processing evaluations" to the good / bad review system and query the evaluation details of completed items in the good / bad review system.

[0103] In proactive evaluation mode, the business to be evaluated is configurable, and filters automatically intercept and obtain business data. In proactive evaluation mode, the evaluation business URL is returned, redirecting to a third-party evaluation page or the system's virtual evaluation business URL, completing the evaluation terminal mapping. The evaluation system is proactively triggered. The third-party evaluation terminal (open zone system) service initializes, completes the evaluation, and synchronizes the evaluation results to the "Good / Bad Reviews" system and the core system. Synchronization of user evaluations from the "Good / Bad Reviews" system is enabled.

[0104] Figure 5 This is a schematic diagram illustrating the connection between a non-directly connected terminal and a "good / bad review" system according to the business processing method of the fifth embodiment of this application. Figure 5 The diagram shows the passive evaluation mode. The executing entity enters and submits a business transaction in the core system, determines whether the transaction needs evaluation, and terminates the process if not. If evaluation is required, the transaction information is registered (default value). The executing entity can query the transaction information to be evaluated from the core system. In the channel system, the executing entity can initialize the evaluation terminal device and periodically poll the backend service (every 3 seconds). Specifically, this can involve querying the transaction information to be evaluated in the core system. If no results are found, the process of periodically polling the backend service (every 3 seconds) is resumed. If results are found, user evaluations of the business are displayed and submitted to the channel system. The executing entity can register and upload user evaluations in the core system. The executing entity can also submit "processing evaluation" evaluations to the good / bad review system.

[0105] For non-directly connected terminals, the pending evaluation information registered after the service is submitted can be pushed to different terminals in multiple modes. Evaluation channels can proactively query pending evaluation information. A background scheduled task is added to register the push status of pending evaluation services and push them to designated channels. Evaluation results are synchronized with the core system. Open evaluation data is periodically synchronized with the "Good / Bad Reviews" system.

[0106] Figure 6 This is a schematic diagram of the main units of a service processing apparatus according to an embodiment of this application. Figure 6 As shown, the business processing device 600 includes a receiving unit 601, a timed push task generation unit 602, a case number generation unit 603, and a business processing unit 604.

[0107] The receiving unit 601 is configured to receive service processing requests, obtain corresponding service data and service identifiers, and then determine the evaluation terminal type based on the service identifiers.

[0108] The scheduled push task generation unit 602 is configured to generate scheduled push tasks based on business data and the evaluation terminal type in response to the evaluation terminal type being a non-directly connected terminal.

[0109] The case number generation unit 603 is configured to push business data to the evaluation terminal corresponding to the evaluation terminal type based on a timed push task, so that the evaluation terminal can generate a case number based on the business data.

[0110] The business processing unit 604 is configured to generate a request message based on the case number, so that the evaluation terminal can perform the corresponding business evaluation based on the request message and obtain the business evaluation result.

[0111] In some embodiments, the business processing apparatus further includes Figure 6 The extraction unit, not shown, is configured to, in response to a transaction identifier not being registered to the factory class, call the corresponding evaluation service program based on the evaluation terminal type to extract business data from the business data.

[0112] In some embodiments, the business processing apparatus further includes Figure 6 The mapping relationship establishment unit (not shown) is configured to: in response to the evaluation terminal type being a direct connection terminal, redirect to a third-party evaluation page to generate business evaluation results based on business evaluation elements; establish and store the mapping relationship between business data and business evaluation results.

[0113] In some embodiments, the case number generation unit 603 is further configured to: determine the push mode identifier corresponding to the timed push task, and then push the business evaluation elements in the business data to the evaluation terminal corresponding to the evaluation terminal type based on the push mode corresponding to the push mode identifier.

[0114] In some embodiments, the receiving unit 601 is further configured to: obtain the evaluation identifier carried in the service processing request, and in response to the evaluation identifier being non-empty, execute the process of obtaining service data and service identifier.

[0115] In some embodiments, the apparatus further includes Figure 6 The registration unit, not shown, is configured to: after obtaining the corresponding business data, start an independent thread to register the business data.

[0116] In some embodiments, the receiving unit 601 is further configured to: obtain the evaluation data requirement information carried in the business processing request, and then inherit the corresponding base class according to the evaluation data requirement information to obtain the business data corresponding to the evaluation data requirement information.

[0117] In some embodiments, the business processing apparatus further includes Figure 6 The review unit, not shown in the diagram, is configured to: in response to detecting an anomaly in the business evaluation result, invoke the appeal review mechanism to conduct an appeal review of the business evaluation result.

[0118] The functional modules that need to be added in this application embodiment include the following parts:

[0119] Business data acquisition module (can be set in receiving unit 601): Based on the factory class pattern, each business module completes its own implementation class according to the central data requirements, collecting business-specific data. The interceptor is responsible for intercepting business information and registering it into the database, facilitating the subsequent mapping between evaluation data and business data.

[0120] Customer review registration module (can be set in the registration unit): Supports the system to complete review records or synchronize the review results of external "good and bad reviews" systems.

[0121] Evaluation result synchronization module (can be set in the registration unit): Supports evaluation initiation and registration on different terminals, and is compatible with both upload and download modes of evaluation data.

[0122] Evaluation data query and analysis module (can be set in business processing unit 604): Supports comprehensive analysis and application of evaluation data, and, in combination with the actual situation of evaluation business, promptly summarizes and identifies bottlenecks and difficulties in government services, and promotes the refinement of service supply.

[0123] The addition of the aforementioned functional modules in this application embodiment enables support for different evaluation schemes across multiple centers in various regions, facilitating expansion. It facilitates the expansion of evaluation channels and strengthens the protection of the rights and interests of both evaluators and those being evaluated. It supports multiple evaluation channels and methods, including SMS, WeChat mini-programs, and evaluation devices. It establishes a mapping relationship between evaluation business and evaluation results, facilitating further tracking, analysis, and application of evaluation data to promote business improvement. It effectively utilizes evaluation results, strengthens the rectification of negative service reviews, and establishes a mechanism for investigating, verifying, urging rectification, and providing feedback on negative reviews and complaints. It enhances the comprehensive analysis and application of evaluation data, promptly identifying bottlenecks and difficulties in government services, and promoting the refinement of service supply. It establishes a mechanism for the generation, collection, transmission, analysis, and feedback of "good and bad reviews" data, connecting various online and offline evaluation channels. It guarantees the right of evaluators to voluntarily and independently evaluate, and establishes a sound system for protecting evaluator information. It establishes an appeal and review mechanism to eliminate erroneous and "malicious" negative reviews.

[0124] It should be noted that the business processing methods and business processing devices in this application are related in terms of specific implementation content, so repeated content will not be described again.

[0125] Figure 7 An exemplary system architecture 700 is shown that can be applied to the business processing method or business processing apparatus of the embodiments of this application.

[0126] like Figure 7As shown, system architecture 700 may include terminal devices 701, 702, and 703, a network 704, and a server 705. Network 704 serves as the medium for providing communication links between terminal devices 701, 702, and 703 and server 705. Network 704 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0127] Users can use terminal devices 701, 702, and 703 to interact with server 705 via network 704 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 701, 702, and 703, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0128] Terminal devices 701, 702, and 703 can be various electronic devices with business processing screens and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0129] Server 705 can be a server providing various services, such as a backend management server supporting business processing requests submitted by users using terminal devices 701, 702, and 703 (for example only). The backend management server can receive business processing requests, obtain corresponding business data and service identifiers, and then determine the evaluation terminal type based on the service identifiers. In response to a non-directly connected terminal, it generates a scheduled push task based on the business data and the evaluation terminal type. Based on the scheduled push task, it pushes business data to the evaluation terminal corresponding to the evaluation terminal type, enabling the evaluation terminal to generate a case number based on the business data. Based on the case number, it generates a request message, enabling the evaluation terminal to perform the corresponding business evaluation and obtain the business evaluation result. It calls the corresponding evaluation service program according to the evaluation terminal type to extract business data. When the evaluation terminal type is a non-directly connected terminal, it enables the evaluation terminal to generate a case number based on the business data, and then generate request information, enabling the evaluation terminal to perform business evaluation based on the generated request information. This allows for compatibility with evaluation needs across multiple transactions and centers, reduces local differences and integration difficulties, enhances the integration of evaluation data and business, reduces expansion difficulty and workload, strongly supports subsequent analysis and statistics, and provides feedback for business optimization and updates.

[0130] It should be noted that the business processing method provided in this application embodiment is generally executed by server 705, and correspondingly, the business processing device is generally set in server 705.

[0131] It should be understood that Figure 7The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0132] The following is for reference. Figure 8 It shows a schematic diagram of the structure of a computer system 800 suitable for implementing a terminal device according to the embodiments of this application. Figure 8 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0133] like Figure 8 As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 802 or programs loaded from storage section 808 into random access memory (RAM) 803. The RAM 803 also stores various programs and data required for the operation of the computer system 800. The CPU 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0134] The following components are connected to I / O interface 805: an input section 806 including a keyboard, mouse, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to I / O interface 805 as needed. A removable medium 811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 810 as needed so that computer programs read from it can be installed into storage section 808 as needed.

[0135] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 809, and / or installed from removable medium 811. When the computer program is executed by central processing unit (CPU) 801, it performs the functions defined above in the system of this application.

[0136] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. Computer-readable storage media can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0137] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0138] The units described in the embodiments of this application can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor may be described as including a receiving unit, a timed push task generation unit, a case number generation unit, and a business processing unit. The names of these units do not necessarily limit the specific unit itself.

[0139] In another aspect, this application also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the device to receive a service processing request, obtain corresponding service data and service identifiers, and then determine the evaluation terminal type based on the service identifiers; in response to the evaluation terminal type being a non-directly connected terminal, generate a scheduled push task based on the service data and the evaluation terminal type; push service data to the evaluation terminal corresponding to the evaluation terminal type based on the scheduled push task, so that the evaluation terminal generates a case number based on the service data; and generate a request message based on the case number, so that the evaluation terminal performs the corresponding service evaluation based on the request message and obtains the service evaluation result.

[0140] The computer program product of this application includes a computer program that, when executed by a processor, implements the business processing method in the embodiments of this application.

[0141] According to the technical solution of this application embodiment, the corresponding evaluation service program is called according to the evaluation terminal type to extract business data; when the evaluation terminal type is a non-directly connected terminal, the evaluation terminal generates a case number based on the business data, and then generates request information, so that the evaluation terminal performs business evaluation based on the generated request information. This can be compatible with the evaluation needs of multiple transactions and multiple centers, reduce local differences and connection difficulties, enhance the integration of evaluation data and business, reduce expansion difficulty and workload, strongly support subsequent analysis and statistics, and feed back into the optimization and updating of business.

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

Claims

1. A business processing method, characterized in that, include: The system receives a business processing request, obtains the corresponding business data and service identifier, and then determines the evaluation terminal type based on the service identifier. Obtaining the corresponding business data includes: obtaining the evaluation data requirement information carried in the business processing request, and then inheriting the corresponding base class based on the evaluation data requirement information to obtain the business data corresponding to the evaluation data requirement information. In response to the fact that the evaluation terminal type is a non-directly connected terminal, a timed push task is generated based on the business data and the evaluation terminal type; Based on the scheduled push task, the business data is pushed to the evaluation terminal corresponding to the evaluation terminal type, so that the evaluation terminal generates a case number based on the business data. This includes: periodically initiating a poll to the evaluation terminal, and pushing the business data to the evaluation terminal when it is determined that the business processing corresponding to the business processing request should be started, so that the evaluation terminal generates a case number based on the business data. The case number is a number used to represent the order in which the corresponding business is processed at the corresponding evaluation terminal. Based on the case number, a request message is generated, including: calling the saveComment method of the factory class to determine that a request message needs to be generated based on the case number, then starting an independent thread to call the triggerComment method of the factory class to generate the request message; so that the evaluation terminal performs the corresponding business evaluation based on the request message and obtains the business evaluation result; This also includes: entering the CommentHandler, defining temporary variables to store various information items required for the evaluation processing logic; determining whether the factory class has registered a transaction corresponding to the business; if so, locating the transaction handler, calling the service's preInvokeService method before the call, extracting business evaluation elements from the transaction input information, and executing the process of calling the corresponding backend service based on the ServiceId; otherwise, directly executing the process of calling the corresponding backend service based on the ServiceId, and after returning the transaction, re-entering the CommentHandler, and continuing to determine whether the factory class has registered a transaction corresponding to the business; if not, returning to the next handler to complete the business request processing; if so, locating the transaction handler, calling the postInvokeService method, extracting business evaluation elements from the transaction output information, and generating a case number based on the business evaluation elements extracted from the transaction output information.

2. The method according to claim 1, characterized in that, Before generating the scheduled push task based on the business data and the evaluation terminal type, the method further includes: Obtain the transaction identifier corresponding to the business processing request; In response to the fact that the transaction identifier is not registered to the factory class, the corresponding evaluation service program is invoked according to the evaluation terminal type to extract the business evaluation elements from the business data.

3. The method according to claim 2, characterized in that, The method further includes: In response to the fact that the evaluation terminal type is a direct connection terminal, the user is redirected to a third-party evaluation page to generate a business evaluation result based on the business evaluation elements. Establish and store the mapping relationship between the business data and the business evaluation results.

4. The method according to claim 2, characterized in that, The step of pushing the business data to the evaluation terminal corresponding to the evaluation terminal type based on the scheduled push task includes: The push mode identifier corresponding to the scheduled push task is determined, and then the business evaluation elements in the business data are pushed to the evaluation terminal corresponding to the evaluation terminal type based on the push mode corresponding to the push mode identifier.

5. The method according to claim 1, characterized in that, Before obtaining the corresponding business data, the method further includes: Obtain the evaluation identifier carried in the business processing request. In response to the evaluation identifier being non-empty, execute the process of obtaining business data and service identifier.

6. The method according to claim 1, characterized in that, The method further includes: After obtaining the corresponding business data, a separate thread is started to register and process the business data.

7. The method according to claim 1, characterized in that, The method further includes: In response to the detection of an anomaly in the business evaluation result, the appeal review mechanism is invoked to review the business evaluation result.

8. A business processing device, characterized in that, include: The receiving unit is configured to receive a service processing request, obtain the corresponding service data and service identifier, and then determine the evaluation terminal type based on the service identifier; wherein, obtaining the corresponding service data includes: obtaining the evaluation data requirement information carried in the service processing request, and then inheriting the corresponding base class based on the evaluation data requirement information to obtain the service data corresponding to the evaluation data requirement information. The scheduled push task generation unit is configured to generate a scheduled push task based on the business data and the evaluation terminal type in response to the evaluation terminal type being a non-directly connected terminal. The case number generation unit is configured to push the business data to the evaluation terminal corresponding to the evaluation terminal type based on the scheduled push task, so that the evaluation terminal generates a case number based on the business data. This includes: periodically polling the evaluation terminal to determine when to start executing the business processing request corresponding to the business processing request, and then pushing the business data to the evaluation terminal so that the evaluation terminal generates a case number based on the business data. The case number is a number representing the order in which the corresponding business is processed at the corresponding evaluation terminal. It also includes: entering the CommentHandler, defining temporary variables to store various information items required for the evaluation processing logic; determining whether the factory class has registered a transaction corresponding to the business; if so, locating the transaction processor and calling... The `preInvokeService` method is called to extract business evaluation elements from the transaction input information and execute the process of calling the corresponding backend service based on the `ServiceId`. Otherwise, the process of calling the corresponding backend service based on the `ServiceId` is executed directly. After returning the transaction, the process re-enters the `CommentHandler` and continues to check whether the factory class has registered a transaction corresponding to the business. If not, it returns to the next handler to complete the business request processing. If so, the transaction handler is located, and the `postInvokeService` method is called to extract business evaluation elements from the transaction output information and generate a case number based on the business evaluation elements extracted from the transaction output information. The business processing unit is configured to generate a request message based on the case number, including: calling the saveComment method of the factory class to determine if a request message needs to be generated based on the case number, then starting an independent thread to call the triggerComment method of the factory class to generate the request message; so that the evaluation terminal performs the corresponding business evaluation based on the request message and obtains the business evaluation result.

9. The apparatus according to claim 8, characterized in that, The device further includes an extraction unit configured to: Obtain the transaction identifier corresponding to the business processing request; In response to the fact that the transaction identifier is not registered to the factory class, the corresponding evaluation service program is invoked according to the evaluation terminal type to extract the business evaluation elements from the business data.

10. The apparatus according to claim 9, characterized in that, The device further includes a mapping relationship establishment unit, configured to: In response to the fact that the evaluation terminal type is a direct connection terminal, the user is redirected to a third-party evaluation page to generate a business evaluation result based on the business evaluation elements. Establish and store the mapping relationship between the business data and the business evaluation results.

11. The apparatus according to claim 9, characterized in that, The case number generation unit is further configured to: The push mode identifier corresponding to the scheduled push task is determined, and then the business evaluation elements in the business data are pushed to the evaluation terminal corresponding to the evaluation terminal type based on the push mode corresponding to the push mode identifier.

12. The apparatus according to claim 8, characterized in that, The receiving unit is further configured to: Obtain the evaluation identifier carried in the business processing request. In response to the evaluation identifier being non-empty, execute the process of obtaining business data and service identifier.

13. A business processing electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-7.

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

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-7.

Images