Business processing methods and equipment

Abstract

This application provides a business processing method and apparatus, relating to the field of bank data processing technology. A mobile client interface displays a branch-specific page for a target branch to perform its unique business. The mobile client sends user operation information to the head office server. The head office server, based on the user operation information, sends a branch-specific business request to the branch server. The branch server responds to the request, obtains the branch-specific business result, and sends it back to the head office server, which then forwards it to the mobile client. The mobile client displays the branch-specific business result to the user. Users can complete the target branch's unique business through the branch-specific page on the mobile client. The head office achieves complete control over the target branch's branch-specific page, and users can instantly obtain the corresponding branch-specific business results, effectively improving data timeliness and enhancing user experience.

Description

Technical Field

[0001] This application relates to the field of bank data processing technology, and in particular to a business processing method and device. Background Technology

[0002] Currently, bank services on mobile clients are generally divided into nationally unified head office services and regionally specific branch services. Because branches offer numerous unique services while head office development resources are limited, to reduce development workload, head office tends to provide dedicated links to these branch-specific services on the mobile client, allowing users to access these services directly through these links.

[0003] However, because the development and maintenance of branch-specific services are handled by the branches themselves, the head office has no control over the branch-specific pages used for these services. Furthermore, data generated from user transactions for these services needs to be transmitted in batches from the branches to the head office via data exchange, typically with a T+1 timeframe. The head office cannot record user transactions in real-time, preventing users from accessing their transaction data immediately. Clearly, the current processing model for branch-specific services is highly detrimental to head office control and degrades user experience. Summary of the Invention

[0004] This application provides a business processing method and device to solve the technical problems in the prior art where the head office cannot control the branch's special pages and the data generated by users handling branch special services has poor timeliness, which reduces user experience.

[0005] Firstly, this application provides a business processing method applied to a head office server; the method includes:

[0006] The system receives user operation information sent by a mobile client. The user operation information is obtained based on the branch feature page of the target branch displayed on the interface of the mobile client. The branch feature page is used to carry out the branch feature business of the target branch.

[0007] Based on the user operation information, a branch-specific service request is sent to the branch server, so that the branch server responds to the branch-specific service request, performs business processing, and obtains the branch-specific service result;

[0008] The branch server forwards the branch-specific service results to the mobile client, enabling the mobile client to display the branch-specific service results.

[0009] In one possible design, prior to receiving user operation information sent by the mobile client, the following is also included:

[0010] The system receives region identification information sent by the mobile client, the region identification information being used to identify the geographical region where the target branch is located.

[0011] Based on the region identification information and local cache identifier, obtain the page information fragment of the target branch from the branch server;

[0012] The verified page information fragment and the corresponding page version number are sent to the mobile client, so that the mobile client generates the branch feature page based on the page information fragment and the page version number and displays the interface.

[0013] In one possible design, obtaining the page information fragment of the target branch from the branch server based on the region identification information and the local cache identifier includes:

[0014] The page number and branch server number of the branch feature page are obtained based on the region identification information;

[0015] If it is determined that the local cache identifier is not true, obtain the branch service information from the head office addressing server according to the branch server number;

[0016] The branch service information is used to send the page number to the branch server and receive the page information fragment returned by the branch server based on the page number.

[0017] The branch service information includes the IP address information, port information, and service endpoint information of the branch server.

[0018] In one possible design, after receiving the page information fragment returned by the branch server according to the page number, the method further includes:

[0019] Generate a page verification value based on the page information fragment, and determine whether the page verification value is consistent with the local page verification value;

[0020] If so, confirm that the page information fragment has passed the verification, and obtain the page version number corresponding to the page fragment.

[0021] In one possible design, if it is determined that the page information fragment verification fails, the method further includes:

[0022] An error message is generated and sent to the mobile client.

[0023] In one possible design, the method further includes:

[0024] Receive a page update request sent by the branch server. The page update request includes the page number to be updated, as well as the new values ​​of the page version number, page verification value, and server number corresponding to the page number to be updated.

[0025] If the page update request is verified, the page version number, page verification value, and server number corresponding to the page number to be updated in the database are all updated to their respective new values, and the local cache flag is set to no.

[0026] In one possible design, if the local cache identifier is determined to be yes, the method further includes:

[0027] Send locally cached page information fragments and the page version number corresponding to the page information fragments to the mobile client.

[0028] In one possible design, sending the branch-specific service request to the branch server based on the user operation information includes:

[0029] The user operation information is parsed to obtain the branch's special service request and the branch's server number;

[0030] The branch service information is obtained from the head office addressing server according to the branch server number;

[0031] The branch-specific service request is sent to the branch server based on the branch service information.

[0032] In one possible design, after parsing the user operation information to obtain the branch-specific service request, the method further includes:

[0033] Extract transaction features from the branch's special business requests. The transaction features include one or more of the following: transaction name, transaction amount, transaction time, and transaction location.

[0034] Generate corresponding transaction log records based on the transaction characteristics;

[0035] The transaction status corresponding to the branch's special service request is set to "in execution".

[0036] In one possible design, after receiving the branch-specific service result, the method further includes:

[0037] Update the transaction status corresponding to the branch's special service request based on the results of the branch's special service.

[0038] In one possible design, the method further includes:

[0039] Receive a user transaction history query request sent by the mobile client, and respond to the user transaction history query request by sending the transaction history record back to the mobile client;

[0040] The user transaction history query request is generated through the branch's featured page.

[0041] Secondly, this application provides a business processing method applied to a mobile client; the method includes:

[0042] Send user operation information to the head office server. The user operation information is obtained from the branch feature page of the target branch displayed on the interface of the mobile client. The branch feature page is used to carry out the branch feature business of the target branch.

