Data publishing method and system for specific industry crowd management analysis

Abstract

The invention belongs to the technical field of data processing. The invention provides a data publishing method and system for specific industry crowd management analysis, and the method comprises the steps: generating a first plaintext key after to-be-analyzed specific industry crowd attribute data is assembled, and encrypting the assembled data through the first plaintext key to generate a first data ciphertext; the first plaintext key is encrypted by using the first public key, the encrypted first plaintext key and the first data ciphertext are sent to the WEB rear end, a filter at the WEB rear end decrypts the first plaintext key by using the first private key and decrypts the first data ciphertext by using the decrypted first plaintext key, and the decrypted first data ciphertext is processed by the WEB rear end; after being encrypted and decrypted again, the processed data are displayed and published at the WEB front end; according to the method, WEB front-end and WEB rear-end encryption and decryption processing is carried out on the secret-related crowd data of the specific industry, so that effective release of the crowd data of the specific industry can be realized, and leakage of the secret-related data can also be avoided.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a data publishing method and a data publishing system for management and analysis of a specific industry population. Background Art

[0002] The statements in this section merely provide background art related to the present invention and do not necessarily constitute prior art.

[0003] At present, the traditional statistical strategy for WEB application layer data is mainly to extract data by writing interface codes to query database data. This method is widely used in the field of traditional WEB development. However, in the field of big data (such as management analysis of people in a specific industry), the result database structure changes frequently, and the needs of various business departments change or are frequently added. If the traditional manual code writing method is used, it is inevitable to update the code frequently and update the version frequently, which is a great challenge in terms of labor cost and code stability.

[0004] The inventors have found that the above situation generally requires a data publishing system to handle. Traditional data publishing services can perform some simple configuration queries on data, but they are all based on a single database. When the data of some statistical items comes from multiple databases or even from multiple non-relational databases, it cannot meet the needs; Patent No. CN117312393A discloses an interface-configured cross-data source data publishing method and system. Although cross-data source data publishing is achieved, there is a problem of poor confidentiality of data queries when the confidentiality level is high or the management population is highly sensitive; for example, when you want to count the distribution of educational information of people in a specific industry, you cannot effectively keep everyone's information confidential, and there is a high risk of data leakage. Summary of the invention

[0005] In order to address the deficiencies of the prior art, the present invention provides a data publishing method and system for management and analysis of people in specific industries, which performs encryption and decryption processing on the confidential data of people in specific industries at the WEB front-end and WEB back-end, thereby not only realizing the effective publication of the data of people in specific industries, but also avoiding the leakage of confidential data.

[0006] In order to achieve the above object, the present invention adopts the following technical solution:

[0007] In a first aspect, the present invention provides a data publishing method for crowd management analysis in a specific industry.

[0008] A data publishing method for crowd management analysis in a specific industry, comprising the following processes:

[0009] After assembling the attribute data of the specific industry population to be analyzed, a first plaintext key is generated, and the assembled data is encrypted using the first plaintext key to generate a first data ciphertext; wherein the attribute data of the specific industry population at least includes: one or more of: geographical information of the specific industry population, age information of the specific industry population, work unit information of the specific industry population, and position information of the specific industry population;

[0010] Encrypt the first plaintext key using the first public key, send the encrypted first plaintext key and the first data ciphertext to the WEB backend, the WEB backend decrypts the first plaintext key using the first private key, decrypts the first data ciphertext using the decrypted first plaintext key, and processes the decrypted first data ciphertext;

[0011] Generate a second plaintext key, and use the second plaintext key to encrypt the data of the specific industry population to generate a second data ciphertext;

[0012] Use the second public key to encrypt the second plaintext key, send the encrypted second plaintext key and the second data ciphertext to the WEB front end, the WEB front end uses the second private key to decrypt the second plaintext key, uses the decrypted second plaintext key to decrypt the second data ciphertext, renders the decrypted second data ciphertext on the page, and displays and publishes it.

[0013] As a further limitation of the first aspect of the present invention, the first plaintext key and the second plaintext key are both AES keys.

[0014] As a further limitation of the first aspect of the present invention, the first public key and the first private key are RSA asymmetric keys, and the second public key and the second private key are RSA asymmetric keys.

[0015] As a further limitation of the first aspect of the present invention, the first plaintext key and the second plaintext key are SM1 key, SM2 key, SM3 key or SM4 key.

