Session processing method and device for enterprise mobile banking fault decoupling, and storage medium

Abstract

The invention discloses a session processing method and device for enterprise mobile banking fault decoupling and a storage medium. The method comprises the following steps: in response to a login interface request of an enterprise mobile banking of a client, a first electronic device verifies the login interface request; the user center creates a first session based on the login interface request, generates a verification token, and sends the verification token to the first electronic device; the first electronic equipment initiates a session creation request to the old E-bank system based on the verification token; the old online banking system creates a second session based on the session creation request, and sends the second session to the first electronic device so as to be used when the first electronic device performs the old online banking system transaction; and the first electronic equipment stores the second electronic equipment, the third session and the verification token, assigns the third session as the session of the first electronic equipment and feeds back a login result to the client, and the login result contains information of the third session. According to the invention, the creation success rate of the enterprise mobile banking session is improved.

Description

Technical Field

[0001] This application relates to the session processing technology for decoupling enterprise mobile banking failures, and particularly to a session processing method and device for decoupling enterprise mobile banking failures, as well as a storage medium. Background Art

[0002] Currently, session processing refers to the technology of identifying, understanding, responding to, and managing continuous conversation content during human-computer interaction or system-to-system communication. It is widely used in fields such as voice assistants, customer service systems, and chatbots. Its core lies in maintaining context coherence, accurately parsing user intentions, and generating responses that conform to the context to enhance the naturalness and efficiency of interaction. The current session creation logic of enterprise mobile banking uses Redis Session in the old BFF (Backend For Frontend) architecture. The current sessions of enterprise mobile banking are completely strongly coupled with the old BFF and the old Redis. In this way, if there is a failure in the three-party middleware or the old BFF under maintenance fails, it will cause login failures in enterprise mobile banking, affecting all customers of enterprise mobile banking. Summary of the Invention

[0003] This application provides a session processing method and device for decoupling enterprise mobile banking failures, as well as a storage medium, which can at least solve the aforementioned technical problems.

[0004] According to the first aspect of the embodiments of this application, a session processing method for decoupling enterprise mobile banking failures is provided, including: In response to a login interface request of an enterprise mobile banking from a client, a first electronic device verifies the login interface request; In response to passing the verification, the first electronic device forwards the login interface request to the user center; The user center creates a first session based on the login interface request, generates a verification token, and sends the verification token to the first electronic device; The first electronic device initiates a session creation request to the old online banking system based on the verification token; the old online banking system creates a second session based on the session creation request and sends the second session to the first electronic device for use when the first electronic device conducts transactions on the old online banking system; The first electronic device initiates a session creation request to a second electronic device. The second electronic device creates a third session, encapsulates the third session with the Yitong component, and stores it in the remote dictionary service Redis; The third session is sent to the first electronic device; The first electronic device stores the second electronic device, the third session, and the verification token, assigns the third session as the session of the first electronic device, and feeds back the login result to the client. The login result contains information about the third session.

[0005] As an implementation, the method further includes: Set a time window and the maximum allowable number of login interface requests. When a login interface request is received, compare the current timestamp with the timestamps recorded within the time window. If the number of requests within the window exceeds the maximum number of requests, discard the login interface request until the time window slides to the next time point, and then receive the login interface request again and perform the maximum number judgment.

[0006] As an implementation, the method further includes: The user center locally caches the created session information, sets a fixed survival time for each cache entry, and updates its most recently used time each time it is accessed. When the cache hits, directly return the session information in the cache; when the cache misses or has expired, pull the latest data again and update the cache.

[0007] As an implementation, the method further includes: During the process of initiating session creation between the first electronic device and the second electronic device, or during the process of initiating session creation between the first electronic device and the old banking system, capture the exception code during the operation of the handler through a Catch block, store the exception code in the Try block, and perform exception handling on the exception code in the Catch block to isolate the exceptions in the execution program, achieve exception release for session creation, and not interrupt the session creation process and subsequent related processing.

[0008] As an implementation, the method further includes: When detecting a failure in the old front-end customized back-end BFF architecture, call the interface of the user center to obtain the session information matching the current login interface request, cache the obtained session information; and return the session information to the first electronic device.

