User attribute information processing method and device, storage medium, and electronic device

Abstract

The present disclosure is about a method and device for processing user attribute information, a storage medium, and an electronic device, and relates to the field of network information security technology. The method includes: uploading the user attribute information input by the current user in the first display interface to the local browser; obtaining the current attribute category corresponding to the current attribute value of the user attribute information through the local browser, and when determining that any current attribute category is a preset category, calling the parser included in the local browser to hash the attribute value to be processed to the target attribute value; generating a user data uplink request according to the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and sending the user data uplink request to the server side where the current application is located. The present disclosure improves the security of user attribute information.

Description

Background Art

[0002] At present, many third-party applications require users to provide a lot of user attribute information related to user privacy during user registration or use. However, in the process of submitting user attribute information to the server, data leakage may occur, resulting in low security of user attribute information.

[0003] In order to solve this problem, in the prior art, a script file is embedded in the web page code implementation, and then the input user attribute information is processed by the script file, and then the processed user attribute information is uploaded.

[0004] However, since the corresponding script files need to be set, the system burden is heavy, which reduces the processing efficiency of user attribute information.

[0005] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0006] The purpose of the present disclosure is to provide a method for processing user attribute information, a device for processing user attribute information, a computer-readable storage medium, and an electronic device, thereby at least to a certain extent overcoming the problem of low efficiency in processing user attribute information due to limitations and defects of related technologies.

[0007] According to one aspect of the present disclosure, a method for processing user attribute information is provided, including:

[0008] In response to a touch operation of a current user on a first preset control included in a first display interface of a current application, uploading user attribute information input by the current user in the first display interface to a local browser;

[0009] Acquire, through the local browser, a current attribute category corresponding to a current attribute value of the user attribute information, and determine whether the current attribute category is a preset category;

[0010] When it is determined that any of the current attribute categories is the preset category, the current attribute value of the current attribute category being the preset category is determined as the attribute value to be processed, and the parser included in the local browser is called to perform hash processing on the attribute value to be processed to obtain a target attribute value;

[0011] A user data uplink request is generated based on the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and the user data uplink request is sent to the server side where the current application is located, so that the server side completes the secure upload of user attribute information based on the target attribute value and other attribute values ​​included in the user data uplink request.

[0012] In an exemplary embodiment of the present disclosure, performing hash processing on the attribute value to be processed to obtain a target attribute value includes:

[0013] Performing binary conversion on the attribute value to be processed to obtain a first binary bit value, and calculating the byte length of the first binary bit value;

[0014] Constructing a target bit string according to the first binary bit value and the byte length;

[0015] The target bit string is grouped to obtain a plurality of message groups, and each of the message groups is iteratively compressed based on a preset compression function to obtain the target attribute value.

[0016] In an exemplary embodiment of the present disclosure, constructing a target bit string according to the binary attribute value and the byte length includes:

[0017] Performing binary conversion on the byte length to obtain a second binary bit value;

[0018] concatenating the first binary bit value and the second binary bit value to obtain a concatenated bit value;

[0019] Filling a preset binary bit value with a preset number of bits at a preset position in the concatenated bit value to obtain the target bit string;

[0020] The preset position is a middle position between the first binary bit value and the second binary bit value, and the preset number of bits is calculated by the byte length.

[0021] In an exemplary embodiment of the present disclosure, the target bit string is grouped to obtain a plurality of message groups, and each of the message groups is iteratively compressed based on a preset compression function to obtain the target attribute value, including:

[0022] The target bit string is grouped based on a preset grouping rule to obtain a plurality of message groups; wherein the plurality of message groups include a first message group, a second message group, ..., an nth message group;

[0023] Based on a preset bit initial value and a preset compression function, compressing the first message group to obtain a first compression result;

[0024] Compressing the second message group based on the first compression result and a preset compression function to obtain a second compression result;

[0025] Repeat the compression step of the second message group to compress other message groups to obtain other compression results, and obtain the target attribute value according to the first compression result, the second compression result and the other compression results.

[0026] In an exemplary embodiment of the present disclosure, based on a preset bit initial value and a preset compression function, compressing the first message group to obtain a first compression result includes:

[0027] Performing message extension on the first message group based on the preset bit initial value to obtain a first extended message;

[0028] The first extended message is circularly shifted left based on a preset initial word register and an initial intermediate variable to obtain the first compression result.

[0029] In an exemplary embodiment of the present disclosure, before obtaining, through the local browser, a current attribute category corresponding to a current attribute value of the user attribute information, the method for processing the user attribute information further includes:

[0030] Configuring the current attribute category for each current attribute value; wherein the current attribute category includes a general category and / or an advanced category;

[0031] The current attribute value corresponding to the general category does not need to be hashed, but the current attribute value corresponding to the advanced category needs to be hashed.

[0032] In an exemplary embodiment of the present disclosure, before responding to a touch operation of a current user on a first preset control included in a first display interface of a current application, the method for processing user attribute information further includes:

