Data storage method, device, equipment, storage medium and program product

Abstract

The application discloses a data storage method, device, equipment, storage medium and program product. The data storage method comprises the following steps: acquiring user data corresponding to a first user; performing data statistics on the user data from multiple dimensions respectively to obtain a target data set under a target dimension, the target dimension comprising at least one dimension in the multiple dimensions; determining a target unified identifier corresponding to the first user under the target dimension, wherein the unified identifiers corresponding to the same user under different dimensions are different; storing data in the target data set into a target data table corresponding to the target dimension in a target database based on the target unified identifier, and updating or adding information corresponding to the target unified identifier in a data item in the target data table. According to the embodiment of the application, the user data of the same user can be uniformly managed, and then user expansion and data sharing between different channels or products are facilitated.

Description

Technical Field

[0001] This application belongs to the field of information management technology, and in particular relates to a data storage method, apparatus, device, storage medium and program product. Background Technology

[0002] As times change, companies accumulate more and more user data, and how to store this user data is an important part of the user data management process.

[0003] Currently, because the collected user data may come from different channels or products, user data is usually stored in different databases using different identification methods according to the different data sources. As a result, it is not possible to manage the user data of the same user in a unified manner when managing user data later, and it is also not convenient to expand users and share data between different channels or products. Summary of the Invention

[0004] This application provides a data storage method, apparatus, device, storage medium, and program product that can uniformly manage user data of the same user, thereby facilitating user expansion and data sharing across different channels or products.

[0005] In a first aspect, embodiments of this application provide a data storage method, the method comprising:

[0006] Retrieve user data corresponding to the first user;

[0007] The user data is statistically analyzed from multiple dimensions to obtain a target data set under the target dimension, wherein the target dimension includes at least one of the multiple dimensions.

[0008] Under the target dimension, a unified target identifier corresponding to the first user is determined, wherein the unified identifier corresponding to the same user is different under different dimensions;

[0009] Based on the target unified identifier, the data in the target data set is stored in the target database in the target data table corresponding to the target dimension, so as to update or add information corresponding to the target unified identifier in the data items in the target data table.

[0010] Secondly, embodiments of this application provide a data storage device, the device comprising:

[0011] The data acquisition module is used to acquire user data corresponding to the first user;

[0012] The data statistics module is used to perform data statistics on the user data from multiple dimensions to obtain a target data set under the target dimension, wherein the target dimension includes at least one of the multiple dimensions.

[0013] The identifier determination module is used to determine a unified identifier corresponding to the first user under the target dimension, wherein the unified identifier corresponding to the same user is different under different dimensions;

[0014] The data storage module is used to store the data in the target data set into the target data table corresponding to the target dimension in the target database based on the target unified identifier, so as to update or add information corresponding to the target unified identifier in the data items in the target data table.

[0015] Thirdly, embodiments of this application provide an electronic device, which includes: a processor and a memory storing computer program instructions;

[0016] When the processor executes the computer program instructions, it implements the steps of the data storage method as described in any embodiment of the first aspect.

[0017] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the steps of the data storage method as described in any embodiment of the first aspect.

[0018] Fifthly, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform the steps of the data storage method as described in any embodiment of the first aspect.

[0019] The data storage method, apparatus, device, storage medium, and program product in this application embodiment perform data statistics on the user data corresponding to the first user obtained from multiple preset dimensions to obtain a target data set under the target dimension. A unified target identifier corresponding to the first user is determined under the target dimension, and then, based on the unified target identifier, the data in the target data set is stored in the target database in the target data table corresponding to the target dimension. Thus, by uniformly identifying the data of the same user under different dimensions and storing it in the same target database, this application embodiment facilitates unified management of the same user's data from multiple dimensions based on the unified identifier under each dimension during subsequent data management. Furthermore, since the unified identifier of the user in this application embodiment is not related to the data source—that is, user data from different channels or products are uniformly identified and stored according to unified rules—it facilitates user expansion and data sharing between different channels or products. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart illustrating a data storage method provided in one embodiment of this application;

[0022] Figure 2 This is an architecture diagram of the deployment scheme provided in this application;

[0023] Figure 3 This is a data structure relationship diagram for the authorized business scenario provided in this application;

[0024] Figure 4 This is a flowchart illustrating the user authorization method provided in this application;

[0025] Figure 5 This is a schematic diagram of the structure of a data storage device provided in one embodiment of this application;

[0026] Figure 6 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0027] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0028] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0029] With the advent of the data era, businesses need to build lasting relationships with users by collecting user data in order to maintain customer relationships, reduce operating costs, maximize profits, and minimize losses from user churn and waste from ineffective business decisions. This requires businesses to manage user data from different channels or products in a unified manner, that is, to uniformly manage services for all customer groups, effectively associate users, and unify user value so as to efficiently share and expand value within the enterprise.

[0030] However, currently, user data from different channels or products uses different identification methods and is stored separately in the databases of each product or channel. As a result, it is impossible to manage the user data of the same user in a unified manner when managing user data later, and it is also not convenient to expand users and share data between different channels or products.

[0031] To address the aforementioned technical challenges, this application's embodiments construct a unified user system. This system enables the fusion and unified management of user data from different channels or products, facilitating cross-channel and cross-product access based on a comprehensive user base. It establishes a comprehensive person-account-card relationship network for user data from various channels that has not yet been effectively integrated and correlated, thereby realizing the value of user data. Based on this, it further promotes joint operations, user acquisition, and traffic sharing during business development and user expansion. To promote the fusion of various types of users centrally and categorized in the user system, and to achieve information correlation, a comprehensive, dynamic, cross-channel, and multi-level person-account-card relationship network is constructed. By building a unified user system, a user information service capability list is created, forming a unified and standardized interface service that supports unified access by business systems across products and channels.