[0009] According to the second aspect of the embodiments of the present application, there is provided a session processing device for decoupling enterprise mobile banking failures, including: A verification unit, configured to, in response to a login interface request of the enterprise mobile banking of the client, the first electronic device verifies the login interface request; A forwarding unit, configured to, in response to passing the verification, trigger the first electronic device to forward the login interface request to the user center; A first creation unit, triggering the user center to create a first session based on the login interface request, generate a verification token, and send the verification token to the first electronic device; A second creation unit, in response to the first electronic device initiating a session creation request to the old online banking system based on a verification token, triggers the old online banking system to create a second session and send the second session to the first electronic device for use when the first electronic device conducts transactions on the old online banking system. A third creation unit, in response to the first electronic device initiating a session creation request to the second electronic device, the second electronic device creates a third session, encapsulates the third session with the Yitong component, and stores it in the remote dictionary service Redis. A sending unit for sending the third session to the first electronic device. An assignment unit triggers the first electronic device to store the second electronic device, the third session, and the verification token, assigns the third session as the session of the first electronic device, and feeds back a login result to the client, where the login result contains information about the third session.

[0010] As an implementation, the device further includes: A time limit control unit for setting a time window and the maximum allowable number of login interface requests. When a login interface request is received, it compares the current timestamp with the timestamps recorded within the time window. If the number of requests within the window exceeds the maximum number of requests, it discards the login interface request until the time window slides to the next time point, and then receives the login interface request again and makes a maximum number judgment.

[0011] As an implementation, the device further includes: A caching unit triggers the user center to locally cache the created session information, sets a fixed survival time for each cache entry, and updates its most recently used time each time it is accessed. When the cache hits, it directly returns the session information in the cache; when the cache misses or has expired, it fetches the latest data again and updates the cache.

[0012] As an implementation, the device further includes: A pass-through unit, during the process of initiating session creation between the first electronic device and the second electronic device, or during the process of initiating session creation between the first electronic device and the old banking system, captures the exception code during the operation of the handler through a Catch block, stores the exception code in a Try block, and performs exception handling on the exception code in the Catch block to isolate the exceptions in the execution program, achieving exception pass-through for session creation without interrupting the session creation process and subsequent related processing.

[0013] As an implementation, the device further includes: A calling unit, which is used to call an interface of a user center to obtain session information matching the current login interface request and cache the obtained session information when detecting a failure of an old front-end customized back-end BFF architecture; and return the session information to a first electronic device.

[0014] According to a third aspect of the embodiments of the present application, there is provided a non-transitory computer-readable storage medium, which enables an electronic device to execute the steps of the session processing method for decoupling enterprise mobile banking failures when instructions in the storage medium are executed by a processor of the electronic device.

[0015] The technical solutions provided by the embodiments of the present application may include the following beneficial effects: In the embodiments of the present application, by automatically switching to a session multiplexing mechanism when an old BFF fails and directly calling an interface of the user center to obtain session information, it is avoided that the entire enterprise mobile banking login function is paralyzed due to BFF or Redis failures, significantly improving the fault tolerance and operation stability of the system. The local cache mechanism is adopted to effectively reduce the frequent calls to the user center interface and avoid the excessive load of the interface caused by high-concurrency requests, thereby ensuring the overall performance and response speed of the system. By introducing a dynamic routing mechanism and a local cache alternative, Redis can be completely bypassed in the failure mode, reducing the strong dependence on Redis, improving the flexibility and maintainability of the system architecture, and avoiding the cascading failure problem caused by Redis failures.

[0016] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. Description of the Drawings

[0017] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application and used together with the specification to explain the principles of the present application.

[0018] Figure 1 It is a schematic flowchart of a session processing method for decoupling enterprise mobile banking failures shown in an embodiment of the present application; Figure 2 It is a schematic flowchart of a session processing method for decoupling enterprise mobile banking failures shown in an embodiment of the present application; Figure 3 It is a schematic composition structure diagram of a session processing device for decoupling enterprise mobile banking failures shown in an embodiment of the present application; Figure 4 It is a block diagram of an electronic device shown according to an exemplary embodiment. Detailed Embodiments