[0043] The branch server receives and displays the branch-specific service results sent by the head office server. The branch-specific service results are obtained by the branch server in response to the branch-specific service request corresponding to the user operation information.

[0044] In one possible design, before sending the user operation information to the head office server, the following is also included:

[0045] Sending region identification information to the head office server, so that the head office server can obtain the page number and branch server number of the target branch from the branch server based on the region identification information, wherein the region identification information is used to identify the geographical region where the target branch is located;

[0046] Receive the page information fragment that has passed verification and the page version number corresponding to the page information fragment sent by the head office server;

[0047] The page information fragment and the page version number are used to generate and display the branch feature page of the target branch. The page information fragment corresponds to the page version number.

[0048] In one possible design, generating and displaying the branch-specific page for the target branch based on the page information fragment and the page version number includes:

[0049] Determine if the page with line breaks is cached locally;

[0050] If so, the interface will be displayed based on the locally cached line-specific pages;

[0051] If not, the rendering framework is invoked to read the received page information fragments, render the branch-featured page, and display the interface of the branch-featured page.

[0052] In one possible design, the interface display based on the locally cached line-by-line feature page includes:

[0053] Determine whether the version number corresponding to the locally cached line-by-line feature page is consistent with the page version number;

[0054] If so, display the interface for the local cached line-by-line feature page;

[0055] If not, the rendering framework is invoked to read the page information fragment in order to render the branch-featured page and display it.

[0056] In one possible design, after rendering the line break feature page, the following is also included:

[0057] The rendered branch-feature page is cached locally, and the version number corresponding to the branch-feature page is recorded.

[0058] In one possible design, the method further includes:

[0059] Send a user transaction history query request to the head office server and display the received transaction history records. The user transaction history query request is generated through the branch's special page.

[0060] Thirdly, this application provides a business processing apparatus applied to a head office server; the apparatus includes:

[0061] The first receiving module is used to receive user operation information sent by the mobile client. The user operation information is obtained based on the branch feature page of the target branch displayed on the interface of the mobile client. The branch feature page is used to perform the branch feature business of the target branch.

[0062] The first sending module is used to send a branch-specific service request to the branch server according to the user operation information, so that the branch server responds to the branch-specific service request, performs business processing, and obtains the branch-specific service result.

[0063] The first sending module is also used to forward the branch-specific service results sent by the branch server to the mobile client, so that the mobile client can display the branch-specific service results.

[0064] Fourthly, this application provides a business processing apparatus for use in a mobile client; the apparatus includes:

[0065] The second sending module is used to send user operation information to the head office server. The user operation information is obtained from the branch feature page of the target branch displayed on the interface of the mobile client. The branch feature page is used to carry out the branch feature business of the target branch.

[0066] The second receiving module is used to receive and display the branch-specific service results sent by the head office server. The branch-specific service results are obtained by the branch server in response to the branch-specific service request corresponding to the user operation information.

[0067] Fifthly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0068] The memory stores computer-executed instructions;

[0069] The processor executes computer execution instructions stored in the memory to implement any of the possible business processing methods provided in the first or second aspect.

[0070] In a sixth aspect, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement any one of the possible business processing methods provided in the first or second aspect.

[0071] In a seventh aspect, this application provides a computer program product, including computer execution instructions, which, when executed by a processor, are used to implement any one of the possible business processing methods provided in the first or second aspect.

[0072] The business processing method and equipment provided in this application allow a mobile client to display a branch-specific page showcasing the target branch's unique services. The mobile client sends user operation information obtained from the branch-specific page to the head office server. The head office server then sends a branch-specific service request to the branch server based on the user operation information. The branch server responds to the request, processes the service, and obtains the result, which is then sent back to the head office server. The head office server then forwards the result to the mobile client, which displays the result to the user. The mobile client can display the target branch's branch-specific page and its service results. Users can complete the target branch's unique services through this page on the mobile client. This allows the head office to have complete control over the target branch's branch-specific page, and users can instantly access the results of the branch-specific services through the mobile client, effectively improving data timeliness and enhancing user experience. Attached Figure Description

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

[0074] Figure 1 A schematic diagram of a system architecture provided for an embodiment of this application;

[0075] Figure 2 A flowchart illustrating a business processing method provided in an embodiment of this application;

[0076] Figure 3 A flowchart illustrating another business processing method provided in an embodiment of this application;

[0077] Figure 4 A flowchart illustrating another business processing method provided in an embodiment of this application;

[0078] Figure 5 A flowchart illustrating another business processing method provided in an embodiment of this application;

[0079] Figure 6 A flowchart illustrating another business processing method provided in an embodiment of this application;

[0080] Figure 7 This is a schematic diagram of the structure of a service processing device provided in an embodiment of this application;

[0081] Figure 8 This is a schematic diagram of another business processing apparatus provided in an embodiment of this application;

[0082] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0083] Figure 10 This is a schematic diagram of the structure of another electronic device provided in an embodiment of this application. Detailed Implementation

[0084] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of methods and apparatus consistent with some aspects of this application as detailed in the appended claims.

[0085] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0086] It should be noted that the collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0087] Currently, the head office typically provides links to branch-specific services on its mobile app, allowing users to access these services directly. However, because the development and maintenance of these branch-specific services are handled by the branches themselves, the head office lacks control over the pages used by the branches for these services. Furthermore, data generated from user transactions requires batch transmission from branches to the head office via data exchange, typically with a T+1 timeframe. The head office cannot record user transactions in real-time, preventing users from accessing their transaction data immediately. Therefore, the existing model for handling branch-specific services is highly detrimental to head office control and negatively impacts user experience.