[0033] In response to a touch operation of a current user on a second preset control included in a second display interface of a current application, generating a user data uplink request, and sending the user data uplink request to the server side;

[0034] Receiving the first display interface sent by the server side in response to the user data uplink request, and receiving user attribute information of the current user acting on the form page included in the first display interface;

[0035] The user attribute information includes at least one of the following: user name, user contact information, user registration password and user identity.

[0036] According to one aspect of the present disclosure, there is provided a device for processing user attribute information, comprising:

[0037] An attribute information uploading module, configured to upload user attribute information input by the current user in the first display interface to a local browser in response to a touch operation of the current user on a first preset control included in the first display interface of the current application;

[0038] An attribute category acquisition module, used to acquire, through the local browser, a current attribute category corresponding to a current attribute value of the user attribute information, and determine whether the current attribute category is a preset category;

[0039] A hash processing module, for determining, when determining that any of the current attribute categories is the preset category, a current attribute value of the current attribute category being the preset category as the attribute value to be processed, and calling a parser included in the local browser to perform hash processing on the attribute value to be processed to obtain a target attribute value;

[0040] The first data uplink request generation module is used to generate a user data uplink request based on the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and send the user data uplink request to the server side where the current application is located, so that the server side completes the secure upload of user attribute information according to the target attribute value and other attribute values ​​included in the user data uplink request.

[0041] According to one aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for processing user attribute information described in any one of the above is implemented.

[0042] According to one aspect of the present disclosure, there is provided an electronic device, including:

[0043] Processor; and

[0044] A memory, configured to store executable instructions of the processor;

[0045] The processor is configured to execute any one of the above-mentioned methods for processing user attribute information by executing the executable instructions.

[0046] A method for processing user attribute information provided by an embodiment of the present disclosure, on the one hand, can upload the user attribute information input by the current user in the first display interface to the local browser; then obtain the current attribute category corresponding to the current attribute value of the user attribute information through the local browser, and when it is determined that any current attribute category is a preset category, determine the current attribute value of the current attribute category as the preset category as the attribute value to be processed, and call the parser included in the local browser to hash the attribute value to be processed to the target attribute value; finally, generate a user data uplink request according to the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and send the user data uplink request to the server side where the current application is located, so that the server The server side completes the secure upload of user attribute information according to the target attribute value and other attribute values ​​included in the user data uplink request, and can directly perform hash processing on the attribute value to be processed through the local browser to obtain the corresponding target attribute value, without setting the corresponding script file, thereby solving the problem in the prior art that the corresponding script file needs to be set, thereby causing a heavy burden on the system and reducing the processing efficiency of user attribute information, reducing the system burden while improving the processing efficiency of user attribute information, thereby improving the security of user attribute information; on the other hand, since the target attribute value is a hash value corresponding to the attribute value to be processed, based on the irreversibility of the hash value, other parties cannot perform inverse operations on the target attribute value, thereby further improving the security of the target attribute value.

[0047] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0049] Figure 1 The following is a flowchart schematically showing a method for processing user attribute information according to an exemplary embodiment of the present disclosure.

[0050] Figure 2 A block diagram schematically shows a system for processing user attribute information according to an exemplary embodiment of the present disclosure.

[0051] Figure 3 A display interface diagram of an application according to an exemplary embodiment of the present disclosure is schematically shown.

[0052] Figure 4A flowchart of a method for performing hash processing on the attribute value to be processed to obtain a target attribute value according to an exemplary embodiment of the present disclosure is schematically shown.

[0053] Figure 5 An example diagram of a calculation scenario of a target bit string according to an example embodiment of the present disclosure is schematically shown.

[0054] Figure 6 A diagram schematically shows an example scenario of a calculation of a compression result according to an example embodiment of the present disclosure.

[0055] Figure 7 An example diagram schematically illustrates a compression process according to an example embodiment of the present disclosure.

[0056] Figure 8 A display interface diagram of another application according to an exemplary embodiment of the present disclosure is schematically shown.

[0057] Fig. 9 A code example diagram schematically illustrates a method for processing user attribute information according to an exemplary embodiment of the present disclosure for implementing the method.

[0058] Fig.10 The flowchart schematically shows another method for processing user attribute information according to an exemplary embodiment of the present disclosure.

[0059] Fig.11 A block diagram schematically illustrates a device for processing user attribute information according to an exemplary embodiment of the present disclosure.

[0060] Fig.12 An electronic device for implementing the method for processing user attribute information according to an exemplary embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0061] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present disclosure will be more comprehensive and complete, and the concepts of the example embodiments are fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.

[0062] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0063] At present, many third-party applications require users to provide a lot of private information during registration or use, such as name, date of birth, mobile phone number, ID number, etc. Some of the data is for business needs, while some of the data is excessive collection. For data such as ID numbers, users cannot change them throughout their lives and are sensitive data. Once leaked, it may cause very serious consequences. Therefore, if the sensitive data is not encrypted, it will lead to security risks in multiple links such as leakage during transmission, third-party plaintext storage, and malicious theft.