[0016] As a further limitation of the first aspect of the present invention, the first public key and the first private key are corresponding SM1 key, SM2 key, SM3 key or SM4 key, and the second public key and the second private key are corresponding SM1 key, SM2 key, SM3 key or SM4 key.

[0017] As a further limitation of the first aspect of the present invention, a filter is used to decrypt the parameters transmitted from the WEB front end, and the decrypted plain text parameters are further transmitted backward to the processor of the WEB back end.

[0018] As a further limitation of the first aspect of the present invention, the data transmission interfaces of the WEB front end and the WEB back end are respectively annotated by means of annotations, and encryption operations are performed by means of AOP.

[0019] As a further limitation of the first aspect of the present invention, the WEB front end uses the Axios framework to define http request and response interceptors, and when the encryption and decryption identifier is detected in the http request, the encryption and decryption operation is automatically performed in the interceptor.

[0020] In a second aspect, the present invention provides a data publishing system for management and analysis of populations in specific industries.

[0021] A data publishing system for crowd management and analysis in a specific industry, comprising a WEB front end and a WEB back end communicating with each other;

[0022] The WEB front end assembles the attribute data of the specific industry population to be analyzed, generates a first plaintext key, and uses the first plaintext key to encrypt the assembled data to generate a first data ciphertext;

[0023] The WEB front end uses the first public key to encrypt the first plaintext key, and sends the encrypted first plaintext key and the first data ciphertext to the WEB back end;

[0024] The WEB backend uses the first private key to decrypt the first plaintext key, uses the decrypted first plaintext key to decrypt the first data ciphertext, and processes the decrypted first data ciphertext;

[0025] The WEB backend generates a second plaintext key, and uses the second plaintext key to encrypt the data of the specific industry population to generate a second data ciphertext;

[0026] The WEB backend uses the second public key to encrypt the second plaintext key, and sends the encrypted second plaintext key and the second data ciphertext to the WEB frontend. The WEB frontend uses the second private key to decrypt the second plaintext key, and uses the decrypted second plaintext key to decrypt the second data ciphertext, and renders the decrypted second data ciphertext on the page and displays and publishes it.

[0027] As a further limitation of the second aspect of the present invention, the data transmission interfaces of the WEB front end and the WEB back end are respectively annotated by means of annotations, and encryption operations are performed by means of AOP.

[0028] Compared with the prior art, the present invention has the following beneficial effects:

[0029] 1. The present invention innovatively proposes a data publishing method and system for management and analysis of people in specific industries, which performs encryption and decryption processing on the confidential data of people in specific industries at the WEB front-end and WEB back-end, which can not only realize the effective publication of the data of people in specific industries, but also avoid the leakage of confidential data.

[0030] 2. The WEB front end of the present invention uses the Axios framework to define the Http request and response interceptor. When the encryption and decryption identifier is detected in the http request, the encryption and decryption operation is automatically performed in the interceptor. The WEB back end uses a filter to decrypt the incoming parameters and continues to pass the decrypted plaintext parameters backward. At this time, the decrypted data is processed in the subsequent code, and there is no need to explicitly call the decryption method, which does not affect the subsequent business layer processing.

[0031] Advantages of additional aspects of the present invention will be given in part in the following description, and in part will become obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The accompanying drawings in the specification, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0033] Figure 1 A schematic diagram of a flow chart of a data publishing method for crowd management and analysis in a specific industry provided in Embodiment 1 of the present invention;

[0034] Figure 2 A schematic diagram of data flow of a data publishing method for crowd management and analysis in a specific industry provided in Example 1 of the present invention;

[0035] Figure 3 A schematic diagram of the educational background distribution of people in a specific industry provided in Example 1 of the present invention. DETAILED DESCRIPTION

[0036] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0037] It should be noted that the following detailed descriptions are exemplary and are intended to provide further explanation of the present invention. Unless otherwise specified, all technical and scientific terms used herein have the same meanings as those commonly understood by those skilled in the art to which the present invention belongs.

[0038] In the absence of conflict, the embodiments of the present invention and the features of the embodiments may be combined with each other.

[0039] Embodiment 1:

[0040] This implementation proposes a data publishing method for crowd management analysis in a specific industry, such as Figure 1 and Figure 2 As shown, the following process is included:

[0041] S1: After assembling the attribute data of the specific industry population to be analyzed, a first plaintext key is generated, and the assembled data is encrypted using the first plaintext key to generate a first data ciphertext;

