Data processing method, device, equipment and storage medium
By comparing the identity to be matched in the identification file to be processed with the known mapping relationship information, the identity identity and account identification code are automatically matched, which solves the problems of low data processing efficiency and high cost in the existing technology, and realizes automatic matching , reduces costs and improves efficiency.
Patent Information
- Application Number
- CN202110276354.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-03-15
- Publication Date
- 2025-02-21
- Estimated Expiration
- 2041-03-15
AI Technical Summary
The method of mining mapping or association relationships between different IDs in the prior art has problems of low data processing efficiency and high cost.
By obtaining the to-process identification file, the identity to be matched in the identification file is compared with the identity identifier in the known mapping relationship information to obtain the matching result, including the identity identifier matching the account identification code and its corresponding account identification code , and output these account identification numbers.
It realizes automatic matching of identity identification and account identification code, reduces the cost of manual participation and improves data processing efficiency.
Smart Images

Figure CN113760904B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of big data technology, and in particular to a data processing method, apparatus, device and storage medium. Background Art
[0002] An identity document (ID) can be understood as a code used to mark a physical entity. Different types of IDs have different encoding methods. IDs can be numbers, letters, or a combination of numbers and letters. Since there are multiple types of IDs that identify users on the Internet, mining the mapping or association between different ID types can more accurately reach users with recommended information.
[0003] At present, the method of mining the mapping or association relationship between different IDs is that the operator actively analyzes and understands the source of the ID, determines the authority ownership of different ID sources, and then determines the mapping or association relationship between different IDs through interaction.
[0004] In the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art: since the sources of different IDs may be different, data from different sources cannot be shared based on the permission issues of different ID sources, and the solution of analyzing and mining the mapping or association relationships between different IDs by operators has the problems of low data processing efficiency and high cost. Summary of the invention
[0005] The embodiments of the present application provide a data processing method, apparatus, device and storage medium to solve the problems of low data processing efficiency and high cost in existing solutions for mining associations or mapping relationships between different IDs.
[0006] According to a first aspect of the present application, an embodiment of the present application provides a data processing method, including:
[0007] Acquire an identification file to be processed, the identification file comprising: at least one identity identification to be matched;
[0008] Comparing the at least one identity identifier to be matched with the identity identifiers in the known mapping relationship information to obtain a matching result, wherein the matching result includes: at least one first identity identifier matched to the account identification code and the account identification code corresponding to each first identity identifier;
[0009] Output the account identification code corresponding to each first identity identifier.
[0010] In a possible design of the first aspect, the method further includes:
[0011] Parsing the identification file to obtain the at least one identity identification to be matched;
[0012] Each identity to be matched is added to the known first identity relationship information to obtain second identity relationship information.
[0013] Optionally, the matching result further includes: at least one second identity identifier that is not matched to the account identification code;
[0014] Accordingly, the method further includes:
[0015] For each second identity identifier, determining whether there is a target identity identifier associated with the second identity identifier in the second identity identifier relationship information;
[0016] If yes, determining the target account identification code corresponding to the target identity identifier according to the target identity identifier and the known mapping relationship information;
[0017] The target account identification code is determined to be the account identification code corresponding to the second identity identifier.
[0018] Optionally, the method further includes:
[0019] The known mapping relationship information is updated according to the mapping relationship between the second identity identifier and the target account identification code.
[0020] In another possible design of the first aspect, before obtaining the identification file to be processed, the method further includes:
[0021] Get historical data collection;
[0022] Processing the data in the historical data set to obtain multiple identity identifiers included in the historical data set and mapping relationship data between the identity identifiers and the account identification codes;
[0023] Based on whether there is an association relationship between identity identifiers, classify and store each identity identifier in the historical data set to obtain first identity identifier relationship information;
[0024] The known mapping relationship information is generated based on the mapping relationship data between the identity identifier and the account identification code and the encoding type of the identity identifier.
[0025] Optionally, the first identity identifier relationship information is represented by an identity identifier relationship table, and the identities located in the same row in the identity identifier relationship table are identities with an associated relationship and belonging to different coding types, and the associated relationship includes at least one of the following relationships: belonging to the same device and belonging to the same user.
[0026] In another possible design of the first aspect, the method further includes:
[0027] Based on the account identification code corresponding to each first identity identifier, information is pushed to the device corresponding to the first identity identifier.
[0028] According to a second aspect of the present application, an embodiment of the present application provides a data processing device, including:
[0029] An acquisition module, used to acquire an identification file to be processed, wherein the identification file includes: at least one identity to be matched;
[0030] A processing module, configured to compare the at least one identity identifier to be matched with the identity identifiers in the known mapping relationship information to obtain a matching result, wherein the matching result includes: at least one first identity identifier matched to the account identification code and the account identification code corresponding to each first identity identifier;
[0031] The output module is used to output the account identification code corresponding to each first identity identifier.
[0032] In a possible design of the second aspect, the processing module is further used to:
[0033] Parsing the identification file to obtain the at least one identity identification to be matched;
[0034] Each identity to be matched is added to the known first identity relationship information to obtain second identity relationship information.
[0035] Optionally, the matching result further includes: at least one second identity identifier that is not matched to the account identification code;
[0036] Accordingly, the processing module is also used for:
[0037] For each second identity identifier, determining whether there is a target identity identifier associated with the second identity identifier in the second identity identifier relationship information;
[0038] If yes, determining the target account identification code corresponding to the target identity identifier according to the target identity identifier and the known mapping relationship information;
[0039] The target account identification code is determined to be the account identification code corresponding to the second identity identifier.
[0040] Optionally, the processing module is further used to update the known mapping relationship information according to the mapping relationship between the second identity identifier and the target account identification code.
[0041] In another possible design of the second aspect, the acquisition module is further used to acquire a historical data set before acquiring the identification file to be processed;
[0042] The processing module is further used for:
[0043] Processing the data in the historical data set to obtain multiple identity identifiers included in the historical data set and mapping relationship data between the identity identifiers and the account identification codes;
[0044] Based on whether there is an association relationship between identity identifiers, classify and store each identity identifier in the historical data set to obtain first identity identifier relationship information;
[0045] The known mapping relationship information is generated based on the mapping relationship data between the identity identifier and the account identification code and the encoding type of the identity identifier.
[0046] In another possible design of the second aspect, the output module is further used to push information to a device corresponding to each first identity identifier based on an account identification code corresponding to the first identity identifier.
[0047] According to the third aspect of the present application, an embodiment of the present application provides a data processing device, including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method described in the first aspect and various possible designs is implemented.
[0048] According to the fourth aspect of the present application, an embodiment of the present application provides a computer-readable storage medium, in which computer execution instructions are stored. When the computer execution instructions are executed by a processor, they are used to implement the method described in the first aspect and various possible designs.
[0049] According to the fifth aspect of the present application, an embodiment of the present application provides a computer program product, including: a computer program, the computer program is stored in a readable storage medium, at least one processor of a data processing device can read the computer program from the readable storage medium, and the at least one processor executes the computer program so that the data processing device executes the method described in the first aspect.
[0050] The data processing method, device, equipment and storage medium provided in the embodiment of the present application, after obtaining the identification file to be processed, compares at least one identity to be matched included in the identification file with the identity in the known mapping relationship information to obtain a matching result, the matching result includes: at least one first identity matched to the account identification code and the account identification code corresponding to each first identity, and finally outputs the account identification code corresponding to each first identity. The technical solution realizes the automatic matching of the identity (ID) and the account identification code (PIN), does not require manual participation, reduces costs, and improves data processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0052] Figure 1 A schematic diagram of an application scenario of the data processing method provided in an embodiment of the present application;
[0053] Figure 2 A flowchart of a first embodiment of the data processing method provided by the present application;
[0054] Figure 3 A schematic diagram of the interface for uploading identification files to be processed;
[0055] Figure 4 A schematic diagram of the storage format of the identity identifier to be matched in the identification file provided in the embodiment of the present application;
[0056] Figure 5 A flowchart of a second embodiment of the data processing method provided in the present application;
[0057] Figure 6 A flowchart of a third embodiment of the data processing method provided in the present application;
[0058] Figure 7 A schematic diagram of the structure of an embodiment of a data processing device provided by the present application;
[0059] Figure 8 A schematic diagram of the structure of an embodiment of a data processing device provided in this application.
[0060] The above drawings show clear embodiments of the present disclosure, which will be described in more detail below. These drawings and text descriptions are not intended to limit the scope of the present disclosure in any way, but to illustrate the concepts of the present disclosure to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0061] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.
[0062] At present, with the rapid development of network technology, there are many types of IDs that identify users on the network, mainly including user business accounts (such as personal identification numbers (PIN)), equipment information (such as mobile phone international mobile equipment identity (IMEI) number), and user registration information (such as email, phone). At present, many e-commerce websites are actively accumulating and storing IDs as data assets. At the same time, according to traffic behavior logs, they establish a mapping relationship between user business account PINs and the other two types of IDs (hereinafter, for the purpose of distinction, the first type of user business account is directly referred to as account PIN, and ID mainly refers to the other two types. In fact, these three types all belong to the category of ID).
[0063] Since ID data and mapping relationship data can help the operation team of e-commerce enterprises reach the crowd through account PIN or device, and can also help the algorithm team of e-commerce enterprises to further analyze and mine, establish the relationship between users, such as person-to-person relationship map and same-person identification, the accumulated ID types and quantities and the mapping relationship between ID and account PIN are very important, which is the cornerstone for further establishing the user relationship identification algorithm.
[0064] However, due to the large number of ID types, different IDs are stored in different teams or departments’ data platforms due to technical or permission issues, or the same type of IDs may be distributed in different departments’ data platforms, for example, one part is stored in the data platform of department A, and the other part is stored in the data platform of department B. At present, the method of mining the mapping or association relationship between different IDs is for operators to actively understand the source of the ID, determine the authority of different ID sources, and then determine the mapping or association relationship between different IDs through interaction. However, the disadvantages of this method are passive work, high communication costs, and low data processing efficiency.
[0065] In response to the above technical problems, the technical conception process of the present application is as follows: Based on the manual collection and sedimentation of existing ID data assets, the current ID data assets have begun to take shape. Now some IDs have established a two-way mapping relationship with the account PIN, and the known mapping relationship information has been obtained. Therefore, after the business personnel obtain the user's identity (for example, device ID) from different channels, they can determine the account PIN corresponding to the identity based on the known mapping relationship information. That is, by productizing the mapping requirement function of the ID data, the ID collection work is changed from passive to active. Based on the existing ID data set, after establishing a two-way mapping relationship between some IDs and PINs, for IDs obtained from different sources, the PINs corresponding to certain IDs can be determined. At the same time, by utilizing the relationship between IDs, the number of mappings between IDs and PINs can also be increased.
[0066] Based on the above technical concept, the embodiment of the present application provides a data processing method. After obtaining the identification file to be processed, at least one identity to be matched included in the identification file is compared with the identity in the known mapping relationship information to obtain a matching result, which includes: at least one first identity matched to the account identification code and the account identification code corresponding to each first identity, and finally outputs the account identification code corresponding to each first identity. This technical solution realizes the automatic matching of the identity (ID) and the account identification code (PIN), does not require manual participation, reduces costs, and improves data processing efficiency.
[0067] For example, Figure 1 Schematic diagram of application scenarios of the data processing method provided in the embodiment of the present application. Figure 1 As shown, the application scenario may include: at least one terminal device ( Figure 1 Three terminal devices are shown, namely terminal device 111, terminal device 112, terminal device 113), network 12, business server 13 and data processing device 14. Each terminal device and business server 13 can communicate through network 12, so that business server 13 can obtain user operation behavior data, thereby determining user identity information carried in the user operation behavior data.
[0068] Optionally, the business server 13 may also generate an identification file to be processed according to the user identity information carried in the user operation behavior data.
[0069] For example, in Figure 1In the application scenario shown, the data processing device 14 can directly exchange information with the business server 13 to obtain the identification file to be processed from the business server 13; or, the data processing device 14 receives the identification file uploaded by the operator through the operation terminal 16, performs matching processing on each identity identifier to be matched in the identification file, and feeds back the matching result to the operation terminal 16 for display. The embodiment of the present application does not limit the specific manner in which the data processing device obtains the identification file to be processed, which can be determined according to the actual scenario and will not be elaborated here.
[0070] In this embodiment, the data processing device 14 can execute the program code of the data processing method provided in this application based on the acquired identification file to be processed, so as to obtain the matching result of each identity identification to be matched.
[0071] Optional, Figure 1 The application scenario shown may also include a data storage device 15 , which may be connected to the service server 13 or the data processing device 14 , and is used to store data output by the service server 13 and / or data output by the data processing device 14 .
[0072] It should be noted that the attached Figure 1 This is only a schematic diagram of an application scenario provided by the embodiment of the present application. Figure 1 does not limit the equipment included in Figure 1 The positional relationship between the devices in the Figure 1 In the embodiment, the data storage device 15 can be an external memory relative to the business server 13. In other cases, the data storage device 15 can also be placed in the business server 13. The data processing device 14 can be a device that exists independently of the business server 13, or it can be a component integrated in the business server 13. The embodiments of the present application do not limit this.
[0073] In practical applications, since both the terminal device and the server are processing devices with data processing capabilities, the above Figure 1 The data processing device in the application scenario shown can be implemented by a terminal device or a server. The embodiment of the present application is explained with the execution subject of the data processing method as the data processing device.
[0074] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0075] Figure 2 This is a flow chart of the first embodiment of the data processing method provided by this application. Figure 2 As shown, the data processing method may include the following steps:
[0076] S201. Obtain an identification file to be processed, where the identification file includes: at least one identity to be matched.
[0077] In the embodiment of the present application, if the operator wants to determine the account PIN of the user of certain platforms, the PIN can be obtained by executing the data processing method provided in the embodiment of the present application through the data processing device. Optionally, the data processing device needs to first obtain the identification file to be processed, and the identification file carries at least one identity to be matched, so that the data processing device can perform targeted queries and matching of mapping relationships.
[0078] As an example, the data processing device is a terminal device that can be operated by an operator, and the identity identifier to be matched in the identification file to be processed can be an identity identifier that has been screened and processed by the operator. The screening and processing by the operator can narrow the processing scope of the data processing device and output the identity identifier to be matched in a targeted manner.
[0079] For example, Figure 3 This is a schematic diagram of the interface for uploading the identification file to be processed. For example, Figure 3 As shown, in this embodiment, the data type of the identity to be matched in the identification file is the device ID, and the ID type to be uploaded can be selected as the Android mobile device identification code: (imei) or WeChat open identification (openID): (wx_openid); the mapping rule can be selected as the most recent activity (optionally, in other scenarios, the mapping rule can also be the highest activity frequency, etc.); select the file to upload, where the identification file can support txt format, the maximum file size is 15M, and the file encoding must be in UTF-8-BOM format. In actual applications, the specific upload process is as follows: Use the Notepad encoding editor (NotePad++) to open txt, click the menu bar [Encoding] to view and select the encoding, and select [Use UTF-8-BOM encoding]-[Save]. Exemplary, according to Figure 3 For the identification file shown, the data processing device can perform operations such as crowd estimation or convertible PIN. When the data processing device determines that all the above operations have passed the verification, it can select [Create] to create the identification file.
[0080] Understandably, Figure 3 The interface diagram for uploading the identification file shown is an exemplary description, and the embodiments of the present application do not limit it, and it can be adjusted according to the actual scenario.
[0081] As another example, the data processing device can directly exchange information with the business server. In this case, the data processing device can directly obtain the identification file to be processed from the business server, or directly obtain user operation data from the business server, and then process the user operation data based on preset rules to determine the identification file to be processed. The embodiment of the present application does not limit the specific method of obtaining the identification file to be processed, which can be determined according to actual needs and will not be elaborated here.
[0082] It is understandable that in practical applications, the identification file is an identity identification file that has been screened. Exemplarily, the type of identity identification to be matched in the identification file is a screened ID type, wherein multiple ID types can be selected, and the purpose of screening ID types is to narrow the query scope during subsequent matching.
[0083] Optionally, the format of the identification file has certain requirements, that is, in a certain identification file, related IDs are placed in the same row. For example, taking IMEI and application identifier (AID) as an example, IMEI and AID are two different types of IDs obtained by mobile phone devices. IMEI belongs to the ID of the mobile phone hardware type, and AID is the ID of the mobile phone operating system. When a user browses items with a mobile phone, the browsing log will store the IMEI number and AID number of this mobile phone in the same row, indicating that these two IDs belong to the same mobile phone device. If the user obtains these two types of IDs from the browsing log table, when generating the identification file, the ID originally stored in the same row should be pasted to the same row of the identification file according to the storage method of the source table to be stored in the identification file, and the ID type code should be indicated.
[0084] For example, Figure 4 This is a schematic diagram of the storage format of the identity identifier to be matched in the identification file provided in the embodiment of the present application. Figure 4 As shown, it is assumed that two types of IDs, such as IMEI and AID, need to be stored in the identification file in txt format, wherein the identity identifiers corresponding to IMEI include: B001, B021, and the identity identifiers corresponding to AID include: C001, C100, and B001 and C001 are two types of IDs for the same terminal device; by querying the document with the preset association relationship between the identification type and the coding type (type), it can be known that the type coding of IMEI is 3, and the type coding of AID is 4, then in the identification file in txt format, the associated IDs are stored in the same row, such as Figure 4As shown, the information in the first row includes: B001,3, C001,4; the information in the second row includes: B021,3; the information in the third row includes: C100,4; wherein, each column in each row represents ID1, ID1_type, ID2, ID2_type, and so on.
[0085] S202: Compare the at least one identity identifier to be matched with the identity identifiers in the known mapping relationship information to obtain a matching result, wherein the matching result includes: at least one first identity identifier matched to the account identification code and the account identification code corresponding to each first identity identifier.
[0086] In an embodiment of the present application, a data processing device stores known mapping relationship information representing an identity identifier and an account identification code. Therefore, after the data processing device parses the acquired identification file and obtains the at least one identity identifier to be matched, each identity identifier to be matched can be compared with the identity identifier in the known mapping relationship information to determine whether the at least one identity identifier to be matched exists in the known mapping relationship information. If so, it is determined that the existing identity identifier to be matched is the first identity identifier that matches the account identification code. Accordingly, at least one first identity identifier that matches the account identification code and the account identification code corresponding to each first identity identifier are obtained.
[0087] Exemplarily, in an embodiment of the present application, it is assumed that the identity identifiers to be matched in the identification file include: B001, B021, C001 and C100, and these identity identifiers to be matched are stored as a column to obtain the identity identifier table to be matched shown in Table 1, so as to facilitate matching with the mapping relationship table corresponding to the known mapping relationship information. Optionally, in this embodiment, Table 2 is a mapping relationship table corresponding to the known mapping relationship information.
[0088] The first column and the second column of Table 1 represent the identity to be matched and the encoding type (type) corresponding to the identity to be matched, respectively. Table 2 is used to represent the association between the identity (ID), the account identification code (PIN) and the encoding type (type). Table 2 is obtained based on the currently known mapping relationship between the identity (ID) and the account PIN.
[0089] Table 1 Identity table to be matched
[0090] B001 3 C001 4 B021 3 C100 4
[0091] Table 2 Mapping relationship table
[0092] ID PIN TYPE A001 PIN1 1 B034 PIN1 3 C123 PIN1 4 C001 PIN2 4 B077 PIN4 3
[0093] Optionally, in this embodiment, by comparing the data in Table 1 with Table 2, it can be known that C001 in Table 1 exists in Table 2, that is, C001 is at least one first identity identifier that matches the account identification code, and the account identification code (PIN) corresponding to C001 is PIN2.
[0094] S203: Output the account identification code corresponding to each first identity identifier.
[0095] In an embodiment of the present application, after determining the account identification code corresponding to the first identity identifier, the data processing device can output the account identification code to display it to the operator. As an example, if the data processing device has a human-computer interaction interface, it can present the account identification code corresponding to each first identity identifier through the human-computer interaction interface. As another example, the data processing device can also be connected to the operator's test terminal, so that the data processing device can send the account identification code corresponding to each first identity identifier or a set of account identification codes corresponding to all first identity identifiers to the test terminal, so that the test terminal displays the account identification code corresponding to each first identity identifier, so that the operator can obtain the account identification code corresponding to the identity identifier in a timely manner.
[0096] The data processing method provided in the embodiment of the present application, after obtaining the identification file to be processed, compares at least one identity to be matched included in the identification file with the identity in the known mapping relationship information to obtain a matching result, which includes: at least one first identity matched to the account identification code and the account identification code corresponding to each first identity, and finally outputs the account identification code corresponding to each first identity. This technical solution realizes the automatic matching of the identity (ID) and the account identification code (PIN), does not require manual participation, reduces costs, and improves data processing efficiency.
[0097] Optionally, based on the above embodiment, Figure 5 The following is a flow chart of the second embodiment of the data processing method provided in the present application. Figure 5 As shown, the data processing method may also include the following steps:
[0098] S501: Parse the identification file to obtain at least one identity to be matched.
[0099] In an embodiment of the present application, in order to facilitate the mapping and matching between the identity identifier and the account PIN, after obtaining the identification file, the data processing device may first parse the identification file to obtain at least one identity identifier to be matched included in the identification file.
[0100] For example, for the above Figure 4The identification file shown, the identification file includes the identity tags to be matched: B001, C001, B021 and C100. Optionally, for the acquired identification file, the data processing device will store each identity tag to be matched obtained by parsing into a hive table based on a data warehouse tool, for example, in Table 1 above.
[0101] S502: Add each identity identifier to be matched to the known first identity identifier relationship information to obtain second identity identifier relationship information.
[0102] In a possible design, it is assumed that the data processing device stores known first identity identification relationship information, and the first identity identification relationship information is obtained based on the association relationship between known IDs. Exemplarily, Table 3 is an identity identification relationship table corresponding to the first identity identification relationship information, and Table 3 is generated based on some existing ID data.
[0103] Table 3 Identity relationship table corresponding to the first identity relationship information
[0104] 1 2 3 4 5 A001 -- B034 C123 -- -- -- -- C001 -- -- -- B077 -- --
[0105] In Table 3, in order to distinguish the encoding type of the ID, 1-5 represent the ID type number respectively. The IDs stored in the same row have some association relationship, for example, they belong to the same device. It is understandable that the ID in Table 3 does not contain the account PIN. The -- in Table 3 all represent null values.
[0106] Specifically, as can be seen from Table 3, the first identity identifier relationship information can be represented by an identity identifier relationship table, in which the identities in the same row are identities with an associated relationship and belong to different coding types, wherein the associated relationship includes at least one of the following relationships: belonging to the same device, belonging to the same user. For example, A001, B034, and C123 in the first row of Table 3 can be two different IDs of the same device.
[0107] In this step, the data processing device can add the B001, C001, B021 and C100 waiting-for-matching identity identifiers included in the above identification file to the identity identifier relationship table corresponding to the first identity identifier relationship information shown in Table 3 above, and obtain the identity identifier relationship table corresponding to the second identity identifier relationship information shown in Table 4. The bold identity identifiers in Table 4 are newly added identity identifiers. The - in Table 4 indicates a null value. Similarly, each identity identifier in each row in Table 4 is also an identity identifier with an associated relationship and belonging to a different encoding type.
[0108] Table 4 Identity relationship table corresponding to the second identity relationship information
[0109] 1 2 3 4 5 A001 -- B034 C123 -- -- -- B001 C001 -- -- -- B077 -- -- -- -- B021 -- -- -- -- -- C100 --
[0110] In this embodiment, by adding the identity to be matched to the identity relationship table corresponding to the known first identity relationship information, convenience is provided for subsequent matching.
[0111] In an embodiment of the present application, as an example, the above matching result also includes: at least one second identity identifier that is not matched to the account identification code.
[0112] Specifically, according to the above Figure 2 It can be seen from step S202 of the illustrated embodiment that among B001, B021, C001 and C100, the first identity identifier that matches the account identification code is C001, and the second identity identifier that does not match the account identification code includes: B001, B021, C100. At this time, the three IDs (B001, B021, C100) that do not match the PIN can be stored in Table 5, which represents the second identity identifier table that does not match the account identification code. Similarly, the -- in Table 5 represents a null value.
[0113] Table 5 Second identity table that does not match the account identification code
[0114] B001 3 B021 3 C100 4
[0115] Accordingly, in this embodiment, if Figure 5 As shown, the data processing method may also include the following steps:
[0116] S503: for each second identity identifier, determine whether there is a target identity identifier associated with the second identity identifier in the second identity identifier relationship information; if so, execute S504; if not, end.
[0117] Exemplarily, since the identities in each row of the identity relationship table corresponding to the second identity relationship information are identities that have an associated relationship and belong to different coding types, by comparing the second identity in Table 5 with the identities in the above Table 4, for each second identity, it is determined whether there is a target identity in Table 4 that has an associated relationship with the second identity.
[0118] Optionally, by comparing Table 5 with Table 4, it is found that the second identity identifier B001 and C001 are located in the same row and have an associated relationship. At this time, C001 is the target identity identifier associated with B001.
[0119] S504: Determine a target account identification code corresponding to the target identity identifier according to the target identity identifier and known mapping relationship information.
[0120] Optionally, the data processing device can find out that C001 can be matched to PIN2 by querying Table 2, that is, by querying the mapping relationship table corresponding to the known mapping relationship information, that is, the account identification code corresponding to C001 is PIN2.
[0121] S505: Determine the target account identification code as the account identification code corresponding to the second identity identifier.
[0122] In this step, according to S503 and S504, the target identification code associated with the second identity identifier B001 is C001, and the account identification code corresponding to C001 is PIN2. Therefore, it can be determined that the account identification code corresponding to the second identity identifier B001 is also PIN2.
[0123] Furthermore, in an embodiment of the present application, the data processing method may further include the following steps:
[0124] S506: Update known mapping relationship information according to the mapping relationship between the second identity identifier and the target account identification code.
[0125] Exemplarily, after the target account identification code corresponding to the second identity identifier is determined, the mapping relationship between the second identity identifier and the target account identification code may be newly added to the mapping relationship table corresponding to the known mapping relationship information.
[0126] For example, the mapping relationship between B001 and PIN2 is added to Table 2 to obtain the mapping relationship table corresponding to the updated known mapping relationship information (ID>PIN mapping relationship table). Optionally, Table 6 is the mapping relationship table corresponding to the updated known mapping relationship information.
[0127] Table 6 Mapping relationship table corresponding to the updated known mapping relationship information
[0128] ID PIN TYPE A001 PIN1 1 B034 PIN1 3 C123 PIN1 4 C001 PIN2 4 B077 PIN4 3 B001 PIN2 3 B021 -- 3 C100 -- 4
[0129] Referring to Table 6 and Table 2, it can be seen that Table 6 adds a mapping relationship between B001 and PIN2 compared to Table 2, and the obtained Table 6 can continue to provide automatic matching services in the future. Similarly, the - in Table 6 represents a null value.
[0130] Furthermore, referring to Table 6, identity tags to be matched are added in Table 6, which can increase the number of ID data assets, and further increase the number of IDs matched to PINs through the internal model in the subsequent process.
[0131] The data processing method provided in the embodiment of the present application obtains the second identity identifier relationship information by adding each identity identifier to be matched in the identification file to the known first identity identifier relationship information. For each second identity identifier, it is determined whether there is a target identity identifier associated with the second identity identifier in the second identity identifier relationship information. If so, the target account identification code corresponding to the target identity identifier is determined based on the target identity identifier and the known mapping relationship information, thereby determining the account identification code corresponding to the second identity identifier, and updating the known mapping relationship information based on the mapping relationship between the second identity identifier and the target account identification code. In this technical solution, according to the association relationship between identity identifiers and the mapping relationship between identity identifiers and account identification codes, a virtuous cycle of automatic data update iteration can be achieved, which increases the number of automatic matches between identity identifiers and account identification codes and the data processing efficiency, and optimizes the background data assets.
[0132] For example, in the embodiments of the present application, Figure 6 This is a flow chart of the third embodiment of the data processing method provided in the present application. Figure 6 As shown, before the above S201, the data processing method may further include the following steps:
[0133] S601. Obtain a historical data set.
[0134] In the embodiment of the present application, based on the data accumulation and manual processing results of the data platform, the data platform has a certain number of historical data sets. Optionally, the historical data set may include part of the ID data assets and the one-way mapping relationship data between the identity identifier and the account identification code (id>pin).
[0135] When the data processing platform executes the technical solution of the present application and determines the mapping relationship between the identity identifier and the account identification code, it can first obtain a historical data set, and by analyzing the historical data set, determine the known known mapping relationship information and the first identity identifier relationship information, thereby laying the foundation for subsequent automatic matching.
[0136] S602: Process the data in the historical data set to obtain multiple identity identifiers included in the historical data set and mapping relationship data between the identity identifiers and the account identification codes.
[0137] Optionally, in an embodiment of the present application, the relationship between the data in the historical data set may not be clear, and the data processing device may distinguish the mapping relationship data between the ID data assets and the identity identifier and the account identification code (id>pin) for subsequent direct use.
[0138] S603: Based on whether there is an association relationship between identity identifiers, classify and store each identity identifier in the historical data set to obtain first identity identifier relationship information.
[0139] In this step, in order to distinguish the types of identity identifiers, the types of identity identifiers can be numbered first, and then each identity identifier in the historical data set can be stored according to the type of identity identifier, and the identity identifiers with associated relationships can be stored according to an associated relationship. For example, identity identifiers belonging to the same device are stored in the same row, and identity identifiers belonging to different devices are stored in different rows, thereby obtaining the known first identity identifier relationship information.
[0140] Exemplarily, assume that the identity identifiers in the historical data set include: A001, B034, C123, C001, B077, and A001, B034, C123 are used to represent different types of identity identifiers of the same device, so C001 and B077 are identity identifiers of different devices respectively. Therefore, by classifying and storing A001, B034, C123, C001, and B077, an identity identifier relationship table corresponding to the first identity identifier relationship information as shown in Table 3 above can be obtained.
[0141] S604: Generate known mapping relationship information based on the mapping relationship data between the identity identifier and the account identification code and the encoding type of the identity identifier.
[0142] In this embodiment, in order to realize the automatic matching of the identity identifier and the account identification code, after obtaining the mapping relationship data between the identity identifier and the account identification code, the data processing device first establishes a mapping relationship table, wherein the first column of the mapping relationship table represents the identity identifier, the second column represents the account identification code, the third column represents the encoding type of the identity identifier, etc. Therefore, based on the mapping relationship data between the identity identifier and the account identification code and the encoding type of the identity identifier, a mapping relationship table corresponding to the known mapping relationship information shown in Table 2 above can be generated.
[0143] The data processing method provided in the embodiment of the present application processes the data in the acquired historical data set to obtain multiple identity identifiers and mapping relationship data between identity identifiers and account identification codes included in the historical data set, and classifies and stores each identity identifier in the historical data set based on whether there is an association relationship between the identity identifiers to obtain first identity identifier relationship information, and finally generates known mapping relationship information based on the mapping relationship data between the identity identifier and the account identification code and the encoding type of the identity identifier. In this technical solution, the first identity identifier relationship information and the known mapping relationship information are obtained according to the historical data set, which provides the implementation conditions for the subsequent automatic matching processing, while improving work efficiency and optimizing the background data assets.
[0144] Furthermore, based on the above embodiments, the data processing method provided by the present application may also include the following steps:
[0145] Based on the account identification code corresponding to each first identity identifier, information is pushed to the device where the first identity identifier is located.
[0146] Optionally, the data processing device obtains the identity (for example, device ID) of the business personnel from different channels through the above Figures 2 to 6 After the account identification codes corresponding to different identity identifiers are determined in the implementation example, messages can be pushed using the account identification codes. For example, information can be pushed to the device where the first identity identifier is located through the account identification code corresponding to each first identity identifier, so that the user can reach the pushed information to a specific user, thereby providing a prerequisite for subsequently improving business efficiency.
[0147] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.
[0148] Figure 7 This is a schematic diagram of the structure of an embodiment of a data processing device provided by the present application. Figure 7 As shown, the data processing device may include:
[0149] The acquisition module 701 is used to acquire an identification file to be processed, wherein the identification file includes: at least one identity identification to be matched;
[0150] The processing module 702 is used to compare the at least one identity identifier to be matched with the identity identifiers in the known mapping relationship information to obtain a matching result, wherein the matching result includes: at least one first identity identifier matched to the account identification code and the account identification code corresponding to each first identity identifier;
[0151] The output module 703 is used to output the account identification code corresponding to each first identity identifier.
[0152] In a possible design of the embodiment of the present application, the processing module 702 is further used to:
[0153] Parsing the identification file to obtain the at least one identity identification to be matched;
[0154] Each identity to be matched is added to the known first identity relationship information to obtain second identity relationship information.
[0155] Optionally, the matching result further includes: at least one second identity identifier that is not matched to the account identification code;
[0156] Accordingly, the processing module 702 is further used for:
[0157] For each second identity identifier, determining whether there is a target identity identifier associated with the second identity identifier in the second identity identifier relationship information;
[0158] If yes, determining the target account identification code corresponding to the target identity identifier according to the target identity identifier and the known mapping relationship information;
[0159] The target account identification code is determined to be the account identification code corresponding to the second identity identifier.
[0160] Optionally, the processing module 702 is further configured to update the known mapping relationship information according to the mapping relationship between the second identity identifier and the target account identification code.
[0161] In another possible design of the embodiment of the present application, the acquisition module 701 is further used to acquire a historical data set before acquiring the identification file to be processed;
[0162] The processing module 702 is further configured to:
[0163] Processing the data in the historical data set to obtain multiple identity identifiers included in the historical data set and mapping relationship data between the identity identifiers and the account identification codes;
[0164] Based on whether there is an association relationship between identity identifiers, classify and store each identity identifier in the historical data set to obtain first identity identifier relationship information;
[0165] The known mapping relationship information is generated based on the mapping relationship data between the identity identifier and the account identification code and the encoding type of the identity identifier.
[0166] In another possible design of the embodiment of the present application, the output module 703 is further used to push information to the device corresponding to the first identity identifier based on the account identification code corresponding to each first identity identifier.
[0167] The device provided in the embodiment of the present application can be used to execute the technical solution described in the method embodiment. Its implementation principle and technical effects are similar and will not be repeated here.
[0168] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. For example, the processing module can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The implementation of other modules is similar. In addition, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.
[0169] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
[0170] Figure 8 This is a schematic diagram of the structure of the data processing device embodiment provided by this application. Figure 8As shown, the data processing device may include: a processor 801, a memory 802, a communication interface 803 and a system bus 804. The memory 802 and the communication interface 803 are connected to the processor 801 through the system bus 804 and communicate with each other. The memory 802 is used to store computer programs, and the communication interface 803 is used to communicate with other devices. When the processor 801 executes the computer program, the technical solution described in the above method embodiment is implemented.
[0171] In this Figure 8 In the embodiment, the processor 801 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 gate or transistor logic devices, or discrete hardware components.
[0172] The memory 802 may include a random access memory (RAM), may include a read-only memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
[0173] The communication interface 803 is used to implement the communication between the database access device and other devices (such as the client, the read-write library and the read-only library).
[0174] The system bus 804 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.
[0175] Optionally, an embodiment of the present application further provides a computer-readable storage medium, in which computer execution instructions are stored. When the computer execution instructions are executed on a computer, the computer executes the technical solution described in the above method embodiment.
[0176] Optionally, an embodiment of the present application further provides a chip for running instructions, wherein the chip is used to execute the technical solution described in the above method embodiment.
[0177] According to an embodiment of the present application, the present application also provides a computer program product, including: a computer program, the computer program is stored in a readable storage medium, at least one processor of a data processing device can read the computer program from the readable storage medium, and at least one processor executes the computer program so that the data processing device executes the solution provided by any of the above embodiments.
[0178] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the application disclosed herein. This application is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.
[0179] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims
1. A data processing method, characterized in that: include: Acquire an identification file to be processed, the identification file comprising: at least one identity identification to be matched; Comparing the at least one identity identifier to be matched with the identity identifiers in the known mapping relationship information to obtain a matching result, wherein the matching result includes: at least one first identity identifier matched to the account identification code and the account identification code corresponding to each first identity identifier; Output the account identification code corresponding to each first identity identifier; The method further comprises: Parsing the identification file to obtain the at least one identity identification to be matched; Each identity to be matched is added to the known first identity relationship information to obtain second identity relationship information; the second identity relationship information is represented by an identity relationship table, and each identity in each row of the identity relationship table is an identity with an associated relationship and belongs to a different coding type, and the associated relationship includes at least one of the following relationships: belonging to the same device and belonging to the same user; The matching result also includes: at least one second identity identifier that is not matched to the account identification code; Accordingly, the method further includes: For each second identity identifier, determining whether there is a target identity identifier associated with the second identity identifier in the second identity identifier relationship information; If yes, determining the target account identification code corresponding to the target identity identifier according to the target identity identifier and the known mapping relationship information; The target account identification code is determined to be the account identification code corresponding to the second identity identifier.
2. The method according to claim 1, characterized in that The method further comprises: The known mapping relationship information is updated according to the mapping relationship between the second identity identifier and the target account identification code.
3. The method according to claim 1 or 2, characterized in that: Before obtaining the identification file to be processed, the method further includes: Get historical data collection; Processing the data in the historical data set to obtain multiple identity identifiers included in the historical data set and mapping relationship data between the identity identifiers and the account identification codes; Based on whether there is an association relationship between identity identifiers, classify and store each identity identifier in the historical data set to obtain first identity identifier relationship information; The known mapping relationship information is generated based on the mapping relationship data between the identity identifier and the account identification code and the encoding type of the identity identifier.
4. The method according to claim 3, characterized in that The first identity identification relationship information is represented by an identity identification relationship table. The identities located in the same row in the identity identification relationship table are identities with an associated relationship and belong to different coding types. The associated relationship includes at least one of the following relationships: belonging to the same device and belonging to the same user.
5. The method according to claim 1 or 2, characterized in that: The method further comprises: Based on the account identification code corresponding to each first identity identifier, information is pushed to the device corresponding to the first identity identifier.
6. A data processing device, characterized in that: include: An acquisition module, used to acquire an identification file to be processed, wherein the identification file includes: at least one identity to be matched; A processing module, configured to compare the at least one identity identifier to be matched with the identity identifiers in the known mapping relationship information to obtain a matching result, wherein the matching result includes: at least one first identity identifier matched to the account identification code and the account identification code corresponding to each first identity identifier; An output module, used to output an account identification code corresponding to each first identity identifier; The processing module is further used for: Parsing the identification file to obtain the at least one identity identification to be matched; Each identity to be matched is added to the known first identity relationship information to obtain second identity relationship information; the second identity relationship information is represented by an identity relationship table, and each identity in each row of the identity relationship table is an identity with an associated relationship and belongs to a different coding type, and the associated relationship includes at least one of the following relationships: belonging to the same device and belonging to the same user; The matching result also includes: at least one second identity identifier that is not matched to the account identification code; Accordingly, the processing module is also used for: For each second identity identifier, determining whether there is a target identity identifier associated with the second identity identifier in the second identity identifier relationship information; If yes, determining the target account identification code corresponding to the target identity identifier according to the target identity identifier and the known mapping relationship information; The target account identification code is determined to be the account identification code corresponding to the second identity identifier.
7. A data processing device comprising a processor, a memory and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 5 is implemented.
8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 5 when executed by a processor.
9. A computer program product comprising: A computer program, characterized in that when the computer program is executed by a processor, it is used to implement the method according to any one of claims 1 to 5.
Citation Information
Patent Citations
Cross-screen user identification method and device
CN107295067A
User identifier association query method, apparatus and device, and readable storage medium
CN112148925A