[0064] In order to solve the above problem, in some technical solutions, JS (JavaScript) scripts are embedded in the web page code to process the information input in the text box. However, this method is complex to implement and easily reserves backdoors, causing other security risks.

[0065] Based on this, this exemplary embodiment first provides a method for processing user attribute information, which can be run on a terminal device, which can be a local terminal device, such as a mobile phone, a tablet computer, and a PC, etc. Of course, those skilled in the art can also run the method disclosed in this disclosure on other platforms as required, and this exemplary embodiment does not specifically limit this. Figure 1 As shown, the method for processing user attribute information may include the following steps:

[0066] Step S110. In response to a touch operation of a current user on a first preset control included in a first display interface of a current application, uploading user attribute information input by the current user in the first display interface to a local browser;

[0067] Step S120. Obtaining, through the local browser, a current attribute category corresponding to the current attribute value of the user attribute information, and determining whether the current attribute category is a preset category;

[0068] Step S130. When it is determined that any of the current attribute categories is the preset category, the current attribute value of the current attribute category being the preset category is determined as the attribute value to be processed, and the parser included in the local browser is called to perform hash processing on the attribute value to be processed to obtain the target attribute value;

[0069] Step S140. Generate a user data uplink request based on the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and send the user data uplink request to the server side where the current application is located, so that the server side completes the secure upload of user attribute information based on the target attribute value and other attribute values ​​included in the user data uplink request.

[0070] In the above method for processing user attribute information, on the one hand, since the user attribute information input by the current user in the first display interface can be uploaded to the local browser; then the current attribute category corresponding to the current attribute value of the user attribute information is obtained through the local browser, and when it is determined that any current attribute category is a preset category, the current attribute value of the current attribute category as the preset category is determined as the attribute value to be processed, and the parser included in the local browser is called to perform hash processing on the attribute value to be processed to the target attribute value; finally, a user data uplink request is generated according to the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and the user data uplink request is sent to the server side where the current application is located, so that the server side can generate a user data uplink request according to the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and the server side can generate a user data uplink request according to the target attribute value and the attribute value to be processed. The target attribute value and other attribute values ​​included in the user data uplink request complete the secure upload of the user attribute information. The attribute value to be processed can be directly hashed through the local browser to obtain the corresponding target attribute value without setting the corresponding script file. This solves the problem in the prior art that the corresponding script file needs to be set, which makes the system burden heavy and reduces the processing efficiency of the user attribute information. It reduces the system burden and improves the processing efficiency of the user attribute information, thereby improving the security of the user attribute information. On the other hand, since the target attribute value is the hash value corresponding to the attribute value to be processed, based on the irreversibility of the hash value, other parties cannot perform inverse operations on the target attribute value, thereby further improving the security of the target attribute value.

[0071] Hereinafter, the method for processing user attribute information according to an exemplary embodiment of the present disclosure will be explained and illustrated in detail with reference to the accompanying drawings.

[0072] First, the invention object of the exemplary embodiments of the present disclosure is explained and described. Specifically, the method for processing user attribute information provided by the exemplary embodiments of the present disclosure can add privacy data options for the current type attribute value of the <input (user input user attribute information)> tag in the syntax of the web implementation programming language without changing the current data interaction transmission and server implementation <hash>After the user enters the corresponding user attribute information, the parser in the browser uses a hashing algorithm such as SM3 to process the attribute values ​​in the user attribute information, thereby achieving irreversible processing of the input privacy data locally (that is, before the data is uploaded to the server), avoiding the risk of privacy data leakage during transmission and on the server.

[0073] Next, the processing system of user attribute information involved in the exemplary embodiment of the present disclosure is explained and illustrated. Figure 2 As shown, the user attribute information processing system includes a terminal device 210 and a server 220. The terminal device can be connected to the server network via a wireless network or a wired network; the terminal device can be used to implement the user attribute information processing method recorded in the exemplary embodiment of the present disclosure, and the server can be used to complete the secure upload of the user attribute information according to the user attribute information uploaded by the terminal device, and complete the information verification of the user according to the uploaded user attribute information. Furthermore, on the display interface of the terminal device, a client or web page of the application is displayed, and the user can enter the user attribute information securely through the client or web page.

[0074] Furthermore, in a method for processing user attribute information provided in an exemplary embodiment of the present disclosure:

[0075] In step S110, in response to a touch operation of a current user on a first preset control included in a first display interface of a current application, user attribute information input by the current user in the first display interface is uploaded to a local browser.

[0076] In this example embodiment, first, in response to the current user's touch operation on the second preset control included in the second display interface of the current application, a user data uplink request is generated, and the user data uplink request is sent to the server side; then, the first display interface sent by the server in response to the user data uplink request is received, and user attribute information of the current user on the form page included in the first display interface is received; wherein the user attribute information includes at least one of the following: user name, user contact information, user registration password, and user identity.