[0042] S2: Use the first public key to encrypt the first plaintext key, send the encrypted first plaintext key and the first data ciphertext to the WEB backend, the WEB backend decrypts the first plaintext key using the first private key, decrypts the first data ciphertext using the decrypted first plaintext key, and processes the decrypted first data ciphertext;

[0043] S3: Generate a second plaintext key, and use the second plaintext key to encrypt the data of the specific industry population to generate a second data ciphertext;

[0044] S4: Use the second public key to encrypt the second plaintext key, send the encrypted second plaintext key and the second data ciphertext to the WEB front end, the WEB front end uses the second private key to decrypt the second plaintext key, uses the decrypted second plaintext key to decrypt the second data ciphertext, renders the decrypted second data ciphertext on the page, and displays and publishes it.

[0045] The attribute data of the specific industry population to be analyzed in step S1 of this implementation method includes but is not limited to: geographical information of the specific industry population, age information of the specific industry population, work unit information of the specific industry population, position information of the specific industry population, etc. It can be understood that the attribute data of the specific industry population here is the information authorized for use, and other attribute data can also be used, which will not be described in detail here, such as Figure 3 The figure below is a schematic diagram of the educational level distribution of people in a specific industry.

[0046] Specifically, the following example is provided. The information before encryption is {"undergraduate degree or below":"3", "undergraduate degree":"2", "graduate degree":"1"}, and the response data after encryption is as follows:

[0047] {"success":true ,"data":{"aesKey":"iUZg4aM2yel8zqWWpdMT8RddybvAAHhr / JNymaZDewKyY4XZXITQcrml8IP Hf1E77xuqQMhzVC8XTPJoOB2NzZo2Mf907zj8EPHT1jNhkZRUlEZsDI7m70iiwoiSGTPEenzrQOd / us M2Arh0O7aHbIAhtVnFnRTVCqPPvA2F1R4=","content":"1rrJDgnpBh+Lk9sWVpS9Z8UqTN9nItU 4rWS6gVv6mglMx8u2DZgg8MYa / 6uT1JZtHGL / eazcEOuLyoCpr4IBiFrOTnsy87jGWPd94SarwhI="}};

[0048] The value of success indicates that the data processing result is successful. The value of data is divided into two parts: aesKey is the encrypted key, and content is the ciphertext content.

[0049] In step S1 and step S2 of the present implementation, the first plaintext key and the second plaintext key are both AES keys, the first public key and the first private key are RSA asymmetric keys, and the second public key and the second private key are RSA asymmetric keys.

[0050] In this implementation, the implementation process of the first plaintext key and the second plaintext key includes:

[0051] (1-1) Key selection.

[0052] AES supports three key lengths: 128 bits, 192 bits, and 256 bits, corresponding to the three encryption methods AES-128, AES-192, and AES-256 respectively. The key length determines the strength and security of the encryption, and also affects the number of encryption rounds and the key expansion process.

[0053] (1-2) Initial round key addition.