[0032] Based on this unified user system, embodiments of this application provide a data storage method, apparatus, device, storage medium, and program product. This data storage method can be applied to scenarios involving the unified identification and storage of user data. The data storage method provided in this application embodiment is described below.

[0033] Figure 1 This is a schematic flowchart of a data storage method provided in one embodiment of this application. This data storage method can be executed by the device hosting the unified user system.

[0034] like Figure 1 As shown, this data storage method may specifically include the following steps:

[0035] S110. Obtain the user data corresponding to the first user;

[0036] S120. Perform data statistics on user data from multiple dimensions to obtain a target data set under the target dimension, where the target dimension includes at least one of the multiple dimensions.

[0037] S130. Determine the unified identifier of the target corresponding to the first user under the target dimension, wherein the unified identifier of the same user is different under different dimensions;

[0038] S140. Based on the unified target identifier, store the data in the target data set into the target data table in the target database corresponding to the target dimension, so as to update or add information corresponding to the unified target identifier in the data items in the target data table.

[0039] Therefore, by statistically analyzing the user data corresponding to the first user from multiple preset dimensions, a target data set under the target dimension is obtained. A unified target identifier corresponding to the first user is determined under the target dimension. Then, based on this unified target identifier, the data in the target data set is stored in the target database in the target data table corresponding to the target dimension. In this way, by uniformly identifying the data of the same user under different dimensions and storing it in the same target database, this embodiment of the application facilitates unified management of the same user's data from multiple dimensions based on the unified identifier under each dimension during later data management. Furthermore, since the unified identifier of the user in this embodiment is not related to the data source, that is, user data from different channels or products are uniformly identified and stored according to unified rules, it facilitates user expansion and data sharing between different channels or products.

[0040] The specific implementation methods for each of the above steps are described below.

[0041] In some implementations, in S110, the user data corresponding to the first user may include basic personal information such as the user's name, ID number, mobile phone number, and bank card number, as well as business-related information such as device manufacturer and application information.

[0042] The methods for obtaining user data corresponding to the first user include, but are not limited to, retrieving existing user data corresponding to the first user from the existing original database, or obtaining incremental user data corresponding to the first user sent by each application platform when the user conducts business using various application platforms; no limitation is made here. The original database can be a database used by each application platform to store user data, or an existing database corresponding to the user type to store user data; no limitation is made here.

[0043] Here, user types can include registered users, authorized users, and card-based users. Registered users are users acquired through registration (e.g., users who register on the target application software), authorized users are users acquired through authorization (e.g., users who authorize the target application service), and card-based users are users acquired through bank card transactions (e.g., users who have previously completed bank card binding transactions).

[0044] In some implementations, the above-mentioned S110 may specifically include:

[0045] Receive the first user data associated with the first user sent by the first application platform;

[0046] Using the first identifier information in the first user data as the search keyword, determine whether there is second user data associated with the first user in the original database, wherein the first identifier information is the identifier information corresponding to the preset identifier type;

[0047] If it is determined that second user data exists, the second user data is obtained, and the first user data and the second user data are used as user data corresponding to the first user.

[0048] If it is determined that there is no second user data, the first user data will be used as the user data corresponding to the first user.

[0049] Here, the user data to be stored can be incremental user data corresponding to the first user sent by the first application platform, i.e., the first user data. The first application platform can be an application platform corresponding to a front-end business system. Taking authorization business as an example, this application platform can be the authorizing party corresponding to the authorized user, such as a network payment platform, an interconnection platform, or other service platforms.

[0050] For example, a first user can perform operations such as registration or authorization through the first application platform, and then the first application platform can send the first user data obtained from user registration or authorization to the unified user system. In this way, the unified user system can receive the first user data sent by the first application platform.

[0051] In addition, the preset identifier type can be a unique identifier type, such as a mobile phone number, ID card number, bank card number, device number, etc. Correspondingly, the first identifier information can be a mobile phone number, ID card number, bank card number, or device number included in the first user data.

[0052] In some specific examples, if the first user data includes a mobile phone number, then the mobile phone number can be used as a search keyword to query the original database to see if there is existing user data corresponding to the first user, i.e., the second user data. If the first user data includes an ID card number, then the ID card number can be used as a search keyword to query the original database to see if there is second user data associated with the first user.

[0053] If a second user data set exists, it indicates that the first user is an existing user. The second user data can be retrieved from the original database and stored together with the first user data as the user data to be stored in the target database. The second user data can be obtained from the database corresponding to the first application platform, or from the database corresponding to another application platform; this is not limited here.

[0054] If the second user data does not exist, it means that the first user is a new user, and the second user data can be stored as user data to be stored in the target database.

[0055] In this way, by determining from the original database whether there is second user data associated with the first user, and if there is second user data, storing the received first user data and the second user data in the original database together as user data to be stored in the target database, it is possible to uniformly identify existing data and incremental data according to a unified rule and store them in the same database when there is existing data. This facilitates the unified management of user data in the later stages.

[0056] In some implementations, in S120, the multiple dimensions may include at least two of the following: natural person dimension, mobile phone number dimension, bank card dimension, and device dimension. The natural person dimension is a dimension for data statistics and identification based on the natural person; the mobile phone number dimension is a dimension for data statistics and identification based on the mobile phone number; the bank card dimension is a dimension for data statistics and identification based on the bank card number; and the device dimension is a dimension for data statistics and identification based on the device fingerprint.