[0019] Exemplary embodiments will be described in detail herein, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0020] In terms of system architecture design, the embodiments of the present application adopt a hierarchical processing mechanism, separating the creation and verification processes of user sessions from the traditional BFF module and directly reusing the existing session information in the user center. When it is detected that the old mobile phone or old online banking BFF fails, the system automatically switches to the backup path, no longer creating a new session through the old BFF, but directly calling the user center interface to obtain the existing session information, and reducing the frequent access to the user center interface through the local cache mechanism. At the same time, to avoid data inconsistency problems caused by cache expiration or untimely updates, the system sets reasonable cache expiration times and refresh policies to ensure the effectiveness of the session verification function in high-concurrency scenarios.

[0021] Regarding the problem of strong coupling of the Redis middleware, the embodiments of the present application propose a decoupling design solution, migrating the session state information originally dependent on Redis storage to the local cache or other distributed storage components to reduce the dependence on Redis. In the normal operating state, the system can still be compatible with the original Redis-based session management method to ensure smooth transition and system compatibility.

[0022] Overall, the embodiments of the present application use key technical means such as session reuse, cache optimization, and middleware decoupling to enable the system to still operate stably in the event of a BFF failure, effectively control the access pressure of the user center interface, and improve the fault tolerance and resource utilization rate of the system.

[0023] The essence of the technical solution of the embodiments of the present application will be further elaborated through specific examples below.

[0024] Figure 1 The following is a schematic flowchart of a session processing method for decoupling enterprise mobile banking failures shown in the embodiments of the present application. As Figure 1 shown, the session processing method for decoupling enterprise mobile banking failures in the embodiments of the present application may include the following processing steps: Step 101, in response to a login interface request of the enterprise mobile banking of the client, the first electronic device verifies the login interface request.

[0025] The technical solution of the embodiment of the present application is mainly used in the enterprise mobile banking system. The enterprise mobile banking system uses the Internet as a medium to provide self-service financial services for enterprises or peer institutions. It is suitable for a large number of small and medium-sized enterprise customers who need to have real-time access to account and financial information and do not involve fund transfers in and out. After the customer opens the enterprise telephone banking or applies for the enterprise ordinary card certificate at the branch, he can register for the enterprise online banking at the counter or online. The verification of the embodiment of the present application is mainly based on the ID of the first electronic device, and the identity information of the first electronic device is verified to determine its identity and access rights. The first electronic device can be a new mobile phone device.

[0026] Step 102: In response to the verification being passed, the first electronic device forwards the login interface request to the user center.

[0027] Step 103: The user center creates a first session based on the login interface request, generates a verification token, and sends the verification token to the first electronic device.

[0028] In an embodiment of the present application, a time window and a maximum number of allowed login interface requests are set. When a login interface request is received, the current timestamp is compared with the timestamp recorded in the time window. If the number of requests in the window exceeds the maximum number of requests, the login interface request is discarded until the time window slides to the next time point, the login interface request is received again and the maximum number is determined.

[0029] The user center locally caches the created session information, sets a fixed expiration time for each cache entry, and updates its most recent usage time on each access. When the cache hits, the session information in the cache is directly returned; when the cache misses or has expired, the latest data is pulled again and the cache is updated.

[0030] In step 104, the first electronic device initiates a session creation request to the old online banking system based on the verification token; the old online banking system creates a second session based on the session creation request and sends the second session to the first electronic device for use when the first electronic device conducts transactions in the old online banking system.

[0031] In step 105, the first electronic device initiates a session creation request to the second electronic device. The second electronic device creates a third session, encapsulates the third session with the Yitong component, and stores it in the remote dictionary service Redis.

[0032] In an embodiment of the present application, when a failure of the old front-end customized back-end BFF architecture is detected, the interface of the user center is called to obtain session information that matches the current login interface request, the obtained session information is cached; and the session information is returned to the first electronic device.

[0033] Step 106: Send the third conversation to the first electronic device; Step 107, the first electronic device stores the second electronic device, the third session, and the authentication token, assigns the third session to the session of the first electronic device, and feeds back the login result to the client. The login result contains the information of the third session.

[0034] In the embodiments of the present application, data processing mainly focuses on the acquisition, caching, and verification of user session information. The system obtains the user's session information by calling the user center interface. The data format returned by this interface is in JSON structure, including keyword fields such as user ID, session token, creation time, expiration time, etc. To ensure data consistency and availability, after obtaining the original data, the system will perform data cleaning operations, including removing invalid characters, verifying field integrity, filtering illegal requests, etc. In addition, the system uses a sliding window algorithm based on a time window to control the access frequency, avoiding a large number of requests in a short time from impacting the user center interface. Specifically, the system sets a time window length T = 60 seconds and a maximum allowable request number N = 100. Whenever a session request is received, the system compares the current timestamp with the timestamps recorded within the window. If the number of requests within the window exceeds N, subsequent requests will be rejected until the window slides to the next time point. This mechanism can effectively control the access frequency to the user center interface per unit time and prevent the interface load from being too high due to sudden traffic.

