Financial terminal application and SP timeout protocol negotiation method, system, device and medium

Abstract

The invention discloses a financial terminal application and SP timeout protocol negotiation method, system, device and medium wherein the financial terminal application and SP timeout protocol negotiation method comprises: initiating a request to the device, the request carrying a timeout time parameter; receiving a timeout time value sent by the device in response to the timeout time parameter, wherein the timeout time value is determined based on the device capability and configuration; adjusting an application timeout time value according to the timeout time value of the equipment, so that the application timeout time value is consistent with the timeout time value of the equipment; according to the method, the error rate of the device can be reduced, it is ensured that interaction between the application program and the device is smoother and more efficient, and meanwhile service requirements and user experience can be met.

Description

Technical Field

[0001] The present invention relates to the technical field of financial services, and in particular to a method, system, device and medium for negotiating a timeout protocol between a financial terminal application and an SP. Background Art

[0002] In the ATM cross-platform WOSA (World Open Services for Applications) protocol, if the application issues a timeout for a request, and the device cannot complete the hardware action required by the request within the timeout, the request will usually fail, and the application needs to handle the timeout exception. The application will usually receive a timeout exception or error code. Generally, the application can design a retry mechanism to deal with the timeout situation, and can record the timeout exception for subsequent troubleshooting and analysis.

[0003] In the financial services sector, the timeout setting has a more direct impact on system performance, user experience, and security. If the timeout is too long, users may become impatient; if it is too short, it may lead to frequent timeout exceptions, affecting user experience. Summary of the invention

[0004] In order to ensure that the interaction between applications and devices is smoother and more efficient while meeting business needs and user experience, the present application provides a method, system, device and medium for negotiating a timeout protocol between a financial terminal application and an SP.

[0005] On the one hand, a method for negotiating a timeout protocol between a financial terminal application and an SP is provided, which is applied to an application program, and the method includes:

[0006] Initiate a request to the device, the request carrying a timeout parameter;

[0007] receiving a timeout value sent by the device in response to the timeout parameter, the timeout value being determined based on the device capability and configuration;

[0008] The application timeout value is adjusted according to the timeout value of the device so that the application timeout value is consistent with the timeout value of the device.

[0009] In an optional implementation, the method for determining the timeout value of the device includes:

[0010] Based on business needs and performance requirements, perform performance testing on the equipment, evaluate the average response time and maximum response time of the equipment under different operations, and obtain equipment performance test results;

[0011] A timeout value of the device is set according to the device performance test result and the hardware limitation of the device, and the timeout value of the device includes device timeout values ​​corresponding to different business requirements.

[0012] In an optional implementation manner, before performing a performance test on the device based on the business demand and the performance requirement, the method further includes:

[0013] Evaluate the business needs, including determining the time requirements for each operation in the business process;

[0014] Determine the performance requirements, including determining the maximum response time of the device and the waiting time acceptable to the user.

[0015] In an optional embodiment, the method further includes:

[0016] monitoring the response time and timeouts of the device;

[0017] According to the monitoring result, the application timeout value is dynamically adjusted.

[0018] On the other hand, a method for negotiating a timeout protocol between a financial terminal application and an SP is provided, which is applied to a device and includes:

[0019] receiving a request from an application, wherein the request carries a timeout parameter;

[0020] In response to the timeout parameter, the timeout value of the device is sent to the application, and the timeout value is determined based on the device capability and configuration; the timeout value of the device is used by the application to adjust the application timeout value so that the application timeout value is consistent with the timeout value of the device.

[0021] In an optional embodiment, the method further includes:

[0022] Based on business needs and performance requirements, perform performance testing on the equipment, evaluate the average response time and maximum response time of the equipment under different operations, and obtain equipment performance test results;

[0023] A timeout value of the device is set according to the device performance test result and the hardware limitation of the device, and the timeout value of the device includes device timeout values ​​corresponding to different business requirements.

[0024] In an optional implementation, before sending the timeout value of the device to the application, the method further includes:

[0025] Determine the current business demand, and obtain the device timeout value corresponding to the current business demand;

[0026] Sending a device timeout value corresponding to the current service requirement to the application.

[0027] On the other hand, a method for negotiating a timeout protocol between a financial terminal application and an SP is also provided, the method comprising:

[0028] The application initiates a request to the device, wherein the request carries a timeout parameter;