[0057] For example, user data can be classified and statistically analyzed from multiple preset dimensions. For instance, based on an individual, data related to that individual can be extracted from the user data to obtain a data set under the "individual" dimension. Similarly, based on a mobile phone number, data related to that number can be extracted from the user data to obtain a data set under the "mobile phone number" dimension, and so on. In this way, all or some of these dimensions, i.e., the target dimensions, can be obtained, corresponding to the target data set. Each dimension can correspond to one data set.

[0058] In some implementations, the above-mentioned S120 may specifically include:

[0059] Based on the identifier type corresponding to each of the multiple dimensions, the identifier information corresponding to the identifier type is obtained from the user data. Different dimensions correspond to different identifier types.

[0060] Once the identifier information corresponding to the identifier type is obtained, the dimension is taken as the target dimension, and multiple data related to the identifier information are obtained from the user data as the target data set under the target dimension.

[0061] Here, one dimension can correspond to one identifier type. When there is identifier information in the user data that corresponds to a certain identifier type, the dimension can be determined as the target dimension. Then, the identifier information can be used to obtain multiple data related to the identifier information from the user data, forming a target data set under the target dimension.

[0062] For example, the identifier type corresponding to the natural person dimension can be, for example, an ID number and ID type; the identifier type corresponding to the mobile phone number dimension can be, for example, a mobile phone number; the identifier type corresponding to the device dimension can be, for example, a device fingerprint; and the identifier type corresponding to the bank card dimension can be, for example, a bank card number.

[0063] In some specific examples, taking the natural person dimension as an example, the document number corresponding to the preset document type can be obtained from the user data first. For example, if the user data is the real name information of the first user, including the first user's ID card number, the ID card number can be obtained, and other data associated with the ID card number can be extracted based on the ID card number, such as name, gender, date of birth, etc., and then these data can be used as the data in the target data set under the natural person dimension.

[0064] In some implementations, in S130, different unified identifiers can be set for the data of the same user under different dimensions, so that user data can be added, deleted, modified and queried from different dimensions in the later data management process.

[0065] Furthermore, within a single dimension, a single user can correspond to one or more unified identifiers, without limitation. For example, under the mobile phone number dimension and the natural person dimension, a user can correspond to one unified identifier, while under the device dimension and the bank card dimension, a user can correspond to multiple unified identifiers.

[0066] For example, it can be first determined whether there is a unified identifier corresponding to the first user in the target data table corresponding to the target dimension in the target database. If it exists, there is no need to create a new unified identifier for the first user; if it does not exist, a unified identifier is created for the first user.

[0067] Based on this, in some implementations, the above-mentioned S130 may specifically include:

[0068] Based on the user data, determine whether there exists a target unified identifier corresponding to the first user;

[0069] In the absence of a unified target identifier corresponding to the first user, a unified target identifier corresponding to the first user is created under the target dimension using the identifier information corresponding to the target identifier type as the primary key, wherein the target identifier type is the identifier type corresponding to the target dimension.

[0070] For example, the identifier information in the user data corresponding to the preset identifier type can be matched with the existing data in the target data table corresponding to the target dimension in the target database. If the same information exists, it can be determined that a unified target identifier corresponding to the first user already exists under the target dimension. If the same information does not exist, it can be determined that a unified target identifier corresponding to the first user does not exist under the target dimension.

[0071] Taking the natural person dimension as an example, if the user data contains identification information, such as an ID card number, this ID card number can be used to determine whether it exists in the corresponding data table. If the ID card number exists, the unified identifier corresponding to that ID card number can be used as the unified natural person identifier for the first user under the natural person dimension. If the ID card number does not exist, the ID card number and ID card type can be used as primary keys to create a unified natural person identifier for the first user under the natural person dimension. Note that a single real user with multiple identification documents can be considered as multiple natural persons.

[0072] Taking the mobile phone number dimension as an example, if the user data contains a mobile phone number, this mobile phone number can be used to determine whether the mobile phone number exists in the data table corresponding to the mobile phone number dimension. If the mobile phone number exists, the unified identifier corresponding to the mobile phone number can be determined as the unified mobile phone number identifier corresponding to the first user under the mobile phone number dimension. If the mobile phone number does not exist, the mobile phone number can be used as the primary key, and a unified mobile phone number identifier corresponding to the first user can be created under the mobile phone number dimension.

[0073] Taking the bank card dimension as an example, if the user data contains a bank card number, this bank card number can be used to determine whether the bank card number exists in the corresponding data table. If the bank card number exists, the unified identifier corresponding to that bank card number can be determined as the unified bank card identifier for the first user under the bank card dimension. If the bank card number does not exist, the bank card number can be used as the primary key to create a unified bank card identifier for the first user under the bank card dimension.

[0074] Taking the device dimension as an example, if the user data contains device information, such as the SEID and device fingerprint corresponding to the application set on the user's mobile phone, this device information can be used to determine whether the device information exists in the data table corresponding to the device dimension. If the device information exists, the unified identifier corresponding to the device information can be determined as the unified device identifier corresponding to the first user under the device dimension. If the device information does not exist, the SEID and device fingerprint can be used as primary keys to create a unified device identifier corresponding to the first user under the device dimension.

[0075] Thus, through the above process, a unified identifier for the target corresponding to the first user under the target dimension can be obtained, which facilitates the storage and management of user data based on the unified identifier for the target.

[0076] In addition, in some embodiments, the data storage method provided in this application may further include:

[0077] Obtain the unified identifiers corresponding to the first user, excluding the target unified identifier;

[0078] The target unified identifier is associated with other unified identifiers and stored together.

