Cache method and device of session hotspot object, electronic equipment and storage medium

Abstract

The application discloses a kind of caching methods of conversation hot spot object and its device, electronic equipment and storage medium, it is related to artificial intelligence technical field, wherein, the caching method includes: obtaining the time period of target customer using target financial application, when reaching the specified time point of caching before time period, the branch office information of data source representation is inquired, and transaction data and account data generated by data source, input to cache decision engine, and receive object generation instruction and object cache time information output by cache decision engine, in the case where object generation instruction indicates that conversation hot spot object needs to be generated in advance, generate conversation hot spot object, and cache conversation hot spot object according to object cache time information.The present application solves the technical problems of slow generation speed and high modification cost in generating group information object in the related art.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of artificial intelligence or other related technical fields, in particular, to a session hot object caching method and device, electronic equipment and storage medium. BACKGROUND

[0002] Currently, various financial institutions provide various applications to serve customers. For example, the enterprise online banking system is an important business system of the financial institution serving enterprise customers. In order to simplify the acquisition and use of customer branch data, account list and other data, the enterprise online banking system queries each data source (i.e. the transaction data source indicated by the customer's branch) to obtain customer information and processes to generate a group information object when the customer logs in. After a long iteration, the group information object may involve a large number of data sources, and the generation logic is extremely complex. For some customers with a large number of branches, the generation of the group information object is slow, which seriously affects the customer login speed.

[0003] To solve the above problems, there are two common technical optimization schemes in related technologies, as follows:

[0004] Scheme 1: Cache customer data in a distributed cache system, and change the way of obtaining customer data from each data source when logging in to obtaining customer data from the distributed cache uniformly. This can save the time of interacting with each data source when generating the object.

[0005] Scheme 2: Change the generation of customer data objects when logging in to obtaining data when the customer uses related functions.

[0006] However, the above two optimization schemes have obvious defects: both have high modification costs and the final optimization effect cannot be guaranteed.

[0007] For scheme 1: the modification cost is high. The existing customer information acquisition logic needs to be completely reconstructed to obtain from the distributed cache first and then from each data source. And the data sources involved need to have a cache mechanism. Each time the function is iterated, the problem of cache breakdown and cache avalanche also needs to be considered. And this scheme only saves the data acquisition time, does not save the data processing time, and the optimization has bottlenecks, so the final effect cannot be guaranteed.

[0008] For scheme 2: the modification cost is high, and it only reduces the login time, but when the customer actually uses the function, there is still a problem of waiting for the generation of the group information object. And generating the group information object by the specific function will lead to scattered and inconsistent technical implementation, and different functions may need to generate the group information object repeatedly, which causes resource waste.

[0009] In view of the above problems, no effective solution has been proposed so far. SUMMARY

[0010] Embodiments of the present application provide a session hotspot object caching method and device, electronic equipment and storage medium to at least solve the technical problem of slow generation speed and high modification cost in generating group information objects in related technologies.

[0011] According to an aspect of embodiments of the present application, a session hotspot object caching method is provided, comprising: obtaining a time period in which a target customer uses a target financial application, wherein the target customer comprises N branch offices, each branch office representing a data source, all data sources being combined into a group information object, the data source indicating a source of data generated by the branch office through the target financial application for financial transactions, and N being a positive integer greater than or equal to 1; querying office information of the branch office represented by the data source, and transaction data and account data generated by the data source at a specified caching time point before reaching the time period; inputting the office information, the transaction data and the account data into a caching decision engine, and receiving object generation instructions and object caching time information output by the caching decision engine, wherein the instruction information of the object generation instructions comprises whether a session hotspot object needs to be generated in advance before the time period in which the target customer uses the target financial application, and the session hotspot object indicates a programmed object with a financial service use frequency value greater than a first preset frequency threshold in a target session; in the case where the object generation instructions indicate that the session hotspot object needs to be generated in advance, generating the session hotspot object, and caching the session hotspot object according to the object caching time information.

[0012] Optionally, after caching the session hotspot object according to the object caching time information, the method further comprises: performing serialization processing on object data of the session hotspot object; and distributing storage of byte data of the serialized session hotspot object.

[0013] Optionally, the cache decision engine is determined by: collecting an object size of a historical session hot object of each customer, usage time information generated by the customer during use of the target financial application, and an update frequency value of customer data, wherein the customer data includes transaction data and account data; integrating the object size of the historical session hot object of the customer, the usage time information, and the update frequency value of the customer data into a customer historical information set; dividing the customer historical information set according to the usage time information, training an initial decision engine with an information set training segment obtained after the division and corresponding usage time information, wherein the customer historical information set after the division includes an information set training segment and an information set verification segment; and confirming that the initial decision engine is trained when a similarity value between usage time information output by the initial decision engine and object information of a session hot object generated by the customer is greater than a preset similarity threshold value, to obtain the cache decision engine.

[0014] Optionally, after the cache decision engine is obtained, the method further includes: querying a session data amount corresponding to each customer with each branch of the customer as a session object; and adjusting the cache decision engine based on the session data amount.

[0015] Optionally, the step of adjusting the cache decision engine based on the session data amount includes: not caching the session hot object when the session data amount is less than a first preset data amount threshold value.

[0016] Optionally, the step of adjusting the cache decision engine based on the session data amount includes: reducing a cache duration of the session hot object and increasing an update frequency of the session hot object when the session data amount is greater than or equal to the first preset data amount threshold value but less than a second preset data amount threshold value, and an update frequency value of customer data of the customer is greater than a second preset frequency threshold value, wherein the second preset data amount threshold value is greater than the first preset data amount threshold value.

[0017] Optionally, the step of adjusting the cache decision engine based on the session data amount includes: increasing the cache duration of the session hot object and reducing the update frequency of the session hot object when the session data amount is greater than or equal to the second preset data amount threshold value and the update frequency value of the customer data of the customer is less than or equal to the second preset frequency threshold value.

[0018] Optionally, after inputting the institution information, the transaction data and the account data into the cache decision engine, the method further comprises: the cache decision engine reading historical operation records of the customer from a message queue in advance, wherein the message queue records operation information of the customer in history in advance; and the cache decision engine outputting the object generation instruction based on the historical operation records of the customer and the institution information, the transaction data and the account data.

[0019] Optionally, the time period in which the target customer uses the target financial application is determined by a time period of at least one of: a salary payment day, a tax filing day, and a settlement day.

[0020] According to another aspect of the embodiments of the present application, a cache device for a session hot spot object is further provided, comprising: an acquisition unit configured to acquire a time period in which a target customer uses a target financial application, wherein the target customer comprises N branch institutions, each of the branch institutions representing a data source, all of the data sources being combined as a group information object, the data source indicating a source of data generated by the branch institution through the target financial application for financial transactions, and N being a positive integer greater than or equal to 1; a query unit configured to query institution information of a branch institution represented by the data source, and transaction data and account data generated by the data source at a cache specified time point before the time period is reached; an input unit configured to input the institution information, the transaction data and the account data into a cache decision engine, and receive an object generation instruction and object cache time information output by the cache decision engine, wherein instruction information of the object generation instruction comprises whether a session hot spot object needs to be generated in advance before the time period in which the target customer uses the target financial application, and the session hot spot object indicates a programmed object with a financial service use frequency value greater than a first preset frequency threshold in a target session; and a cache unit configured to generate the session hot spot object in a case where the object generation instruction indicates that the session hot spot object needs to be generated in advance, and cache the session hot spot object according to the object cache time information.

[0021] Optionally, the cache device for a session hot spot object further comprises: a serialization unit configured to perform serialization processing on object data of the session hot spot object after the session hot spot object is cached according to the object cache time information; and a storage unit configured to distribute and store byte data of the session hot spot object after serialization.

[0022] Optionally, the cache decision engine is determined by: collecting an object size of a historical session hot object of each client, usage time information generated by the client during use of the target financial application, and an update frequency value of client data, wherein the client data includes transaction data and account data; integrating the object size of the historical session hot object of the client, the usage time information, and the update frequency value of the client data into a client historical information set; dividing the client historical information set according to the usage time information, training an initial decision engine with an information set training segment obtained after the division and corresponding usage time information, wherein the client historical information set after the division includes an information set training segment and an information set verification segment; and confirming that the initial decision engine is trained completely and the cache decision engine is obtained when a similarity value between usage time information output by the initial decision engine and object information of a session hot object generated by the client is greater than a preset similarity threshold.

[0023] Optionally, the cache device of the session hot object further includes: a first query module configured to query a session data amount corresponding to each client with each branch of the client as a session object after the cache decision engine is obtained; and an adjustment unit configured to adjust the cache decision engine based on the session data amount.

[0024] Optionally, the adjustment unit includes a non-cache module configured to not cache the session hot object when the session data amount is less than a first preset data amount threshold.

[0025] Optionally, the adjustment unit includes a first adjustment module configured to reduce a cache duration of the session hot object and increase an update frequency of the session hot object when the session data amount is greater than or equal to the first preset data amount threshold but less than a second preset data amount threshold, and an update frequency value of client data of the client is greater than a second preset frequency threshold, wherein the second preset data amount threshold is greater than the first preset data amount threshold.

[0026] Optionally, the adjustment unit includes a second adjustment module configured to increase the cache duration of the session hot object and reduce the update frequency of the session hot object when the session data amount is greater than or equal to the second preset data amount threshold and the update frequency value of the client data of the client is less than or equal to the second preset frequency threshold.

[0027] Optionally, after inputting the institution information, the transaction data and the account data into the cache decision engine, the method further comprises: the cache decision engine reading historical operation records of the customer in the message queue, wherein the message queue has pre-recorded operation information of the customer in the historical process; and the cache decision engine outputting the object generation instruction based on the historical operation records of the customer and the institution information, the transaction data and the account data.

[0028] Optionally, the time period in which the target customer uses the target financial application is determined by at least one of a payroll date, a tax filing date, and a settlement date.

[0029] According to another aspect of an embodiment of the present application, a computer readable storage medium is provided, the computer readable storage medium comprising a stored computer program, wherein the computer readable storage medium is caused to perform the cache method of the session hot object when the computer program is executed.

[0030] According to another aspect of an embodiment of the present application, an electronic device is provided, comprising one or more processors and a memory, the memory being configured to store one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the cache method of the session hot object.

[0031] In the present disclosure, when caching the session hot object of the customer, the time period in which the target customer uses the target financial application is obtained first, and when reaching the cache specified time point before the time period, the institution information of the branch institution represented by the data source and the transaction data and the account data generated by the data source are queried, the institution information, the transaction data and the account data are input into the cache decision engine, and the object generation instruction and the object cache time information output by the cache decision engine are received, in the case that the object generation instruction indicates that the session hot object needs to be generated in advance, the session hot object is generated, and the session hot object is cached according to the object cache time information.

[0032] In the present disclosure, the session hot object that the customer is likely to perform can be cached in advance, data acquisition and processing are performed in advance, and a large amount of object generation time can be saved, thereby solving the technical problems of slow generation speed and large improvement cost of the group information object in the related art.

[0033] In the present disclosure, an intelligent and simple session object cache pre-fetching scheme is provided, which not only solves the problem of slow acquisition of the group information object of the financial institution, but also adapts to the generation and acquisition of various types of session hot objects.

[0034] In the present disclosure, the final generated memory object serialization result can be saved in byte form, and the business data cache is more intelligent and flexible.

[0035] Meanwhile, in the present disclosure, the data acquisition and processing flow does not need to be modified, and only the acquisition method of the session hotspot object needs to be modified to pre-cache the generated session hotspot object, thereby solving the problems in the prior art. BRIEF DESCRIPTION OF DRAWINGS

[0036] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:

[0037] Figure 1 is a flowchart of an optional cache method of a session hotspot object according to an embodiment of the present application;

[0038] Figure 2 is an interaction flow of an application server and an intelligent cache system according to another optional embodiment of the present application Figure 1 ;

[0039] Figure 3 is an interaction flow of an application server and an intelligent cache system according to another optional embodiment of the present application Figure 2 ;

[0040] Figure 4 is a schematic diagram of an optional cache device of a session hotspot object according to an embodiment of the present application;

[0041] Figure 5 is a hardware structure block diagram of an electronic device (or a mobile device) for a cache method of a session hotspot object according to an embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to enable persons skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings of the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work should fall within the scope of protection of the present application.

[0043] It should be noted that the terms "first", "second", and the like in the description and in the claims of the present application and in the above-described drawings are intended to distinguish similar objects and not necessarily describe a particular sequential or chronological order. It should be understood that the data thus used can be interchanged, where appropriate, so that the embodiments of the application described herein can be practiced in other than the illustrated or described order. Furthermore, the terms "comprise" and "have", and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product, or apparatus that comprises a list of steps or units is not necessarily limited to those steps or units that are clearly listed, but can include other steps or units that are not clearly listed or inherent to such processes, methods, products, or apparatuses.

[0044] For the convenience of those skilled in the art to understand the present application, the following explains some terms or nouns involved in the embodiments of the present application:

[0045] Group information object: a programming object (for example, a Java object) that stores information such as a customer branch, an account list, and the like.

[0046] Session hot spot object: a programming object that is stored in a session and is frequently read by a business function.

[0047] Cache miss: a hot spot data expires, causing a large number of requests to directly access the database through the cache.

[0048] Cache avalanche: a large number of cache data expire at the same time, causing a large number of requests to directly access the database through the cache.

[0049] It should be noted that the cache method and device for the session hot spot object in the present disclosure can be used in the field of artificial intelligence technology, and in the case of obtaining a group information object formed by a customer branch and pre-caching a session hot spot object (especially a larger object). In addition to the field of artificial intelligence technology, the cache method and device for the session hot spot object in the present disclosure can also be used in the case of obtaining a group information object formed by a customer branch and pre-caching a session hot spot object in any field. The application field of the cache method and device for the session hot spot object in the present disclosure is not limited.

[0050] It should be noted that the related information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present disclosure are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with the relevant laws, regulations and standards of the country and region, and provide corresponding operation portal for the user to choose authorization or refusal. For example, an interface is provided between the system and the related user or institution, and before obtaining the related information, the interface needs to send an acquisition request to the aforementioned user or institution, and after receiving the consent information fed back by the aforementioned user or institution, the related information is acquired.

[0051] The following embodiments of the present application can be applied to application systems of various financial institutions, for example, enterprise online banking systems, and can obtain customer information to process and generate group information objects by pre-acquiring data sources formed by each branch of the customer, and save them in the session. It overcomes the shortcomings of high modification cost and high program invasiveness of the existing scheme, and provides an intelligent and simple cache pre-fetching scheme for session hot objects. Not only solves the slow problem of group information object acquisition of the target application (for example, enterprise online banking application) of the financial institution, but also adapts to the generation and acquisition of other session hot large objects.

[0052] The present application will be described in detail below in conjunction with various embodiments.

[0053] Embodiment one

[0054] According to the embodiments of the present application, an embodiment of a cache method for session hot objects is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in a different order.

[0055] Figure 1 is a flowchart of an optional cache method for session hot objects according to the embodiments of the present application, as shown in Figure 1 The method comprises the following steps:

[0056] Step S101, obtaining the time period of the target customer using the target financial application, wherein the target customer contains N branch institutions, each branch institution represents a data source, all data sources are combined into a group information object, the data source indicates the source of data generated by the branch institution through the target financial application for financial transaction, and N is a positive integer greater than or equal to 1;

[0057] Step S102, at a cache specified time point before the time period, query the branch office information represented by the data source, and the transaction data and account data generated by the data source;

[0058] Step S103, input the branch office information, transaction data and account data into the cache decision engine, and receive the object generation instruction and object cache time information output by the cache decision engine, wherein the instruction information of the object generation instruction contains whether the session hot spot object needs to be generated in advance before the time period when the target customer uses the target financial application, and the session hot spot object indicates a programmed object with a financial service use frequency value greater than a first preset frequency threshold in the target session;

[0059] Step S104, in the case where the object generation instruction indicates that the session hot spot object needs to be generated in advance, generate the session hot spot object and cache the session hot spot object according to the object cache time information.

[0060] Through the above steps, when caching the session hot spot object of the customer, the time period when the target customer uses the target financial application is first obtained, at a cache specified time point before the time period, the branch office information represented by the data source and the transaction data and account data generated by the data source are queried, the branch office information, transaction data and account data are input into the cache decision engine, and the object generation instruction and object cache time information output by the cache decision engine are received, in the case where the object generation instruction indicates that the session hot spot object needs to be generated in advance, the session hot spot object is generated, and the session hot spot object is cached according to the object cache time information. In this embodiment, the session hot spot object that the customer is likely to perform can be cached in advance, data acquisition and processing are performed in advance, and a large amount of object generation time can be saved, thereby solving the technical problems of slow generation speed and large improvement cost in generating group information objects in the related art.

[0061] The present application will be described in detail below in combination with the above-mentioned implementation steps.

[0062] Step S101, obtain the time period when the target customer uses the target financial application, the target customer contains N branch offices, each branch office represents a data source, and all data sources are combined into a group information object, and the data source indicates the source of data generated by the branch office through the target financial application for financial transaction.

[0063] Optionally, the time period when the target customer uses the target financial application is determined by at least one of the following time periods: pay day, tax filing day, settlement day. Of course, the time period involved in the present embodiment can also be determined by other time information, such as temporary transfer time period, billing day.

[0064] By analyzing the time period of the target financial application used by the customer, the use time habit of the customer using the target financial application is queried, and the use time habit can be used to decide whether to generate the customer session hot spot object in advance, generate the customer session hot spot object multiple times in advance, and the cache time of the customer session hot spot object according to the use data generated in the historical process of the customer before the time period arrives.

[0065] The target financial application described above includes but is not limited to an enterprise online banking system developed by a financial institution for use by various customers. The target financial application can provide various financial services for customers, such as transferring, remitting, depositing, and lending. Since each customer may include different branches, in order to simplify various business functions, obtain and use the branch of the customer, the account list and other data, the target financial application can query the data source represented by each branch when the customer logs in to use the financial application, obtain the customer information to process and generate a group information object, and save the object data of the group information object in the session.

[0066] Optionally, the target financial application in the embodiment of the application can be installed in a terminal used by the customer (or referred to as a cache front end), wherein the terminal can be integrated with an application server, and part of the data in the historical process of the customer using the target financial application can be collected in advance through the application server, such as the branch information of the branch represented by the data source and the transaction data and account data generated by the data source.

[0067] In step S102, the branch information of the branch represented by the data source and the transaction data and account data generated by the data source are queried at the cache specified time point before the time period arrives.

[0068] For example, the time period of the customer using the target financial application is from 9:00 to 17:00 on the 28th of each month. The cache specified time point can be set as from 6:00 to 8:00 on the 28th of each month, which is before the time period of the customer using the application, to determine whether the customer needs to cache data and whether the session hot spot object needs to be generated to generate the session in advance and obtain the operation record of the customer, and to decide whether the related data of the customer (including the transaction data and account data generated by the data source) needs to be cached.

[0069] The branch information of the branch includes the subordinate relationship between the branch and the total group of the customer, the branch name, the branch code, the branch manager, the number of branch employees, and the location of the branch. The transaction data includes but is not limited to the transaction date, the transaction amount, and the transaction object. The account data includes but is not limited to the account association relationship with the total group of the customer, the account belonging to the branch, the account card number, and the data of the financial transaction generated by the account.

[0070] Step S103, input the institution information, transaction data and account data to the cache decision engine, and receive the object generation instruction and object cache time information output by the cache decision engine.

[0071] The object cache time information is used to indicate the time information of caching the session hot spot object when the session hot spot object needs to be generated in advance.

[0072] Optionally, the cache decision engine can determine whether to generate the customer session hot spot object in advance, how long to generate the customer session hot spot object in advance and the customer session hot spot object cache time according to the time period of the next use of the target financial application by the customer when the institution information, transaction data and account data are obtained.

[0073] The session hot spot object can be a session object frequently used by the customer to use the target financial application. The session hot spot object is created by the target financial application installed on the terminal used by the customer, and various data in the application process is saved through the session. If a financial business function of the target financial application is frequently created by the customer, and the number of sessions is greater than a preset number threshold, the financial business function can be a session hot spot object, which needs to be cached in advance. For example, the session hot spot object is a Java object saved in the session and frequently read by the financial application.

[0074] It should be noted that, in order to solve the problem of machine learning cold start, a certain number of customer lists to be cached, a time to generate customer information objects and an update time of the cache are preset when the intelligent cache engine starts to work. The intelligent decision engine collects enough data for learning and constructs an initial decision engine, and then the initial decision engine starts to make intelligent cache decisions according to the recent operation records of the customer.

[0075] Optionally, the cache decision engine is determined by the following method: collecting the object size of the historical session hot spot object of each customer, the use time information generated during the use of the target financial application by the customer, and the update frequency value of the customer data, wherein the customer data includes transaction data and account data; the object size of the historical session hot spot object of the customer, the use time information and the update frequency value of the customer data are integrated into a customer historical information set; the customer historical information set is divided according to the use time information, and the initial decision engine is trained by the information set training segment obtained after the division and the corresponding use time information, wherein the customer historical information set after the division includes the information set training segment and the information set verification segment; in the case that the similarity value between the use time information output by the initial decision engine and the object information of the session hot spot object generated by the customer and the information set verification segment is greater than a preset similarity threshold, it is confirmed that the initial decision engine is trained, and the cache decision engine is obtained.

[0076] In this embodiment, an intelligent cache decision engine can be used, which uses the habit of customers to use the target financial application at fixed time periods, uses this rule, and combines human activity recognition algorithms based on machine learning to construct a cache decision engine from the dimensions of session hotspot object size, customer online banking usage habits, and customer data update frequency, so as to evaluate the time period of the next use of the target financial application by the customer, and to decide whether to generate the customer session hotspot object in advance, how long to generate the customer session hotspot object in advance, and the cache time of the customer session hotspot object.

[0077] After generating the cache decision engine, the intelligent cache decision engine needs to be adjusted and optimized continuously according to the use data changes of each customer.

[0078] Optionally, after obtaining the cache decision engine, the method further includes: taking each branch of the customer as a session object, querying the session data amount corresponding to each customer; and adjusting the cache decision engine based on the session data amount.

[0079] Optionally, the step of adjusting the cache decision engine based on the session data amount includes: in a case where the session data amount is less than a first preset data amount threshold, not caching the session hotspot object.

[0080] The optimization of the intelligent cache decision engine has the following direction: for customers with small session data amounts, not caching to improve data timeliness.

[0081] Optionally, the step of adjusting the cache decision engine based on the session data amount includes: in a case where the session data amount is greater than or equal to a first preset data amount threshold but less than a second preset data amount threshold, and the update frequency value of the customer data of the customer is greater than a second preset frequency threshold, reducing the cache time length of the session hotspot object and increasing the update frequency of the session hotspot object, wherein the second preset data amount threshold is greater than the first preset data amount threshold.

[0082] The optimization of the intelligent cache decision engine has the following direction: for customers with large session data amounts and frequent business data updates, reducing the cache time of the session hotspot object and increasing the update frequency of the session hotspot object to improve the timeliness of the cached business data.

[0083] Optionally, the step of adjusting the cache decision engine based on the session data amount includes: in a case where the session data amount is greater than or equal to a second preset data amount threshold and the update frequency value of the customer data of the customer is less than or equal to a second preset frequency threshold, increasing the cache time length of the session hotspot object and reducing the update frequency of the session hotspot object.

[0084] The tuning of the intelligent cache decision engine has the following directions: for the client with large session data and infrequent business data update, increasing the session hot object cache time and reducing the session hot object update frequency to save system resources.

[0085] Optionally, after inputting the institution information, transaction data and account data into the cache decision engine, the method further comprises: the cache decision engine reading the historical operation records of the client pre-cached in the message queue, wherein the message queue pre-records the operation information of the client in the historical process; and the cache decision engine outputting the object generation instruction based on the historical operation records of the client and the institution information, transaction data and account data.

[0086] The embodiment provides the message queue, which is used for the cache decision engine to asynchronously collect the client behavior data and avoids the cache decision engine from becoming a system bottleneck.

[0087] In step S104, the session hot object is generated and cached according to the object cache time information in the case that the object generation instruction indicates that the session hot object needs to be pre-generated.

[0088] Optionally, after the session hot object is cached according to the object cache time information, the method further comprises: performing serialization processing on the object data of the session hot object; and distributedly storing the serialized byte data of the session hot object.

[0089] The embodiment provides the distributed cache, which can store the serialized byte data of the session hot object and provides high-time-efficiency and high-availability data storage.

[0090] The application will be described in detail below in combination with another optional embodiment.

[0091] The application scheme realizes an intelligent cache system, which caches the session hot object according to the use habit of the client, and the system mainly comprises the following modules:

[0092] The application server is used for illustrating the target financial application of the enterprise online bank, and the application server collects data, caches the client data and generates the session object.

[0093] The intelligent cache front end is the front end of the intelligent cache decision engine, which is used for collecting the data required by the intelligent cache decision engine, providing the decision result of the intelligent cache decision engine and the cache content.

[0094] Intelligent cache decision engine: Enterprise online banking customers often use enterprise online banking in fixed time periods, such as salary day, tax day, settlement day, etc. Using this rule, combined with human activity recognition algorithm of machine learning, the intelligent cache system constructs an intelligent cache decision engine from the dimensions of session hotspot object size, customer online banking usage habits, customer data update frequency, etc. to evaluate the time when the customer next uses the enterprise online banking, and to decide whether to generate the customer session hotspot large object in advance, how long to generate the customer session hotspot large object in advance, and the cache time of the customer's session hotspot large object.

[0095] Message queue: used for the intelligent decision engine to asynchronously collect customer behavior data, avoiding the cache decision engine from becoming a system bottleneck.

[0096] Distributed cache: stores the serialized byte data of the session hotspot object, provides high timeliness and high availability data storage, and can be realized based on redis (remote dictionary service).

[0097] The interaction process of each module in the intelligent cache system for customers who need to cache data and customers who do not need to cache data is described below.

[0098] Figure 2 is an optional application server and intelligent cache system interaction process according to an embodiment of the application Figure 1 , as shown in Figure 2 , for customers who do not need to cache data, the process includes:

[0099] 1. The application server receives a session creation request. The session creation request is generated after the customer clicks on a certain business function in the enterprise online banking on the terminal.

[0100] 2. The application server queries the intelligent cache front end whether there is object caching.

[0101] 3. The intelligent cache front end queries the intelligent cache decision engine whether there is cache data.

[0102] 4. The intelligent cache decision engine returns no cache data.

[0103] 5. The intelligent cache decision engine responds to the application server that there is no cache data for the customer.

[0104] 6. The application server obtains the customer data of the customer.

[0105] 7. The application server generates a session object.

[0106] 8. After the application server confirms that the session object has been generated, the application server sends the session object to the intelligent cache front end.

[0107] 9. The intelligent cache front end queries the message queue for the customer operation record associated with the customer based on the session object.

[0108] 10. The message queue returns the customer operation record to the intelligent cache decision engine.

[0109] Wherein the intelligent cache decision engine asynchronously obtains the customer operation record from the message queue to decide whether the cache is needed.

[0110] Through the flow shown in Figure 2 , for the customers who do not need to cache data, the cache data of the customers does not need to be read, the customer data can be directly obtained, the session creation request sent by the terminal used by the customer in real time is responded, the session object is generated, after the generation of the session object is completed, the operation record of the customer can be stored in the message queue through the session object, and preparation is made for subsequent judgment of whether the session hotspot object needs to be generated in advance and the customer data needs to be cached.

[0111] Figure 3 is another optional application server and intelligent cache system interaction flow according to an embodiment of the application Figure 2 , as shown in Figure 3 , for the customers who need to cache data, the flow includes:

[0112] 1. The application server receives a session creation request. Wherein the session creation request is a session request generated after the customer clicks a business function in the enterprise online banking on the terminal.

[0113] 2. The application server inquires the intelligent cache front end whether there is an object cache.

[0114] 3. The intelligent cache front end inquires the intelligent cache decision engine whether there is cache data.

[0115] 4. The intelligent cache decision engine judges that the customer needs to cache data according to the operation record in the historical process, and has called the application server to generate the session hotspot object, and reads the cache data of the customer from the distributed cache.

[0116] 5. The distributed cache returns the customer data of the customer cached to the intelligent cache decision engine.

[0117] 6. The intelligent cache decision engine returns the cache result to the intelligent cache front end.

[0118] 7. The intelligent cache front end returns the hotspot object of the customer to the application server.

[0119] 8. The application server generates a session according to the hotspot object of the customer.

[0120] 9. The application server completes the generation of the session.

[0121] 10. The intelligent caching frontend queries the message queue for customer operation records associated with the customer based on the session object.

[0122] 11. The message queue returns client operation records to the intelligent cache decision engine.

[0123] The intelligent caching decision engine asynchronously retrieves customer operation records from the message queue to decide whether caching is necessary.

[0124] pass Figure 3 The process shown involves generating a session hotspot object for customers who need to cache data, since they have already generated a lot of historical operation records and need to cache these records. Then, it responds to the session creation request sent in real time by the terminal used by the customer and generates a session object. After the session object is generated, the latest operation record generated by the customer can be stored in the message queue through the session object, preparing for the next determination of whether to generate a session hotspot object in advance and cache customer data.

[0125] To address the cold start problem in machine learning, the intelligent caching system in this embodiment pre-determines a certain number of customers to be cached, the time for generating customer information objects, and the cache update time when it first starts working. After the intelligent decision engine collects enough data for learning and forms an intelligent model, the intelligent caching decision engine begins to make intelligent caching decisions based on the customer's recent operation records.

[0126] Optionally, after obtaining the intelligent caching decision engine, this embodiment can adjust the engine in the following directions: For customers with small amounts of session data, do not cache to improve data timeliness. For customers with large amounts of session data and frequent business data updates, reduce the caching time of hot session objects and increase the update frequency of hot session objects to improve the timeliness of caching business data. For customers with large amounts of session data and infrequent business data updates, increase the caching time of hot session objects and reduce the update frequency of hot session objects to save system resources. The specific strategy is determined by the intelligent caching engine.

[0127] Through the above implementation methods, business data caching becomes more intelligent and flexible. The intelligent caching system can save the serialized result of the final generated memory object in byte form. Simultaneously, by pre-generating session hotspot objects, data acquisition and processing can be performed in advance. Compared with caching schemes that only cache data, the final effect is not limited by complex data processing logic, saving more time.

[0128] Meanwhile, integrating with the intelligent caching system does not require modifying the data acquisition and processing flow; only the method for acquiring hot objects needs to be modified. When subsequent business logic changes, there is no need to re-integrate, resulting in lower modification and maintenance costs.

[0129] The application will be described below in connection with another alternative embodiment.

[0130] Embodiment two

[0131] The cache device of the session hot spot object provided in this embodiment includes a plurality of implementation units, each of which corresponds to each implementation step in Embodiment One.

[0132] Figure 4 is a schematic diagram of an alternative cache device of a session hot spot object according to an embodiment of the application, as shown in the cache device of the session hot spot object can include an acquisition unit 40, a query unit 41, an input unit 42, and a cache unit 43, wherein, Figure 4

[0133] The acquisition unit 40 is configured to acquire a time period during which a target customer uses a target financial application, wherein the target customer includes N branch offices, each branch office represents a data source, all data sources are combined into a group information object, the data source indicates the source of data generated by the branch office through the target financial application for financial transactions, and N is a positive integer greater than or equal to 1.

[0134] The query unit 41 is configured to query, at a cache specified time point before the time period, branch office information represented by the data source and transaction data and account data generated by the data source.

[0135] The input unit 42 is configured to input the branch office information, the transaction data, and the account data to a cache decision engine and receive object generation instructions and object cache time information output by the cache decision engine, wherein the instruction information of the object generation instructions includes whether a session hot spot object needs to be generated in advance before the target customer uses the target financial application in the time period, and the session hot spot object indicates a programmed object with a financial service usage frequency value greater than a first preset frequency threshold in a target session.

[0136] The cache unit 43 is configured to generate the session hot spot object when the object generation instructions indicate that the session hot spot object needs to be generated in advance, and cache the session hot spot object according to the object cache time information.

[0137] ​The cache device of the session hotspot object can, when caching the session hotspot object of the client, first acquire the time period in which the target client uses the target financial application through the acquisition unit 40, query the branch office information represented by the data source, the transaction data and the account data generated by the data source at the cache specified time point before the time period is reached through the query unit 41, input the branch office information, the transaction data and the account data to the cache decision engine through the input unit 42, and receive the object generation instruction and the object cache time information output by the cache decision engine. In the case where the object generation instruction indicates that the session hotspot object needs to be generated in advance, the session hotspot object is generated through the cache unit 43, and the session hotspot object is cached according to the object cache time information. In this embodiment, the session hotspot object that the client is likely to perform can be cached in advance, data acquisition and processing are performed in advance, and a large amount of object generation time can be saved, thereby solving the technical problems of slow generation speed and high modification cost in generating group information objects in the related art.

[0138] Optionally, the cache device of the session hotspot object further comprises a serialization unit configured to perform serialization processing on object data of the session hotspot object after the session hotspot object is cached according to the object cache time information; and a storage unit configured to store byte data of the serialized session hotspot object in a distributed manner.

[0139] Optionally, the cache decision engine is determined by: collecting object size of historical session hotspot objects of each client, use time information generated during use of the target financial application by the client, and update frequency value of client data, wherein the client data includes transaction data and account data; integrating the object size of the historical session hotspot objects of the client, the use time information and the update frequency value of the client data into a client historical information set; dividing the client historical information set according to the use time information, training an initial decision engine with information set training fragments obtained after the division and corresponding use time information; and confirming that the initial decision engine is trained completely and obtaining the cache decision engine in the case where the similarity value between the use time information output by the initial decision engine and object information of the session hotspot object generated by the client and the information set verification fragment is greater than a preset similarity threshold.

[0140] Optionally, the cache device of the session hotspot object further comprises a first query module configured to query the amount of session data corresponding to each client with each branch office of the client as a session object after the cache decision engine is obtained; and an adjustment unit configured to adjust the cache decision engine based on the amount of session data.

[0141] Optionally, the adjustment unit comprises a non-caching module configured to not cache the session hotspot object in the case where the amount of session data is less than a first preset data amount threshold.

[0142] Optionally, the adjusting unit comprises a first adjusting module configured to, in a case that the session data volume is greater than or equal to the first preset data volume threshold but less than the second preset data volume threshold, and the update frequency value of the customer data of the customer is greater than the second preset frequency threshold, decrease the cache duration of the session hot object and increase the update frequency of the session hot object, wherein the second preset data volume threshold is greater than the first preset data volume threshold.

[0143] Optionally, the adjusting unit comprises a second adjusting module configured to, in a case that the session data volume is greater than or equal to the second preset data volume threshold and the update frequency value of the customer data of the customer is less than or equal to the second preset frequency threshold, increase the cache duration of the session hot object and decrease the update frequency of the session hot object.

[0144] Optionally, after the institution information, the transaction data and the account data are input into the cache decision engine, the method further comprises: the cache decision engine reading the historical operation record of the customer pre-cached in a message queue, wherein the message queue pre-records operation information of the customer in a historical process; and the cache decision engine outputting the object generation instruction based on the historical operation record of the customer and the institution information, the transaction data and the account data.

[0145] Optionally, the time period in which the target customer uses the target financial application is determined by a time period of at least one of: a salary payment day, a tax filing day, and a settlement day.

[0146] The cache device of the session hot object described above can further comprise a processor and a memory, and the acquisition unit 40, the query unit 41, the input unit 42, and the cache unit 43 are all stored in the memory as program units, and the corresponding functions are realized by the processor executing the program units stored in the memory.

[0147] The processor described above comprises a kernel, and the kernel calls the corresponding program units in the memory. The kernel can be set to one or more, and the kernel parameters are adjusted to generate the session hot object when the object generation instruction indicates that the session hot object needs to be pre-generated, and the session hot object is cached according to the object cache time information.

[0148] The memory described above can comprise a non-permanent memory in a computer readable medium, a random access memory (RAM) and / or a non-volatile memory such as a read-only memory (ROM) or a flash memory (flash RAM), and the memory comprises at least one memory chip.

[0149] The application further provides a computer program product adapted to execute the program of the following method steps when executed on a data processing device: obtaining a time period during which a target customer uses a target financial application, wherein the target customer comprises N branch offices, each branch office represents a data source, all data sources are combined into a group information object, the data source indicates a source of data generated by the branch office through the target financial application for financial transactions, and N is a positive integer greater than or equal to 1; querying office information of the branch office represented by the data source and transaction data and account data generated by the data source at a specified cache time point before the time period is reached; inputting the office information, the transaction data and the account data into a cache decision engine, and receiving object generation instructions and object cache time information output by the cache decision engine, wherein the instruction information of the object generation instructions comprises whether a session hot spot object needs to be generated in advance before the target customer uses the target financial application during the time period, and the session hot spot object indicates a programmed object with a financial service use frequency value greater than a first preset frequency threshold in a target session; and in the case that the object generation instructions indicate that the session hot spot object needs to be generated in advance, the session hot spot object is generated, and the session hot spot object is cached according to the object cache time information.

[0150] According to another aspect of the embodiments of the present application, a computer readable storage medium is also provided, which comprises a stored computer program, wherein the computer readable storage medium controls the device where the computer readable storage medium is located to execute the above-mentioned cache method of the session hot spot object when the computer program is running.

[0151] According to another aspect of the embodiments of the present application, an electronic device is also provided, which comprises one or more processors and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the above-mentioned cache method of the session hot spot object.

[0152] Figure 5 is a hardware structure block diagram of an electronic device (or a mobile device) for a cache method of a session hot spot object according to an embodiment of the present application. As shown in Figure 5 , the electronic device can include one or more (adopt 502a, 502b, …, 502n to show in the Figure 5 processor 502 (the processor 502 can include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 504 for storing data. In addition, it can also include a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which can be included as one of the ports of the I / O interface), a network interface, a keyboard, a power supply and / or a camera. Those skilled in the art can understand that Figure 5The shown structure is only schematic and the electronic device is not limited to the structure shown. For example, the electronic device can further include more or less components than those shown, or have a different configuration of components than shown. Figure 5 The electronic device can include more or less components than those shown, or have a different configuration of components than shown. Figure 5 The electronic device can include more or less components than those shown, or have a different configuration of components than shown.

[0153] The above-mentioned embodiment numbers of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.

[0154] In the above-described embodiments of the present application, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.

[0155] In several embodiments provided in the present application, it should be understood that the disclosed technical contents can be implemented by other ways. Among them, the above-described device embodiments are only schematic, for example, the division of the units can be a logical function division, and actual implementation can have another division way, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed units can be indirect coupling or communication connection through some interfaces, units or modules, which can be electrical or other forms.

[0156] The units described as separate components can or can not be physically separated, and the components displayed as units can or can not be physical units, that is, they can be located in one place, or can be distributed to multiple units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiment scheme.

[0157] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The above integrated unit can be realized in the form of hardware or in the form of software functional unit.

[0158] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, essentially or in other words, the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a number of instructions to make a computer device (which can be a personal computer, a server or a network device, etc.) execute all or part of the steps of the methods described in various embodiments of the present application. The aforementioned storage medium includes: a U disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.

[0159] The above is only the preferred embodiment of the present application, and it should be pointed out that for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, and these improvements and refinements should be considered as the protection scope of the present application.

Claims

1. A cache method of a session hotspot object, characterized by, The method comprises the following steps: acquiring a time period in which a target client uses a target financial application, wherein the target client comprises N branch offices, each of the branch offices represents a data source, all the data sources are combined into a group information object, the data source indicates a source of data generated by the branch office through the target financial application for financial transactions, and N is a positive integer greater than or equal to 1; querying office information of the branch office represented by the data source, transaction data and account data generated by the data source at a specified time point before the time period is reached; inputting the office information, the transaction data and the account data into a cache decision engine, and receiving object generation instructions and object cache time information output by the cache decision engine, wherein the instruction information of the object generation instructions comprises whether a session hotspot object needs to be generated in advance before the target client uses the target financial application in the time period, and the session hotspot object indicates a programmed object with a financial service use frequency value greater than a first preset frequency threshold in a target session; in a case where the object generation instructions indicate that the session hotspot object needs to be generated in advance, generating the session hotspot object and caching the session hotspot object according to the object cache time information; wherein the cache decision engine is determined by the following method: collecting object size of historical session hotspot objects of each client, use time information generated during use of the target financial application by the client, and update frequency value of client data, wherein the client data comprises transaction data and account data; integrating the object size of the historical session hotspot objects of the client, the use time information and the update frequency value of the client data into a client historical information set; segmenting the client historical information set according to the use time information, training an initial decision engine with an information set training segment obtained after segmentation and corresponding use time information, wherein the client historical information set after segmentation comprises an information set training segment and an information set verification segment; in a case where a similarity value between use time information output by the initial decision engine and object information of a session hotspot object generated by the client is greater than a preset similarity threshold, confirming that the initial decision engine is trained, and obtaining the cache decision engine.

2. The method of claim 1, wherein, After caching the session hotspot object according to the object cache time information, the method further comprises the following steps: serializing object data of the session hotspot object; distributively storing byte data of the serialized session hotspot object.

3. The method of claim 1, wherein, After obtaining the cache decision engine, the method further comprises the following steps: querying a session data amount corresponding to each client with each branch office of the client as a session object; adjusting the cache decision engine based on the session data amount.

4. The method of claim 3, wherein, The step of adjusting the cache decision engine based on the session data amount comprises: in a case where the session data amount is less than a first preset data amount threshold, not caching the session hotspot object.

5. The method of claim 3, wherein, The step of adjusting the cache decision engine based on the session data amount comprises: In a case where the session data amount is greater than or equal to a first preset data amount threshold but less than a second preset data amount threshold, and the update frequency value of the customer data of the customer is greater than a second preset frequency threshold, the cache time length of the session hot spot object is reduced, and the update frequency of the session hot spot object is increased, wherein the second preset data amount threshold is greater than the first preset data amount threshold.

6. The method of claim 5, wherein, The step of adjusting the cache decision engine based on the session data amount comprises: In a case where the session data amount is greater than or equal to the second preset data amount threshold and the update frequency value of the customer data of the customer is less than or equal to the second preset frequency threshold, the cache time length of the session hot spot object is increased, and the update frequency of the session hot spot object is reduced.

7. The method of claim 1, wherein, After inputting the institution information, the transaction data and the account data into the cache decision engine, further comprising: The cache decision engine reads the historical operation records of the customer pre-cached in a message queue, wherein the message queue pre-records operation information of the customer in a historical process; The cache decision engine outputs the object generation instruction based on the historical operation records of the customer and the institution information, the transaction data and the account data.

8. The method of claim 1, wherein, The time period in which the target customer uses the target financial application is determined by the time period of at least one of the following: a salary payment day, a tax filing day, and a settlement day.

9. A cache apparatus of a session hotspot object, characterized by, Comprise: An acquisition unit is configured to acquire a time period in which a target customer uses a target financial application, wherein the target customer comprises N branch institutions, each of the branch institutions represents a data source, all the data sources are combined into a group information object, the data source indicates a source of data generated by the branch institution through the target financial application for financial transactions, and N is a positive integer greater than or equal to 1; A query unit is configured to query institution information of a branch institution represented by the data source, and transaction data and account data generated by the data source at a cache specified time point before the time period is reached; An input unit is configured to input the institution information, the transaction data and the account data into a cache decision engine, and receive an object generation instruction and object cache time information output by the cache decision engine, wherein instruction information of the object generation instruction comprises whether a session hot spot object needs to be pre-generated before the time period in which the target customer uses the target financial application, and the session hot spot object indicates a programming object with a financial service use frequency value greater than a first preset frequency threshold in a target session; A cache unit is configured to generate the session hot spot object in a case where the object generation instruction indicates that the session hot spot object needs to be pre-generated, and cache the session hot spot object according to the object cache time information. The cache decision engine is determined by the following way: The object size of each customer's historical session hot spot object, the use time information generated during the customer's use of the target financial application, and the update frequency value of the customer data are collected, wherein the customer data comprises transaction data and account data. The object size of the historical session hotspot object of the client, the use time information and the update frequency value of the client data are integrated into a client historical information set; The client historical information set is segmented according to the use time information, and an information set training segment and corresponding use time information training are obtained by segmentation, wherein the segmented client historical information set comprises an information set training segment and an information set verification segment; If the similarity value between the use time information output by the initial decision engine and the object information of the client generated session hotspot object and the information set verification segment is greater than a preset similarity threshold, it is confirmed that the initial decision engine is trained, and the cache decision engine is obtained.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium comprises a stored computer program, wherein the computer readable storage medium controls the device where the computer readable storage medium is located to execute the cache method of the session hotspot object according to any one of claims 1 to 8 when the computer program runs.

11. An electronic device, comprising: The computer readable storage medium comprises a stored computer program, wherein the computer readable storage medium controls the device where the computer readable storage medium is located to execute the cache method of the session hotspot object according to any one of claims 1 to 8 when the computer program runs. The computer readable storage medium comprises a stored computer program, wherein the computer readable storage medium controls the device where the computer readable storage medium is located to execute the cache method of the session hotspot object according to any one of claims 1 to 8 when the computer program runs.

Images