[0029] The device receives the request, and in response to the timeout parameter, sends a timeout value of the device to the application, where the timeout value is determined based on the device capability and configuration;

[0030] The application receives the timeout value of the device, and adjusts the application timeout value according to the timeout value of the device, so that the application timeout value is consistent with the timeout value of the device.

[0031] On the other hand, a financial terminal application and SP timeout protocol negotiation system is provided, including an application module, an SP module and a rule base module, wherein:

[0032] The application module is used to initiate a request to the device, wherein the request carries a timeout parameter;

[0033] The SP module is configured to receive the request, and in response to the timeout parameter, send a timeout value of the device to the application, wherein the timeout value is determined based on the device capability and configuration;

[0034] The application module is further used to receive a timeout value of the device, and adjust the application timeout value according to the timeout value of the device, so that the application timeout value is consistent with the timeout value of the device;

[0035] The rule base module is used to store the timeout negotiation rules between the application module and the SP module.

[0036] According to a third aspect, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the aforementioned financial terminal application and SP timeout protocol negotiation method and any possible implementation method thereof.

[0037] In a fourth aspect, a computer storage medium is provided, wherein the computer storage medium stores one or more instructions, wherein the one or more instructions are suitable for being loaded by a processor and executing the steps of the above-mentioned financial terminal application and SP timeout protocol negotiation method and any possible implementation method thereof.

[0038] The present application initiates a request to a device, wherein the request carries a timeout parameter; receives a timeout value sent by the device in response to the timeout parameter, wherein the timeout value is determined based on the device capability and configuration; adjusts the application timeout value according to the timeout value of the device so that the application timeout value is consistent with the timeout value of the device; the method determines the timeout by negotiation, which can reduce the error rate of the device, ensure that the interaction between the application and the device is smoother and more efficient, and meet business needs and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.

[0040] Figure 1 A flowchart of a method for negotiating a timeout protocol between a financial terminal application and an SP provided in an embodiment of the present application;

[0041] Figure 2 A flowchart of another method for negotiating a timeout protocol between a financial terminal application and an SP provided in an embodiment of the present application;

[0042] Figure 3 A flowchart of another method for negotiating a timeout protocol between a financial terminal application and an SP provided in an embodiment of the present application;

[0043] Figure 4 A schematic diagram of the structure of a financial terminal application and SP timeout protocol negotiation system provided in an embodiment of the present application;

[0044] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0046] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0047] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0048] The WOSA protocol mentioned in the embodiments of the present application simplifies the development and deployment process of Windows applications by providing a standard interface and architecture. At the same time, through its extensions such as WOSA / XFS and MAPI, it further meets the special needs of specific industries such as the financial industry, and improves the interoperability and efficiency of software.

[0049] In the ATM cross-platform WOSA (World Open Services for Applications) protocol, if an application sends a timeout for a request and the device cannot complete the hardware action required by the request within the timeout, the following situations usually occur:

[0050] 1. Timeout exception:

[0051] When a device fails to complete a request within the specified timeout period, the application typically receives a timeout exception or error code.

[0052] This exception is usually caught by the ATM application and appropriate error handling is performed.

[0053] 2. Request failed:

[0054] If the hardware action is not completed within the timeout period, the request is considered failed.

[0055] The application needs to handle request failures based on specific circumstances, such as retrying, prompting the user, and logging.

[0056] 3. Retry mechanism:

[0057] Applications can design a retry mechanism to handle timeout situations.

[0058] For example, after the first request times out, the application can try to send the request again, or try other alternatives.

[0059] 4. Status recovery:

[0060] If the request involves a change in hardware state (such as dispensing cash), the application needs to ensure that it can recover to a safe state.

[0061] This might include rolling back some operations or marking the device as unavailable until the problem is resolved.

[0062] 5. Logging:

[0063] The application needs to record timeout exceptions to facilitate subsequent troubleshooting and analysis.

[0064] The log should contain sufficient information, such as request type, request time, timeout, etc.

[0065] Based on the above description, an example of an application scenario is given:

[0066] Assume that an ATM application sends a cash dispensing request to the hardware and sets a timeout of 10 seconds. If the hardware fails to complete the cash dispensing action within 10 seconds, the following will happen:

[0067] 1. The application receives a timeout exception:

[0068] The application may receive a timeout exception, such as a specific error code defined in the WOSA protocol.

[0069] For example, an application might receive an error code such as WOSA_ERROR_TIMEOUT.