[0088] To address the aforementioned problems in the existing technology, this application provides a business processing method and apparatus. The inventive concept of the business processing method provided in this application lies in: through information interaction between a mobile client and the head office server, the mobile client can display the branch's featured pages and the results of its featured services. Users can complete the featured services of the target branch through the featured pages on the mobile client. This allows the head office to have complete control over the featured pages of the target branch, and also enables users to instantly receive the results of the featured services, effectively improving data timeliness and enhancing user experience.

[0089] The following describes exemplary application scenarios of the embodiments of this application.

[0090] Figure 1 This is a schematic diagram of a system architecture provided for an embodiment of this application. Figure 1 As shown, the mobile client 101 contains native Android or iOS applications, which are used to process user business. The head office server 102 is deployed at the head office, first-level branches, or other branches of the bank. Branch servers 103, 104, and others are deployed at various branches under the head office, and these branches can be located in different geographical areas, such as different provinces or municipalities. This embodiment of the application, through information interaction between the mobile client 101, the head office server 102, and the branch servers, allows the head office to have complete control over the branch-specific pages of the target branches, and also allows users to instantly obtain the results of branch-specific services, effectively improving data timeliness and enhancing user experience. The branch-specific page refers to a regionally specific function developed on the mobile client 101 using single-page technology, which is generally only accessible to users within the branch's jurisdiction.

[0091] Optionally, Figure 1 The system architecture diagram shown may also include a head office addressing server 105, which is used to store branch service information of branch servers deployed in different geographical areas. The branch service information includes, but is not limited to, service number, IP address, port, service endpoint, etc. The service endpoint refers to the service address published to the outside world, which can be accessed by mobile client 101 for various business services.

[0092] Optionally, for information and data security, Figure 1 The system architecture diagram shown can also include a head office firewall 106 and a head office web server 107 to ensure data security within the system architecture.

[0093] It is understood that the mobile client 101 can be a smart device capable of running applications, such as a smartphone, tablet, or smart POS machine. This application embodiment does not limit the type of the mobile client 101. Figure 1 The example shown is a smartphone. The head office server 102 and the branch office servers can be servers, server clusters, etc. Figure 1 The example shown is a server cluster.

[0094] It should be noted that the above system architecture is merely illustrative, and the business processing methods provided in the embodiments of this application include, but are not limited to, the above system architecture.

[0095] Figure 2 This is a flowchart illustrating a business processing method provided in an embodiment of this application. Figure 2 As shown in the embodiments of this application, the business processing method includes:

[0096] S101: The mobile client sends user operation information to the head office server.

[0097] Accordingly, the head office server receives user operation information sent by the mobile client.

[0098] The user operation information is obtained from the branch feature page of the target branch displayed on the mobile client interface.

[0099] When a user requests a branch-specific service from a target branch, the user can perform actions on the branch-specific page displayed on the mobile client interface. These actions generate user action information. The mobile client then sends this information to the head office server, which in turn enables the branch server deployed at the target branch to process the corresponding branch-specific service based on the user action information. The branch-specific page is used to access the target branch's unique services.

[0100] S102: The head office server sends a request for branch-specific services to the branch server based on the user's operation information.

[0101] Accordingly, the branch server receives branch-specific service requests sent by the head office server based on user operation information.

[0102] Among them, the branch-specific service request is used to instruct the branch server to perform the branch-specific service corresponding to the user's operation information.

[0103] After receiving user operation information, the head office server sends a branch-specific service request to the branch server based on the user operation information, requesting the corresponding branch server to respond to the branch-specific service request and process the corresponding branch-specific service. Optionally, the head office server may forward the branch-specific service request to the branch server.

[0104] In one possible design, step S102 could be implemented as follows: Figure 3 As shown, Figure 3 This is a flowchart illustrating another business processing method provided in an embodiment of this application. For example... Figure 3 As shown, the embodiments of this application include:

[0105] S1021: Parse user operation information to obtain branch-specific business requests and branch server numbers.

[0106] S1022: Obtain branch service information from the head office addressing server based on the branch server number.

[0107] S1023: Send a request for branch-specific services to the branch server based on the branch service information.

[0108] After receiving the user's operation information, the head office server first parses the user's operation information to extract the branch-specific business request and the branch server number. The branch server number is used to identify the branch server of the target branch used to carry out the branch-specific business.

[0109] The head office addressing server stores the association between the branch service information of each branch server and the branch server number. After resolving the branch server number, the head office server can retrieve the corresponding branch service information of the target branch from the head office addressing server, such as service number, IP address, port, and service endpoint. Then, based on the branch service information, the head office server sends a branch-specific service request to the corresponding branch server of the target branch, enabling the head office server to send branch-specific service requests to branch servers based on user operation information.

[0110] Optionally, after step S1021, the head office server may further include:

[0111] The head office server extracts transaction features from the branch's special business requests. These features can include one or more of the following: transaction name, transaction amount, transaction time, and transaction location. Based on these features, the head office server generates a corresponding transaction log record, which means adding a new transaction log record locally. The log record status corresponding to the branch's special business request is set to "in execution" to indicate that the log record for the branch's special business request is currently in the process of execution.

[0112] S103: The branch server responds to the branch-specific business request, processes the business, and obtains the branch-specific business result.

[0113] After receiving a request for branch-specific services from the head office server, the branch server responds to the request by performing the business processing, i.e., executing the branch-specific service and obtaining the result.

[0114] For example, if the branch's special service request indicates an actual business such as payment or top-up, the branch server will perform the actual business and obtain the corresponding business processing result, i.e., the branch's special service result, such as business processing success or business processing failure.

[0115] S104: The branch server sends the results of the branch's special business to the head office server.

[0116] Correspondingly, the head office server receives the branch-specific business results sent by the branch server.

[0117] After the branch server completes the branch-specific business and obtains the result, it sends the result to the head office server.