[0035] Meanwhile, the system locally caches the obtained session information. The caching policy adopts the LRU (Least Recently Used) algorithm, combined with the TTL (Time to Live) expiration mechanism. Each cache entry is set with a fixed survival time TTL = 300 seconds, and its most recently used time is updated each time it is accessed. When the cache is hit, the session information in the cache is directly returned; when the cache is not hit or has expired, the latest data is pulled from the user center interface again and the cache is updated.

[0036] The core system architecture of the embodiments of the present application adopts a layered design, mainly including a front-end access layer, a session management middle layer, a user center interface layer, a cache layer, and a Redis decoupling layer. Communication between each layer is carried out through standardized interfaces to achieve modularization and decoupling.

[0037] The front-end access layer is responsible for receiving requests from the client and determining whether it is a scenario of an old mobile phone or an old online banking BFF failure. The judgment logic is based on a preset fault detection mechanism, such as heartbeat detection failure, service response timeout, error code matching, etc. Once it is confirmed as a fault state, the system automatically switches to the backup path and no longer creates a new session through the old BFF.

[0038] The session management middle layer is a key part of the embodiments of this application. Its core function is to achieve session reuse and cache control. The session verification logic is encapsulated inside this layer, supporting two modes: normal mode and failure mode. Normal mode: When the old BFF runs normally, the system continues to follow the original process, creates a session through the BFF, and stores the session information in Redis. Failure mode: When it is detected that the old BFF fails, the system skips the BFF and directly calls the user center interface to obtain the existing session information, and reduces the access pressure on the user center through the local cache mechanism.

[0039] The user center interface layer provides a unified session query interface for obtaining the session information of users. This interface supports multiple parameter inputs, including user ID, device type, login time range, etc., and the output result is the JSON format data mentioned above.

[0040] The cache layer combines local memory cache and distributed cache. The local cache is used to quickly respond to high-frequency requests, and the distributed cache (such as Redis) is used as a backup storage for sharing session information across nodes. However, in the embodiments of this application, the system can completely bypass Redis in the failure mode through a configuration switch and only rely on the local cache, thereby achieving decoupling from Redis.

[0041] To reduce the strong dependence on Redis, the embodiments of this application introduce a dynamic routing mechanism to decide whether to use Redis according to the current system state. In the normal running state, the system is still compatible with the original Redis storage method; while in the case of failure or high load, the system automatically switches to the local cache or other distributed storage components (such as HBase, Cassandra, etc.) to ensure the stability and availability of the system.

[0042] In the initial stage of system deployment, all requests create sessions through the old BFF and store the session information in Redis. At this time, the system is in the normal mode, the access volume of the user center interface is low, and Redis undertakes the main session storage task.

[0043] Figure 2 A schematic flow diagram of a session processing method for decoupling enterprise mobile banking failures shown in the embodiments of this application, as Figure 2 shown, the session processing method for decoupling enterprise mobile banking failures in the embodiments of this application includes the following processing steps: The front end sends a login interface request to the new mobile phone. The new mobile phone verifies the identity of the front-end user. After successful verification, it sends a login interface request to the user center, creates a session and returns a token (tokeEO) to the new mobile phone. The new mobile phone sends a session creation request to the old online banking. The old online banking creates a session and returns the session created by the old online banking to the new mobile phone. The new mobile phone sends a session creation request to the old mobile phone. The old mobile phone creates a session, encapsulates the created session using the Yitong component, stores it in Redis, and returns the session information created by the old mobile phone to the new mobile phone. The new mobile phone stores the session information of the old mobile phone, the old online banking, and the tokeEO of the user center, and assigns the session created by the old mobile phone to the new mobile phone. The encapsulation of the Spring boot framework is implemented. The new mobile phone returns the login result to the front end, and the login result contains session information.

[0044] As an example, the Yitong component in the embodiments of the present application includes cells such as key values, session attribute-related information, creation time, and last access time.