[0070] 2. Handling exceptions:

[0071] The application needs to handle this exception, such as logging, displaying an error message to the user, or performing other error handling logic.

[0072] 3. Retry mechanism:

[0073] The application may try to resend the cash out request.

[0074] If the retries still fail, further action may be required, such as notifying an administrator or prompting the user to contact their bank.

[0075] 4. Status recovery:

[0076] If the request is not completed successfully, the application needs to ensure that the ATM returns to a safe state.

[0077] For example, if cash has been partially dispensed but not completely, the application needs to ensure that the cash is recycled and the ATM is marked as unusable.

[0078] 5. User Interaction:

[0079] Apps need to provide users with clear information about what happened and provide guidance on next steps.

[0080] For example, an error message is displayed: "The device is temporarily unable to complete the operation. Please try again later."

[0081] The embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application.

[0082] See also Figure 1 , Figure 1 is a flowchart of a method for negotiating a timeout protocol between a financial terminal application and an SP provided in an embodiment of the present application, such as Figure 1 As shown, the method is applied to an application program, and the method may include:

[0083] 101. The application initiates a request to the device, and the request carries a timeout parameter;

[0084] 102. The application receives a timeout value sent by the device in response to the timeout parameter, where the timeout value is determined based on the device capability and configuration;

[0085] 103. The application program adjusts the application timeout value according to the timeout value of the device, so that the application timeout value is consistent with the timeout value of the device.

[0086] The application in the embodiment of the present application may be an application in the ATM cross-platform WOSA protocol, and the device may be a financial terminal device.

[0087] Specifically, the application can communicate with the device and send a request to make the device complete the corresponding instruction. A reasonable timeout period needs to be configured on the device side. When the application communicates with the device, the device can be informed of the expected timeout period, that is, the timeout period parameter carried in the above request.

[0088] The timeout parameter indicates the timeout period expected by the application in this operation request. The device needs to provide a device timeout value, which can be understood as the timeout period expected by the device in this operation request, for two-way negotiation. Usually, when the device cannot perform the corresponding task operation within the timeout period specified by the application, it is considered that the task has timed out and the request has failed.

[0089] When setting the timeout value of the above-mentioned device, factors such as business needs, performance requirements, user experience, security and resource utilization can be considered, and the embodiments of the present application do not limit this.

[0090] In the embodiment of the present application, a two-way negotiation mechanism is established between the application and the device to ensure that the timeout settings of both parties are consistent. The device can return an acceptable timeout value based on its own capabilities and configuration, and the application can adjust the timeout value based on the device feedback and ensure that it matches the timeout set by the device.

[0091] In an optional implementation, the method for determining the timeout value of the above device includes:

[0092] Based on business needs and performance requirements, the above equipment is tested for performance, the average response time and maximum response time of the equipment under different operations are evaluated, and the equipment performance test results are obtained;

[0093] According to the performance test results of the above-mentioned equipment and the hardware limitations of the above-mentioned equipment, the timeout value of the above-mentioned equipment is set, and the timeout value of the above-mentioned equipment includes the equipment timeout value corresponding to different business requirements.

[0094] In an optional implementation manner, before performing a performance test on the device based on the business needs and performance requirements, the method further includes:

[0095] Evaluate the above business needs, including determining the time requirements for each operation in the above business processes;

[0096] Determine the above performance requirements, including determining the maximum response time of the equipment and the waiting time acceptable to the user.

[0097] To determine a reasonable device timeout period, you can take the following steps:

[0098] (1) Determine business needs and performance requirements

[0099] Assess business needs: Understand the time requirements for each operation in the business process, such as cash withdrawal, balance inquiry, etc.;

[0100] Determine performance requirements: Determine the maximum response time of the device and the acceptable wait time for users.

[0101] (2) Equipment Capability Assessment

[0102] Equipment performance test: Perform performance test on the equipment to evaluate the average response time and maximum response time of the equipment under different operations.

[0103] Hardware limitations: Understand the hardware limitations of the device, such as processor performance, memory size, etc., which will affect the response time of the device.

[0104] (3) Set a reasonable timeout period

[0105] Setting based on test results: According to the result of step (2), set a reasonable timeout period.

[0106] Consider redundancy: When setting the timeout period, allow for a certain amount of redundancy to account for network delays, device performance fluctuations, and other situations.