[0118] S105: The head office server updates the transaction status corresponding to the branch's special business request based on the branch's special business results.

[0119] After the head office server receives the results of the branch's special business, it updates the transaction status of the branch's special business request based on the previously set transaction status, such as updating the transaction status to "successfully completed" or "execution failed".

[0120] S106: The head office server sends the results of the branch's special business to the mobile client.

[0121] Correspondingly, the mobile client receives the branch's special business results sent by the head office server.

[0122] The head office server sends the received branch-specific service results to the mobile client, so that the mobile client can display the branch-specific service results to users on the branch-specific page.

[0123] S107: The mobile client displays the results of the branch's special services.

[0124] The mobile client receives the branch's featured service results forwarded from the head office server and displays them on the corresponding branch's featured page for the user to check.

[0125] Based on the above embodiments, optionally, the business processing method provided in this application embodiment may further include:

[0126] S108: The mobile client sends a user transaction history query request to the head office server.

[0127] S109: The head office server responds to the user's transaction record query request and sends the transaction record back to the mobile client.

[0128] S1010: The mobile client displays transaction records.

[0129] When a user performs a transaction history query on the branch's featured page displayed on the mobile client interface, a user transaction history query request is generated. The mobile client sends this request to the head office server. Since the head office server has a record of the transaction history corresponding to the user's operation information—generated from transaction features extracted from the branch's featured business request obtained by parsing the user's operation information—and this record is stored locally on the head office server, the head office server will respond to the user's transaction history query request by retrieving the corresponding transaction history from its local database and sending it back to the mobile client for display. For the user, this allows for instant querying of transaction history records, eliminating the need for a T+1 timeout.

[0130] As described above, users perform actions on the branch-specific pages displayed on the mobile client interface, obtaining user operation information. The mobile client sends this information to the head office server. The head office server then sends a branch-specific service request to the branch server based on the user operation information. The branch server responds to the request, processes the service, obtains the corresponding branch-specific service result, and sends the result back to the mobile client via the head office server. The mobile client then displays the result to the user. Therefore, this embodiment completes branch-specific services through information interaction between the mobile client, the head office server, and the branch servers. This allows the head office to have full control over the branch-specific services set up by its subordinate branches. Users can then instantly access relevant data generated during the branch-specific service process on their mobile clients, such as service results, transaction status, and transaction records. This achieves T+0 timeliness for the relevant data, improving the user experience.

[0131] The business processing method provided in this application embodiment allows the mobile client to display the branch-specific pages and branch-specific business results of the target branch. Users can complete the branch-specific business of the target branch through the branch-specific pages on the mobile client. This enables the head office to have complete control over the branch-specific pages of the target branch. Users can instantly obtain the branch-specific business results corresponding to the branch-specific business through the mobile client, effectively improving data timeliness and enhancing user experience.

[0132] Based on the above embodiments, before step S101, the business processing method provided in this application embodiment further includes, as follows: Figure 4 The steps shown are for displaying the branch-specific pages on the mobile client. Figure 4 This is a flowchart illustrating another business processing method provided in an embodiment of this application. Figure 4 As shown, the embodiments of this application include:

[0133] S201: The mobile client sends region identification information to the head office server.

[0134] Accordingly, the head office server receives the region identification information sent by the mobile client.

[0135] Among them, the region identification information is used to identify the geographical region where the target branch is located.

[0136] For example, a user in the geographic area of ​​a target branch needs to conduct a branch-specific service at that branch. The user can select this geographic area in the application running on the mobile client, and the mobile client will then generate region identification information to identify that geographic area and send the region identification information to the head office server.

[0137] S202: The head office server obtains page information fragments of the target branch from the branch server based on the region identification information and the local cache identifier.

[0138] After receiving the region identification information sent by the mobile client, the head office server retrieves the page information fragments of the target branch from the branch server based on the region identification information and the local cache identifier. These page information fragments are used to render the branch's featured page, such as generating HTML / JS / CSS fragments for a webpage like the branch's featured page using HTML5 technology. The local cache identifier indicates whether the head office server has the target branch's featured page cached locally.

[0139] In one possible design, step S202 could be implemented as follows: Figure 5 As shown, Figure 5 This is a flowchart illustrating another business processing method provided in an embodiment of this application. Figure 5 As shown, the embodiments of this application include:

[0140] S2021: The head office server obtains the page number and branch server number of the branch's featured page based on the regional identification information.

[0141] After receiving the region identification information, the head office server parses the region identification information to obtain the page number and branch server number of the branch's featured page.

[0142] S2022: The head office server determines whether the local cache flag is positive or negative.

[0143] Further, the head office server determines the status of the local cache identifier, specifically whether the local cache identifier is negative. If it is negative (i.e., the determination result is positive), it means that the head office server does not have the branch-specific page cached locally, or that a new version of the branch-specific page has been released. Therefore, step S2023 needs to be executed to obtain the relevant information from the branch server to retrieve the branch-specific page that is not locally available. Conversely, if the local cache identifier is positive (i.e., the determination result is negative), it means that there is no new version of the branch-specific page. The head office server does not need to obtain page information fragments from the branch server; instead, it uses the locally cached page information fragments, and can then send the locally cached page information fragments and the corresponding page version number to the mobile client.

[0144] In other words, if the local cache identifier of the head office server is determined to be yes, the head office server sends the page information fragments cached locally and the page version number corresponding to the page information fragments to the mobile client, so that the mobile client can render the branch-specific pages accordingly.

[0145] S2023: The head office server obtains branch service information from the head office addressing server based on the branch server number.