[0077] For example, when the current user needs to complete user registration or information input in a certain application, he can touch the second display interface of the client provided by the application (for example, open the application interface displayed by the client); then, touch the registration interaction control (second preset control) included in the second display interface. When the terminal device receives the touch operation on the registration interaction control, it can generate a corresponding user data uplink request, and then send the user data uplink request to the server side where the application is located; when the server side receives the user data uplink request, it returns the first display interface that requires the user attribute information that the current user needs to fill in, and then the client can display the first display interface according to the code returned by the server.

[0078] Furthermore, after the terminal device displays the first display interface, the user can enter the corresponding user attribute information at the corresponding position of the form by touching the form included in the first display interface; wherein the input user attribute information can be specifically referred to Figure 3 As shown; when the user attribute information is input, the first preset control (the first preset control is a publishing control) included in the first display interface can be touched to upload the attribute information to the local browser. It should be noted here that the above user attribute information can include not only at least one of the following: user name, user contact information, user registration password and user identity, but also user address, user company name, etc. This example does not impose any special restrictions on this.

[0079] In step S120, the current attribute category corresponding to the current attribute value of the user attribute information is obtained through the local browser, and it is determined whether the current attribute category is a preset category.

[0080] In this example embodiment, first, the current attribute category is configured for each current attribute value; wherein the current attribute category includes a general category and / or an advanced category; the current attribute value corresponding to the general category does not need to be hashed, and the current attribute value corresponding to the advanced category needs to be hashed. Figure 3 As shown, the current attribute category can be configured for each current attribute value in the form position where the current attribute value corresponding to each attribute information is located; for example, an advanced category can be configured in the form position corresponding to the ID card number, and a general category can be configured in the form position corresponding to the user name, and so on. The corresponding current attribute category can also be configured according to actual needs, and this example does not impose any special restrictions on this.

[0081] Secondly, after the current attribute category is configured, the current attribute category corresponding to each current attribute value can be obtained through the local browser, and it can be determined whether the current attribute category is a preset category; that is, it can be determined whether there is a current attribute value whose current attribute category is a high-level category; if so, hash processing is performed on the current attribute value; if not, it can be directly published, that is, directly uploaded to the server side. Through this method, the corresponding user attribute information can be processed according to actual needs, and the secure upload of user attribute information can be completed on the basis of ensuring the security of privacy information, thereby further improving the user experience.

[0082] In step S130, when it is determined that any of the current attribute categories is the preset category, the current attribute value of the current attribute category being the preset category is determined as the attribute value to be processed, and the parser included in the local browser is called to hash the attribute value to be processed to the target attribute value.

[0083] Specifically, if there is any current attribute value whose current attribute category is a high-level category, the current attribute value can be determined as the attribute value to be processed. For example, the attribute value to be processed can be an ID card number. Then, the parser included in the local browser is called to perform hash processing on the attribute value to be processed to obtain the target attribute value. Specifically, refer to Figure 4 As shown, performing hash processing on the attribute value to be processed to obtain the target attribute value may include the following steps:

[0084] Step S410: performing binary conversion on the attribute value to be processed to obtain a first binary bit value, and calculating the byte length of the first binary bit value.

[0085] Step S420: construct a target bit string according to the first binary bit value and byte length.

[0086] Specifically, constructing a bit string according to the binary attribute value and the byte length may include: first, performing binary conversion on the byte length to obtain a second binary bit value; second, concatenating the first binary bit value and the second binary bit value to obtain a concatenated bit value; finally, filling a preset binary bit value with a preset number of bits at a preset position in the concatenated bit value to obtain the target bit string; wherein the preset position is the middle position between the first binary bit value and the second binary bit value, and the preset number of bits is calculated through the byte length.

[0087] Step S430: group the target bit string to obtain a plurality of message groups, and iteratively compress each of the message groups based on a preset compression function to obtain the target attribute value.

[0088] Specifically, grouping the target bit string to obtain multiple message groups, and iteratively compressing each message group based on a preset compression function to obtain the target attribute value may include: first, grouping the target bit string based on a preset grouping rule to obtain multiple message groups; wherein the multiple message groups include a first message group, a second message group, ..., an nth message group; secondly, compressing the first message group based on a preset bit initial value and a preset compression function to obtain a first compression result; then, compressing the second message group based on the first compression result and the preset compression function to obtain a second compression result; finally, repeating the compression step of the second message group to compress other message groups to obtain other compression results, and obtaining the target attribute value according to the first compression result, the second compression result and other compression results.

[0089] Among them, compressing the first message group based on a preset bit initial value and a preset compression function to obtain a first compression result may include: first, performing message expansion on the first message group based on the preset bit initial value to obtain a first extended message; second, performing a circular left shift on the first extended message based on a preset initial word register and an initial intermediate variable to obtain the first compression result.

