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

Abstract

The present application discloses a session processing method, device, and storage medium for fault decoupling of enterprise mobile banking. The method includes: in response to a login interface request of the 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 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 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 the login result to the client, wherein the login result includes information about the third session. The present application improves the success rate of creating enterprise mobile banking sessions.

Description

Technical Field

[0001] The present application relates to a session processing technology for enterprise mobile banking fault decoupling, and in particular to a session processing method, device, and storage medium for enterprise mobile banking fault decoupling. Background Art

[0002] Currently, session processing refers to the technology used to identify, understand, respond to, and manage continuous conversational content during human-computer interaction or inter-system communication. It is widely used in voice assistants, customer service systems, chatbots, and other fields. Its core focus is to maintain contextual consistency, accurately interpret user intent, and generate contextually appropriate responses to enhance the naturalness and efficiency of interactions. The current session creation logic for enterprise mobile banking, in the legacy BFF (Backend for Frontend) architecture, uses Redis sessions. Current enterprise mobile banking sessions are tightly coupled to the legacy BFF and legacy Redis. Consequently, failures in the third-party middleware or the legacy BFF during maintenance can cause login issues for enterprise mobile banking, impacting all enterprise mobile banking customers. Summary of the Invention

[0003] The present application provides a session processing method and device, and a storage medium for fault decoupling of enterprise mobile banking, which can at least solve the aforementioned technical problems.

[0004] According to a first aspect of an embodiment of the present application, a method for session processing with fault decoupling for enterprise mobile banking is provided, comprising:

[0005] In response to the client's corporate mobile banking login interface request, the first electronic device verifies the login interface request;

[0006] In response to the verification being passed, the first electronic device forwards the login interface request to the user center;

[0007] 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;

[0008] 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;

[0009] 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 with the Yitong component, and stores it in the remote dictionary service Redis;

[0010] sending the third conversation to the first electronic device;

[0011] 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.

[0012] As an implementation mode, the method further includes:

[0013] 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.

[0014] As an implementation mode, the method further includes:

[0015] 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.

[0016] As an implementation mode, the method further includes:

[0017] 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.

[0018] As an implementation mode, the method further includes:

[0019] 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.

[0020] According to a second aspect of an embodiment of the present application, a session processing device for enterprise mobile banking fault decoupling is provided, comprising:

[0021] 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;

[0022] 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;

[0023] 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;

[0024] A second creation unit, in response to the first electronic device initiating a session creation request to the old online banking system based on the 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 in the old online banking system;

[0025] A third creating unit, in response to the first electronic device initiating a session creation request to the second electronic device, the second electronic device creating a third session, performing Yitong component encapsulation on the third session, and storing the third session in a remote dictionary service Redis;

[0026] a sending unit, configured to send the third conversation to the first electronic device;

[0027] The assignment unit triggers the first electronic device to store 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.

[0028] As an implementation method, the device further includes:

[0029] The time limit control unit is used to set the time window and the maximum number of login interface requests allowed. 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, and the login interface request is received again and the maximum number is determined.

[0030] As an implementation method, the device further includes:

[0031] The cache unit triggers the user center to locally cache 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.

[0032] As an implementation method, the device further includes:

[0033] The release unit is used to capture the exception code 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, through the Catch block, store the exception code in the Try block, and perform exception processing on the exception code in the Catch block to isolate the exception in the execution program, realize the exception release of the session creation, and do not interrupt the session creation process and subsequent related processing.

[0034] As an implementation method, the device further includes:

[0035] The calling unit is used to call the interface of the user center to obtain session information matching the current login interface request when detecting a failure of the old front-end customized back-end BFF architecture, cache the obtained session information; and return the session information to the first electronic device.

[0036] According to the third aspect of the embodiment of the present application, a non-temporary computer-readable storage medium is provided. When the instructions in the storage medium are executed by the processor of an electronic device, the electronic device is enabled to perform the steps of the session processing method for fault decoupling of corporate mobile banking.

[0037] The technical solutions provided by the embodiments of the present application may have the following beneficial effects:

[0038] In the embodiment of the present application, by automatically switching to the session reuse mechanism when the old BFF fails and directly calling the user center interface to obtain session information, the paralysis of the entire enterprise mobile banking login function due to BFF or Redis failure is avoided, and the fault tolerance and operational stability of the system are significantly improved. The local cache mechanism is adopted to effectively reduce the frequent calls to the user center interface and avoid excessive interface load due to high concurrent 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 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 failure.

[0039] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0041] Figure 1 This is a flow chart of a method for session processing with fault decoupling for enterprise mobile banking according to an embodiment of the present application;

[0042] Figure 2 This is a flow chart of a method for session processing with fault decoupling for enterprise mobile banking according to an embodiment of the present application;

