Method and device for processing scenario financial big data
By detecting APP jump operation and cache area adjustment, the problem of difficulty of traditional banks in identifying and migrating user scenario needs is solved, timely transmission and adaptability of financial data is achieved, and cross-device environments are adapted to user experience and data integrity are improved. .
Patent Information
- Application Number
- CN202411132344.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-19
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2044-08-19
AI Technical Summary
When traditional banks provide scenario financial services, it is difficult for them to identify and migrate users' demand characteristics in different scenarios, resulting in improper data identification, cache and transfer modes, which cannot ensure the integrity and timeliness of scenario financial data, and the existing data acquisition methods are not Adapt to cross-scenario and cross-device applications.
A scenario financial big data processing method and device is proposed. By detecting the APP jump operation, it determines whether to enable cached data reading and adjust the cache area size to ensure the timely transmission and adaptability of financial data between different APPs and devices, including APP Type recognition, cache data transfer, page layout adjustment and other functions.
It realizes timely storage and scenario-based adjustment of financial data, reduces the delay in data collection, transfer and acquisition, adapts to cross-device environments, and improves user experience and data integrity.
Smart Images

Figure CN118656166B_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the field of scenario finance and data processing technology, and in particular, relates to a method, device and computer-readable storage medium for processing scenario finance big data. Background Art
[0002] Scenario finance, or the "scenario + finance" model, uses digital technology to embed financial activities into various scenario services, facilitating efficient payment, transactions or services, so as to meet customers' financial needs and experiences in the natural interaction of scenarios. Scenario finance shifts the perspective from the traditional product- and transaction-centric to customer-centric, and shifts the physical space of services from bank-centric to scenario-centric. It provides end-to-end services by connecting the financial needs generated in customers' lives and production scenarios, bringing about financial innovation and business transformation.
[0003] The scenario finance built by traditional banks has obvious characteristics, and its form and function are single. In the market environment where competition for homogeneous services is becoming increasingly fierce, after meeting customer needs, the number of new customers is decreasing. With the development of mobile Internet and big data technology, scenario finance has become a new trend in the development of commercial banks. Banks need to design and provide scenario-based financial services based on the individual needs of users in different scenarios.
[0004] However, it is still difficult for banks to identify, save, and migrate user demand characteristics in different scenarios and design scenario-based data service models based on these needs. If the data identification, caching, and transfer modes are inappropriate, the integrity and timeliness of scenario-based financial data cannot be ensured; at the same time, the existing scenario-based financial data acquisition and utilization methods cannot be applied across scenarios and devices, and are not suitable for users' multi-terminal application scenarios. Summary of the invention
[0005] In order to solve the above technical problems, the present invention proposes a method, device and computer-readable storage medium for processing scenario financial big data.
[0006] In a first aspect of the present invention, a method for processing scenario financial big data is proposed. The method is applied to a user terminal device, where a financial APP and a non-financial APP are installed. The method comprises the following steps:
[0007] S1: In response to detecting an APP jump operation when the current user operates the user terminal device, determining the type of the APP jump operation; the APP jump operation includes jumping from a first APP to a second APP;
[0008] S2: Based on the type of the APP jump operation, determine whether to enable the cache data reading operation;
[0009] If yes, read the cache data of the first APP from the first cache area and store it in the second cache area; go to step S3;
[0010] If not, clear the cache data in the first cache area, and start caching the operation data after the user jumps to the second APP to the first cache area, and return to step S1;
[0011] S3: Determine whether the operation time t of the user on the second APP exceeds a first preset value T. If so, adjust the page layout and / or display data of the second APP based on the data in the second cache area.
[0012] The storage space size of the first cache area is M1, and the storage space size of the second cache area is M2; and M2>K*M1; K≥2.
[0013] The step S2 determines whether to enable the cache data reading operation based on the type of the APP jump operation, and specifically includes:
[0014] If the first APP is a non-financial APP and the second APP is a financial APP, the cache data reading operation is started;
[0015] Alternatively, if the second APP is a financial APP, the first APP is a financial APP, and the first APP is activated by jumping from a non-financial APP, the cache data reading operation is started.
[0016] In step S3, if the operation time t of the user on the second APP is less than the first preset value T, the operation data of the user on the second APP is directly cached in the second cache area, and the process returns to step S1.
[0017] In step S3, when the operation time t of the user on the second APP exceeds the first preset value T, the size of K is adjusted according to the operation time t of the user on the second APP and the cumulative number of times Num that the operation time t exceeds the first preset value T.
[0018] In a second aspect of the present invention, a device for processing scenario financial big data is provided, the device comprising a pre-set first cache area and a second cache area, an APP type identification unit, an APP jump operation detection unit, a cache data transfer unit, a cache data access unit, and a financial scenario adaptation unit;
[0019] The APP jump operation detection unit detects an APP jump operation from a first APP to a second APP;
[0020] When the APP jump operation detection unit detects the APP jump operation, the APP type identification unit identifies the APP types of the first APP and the second APP, and the APP types include financial APPs or non-financial APPs;
[0021] Based on the identification result of the APP type identification unit, the cache data transfer unit reads the cache data of the first APP from the first cache area and transfers and stores it to the second cache area, or the cache data access unit clears the cache data in the first cache area and starts to cache the operation data after the user jumps to the second APP in the first cache area;
[0022] When the operation time t of the user on the second APP exceeds the first preset value T, the financial scenario adaptation unit adjusts the page layout and / or display data of the second APP based on the data in the second cache area.
[0023] The processing device also includes a cache size adjustment unit;
[0024] When the user's operation time t on the second APP exceeds the first preset value T, the cache size adjustment unit adjusts the size of the first cache area and / or the second cache area according to the user's operation time t on the second APP and the cumulative number of times Num that the operation time t exceeds the first preset value T.
[0025] Based on the identification result of the APP type identification unit, the cache data transfer unit reads the cache data of the first APP from the first cache area and transfers and stores it to the second cache area, or the cache data access unit clears the cache data in the first cache area and starts to cache the operation data after the user jumps to the second APP to the first cache area, specifically including:
[0026] If the first APP is a non-financial APP and the second APP is a financial APP, the cache data transfer unit reads the cache data of the first APP from the first cache area and transfers and stores it in the second cache area;
[0027] Alternatively, if the second APP is a financial APP, the first APP is a financial APP, and the first APP is activated by jumping from a non-financial APP, the cache data transfer unit reads the cache data of the first APP from the first cache area and transfers and stores it in the second cache area;
[0028] Otherwise, the cache data access unit clears the cache data in the first cache area, and starts to cache the operation data after the user jumps to the second APP in the first cache area.
[0029] When the operation time t of the user on the second APP is less than the first preset value T, the cache data access unit directly caches the operation data of the user on the second APP to the second cache area.
[0030] The processing device includes a first electronic device and a second electronic device, wherein the first electronic device uses any one of Bluetooth, ultrasound, electromagnetic waves and laser to achieve communication connection with the second electronic device;
[0031] The first buffer area is arranged in the first electronic device, and the second buffer area is arranged in the second electronic device;
[0032] And / or, the first electronic device installs the first APP, and the second electronic device installs the second APP.
[0033] In the third aspect of the present invention, a computer-readable storage medium is also provided for storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes a method for processing scenario financial big data as described in the first aspect.
[0034] In a fourth aspect of the present invention, a computer device is also proposed. When a computer instruction runs on the computer device, the electronic device executes the aforementioned method for processing scenario financial big data.
[0035] Specifically, the computer device can be various electronic devices, such as a portable terminal device including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of a method for processing scenario financial big data described in the first aspect are implemented.
[0036] The technical solution of the present invention identifies the type of APP jump operation when the current user operates the user terminal device, and then obtains or caches the user's operation data when the cache data reading operation needs to be enabled. The data acquisition or caching is performed based on cache areas of different sizes, thereby ensuring that financial data with scenario value can be saved in time and used for subsequent scenario adjustments, and reducing the delay in data collection, transfer and acquisition; at the same time, the technical solution also includes an adaptive adjustment process of the cache area size, which can ensure that more financial data with scenario value can be completely saved. The method can also be applied to a cross-device environment, thereby improving the user experience.
[0037] Further advantages of the present invention will be further reflected in detail in the specific embodiments section in conjunction with the drawings of the specification. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0039] Figure 1 It is a main flow chart of a method for processing scenario financial big data according to an embodiment of the present invention;
[0040] Figure 2 yes Figure 1 A schematic diagram of a specific embodiment of the method when it is executed on a user terminal device;
[0041] Figure 3 It is a schematic diagram of the functional unit composition of a scene financial big data processing device according to an embodiment of the present invention;
[0042] Figure 4 It is a schematic diagram of a specific implementation of the technical solution of the present invention in a cross-device environment;
[0043] Figure 5 It is a computer program implementation flow chart of a specific embodiment of the technical solution of the present invention. DETAILED DESCRIPTION
[0044] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the 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 that are the same as the present application. Instead, they are only examples of devices and methods that are the same as some aspects of the present application as detailed in the attached claims.
[0045] Before introducing the embodiments of the present application, the meaning of some technical features related to the present application and the motivation for proposing the technical solution of the present application are first introduced.
[0046] User terminal equipment: includes mobile terminals, desktop terminals and other electronic devices used by users, such as mobile phones, tablet computers, desktop computers, etc.
[0047] In an embodiment of the present application, each user has at least two types (two) of terminal devices, and these two types (two) of terminal devices are connected based on wireless communication and can share screen content in real time or with a delay.
[0048] Assuming that the user has a first electronic device and a second electronic device, the real-time sharing method includes: opening the first electronic device and the second electronic device at the same time, and after operating the first electronic device, continuing to operate the second electronic device based on the operation result of the first device. For example, after the user operates the first APP on the first electronic device, it is necessary to open the second APP on the second electronic device, and the second APP at least shares all or part of the content that the first APP has previously operated.
[0049] The delayed sharing method includes: after the current user logs in to the first APP on the first electronic device with the user login name, within the preset delay period, logs in to the second APP on the second electronic device with the same login name, and continues to operate the second APP on the second electronic device based on the operation result of the first APP on the first device. For example, after the user operates the first APP on the first electronic device, the second APP is opened on the second electronic device within the preset delay period (for example, within 5 minutes), and the second APP at least shares all or part of the content that has been previously operated by the first APP.
[0050] Financial apps and non-financial apps.
[0051] Financial apps mainly refer to apps registered with financial regulatory agencies, mainly various types of bank apps, such as "XX Mobile Banking", "XXXX Bank Card", etc.
[0052] Non-financial APPs refer to APPs other than financial APPs. In the embodiments of the present application, they mainly include e-commerce shopping APPs, game APPs, and social APPs.
[0053] APP jump: refers to the operation of jumping from one APP to another.
[0054] In the embodiments of the present application, APP jump is mainly carried out in two ways:
[0055] (1) Internal jump to an APP: When a user is operating a first APP, they can directly jump to a second APP through a specific operation (such as clicking a link, component or control in the first APP);
[0056] (2) External APP jump: After operating the first APP, the user closes the first APP or minimizes the first APP, switches the first APP to the background and makes it invisible, and then opens the second APP to operate.
[0057] In the present application, whether it is an APP jump or an APP external jump, from operating the first APP to operating the second APP is a continuous operation, and there are no other operations in between. Therefore, based on the system cache mechanism, the second APP at least shares all or part of the content that has been previously operated by the first APP.
[0058] Scenario finance: a data acquisition method relative to non-scenario finance. Traditional non-scenario financial services (such as the bank’s own APP) are independent of life scenarios, have severe homogeneous competition, and are prone to customer loss. However, successful scenario finance can often form a complete financial ecological closed loop after a period of operation. The research and development process of financial products for traditional non-scenario financial services is initiated from the bank side (web side, mobile side itself). Although the early market research and user demand analysis are constantly improving, there are still some problems such as the disconnection between product launch and user demand. Under the scenario finance model, the research and development process of financial products starts from the real scenario where the product will be used in the end, and the product is customized according to needs. Therefore, the demand matching degree is high, the target customer group is clear, and it is easier to carry out precision marketing.
[0059] In addition, the specific implementation methods of this application involve user-related data. When the embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions. Optionally, user-related data will not be used for identity identification and needs to be anonymized. At the same time, when the user exits the relevant APP or application, the relevant data will not be saved on the server.
[0060] On this basis, see first Figure 1 , Figure 1 A main flow chart showing a method for processing scenario financial big data according to an embodiment of the present invention.
[0061] Figure 1 The method comprises the following steps S1-S3:
[0062] S1: In response to detecting an APP jump operation when the current user operates the user terminal device, determining the type of the APP jump operation; the APP jump operation includes jumping from a first APP to a second APP;
[0063] S2: Based on the type of the APP jump operation, determine whether to enable the cache data reading operation;
[0064] If yes, read the cache data of the first APP from the first cache area and store it in the second cache area; go to step S3;
[0065] If not, clear the cache data in the first cache area, and start caching the operation data after the user jumps to the second APP to the first cache area, and return to step S1;
[0066] S3: Determine whether the operation time t of the user on the second APP exceeds a first preset value T. If so, adjust the page layout and / or display data of the second APP based on the data in the second cache area.
[0067] In practical applications, the method is applied to a user terminal device, which has financial APPs and non-financial APPs installed.
[0068] The step S2 determines whether to enable the cache data reading operation based on the type of the APP jump operation, and specifically includes:
[0069] If the first APP is a non-financial APP and the second APP is a financial APP, the cache data reading operation is started;
[0070] For better understanding Figure 1 For an example, see Figure 2 , Figure 2 yes Figure 1 A schematic diagram of a specific embodiment of the method when it is executed on a user terminal device.
[0071] Figure 2 In the example, it is assumed that the first APP currently operated by the user is a non-financial APP (XX Shopping), and the second APP after the jump operation is a financial APP (YY Bank).
[0072] When the user operates the first APP, the electronic device temporarily stores (caches) the relevant operation data of the operation of the first APP in the first cache area.
[0073] When the user opens the second APP based on a jump operation (which may be an external jump or an internal jump), it is determined whether to start the cache data reading operation based on the type of the APP jump operation.
[0074] exist Figure 2 In the embodiment, the first APP is a non-financial APP and the second APP is a financial APP, so the cache data reading operation is enabled.
[0075] Specifically, the cache data of the first APP is read from the first cache area and stored in the second cache area.
[0076] Next, determine whether the user's operation time t on the second APP exceeds the first preset value T. If so, adjust the page layout and / or display data of the second APP based on the data in the second cache area.
[0077] As an example, when a user jumps from a first non-financial APP to a second financial APP, it is usually because the user needs to continue to complete the operation that was not completed (or could not be completed) on the first non-financial APP on the second financial APP, such as payment operation, change of payment method (to use a specific bank coupon), etc. That is, the first APP needs to call the second APP to complete the payment operation, or the first APP needs to obtain the coupon provided by the second APP, etc.
[0078] When the user's operation time t on the second APP exceeds the first preset value T, it means that the current page layout and / or display data of the second financial APP do not meet the personalized needs of the current user, for example, the payment button is hidden deeper (in the sub-page of the next layer), the coupon click button is not visible (manual search is required), etc.
[0079] At this time, the second financial APP can adjust the page layout and / or display data of the second APP based on the data in the second cache area, for example, display the payment button in a prominent position on the homepage, directly display the coupon acquisition method related to the first APP, etc.
[0080] Figure 2 The implementation method embodies the first advantage of the scenario financial data processing method of the present application, that is, the research and development process of financial products starts from the real scenario in which the product will be ultimately used, ensuring that financial data with scenario value can be saved in a timely manner and used for subsequent scenario adjustments, and reducing the delay in data collection, transfer and acquisition.
[0081] Of course, the technical solution of this application focuses on the situation where the user switches from a non-financial scenario to a financial scenario. This type of situation is the best way to obtain scenario financial data, because the sharing of financial scenario data between similar financial data is easy to achieve within the bank.
[0082] Correspondingly, if the current jump indicates that there is a high possibility that non-financial scenario data does not exist, based on the type of the APP jump operation, it is determined that there is no need to enable the cache data reading operation.
[0083] At this time, the cache data in the first cache area is cleared, and the operation data after the user jumps to the second APP starts to be cached in the first cache area, and the process returns to step S1;
[0084] That is to say, at this time, the second APP needs to perform possible subsequent adjustments based on the operation data of the user operating the second APP itself.
[0085] As an extended scenario, the step S2 determines whether to enable the cache data reading operation based on the type of the APP jump operation, and further includes:
[0086] If the second APP is a financial APP, the first APP is a financial APP, and the first APP is activated by jumping from a non-financial APP, the cache data reading operation is started.
[0087] It can be seen that there is still non-financial scenario data of non-financial apps at this time, and cache data reading operations also need to be enabled.
[0088] Since users have different operation durations and operation types on different apps, the size of the corresponding cache data changes all the time. If a static cache size is used, data overflow is likely to occur; if a fixed, larger cache size is preset, there may be storage waste.
[0089] Therefore, as a second advantage of the present application, a dynamic first variable-size buffer area and a second variable-size buffer area are adopted.
[0090] Specifically, the storage space size of the first cache area is M1, and the storage space size of the second cache area is M2; and M2>K*M1; K is a coefficient greater than or equal to 2, that is, K≥2.
[0091] In step S3, when the operation time t of the user on the second APP exceeds the first preset value T, the size of K is adjusted according to the operation time t of the user on the second APP and the cumulative number of times Num that the operation time t exceeds the first preset value T.
[0092] The first preset value T is usually obtained by APP developers based on historical data statistics. For example, assuming that historical statistics show that the maximum tolerable time for users to find a function button is 1 minute (they will give up directly if it exceeds 1 minute), the preset value T = 60 seconds;
[0093] When the operation time t after the user opens the second APP is greater than 60 seconds each time, the cumulative number Num increases by 1; the larger the cumulative number, the stronger the user's dependence on the second APP, so the current scene data is more valuable and more cache space is needed.
[0094] Preferably, the size of K is adjusted according to the operation time t of the user on the second APP and the cumulative number of times Num that the operation time t exceeds the first preset value T. The size adjustment is implemented by a computer program as follows:
[0095]
[0096] in, is the K value before adjustment.
[0097] Preferably, K is an integer, that is, the K value calculated by the above formula is rounded up.
[0098] When the first APP and the second APP are closed at the same time, the cumulative number Num is reset to zero and the K value is restored to the initialization value.
[0099] Based on the above method, the data acquisition or caching of the present application is carried out based on cache areas of different sizes, thereby ensuring that financial data with scenario value can be saved in a timely manner and used for subsequent scenario adjustments, and reducing the delay in data collection, transfer and acquisition; at the same time, the technical solution also includes an adaptive adjustment process of the cache area size, which can ensure that more financial data with scenario value can be completely saved.
[0100] Figure 3-Figure 4 The embodiment of the present invention introduces a schematic diagram of the functional unit composition of a scene financial big data processing device according to an embodiment of the present invention from a system perspective.
[0101] exist Figure 3 A device for processing scenario financial big data, the device comprising a pre-set first cache area and a second cache area, an APP type identification unit, an APP jump operation detection unit, a cache data transfer unit, a cache data access unit, and a financial scenario adaptation unit;
[0102] The APP jump operation detection unit detects an APP jump operation from a first APP to a second APP;
[0103] When the APP jump operation detection unit detects the APP jump operation, the APP type identification unit identifies the APP types of the first APP and the second APP, and the APP types include financial APPs or non-financial APPs;
[0104] Based on the identification result of the APP type identification unit, the cache data transfer unit reads the cache data of the first APP from the first cache area and transfers and stores it to the second cache area, or the cache data access unit clears the cache data in the first cache area and starts to cache the operation data after the user jumps to the second APP in the first cache area;
[0105] When the operation time t of the user on the second APP exceeds the first preset value T, the financial scenario adaptation unit adjusts the page layout and / or display data of the second APP based on the data in the second cache area.
[0106] When the user's operation time t on the second APP exceeds the first preset value T, the cache size adjustment unit adjusts the size of the first cache area and / or the second cache area according to the user's operation time t on the second APP and the cumulative number of times Num that the operation time t exceeds the first preset value T.
[0107] Based on the identification result of the APP type identification unit, the cache data transfer unit reads the cache data of the first APP from the first cache area and transfers and stores it to the second cache area, or the cache data access unit clears the cache data in the first cache area and starts to cache the operation data after the user jumps to the second APP to the first cache area, specifically including:
[0108] If the first APP is a non-financial APP and the second APP is a financial APP, the cache data transfer unit reads the cache data of the first APP from the first cache area and transfers and stores it in the second cache area;
[0109] Alternatively, if the second APP is a financial APP, the first APP is a financial APP, and the first APP is activated by jumping from a non-financial APP, the cache data transfer unit reads the cache data of the first APP from the first cache area and transfers and stores it in the second cache area;
[0110] Otherwise, the cache data access unit clears the cache data in the first cache area, and starts to cache the operation data after the user jumps to the second APP in the first cache area.
[0111] When the operation time t of the user on the second APP is less than the first preset value T, the cache data access unit directly caches the operation data of the user on the second APP to the second cache area.
[0112] Figure 4 It is a schematic diagram of a specific implementation of the technical solution of the present invention in a cross-device environment.
[0113] Specifically, the processing device includes a first electronic device and a second electronic device, and the first electronic device uses any one of Bluetooth, ultrasound, electromagnetic waves and laser connection methods to achieve communication connection with the second electronic device;
[0114] The first cache area is set in the first electronic device, and the second cache area is set in the second electronic device; and / or, the first electronic device installs the first APP, and the second electronic device installs the second APP.
[0115] As a specific example, each user has at least two types (two) of terminal devices, and these two types (two) of terminal devices are connected based on wireless communication and can share screen content in real time or with delay.
[0116] Assuming that the user has a first electronic device and a second electronic device, the real-time sharing method includes: opening the first electronic device and the second electronic device at the same time, and after operating the first electronic device, continuing to operate the second electronic device based on the operation result of the first device. For example, after the user operates the first APP on the first electronic device, it is necessary to open the second APP on the second electronic device, and the second APP at least shares all or part of the content that the first APP has previously operated.
[0117] The delayed sharing method includes: after the current user logs in to the first APP on the first electronic device with the user login name, within the preset delay period, logs in to the second APP on the second electronic device with the same login name, and continues to operate the second APP on the second electronic device based on the operation result of the first APP on the first device. For example, after the user operates the first APP on the first electronic device, the second APP is opened on the second electronic device within the preset delay period (for example, within 5 minutes), and the second APP at least shares all or part of the content that has been previously operated by the first APP.
[0118] It is understandable that after the embodiment in the form of method flow is elaborated in detail, the corresponding embodiment in the form of system function architecture does not need to be repeated again, but those skilled in the art can directly and unambiguously determine that the embodiment in the form of system function architecture also corresponds to all the contents of the embodiment in the form of method flow. The same is true for the embodiment in the form of computer program code pseudo language.
[0119] Based on the above introduction, Figure 5 It is a computer program implementation flow chart of a specific embodiment of the technical solution of the present invention, which is specifically introduced as follows ( Figure 5 Step numbers are omitted):
[0120] Step 1: Detect the jump from non-financial APP to financial APP;
[0121] Step 2: Start the cache data reading operation;
[0122] Step 3: Read the cache data of non-financial apps from the first cache area and store it in the second cache area;
[0123] Step 4: Determine whether the user's operation time t on the financial APP exceeds the first preset value T;
[0124] If yes, go to Step 6; otherwise, go to Step 5;
[0125] Step 5: directly cache the user's operation data on the financial APP into the second cache area, and return to Step 1;
[0126] Step 6: Based on the data in the second cache area, adjust the page layout and / or display data of the financial APP;
[0127] Step 7: Adjust the size of the first cache area and / or the second cache area according to the operation time t of the user on the financial APP and the cumulative number of times Num that the operation time t exceeds the first preset value T, and return to Step 1.
[0128] By identifying the type of APP jump operation when the current user operates the user terminal device, and then obtaining or caching the user's operation data when the cache data reading operation needs to be enabled, the data acquisition or caching is performed based on cache areas of different sizes. The technical solution of the present invention ensures that financial data with scenario value can be saved in time and used for subsequent scenario adjustments, and reduces the delay in data collection, transfer and acquisition; at the same time, the technical solution also includes an adaptive adjustment process of the cache area size, which can ensure that more financial data with scenario value can be completely saved. The method can also be applied to cross-device environments, thereby improving user experience.
[0129] The present invention provides multiple embodiments, each of which can constitute an independent technical solution and may contribute to the prior art and solve corresponding technical problems. However, it should be pointed out that different embodiments can be combined with each other without violating logic; at the same time, each embodiment can solve at least one technical problem, but it is not required that each individual embodiment solves multiple or all technical problems.
Claims
1. A method for processing scenario financial big data, the method being applied to a user terminal device, the user terminal device being installed with a financial APP and a non-financial APP; It is characterized in that The method comprises the following steps: S1: In response to detecting an APP jump operation when the current user operates the user terminal device, determining the type of the APP jump operation; the APP jump operation includes jumping from a first APP to a second APP; And the operation data related to the operation of the first APP is cached in the first cache area; S2: Based on the type of the APP jump operation, determine whether to enable the cache data reading operation; if so, read the relevant operation data of the first APP from the first cache area and transfer it to the second cache area; Go to step S3; If not, clear the cache data in the first cache area, and start caching the operation data after the user jumps to the second APP in the first cache area, and return to step S1; S3: Determine whether the operation time t of the user on the second APP exceeds a first preset value T. If yes, adjust the page layout and / or display data of the second APP based on the data in the second cache area; The step S2 determines whether to enable the cache data reading operation based on the type of the APP jump operation, and specifically includes: If the first APP is a non-financial APP and the second APP is a financial APP, the cache data reading operation is started; Alternatively, if the second APP is a financial APP, the first APP is a financial APP, and the first APP is activated by jumping from a non-financial APP, the cache data reading operation is started.
2. The method for processing scenario financial big data according to claim 1, characterized in that: The storage space size of the first cache area is M1, and the storage space size of the second cache area is M2; and M2>K*M1; K≥2.
3. The method for processing scenario financial big data according to claim 1, characterized in that: In step S3, if the operation time t of the user on the second APP is less than the first preset value T, the operation data of the user on the second APP is directly cached in the second cache area, and the process returns to step S1.
4. A method for processing scenario financial big data according to claim 2, characterized in that: In step S3, when the operation time t of the user on the second APP exceeds the first preset value T, the size of K is adjusted according to the operation time t of the user on the second APP and the cumulative number of times Num that the operation time t exceeds the first preset value T.
5. A device for processing scenario financial big data, the device comprising a pre-set first cache area and a second cache area, an APP type identification unit, an APP jump operation detection unit, a cache data transfer unit, a cache data access unit, and a financial scenario adaptation unit, characterized in that: The APP jump operation detection unit detects an APP jump operation from a first APP to a second APP; and the relevant operation data of operating the first APP is cached in the first cache area; When the APP jump operation detection unit detects the APP jump operation, the APP type identification unit identifies the APP types of the first APP and the second APP, and the APP types include financial APPs or non-financial APPs; Based on the identification result of the APP type identification unit, the cache data transfer unit reads the relevant operation data of the first APP from the first cache area and transfers it to the second cache area, or the cache data access unit clears the cache data in the first cache area and starts to cache the operation data after the user jumps to the second APP in the first cache area; When the operation time t of the user on the second APP exceeds a first preset value T, the financial scenario adaptation unit adjusts the page layout and / or display data of the second APP based on the data in the second cache area; Wherein, based on the identification result of the APP type identification unit, the cache data transfer unit reads the relevant operation data of the first APP from the first cache area and transfers it to the second cache area, or the cache data access unit clears the cache data in the first cache area and starts to cache the operation data after the user jumps to the second APP to the first cache area, specifically including: If the first APP is a non-financial APP and the second APP is a financial APP, the cache data transfer unit reads the cache data of the first APP from the first cache area and transfers and stores it in the second cache area; Alternatively, if the second APP is a financial APP, the first APP is a financial APP and the first APP is activated by jumping from a non-financial APP, the cache data transfer unit reads the cache data of the first APP from the first cache area and transfers it to the second cache area for storage; otherwise, the cache data access unit clears the cache data in the first cache area and starts caching the operation data after the user jumps to the second APP to the first cache area.
6. A scenario financial big data processing device as claimed in claim 5, characterized in that: The processing device also includes a cache size adjustment unit; When the user's operation time t on the second APP exceeds the first preset value T, the cache size adjustment unit adjusts the size of the first cache area and / or the second cache area according to the user's operation time t on the second APP and the cumulative number of times Num that the operation time t exceeds the first preset value T.
7. The device for processing scenario financial big data according to claim 5, characterized in that: When the operation time t of the user on the second APP is less than the first preset value T, the cache data access unit directly caches the operation data of the user on the second APP to the second cache area.
8. The device for processing scenario financial big data according to claim 5, characterized in that: The processing device includes a first electronic device and a second electronic device, wherein the first electronic device uses any one of Bluetooth, ultrasound, electromagnetic waves and laser to achieve communication connection with the second electronic device; The first buffer area is arranged in the first electronic device, and the second buffer area is arranged in the second electronic device; and / or, The first electronic device installs the first APP, and the second electronic device installs the second APP.
Citation Information
Patent Citations
Storage control method and device of application cache data
CN105516787A
Page processing method and device, equipment and storage medium
CN118034822A
APP operating method and device and APP output device supporting the same
US20140298355A1
Cascade cache refreshing
US20200320011A1
