Message pushing method based on mobile banking APP

Abstract

The invention discloses a message pushing method based on a mobile phone bank APP. The message pushing method comprises the following steps: configuring related configuration information of pushing services of multiple channels and interface information of a message pushing function at a management end of a message pushing system; the mobile phone bank APP and the message service carry out authentication and transmit a message to the downstream; when the message is sent, the token is carried, and the message pushing system carries out analysis according to the received message data and automatically constructs a message body. The management end of the message pushing system not only covers essential basic functions of the management system, but also additionally provides the capability of monitoring SQL query in real time and service health state inspection. Through the enhanced monitoring characteristic, the user can master the operation state of the system in real time, and the stability and reliability of the message pushing service are ensured.

Description

Technical Field

[0001] This invention relates to the field of bank message push systems, and more particularly to a message push method based on a mobile banking APP. Background Technology

[0002] A message push system is a message delivery solution designed specifically for mobile banking apps. Its core purpose is to optimize and solve the problem of information transmission between communication devices.

[0003] With the rise and increasing maturity of the HarmonyOS system, compatibility with it has become an indispensable part of enterprise technology deployment. Taking mobile banking (HarmonyOS operating system) as an example, upstream and downstream apps in its business ecosystem need to rely on push notification functionality to flexibly cope with various complex and ever-changing business scenarios. HarmonyOS messaging service supports a wide variety of message scenarios, such as notification messages, background messages, in-app call messages, etc., and the message body structure differs for each scenario. This means that mobile banking apps need to build multiple types of message bodies to adapt to the diversity of HarmonyOS messaging service. However, once the message body structure of HarmonyOS push notification service changes, the mobile device needs to be re-adapted, and frequent application updates will undoubtedly weaken the user experience and affect satisfaction. In addition, to ensure information traceability, all messages sent by upstream systems should be logged and archived for future use.

[0004] Against this backdrop, push notification systems have emerged, boasting multi-channel access capabilities and comprehensive coverage of platforms such as Android, iOS, and the emerging HarmonyOS NEXT. Notably, this system has undergone deep optimization for HarmonyOS push notification functionality. By simplifying the complexity of message body structure and adopting a unified data format, it can flexibly handle all push notification scenarios under the HarmonyOS push notification service. The upstream system of mobile banking apps integrates all message scenarios into a single data format and uses message type as the distinguishing criterion before sending messages to the push notification system. The push notification system automatically constructs a message body structure matching the push notification service of that channel based on the received message type, ultimately accurately pushing the message to the downstream system.

[0005] Currently, after the upstream system of a mobile banking app constructs a push notification request body, it directly requests the push notification service of its respective channel, which then distributes the message to downstream systems. For different messaging scenarios, the message body structure of each channel's push notification service varies. The upstream system of the mobile banking app needs to construct multiple types of message bodies to meet the needs of different business scenarios, which undoubtedly increases the complexity of message body construction. Furthermore, storing a large number of messages directly on the client side is inconvenient, especially for business-related message types such as backend messages, where downstream systems rely on message commands to complete corresponding business operations. If messages are not properly stored, troubleshooting will become significantly more difficult if problems arise later.

[0006] This process also has a drawback: if the message structure of the push notification service changes, the mobile banking app must adapt promptly, otherwise it risks functional limitations. For mobile banking apps running on the client side, this means frequently guiding users to update the application to adapt to these changes. However, frequent application updates not only increase the user's usage cost but may also negatively impact the user experience, causing inconvenience. Summary of the Invention

[0007] In view of the above problems, the present invention is proposed to provide a message push method based on a mobile banking APP that overcomes or at least partially solves the above problems.

[0008] According to one aspect of the present invention, a message push method based on a mobile banking APP is provided, the message push method comprising:

[0009] Configure the relevant configuration information for push services from multiple channels and the interface information for push functions on the management terminal of the push system;

[0010] Mobile banking apps and messaging services perform authentication and transmit messages to downstream users;

[0011] When sending a message, a token is included. The message push system parses the received message data and automatically constructs the message body.

[0012] Optionally, the interface information includes: interface address, request method, protocol name, media type, and example request parameters.

[0013] Optionally, the example request parameters will serve as the data basis for the message push service platform to automatically match message types.

[0014] Optionally, the message push system parses the received message data and automatically constructs the message body, specifically including:

[0015] The message push system obtains channel information and the corresponding message push service interface data based on the token;

[0016] Based on the message type, the corresponding interface request parameter example is extracted as the template for constructing the message body. The automatic construction of the request body uses a recursive algorithm.

[0017] Optionally, the recursive algorithm specifically includes:

[0018] Map the input JSON data from the upstream mobile app to a predefined request body template structure to generate standardized JSON data that conforms to the template format;