[0079] Here, in this embodiment of the application, the unified identifiers corresponding to the same user under various dimensions can also be associated and stored. Specifically, after creating the target unified identifier corresponding to the first user under the target dimension, other unified identifiers corresponding to the first user under other dimensions can also be associated.

[0080] In some specific examples, after creating a unified mobile phone number identifier for the first user, the unified natural person identifier, unified bank card identifier, etc., corresponding to the data source can be associated from a preset unified identifier mapping table based on the source of the user data. The data source information (such as product or channel information and the user account identifier information used by the first user) is then recorded in the unified identifier mapping table. Specifically, the structure of this unified identifier mapping table can be shown in Table 1 below:

[0081] Table 1

[0082]

[0083] In this way, by storing unified identifiers across various dimensions, it becomes easier to perform data queries and other operations using the relationships between unified identifiers during later user data management, thus facilitating unified data management.

[0084] In some implementations, in S140, after determining the target unified identifier, the storage location in the target data table can be determined based on the target unified identifier, and then the target data set can be stored in the corresponding storage location in the target data table. Different dimensions in the target database can correspond to different data tables, and the target data table can be the data table in the target database corresponding to the target dimension.

[0085] Here, the target database can be a database used to store user data after unified identification, and this database can correspond to the data source of the user data.

[0086] Based on this, in some embodiments, prior to S140 above, the data storage method provided in this application embodiment may further include:

[0087] Identify the target application platform for acquiring user data;

[0088] The database corresponding to the target application platform is determined from multiple databases and used as the target database. One database corresponds to one or more application platforms.

[0089] Here, this application provides centralized and distributed deployment schemes. The centralized deployment scheme involves multiple application platforms sharing the same application and data layers, meaning multiple application platforms share a single database for data storage. The distributed deployment scheme, on the other hand, deploys the application and data layers independently, meaning each application platform uses its own database for data storage. For example, application platforms with high security requirements can be deployed independently, meaning they can use a separate database for data storage, while application platforms with lower security requirements can share a single database for data storage.

[0090] It's important to note that regardless of the deployment scheme described above, the entire unified user system uses only one access layer. This alters the existing routing rules from the access layer to the application layer, exposing only a single interface and using application platform keyword configuration for routing, making it seamless for front-end business systems. See details below. Figure 2 The architecture diagram shown illustrates that platform a has its own dedicated service layer and data layer, and uses a separate database A. Platforms b and c share a dedicated service layer and data layer, and both platforms use the same database B.

[0091] In some specific examples, if the user data comes from platform a, then based on the platform a identifier and the preset database correspondence table, the corresponding database A can be determined as the target database for storing the user data; if the user data comes from platform b or platform c, then based on the platform b or platform c identifier and the preset database correspondence table, the corresponding database B can be determined as the target database for storing the user data.

[0092] In this way, by using centralized and distributed deployment schemes, based on the target application platform for acquiring user data, a database corresponding to the target application platform is determined from multiple databases as the target database, and the data is stored in the target database. This can achieve the purpose of data fusion storage of different business systems while ensuring the security requirements of personalized data storage.

[0093] In addition, in some implementations, the target data table may include data items corresponding to at least one attribute of the application platform, application scenario, and user account.

[0094] Here, this application embodiment introduces a user construction and storage scheme that combines an application platform with application scenarios and user accounts. Taking the authorization business as an example, the application platform can be an authorization platform, the application scenario can be an authorization scenario, and the user account can be an entity account number.

[0095] For example, such as Figure 3 As shown, taking authorization as an example, the authorization platform can be the authorizing party corresponding to the authorized user, such as an online payment platform, an interoperability platform, or some authorized apps, all of which can be stored as an attribute in the target data table. Similarly, the authorization scenario can be a sub-scenario under the authorization platform. User data under different authorization scenarios can be distinguished through attribute values. For an authorization platform with only one authorization scenario, the authorization scenario is equivalent to the authorization platform. For example, in an online payment platform, an authorized user corresponds to only one scenario of the online payment platform. In addition, the entity account number can be an element used to distinguish different authorized users in each authorization scenario. In different scenarios, the entity account number can be a unique account identifier such as a mobile phone number, ID number, or card number. For example, in an online payment platform, user accounts are constructed based on natural persons, that is, ID numbers are used as entity account numbers to construct authorized users. In an interoperability platform, authorized users are constructed based on mobile phone numbers, so the entity account number is the mobile phone number.

[0096] Thus, the embodiments of this application can support the creation and maintenance of users under various authorized platforms, including online payment platforms, and support the split storage of data of the same user in different scenarios, so as to meet the needs of each authorized platform for dynamic changes in user elements.

[0097] In addition, in some implementations, the target data table may include a first type of data table and a second type of data table, wherein the first type of data table is used to store basic user data under the target dimension, and the second type of data table is used to store business extension data under the target dimension.

[0098] Here, the first type of data table can be a basic information table, used to store basic user data under the target dimension. The basic user data can be attribute data common to different business scenarios, such as card number, mobile phone number, etc.

[0099] The second type of data table can be an extended information table, used to store business extended data under the target dimension. The business extended data can be attribute data unique to each business scenario, such as application name, payment channel, device manufacturer, etc.

[0100] For multiple preset dimensions, a first type of data table and a second type of data table can be set up under each dimension.

[0101] In some implementations, the first type of data table includes data items corresponding to multiple user basic attributes under the target dimension;

[0102] Based on this, the aforementioned S140 may specifically include:

[0103] Extract user basic data corresponding to at least one user basic attribute from the target dataset;

[0104] Based on the unified target identifier, the user's basic data is stored in the data item corresponding to at least one user basic attribute in the first type of data table.

