Method and device for displaying payment marking activity
By adding daily scheduled tasks and real-time data records in the payment tag service system, the problem of unreal-time and high resource consumption of payment tag activity statistics and display in the existing technology is solved, and more intuitive and real-time display and Optimization of system resources.
Patent Information
- Application Number
- CN202411419085.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-12
- Publication Date
- 2024-11-12
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The existing payment tag service system lacks real-time and intuitiveness when stating and displaying payment tag activities, and the background database query has system operation risks and high resource consumption, which affects the normal operation of the system.
New daily scheduled tasks are added to the payment tag service system, automatically counting and writing historical data, recording the day's data in real time, and counting and displaying the history and day data in the display interface to achieve more intuitive and real-time display. Reduce system resource consumption.
It realizes a more intuitive, real-time and operational risk-free display of payment tagging activities, reduces system resource consumption, and improves the operation efficiency of payment tagging service system.
Smart Images

Figure CN118941289A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a method and device for displaying payment marking activities. Background Art
[0002] Payment tag service providers are responsible for the payment tag lifecycle management. In addition to providing payment tag generation, payment tag verification and other services, they should also collect statistics and display payment tag generation and payment tag verification activities in order to understand the operation status of payment tag activities.
[0003] At present, the statistics and display of payment tag activities by the payment tag service system are mainly through manual query on the front-end interface or query in the back-end database, and then displayed in a static manner. This method is not real-time and intuitive enough to display the operation of payment tag activities. There are system operation risks in the back-end database query, and it may also greatly increase the system resource consumption of the payment tag service system, thereby affecting the normal operation of the payment tag service system. Summary of the invention
[0004] The purpose of the present invention is to provide a method and device for displaying payment marking activities to improve the above technical problems.
[0005] In order to achieve the above objectives, the present application provides the following technical solutions: On the one hand, an embodiment of the present application provides a method for displaying a payment tag activity, the method comprising: adding a daily scheduled task in a payment tag service system so that the system runs automatically when idle, and after counting the relevant data of the payment tag generation and payment tag verification of the previous day, obtaining a historical payment tag activity statistical record corresponding to the previous day, and writing it into a database, thereby obtaining historical payment tag activity data; at the end of the transaction of the payment tag generation activity and the payment tag verification activity of the day, adding the relevant data of the payment tag activity to the statistics, and writing it into the memory in the form of a record, thereby obtaining the payment tag activity data of the day, wherein the content of the record is the same as the historical payment tag activity record; when entering the payment tag activity display interface, according to the above-mentioned historical payment tag activity data and the payment tag activity data of the day, statistics are performed, processed and displayed, including: the cumulative number of payment tag activities since the payment tag service system was put into operation to the day, the application scenarios supported by the payment tag activity and the number of payment tag generation activities and payment tag verification activities in the specified scenario and specified date period, and the type of payment tag activity failure and the corresponding number are displayed.
[0006] Optionally, the payment tag activity statistical record includes the cumulative number of payment tag activities, the number of payment tag applications in different application scenarios, the number of payment tag verifications in different application scenarios, and the types and corresponding numbers of payment tag activity failures, wherein the number of payment tag activities includes payment tag generation, payment tag verification, payment tag generation and verification, and the different application scenarios include mobile banking and aggregated payment.
[0007] Optionally, the implementation method of adding a daily scheduled task in the payment token service system is: Reading the operation cycle of each scheduled task in the database, and determining a target scheduled task from each scheduled task according to the operation cycle, wherein the target scheduled task is a task for collecting statistics on payment tag activity-related data of payment tag generation and payment tag verification on the previous day; Compare the estimated running time of the target scheduled task with the preset time index value, and determine whether the target scheduled task has dependency locking; When the estimated running time of the target scheduled task is less than the preset time index value and there is no dependency lock, determining the running mode of the target scheduled task; the running mode includes calling the interface running type; The metadata of the target scheduled task is sent to the task queue of the scheduling end corresponding to the operation mode, so that the payment token service system corresponding to the scheduling end executes data statistics related to the payment token activity.
[0008] Optionally, the step of determining whether the target scheduled task has a dependency lock includes: Reading metadata of the target scheduled task, and determining a first task identifier and a dependency status of a dependent task of the target scheduled task from the metadata; Reading the running status of the scheduled task corresponding to the first task identifier; If the running state does not match the dependency state, it is determined that the target scheduled task has a dependency lock.
[0009] In a second aspect, this embodiment provides a device for displaying a payment token activity, the device comprising: The first calculation module is used to add a daily scheduled task in the payment tag service system so that the system can automatically run when the system is idle, collect statistics on the payment tag generation and payment tag verification related data of the previous day, obtain a historical payment tag activity statistics record corresponding to the previous day, and write it into the database, thereby obtaining the historical payment tag activity data; The second calculation module is used to add relevant data statistics of the payment tag activity at the end of the transaction of the payment tag generation activity and the payment tag verification activity of the day, and write the data into the memory in the form of record, so as to obtain the payment tag activity data of the day, wherein the content of the record is the same as the historical payment tag activity record; The display module is used to count, process and display the historical payment tag activity data and the current day payment tag activity data when entering the payment tag activity display interface, including: the cumulative number of payment tag activities since the payment tag service system was put into operation to the current day, the application scenarios supported by the payment tag activities and the number of payment tag generation activities and payment tag verification activities in the specified scenario and specified date period, as well as the types of payment tag activity failures and the corresponding numbers.
[0010] The beneficial effects of the present invention are: The present invention prepares "historical payment tag activity data" and "daily payment tag activity data" in advance by adding scheduled tasks and real-time transaction notifications in the payment tag service system. When the payment tag activity is displayed, the data is accessed, and statistics, report rendering, and front-end timed data updates are performed, thereby realizing a more intuitive, more real-time, and operational risk-free display of the payment tag activity, and reducing system resource consumption. That is, while displaying the payment tag activity in a more real-time, more intuitive, and operational risk-free manner, it can also reduce the resource consumption caused by the display of the payment tag activity to the operation of the payment tag service system.
[0011] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or be understood by implementing the embodiments of the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.
[0013] Figure 1 It is a flow chart of a method for displaying a payment marking activity according to an embodiment of the present invention; Figure 2 is a schematic diagram of an implementation scenario corresponding to an embodiment of the present invention; Figure 3 A schematic diagram showing a payment tagging activity according to an embodiment of the present invention; Figure 4 A schematic diagram of “historical payment tag activity data” corresponding to an embodiment of the present invention; Figure 5 This is a schematic diagram of the “same-day payment tag activity data” described in an embodiment of the present invention. DETAILED DESCRIPTION
[0014] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.
[0015] It should be noted that similar reference numerals or letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. At the same time, in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.
[0016] Embodiment 1: like Figure 1-2 As shown, this embodiment provides a method for displaying a payment token activity, and the method includes step S100, step S200 and step S300.
[0017] Step S100: Add a daily scheduled task in the payment tag service system, such as 2:00-4:00 in the morning, so that the system can automatically run when idle. After collecting statistics on the payment tag generation and payment tag verification related data of the previous day (D-1), a historical payment tag activity statistical record corresponding to the previous day is obtained and written into the database, thereby obtaining historical payment tag activity data. The payment tag activity statistical record includes the cumulative number of payment tag activities (including payment tag generation, payment tag verification, payment tag generation and verification), the number of payment tag applications under different application scenarios (such as mobile banking, aggregated payment), and the number of payment tag activities that are not The number of payment tag verifications and the types and corresponding numbers of payment tag activity failures in the same application scenario. In this way, there are N days since the payment tag service system was put into operation, and there are N-1 "payment tag activity statistics records" in the database. If this method is used midway, the "payment tag activity statistics records" before the previous day can be generated at one time by cyclically running this scheduled task according to the time period. After all the "previous day" records are accumulated, the "historical payment tag activity data" is generated, where the number of payment tag activities includes payment tag generation, payment tag verification, and payment tag generation and verification. The different application scenarios include mobile banking and aggregated payment; Step S200: after the transaction of the payment tag generation activity and the payment tag verification activity of the day is completed, the relevant data of the payment tag activity is added and recorded in the memory, thereby obtaining the payment tag activity data of the day, wherein the content of the record is the same as the historical payment tag activity record, that is, the payment tag activity statistical record includes the cumulative number of payment tag activities (including payment tag generation, payment tag verification, payment tag generation and verification), the number of payment tag applications under different application scenarios (such as mobile banking, aggregated payment), the number of payment tag verifications under different application scenarios, and the types and corresponding numbers of payment tag activity failures. In this way, there is one "payment tag activity statistical record" of the day in the memory. When crossing days, no new record is added, and the data in the record is initialized and cleared; Step S300, when entering the payment tag activity display interface, such as in the web interface, statistics, processing and display are performed based on the above historical payment tag activity data and the payment tag activity data of the day, including: the cumulative number of payment tag activities from the commissioning of the payment tag service system to the day (i.e., DN day to D day), the application scenarios supported by the payment tag activity and the number of payment tag generation activities in the specified scenario (user selection, the first scenario by default), the number of payment tag verification activities in the specified date period (user selection, the default is the past 6 months), and the type of payment tag activity failure and the corresponding number of displays. For charts that need to be displayed as curve charts and pie charts, call the relevant chart components in the front-end framework, such as in the vue framework, such as in the echarts component, for rendering. In order to achieve real-time effects, the display interface is set to access the "Payment Tag Activity Data of the Day" after a timer, such as 1 second, and the data is synchronized to the display interface after updating.
[0018] like Figure 3 As shown, it includes the number of token generation activities, the total number of token activities, the number of token verification activities, the application scenarios of token activities, the token activity scenario curve, and the token activity failure pie chart.
[0019] The curve shows the number of token generation activities and token verification activities in a specified time period (user selected, default is the last 6 months) under a certain scenario (user selected, default is the first one), and the curves are shown separately.
[0020] Among them, the pie chart shows the types and corresponding numbers of token activity failures since the launch of TSP to the current time.
[0021] This embodiment prepares "historical payment tag activity data" and "daily payment tag activity data" in advance by adding scheduled tasks and real-time transaction notifications in the payment tag service system. When the payment tag activity is displayed, the data is accessed and statistics, report rendering, and front-end scheduled data updates are performed, thereby achieving a more intuitive, more real-time, and risk-free display of the payment tag activity and reducing system resource consumption.
[0022] Figure 4 This is a schematic diagram of the "Historical Payment Tag Activity Data" corresponding to this specification.
[0023] like Figure 4As shown, the token in the figure refers to the "payment tag". The "historical payment tag activity data" includes the payment tag activity data from the time the payment tag service system was put into operation (DN) to the previous day (D-1). It is stored in the database in the form of records, one record per day. There are N-1 records for as many days (N) since the system was put into operation, generating the "historical payment tag activity data".
[0024] The “payment tag activity data” on D-1 includes the total number of payment tag activities on D-1, scenario 1 on D-1: number of payment tag generation and verification activities, scenario N on D-1: number of payment tag generation and verification activities, and the types and corresponding numbers of payment tag activity failures on D-1.
[0025] Figure 5 This is a schematic diagram of the "Same-day Payment Mark Activity Data" corresponding to this instruction manual.
[0026] like Figure 5 As shown in the figure, "Current token activity data" is the token activity data record from 0:00 to the current time (the time when the user enters the activity display interface) of the day, which is stored in the memory as a record. The record content includes the total number of token activities on D day, D day scenario 1: the number of token generation and verification activities, D day scenario N: the number of token generation and verification activities, and the types and corresponding numbers of token activity failures on D-1 day.
[0027] Secondly, the specific implementation method of adding a daily scheduled task in the payment token service system can be: Step 131, reading the operation cycle of each scheduled task in the database, and determining a target scheduled task from each scheduled task according to the operation cycle, wherein the target scheduled task is a task for collecting statistics on payment tag activity-related data of payment tag generation and payment tag verification on the previous day; Step 132: Compare the estimated running time of the target scheduled task with the preset time index value, and determine whether the target scheduled task has a dependency lock; Step 133: when the estimated running time of the target scheduled task is less than the preset time index value and there is no dependency lock, determine the running mode of the target scheduled task; the running mode includes calling the interface running type; Step 134: Send the metadata of the target scheduled task to the task queue of the scheduling end corresponding to the operation mode, so that the payment token service system corresponding to the scheduling end executes data statistics related to the payment token activity.
[0028] The specific implementation method of the step of determining whether the target scheduled task has a dependency lock in step S132 may be: Step S1321, reading metadata of the target scheduled task, and determining a first task identifier and a dependency status of a dependent task of the target scheduled task from the metadata; Step S1322: Read the running status of the scheduled task corresponding to the first task identifier; Step S1323: If the running state does not match the dependency state, it is determined that the target scheduled task has a dependency lock.
[0029] The above-mentioned scheduled task processing method determines the current target scheduled task by reading the operating cycle of each scheduled task in the database. When the estimated operating time of the target scheduled task is less than the preset duration indicator value and there is no dependency lock, the metadata of the target scheduled task is sent to the task queue of the scheduling end corresponding to the operating mode of the target scheduled task, so as to schedule the scheduled task to different scheduling ends, and the scheduling end calls the execution server to execute the target scheduled task. The task queue is used to decouple the scheduling of the scheduled task and the execution of the scheduled task, so as to realize the processing of the scheduled task between multiple servers and multiple systems, so that the processing of the scheduled task is not affected by the performance of a single machine, and the generation of performance bottlenecks and the decline in the accuracy and frequency of the execution of scheduled tasks are effectively avoided.
[0030] Embodiment 2: like Figure 2 As shown, this embodiment provides a device for displaying a payment token activity, the device comprising: The first calculation module is used to add a daily scheduled task in the payment tag service system so that the system can automatically run when the system is idle, collect statistics on the payment tag generation and payment tag verification related data of the previous day, obtain a historical payment tag activity statistics record corresponding to the previous day, and write it into the database, thereby obtaining the historical payment tag activity data; The second calculation module is used to add relevant data statistics of the payment tag activity at the end of the transaction of the payment tag generation activity and the payment tag verification activity of the day, and write the data into the memory in the form of record, so as to obtain the payment tag activity data of the day, wherein the content of the record is the same as the historical payment tag activity record; The display module is used to count, process and display the historical payment tag activity data and the payment tag activity data of the day when entering the payment tag activity display interface, including: the number of payment tag activities accumulated since the payment tag service system was put into operation to the day, the payment tag activity data ... Record the application scenarios supported by the activity, as well as the number of payment tag generation activities and payment tag verification activities in the specified scenario and date period, as well as the types and corresponding numbers of payment tag activity failures.
[0031] It should be noted that, regarding the device in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.
Claims
1. A method for displaying a payment token activity, characterized in that: The method comprises: Add a daily scheduled task in the payment token service system to enable the system to run automatically when the system is idle. After collecting statistics on the payment token generation and payment token verification activities of the previous day, a historical payment token activity statistics record corresponding to the previous day is obtained and written into the database, thereby obtaining historical payment token activity data; At the end of the transaction of the payment tag generation activity and the payment tag verification activity of the day, the relevant data of the payment tag activity is added and recorded in the memory, thereby obtaining the payment tag activity data of the day, wherein the content of the record is the same as the historical payment tag activity record; When entering the payment tag activity display interface, statistics are collected, processed and displayed based on the above-mentioned historical payment tag activity data and the payment tag activity data of the day, including: the cumulative number of payment tag activities since the payment tag service system was put into operation to the day, the application scenarios supported by the payment tag activities and the number of payment tag generation activities in the specified scenario and specified date period, the number of payment tag verification activities and the type and corresponding number of failed payment tag activities.
2. The method for displaying a payment token activity according to claim 1, characterized in that: The payment tag activity statistical record includes the cumulative number of payment tag activities, the number of payment tag applications in different application scenarios, the number of payment tag verifications in different application scenarios, and the types and corresponding numbers of payment tag activity failures, wherein the number of payment tag activities includes payment tag generation, payment tag verification, and payment tag generation and verification, and the different application scenarios include mobile banking and aggregated payment.
3. The method for displaying payment token activities according to claim 1, characterized in that: The implementation method of adding a daily scheduled task in the payment token service system is as follows: Reading the operation cycle of each scheduled task in the database, and determining a target scheduled task from each scheduled task according to the operation cycle, wherein the target scheduled task is a task for collecting statistics on payment tag activity-related data of payment tag generation and payment tag verification on the previous day; Compare the estimated running time of the target scheduled task with the preset time index value, and determine whether the target scheduled task has dependency locking; When the estimated running time of the target scheduled task is less than the preset time index value and there is no dependency lock, determining the running mode of the target scheduled task; the running mode includes calling the interface running type; The metadata of the target scheduled task is sent to the task queue of the scheduling end corresponding to the operation mode, so that the payment token service system corresponding to the scheduling end executes data statistics related to the payment token activity.
4. The method for displaying payment token activities according to claim 3, characterized in that: The step of determining whether the target scheduled task has a dependency lock comprises: Reading metadata of the target scheduled task, and determining a first task identifier and a dependency status of a dependent task of the target scheduled task from the metadata; Reading the running status of the scheduled task corresponding to the first task identifier; If the running state does not match the dependency state, it is determined that the target scheduled task has a dependency lock.
5. A device for displaying payment marking activities, characterized in that: The device comprises: The first calculation module is used to add a daily scheduled task in the payment tag service system so that the system can automatically run when the system is idle, collect statistics on the payment tag generation and payment tag verification related data of the previous day, obtain a historical payment tag activity statistics record corresponding to the previous day, and write it into the database, thereby obtaining the historical payment tag activity data; The second calculation module is used to add relevant data statistics of the payment tag activity at the end of the transaction of the payment tag generation activity and the payment tag verification activity of the day, and write the data into the memory in the form of record, so as to obtain the payment tag activity data of the day, wherein the content of the record is the same as the historical payment tag activity record; The display module is used to count, process and display the historical payment tag activity data and the current day payment tag activity data when entering the payment tag activity display interface, including: the cumulative number of payment tag activities since the payment tag service system was put into operation to the current day, the application scenarios supported by the payment tag activities and the number of payment tag generation activities and payment tag verification activities in the specified scenario and specified date period, as well as the types of payment tag activity failures and the corresponding numbers.
Citation Information
Patent Citations
Internet of Things-based business monitoring and management method
CN107909337A
Timed task scheduling method and timed task processing method
CN109992390A
Mobile phone payment security protection system
CN113592508A
Internet proxy accounting intelligent platform based on blockchain technology
CN113592614A
Automatic payment and settlement method and system
CN114418559A