[0019] By recursively parsing and processing the nested structure of JSON data layer by layer, it ensures that the fields at each level are consistent with the template definition, while also providing a function to fill in the default values ​​for missing fields.

[0020] Optionally, the detailed steps of the recursive algorithm specifically include:

[0021] After the message body is constructed, the message status of this request is recorded in the database, and the message is written to Kafka.

[0022] Send a request to the message push service. If the request is successful, update the message status in the database to "pushed" and return the status to the upstream system of the mobile banking APP.

[0023] If message sending fails, the template pattern is used to match the status code. If the message push failure is due to network issues, the message push will continue to be attempted. Otherwise, the failure information will be returned to the upstream system of the mobile banking APP for parameter adjustment.

[0024] Optionally, the nested structure of JSON data that is parsed and processed layer by layer recursively specifically includes:

[0025] If the template is an object type, process each field recursively, mapping the corresponding value in the input JSON to the template;

[0026] If the template is an array, process each element in the array recursively to ensure that the output array conforms to the template structure;

[0027] If the template is a value type, return the value from the input JSON directly, or retain the default value provided in the template.

[0028] Optionally, the default value filling function for missing fields specifically includes:

[0029] When certain fields are missing in the input JSON, the default values ​​in the template are used as a fallback to ensure the integrity of the output JSON.

[0030] This invention provides a message push method based on a mobile banking app. The method includes: configuring relevant configuration information for push services across multiple channels and interface information for the message push function on the management terminal of the message push system; authenticating between the mobile banking app and the message service, and transmitting messages downstream; carrying a token when sending a message; and parsing the received message data and automatically constructing the message body. The management terminal of the message push system not only covers the basic functions necessary for managing the system but also provides additional capabilities for real-time monitoring of SQL queries and service health status checks. Through these enhanced monitoring features, users can monitor the system's operating status in real time, ensuring the stability and reliability of the message push service.

[0031] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

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

[0033] Figure 1 A flowchart illustrating a message push method based on a mobile banking app, provided as an embodiment of the present invention;

[0034] Figure 2 This is a block diagram of the message push system provided in an embodiment of the present invention. Detailed Implementation

[0035] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0036] The terms "comprising" and "having," and any variations thereof, in the specification, embodiments, claims, and drawings of this invention are intended to cover non-exclusive inclusion, such as including a series of steps or units.

[0037] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

[0038] like Figure 1 As shown, a message push method based on a mobile banking app includes:

[0039] Configure the relevant configuration information for push services from multiple channels and the interface information for push functions on the management terminal of the push system;

[0040] Mobile banking apps and messaging services perform authentication and transmit messages to downstream users;

[0041] When sending a message, a token is included. The message push system parses the received message data and automatically constructs the message body.

[0042] Configure the relevant configuration information of the push service for each channel and the interface information of the push function in the management terminal of the push system. The interface information mainly includes the interface address, request method, protocol name, media type, and request parameter example. The request parameter example will serve as the data basis for the push service platform to automatically match the message type.

[0043] Mobile banking apps need to authenticate with the messaging service first. Once authentication is complete, they can send messages downstream. When sending a message, a token is required. The push notification system parses the received message data and automatically constructs the message body.

[0044] The specific process is as follows: The message push system obtains channel information and the interface data of the message push service corresponding to the channel based on the token. According to the message type, it extracts the request parameter example of the corresponding interface as a template for building the message body. The automatic construction of the request body adopts a recursive algorithm.

[0045] The core objective of the algorithm is to map the input JSON data from the upstream mobile app to a predefined request body template structure, generating standardized JSON data that conforms to the template format. Through recursion, the algorithm parses and processes the nested structure of the JSON data layer by layer, ensuring that the fields at each level remain consistent with the template definition, while also providing default value filling functionality for missing fields.

[0046] Recursive parsing and mapping, including:

[0047] If the template is an object type, process each field recursively, mapping the corresponding value in the input JSON to the template;

[0048] If the template is an array, process each element in the array recursively to ensure that the output array conforms to the template structure;

[0049] If the template is a value type, return the value from the input JSON directly, or retain the default value provided in the template.

[0050] Default values ​​are filled, including:

[0051] When certain fields are missing in the input JSON, the algorithm uses the default values ​​in the template as a fallback to ensure the integrity of the output JSON.

[0052] Universality and fault tolerance, including:

[0053] This algorithm is applicable to arbitrarily complex JSON and template structures, including nested objects and arrays.

[0054] It has strong fault tolerance and can safely handle situations where fields are missing or the structure is mismatched.

[0055] Scalability, including:

[0056] The algorithm supports dynamic template adjustment and can be expanded to include features such as field type validation, rule validation, and logging in the future.