[0105] For example, taking the target dimension as the natural person dimension, the first type of data table may include data items corresponding to the user's basic attributes such as unified natural person identifier, name, document type, document number, date of birth, gender, creation source, and update source.

[0106] Taking the target dimension as the mobile phone number dimension as an example, the first type of data table may include data items corresponding to basic user attributes such as unified mobile phone number identifier, mobile phone number, network, operator, creation source, and update source.

[0107] Taking bank card as the target dimension as an example, the first type of data table may include data items corresponding to basic user attributes such as unified bank card number identifier, bank card number, card level, issuing institution, card type, creation source, and update source.

[0108] Taking the target dimension as the device dimension as an example, the first type of data table may include data items corresponding to user basic attributes such as unified device identifier, device number, device fingerprint, device manufacturer organization number, creation source, and update source.

[0109] In some specific examples, for the first type of data table under the natural person dimension, at least one piece of data such as user name, document type, document number, creation source, and update source can be extracted from the data set under the natural person dimension. Then, based on the unified natural person identifier, the corresponding storage location in the first type of data table can be found, and the extracted data can be stored in the data item of the corresponding attribute under that storage location. Data under other dimensions can be stored in a similar way as described above, and will not be elaborated further here.

[0110] In some embodiments, the above-mentioned S140 may further include:

[0111] Extract business extension data corresponding to at least one business extension attribute from the target dataset;

[0112] Based on the unified target identifier, business extension data is stored in the target database in the second type of data table corresponding to the target dimension.

[0113] For example, since different business scenarios may have their own unique attributes, namely business extended attributes, data corresponding to the specific attributes under the target dimension can be extracted from the target data set, namely business extended data, and then the data can be stored in the corresponding data item of the second type of data table.

[0114] In specific examples, for the second type of data table under the natural person dimension, business-specific extended data for each business scenario can be extracted from the dataset under the natural person dimension. For example, data corresponding to the application name attribute unique to user data obtained in business scenario A. Then, based on the determined unified natural person identifier, the corresponding storage location in the second type of data table is found, and the extracted data is stored in the data item of the corresponding attribute under that storage location. Data under other dimensions can also be stored in a similar manner, which will not be elaborated further here.

[0115] In this way, by setting up a first type of data table and a second type of data table, the common basic data of various business scenarios can be stored in one data table, while the unique business data can be stored in other data tables. This avoids the duplication of data common to each business scenario, thereby saving storage space.

[0116] To facilitate the extension of unique attributes for various business scenarios, in some implementations, the step of storing the extended business data in the target database based on the unified target identifier into a second-type data table corresponding to the target dimension may specifically include:

[0117] Based on the target unified identifier, at least one business extended attribute is stored in the first data item of the second type of data table;

[0118] For each business extension attribute, the business extension data is stored in the second data item of the second type of data table.

[0119] Here, in the second type of data table, a vertical table format can be used for storage to facilitate the storage of information related to business scenarios, in addition to basic user information, such as application name and device manufacturer. Attributes under each business scenario can be freely extended, meaning that data for different attributes of the same user can be stored as multiple records in the second type of data table. For example, as shown in Table 2 below, the attribute identifier (e.g., attribute name) of the extended business attributes under each business scenario can be stored in the "Attribute" data item (i.e., the first data item), while the extended business data corresponding to the extended business attributes can be stored in their respective "Value" data item (i.e., the second data item).

[0120] Table 2

[0121]

[0122]

[0123] In this way, no matter how the business scenario expands its unique attributes, they can all be stored in the second type of data table, which makes it convenient for each business scenario to expand its unique attributes without changing the data table structure.

[0124] In addition, in some implementations, the first type of data table includes target data items corresponding to service tag attributes. The character information stored in the target data items is used to identify the user's use of multiple preset service functions, wherein a preset service function corresponds to one or more character positions in the character information.

[0125] Here, since service tags are an important feature in user data, data administrators can clearly understand which service functions a user has used, such as which products a user has transacted with using a bank card. To this end, this application provides a functional bitmap, which can be a character information of a preset length, the length of which can be determined according to the number of service functions. This character information can include multiple characters, and the character position of each character can be 0 or 1, specifically defined by a preset data dictionary indicating which character position corresponds to which type of service function. A value of 1 indicates that the user has used that type of service function, such as making such a transaction; a value of 0 indicates that the user has not used that type of service function, such as not making such a transaction.

[0126] For example, if a bitmap (i.e. character information) is "01011", then according to the data dictionary, the user has used the second service function, the fourth service function, and the fifth service function.

[0127] Of course, a preset service function can also correspond to information of multiple character positions. For example, a preset service function can correspond to two character positions, and different values ​​of these two character positions can correspond to different usage states, thereby enabling the preset service function to be identified in multiple usage states.

[0128] In addition, the preset service functions can be expanded indefinitely; you only need to expand the length and fields of the bitmap.

[0129] In some implementations, the data storage method provided in this application may further include:

[0130] Determine whether the first user has used the target service function based on user data, wherein the target service function is any one of a plurality of preset service functions;

[0131] If it is determined that the first user has used the target service function, the target information stored in the target data item in the first type of data table is set as the first character information based on the target unified identifier.

[0132] If it is determined that the first user has not used the target service function, the target information stored in the target data item in the first type of data table is set as the second character information based on the target unified identifier.

[0133] Among them, the target information is the target character position information stored in the character information corresponding to the target unified identifier in the target data item, and the target character position is the character position corresponding to the target service function.

[0134] Here, the first character information could be, for example, "1", and the second character information could be, for example, "0".