[0146] If the head office server determines that its local cache identifier is false, the head office server retrieves the branch service information of the branch server from the head office addressing server based on the branch server number. The head office addressing server stores the association between the branch service information of each branch server and its corresponding branch server number. The branch service information may include, for example, the service number, IP address, port, and service endpoint.

[0147] S2024: The head office server sends the page number to the branch server based on the branch service information.

[0148] After the head office server obtains the branch service information, it sends the page number of the branch's featured page, which is not available locally, to the corresponding branch server based on the branch service information.

[0149] S2025: The branch server returns a page information fragment to the head office server based on the page number.

[0150] After receiving the page number of the branch's featured page, the branch server sends back the page information fragments it developed for that branch's featured page to the head office server. These page information fragments can be, for example, HTML5 technologies used to generate web page HTML / JS / CSS snippets for the branch's featured page. It's understood that the branch server supports rendering framework calls to complete the development of a single-page application and obtain the branch's featured page.

[0151] The business processing method provided in this application embodiment allows the head office server to obtain page information fragments for obtaining branch-specific pages from the branch server based on regional identification information and local cache identifiers. This can form a control mechanism for the head office to manage the development and production activities of the target branch for the branch-specific pages, effectively decoupling the development responsibilities of the head office and the branches.

[0152] S203: The head office server generates a page verification value based on the page information fragment and determines whether the page verification value is consistent with the local page verification value.

[0153] After receiving the page information fragment returned by the branch server, the head office server performs a check mechanism on the page information fragment. For example, the head office server recalculates the page information fragment to generate a corresponding page verification value based on the page information fragment, and then compares the calculated page verification value with the page verification value of the branch-specific page corresponding to the page number recorded locally, that is, the consistency of the local page verification value.

[0154] If the two are consistent, the result is confirmed as yes, and the verification passes. This indicates that the page information fragment received by the head office server is correct, and step S204 is then executed. Conversely, if the two are inconsistent, the result is confirmed as no. This indicates that the page fragment information used by the target branch's branch server to obtain the branch's special page is inconsistent with the content reported to the head office server during the registration phase, and the verification fails. Therefore, an error message needs to be generated and sent to the mobile client, i.e., step S205 is executed. Alternatively, the head office's control center can be notified to inform the control personnel.

[0155] S204: The head office server confirms that the page information fragment verification has passed and obtains the page version number corresponding to the page fragment.

[0156] The head office server determines that the received page information fragment has passed verification, then obtains the page version number corresponding to the verified page information fragment, and further executes step S206. It should be noted that the head office server may locally store information such as branch-specific page registration applications, region identification information, the page number of the branch-specific page, the page version number of the branch-specific page, the page verification value of the branch-specific page, and the association between this information and the branch server number of the corresponding target branch's branch server.

[0157] S205: The head office server generates an error message and sends it to the mobile client.

[0158] The head office server generates an error message and sends it to the mobile client.

[0159] S206: The head office server sends the verified page information fragment and the corresponding page version number to the mobile client.

[0160] Accordingly, the mobile client receives the verified page information fragment and the corresponding page version number sent by the head office server.

[0161] The head office server performs a check mechanism on the page information fragments it receives. If the check passes, it sends the page information fragment and the corresponding page version number to the mobile client so that the mobile client can render the page to obtain the branch's special page.

[0162] S207: The mobile client generates a branch-specific page for the target branch based on page information fragments and page version number, and displays the interface.

[0163] After receiving the page information fragment and the corresponding page version number sent by the head office server, the mobile client renders the branch-specific page of the target branch based on the page information fragment and the page version number using the rendering framework, and then displays the branch-specific page.

[0164] Among them, the mobile client supports calling the rendering framework to complete the development of single-page applications and obtain branch-specific pages.

[0165] In one possible design, step S207 could be implemented as follows: Figure 6 As shown. Figure 6 This is a flowchart illustrating another business processing method provided in an embodiment of this application. Figure 6 As shown, the embodiments of this application include:

[0166] S2071: Determine if the page with line breaks is cached locally.

[0167] After receiving the page information fragment and the corresponding page version number sent by the head office server, the mobile client first determines whether a branch-specific page is cached locally. If not, meaning no branch-specific page is cached locally, then step S2072 is executed. Conversely, if yes, meaning a branch-specific page is cached locally, then the interface can be displayed according to the cached branch-specific page, i.e., step S2073 is executed.

[0168] S2072: Call the rendering framework to read the received page information fragments, render the branch-featured page, and display the interface of the branch-featured page.

[0169] The mobile client supports the rendering framework of a single-page application. Therefore, when it determines that there is no line break feature page cached locally, it calls the rendering framework to read the page information fragment that it has received and verified, so as to render the corresponding line break feature page, and display the rendered line break feature page in its own application interface for user operation.

[0170] Optionally, the mobile client also caches the branch-featured page rendered by the rendering framework locally and records the version number corresponding to the rendered branch-featured page.

[0171] S2073: Determine whether the version number corresponding to the locally cached line-by-line special page is consistent with the page version number.

[0172] When the mobile client determines that there is a branch-specific page in the local cache, it further determines whether the version number corresponding to the branch-specific page in the local cache is consistent with the page version number it received. If they are consistent, it means that the version number of the branch-specific page in the local cache is consistent with the page version number stored on the head office server and rendered by the branch server. Then, the local cached branch-specific page can be used directly for interface display, i.e., step S2074 is executed.

[0173] Conversely, if the mobile client determines that the version number corresponding to the locally cached line-by-line feature page is inconsistent with the page version number it received, then the mobile client uses the page information fragment it received to render the corresponding line-by-line feature page, i.e., executes step S2072.

[0174] S2074: Display the interface of the locally cached line-by-line feature page.