[0054] Plaintext grouping: Group the input plaintext by bytes, with each group consisting of 16 bytes (i.e. 128 bits) to form a 4x4 matrix. If the plaintext length is not a multiple of 16 bytes, padding (such as PKCS#7 padding) is required to reach the required length.

[0055] Key expansion: Based on the selected key length, a series of round keys (RoundKeys) are generated through the key expansion algorithm. These round keys will be used in the subsequent encryption process;

[0056] Initial round key addition: The initial key (i.e. the key entered by the user) is XORed with the first group of plaintext (or called the initial state matrix) as the initial input of the encryption process.

[0057] (1-3) Application of round function.

[0058] The AES encryption process is implemented through multiple round functions, each of which includes four basic operations: byte substitution (SubBytes), row shift (ShiftRows), column confusion (MixColumns) and round key addition (AddRoundKey);

[0059] SubBytes: Each byte in the state matrix is ​​replaced by a fixed S-box (Substitution Box). The S-box is a predefined substitution table used to map an input byte to another byte.

[0060] ShiftRows: Circularly shift the rows of the state matrix to the left. Specifically, the first row is not shifted, the second row is shifted left by 1, the third row is shifted left by 2, and the fourth row is shifted left by 3.

[0061] Mix Columns: Multiply the state matrix with a fixed matrix (the multiplication here is modulo 2 multiplication, that is, XOR operation) to achieve confusion between columns. However, it should be noted that the column mixing step is usually omitted in the last round of encryption;

[0062] AddRoundKey: XOR the round key generated in the current round with the state matrix to further obfuscate the data.

[0063] (1-4) Repeat the round function.

[0064] Depending on the selected key length and encryption mode (such as ECB, CBC, CFB, OFB, CTR, etc.), the above round function is repeatedly applied multiple times. For AES-128, usually 10 rounds are required; for AES-192, 12 rounds are required; for AES-256, 14 rounds are required.

[0065] (1-5) Final round of processing.

[0066] In the last round of encryption, the column obfuscation step is omitted, and only byte substitution, row shift and round key addition operations are performed. This is because in the last round, column obfuscation may no longer be necessary, or it may be omitted to simplify the decryption process.

[0067] (1-6) Output ciphertext.

[0068] The state matrix after the last round of processing is output as ciphertext by column. If the original plaintext is padded, these padding bytes need to be removed during decryption to restore the original plaintext.

[0069] Specifically in the present application, the encryption and decryption process between the first public key and the first private key, or the encryption and decryption process between the second public key and the second private key, includes:

[0070] (2-1) Secret key generation

[0071] Choose two large prime numbers: Randomly select two large and different prime numbers p and q. The larger the two prime numbers, the higher the security of the key.

[0072] Calculate the modulus n: Calculate the product of p and q n = p * q, n will be used as the modulus of the public key and private key and is public;

[0073] Calculate the Euler's totient function φ(n): Calculate φ(n) = (p - 1) * (q - 1). φ(n) is a crucial part of private key generation and should not be made public;

[0074] Select the encryption exponent e: Select an integer e such that 1 < e < φ(n) and e is relatively prime to φ(n). e will be part of the public key and is used for encryption operations;

[0075] Calculate the decryption exponent d: Solve for the modular multiplicative inverse d such that e * d = 1 (mod φ(n)). d will be part of the private key and is used for decryption operations;

[0076] At this point, we have obtained the public key (n, e) and the private key (n, d). The public key can be publicly distributed to anyone, while the private key must be kept strictly confidential.

[0077] (2 - 2) Encryption process.

[0078] To encrypt using the RSA algorithm, the following steps need to be performed:

[0079] Convert the plaintext message M into an integer form and ensure that M is less than n;

[0080] Encrypt M using the public key (n, e) and calculate the ciphertext C = M e (mod n), where "e" represents exponentiation and "mod" represents modular arithmetic;

[0081] Securely transmit the encrypted ciphertext C to the holder of the private key.

[0082] (2 - 3) Decryption process.

[0083] After the holder of the private key receives the ciphertext C, they can use the private key (n, d) to decrypt and recover the original plaintext message M:

[0084] Decrypt the ciphertext C using the private key and calculate the plaintext M = C d (mod n), where exponentiation and modular arithmetic are also used here;

[0085] The decrypted plaintext M is the original message. Only the holder of the private key can decrypt the message because only they know the private key (n, d);

[0086] Key length: To maintain the security of the RSA algorithm, a sufficiently large key length must be selected. In modern standards, a key length of at least 2048 bits is usually recommended to resist known attack methods;

[0087] Random number generation: The random numbers used in the key generation process must have good randomness to avoid potential security vulnerabilities;

[0088] Parameter selection: Choosing appropriate prime numbers p and q and the encryption exponent e is crucial to the security of the algorithm. Use secure parameter generation methods to avoid common pitfalls and weaknesses.

[0089] It can be understood that in some other implementations, in step S1 and step S2 of this implementation, the first plaintext key and the second plaintext key may also be SM1 key, SM2 key, SM3 key or SM4 key, which will not be repeated here.

[0090] It can be understood that in some other implementations, in step S1 and step S2 of this implementation, the first public key and the first private key are corresponding SM1 key, SM2 key, SM3 key or SM4 key, and the second public key and the second private key are corresponding SM1 key, SM2 key, SM3 key or SM4 key.

[0091] In this implementation, the WEB front end uses the Axios framework to define http request and response interceptors. When the encryption and decryption flags are detected in the http request, encryption and decryption operations are automatically performed in the interceptor. The flag for request parameter encryption is httpEncrypt=true, and the flag for response parameter decryption is httpDecrypt=true.

[0092] In step S2 of this implementation, the filter is used to decrypt the parameters passed in by the WEB front end, and the decrypted plain text parameters are further passed back to the processor of the WEB back end. The filter plays an important role in Java Web applications, and is mainly responsible for pre-processing or post-processing the HTTP request sent by the client to the server and the data of the server's response to the client. It is located between the WEB front end and the WEB back end program logic, so its characteristics are used to convert the ciphertext passed in by the front end into plain text parameters readable by the program.

[0093] By defining annotations for encrypted responses (i.e., annotating the data transmission interfaces of the WEB front-end and WEB back-end respectively with annotations), the response parameters are encrypted using AOP. AOP (Aspect-Oriented Programming) is a programming paradigm that allows developers to define common behaviors across multiple classes and methods without modifying existing code. AOP can be used to encrypt response parameters.

[0094] In this implementation, the server uses annotations to mark the interfaces to be encrypted, and the encryption algorithm used is as follows:

[0095] @Pointcut("@annotation(com.fosung.rsa.annotations.Encrypt)")publicvoid point () {}@Around(value = "point() && @annotation(encrypt)")publicObject around (ProceedingJoinPoint joinPoint, Encrypt encrypt) throwsThrowable { Object res = joinPoint.proceed(); String jsonString = this.objectMapper.writeValueAsString(res); String aesKeyStr = AESUtil.getAesKey(16);String content = AESUtil.encryptToBase64(jsonString, aesKeyStr); StringaesKey = RSAUtil.encryptByPublicKey(aesKeyStr, this.publicKey, 117); returnResponseParam.success().data(CommonBody.builder().aesKey(aesKey).content(content).build());}.

[0096] In this implementation, the WEB front-end stores the first private key and the second public key (stored using the configuration file), and the WEB back-end stores the second private key and the first public key (stored in the configuration file or database). The interface address to be decrypted is defined in the configuration file of the WEB back-end. If there are multiple addresses, they can be separated by English commas.

[0097] The WEB front-end interface call example is:

[0098] template3 (data) {

[0099] return http.postJson(' / api / xxxxxx / xxx', data, { httpEncrypt: true, httpDecrypt: true})

[0100] };

[0101] For the usage example of encrypted return by WEB backend, you only need to mark the @Encrypt annotation on the method declared in the interface. You can regularly replace the public key and private key to enhance data security.

[0102] In this implementation, the server implements the automatic decryption process through the filter. The specific algorithm is as follows:

[0103] @Override public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws ServletException, IOException { RepeatableReadRequestWrapper rrRequest = new RepeatableReadRequestWrapper((HttpServletRequest) request); StringBuilder json = new StringBuilder(); String line; BufferedReader reader; reader = rrRequest.getReader(); while((line = reader.readLine()) != null) { json.append(line);} JSONObject jsonObject = JSON.parseObject(json.toString()); String content = jsonObject.getString(RsaConstant.CONTENT); String aesKey = jsonObject.getString(RsaConstant.AES_KEY); if(StringUtils.isBlank(aesKey)) { throw new RemoteException("AES key is empty!");} if(StringUtils.isBlank(content)){ throw new RemoteException("Content is empty!");} aesKey = RSAUtil.decryptByPrivateKey(aesKey, this.privateKey, 128); String data = AESUtil.decryptFromBase64(content , aesKey); jsonObject = JSON.parseObject(data); jsonObject.put(RsaConstant.AES_KEY , aesKey); rrRequest.setBody(jsonObject.toJSONString().getBytes()); chain.doFilter(rrRequest,response);}.

[0104] Embodiment 2:

[0105] This implementation provides a data publishing system for crowd management and analysis in a specific industry, including a WEB front end and a WEB back end that communicate with each other;

[0106] The WEB front end assembles the attribute data of the specific industry population to be analyzed, generates a first plaintext key, and uses the first plaintext key to encrypt the assembled data to generate a first data ciphertext;

[0107] The WEB front end uses the first public key to encrypt the first plaintext key, and sends the encrypted first plaintext key and the first data ciphertext to the WEB back end;

[0108] The WEB backend uses the first private key to decrypt the first plaintext key, uses the decrypted first plaintext key to decrypt the first data ciphertext, and processes the decrypted first data ciphertext;

[0109] The WEB backend generates a second plaintext key, and uses the second plaintext key to encrypt the data of the specific industry population to generate a second data ciphertext;

[0110] The WEB backend uses the second public key to encrypt the second plaintext key, and sends the encrypted second plaintext key and the second data ciphertext to the WEB frontend. The WEB frontend uses the second private key to decrypt the second plaintext key, and uses the decrypted second plaintext key to decrypt the second data ciphertext, and renders the decrypted second data ciphertext on the page and displays and publishes it.

[0111] The specific working process of the above-mentioned data publishing system for specific industry crowd management and analysis is described in Example 1 and will not be repeated here.

[0112] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A data publishing method for crowd management analysis in a specific industry, characterized in that: The process includes: After assembling the attribute data of the specific industry population to be analyzed, a first plaintext key is generated, and the assembled data is encrypted using the first plaintext key to generate a first data ciphertext; Encrypt the first plaintext key using the first public key, send the encrypted first plaintext key and the first data ciphertext to the WEB backend, the WEB backend decrypts the first plaintext key using the first private key, decrypts the first data ciphertext using the decrypted first plaintext key, and performs pre-release processing on the decrypted first data ciphertext; Generate a second plaintext key, and use the second plaintext key to encrypt the processed data of the specific industry population before publishing to generate a second data ciphertext; Use the second public key to encrypt the second plaintext key, send the encrypted second plaintext key and the second data ciphertext to the WEB front end, the WEB front end uses the second private key to decrypt the second plaintext key, uses the decrypted second plaintext key to decrypt the second data ciphertext, renders the decrypted second data ciphertext on the page, and displays and publishes it.

2. The data publishing method for specific industry crowd management analysis according to claim 1, characterized in that: The first plaintext key and the second plaintext key are both AES keys.

3. The data publishing method for specific industry crowd management analysis according to claim 1 or 2, characterized in that: The first public key and the first private key are RSA asymmetric keys, and the second public key and the second private key are RSA asymmetric keys.

4. The data publishing method for specific industry crowd management analysis according to claim 1, characterized in that: The first plaintext key and the second plaintext key are an SM1 key, an SM2 key, an SM3 key or an SM4 key.

5. The data publishing method for specific industry crowd management analysis according to claim 1 or 4, characterized in that: The first public key and the first private key are corresponding SM1 keys, SM2 keys, SM3 keys or SM4 keys, and the second public key and the second private key are corresponding SM1 keys, SM2 keys, SM3 keys or SM4 keys.

6. The data publishing method for specific industry crowd management analysis according to claim 1, characterized in that: Use the filter to decrypt the parameters passed in by the WEB front end, and then pass the decrypted plaintext parameters to the processor of the WEB back end.

7. The data publishing method for specific industry crowd management analysis according to claim 1, characterized in that: The data transmission interfaces of the WEB front-end and WEB back-end are marked with annotations, and encryption operations are performed using AOP.

8. The data publishing method for specific industry crowd management analysis according to claim 1, characterized in that: The WEB front end uses the Axios framework to define the Http request and response interceptors. When the encryption and decryption identifiers are detected in the http request, encryption and decryption operations are automatically performed in the interceptor.

9. A data publishing system for crowd management and analysis in a specific industry, characterized in that: Includes a web front-end and a web back-end that communicate with each other; The WEB front end assembles the attribute data of the specific industry population to be analyzed, generates a first plaintext key, and uses the first plaintext key to encrypt the assembled data to generate a first data ciphertext; The WEB front end uses the first public key to encrypt the first plaintext key, and sends the encrypted first plaintext key and the first data ciphertext to the WEB back end; The WEB backend uses the first private key to decrypt the first plaintext key, uses the decrypted first plaintext key to decrypt the first data ciphertext, and processes the decrypted first data ciphertext; The WEB backend generates a second plaintext key, and uses the second plaintext key to encrypt the data of the specific industry population to generate a second data ciphertext; The WEB backend uses the second public key to encrypt the second plaintext key, and sends the encrypted second plaintext key and the second data ciphertext to the WEB frontend. The WEB frontend uses the second private key to decrypt the second plaintext key, and uses the decrypted second plaintext key to decrypt the second data ciphertext, and renders the decrypted second data ciphertext on the page and displays and publishes it.

10. The data publishing system for specific industry crowd management and analysis as claimed in claim 9, characterized in that: The data transmission interfaces of the WEB front-end and WEB back-end are marked with annotations, and encryption operations are performed using AOP.

Images