[0057] After the message body is constructed, the message status of this request is recorded in the database, and the message is written to Kafka. A request is sent to the message push service. If the request is successful, the message status in the database is updated to "pushed" and the status is returned to the upstream system of the mobile banking app. If the message sending fails, a template pattern can be used to match the status code. If the message push failure is due to network or other reasons, the message push will continue to be attempted. Otherwise, the failure information will be returned to the upstream system of the mobile banking app for parameter adjustment.

[0058] The message push system's management interface not only covers the basic functions necessary for managing a system, but also provides additional capabilities such as real-time monitoring of SQL queries and service health checks. Through these enhanced monitoring features, users can stay informed about the system's operational status in real time, ensuring the stability and reliability of the message push service.

[0059] like Figure 2 As shown, the system of this invention is built on the Spring Boot architecture, with Nacos as the registry center, to realize the registration and discovery of push service (Push-Server).

[0060] The Gateway plays a crucial role in authenticating the mobile banking app and routing push notifications. The mobile banking app authenticates by submitting a unique identifier via an HTTP request. Upon successful authentication, the system generates and returns a token, storing its association with the mobile banking app in Redis to maintain session state. The database stores critical business data such as push notification status; messages that fail to push due to network issues are resent. Message content and operation logs are distributed and stored using Kafka for subsequent troubleshooting and log analysis. The file system stores unstructured data such as images. A monitoring system monitors SQL execution efficiency and the health of the push notification service in real time. Finally, the project integrates a build pipeline and other automated deployment processes to package the entire push notification system and seamlessly deploy it to the cloud environment, enabling rapid iteration and efficient operation and maintenance.

[0061] Beneficial effects:

[0062] Supports multi-channel access: It is compatible with multi-channel access and provides message push and message storage middleware capabilities for more platforms;

[0063] Historical message record storage: Supports original data recording and tracing of upstream message history received from various channels, ensuring transparency and traceability of information flow.

[0064] Simplified message body structure: When dealing with diverse message types, the upstream system only needs to provide a unified data format, and the message push system automatically adapts to the message body structure of the corresponding channel's message push service, which simplifies development and improves efficiency.

[0065] The above specific embodiments further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A message push method based on a mobile banking app, characterized in that, The message push method includes: Configure the relevant configuration information for push services from multiple channels and the interface information for push functions on the management terminal of the push system; Mobile banking apps and messaging services perform authentication and transmit messages to downstream users; When sending a message, a token is included. The message push system parses the received message data and automatically constructs the message body.

2. The message push method based on a mobile banking APP according to claim 1, characterized in that, The interface information includes: interface address, request method, protocol name, media type, and example request parameters.

3. The message push method based on a mobile banking APP according to claim 2, characterized in that, The example request parameters will serve as the data basis for the message push service platform to automatically match message types.

4. The message push method based on a mobile banking APP according to claim 1, characterized in that, The message push system parses the received message data and automatically constructs the message body, specifically including: The message push system obtains channel information and the corresponding message push service interface data based on the token; Based on the message type, the corresponding interface request parameter example is extracted as the template for constructing the message body. The automatic construction of the request body uses a recursive algorithm.

5. The message push method based on a mobile banking APP according to claim 1, characterized in that, The recursive algorithm specifically includes: Map the input JSON data from the upstream mobile app to a predefined request body template structure to generate standardized JSON data that conforms to the template format; By recursively parsing and processing the nested structure of JSON data layer by layer, it ensures that the fields at each level are consistent with the template definition, while also providing a function to fill in the default values ​​for missing fields.

6. The message push method based on a mobile banking APP according to claim 1, characterized in that, The detailed steps of the recursive algorithm include: After the message body is constructed, the message status of this request is recorded in the database, and the message is written to Kafka. Send a request to the message push service. If the request is successful, update the message status in the database to "pushed" and return the status to the upstream system of the mobile banking APP. If message sending fails, the template pattern is used to match the status code. If the message push failure is due to network issues, the message push will continue to be attempted. Otherwise, the failure information will be returned to the upstream system of the mobile banking APP for parameter adjustment.

7. A message push method based on a mobile banking app according to claim 5, characterized in that, The nested structure of JSON data parsing and processing layer by layer through recursion specifically includes: If the template is an object type, process each field recursively, mapping the corresponding value in the input JSON to the template; If the template is an array, process each element in the array recursively to ensure that the output array conforms to the template structure; If the template is a value type, return the value from the input JSON directly, or retain the default value provided in the template.

8. A message push method based on a mobile banking app according to claim 5, characterized in that, The default value filling function for missing fields specifically includes: When certain fields are missing in the input JSON, the default values ​​in the template are used as a fallback to ensure the integrity of the output JSON.

Images