[0045] As an example, the session of the Spring boot framework in the embodiments of the present application includes cells such as correct update identification, offline Redis key values, etc.

[0046] When the system detects a failure of the old BFF (such as heartbeat failure, response timeout, etc.), the system automatically switches to the failure mode. At this time, the system no longer creates a new session through the old BFF, but directly calls the user center interface to obtain the existing session information. To reduce the pressure on the user center interface, the embodiments of the present application adopt a local cache mechanism, cache the obtained session information in the local memory, and set a reasonable TTL (such as 300 seconds, etc.). For frequently accessed session information, the system also uses the LRU algorithm for cache eviction to ensure the effective use of the cache space.

[0047] In the failure mode, the system also supports a hybrid mode, that is, under certain specific conditions (such as cache miss, cache expiration, etc.), the system can still temporarily access Redis, but preferentially use the local cache. This design not only ensures the stability of the system but also reduces the dependence on Redis.

[0048] In addition, the system supports a smooth transition mechanism, that is, after the old BFF is restored, the system can automatically switch back to the normal mode, continue to create sessions through the old BFF, and gradually synchronize the session information in the cache to Redis to ensure data consistency.

[0049] In summary, through the introduction of a session multiplexing mechanism, a cache optimization strategy, and a Redis decoupling design, the embodiments of the present application enable the system to still operate stably when the old BFF fails. At the same time, the access pressure on the user center interface is effectively controlled, and the fault tolerance and resource utilization rate of the system are improved.

[0050] Figure 3 It is a schematic structural diagram of the session processing device for decoupling enterprise mobile banking failures shown in the embodiments of the present application. As Figure 3 shown, the session processing device for decoupling enterprise mobile banking failures in the embodiments of the present application includes: A verification unit 30, configured to, in response to a login interface request of the enterprise mobile banking of the client, the first electronic device verifies the login interface request; A forwarding unit 31, configured to, in response to passing the verification, trigger the first electronic device to forward the login interface request to the user center; A first creation unit 32, triggering the user center to create a first session based on the login interface request, generating a verification token, and sending the verification token to the first electronic device; A second creation unit 33, in response to the first electronic device initiating a session creation request to the old online banking system based on the verification token; triggering the old online banking system to create a second session based on the session creation request, and sending the second session to the first electronic device for use when the first electronic device conducts transactions on the old online banking system; A third creation unit 34, in response to the first electronic device initiating a session creation request to the second electronic device, the second electronic device creates a third session, performs Yitong component encapsulation on the third session, and stores it in the remote dictionary service Redis; A sending unit 35, configured to send the third session to the first electronic device; An assignment unit 36, triggering the first electronic device to store the second electronic device, the third session, and the verification token, and assign the third session as the session of the first electronic device, and feed back the login result to the client, where the login result includes information about the third session.

[0051] As an implementation, the session processing device for decoupling enterprise mobile banking failures in the embodiments of the present application further includes: A time limit control unit ( Figure 3 not shown in the figure), configured to set a time window and the maximum allowable number of login interface requests. When a login interface request is received, compare the current timestamp with the timestamps recorded within the time window. If the number of requests within the window exceeds the maximum number of requests, discard the login interface request until the time window slides to the next time point, and then receive the login interface request again and perform the maximum number judgment.

[0052] As an implementation manner, the session processing device for decoupling enterprise mobile banking faults in the embodiments of the present application further includes: A cache unit ( Figure 3 not shown in the figure) that triggers the user center to locally cache the created session information, sets a fixed survival time for each cache entry, and updates its most recently used time each time it is accessed. When the cache hits, the session information in the cache is directly returned; when the cache misses or has expired, the latest data is pulled again and the cache is updated.

[0053] As an implementation manner, the session processing device for decoupling enterprise mobile banking faults in the embodiments of the present application further includes: A pass-through unit ( Figure 3 not shown in the figure) that, during the process of initiating session creation between the first electronic device and the second electronic device or between the first electronic device and the old banking system, captures the exception code during the operation of the processing program through a Catch block, stores the exception code in a Try block, and performs exception handling on the exception code in the Catch block to isolate the exception in the execution program, implement exception pass-through for session creation, and not interrupt the session creation process and subsequent related processing.