[0107] The application makes adjustments based on the timeout value fed back by the device through the above two-way negotiation mechanism to ensure that the timeout settings of both parties are consistent, that is, the timeout of the request (application timeout value) can be set to a reasonable timeout value on the device side.

[0108] The set timeout value of the device may include device timeout values ​​corresponding to different business requirements. In a specific application, when executing different business processing operations, the device may select a corresponding timeout value to feed back to the application.

[0109] In an optional implementation, the above method further includes:

[0110] Monitor the response time and timeouts of the above devices;

[0111] According to the monitoring results, the above application timeout value is dynamically adjusted.

[0112] In an optional implementation, a monitoring and adjustment function is provided. Specifically, a monitoring system can be established to monitor the device response time and timeout conditions, and based on the monitoring results, the timeout setting can be dynamically adjusted to adapt to changes in device performance and changes in business needs.

[0113] Through the above steps, the goal of matching the timeout time set by the application to send the request with the timeout time set by the device itself can be achieved. This helps improve system stability and user experience, while ensuring that device resources are used reasonably.

[0114] In an optional implementation, in subsequent processing, if the application sends the same request to the device, the timeout value adjusted last time can be used as the timeout parameter in the request and sent to the device. In this case, if the device detects that the timeout time is the same after negotiation, it can execute the corresponding operation request without further negotiation.

[0115] Optionally, except for negotiating the timeout period between the application and the SP, the rest of the startup process can use the existing process, and the embodiment of the present application does not limit this.

[0116] Usually, if the timeout set by the application request and the timeout set by the device itself do not match, the following consequences will occur:

[0117] 1. Request failed:

[0118] If the device's timeout is shorter than the timeout set by the application, the device might time out before completing the task, causing the request to fail.

[0119] If the device's timeout period is longer than the timeout period set by the application, the application may consider the task to have timed out before the device completes the task, which also causes the request to fail.

[0120] 2. Impaired user experience:

[0121] The user may need to wait longer to complete the operation, or the operation may be interrupted due to timeout, affecting the user experience.

[0122] Users may become frustrated by frequent timeout errors.

[0123] 3. Waste of resources:

[0124] Too long a timeout period may result in a waste of device and network resources.

[0125] If the device is idle while waiting for the application to time out, this may affect other users.

[0126] 4. Security issues:

[0127] If the timeout period is not set correctly, the device may be vulnerable for a long time.

[0128] A timeout period that is too long may allow the device to be exploited maliciously before the operation is completed.

[0129] 5. System performance degradation:

[0130] If the timeout period is not set properly, system performance may be degraded.

[0131] A timeout period that is too long may cause the device to occupy resources for a long time and affect the execution of other tasks.

[0132] 6. Fault recovery is difficult:

[0133] If the timeout period is not set correctly, it may affect the triggering of the fault recovery mechanism.

[0134] For example, if a device encounters a failure while processing a request, a reasonable timeout period can trigger a failure recovery mechanism, while an incompatible timeout period may result in delayed failure recovery.

[0135] 7. Increased difficulty in maintenance and management:

[0136] If the timeout settings are inconsistent, it may increase the difficulty of system maintenance and management.

[0137] Developers and operations staff need to spend more time troubleshooting.

[0138] 8. Data consistency issues:

[0139] If the timeout is not set correctly, data consistency issues may occur.

[0140] For example, in a distributed system, if the timeout of one node is inconsistent with other nodes, it may cause data synchronization problems.

[0141] 9. Service Interruption:

[0142] If the device and application timeouts do not match, this can result in service interruption.

[0143] For example, if a device encounters a failure while processing a request and it is not detected by the application in a timely manner, it may cause the service to be unavailable for a long time.

[0144] 10. System stability decreases:

[0145] Mismatched timeouts may cause system instability and increase the probability of failure.

[0146] The financial terminal application and SP timeout protocol negotiation method in the embodiment of the present application can achieve a timeout period that is agreed upon between the application and the device to ensure that the system can run stably and efficiently and avoid the occurrence of the above-mentioned problems.

[0147] See also Figure 2 , Figure 2 A flowchart of another method for negotiating a timeout protocol between a financial terminal application and an SP provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the method is applied to a device, which can be a financial terminal device, and the method includes:

[0148] 201. The device receives a request from an application, where the request carries a timeout parameter.

[0149] 202. The device sends the timeout value of the device to the application in response to the timeout parameter, where the timeout value is determined based on the device capability and configuration; the timeout value of the device is used by the application to adjust the application timeout value so that the application timeout value is consistent with the timeout value of the device.