[0175] The business processing method provided in this application embodiment involves a mobile client receiving a page information fragment and a corresponding page version number. The mobile client then determines whether a branch-specific page is cached locally. If so, it further confirms whether the version number of the cached branch-specific page matches the received page version number. If they match, the cached branch-specific page is used for interface display, improving display efficiency. Conversely, if no branch-specific page is cached locally, or if a cached page exists but its version number differs from the page version number, the rendering framework is invoked to read the page information fragment, render the corresponding branch-specific page, and display it. This method enables the mobile client to generate and display the target branch's branch-specific page based on the page information fragment and page version number, ensuring consistency between the branch-specific page displayed on the mobile client and the branch-specific page developed by the target branch's branch server, thus guaranteeing the smooth completion of branch-specific services.

[0176] Based on the above embodiments, optionally, the business processing method provided in this application embodiment may further include:

[0177] S208: The branch server sends a page update request to the head office server.

[0178] Accordingly, the head office server receives page update requests sent by the branch office servers.

[0179] S209: The head office server verifies the page update request. If the verification is successful, the page version number, page verification value, and server number corresponding to the page number to be updated in the database are all updated to their respective new values, and the local cache flag is set to no.

[0180] A branch office submits a page update request, which is then sent from the branch office server to the head office server. This request includes the page number to be updated, along with the new values ​​for the corresponding page version number, page verification value, and server number. Upon receiving the update request, the head office server verifies it. If verification is successful, it updates the corresponding data in its local storage. For example, it updates the page version number, page verification value, and server number in the database to their respective new values ​​and changes the local cache flag to "No," indicating that the target branch's featured page has a new version. This allows the head office server to control the deployment changes of the branch's featured page.

[0181] Optionally, when a branch needs to develop and register a branch-specific page, the branch can submit a page registration request. The branch server then sends the page registration request to the head office server. The page registration request includes the page number to be developed or registered, as well as the page version number, page verification value, and server number corresponding to that page number. After receiving the page registration request, the head office server verifies it. If the verification passes, the corresponding data is stored locally, for example, in the database, along with the page version number, page verification value, and server number corresponding to the page number to be developed or registered, thus completing the branch's registration of the branch-specific page with the head office.

[0182] The business processing method provided in this application embodiment enables the head office to form an effective control mechanism for the development, registration, and production of branch-specific pages by the target branch through information interaction between the mobile client, the head office server, and the branch server. This achieves the decoupling and separation of the development and operation responsibilities between the head office and the branches. Furthermore, through checking mechanisms such as page version number and page verification value, it ensures that the head office can fully control the production change behavior of the branches, thereby achieving effective control of the branch-specific business by the head office.

[0183] Figure 7 This is a schematic diagram of a service processing device provided in an embodiment of this application. Figure 7 As shown, the service processing apparatus 400 provided in this application embodiment includes:

[0184] The first receiving module 401 is used to receive user operation information sent by the mobile client. The user operation information is obtained from the branch feature page of the target branch displayed on the interface of the mobile client. The branch feature page is used to carry out the branch feature business of the target branch.

[0185] The first sending module 402 is used to send a branch-specific service request to the branch server according to the user operation information, so that the branch server responds to the branch-specific service request, performs business processing, and obtains the branch-specific service result.

[0186] The first sending module 403 is also used to forward the branch-specific business results sent by the branch server to the mobile client, so that the mobile client can display the branch-specific business results.

[0187] The business processing apparatus provided in this application embodiment can execute each step of the business processing method on the head office server side in the above method embodiment. Its implementation principle and technical effect are similar, and will not be repeated here.

[0188] Figure 8 This is a schematic diagram of another service processing apparatus provided in an embodiment of this application. Figure 8 As shown, the service processing apparatus 500 provided in this application embodiment includes:

[0189] The second sending module 501 is used to send user operation information to the head office server. The user operation information is obtained from the branch feature page of the target branch displayed on the interface of the mobile client. The branch feature page is used to carry out the branch feature business of the target branch.

[0190] The second receiving module 502 is used to receive and display the branch-specific business results sent by the head office server. The branch-specific business results are obtained by the branch server responding to the branch-specific business request corresponding to the user operation information and performing business processing.

[0191] The business processing apparatus provided in this application embodiment can execute each step of the business processing method on the mobile client side in the above method embodiment. Its implementation principle and technical effect are similar, and will not be repeated here.

[0192] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 9 As shown, the electronic device 600 may include a processor 601 and a memory 602 communicatively connected to the processor 601.

[0193] The memory 602 is used to store programs. Specifically, the program may include program code, which includes computer-executable instructions.

[0194] The memory 602 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0195] The processor 601 is used to execute computer execution instructions stored in the memory 602 to implement the business processing methods on the head office server side.

[0196] The processor 601 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0197] Optionally, the memory 602 can be either standalone or integrated with the processor 601. When the memory 602 is a device independent of the processor 601, the electronic device 600 may further include:

[0198] Bus 603 is used to connect processor 601 and memory 602. The bus can be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc., but this does not mean there is only one bus or one type of bus.

[0199] Optionally, in a specific implementation, if the memory 602 and the processor 601 are integrated on a single chip, the memory 602 and the processor 601 can communicate through an internal interface.

[0200] This application also provides a computer-readable storage medium, which may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. Specifically, the computer-readable storage medium stores computer-executable instructions, which are used in the various steps of the methods described in the above embodiments.

[0201] Figure 10 This is a schematic diagram of the structure of another electronic device provided in an embodiment of this application. For example... Figure 10 As shown, the electronic device 700 may include a processor 701 and a memory 702 communicatively connected to the processor 701.

[0202] The memory 702 is used to store programs. Specifically, the program may include program code, which includes computer-executable instructions.

[0203] The memory 702 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0204] The processor 701 is used to execute computer execution instructions stored in the memory 702 to enable business processing methods on the mobile client side.