[0135] For example, the method for determining character information can be as follows: based on the user data corresponding to the first user acquired each time, determine whether the first user has used any of the multiple preset service functions. If the user data shows that the first user has used a certain service function, such as the second service function, and the character position corresponding to the second service function is determined to be the second position according to the data dictionary, then the second character position in the character information corresponding to the target unified identifier stored in the first type of data table can be set to "1". If the user data shows that the first user has not used a certain service function, such as the fourth service function, and the character position corresponding to the fourth service function is determined to be the fourth position according to the data dictionary, then the fourth character position in the character information corresponding to the target unified identifier stored in the first type of data table can be set to "0", and so on, to determine the value corresponding to each character position in the character information.

[0136] In this way, all the service functions used by a user can be obtained with a single character message, which makes it easier to expand user services across different channels and applications during later data management, thus facilitating user management.

[0137] In addition, the target database in this embodiment can also be connected to omnichannel systems, QR code systems, and clearing and settlement systems to provide user data support services for various systems. While supporting online real-time query and write operations (within 10ms) of billions of data points, it can also support batch tasks of OLAP (Online Analytical Processing).

[0138] In addition, this application embodiment also designs a data fusion system for multiple types of users. This system consists of four layers: a source data layer, an extraction layer, an aggregation layer, and a processing layer. The source data layer comprises the various user types, such as registered users, authorized users, and card-based users. The source data layer is fused upwards through the extraction layer, which extracts the database table structures of all data sources across the entire user system. This data is then passed to the aggregation layer, where Kafka can be used as a high-performance fusion data bus. Finally, the data reaches the data fusion processing layer, where different data sources are fused to generate a unified identifier for individuals, users, and cards.

[0139] To better describe the overall solution, based on the above embodiments, we will take the authorization business scenario as an example and provide some specific examples.

[0140] For example, such as Figure 4 The flowchart shown illustrates the user authorization method. This user authorization method may include S401-S409, which will be explained in detail below.

[0141] S401, the user requests authorization from the front-end business system;

[0142] S402, the front-end business system sends user data obtained with user authorization to the unified user system via the network;

[0143] S403, the unified user system extracts the required data information from the data table from the user data;

[0144] S404, the unified user system classifies and records user data according to four dimensions: natural person, mobile phone number, bank card, and device number;

[0145] S405, the unified user system sends user data to the corresponding database for storage;

[0146] S406, the database records user data, completing the user binding process;

[0147] S407, the database returns the binding result to the unified user system;

[0148] S408, the unified user system returns the binding result to the front-end business system;

[0149] S409, the front-end business system returns an authorization success message to the user based on the binding result.

[0150] Furthermore, in the above process, the unified user system can provide front-end business systems with services for storing, querying, and modifying user data. The real-time performance and accuracy of the stored data should be guaranteed by the front-end business systems; the unified user system does not need to perform duplicate verifications.

[0151] It should be noted that the application scenarios described in the above embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0152] Based on the same inventive concept, this application also provides a data storage device. (Specifically combined with...) Figure 5 Please provide a detailed explanation.

[0153] Figure 5 This is a schematic diagram of the structure of a data storage device provided in one embodiment of this application.

[0154] like Figure 5 As shown, the data storage device 500 may include:

[0155] Data acquisition module 501 is used to acquire user data corresponding to the first user;

[0156] Data statistics module 502 is used to perform data statistics on the user data from multiple dimensions to obtain a target data set under the target dimension, wherein the target dimension includes at least one of the multiple dimensions;

[0157] The identifier determination module 503 is used to determine the target unified identifier corresponding to the first user under the target dimension, wherein the unified identifier corresponding to the same user is different under different dimensions;

[0158] The data storage module 504 is used to store the data in the target data set into the target data table in the target database corresponding to the target dimension based on the target unified identifier, so as to update or add information corresponding to the target unified identifier in the data items in the target data table.

[0159] The data storage device 500 described above will be described in detail below:

[0160] In some embodiments, the data acquisition module 501 specifically includes:

[0161] The data receiving submodule is used to receive the first user data associated with the first user sent by the first application platform;

[0162] The data retrieval submodule is used to determine whether there is second user data associated with the first user in the original database by using the first identification information in the first user data as the retrieval keyword, wherein the first identification information is identification information corresponding to a preset identification type;

[0163] The first processing submodule is used to obtain the second user data when it is determined that the second user data exists, and to use the first user data and the second user data as user data corresponding to the first user.

[0164] The second processing submodule is used to treat the first user data as the user data corresponding to the first user if it is determined that the second user data does not exist.

[0165] In some embodiments, the data statistics module 502 specifically includes:

[0166] The information acquisition submodule is used to acquire identifier information corresponding to the identifier type from the user data according to the identifier type corresponding to each of the multiple dimensions, wherein different dimensions correspond to different identifier types;

[0167] The collection acquisition submodule is used to, when the identification information corresponding to the identification type is obtained, take the dimension as the target dimension, and obtain multiple data associated with the identification information from the user data as the target data set under the target dimension.

[0168] In some embodiments, the identifier determination module 503 specifically includes:

[0169] The identifier determination submodule is used to determine whether there is a target unified identifier corresponding to the first user based on the user data;

[0170] The identifier creation submodule is used to create a target unified identifier corresponding to the first user under the target dimension, using the identifier information corresponding to the target identifier type as the primary key, when there is no target unified identifier corresponding to the first user. The target identifier type is the identifier type corresponding to the target dimension.

[0171] In some embodiments, the data storage device 500 further includes:

[0172] The identifier acquisition module is used to acquire other unified identifiers besides the target unified identifier corresponding to the first user;

[0173] The associated storage module is used to associate and store the target unified identifier with the other unified identifiers.