[0150] In an optional implementation, the above method further includes:

[0151] Based on business needs and performance requirements, the above equipment is tested for performance, the average response time and maximum response time of the equipment under different operations are evaluated, and the equipment performance test results are obtained;

[0152] According to the performance test results of the above-mentioned equipment and the hardware limitations of the above-mentioned equipment, the timeout value of the above-mentioned equipment is set, and the timeout value of the above-mentioned equipment includes the equipment timeout value corresponding to different business requirements.

[0153] In an optional implementation manner, before sending the timeout value of the device to the application, the method further includes:

[0154] Determine the current business requirements and obtain the device timeout value corresponding to the current business requirements;

[0155] The device timeout value corresponding to the current business requirement is sent to the application.

[0156] Specifically, considering business needs, the time requirements for each operation in different business processes are different, such as cash withdrawal, balance inquiry, etc. Therefore, when setting the device timeout value, you can also set a reasonable timeout time for different business needs. Specifically, you can set the corresponding relationship between each operation and the timeout time value in the business process; in actual applications, you can determine the corresponding device timeout time value according to the current business needs and feed it back to the application for negotiation. At this time, you can set a reasonable timeout time for the current specific business operation, while meeting the device performance requirements.

[0157] The above steps 201 and 202 can also refer to Figure 1 The specific steps performed by the device in the illustrated embodiment will not be repeated here.

[0158] See also Figure 3 , Figure 3 A flowchart of another method for negotiating a timeout protocol between a financial terminal application and an SP provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, the method can be applied to a financial terminal application and an SP timeout protocol negotiation system, which may include interaction between an application program and a device; the method includes:

[0159] 301. The application initiates a request to the device, and the request carries a timeout parameter;

[0160] 302. The device receives the request, and in response to the timeout parameter, obtains a timeout value, where the timeout value is determined based on the device capability and configuration.

[0161] 303. The device sends a timeout value of the device to the application;

[0162] 304. The application receives the timeout value, and adjusts the application timeout value according to the timeout value of the device, so that the application timeout value is consistent with the timeout value of the device.

[0163] Among them, the above steps 301 to 304 can also refer to Figure 1 and Figure 2 The specific steps in the embodiment shown are not repeated here; for example, the above step 301 and the above step 304 can refer to Figure 1 and Figure 2 In the embodiment shown, the steps performed by the application program, the above step 302 and the above step 303 can refer to Figure 1 and Figure 2 The steps performed by the device in the illustrated embodiment.

[0164] For example, to make the timeout set by the application to send the request match the timeout set by the device itself, you can take the following steps to achieve this goal:

[0165] Step 1: Determine business needs and performance requirements

[0166] Assess business needs: Understand the time requirements for each operation in the business process, such as cash withdrawal, balance inquiry, etc.

[0167] Performance requirements: Determine the maximum response time of the device and the acceptable waiting time for users.

[0168] Step 2: Equipment Capability Assessment

[0169] Equipment performance test: Perform performance test on the equipment to evaluate the average response time and maximum response time of the equipment under different operations.

[0170] Hardware limitations: Understand the hardware limitations of the device, such as processor performance, memory size, etc., which will affect the response time of the device.

[0171] Step 3: Set a reasonable timeout

[0172] Set based on test results: According to the result of step 2, set a reasonable timeout period.

[0173] Consider redundancy: When setting the timeout period, allow for a certain amount of redundancy to account for network delays, device performance fluctuations, and other situations.

[0174] Step 4: Device Configuration and Application Communication

[0175] Device configuration: Configure a reasonable timeout period on the device.

[0176] Application communication: When an application communicates with a device, it should explicitly inform the device of the expected timeout.

[0177] Step 5: Two-way negotiation

[0178] Bidirectional negotiation mechanism: A bidirectional negotiation mechanism is established between the application and the device to ensure that the timeout settings of both parties are consistent.

[0179] Negotiation process: When the application initiates a request, it carries a timeout parameter; the device returns an acceptable timeout value based on its own capabilities and configuration.

[0180] Negotiation result: The application makes adjustments based on the timeout value fed back by the device and ensures that it matches the timeout value set by the device.

[0181] Step 6: Monitor and adjust

[0182] Monitoring system: Establish a monitoring system to monitor device response time and timeouts.