[0090] Steps S410 to S430 are explained and illustrated below. Specifically, first, the above-mentioned attribute value to be processed is converted into binary to obtain a first binary bit value; for example, the first binary bit value (m) can be: 01100001 01100010 01100011, and then the length l of the first binary bit value (m) is calculated, for example, the length l=24; secondly, the target bit string is constructed according to the first binary bit value and the byte length; wherein, in the process of constructing the target bit string, first, the second binary bit value of the section length needs to be calculated; for example, the second binary bit value can be 00…011000; secondly, the first binary bit value and the second binary bit value are concatenated to obtain a concatenated bit value; wherein, in the specific concatenation process, the second binary bit value can be placed at the end position and the first binary bit value can be placed at the beginning position; finally, k digital zeros are filled in the middle position of the concatenated bit value to obtain the target bit string; wherein, the generation scenario of the target bit string can refer to Figure 5 As shown; at the same time, the calculation method of k can be shown in the following formula (1):

[0091] l+1+k=448mod512; Formula (1)

[0092] Furthermore, after obtaining the target bit string m', the target bit string m' can be grouped to obtain n message groups B (0) B (1) ...B (n-1) ; The calculation process of n can be shown as the following formula (2):

[0093]

[0094] That is, after grouping, the target bit string can be expressed as: m'=B (0) B (1) ...B (n-1) .

[0095] Furthermore, after obtaining n message groups, the first message group can be expanded based on the preset bit initial value to obtain the first extended message; then the first extended message is circularly shifted left based on the preset initial word register and the initial intermediate variable to obtain the first compression result; finally, the second message group is compressed based on the first compression result and the preset compression function to obtain the second compression result, and the compression steps are repeated to compress other message groups to obtain other compression results, and the target attribute value can be obtained. The calculation scenario diagram of each compression result can be referred to Figure 6 shown.

[0096] Furthermore, message expansion refers to the addition of B i Expanded to 132 words: W0, W1, ..., W 67 and W'0,W'1,...,W' 63 The specific expansion process can be shown in the following formula (3) and formula (4):

[0097]

[0098]

[0099] in, = means circular left shift;

[0100] Meanwhile, the compression process can be as follows:

[0101] First, let ABCDEFGH be the initial word register, SS1, SS2, TT1, TT2 be the initial intermediate variables, and we have: ABCDEFGH←V (i) (V (i) is the i-th compression result, and the preset bit initial value is V (0) , its specific value can be: 7380166f 4914b2b9 172442d7da8a0600 a96f30bc 163138aa e38dee4d b0fb0e4e); the specific compression process can be shown in the following formula (5)-formula (13):

[0102] SS1←((A=12)+E+(T j =j))=7; Formula (5)

[0103]

[0104] TT1←FF j (A,B,C)+D+SS2+W' j ; Formula (7)

[0105] TT2←GG j (E,F,G)+H+SS1+W j ; Formula (8)

[0106]

[0107]

[0108]

[0109]

[0110]

[0111] Among them, ∧ represents the AND operation, ∨ represents the OR operation, Represents a negation operation, represents XOR operation; and the specific compression process can be referred to Figure 7 shown.

[0112] So far, the first compression result, the second compression result and other compression results have been completely obtained. Finally, the target attribute value y is obtained according to each compression result, and there are:

[0113] y=ABCDEFGH, the byte length of the target attribute value is 256 bits, and the target attribute value can also be called a hash value.

[0114] Finally, after obtaining the target attribute value, the target attribute value can be used to replace the attribute value to be processed, thereby achieving the purpose of protecting the user's privacy data. The target attribute value can be, for example: 3f64659c850d54dfc901fe856…; the display interface after replacement can refer to Figure 8 As shown, the specific implementation code can be referred to Fig. 9 shown.

[0115] In step S140, a user data uplink request is generated based on the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and the user data uplink request is sent to the server side where the current application is located, so that the server side completes the secure upload of user attribute information based on the target attribute value and other attribute values ​​included in the user data uplink request.

[0116] Specifically, after the replacement is completed, a user data uplink request can be generated according to the target attribute value and other attribute values, and then sent to the server side; after the server side receives the user data uplink request, the target attribute value and other attribute values ​​are stored, and the processing of the user data uplink request is completed. Finally, a feedback message is generated based on the information of successful processing, and the feedback message is fed back to the terminal device. It should be supplemented here that the user data uplink request can be applied to user registration scenarios, and can also be used in other scenarios where user attribute information needs to be filled in, such as other information queries (such as electronic certificates, bank information or label information, such as QR codes) based on the attribute information entered by the user, etc. This example does not impose special restrictions on this.

[0117] The following, combined Fig.10 The method for processing user attribute information in the exemplary embodiment of the present disclosure is further explained and illustrated. Fig.10 As shown, the method for processing user attribute information may include the following steps:

[0118] S1001, the server returns a page that requires the user to fill in information;