[0043] Figure 3 A schematic diagram of the structure of a session processing device for enterprise mobile banking fault decoupling according to an embodiment of the present application;

[0044] Figure 4 It is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0045] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0046] In terms of system architecture design, the embodiment of the present application adopts a layered processing mechanism to separate the user session creation and verification process from the traditional BFF module and directly reuse the existing session information of the user center. When a failure is detected in the old mobile phone or old online banking BFF, the system automatically switches to the backup path and no longer creates a new session through the old BFF. Instead, it directly calls the user center interface to obtain the existing session information and reduces frequent access to the user center interface through the local cache mechanism. At the same time, in order to avoid data inconsistency problems caused by cache failure or untimely updates, the system sets a reasonable cache expiration time and refresh strategy to ensure that the effectiveness of the session verification function can be maintained in high-concurrency scenarios.

[0047] To address the issue of tight coupling with Redis middleware, this application proposes a decoupling design solution that migrates session state information, previously stored in Redis, to a local cache or other distributed storage component, reducing reliance on Redis. Under normal operating conditions, the system remains compatible with the existing Redis-based session management method, ensuring a smooth transition and system compatibility.

[0048] Overall, the embodiments of the present application achieve stable operation of the system in the event of a BFF failure through key technical means such as session reuse, cache optimization, and middleware decoupling, while effectively controlling the access pressure of the user center interface and improving the system's fault tolerance and resource utilization.

[0049] The essence of the technical solution of the embodiment of the present application is further explained below through specific examples.

[0050] Figure 1 This is a flow chart of a method for processing a session with fault decoupling for enterprise mobile banking according to an embodiment of the present application. Figure 1 As shown, the session processing method for enterprise mobile banking fault decoupling according to the embodiment of the present application may include the following processing steps:

[0051] Step 101: In response to a login interface request for corporate mobile banking from a client, a first electronic device verifies the login interface request.

[0052] 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.

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

[0054] 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.

[0055] 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.

[0056] 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.

[0057] 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.

[0058] 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.

[0059] 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 matching the current login interface request, the obtained session information is cached; and the session information is returned to the first electronic device.

[0060] Step 106: Send the third conversation to the first electronic device;

[0061] In step 107 , 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.

[0062] In the embodiments of this application, data processing primarily revolves around the acquisition, caching, and verification of user session information. The system retrieves user session information by calling a user-centric interface. The data returned by this interface is formatted as a JSON structure and contains key fields such as the user ID, session token, creation time, and expiration time. To ensure data consistency and availability, after acquiring the raw data, the system performs data cleansing operations, including removing invalid characters, verifying field integrity, and filtering out illegal requests. Furthermore, the system uses a sliding window algorithm based on a time window to control access frequency, preventing a large number of requests from overwhelming the user-centric interface within a short period of time. Specifically, the system sets a time window length of T = 60 seconds and a maximum number of requests allowed, N = 100. Whenever a session request is received, the system compares the current timestamp with the timestamps already recorded within the window. If the number of requests within the window exceeds N, subsequent requests are rejected until the window slides to the next time point. This mechanism effectively controls the frequency of access to the user-centric interface per unit time, preventing excessive interface load caused by sudden traffic.

[0063] The system also caches the acquired session information locally, using an LRU (Least Recently Used) algorithm combined with a TTL (Time to Live) expiration mechanism. Each cache entry has a fixed TTL of 300 seconds, and its last used time is updated with each access. If a cache hit occurs, the session information in the cache is directly returned. If a cache miss occurs or the session has expired, the latest data is retrieved from the user center interface and the cache is updated.

[0064] The core system architecture of the embodiment 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. The layers communicate through standardized interfaces to achieve modularization and decoupling.

[0065] The front-end access layer is responsible for receiving client requests and determining whether the failure scenario involves a legacy mobile phone or legacy online banking BFF. This determination is based on pre-defined fault detection mechanisms, such as heartbeat failure, service response timeout, and error code matching. Once a failure is confirmed, the system automatically switches to a backup path and no longer creates new sessions through the legacy BFF.

[0066] The session management middle layer is a key part of the embodiment of the present application, and its core function is to realize session reuse and cache control. This layer encapsulates the session verification logic and supports two modes: normal mode and fault mode. Normal mode: When the old BFF is running normally, the system continues to use the original process, creates sessions through BFF, and stores session information in Redis. Fault mode: When the old BFF failure is detected, the system skips the BFF and directly calls the user center interface to obtain existing session information, and reduces the access pressure to the user center through the local cache mechanism.

[0067] The user-centric interface layer provides a unified session query interface for obtaining user session information. This interface supports multiple parameter inputs, including user ID, device type, login time range, etc., and outputs the data in the JSON format mentioned above.