[0183] Dynamic adjustment: Based on monitoring results, dynamically adjust the timeout setting to adapt to changes in device performance and business needs.

[0184] Step 7: Error handling and failure recovery

[0185] Error handling: Design error handling mechanisms so that the application can handle the situation appropriately when the device fails to complete the task within the timeout period.

[0186] Failure recovery: Ensure that the system has failure recovery capabilities, such as being able to automatically retry after a timeout or prompting the user to retry manually.

[0187] Step 8: Documentation and Training

[0188] Documentation: Record the methods, steps, and results of timeout settings.

[0189] Training: Provide training to relevant personnel to ensure they understand the importance of timeout setting and the specific operation procedures.

[0190] Through the above steps, the goal of matching the timeout time set by the application to send the request with the timeout time set by the device itself can be achieved. This helps improve system stability and user experience, while ensuring that device resources are used reasonably.

[0191] It should be noted that the timeout value determined on the device side in the embodiment of the present application can be a fixed value determined based on manual evaluation and analysis, or a corresponding determination rule or model can be set to determine the timeout value of the device by analyzing the device capabilities, configuration, business requirements, etc., and real-time adjustments can also be made, etc. The embodiment of the present application does not limit this.

[0192] Optionally, the timeout value set on the device side is not absolute, and the timeout value stored in the device can be used as a reference time value and can be adjusted based on the reference time value. The reference time value is also a timeout value that can meet the corresponding business needs and device performance requirements. When receiving a request from an application, the target time value can be selected and fed back to the application based on the timeout parameter it carries. Specifically, the adjustment can be made based on the reference time value and the timeout parameter. The above reference time value can be a single value, multiple values, or a range of values. For example, the timeout parameter in the application request is 10s, and the range of the device reference time value is 10s-12s. The target time value can be set to 10s (at this time, the timeout does not need to be adjusted when fed back to the application), or 11s (it may be an optimal value determined considering various reasons, and at this time, it is fed back to the application and the timeout is adjusted by the application).

[0193] The specific negotiation methods involved in the above steps can also be found in Figure 1 and Figure 2 The corresponding description in the illustrated embodiment will not be repeated here.

[0194] The financial terminal application and SP timeout protocol negotiation method in the embodiment of the present application can achieve the following technical effects:

[0195] 1) Reduce the error rate of self-service equipment, improve the degree of automation, and increase the startup rate.

[0196] 2) Improved the adaptability of the upper-layer application software of self-service devices and SP middleware, and improved the reliability of cross-platform software.

[0197] 3) Improve the security and integrity of business process processing and reduce the probability of accounting errors caused by operations.

[0198] The reasons for the negotiation are listed below to further illustrate the effect of this application:

[0199] 1. Ensure compatibility:

[0200] Different devices have different hardware performance, and the time required to complete the same task may vary.

[0201] Negotiation can ensure that the timeout period set by the application matches the actual capabilities of the device, avoiding problems caused by improper timeout period settings.

[0202] 2. Optimize performance:

[0203] Devices and applications can dynamically adjust timeouts based on actual needs to achieve optimal performance.

[0204] For example, during peak hours you may want to set a shorter timeout to reduce waiting time, while during off-peak hours you may want to set a longer timeout to ensure task integrity.

[0205] 3. Improve user experience:

[0206] An appropriate timeout period can reduce user waiting time and improve user experience.

[0207] If the timeout is too long, users may become impatient; if it is too short, it may cause frequent timeout exceptions, affecting the user experience.

[0208] 4. Ensure safety:

[0209] When setting the timeout period, you need to consider security factors, such as avoiding long-term occupation of device resources and reducing potential security risks.

[0210] For example, a timeout period that is too long may leave the device vulnerable for a long period of time.

[0211] 5. Adapt to different business scenarios:

[0212] Different business scenarios may have different requirements for timeout periods.

[0213] For example, a simple query operation may require a shorter timeout, while a complex transfer operation may take a longer time.

[0214] 6. Improve fault tolerance:

[0215] A reasonable timeout period can be set through negotiation to ensure timely detection and remedial measures when a failure occurs.

[0216] For example, if a device encounters a problem that takes a long time to process, a reasonable timeout period can avoid unnecessary interruptions.

[0217] 7. Reduce resource waste:

[0218] Too long a timeout may result in a waste of resources, such as network bandwidth and CPU time.