[0119] S1002, the local browser of the terminal device displays page information according to the code returned by the server;

[0120] S1003, the user enters information according to the page prompts and clicks the submit upload control;

[0121] S1004: The local browser determines whether the page is <hash>; If yes, jump to step S1005; if no, jump to step S1006;

[0122] Step S1005, calling algorithms such as SM3 to process data, and after the processing is completed, submitting all input information in the page to the server;

[0123] Step S1006, directly submit the page data to the server.

[0124] The method for processing user attribute information provided in the exemplary embodiment of the present disclosure can be applied to the sensitive privacy data filled in by the user in the form of collecting user information by a third-party application, especially information such as identity card, which can effectively avoid the leakage of the user's real information; at the same time, the method for processing user attribute information provided in the exemplary embodiment of the present disclosure can be used in the existing grammar. <input> Tag type attribute value, add privacy data option <hash>, and then the input information can be called to the browser parser, and hash algorithms such as SM3 can be used for data processing, ultimately achieving irreversible data processing and improving the security of privacy data.

[0125] The exemplary embodiment of the present disclosure also provides a device for processing user attribute information. Fig.11 As shown, the user attribute information processing device may include an attribute information uploading module 1110, an attribute category acquisition module 1120, a hash processing module 1130, and a first data uplink request generation module 1140. Among them:

[0126] The attribute information uploading module 1110 may be used to upload the user attribute information input by the current user in the first display interface to the local browser in response to the current user's touch operation on the first preset control included in the first display interface of the current application;

[0127] The attribute category acquisition module 1120 may be used to acquire, through the local browser, a current attribute category corresponding to a current attribute value of the user attribute information, and determine whether the current attribute category is a preset category;

[0128] The hash processing module 1130 may be used to, when determining that any of the current attribute categories is the preset category, determine the current attribute value of the current attribute category as the preset category as the attribute value to be processed, and call the parser included in the local browser to perform hash processing on the attribute value to be processed to obtain a target attribute value;

[0129] The first data uplink request generation module 1140 can be used to generate a user data uplink request based on the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and send the user data uplink request to the server side where the current application is located, so that the server side completes the secure upload of user attribute information based on the target attribute value and other attribute values ​​included in the user data uplink request.

[0130] In the above-mentioned user attribute information processing device, on the one hand, since the user attribute information input by the current user in the first display interface can be uploaded to the local browser; then the current attribute category corresponding to the current attribute value of the user attribute information is obtained through the local browser, and when any current attribute category is determined to be a preset category, the current attribute value of the current attribute category being the preset category is determined as the attribute value to be processed, and the parser included in the local browser is called to perform hash processing on the attribute value to be processed to obtain the target attribute value; finally, a user data uplink request is generated according to the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and the user data uplink request is sent to the server side where the current application is located, so that the server side can generate the user data uplink request according to the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and the server side can generate the user data uplink request according to the target attribute value and the attribute value to be processed. The target attribute value and other attribute values ​​included in the user data uplink request complete the secure upload of the user attribute information, so as to directly perform hash processing on the attribute value to be processed through the local browser to obtain the corresponding target attribute value, without setting the corresponding script file, thereby solving the problem in the prior art that the corresponding script file needs to be set, thereby causing a heavy burden on the system and reducing the processing efficiency of the user attribute information, reducing the system burden while improving the processing efficiency of the user attribute information, thereby improving the security of the user attribute information; on the other hand, since the target attribute value is the hash value corresponding to the attribute value to be processed, based on the irreversibility of the hash value, other parties cannot perform inverse operations on the target attribute value, thereby further improving the security of the target attribute value.

[0131] In an exemplary embodiment of the present disclosure, performing hash processing on the attribute value to be processed to obtain a target attribute value includes:

[0132] Performing binary conversion on the attribute value to be processed to obtain a first binary bit value, and calculating the byte length of the first binary bit value;

[0133] Constructing a target bit string according to the first binary bit value and the byte length;

[0134] The target bit string is grouped to obtain a plurality of message groups, and each of the message groups is iteratively compressed based on a preset compression function to obtain the target attribute value.

[0135] In an exemplary embodiment of the present disclosure, constructing a target bit string according to the binary attribute value and the byte length includes:

[0136] Performing binary conversion on the byte length to obtain a second binary bit value;

[0137] concatenating the first binary bit value and the second binary bit value to obtain a concatenated bit value;

[0138] Filling a preset binary bit value with a preset number of bits at a preset position in the concatenated bit value to obtain the target bit string;

[0139] The preset position is a middle position between the first binary bit value and the second binary bit value, and the preset number of bits is calculated by the byte length.

[0140] In an exemplary embodiment of the present disclosure, the target bit string is grouped to obtain a plurality of message groups, and each of the message groups is iteratively compressed based on a preset compression function to obtain the target attribute value, including:

[0141] The target bit string is grouped based on a preset grouping rule to obtain a plurality of message groups; wherein the plurality of message groups include a first message group, a second message group, ..., an nth message group;

