User feature data acquisition method, system and device and medium
By building a user attribute library and analyzing and processing, the problem of low user feature data acquisition efficiency in a multi-service database environment is solved, comprehensive evaluation of user feature data and personalized business support is realized, and the stability and efficiency of the business system are improved. .
Patent Information
- Application Number
- CN202310502156.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-06
- Publication Date
- 2024-11-08
AI Technical Summary
In a multi-service database environment, it is difficult to quickly parse multi-dimensional user feature analysis results, which affects the stable operation of the business system and cannot effectively support personalized business customization and recommendation functions.
By building a user attribute library, synchronizing user basic data to the distributed file system using timed execution tasks, using computing engines and ETL tools for analysis and processing, obtaining user feature data, and ensuring the legitimacy of data access requests through verification mechanisms to obtain feature data .
It realizes a comprehensive evaluation of user characteristic data, improves the response efficiency and data acquisition efficiency of the business system, supports personalized business customization and recommendation functions, and avoids the need for the business system to process other business database data by itself.
Smart Images

Figure CN118916907A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the field of data processing technology, and in particular relates to a method, system, device and medium for acquiring user characteristic data. Background Art
[0002] At present, some companies involved in multiple businesses have multiple databases, storing various business data of users in different databases. However, it is difficult to fully evaluate the user's characteristic information by querying the report data of the business system from only one independent database, and it is impossible to provide data support for functions such as personalized business customization and business recommendation for users. In the case of multiple business databases and excessive business data volume, the business system cannot quickly parse out the multi-dimensional user characteristic analysis results, which easily affects the stable operation of the business system.
[0003] Therefore, it is necessary to provide a new method, system, device and medium for obtaining user characteristic data to solve the above technical problems. Summary of the invention
[0004] The purpose of the present invention is to provide a method for acquiring user characteristic data in order to solve the above-mentioned problem.
[0005] The present invention achieves the above-mentioned purpose through the following technical solutions:
[0006] A method for acquiring user characteristic data comprises the following steps:
[0007] Acquire user basic data, and build a user attribute library based on the user basic data;
[0008] Analyze and process the user basic data based on the user attribute library to obtain user feature data and store it in the user attribute library;
[0009] A data access request is obtained, and the legitimacy of the data access request is verified. After the verification, the user characteristic data matching the data access request is called from the user attribute library.
[0010] As a further optimization solution of the present invention, basic user data is obtained, and a user attribute library is constructed based on the basic user data. The specific process is as follows:
[0011] Based on the scheduled task execution function component, the user basic data within the preset time period is synchronized to the distributed file system in each business database to build a user attribute library; the preset time period is from the first day of the month to the day before the current time.
[0012] As a further optimization scheme of the present invention, the user basic data is analyzed and processed based on the user attribute library to obtain user feature data and store it in the user attribute library. The specific process is as follows:
[0013] The user attribute library uses a computing engine and ETL tools to perform conversion and filtering analysis on a large amount of user basic data, and then loads the processing results into the data warehouse according to a pre-defined data warehouse model. The processing results are the summarized user feature data.
[0014] As a further optimization scheme of the present invention, the user attribute library includes multiple servers. While synchronizing the user basic data to the distributed file system, the user basic data from different business databases are synchronized to different servers respectively. Each server uses a computing engine and an ETL tool to analyze and summarize the synchronized user basic data on the server, and then summarizes the analysis results of each server.
[0015] As a further optimization solution of the present invention, the distributed file system is a Hadoop distributed file system; and the computing engine adopts a SPARK computing engine.
[0016] As a further optimization solution of the present invention, the specific process of storing user feature data in the user attribute library is as follows:
[0017] The user characteristic data is saved in a temporary table of the user attribute library, and before the user basic data in each business database is synchronized to the user attribute library next time, the characteristic data stored in the temporary table is deleted.
[0018] As a further optimization solution of the present invention, a data access request is obtained, and the legitimacy of the data access request is verified. After verification, the user feature data matching the data access request is called from the user attribute library. The specific process is as follows:
[0019] Based on the interface of the user attribute library, obtaining a data access request issued by the business system;
[0020] Determine whether the IP address and the access key carried in the data access request are both present in the configuration file of the user attribute library;
[0021] If not, an error message will be displayed;
[0022] If yes, then obtaining attribute information in the data access request, the attribute information including data request parameters and an encrypted visitor signature;
[0023] Decrypting the visitor signature, determining whether the decrypted visitor signature is the same as the signature in the configuration file, and determining whether the data request parameter meets a preset condition;
[0024] If not all conditions are met, an error message will be displayed;
[0025] If all conditions are met, the data access request is determined to be legal, and the feature data matching the data access request is returned to the business system.
[0026] A method for acquiring user characteristic data, comprising:
[0027] Data acquisition module, used to obtain basic user data;
[0028] A construction module, used to construct a user attribute library based on the user basic data;
[0029] A data processing module, used to analyze and process the user basic data based on the user attribute library to obtain user feature data;
[0030] A storage module, used for storing the user characteristic data in the user attribute library;
[0031] A receiving module, used for obtaining a data access request;
[0032] A verification module, used to verify the legitimacy of the data access request;
[0033] The calling module is used to call the user characteristic data matching the data access request from the user attribute library after verification.
[0034] An electronic device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;
[0035] Memory, used to store computer programs;
[0036] The processor is used to implement the method for acquiring user characteristic data when executing the program stored in the memory.
[0037] A computer-readable storage medium stores a computer program, which implements a method for acquiring user characteristic data when executed by a processor.
[0038] The beneficial effects of the present invention are:
[0039] In the case of multiple business databases being separated, the present invention constructs a user attribute library that summarizes user basic data, and the analysis and summary process is performed in the user attribute library, so it will not affect the operation of the existing business system, and then quickly parses out the feature data corresponding to each user based on the calculation engine, thereby achieving a comprehensive evaluation of the user feature data; by using the interface to receive data access requests, each business system can easily obtain the user's feature data, and then can provide accurate data support for functions such as personalized business customization and business recommendation for users according to the different feature data corresponding to different users. At the same time, since the business system is prevented from having to perform conversion processing on the user basic data in other business databases, the efficiency of the business system in obtaining user feature data is improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] Figure 1 is a flow chart of the method of the present invention;
[0041] Figure 2 It is a system structure block diagram of the present invention;
[0042] Figure 3 It is a block diagram of the device structure of the present invention;
[0043] Figure 4 It is a block diagram of a computer storage medium of the present invention. DETAILED DESCRIPTION
[0044] The present application is further described in detail below in conjunction with the accompanying drawings. It is necessary to point out here that the following specific implementation methods are only used to further illustrate the present application and cannot be understood as limiting the scope of protection of the present application. Technical personnel in this field can make some non-essential improvements and adjustments to the present application based on the above application content.
[0045] like Figure 1 As shown, a method for obtaining user characteristic data includes the following steps:
[0046] S1: Obtain user basic data, and build a user attribute library based on the user basic data;
[0047] The specific process is as follows:
[0048] Based on the scheduled task execution function component, the user basic data within the preset time period is synchronized to the distributed file system in each business database to build a user attribute library; the preset time period is from the first day of the month to the day before the current time.
[0049] In this embodiment, the business database is used to manage and store data resources generated by the business system, and the data resources include user basic data. Among them, users refer to customers directly faced by the business, that is, user basic data is business information or basic information related to customers. For example, the user basic data generated by the life insurance underwriting system is the personal basic data of the policy customer. The user basic data generated by different business systems can be stored in different business databases.
[0050] After using Hadoop technology to synchronize the user basic data stored in each business database to the HDFS file system, since the user basic data includes the user's personal information and consumption information when handling different businesses, in essence, the HDFS file system that has the user basic data generated by each business system constitutes a user attribute library, which is also a database.
[0051] During the synchronization process of the above-mentioned user basic data, although there is a transmission time difference and real-time synchronization between the business database and the user attribute library cannot be maintained, since the user attribute library does not have high requirements for the real-time performance of resource data, the above-mentioned synchronization method of user basic data can meet the construction needs of the user attribute library.
[0052] JOB (scheduled task execution function component) is a function provided by the database to periodically execute a stored procedure or package body. In order for the HDFS file system to trigger synchronization operations, data synchronization is implemented at the database level through the SQLJOB scheduled job. The implementation principle includes: creating a data synchronization task through the JOB method, and setting the task execution time and task execution interval in the execution conditions corresponding to the data synchronization task. When the current time reaches the preset task execution time, or when the difference between the current time and the task execution time is a multiple of the task execution interval, the HDFS file system creates a database connection for connecting to each business database respectively. Thereafter, the SQL statement preset in the HDFS file system is executed. According to the syntax parsing result of the SQL statement, if the table parameters corresponding to the SQL statement exist in the business database, the HDFS file system reads the user basic data from the business database with the preset identity authority, and
[0053] The read user basic data is updated and inserted into the HDFS file system. The HDFS file system creates a database connection, including creating a dblink of a remote database. Based on the dblink approach, the HDFS file system can quickly obtain the user basic data of the remote business database as if accessing a local database, thereby improving synchronization efficiency. If the data that needs to be synchronized in the JOB-style data synchronization task is the user basic data generated by the business system within a preset time period, then when executing the data synchronization task, the HDFS file system will only synchronize the user basic data generated by the business system within the preset time period to the local. Preferably, the preset time period is from the first day of the month to before the current day. That is, the HDFS file system only synchronizes the user basic data generated by the business system from the 1st of each month to before the current day.
[0054] On the day when the data synchronization task is executed, since the day has not yet passed, the user basic data in the business database is still in a real-time update state. Therefore, in order to avoid the phenomenon that the HDFS file system and the business database are not actually synchronized after the HDFS file system is synchronized due to the update of the user basic data in the business database, the HDFS file system only synchronizes the user basic data generated by the business system before the day when executing the data synchronization task. In addition, in actual operation, since the validity period of the user's business is calculated in months, and the 31st of each month is the expiration date, most of the user basic data in the business database before the 1st of each month is historical data. In order to improve the synchronization effectiveness of the HDFS file system for user basic data, reduce the amount of synchronized data, and improve synchronization efficiency, the HDFS file system only synchronizes the user basic data generated by the business system from the 1st to the day of each month.
[0055] In the user attribute library, according to different user levels, user basic data is divided into ordinary level and important level. The user attribute library presets two JOB tasks, which are used to set the execution time of analysis and summary actions on ordinary level and important level user basic data respectively.
[0056] The user attribute library only performs analysis and summary operations on user basic data during non-busy access periods. By limiting the execution time of the analysis and summary actions of the user attribute library, it is ensured that when the business system issues a data access request, the user attribute library can respond in a timely manner, and will not occupy too many system resources due to analysis and summary operations, thereby improving the response efficiency of the user attribute library. By storing feature data in a temporary table, the consumption of memory resources in the user attribute library can be reduced. By regularly clearing the feature data in the temporary table, it is ensured that the amount of data in the temporary table is not too much, so that the user attribute library has better performance.
[0057] S2: Analyze and process the user basic data based on the user attribute library to obtain user feature data and store it in the user attribute library;
[0058] The specific process is as follows:
[0059] The user attribute library uses a computing engine and ETL tools to perform conversion and filtering analysis on a large amount of user basic data, and then loads the processing results into the data warehouse according to a pre-defined data warehouse model. The processing results are the summarized user feature data.
[0060] The user attribute library includes multiple servers. While synchronizing user basic data to the distributed file system, the user basic data from different business databases are synchronized to different servers respectively. Each server uses a computing engine and ETL tools to analyze and summarize the synchronized user basic data on the server, and then summarizes the analysis results of each server.
[0061] The distributed file system is the Hadoop distributed file system; the computing engine adopts the SPARK computing engine.
[0062] The specific process of storing user feature data in the user attribute library is as follows:
[0063] The user characteristic data is saved in a temporary table of the user attribute library, and before the user basic data in each business database is synchronized to the user attribute library next time, the characteristic data stored in the temporary table is deleted.
[0064] S3: Obtain a data access request, and verify the legitimacy of the data access request. After verification, call the user feature data matching the data access request from the user attribute library.
[0065] The specific process is as follows:
[0066] Based on the interface of the user attribute library, obtaining a data access request issued by the business system;
[0067] Determine whether the IP address and the access key carried in the data access request are both present in the configuration file of the user attribute library;
[0068] If not, an error message will be displayed;
[0069] If yes, then obtaining attribute information in the data access request, the attribute information including data request parameters and an encrypted visitor signature;
[0070] Decrypting the visitor signature, determining whether the decrypted visitor signature is the same as the signature in the configuration file, and determining whether the data request parameter meets a preset condition;
[0071] If not all conditions are met, an error message will be displayed;
[0072] If all conditions are met, the data access request is determined to be legal, and the feature data matching the data access request is returned to the business system.
[0073] When the user attribute library receives a data access request based on user feature data from any business system through the interface, it does not immediately return the user's feature data to the business system, but first determines whether the data access request is legal, including: determining whether the source of the data access request meets the preset data acquisition authority and determining whether the data content of the data access request has abnormal parameters. Only when the data access request is legal, the user attribute library queries and returns the user feature data requested by the business system. The user feature data requested by the business system is the feature data that matches the user number carried in the data access request. The user attribute library executes a query from the stored data based on the user number, and converts the feature data obtained from the query into data in XML format before returning it.
[0074] The specific implementation process is as follows:
[0075] It is determined whether the IP address and the access key carried in the data access request are both present in the configuration file of the user attribute library.
[0076] The user attribute library parses and processes the received data access request, reads the first attribute value corresponding to the source IP field and the second attribute value corresponding to the access key field from the datagram of the data access request, then the first attribute value is the IP address carried by the above data access request, indicating the IP address currently used by the business system that issued the data access request, and the second attribute value is the access key, indicating the account key entered by the operator of the business system.
[0077] During operation, the user attribute library will load the settings and files of the environment it needs, which is the configuration file. In order to verify the legitimacy of the data access request, the source IP address and access key that are allowed to obtain the user feature data are pre-saved in the configuration file. The legal IP addresses saved in the configuration file include precise IP addresses, IP address segments, or IP addresses expressed in wildcard form. As long as the user attribute library detects that the IP address carried by the data access request is the same as the IP address in the configuration file or belongs to any IP address segment in the configuration file, it can be determined that the IP address carried by the data access request exists in the configuration file of the user attribute library.
[0078] If the IP address and access key carried by the data access request are both present in the configuration file of the user attribute library, the attribute information in the data access request is obtained, and the attribute information includes the data request parameters and the encrypted visitor signature. The visitor signature is the key data attached to the data access request, or a transformation of the key data. The user attribute library uses a pre-agreed decryption key to decrypt the received visitor signature, thereby determining whether the source of the data access request is a real authorized user, and confirming the message integrity of the data access request, so that when receiving a data access request forged by criminals, the user attribute library can also identify it and not respond to the data access request, thereby improving the transmission security of user feature data.
[0079] If the IP address or access key carried in the data access request does not exist in the configuration file of the user attribute library, the user attribute library will not respond to the data access request.
[0080] The visitor signature is decrypted, and it is determined whether the decrypted visitor signature is the same as the signature in the configuration file, and whether the data request parameter meets a preset condition.
[0081] If the decrypted visitor signature is identical to the signature in the configuration file, and the data request parameters meet preset conditions, the data access request is determined to be legitimate, and the feature data matching the data access request is returned to the business system.
[0082] The preset conditions are grammatical structure rules, including character type attributes and value range intervals. Only when all data request parameters in the data access request meet the preset grammatical structure rules, the user attribute library determines that the data access request is legal and responds to the data access request, that is, according to the required user's feature data, after querying the user attribute library for the feature data corresponding to the user, it returns to the business system that issued the data access request.
[0083] If the decrypted visitor signature is different from the signature in the configuration file, and any data request parameter in the data access request does not meet the preset grammatical structure rules, the user attribute library generates an error prompt message and responds to the data access request based on the error prompt message.
[0084] When receiving a data access request, the user attribute library first determines whether the number of data access requests received in a first time period has reached a preset threshold. The first time period is a time interval from a certain moment before receiving the data access request to when the data access request is received, and the length of the first time period is a preset duration.
[0085] If the number of data access requests received within the first time period has reached the preset threshold, no response is made to the data access request received at the current moment, and the above steps S411 to S414 are not performed.
[0086] The user attribute library can judge the number of data access requests within a preset time period and not respond when the number exceeds the threshold, thus avoiding the user attribute library from continuously processing a large number of data access requests, controlling the processing frequency of data access requests, and ensuring the normal operation of the user attribute library. When the user attribute library provides external inquiries of user feature data, it uses views. The business system directly calls the view provided by the user attribute library through the above interface and can directly request to obtain the user feature data corresponding to the view. Therefore, when the stored data is adjusted inside the user attribute library, since the view and interface have not changed, the business system that calls the user feature data inside the user attribute library through the interface and view will not be affected, and the adjustment process is invisible to the business system.
[0087] As an embodiment of the present invention, another specific implementation process is described in detail as follows:
[0088] The IP address of the data access request is obtained.
[0089] Obtain the total number of historical data access requests based on the IP address within a preset time period.
[0090] According to the access log file, the user attribute library determines the number of source IP addresses of the data access requests received within the preset time period that are the same as the IP address in S421. The preset time period is the time interval from a certain moment before the data access request is received to the time when the data access request is received, and the length of the preset time period is the preset duration.
[0091] The detailed messages in the above log files record information such as the source time, request parameters, source IP address, processing time and processing results of each data access request by the user attribute library.
[0092] If the total number of historical data access requests based on the IP address within a preset time period is greater than a preset threshold, the data access requests are cached, and the legitimacy of the cached data access requests is verified after a preset delay.
[0093] If the total number of data access requests based on the IP address within a preset time period is greater than a first preset threshold and less than a second preset threshold, the data access request is cached. If the time for which the data access request has been cached in a pre-created cache area has reached a preset time period, the user attribute library verifies the legitimacy of the data access request.
[0094] If the total number of data access requests based on the IP address within the preset time period is greater than a second preset threshold, no response is made to the data access request.
[0095] If the data access request is legal, the feature data matching the data access request is returned to the business system.
[0096] like Figure 2 As shown, a method for obtaining user characteristic data includes:
[0097] Data acquisition module, used to obtain basic user data;
[0098] A construction module, used to construct a user attribute library based on the user basic data;
[0099] A data processing module, used to analyze and process the user basic data based on the user attribute library to obtain user feature data;
[0100] A storage module, used for storing the user characteristic data in the user attribute library;
[0101] A receiving module, used for obtaining a data access request;
[0102] A verification module, used to verify the legitimacy of the data access request;
[0103] The calling module is used to call the user characteristic data matching the data access request from the user attribute library after verification.
[0104] The implementation process of the functions and effects of each unit in the above system is specifically described in the implementation process of the corresponding steps in the above method, which will not be repeated here.
[0105] As for the system embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The system embodiment described above is only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of the present invention. Ordinary technicians in this field can understand and implement it without paying creative work.
[0106] In the above-mentioned embodiment, any multiple of all units can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least some functions of one or more of these modules can be combined with at least some functions of other modules and implemented in one module. At least one of all units can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation modes of software, hardware and firmware or in a suitable combination of any of them. Alternatively, at least one of all units can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be executed.
[0107] like Figure 3 As shown, an electronic device includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus;
[0108] Memory, used to store computer programs;
[0109] The processor is used to implement a method for acquiring user characteristic data when executing a program stored in the memory.
[0110] The above communication bus may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus may be divided into an address bus, a data bus, a control bus, etc.
[0111] The communication interface is used for communication between the above electronic device and other devices.
[0112] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.
[0113] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
[0114] like Figure 4 As shown, a computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, a method for acquiring user characteristic data is implemented.
[0115] The computer-readable storage medium may be included in the device / apparatus described in the above embodiment; or it may exist independently without being assembled into the device / apparatus. The above computer-readable storage medium carries one or more programs. When the above one or more programs are executed, a method for obtaining user characteristic data according to an embodiment of the present disclosure is implemented.
[0116] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.
[0117] The above-mentioned embodiments only express several implementation methods of the present invention, and the description thereof is relatively specific and detailed, but it cannot be understood as limiting the scope of the present invention. It should be pointed out that, for ordinary technicians in this field, several variations and improvements can be made without departing from the concept of the present invention, which all belong to the protection scope of the present invention.
Claims
1. A method for acquiring user characteristic data, applied to be executed on a server with a distributed file system installed, characterized in that: The following steps are involved: Acquire user basic data, and build a user attribute library based on the user basic data; Analyze and process the user basic data based on the user attribute library to obtain user feature data and store it in the user attribute library; A data access request is obtained, and the legitimacy of the data access request is verified. After the verification, the user characteristic data matching the data access request is called from the user attribute library.
2. The method for obtaining user characteristic data according to claim 1, characterized in that: Obtain user basic data and build a user attribute library based on the user basic data. The specific process is as follows: Based on the scheduled task execution function component, the user basic data within the preset time period is synchronized to the distributed file system in each business database to build a user attribute library; the preset time period is from the first day of the month to the day before the current time.
3. The method for obtaining user characteristic data according to claim 2, characterized in that: The user basic data is analyzed and processed based on the user attribute library to obtain user feature data and store it in the user attribute library. The specific process is as follows: The user attribute library uses a computing engine and ETL tools to perform conversion and filtering analysis on a large amount of user basic data, and then loads the processing results into the data warehouse according to a pre-defined data warehouse model. The processing results are the summarized user feature data.
4. The method for acquiring user characteristic data according to claim 3, characterized in that: The user attribute library includes multiple servers. While synchronizing user basic data to the distributed file system, the user basic data from different business databases are synchronized to different servers respectively. Each server uses a computing engine and ETL tools to analyze and summarize the synchronized user basic data on the server, and then summarizes the analysis results of each server.
5. A method for acquiring user characteristic data according to claim 3 or 4, characterized in that: The distributed file system is the Hadoop distributed file system; the computing engine adopts the SPARK computing engine.
6. The method for acquiring user characteristic data according to claim 1, characterized in that: The specific process of storing user feature data in the user attribute library is as follows: The user characteristic data is saved in a temporary table of the user attribute library, and before the user basic data in each business database is synchronized to the user attribute library next time, the characteristic data stored in the temporary table is deleted.
7. The method for acquiring user characteristic data according to claim 1, characterized in that: Obtain a data access request, and verify the legitimacy of the data access request. After verification, call the user feature data matching the data access request from the user attribute library. The specific process is as follows: Based on the interface of the user attribute library, obtaining a data access request issued by the business system; Determine whether the IP address and the access key carried in the data access request are both present in the configuration file of the user attribute library; If not, an error message will be displayed; If yes, then obtaining attribute information in the data access request, the attribute information including data request parameters and an encrypted visitor signature; Decrypting the visitor signature, determining whether the decrypted visitor signature is the same as the signature in the configuration file, and determining whether the data request parameter meets a preset condition; If not all conditions are met, an error message will be displayed; If all conditions are met, the data access request is determined to be legal, and the feature data matching the data access request is returned to the business system.
8. A method for acquiring user characteristic data, characterized in that: include: Data acquisition module, used to obtain basic user data; A construction module, used to construct a user attribute library based on the user basic data; A data processing module, used to analyze and process the user basic data based on the user attribute library to obtain user feature data; A storage module, used for storing the user characteristic data in the user attribute library; A receiving module, used for obtaining a data access request; A verification module, used to verify the legitimacy of the data access request; The calling module is used to call the user characteristic data matching the data access request from the user attribute library after verification.
9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory, used to store computer programs; The processor is used to implement the method for acquiring user characteristic data according to any one of claims 1 to 7 when executing the program stored in the memory.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for acquiring user characteristic data according to any one of claims 1 to 7 is implemented.