[0219] Negotiating an appropriate timeout period can make more efficient use of resources.

[0220] 8. Enhance system stability:

[0221] Negotiation can ensure that the system can operate stably under various conditions.

[0222] For example, in the case of unstable network or degraded device performance, appropriate timeout period can ensure that the system does not crash due to frequent timeout exceptions.

[0223] 9. Support fault recovery:

[0224] An appropriate timeout period can help the system recover quickly when a failure occurs.

[0225] For example, if a device encounters a failure while processing a request, a reasonable timeout period can trigger a failure recovery mechanism to reduce the impact on users.

[0226] 10. Promote standardization:

[0227] Through negotiation, a set of standardized timeout setting schemes can be developed to facilitate management and maintenance.

[0228] This helps ensure consistency and interoperability across different devices and applications.

[0229] Based on the description of the above-mentioned financial terminal application and SP timeout protocol negotiation method embodiment, the embodiment of the present application also discloses a financial terminal application and SP timeout protocol negotiation system.

[0230] See also Figure 4 The structure diagram of a financial terminal application and SP timeout protocol negotiation system shown in the figure, wherein the financial terminal application and SP timeout protocol negotiation system 400 application module 410, SP module 420 and rule base module 430, wherein:

[0231] The application module 410 is used to initiate a request to the device, and the request carries a timeout parameter;

[0232] The SP module 420 is configured to receive the request and, in response to the timeout parameter, send a timeout value of the device to the application, where the timeout value is determined based on the device capability and configuration;

[0233] The application module 410 is further configured to receive a timeout value of the device, and adjust the application timeout value according to the timeout value of the device, so that the application timeout value is consistent with the timeout value of the device;

[0234] The rule base module 430 is used to store the negotiation rules between the application module 410 and the SP module 420 .

[0235] The rule base module 430 in the embodiment of the present application can store the rules for timeout negotiation between the application module 410 and the SP module 420, which may specifically include the negotiation process between the two parties, as well as setting and storing the rules for determining the device timeout value in the aforementioned embodiment, etc., which will not be repeated here.

[0236] According to one embodiment of the present application, Figure 1 , Figure 2 or Figure 3 Each step involved in the method shown can be performed by Figure 4 The financial terminal application and the SP timeout protocol negotiation system 400 shown are executed by various modules, for example, the application module 410 executes any steps executed by the application program in the aforementioned embodiment, and the SP module 420 executes any steps executed by the device in the aforementioned embodiment, which will not be repeated here.

[0237] Based on the description of the above method embodiment, the present application embodiment also provides an electronic device. Figure 5 The electronic device 500 at least includes a processor 501, an input device 502, an output device 503, and a computer storage medium 504. The processor 501, the input device 502, the output device 503, and the computer storage medium 504 in the electronic device may be connected via a bus or other means.

[0238] The electronic device 500 in the embodiment of the present application may be a financial terminal device, including but not limited to various types of financial self-service terminals, such as ATM devices. The computer storage medium 504 may be stored in the memory of the electronic device, and the computer storage medium 504 is used to store a computer program, and the computer program includes program instructions, and the processor 501 is used to execute the program instructions stored in the computer storage medium 504. The processor 501 (or CPU (Central Processing Unit)) is the computing core and control core of the electronic device, which is suitable for implementing one or more instructions, and is specifically suitable for loading and executing one or more instructions to implement corresponding method flows or corresponding functions; in one embodiment, the processor 501 in the embodiment of the present application may be used to perform a series of processes, including such as Figure 1 , Figure 2 or Figure 3 The method steps performed by the application program in the embodiment shown, or Figure 1 , Figure 2 or Figure 3 The method steps etc. executed by the device in the illustrated embodiment.

[0239] The embodiment of the present application also provides a computer storage medium (Memory), which is a memory device in an electronic device for storing programs and data. It is understandable that the computer storage medium here can include both built-in storage media in electronic devices and, of course, extended storage media supported by electronic devices. The computer storage medium provides a storage space that stores the operating system of the electronic device. In addition, one or more instructions suitable for being loaded and executed by the processor 501 are also stored in the storage space, and these instructions can be one or more computer programs (including program codes). It should be noted that the computer storage medium here can be a high-speed RAM memory, or a non-volatile memory, such as at least one disk storage; optionally, it can also be at least one computer storage medium located away from the aforementioned processor.