[0142] Based on a preset bit initial value and a preset compression function, compressing the first message group to obtain a first compression result;

[0143] Compressing the second message group based on the first compression result and a preset compression function to obtain a second compression result;

[0144] Repeat the compression step of the second message group to compress other message groups to obtain other compression results, and obtain the target attribute value according to the first compression result, the second compression result and the other compression results.

[0145] In an exemplary embodiment of the present disclosure, based on a preset bit initial value and a preset compression function, compressing the first message group to obtain a first compression result includes:

[0146] Performing message extension on the first message group based on the preset bit initial value to obtain a first extended message;

[0147] The first extended message is circularly shifted left based on a preset initial word register and an initial intermediate variable to obtain the first compression result.

[0148] In an exemplary embodiment of the present disclosure, the device for processing user attribute information further includes:

[0149] A current attribute category configuration module, used to configure the current attribute category for each current attribute value; wherein the current attribute category includes a general category and / or an advanced category;

[0150] The current attribute value corresponding to the general category does not need to be hashed, but the current attribute value corresponding to the advanced category needs to be hashed.

[0151] In an exemplary embodiment of the present disclosure, the device for processing user attribute information further includes:

[0152] A second data uplink request generating module, configured to generate a user data uplink request in response to a touch operation of a current user on a second preset control included in a second display interface of a current application, and send the user data uplink request to the server side;

[0153] A user attribute information receiving module, which can be used to receive the first display interface sent by the server side in response to the user data uplink request, and receive user attribute information of the current user acting on the form page included in the first display interface;

[0154] The user attribute information includes at least one of the following: user name, user contact information, user registration password and user identity.

[0155] The specific details of each module in the above-mentioned user attribute information processing device have been described in detail in the corresponding user attribute information processing method, so they will not be repeated here.

[0156] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0157] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0158] In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

[0159] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods or program products. Therefore, various aspects of the present disclosure may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, which may be collectively referred to herein as "circuits", "modules" or "systems".

[0160] Refer to the following Fig.12 1200 according to this embodiment of the present disclosure is described. Fig.12 The electronic device 1200 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0161] like Fig.12 As shown, the electronic device 1200 is in the form of a general computing device. The components of the electronic device 1200 may include, but are not limited to: the at least one processing unit 1210, the at least one storage unit 1220, a bus 1230 connecting different system components (including the storage unit 1220 and the processing unit 1210), and a display unit 1240.

[0162] The storage unit stores a program code, which can be executed by the processing unit 1210, so that the processing unit 1210 performs the steps according to various exemplary embodiments of the present disclosure described in the above "Exemplary Method" section of this specification. For example, the processing unit 1210 can perform the following steps: Figure 1 Step S110 shown in: in response to the current user's touch operation on the first preset control included in the first display interface of the current application, the user attribute information input by the current user in the first display interface is uploaded to the local browser; Step S120: obtaining the current attribute category corresponding to the current attribute value of the user attribute information through the local browser, and judging whether the current attribute category is a preset category; Step S130: when it is determined that any of the current attribute categories is the preset category, determining the current attribute value whose current attribute category is the preset category as the attribute value to be processed, and calling the parser included in the local browser to hash the attribute value to be processed to the target attribute value; Step S140: generating a user data uplink request according to the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and sending the user data uplink request to the server side where the current application is located, so that the server side completes the secure upload of the user attribute information according to the target attribute value and other attribute values ​​included in the user data uplink request.

[0163] The storage unit 1220 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 12201 and / or a cache storage unit 12202 , and may further include a read-only storage unit (ROM) 12203 .

[0164] The storage unit 1220 may also include a program / utility 12204 having a set (at least one) of program modules 12205, such program modules 12205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0165] Bus 1230 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0166] The electronic device 1200 may also communicate with one or more external devices 1300 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 1200, and / or communicate with any device that enables the electronic device 1200 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 1250. Furthermore, the electronic device 1200 may also communicate with one or more networks (e.g., a local area network (LAn), a wide area network (WAn), and / or a public network, such as the Internet) via a network adapter 1260. As shown, the network adapter 1260 communicates with other modules of the electronic device 1200 via a bus 1230. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0167] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0168] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of the present specification is stored. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present disclosure described in the above "Exemplary Method" section of the present specification.

[0169] According to the program product for implementing the above method in the embodiment of the present disclosure, it can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0170] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0171] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0172] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0173] Program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0174] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0175] Other embodiments of the present disclosure will be readily apparent to those skilled in the art after considering the specification and practicing the inventions invented herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not invented by the present disclosure. The specification and examples are to be considered merely exemplary, and the true scope and spirit of the present disclosure are indicated by the claims.< / hash> < / hash> < / hash>

Claims