[0205] The processor 701 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0206] Optionally, the memory 702 can be either standalone or integrated with the processor 701. When the memory 702 is a device independent of the processor 701, the electronic device 700 may further include:

[0207] Bus 703 is used to connect processor 701 and memory 702. The bus can be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc., but this does not mean there is only one bus or one type of bus.

[0208] Optionally, in a specific implementation, if the memory 702 and the processor 701 are integrated on a single chip, the memory 702 and the processor 701 can communicate through an internal interface.

[0209] This application also provides a computer-readable storage medium, which may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. Specifically, the computer-readable storage medium stores computer-executable instructions, which are used in the various steps of the methods described in the above embodiments.

[0210] This application also provides a computer program product, including computer execution instructions that, when executed by a processor, implement the steps of the methods described above.

[0211] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the claims.

[0212] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A service processing method characterized by, The application is applied to a total line server; the method comprises: Receiving user operation information sent by a mobile client, wherein the user operation information is obtained according to a branch characteristic page of a target branch displayed on an interface of the mobile client, and the branch characteristic page is used for carrying out branch characteristic services of the target branch; According to the user operation information, a branch characteristic service request is sent to a branch server, so that the branch server carries out service processing according to the branch characteristic service request to obtain a branch characteristic service result; Forwarding the branch characteristic service result sent by the branch server to the mobile client, so that the mobile client displays the branch characteristic service result; Before the receiving of the user operation information sent by the mobile client, the method further comprises: Receiving region identification information sent by the mobile client, wherein the region identification information is used for identifying a geographical region where the target branch is located; According to the region identification information and a local cache identifier, a page information segment of the target branch is obtained from the branch server; Sending the page information segment and a page version number corresponding to the page information segment to the mobile client, so that the mobile client generates the branch characteristic page according to the page information segment and the page version number and displays an interface; According to the region identification information, a page number and a branch server number of the branch characteristic page are obtained; If it is judged that the local cache identifier is no, branch service information is obtained from a total line addressing server according to the branch server number; According to the branch service information, the page number is sent to the branch server, and the page information segment returned by the branch server according to the page number is received; The branch service information comprises IP address information, port information and service endpoint information of the branch server. After the page information segment returned by the branch server according to the page number is received, the method further comprises:

2. The service processing method according to claim 1, characterized by, According to the page information segment, a page check value is generated, and it is determined whether the page check value is consistent with a local page check value; If yes, it is determined that the page information segment passes the check, and a page version number corresponding to the page segment is obtained. If it is determined that the page information segment does not pass the check, the method further comprises:

3. The service processing method according to claim 2, characterized by, Generating error prompt information and sending the error prompt information to the mobile client. Further comprising:

4. The service processing method according to claim 3, characterized by, Receiving a page update demand sent by the branch server, wherein the page update demand comprises a page number to be updated, a page version number corresponding to the page number to be updated, a page check value and a new value of a server number respectively; If the page update demand is verified to pass, the page version number, the page check value and the server number corresponding to the page number to be updated in the database are all updated to the respective new values, and the local cache identifier is set to no. If it is judged that the local cache identifier is yes, the method further comprises:

5. The service processing method of claim 1, wherein, ​ Send the locally cached page information segment and the page version number corresponding to the page information segment to the mobile client.

6. The transaction processing method according to any one of claims 1 to 5, characterized by, The sending of the branch characteristic service request to the branch server according to the user operation information comprises: The user operation information is parsed to obtain the branch characteristic service request and the branch server number; The branch service information is obtained from the head office addressing server according to the branch server number; The branch characteristic service request is sent to the branch server according to the branch service information.

7. The service processing method according to claim 6, characterized by, After the user operation information is parsed to obtain the branch characteristic service request, the method further comprises: Extracting transaction features in the branch characteristic service request, the transaction features comprising one or more of transaction name, transaction amount, transaction time and transaction location; Generating corresponding transaction flow records according to the transaction features; Setting the flow state corresponding to the branch characteristic service request to be in execution.

8. The service processing method according to claim 7, characterized by, After receiving the branch characteristic service result, the method further comprises: Updating the flow state corresponding to the branch characteristic service request according to the branch characteristic service result.

9. The service processing method according to claim 8, characterized by, Further comprising: Receiving a user flow query request sent by the mobile client, and returning the transaction flow records to the mobile client in response to the user flow query request; The user flow query request is generated through the branch characteristic page.

10. A service processing method characterized by comprising: Applied to a mobile client; The method comprises: Sending user operation information to a head office server, the user operation information being obtained according to a branch characteristic page of a target branch displayed on an interface of the mobile client, the branch characteristic page being used to perform branch characteristic services of the target branch; Receiving and displaying branch characteristic service results sent by the head office server, the branch characteristic service results being obtained by branch servers in response to branch characteristic service requests corresponding to the user operation information; Before sending the user operation information to the head office server, the method further comprises: Sending area identification information to the head office server, so that the head office server obtains a target branch page information segment from the branch server according to the area identification information and a local cache identifier, the area identification information being used to identify a geographical area where the target branch is located; Receiving a page information segment and a page version number corresponding to the page information segment sent by the head office server, the page information segment passing verification; Generating the branch characteristic page of the target branch according to the page information segment and the page version number, and performing interface display, the page information segment corresponding to the page version number; The page information segment is sent by the branch server according to branch service information to the branch server, and is returned by the branch server according to the page number, the page number is the page number of the branch characteristic page obtained according to the area identification information, and the branch service information is obtained from the head office addressing server according to the branch server number when it is judged that the local cache identifier is no.