[0240] In one embodiment, the processor 501 may load and execute one or more instructions stored in a computer storage medium to implement the corresponding steps in the above embodiment; in a specific implementation, the processor 501 may load and execute one or more instructions in a computer storage medium as follows: Figure 1 , Figure 2 or Figure 3 The method steps performed by the application program in the embodiment shown, or Figure 1 , Figure 2 or Figure 3 The method steps and the like executed by the device in the illustrated embodiment will not be described in detail here.

[0241] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and modules can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0242] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the division of the module is only a logical function division, and there may be other division methods in actual implementation, for example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. The mutual coupling, direct coupling, or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0243] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0244] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrations. The available medium may be a read-only memory (ROM), or a random access memory (RAM), or a magnetic medium, such as a floppy disk, a hard disk, a tape, a magnetic disk, or an optical medium, such as a digital versatile disc (DVD), or a semiconductor medium, such as a solid state disk (SSD), etc.

Claims

1. A method for negotiating a timeout protocol between a financial terminal application and an SP, applied to an application program, characterized in that: include: Initiate a request to the device, the request carrying a timeout parameter; receiving a timeout value sent by the device in response to the timeout parameter, the timeout value being determined based on the device capability and configuration; The application timeout value is adjusted according to the timeout value of the device so that the application timeout value is consistent with the timeout value of the device.

2. The method according to claim 1, characterized in that The method for determining the timeout value of the device includes: Based on business needs and performance requirements, perform performance testing on the equipment, evaluate the average response time and maximum response time of the equipment under different operations, and obtain equipment performance test results; A timeout value of the device is set according to the device performance test result and the hardware limitation of the device, and the timeout value of the device includes device timeout values ​​corresponding to different business requirements.

3. The method according to claim 2, characterized in that Before performing a performance test on the device based on the business needs and performance requirements, the method further includes: Evaluate the business needs, including determining the time requirements for each operation in the business process; Determine the performance requirements, including determining the maximum response time of the device and the waiting time acceptable to the user.

4. The method according to claim 1, characterized in that: The method further comprises: monitoring the response time and timeouts of the device; According to the monitoring result, the application timeout value is dynamically adjusted.

5. A method for negotiating a timeout protocol between a financial terminal application and an SP, applied to a device, characterized in that: include: receiving a request from an application, wherein the request carries a timeout parameter; In response to the timeout parameter, the timeout value of the device is sent to the application, and the timeout value is determined based on the device capability and configuration; the timeout value of the device is used by the application to adjust the application timeout value so that the application timeout value is consistent with the timeout value of the device.

6. The method according to claim 5, characterized in that The method further comprises: Based on business needs and performance requirements, perform performance testing on the equipment, evaluate the average response time and maximum response time of the equipment under different operations, and obtain equipment performance test results; A timeout value of the device is set according to the device performance test result and the hardware limitation of the device, and the timeout value of the device includes device timeout values ​​corresponding to different business requirements.

7. The method according to claim 6, characterized in that Before sending the timeout value of the device to the application, the method further includes: Determine the current business demand, and obtain the device timeout value corresponding to the current business demand; Sending a device timeout value corresponding to the current service requirement to the application.

8. A method for negotiating a timeout protocol between a financial terminal application and an SP, characterized in that: include: The application initiates a request to the device, wherein the request carries a timeout parameter; The device receives the request, and in response to the timeout parameter, sends a timeout value of the device to the application, where the timeout value is determined based on the device capability and configuration; The application receives the timeout value of the device, and adjusts the application timeout value according to the timeout value of the device, so that the application timeout value is consistent with the timeout value of the device.

9. A financial terminal application and SP timeout protocol negotiation system, characterized in that: It includes application module, SP module and rule base module, among which: The application module is used to initiate a request to the device, wherein the request carries a timeout parameter; The SP module is configured to receive the request, and in response to the timeout parameter, send a timeout value of the device to the application, wherein the timeout value is determined based on the device capability and configuration; The application module is further used to receive a timeout value of the device, and adjust the application timeout value according to the timeout value of the device, so that the application timeout value is consistent with the timeout value of the device; The rule base module is used to store the timeout negotiation rules between the application module and the SP module.

10. An electronic device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the method for negotiating a timeout protocol between a financial terminal application and an SP according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: A computer program is stored, and when the computer program is executed by a processor, the processor executes the steps of the method for negotiating a timeout protocol between a financial terminal application and an SP according to any one of claims 1 to 8.

Images