[0174] In some embodiments, the data storage device 500 further includes:

[0175] The platform determination module is used to determine the target application platform for obtaining the user data before storing the data in the target data set into the target data table corresponding to the target dimension in the target database based on the target unified identifier.

[0176] The target determination module is used to determine the database corresponding to the target application platform from multiple databases, and use it as the target database, wherein one database corresponds to one or more application platforms.

[0177] In some embodiments, the target data table includes a first type of data table and a second type of data table, wherein the first type of data table is used to store basic user data under the target dimension, and the second type of data table is used to store business extension data under the target dimension.

[0178] In some embodiments, the first type of data table includes data items corresponding to multiple user basic attributes under the target dimension;

[0179] The data storage module 504 includes:

[0180] The first extraction submodule is used to extract user basic data corresponding to at least one of the user basic attributes from the target data set;

[0181] The first storage submodule is used to store the user basic data into data items corresponding to at least one of the user basic attributes in the first type of data table based on the target unified identifier.

[0182] In some embodiments, the data storage module 504 further includes:

[0183] The second extraction submodule is used to extract business extension data corresponding to at least one business extension attribute from the target data set.

[0184] The second storage submodule is used to store the business extended data into the second type of data table in the target database corresponding to the target dimension, based on the target unified identifier.

[0185] In some embodiments, the second storage submodule includes:

[0186] The first storage unit is used to store the at least one business extension attribute into the first data item of the second type of data table based on the target unified identifier;

[0187] The second storage unit is used to store the business extension data into the second data item of the second type of data table, corresponding to the at least one business extension attribute.

[0188] In some embodiments, the first type of data table includes target data items corresponding to service tag attributes, and the character information stored in the target data items is used to identify the user's usage of multiple preset service functions, wherein one of the preset service functions corresponds to one or more character positions in the character information.

[0189] In some embodiments, the data storage device 500 further includes:

[0190] The judgment module is used to determine whether the first user has used the target service function based on the user data, wherein the target service function is any one of the plurality of preset service functions;

[0191] The first setting module is used to, when it is determined that the first user has used the target service function, set the target information stored in the target data item in the first type data table as the first character information based on the target unified identifier.

[0192] The second setting module is used to set the target information stored in the target data item in the first type data table as the second character information based on the target unified identifier when it is determined that the first user has not used the target service function.

[0193] The target information is the target character position information stored in the character information corresponding to the target unified identifier in the target data item, and the target character position is the character position corresponding to the target service function.

[0194] In some embodiments, the plurality of dimensions includes at least two of the following: natural person dimension, mobile phone number dimension, bank card dimension, and device dimension.

[0195] In some embodiments, the target data table includes data items corresponding to at least one attribute of the application platform, application scenario, and user account.

[0196] Therefore, by statistically analyzing the user data corresponding to the first user from multiple preset dimensions, a target data set under the target dimension is obtained. A unified target identifier corresponding to the first user is determined under the target dimension. Then, based on this unified target identifier, the data in the target data set is stored in the target database in the target data table corresponding to the target dimension. In this way, by uniformly identifying the data of the same user under different dimensions and storing it in the same target database, this embodiment of the application facilitates unified management of the same user's data from multiple dimensions based on the unified identifier under each dimension during later data management. Furthermore, since the unified identifier of the user in this embodiment is not related to the data source, that is, user data from different channels or products are uniformly identified and stored according to unified rules, it facilitates user expansion and data sharing between different channels or products.

[0197] Figure 6 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application.

[0198] The electronic device 600 may include a processor 601 and a memory 602 storing computer program instructions.

[0199] Specifically, the processor 601 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0200] Memory 602 may include mass storage for data or instructions. For example, and not limitingly, memory 602 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 602 may include removable or non-removable (or fixed) media. Where appropriate, memory 602 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 602 is non-volatile solid-state memory.

[0201] In certain embodiments, the memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Thus, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this application.

[0202] The processor 601 implements any of the data storage methods described in the above embodiments by reading and executing computer program instructions stored in the memory 602.

[0203] In some examples, electronic device 600 may also include communication interface 603 and bus 610. For example, Figure 6 As shown, the processor 601, memory 602, and communication interface 603 are connected through bus 610 and complete communication with each other.

[0204] The communication interface 603 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0205] Bus 610 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not as a limitation, bus 610 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 610 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0206] For example, the electronic device 600 can be a mobile phone, tablet computer, laptop computer, handheld computer, in-vehicle electronic device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc.

[0207] The electronic device 600 can execute the data storage method in the embodiments of this application, thereby achieving the combination Figure 1 and Figure 5 The data storage method and apparatus described.

[0208] Furthermore, in conjunction with the data storage methods in the above embodiments, this application embodiment can provide a computer-readable storage medium for implementation. This computer-readable storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the data storage methods in the above embodiments. Examples of computer-readable storage media include non-transitory computer-readable storage media, such as portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, etc.

[0209] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0210] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0211] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0212] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0213] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A data storage method, characterized in that, include: Retrieve user data corresponding to the first user; Based on the identifier type corresponding to each of the multiple dimensions, identifier information corresponding to the identifier type is obtained from the user data, wherein different dimensions correspond to different identifier types; When the identifier information corresponding to the identifier type is obtained, the dimension is taken as the target dimension, and multiple data associated with the identifier information are obtained from the user data as the target data set under the target dimension; Under the target dimension, a unified target identifier corresponding to the first user is determined, wherein the unified identifier corresponding to the same user is different under different dimensions; Based on the target unified identifier, the data in the target data set is stored in the target database in the target data table corresponding to the target dimension, so as to update or add information corresponding to the target unified identifier in the data items in the target data table; Obtain other unified identifiers corresponding to the first user besides the target unified identifier; The target unified identifier is associated with and stored with the other unified identifiers, wherein the association relationship of unified identifiers in each dimension is recorded through a unified identifier correspondence table; The target data table includes a first type of data table and a second type of data table, wherein the first type of data table is used to store basic user data under the target dimension, and the second type of data table is used to store business extension data under the target dimension; The first type of data table includes target data items corresponding to service tag attributes. The character information stored in the target data items is used to identify the user's usage of multiple preset service functions. Each preset service function corresponds to one or more character positions in the character information. The character information stored in the target data items adopts a function bitmap.