[0054] As an implementation manner, the session processing device for decoupling enterprise mobile banking faults in the embodiments of the present application further includes: An invocation unit ( Figure 3 not shown in the figure) that, when detecting a fault in the old front-end customized back-end BFF architecture, invokes the interface of the user center to obtain the session information matching the current login interface request, caches the obtained session information; and returns the session information to the first electronic device.

[0055] In an exemplary embodiment, each of the above processing units and the like may be implemented by one or more central processing units (CPUs), graphics processing units (GPUs), baseband processors (BPs), application specific integrated circuits (ASICs), digital signal processors (DSPs), programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general purpose processors, controllers, microcontroller units (MCUs), microprocessors, or other electronic components.

[0056] In an embodiment of the present application, Figure 3 The specific manners in which the respective units in the illustrated session processing apparatus for decoupling enterprise mobile banking failures perform operations have been described in detail in the embodiments related to the method, and will not be elaborated herein.

[0057] Figure 4 is a block diagram of an electronic device shown according to an exemplary embodiment. The electronic device 800 is intended to represent various forms of digital computers, such as, for example, laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as, personal digital assistants, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely exemplary and are not intended to limit the implementation of the present application described and / or claimed herein.

[0058] As Figure 4As shown, the electronic device 800 includes a computing unit 801, which can perform various appropriate actions and processes according to computer programs stored in a read-only memory (ROM) 802 or computer programs loaded from a storage unit 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the electronic device 800 can also be stored. The computing unit 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0059] Multiple components in the electronic device 800 are connected to the I / O interface 805, including: an input unit 806, such as a keyboard, a mouse, etc.; an output unit 807, such as various types of displays, speakers, etc.; a storage unit 808, such as a magnetic disk, an optical disc, etc.; and a communication unit 809, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 809 allows the electronic device 800 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0060] The computing unit 801 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include but are not limited to a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The computing unit 801 executes the various methods and processes described above, such as the session processing method for decoupling faults in enterprise mobile banking. For example, in some embodiments, the session processing method for decoupling faults in enterprise mobile banking can be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as the storage unit 808. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 800 via the ROM 802 and / or the communication unit 809. When the computer program is loaded into the RAM 803 and executed by the computing unit 801, one or more steps of the session processing method for decoupling faults in enterprise mobile banking described above can be executed. Alternatively, in other embodiments, the computing unit 801 can be configured as the session processing method for decoupling faults in enterprise mobile banking by any other appropriate means (e.g., by means of firmware).

[0061] The various embodiments of the systems and techniques described above in this specification can be implemented in digital electronic circuitry, integrated circuit systems, field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), application specific standard products (ASSP), system on a chip (SOC), complex programmable logic devices (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include: being implemented in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be a special-purpose or general-purpose programmable processor that receives data and instructions from, and transmits data and instructions to, a storage system, at least one input device, and at least one output device.

[0062] The program code for implementing the methods of this application can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing device, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowchart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package partially on the machine and partially on a remote machine, or entirely on the remote machine or server.

[0063] In the context of this application, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0064] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, speech input, or tactile input).

[0065] The systems and techniques described herein can be implemented in a computing system including backend components (e.g., as a data server), or a computing system including middleware components (e.g., an application server), or a computing system including frontend components (e.g., a user computer having a graphical user interface or a web browser through which the user can interact with an implementation of the systems and techniques described herein), or a computing system including any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected to each other by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local area network (LAN), wide area network (WAN), and the Internet.

[0066] A computer system can include a client and a server. The client and the server are generally far from each other and typically interact through a communication network. The relationship between the client and the server is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, can also be a server of a distributed system, or a server incorporating a blockchain.

[0067] It should be understood that various forms of the processes shown above can be used, with steps reordered, added, or deleted. For example, the steps recited in this disclosure can be executed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in this application can be achieved, and no limitations are set herein.

[0068] In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first" and "second" can explicitly or implicitly include at least one such feature. In the description of this application, "a plurality" means two or more unless otherwise specifically defined.