11. The service processing method according to claim 10, characterized by, The branch characteristic page of the target branch is generated according to the page information segment and the page version number, and interface display is performed, including: Judging whether the local cache has a branch characteristic page; If yes, interface display is performed according to the local cache branch characteristic page; If no, the rendering framework is called to read the received page information segment to render the branch characteristic page, and interface display is performed on the branch characteristic page.

12. The transaction processing method of claim 11, wherein, The interface display is performed according to the local cache branch characteristic page, including: Judging whether the version number corresponding to the local cache branch characteristic page is consistent with the page version number; If yes, interface display is performed on the local cache branch characteristic page; If no, the rendering framework is called to read the page information segment to render the branch characteristic page, and the branch characteristic page is displayed.

13. The service processing method according to claim 11 or 12, characterized by, After the branch characteristic page is rendered, it further includes: The rendered branch characteristic page is cached locally, and the version number corresponding to the branch characteristic page is recorded.

14. The transaction processing method of claim 13, wherein, It further includes: Sending a user flow query request to the head office server to display the received transaction flow record, the user flow query request being generated through the branch characteristic page.

15. A service processing apparatus characterized by comprising: Applied to the head office server; The device includes: The first receiving module is configured to receive user operation information sent by a mobile client, the user operation information being obtained according to a branch characteristic page of a target branch displayed on the mobile client, the branch characteristic page being used to perform branch characteristic services of the target branch; The first sending module is configured to send a branch characteristic service request to a branch server according to the user operation information, so that the branch server performs service processing to obtain branch characteristic service results in response to the branch characteristic service request; The first sending module is further configured to forward branch characteristic service results sent by the branch server to the mobile client, so that the mobile client displays the branch characteristic service results; The first receiving module is further configured to receive area identification information sent by the mobile client, the area identification information being used to identify a geographical area where the target branch is located; The page information segment of the target branch is obtained from the branch server according to the area identification information and a local cache identifier; The branch characteristic page of the target branch is generated according to the page information segment and the page version number, and interface display is performed, including: Judging whether the local cache has a branch characteristic page; If yes, interface display is performed according to the local cache branch characteristic page; If no, the rendering framework is called to read the received page information segment to render the branch characteristic page, and interface display is performed on the branch characteristic page. The interface display is performed according to the local cache branch characteristic page, including: Judging whether the version number corresponding to the local cache branch characteristic page is consistent with the page version number; If yes, interface display is performed on the local cache branch characteristic page; If no, the rendering framework is called to read the page information segment to render the branch characteristic page, and the branch characteristic page is displayed. After the branch characteristic page is rendered, it further includes: The rendered branch characteristic page is cached locally, and the version number corresponding to the branch characteristic page is recorded. It further includes: Sending a user flow query request to the head office server to display the received transaction flow record, the user flow query request being generated through the branch characteristic page. Applied to the head office server; The device includes: The first receiving module is configured to receive user operation information sent by a mobile client, the user operation information being obtained according to a branch characteristic page of a target branch displayed on the mobile client, the branch characteristic page being used to perform branch characteristic services of the target branch; The first sending module is configured to send a branch characteristic service request to a branch server according to the user operation information, so that the branch server performs service processing to obtain branch characteristic service results in response to the branch characteristic service request; The first sending module is further configured to forward branch characteristic service results sent by the branch server to the mobile client, so that the mobile client displays the branch characteristic service results; The first receiving module is further configured to receive area identification information sent by the mobile client, the area identification information being used to identify a geographical area where the target branch is located; According to the area identification information and the local cache identifier, the page information segment of the target branch is obtained from the branch server; The mobile client is caused to generate and display the sub-branch featured page according to the page information segment and the page version number. The first receiving module is specifically configured to: The page number and the sub-branch server number of the sub-branch featured page are obtained according to the region identification information; If it is judged that the local cache identifier is no, the sub-branch service information is obtained from the total bank addressing server according to the sub-branch server number; The page number is sent to the sub-branch server according to the sub-branch service information, and the page information segment returned by the sub-branch server according to the page number is received; The sub-branch service information includes IP address information, port information and service endpoint information of the sub-branch server.

16. A service processing apparatus characterized by comprising: The device is applied to a mobile client and includes: The second sending module is configured to send user operation information to a total bank server, the user operation information being obtained according to a sub-branch featured page of a target sub-branch displayed on the mobile client, the sub-branch featured page being used to perform a sub-branch featured service of the target sub-branch; The second receiving module is configured to receive and display a sub-branch featured service result sent by the total bank server, the sub-branch featured service result being obtained by performing a service process on a sub-branch featured service request corresponding to the user operation information by a sub-branch server; The second sending module is further configured to send region identification information to the total bank server, so that the total bank server obtains a target sub-branch page information segment from the sub-branch server according to the region identification information and a local cache identifier, the region identification information being used to identify a geographical region where the target sub-branch is located; The second receiving module is further configured to receive a page information segment and a page version number corresponding to the page information segment sent by the total bank server, and generate and display the sub-branch featured page of the target sub-branch according to the page information segment and the page version number, the page information segment corresponding to the page version number; The page information segment is returned by the sub-branch server according to the page number, the page number being obtained according to the region identification information, and the sub-branch service information is obtained from the total bank addressing server according to the sub-branch server number when it is judged that the local cache identifier is no, the sub-branch service information including IP address information, port information and service endpoint information of the sub-branch server.

17. An electronic device, comprising: The device includes: A processor and a memory connected with the processor in communication; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory to implement the service processing method in any one of claims 1 to 9 or any one of claims 10 to 14.

18. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer-executable instructions, which, when executed by a processor, implement the business processing method according to any one of claims 1-8, or any one of 10-14.

19. A computer program product, comprising computer-executable instructions, which, when executed by a processor, implement the business processing method according to any one of claims 1-9, or any one of 10-14.

Images