2. The method according to claim 1, characterized in that, The acquisition of user data corresponding to the first user includes: Receive the first user data associated with the first user sent by the first application platform; Using the first identifier information in the first user data as the search keyword, determine whether there is second user data associated with the first user in the original database, wherein the first identifier information is identifier information corresponding to a preset identifier type; If it is determined that the second user data exists, the second user data is obtained, and the first user data and the second user data are used as user data corresponding to the first user; If it is determined that the second user data does not exist, the first user data shall be used as the user data corresponding to the first user.

3. The method according to claim 1, characterized in that, Determining the target unified identifier corresponding to the first user under the target dimension includes: Based on the user data, determine whether there exists a target unified identifier corresponding to the first user; In the absence of a unified target identifier corresponding to the first user, a unified target identifier corresponding to the first user is created under the target dimension using the identifier information corresponding to the target identifier type as the primary key, wherein the target identifier type is the identifier type corresponding to the target dimension.

4. The method according to claim 1, characterized in that, Before storing the data in the target data set into the target data table corresponding to the target dimension in the target database based on the target unified identifier, the method further includes: Determine the target application platform for acquiring the user data; The database corresponding to the target application platform is determined from multiple databases and used as the target database, wherein one database corresponds to one or more application platforms.

5. The method according to claim 1, characterized in that, The first type of data table includes data items corresponding to multiple user basic attributes under the target dimension; The step of storing the data in the target data set into the target data table corresponding to the target dimension in the target database based on the target unified identifier includes: Extract user basic data corresponding to at least one of the user basic attributes from the target dataset; Based on the target unified identifier, the user basic data is stored in the first type of data table in the corresponding data item corresponding to at least one of the user basic attributes.

6. The method according to claim 5, characterized in that, The step of storing the data in the target data set into the target data table corresponding to the target dimension in the target database based on the target unified identifier further includes: Extract business extension data corresponding to at least one business extension attribute from the target data set; Based on the target unified identifier, the business extended data is stored in the target database in the second type of data table corresponding to the target dimension.

7. The method according to claim 6, characterized in that, The step of storing the business extension data in the target database corresponding to the second type of data table in the target database based on the target unified identifier includes: Based on the target unified identifier, the at least one business extension attribute is stored in the first data item of the second type of data table; Corresponding to the at least one business extension attribute, the business extension data is stored in the second data item of the second type of data table.

8. The method according to claim 1, characterized in that, The method further includes: Based on the user data, it is determined whether the first user has used the target service function, wherein the target service function is any one of the plurality of preset service functions; If it is determined that the first user has used the target service function, the target information stored in the target data item in the first type data table is set as the first character information based on the target unified identifier. If it is determined that the first user has not used the target service function, the target information stored in the target data item in the first type data table is set as the second character information based on the target unified identifier. The target information is the target character position information stored in the character information corresponding to the target unified identifier in the target data item, and the target character position is the character position corresponding to the target service function.

9. The method according to any one of claims 1-4, characterized in that, The multiple dimensions include at least two of the following: natural person dimension, mobile phone number dimension, bank card dimension, and device dimension.

10. The method according to any one of claims 1-4, characterized in that, The target data table includes data items corresponding to at least one of the following attributes: application platform, application scenario, and user account.

11. A data storage device, characterized in that, include: The data acquisition module is used to acquire user data corresponding to the first user; The information acquisition submodule is used to acquire the identifier information corresponding to the identifier type from the user data according to the identifier type corresponding to each of the multiple dimensions, wherein different dimensions correspond to different identifier types; The collection acquisition submodule is used to, when the identification information corresponding to the identification type is obtained, take the dimension as the target dimension and obtain multiple data associated with the identification information from the user data as the target data set under the target dimension; The identifier determination module is used to determine a unified identifier corresponding to the first user under the target dimension, wherein the unified identifier corresponding to the same user is different under different dimensions; The data storage module is used to store the data in the target data set into the target data table corresponding to the target dimension in the target database based on the target unified identifier, so as to update or add information corresponding to the target unified identifier in the data items in the target data table; The identifier acquisition module is used to acquire other unified identifiers besides the target unified identifier corresponding to the first user; An associated storage module is used to associate and store the target unified identifier with the other unified identifiers, wherein the association relationship of unified identifiers in each dimension is recorded through a unified identifier correspondence table; The target data table includes a first type of data table and a second type of data table, wherein the first type of data table is used to store basic user data under the target dimension, and the second type of data table is used to store business extension data under the target dimension; The first type of data table includes target data items corresponding to service tag attributes. The character information stored in the target data items is used to identify the user's usage of multiple preset service functions. Each preset service function corresponds to one or more character positions in the character information. The character information stored in the target data items adopts a function bitmap.

12. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the steps of the data storage method as described in any one of claims 1-10.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the steps of the data storage method as described in any one of claims 1-10.

14. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device causes the electronic device to perform the steps of the data storage method as described in any one of claims 1-10.

Images