[0069] As described above, it is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A session processing method for decoupling enterprise mobile banking failures, characterized in that, The method comprises: In response to the client's corporate mobile banking login interface request, the first electronic device verifies the login interface request; In response to the verification being passed, the first electronic device forwards the login interface request to the user center; The user center creates a first session based on the login interface request, generates a verification token, and sends the verification token to the first electronic device; The first electronic device initiates a session creation request to the old online banking system based on the verification token; the old online banking system creates a second session based on the session creation request and sends the second session to the first electronic device for use when the first electronic device conducts transactions in the old online banking system; The first electronic device initiates a session creation request to the second electronic device, and the second electronic device creates a third session, encapsulates the third session into components, and stores the components in the remote dictionary service Redis. sending the third conversation to the first electronic device; The first electronic device stores the second electronic device, the third session, and the verification token, assigns the third session to the session of the first electronic device, and feeds back a login result to the client, the login result including information about the third session.

2. The method according to claim 1, wherein The method further comprises: Set the time window and the maximum number of login interface requests allowed. When a login interface request is received, compare the current timestamp with the timestamp recorded in the time window. If the number of requests in the window exceeds the maximum number of requests, discard the login interface request until the time window slides to the next time point, receive the login interface request again, and determine the maximum number.

3. The method according to claim 1, characterized in that, The method further comprises: The user center locally caches the created session information, sets a fixed expiration time for each cache entry, and updates its most recent usage time on each access. When the cache hits, the session information in the cache is directly returned; when the cache misses or has expired, the latest data is pulled again and the cache is updated.

4. The method according to claim 2 or 3, characterized in that, The method further comprises: In the process of initiating the creation of a session between the first electronic device and the second electronic device, or in the process of initiating the creation of a session between the first electronic device and the old bank system, the exception code in the process of processing the program is captured by the Catch block, the exception code is stored in the Try block, and the exception code is handled in the Catch block to isolate the exception in the execution program, realize the exception handling of the session creation, and do not interrupt the session creation process and subsequent related processing.

5. The method according to claim 4, wherein The method further comprises: When a failure of the old front-end customized back-end BFF architecture is detected, the user center interface is called to obtain session information matching the current login interface request, the obtained session information is cached, and the session information is returned to the first electronic device.

6. A session processing device for decoupling enterprise mobile banking failures, characterized in that, The device comprises: a verification unit, configured to respond to a login interface request for corporate mobile banking from a client, and verify the login interface request by the first electronic device; a forwarding unit, configured to trigger the first electronic device to forward the login interface request to the user center in response to the verification being passed; A first creation unit triggers the user center to create a first session based on a login interface request, generates a verification token, and sends the verification token to the first electronic device; A second creation unit, in response to the first electronic device initiating a session creation request to the old online banking system based on a verification token, triggers the old online banking system to create a second session based on the session creation request, and sends the second session to the first electronic device for use when the first electronic device conducts transactions on the old online banking system; A third creation unit, in response to the first electronic device initiating a session creation request to the second electronic device, the second electronic device creates a third session, performs component encapsulation on the third session, and stores it in the remote dictionary service Redis; A sending unit, configured to send the third session to the first electronic device; An assignment unit, triggers the first electronic device to store the second electronic device, the third session, and the verification token, assigns the third session as the session of the first electronic device, and feeds back a login result to the client, where the login result includes information about the third session.

7. The device according to claim 6, characterized in that, The apparatus further includes: A time limit control unit, configured to set a time window and the maximum allowed number of login interface requests. When a login interface request is received, compare the current timestamp with the timestamps recorded within the time window. If the number of requests within the window exceeds the maximum number of requests, discard the login interface request until the time window slides to the next time point, and then receive the login interface request again and perform the maximum number judgment.

8. The device according to claim 6, characterized in that, The apparatus further includes: A caching unit, triggers the user center to perform local caching on the created session information, sets a fixed survival time for each cache entry, and updates its most recently used time each time it is accessed. When the cache is hit, directly return the session information in the cache; when the cache is not hit or has expired, pull the latest data again and update the cache.

9. The device according to claim 7 or 8, characterized in that The apparatus further includes: A pass-through unit, during the process of initiating session creation between the first electronic device and the second electronic device, or during the process of initiating session creation between the first electronic device and the old banking system, captures the exception code during the operation of the handler through a Catch block, stores the exception code in the Try block, and performs exception handling on the exception code in the Catch block to isolate the exceptions in the execution program, achieve exception pass-through for session creation, and do not interrupt the session creation process and subsequent related processing.

10. A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by a processor of an electronic device, enable the electronic device to execute the steps of the session processing method for decoupling enterprise mobile banking failures according to any one of claims 1 to 5.

Images