[0068] The cache layer uses a combination of local memory cache and distributed cache. The local cache is used to quickly respond to high-frequency requests, while the distributed cache (such as Redis) serves as a backup store for sharing session information across nodes. However, in this embodiment of the application, the system can completely bypass Redis in failure mode by configuring a switch, relying solely on the local cache, thereby achieving decoupling from Redis.

[0069] To reduce the heavy reliance on Redis, this embodiment introduces a dynamic routing mechanism that determines whether to use Redis based on the current system state. Under normal operating conditions, the system remains compatible with the existing Redis storage method; however, in the event of a failure or high load, the system automatically switches to local cache or other distributed storage components (such as HBase, Cassandra, etc.) to ensure system stability and availability.

[0070] In the early stages of system deployment, all requests created sessions through the old BFF and stored session information in Redis. At this time, the system was in normal mode, with low traffic to the user center interface, and Redis was primarily responsible for session storage.

[0071] Figure 2 This is a flow chart of a method for processing a session with fault decoupling for enterprise mobile banking according to an embodiment of the present application. Figure 2 As shown, the session processing method for enterprise mobile banking fault decoupling in the embodiment of the present application includes the following processing steps:

[0072] The front-end initiates a login interface request to the new phone. The new phone verifies the identity of the front-end user and, after the verification is passed, initiates a login interface request to the user center, creates a session, and returns a token (tokeEO) to the new phone. The new phone initiates 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 phone. The new phone initiates a session creation request to the old phone. The old phone creates a session, uses the Yitong component to encapsulate the created session, stores it in Redis, and returns the session information created by the old phone to the new phone. The new phone stores the old phone, the old online banking session information, and the tokeEO of the user center, and assigns the session created by the old phone to the new phone. Implement the encapsulation of the Spring boot framework. The new phone returns the login result to the front-end, which contains the session information.

[0073] As an example, the Yitong component of an embodiment of the present application includes information elements such as key values, session attribute related information, creation time, and last access time.

[0074] As an example, the session of the Spring boot framework in the embodiment of the present application includes information elements such as the correct update identifier and the offline Redis key value.

[0075] When the system detects a failure in the old BFF (e.g., heartbeat failure, response timeout, etc.), it automatically switches to failure mode. At this point, the system no longer creates a new session through the old BFF, but instead directly calls the user-centric interface to retrieve existing session information. To reduce the pressure on the user-centric interface, the present embodiment employs a local caching mechanism to cache acquired session information in local memory and sets a reasonable TTL (e.g., 300 seconds). For frequently accessed session information, the system also uses a LRU algorithm to eliminate cache entries, ensuring efficient use of cache space.

[0076] In failure mode, the system also supports a hybrid mode. That is, under certain conditions (such as cache misses and cache expiration), the system can still temporarily access Redis, but prioritizes using the local cache. This design ensures system stability while reducing dependence on Redis.

[0077] In addition, the system supports a smooth transition mechanism, that is, after the old BFF is restored, the system can automatically switch back to 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.

[0078] To sum up, the embodiment of the present application introduces a session reuse mechanism, a cache optimization strategy, and a Redis decoupling design, thereby ensuring that the system can still operate stably when the old BFF fails, while effectively controlling the access pressure of the user center interface and improving the system's fault tolerance and resource utilization.

[0079] Figure 3 This is a schematic diagram of the structure of a session processing device for enterprise mobile banking fault decoupling shown in an embodiment of the present application. Figure 3 As shown, the session processing device for enterprise mobile banking fault decoupling in the embodiment of the present application includes:

[0080] The verification unit 30 is configured to respond to the corporate mobile banking login interface request from the client, and the first electronic device verifies the login interface request;

[0081] A forwarding unit 31 is configured to trigger the first electronic device to forward the login interface request to the user center in response to the verification being passed;

[0082] The first creation unit 32 triggers the user center to create a first session based on the login interface request, generates a verification token, and sends the verification token to the first electronic device;

[0083] The 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, 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 in the old online banking system;

[0084] The third creating unit 34 is configured to, in response to the first electronic device initiating a session creation request to the second electronic device, cause the second electronic device to create a third session, perform Yitong component encapsulation on the third session, and store the encapsulated session in a remote dictionary service Redis.

[0085] The sending unit 35 is configured to send the third conversation to the first electronic device;

[0086] The assignment unit 36 ​​triggers the first electronic device to store 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.

[0087] As an implementation method, the session processing device for enterprise mobile banking fault decoupling in the embodiment of the present application further includes:

[0088] Time limit control unit ( Figure 3 (not shown) is used to set the time window and the maximum number of login interface requests allowed. 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.

[0089] As an implementation method, the session processing device for enterprise mobile banking fault decoupling in the embodiment of the present application further includes:

[0090] Cache Unit ( Figure 3 ), triggering the user center to locally cache the created session information, set a fixed expiration time for each cache entry, and update 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.

[0091] As an implementation method, the session processing device for enterprise mobile banking fault decoupling in the embodiment of the present application further includes:

[0092] Release unit ( Figure 3 ), used for initiating a session creation process between a first electronic device and a second electronic device, or initiating a session creation process between the first electronic device and an old bank system, capturing exception codes during program execution through a Catch block, storing the exception codes in a Try block, and performing exception handling on the exception codes in the Catch block to isolate exceptions in the executing program, thereby allowing exceptions to be passed through during session creation without interrupting the session creation process and subsequent related processing.

[0093] As an implementation method, the session processing device for enterprise mobile banking fault decoupling in the embodiment of the present application further includes:

[0094] Calling unit ( Figure 3 Not shown), when detecting a failure of the old front-end customized back-end BFF architecture, calling the user center interface to obtain session information that matches the current login interface request, caching the obtained session information; and returning the session information to the first electronic device.

[0095] In an exemplary embodiment, the above-mentioned processing units may be implemented by one or more central processing units (CPU), graphics processing units (GPU), baseband processors (BP), application-specific integrated circuits (ASIC), digital signal processors (DSP), programmable logic devices (PLD), complex programmable logic devices (CPLD), field-programmable gate arrays (FPGA), general-purpose processors, controllers, microcontrollers (MCU), microprocessors, or other electronic components.

[0096] In the embodiments of this application, Figure 3 The specific manner in which each unit in the illustrated session processing device for enterprise mobile banking fault decoupling performs operations has been described in detail in the embodiment of the method and will not be elaborated on here.

[0097] Figure 4 8 is a block diagram of an electronic device according to an exemplary embodiment. The electronic device 800 is intended to represent various forms of digital computers, such as 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 phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or claimed herein.

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

[0099] 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 disk, 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.

[0100] The computing unit 801 can be any general-purpose and / or specialized processing component 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 specialized artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 executes the various methods and processes described above, such as the method for handling sessions with fault decoupling for enterprise mobile banking. For example, in some embodiments, the method for handling sessions with fault decoupling for enterprise mobile banking can be implemented as a computer software program tangibly embodied 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 on 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 method for handling sessions with fault decoupling for enterprise mobile banking described above can be performed. Alternatively, in other embodiments, the computing unit 801 may be configured as a session processing method for enterprise mobile banking fault decoupling in any other appropriate manner (eg, by means of firmware).

[0101] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), 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 interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0102] The program code for implementing the methods of the present application can be written in any combination of one or more programming languages. Such program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the program code is executed by the processor or controller, the functions / operations specified in the flow charts and / or block diagrams are 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 a remote machine or server.

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

[0104] 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 pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types 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, voice input, or tactile input).

[0105] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

[0106] A computer system may include a client and a server. The client and server are generally remote from each other and typically interact through a communication network. The client-server relationship arises through computer programs running on the respective computers and having a client-server relationship with each other. The server may be a cloud server, a server in a distributed system, or a server integrated with a blockchain.

[0107] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be performed 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. This is not a limitation herein.

[0108] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. Throughout the description of this application, "plurality" means two or more, unless otherwise specifically defined.

[0109] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A session processing method for enterprise mobile banking fault decoupling, 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, characterized in that 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, characterized in that 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 enterprise mobile banking fault decoupling, 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 the 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 in the old online banking system; a third creating unit, in response to the first electronic device initiating a session creation request to the second electronic device, causing the second electronic device to create a third session, encapsulate the third session into components, and store the components in a remote dictionary service Redis; a sending unit, configured to send the third conversation to the first electronic device; The assignment unit triggers the first electronic device to store 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.

7. The device according to claim 6, characterized in that The device further comprises: The time limit control unit is used to set the time window and the maximum number of login interface requests allowed. 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, and the login interface request is received again and the maximum number is determined.

8. The device according to claim 6, characterized in that The device further comprises: The cache unit triggers the user center to locally cache 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.

9. The device according to claim 7 or 8, characterized in that The device further comprises: The release unit is used to capture the exception code 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, through the Catch block, store the exception code in the Try block, and perform exception processing on the exception code in the Catch block to isolate the exception in the execution program, realize the exception release of the session creation, and do not interrupt the session creation process and subsequent related processing.

10. A non-transitory computer-readable storage medium, which, when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to perform the steps of the session processing method for fault decoupling of corporate mobile banking as described in any one of claims 1 to 5.

Images