1. A method for processing user attribute information, characterized in that: include: In response to a touch operation of a current user on a first preset control included in a first display interface of a current application, uploading user attribute information input by the current user in the first display interface to a local browser; Acquire, through the local browser, a current attribute category corresponding to a current attribute value of the user attribute information, and determine whether the current attribute category is a preset category; When it is determined that any of the current attribute categories is the preset category, the current attribute value of the current attribute category being the preset category is determined as the attribute value to be processed, and the parser included in the local browser is called to perform hash processing on the attribute value to be processed to obtain a target attribute value, including: performing binary conversion on the attribute value to be processed to obtain a first binary bit value, and calculating the byte length of the first binary bit value; performing binary conversion on the byte length to obtain a second binary bit value; splicing the first binary bit value and the second binary bit value to obtain a spliced ​​bit value; filling a preset binary bit value with a preset number of bits at a preset position in the spliced ​​bit value to obtain a target bit string; grouping the target bit string to obtain multiple message groups, and iteratively compressing each of the message groups based on a preset compression function to obtain the target attribute value; A user data uplink request is generated based on the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and the user data uplink request is sent to the server side where the current application is located, so that the server side completes the secure upload of user attribute information based on the target attribute value and other attribute values ​​included in the user data uplink request.

2. The method for processing user attribute information according to claim 1, characterized in that: The preset position is a middle position between the first binary bit value and the second binary bit value, and the preset number of bits is calculated by the byte length.

3. The method for processing user attribute information according to claim 1, characterized in that: The target bit string is grouped to obtain a plurality of message groups, and each of the message groups is iteratively compressed based on a preset compression function to obtain the target attribute value, including: The target bit string is grouped based on a preset grouping rule to obtain a plurality of message groups; wherein the plurality of message groups include a first message group, a second message group, ..., an nth message group; Based on a preset bit initial value and a preset compression function, compressing the first message group to obtain a first compression result; Compressing the second message group based on the first compression result and a preset compression function to obtain a second compression result; Repeat the compression step of the second message group to compress other message groups to obtain other compression results, and obtain the target attribute value according to the first compression result, the second compression result and the other compression results.

4. The method for processing user attribute information according to claim 3, characterized in that: Based on a preset bit initial value and a preset compression function, compressing the first message group to obtain a first compression result includes: Performing message extension on the first message group based on the preset bit initial value to obtain a first extended message; The first extended message is circularly shifted left based on a preset initial word register and an initial intermediate variable to obtain the first compression result.

5. The method for processing user attribute information according to claim 1, characterized in that: Before obtaining, through the local browser, a current attribute category corresponding to a current attribute value of the user attribute information, the method for processing the user attribute information further includes: Configuring the current attribute category for each current attribute value; wherein the current attribute category includes a general category and / or an advanced category; The current attribute value corresponding to the general category does not need to be hashed, but the current attribute value corresponding to the advanced category needs to be hashed.

6. The method for processing user attribute information according to claim 1, characterized in that: Before responding to the current user's touch operation on the first preset control included in the first display interface of the current application, the method for processing user attribute information further includes: In response to a touch operation of a current user on a second preset control included in a second display interface of a current application, generating a user data uplink request, and sending the user data uplink request to the server side; Receiving the first display interface sent by the server side in response to the user data uplink request, and receiving user attribute information of the current user acting on the form page included in the first display interface; The user attribute information includes at least one of the following: user name, user contact information, user password and user identity.

7. A device for processing user attribute information, characterized in that: include: An attribute information uploading module, configured to upload user attribute information input by the current user in the first display interface to a local browser in response to a touch operation of the current user on a first preset control included in the first display interface of the current application; An attribute category acquisition module, used to acquire, through the local browser, a current attribute category corresponding to a current attribute value of the user attribute information, and determine whether the current attribute category is a preset category; A hash processing module is used to, when determining that any of the current attribute categories is the preset category, determine the current attribute value of the current attribute category as the preset category as the attribute value to be processed, and call the parser included in the local browser to perform hash processing on the attribute value to be processed to obtain a target attribute value, including: performing binary conversion on the attribute value to be processed to obtain a first binary bit value, and calculating the byte length of the first binary bit value; performing binary conversion on the byte length to obtain a second binary bit value; splicing the first binary bit value and the second binary bit value to obtain a spliced ​​bit value; filling a preset binary bit value with a preset number of bits at a preset position in the spliced ​​bit value to obtain a target bit string; grouping the target bit string to obtain multiple message groups, and iteratively compressing each of the message groups based on a preset compression function to obtain the target attribute value; The first data uplink request generation module is used to generate a user data uplink request based on the target attribute value and other attribute values ​​in the current attribute value except the attribute value to be processed, and send the user data uplink request to the server side where the current application is located, so that the server side completes the secure upload of user attribute information according to the target attribute value and other attribute values ​​included in the user data uplink request.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for processing user attribute information according to any one of claims 1 to 6 is implemented.

9. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; Wherein, the processor is configured to execute the method for processing user attribute information as described in any one of claims 1-6 by executing the executable instructions.

Images