Information transmission method, system, device, storage medium and program product

Abstract

The present application provides an information transmission method, system, device, storage medium and program product, the method comprising: determining a user's authorization result for a privacy policy; wherein the privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list; generating an authorization text corresponding to the authorization result based on the type of list in the privacy policy, and sending the text to a receiving end; wherein the authorization text is used to indicate the privacy policy and the authorization result, and different authorization texts can be obtained according to changes in the list type in the privacy policy, thereby describing complex list information through the authorization text, meeting the transmission requirements of different scenarios, and realizing rapid and accurate recording and transmission of the user's authorization results, thereby improving transmission efficiency.

Description

Technical Field

[0001] The present application relates to the field of data transmission technology, and in particular to an information transmission method, system, device, storage medium and program product. Background Art

[0002] With the rapid development of the internet, users' personal privacy information is increasingly exposed, and public awareness of protecting personal privacy is also growing. When collecting user personal information during application operation, privacy compliance requirements must be met.

[0003] To implement this mechanism, it's necessary to record the "notification-consent" information between the application and the user, confirming what personal information the user has authorized the application to collect. In this context, how to quickly and accurately record and transmit user authorization results has become a pressing issue. Summary of the Invention

[0004] The main purpose of the embodiments of the present application is to provide an information transmission method, system, device, storage medium and program product, which generates authorization text from the received authorization results according to the type of list in the privacy policy, thereby quickly and accurately recording and transmitting the user's authorization results.

[0005] In a first aspect, an embodiment of the present application provides an information transmission method, including:

[0006] Determining the user's authorization result for the privacy policy; wherein the privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list;

[0007] According to the type of the list in the privacy policy, an authorization text corresponding to the authorization result is generated and sent to the receiving end; wherein the authorization text is used to indicate the privacy policy and the authorization result.

[0008] In a second aspect, an embodiment of the present application provides another information transmission method, including:

[0009] Obtaining authorization text corresponding to the user's authorization result for the privacy policy sent by the sending end; wherein the privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list;

[0010] The authorization result is determined according to the authorization text and the type of the list in the privacy policy.

[0011] In a third aspect, an embodiment of the present application provides an information transmission system, including: a privacy compliance server, a privacy compliance component;

[0012] The privacy compliance server is used to: obtain a privacy policy input by the provider of the application; wherein the privacy policy includes a list of at least one type of personal information;

[0013] The privacy compliance component is built into the application and is used to: display the privacy policy and obtain the user's authorization result for the privacy policy; wherein the authorization result is used to indicate whether the user authorizes the collection of personal information in each list; and generate the authorization text corresponding to the authorization result based on the type of list in the privacy policy;

[0014] The privacy compliance server is also used to obtain the authorization text and to verify the authorization result based on the authorization text.

[0015] In a fourth aspect, an embodiment of the present application provides an electronic device, including:

[0016] at least one processor; and

[0017] a memory communicatively coupled to the at least one processor;

[0018] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the electronic device to execute the method described in any one of the above aspects.

[0019] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the method described in any one of the above aspects is implemented.

[0020] In a sixth aspect, an embodiment of the present application provides a computer program product, including a computer program, which implements the method described in any of the above aspects when executed by a processor.

[0021] The information transmission method, system, device, storage medium and program product provided by the present application include: determining the user's authorization result for the privacy policy; wherein the privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list; based on the type of list in the privacy policy, generating an authorization text corresponding to the authorization result and sending it to the receiving end; wherein the authorization text is used to indicate the privacy policy and the authorization result, and different authorization texts can be obtained according to changes in the list type in the privacy policy, thereby describing complex list information through the authorization text, meeting the transmission requirements of different scenarios, and realizing fast and accurate recording and transmission of the user's authorization results, thereby improving transmission efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0023] Figure 1 A schematic diagram of an application scenario provided in an embodiment of the present application;

[0024] Figure 2 A flowchart of an information transmission method provided in an embodiment of the present application;

[0025] Figure 3 A schematic diagram of the structure of an authorization document provided in an embodiment of the present application;

[0026] Figure 4 A schematic diagram of the structure of a basic text provided in an embodiment of the present application;

[0027] Figure 5 A schematic diagram of the structure of a list text for a personal information list provided in an embodiment of the present application;

[0028] Figure 6 A schematic diagram of the structure of a list text of a personal information list shared with a third-party SDK provided in an embodiment of the present application;

[0029] Figure 7 A flowchart of another information transmission method provided in an embodiment of the present application;

[0030] Figure 8 A schematic diagram of the structure of an information transmission system provided in an embodiment of the present application;

[0031] Figure 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0032] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0033] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0034] First, let’s explain the terms involved in this application:

[0035] RCString (Risk and Compliance String): A string used to record the user's authorization result for the privacy policy, which can be used as the authorization text in this application.

[0036] Privacy Policy: A privacy policy is a document that tells users how other products or services will collect and use their personal information. According to relevant regulations, a double list is required in the privacy policy to inform users of the permissions and purposes requested by the application and / or third party.

[0037] The application scenarios and inventive concepts of this application are explained below.

[0038] With the increasing emphasis on user privacy across all industries and the promulgation and implementation of relevant legal documents, privacy compliance for enterprise applications has become a key legal requirement. To implement these requirements, it is necessary to record the "notice-consent" information between applications and users to determine what personal information users have authorized applications to collect.

[0039] In some technologies, applications only support a "blanket authorization" solution, meaning users cannot select which personal information the application collects and can only consent to all personal information collected as outlined in the privacy policy. This solution cannot meet the requirements for recording authorization results in complex scenarios. In such scenarios, how can user terminals quickly and accurately record and transmit authorization results to reduce storage costs and improve transmission efficiency? This is a problem that needs to be solved.

[0040] In view of this, the present application provides an information transmission method, which determines the user's authorization result of the privacy policy when transmitting the authorization result of the privacy policy, wherein the privacy policy includes at least one type of personal information list, and generates an authorization text corresponding to the authorization result according to the type of the list in the privacy policy. The authorization result and the privacy policy are represented by the authorization text, thereby achieving fast and accurate transmission of different types of privacy policies and different authorization results, improving transmission efficiency, and meeting the transmission requirements for different authorization results.

[0041] Figure 1 This is an application scenario diagram provided by the embodiment of this application. Figure 1As shown in the figure, to meet the privacy compliance requirements of applications, a privacy compliance system has been designed. The privacy compliance system includes a privacy compliance server and a privacy compliance component. An application (APP) developed by an application provider is installed on the user terminal, and the APP has a built-in privacy compliance component. The privacy compliance server provides an editor that the application provider can edit online, which can retrieve and save the privacy policy edited by the application provider. When a user first uses the APP, the privacy compliance component retrieves the privacy policy corresponding to the APP from the privacy compliance server and displays it to the user. After the user selects the option to consent to the collection of personal information by the application or a third party, the privacy compliance component obtains the authorization result. The privacy compliance component encodes the authorization result to obtain the authorization text and transmits the confirmed authorization text to the privacy compliance server. The privacy compliance server can parse the obtained authorization text to obtain the user's authorization result. Furthermore, to ensure that the application provider can prove its innocence in terms of privacy compliance and privacy security in the event of a legal dispute related to personal privacy, the privacy compliance server can use blockchain to link the privacy policy and authorization text to establish a solid evidence, enhancing the credibility of the privacy authorization and facilitating subsequent search and verification.

[0042] The information transmission method provided in the embodiment of the present application can be a process for the privacy compliance component in the above-mentioned privacy compliance solution to encode the authorization result to obtain the authorization text, which can improve the transmission efficiency and meet the requirements under different authorization results.

[0043] Optionally, the technical solution provided in this application can be applied to any scenario where the authorization results corresponding to the privacy policy need to be transmitted or stored.

[0044] For example, in the field of live broadcasting, users can watch video content through live broadcasting software. A third-party SDK (Software Development Kit) is provided in the live broadcasting software. The third-party SDK can be a payment software to realize the user's need to purchase goods from the live broadcasting software through the third-party SDK. Among them, the live broadcasting software expects to collect the user's location information, voice information, and image information, etc., and the payment software corresponds to a list of personal information shared by a third party, such as the user's billing information and location information. The privacy compliance component can adopt the method provided in the embodiment of the present application to process different types of lists and authorization results of different granularities, obtain the corresponding authorization text and transmit it.

[0045] Optionally, the privacy compliance component determines the user's authorization result for the privacy policy of the live broadcast software; the privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list; according to the type of list in the privacy policy, an authorization text corresponding to the authorization result is generated and sent to the receiving end; wherein, the authorization text is used to indicate the privacy policy and the authorization result.

[0046] Specifically, a privacy compliance component is installed within the live streaming software. It can retrieve the privacy policy entered by the corporate client providing the live streaming software from the privacy compliance server. User terminals can install the live streaming software containing the privacy compliance component and display the privacy policy to the user. The privacy compliance component can then receive the user's authorization of the privacy policy.

[0047] Among them, the personal information list is a list of personal information that the live broadcast software expects to collect. Third parties related to the live broadcast software can include various types, such as related parties, third-party SDKs and partners. The personal information list shared by third parties can include a related party sharing list, an SDK sharing list and a partner sharing list. Each list can include personal information that needs to be collected. When the privacy compliance component obtains the authorization results corresponding to each of the above lists, it can generate an authorization text according to the type of list. When the list type is different, the generated authorization text is different. For example, when there is only a personal information list, one authorization text is generated; when there is a personal information list and a personal information list shared by a third party, another authorization text can be generated.

[0048] Through the above solution, the user's authorization results can be transmitted to the privacy compliance server in the form of authorization text in the live broadcast scenario. Different authorization texts can be obtained under different authorization situations, meeting the transmission requirements of authorization results in the live broadcast field and improving transmission reliability and efficiency.

[0049] In addition, the embodiments of the present application can also be applied to other fields, for example, in the film and television field, users can watch programs through film and television series software, and set up a third-party SDK in the film and television series software. The third-party SDK can be a payment software to realize the user's needs to purchase membership and other products through the third-party SDK. When using the film and television series software to watch programs, the live broadcast software can collect the user's contact information, location information, voice information, etc.; when purchasing goods, the third-party SDK can collect the user's bill information, etc.

[0050] The following detailed description of some embodiments of the present application is provided in conjunction with the accompanying drawings. The following embodiments and features thereof may be combined with one another unless they conflict with each other. Furthermore, the sequence of steps in the following method embodiments is provided for illustrative purposes only and is not intended to be a strict limitation.

[0051] Figure 2 This is a flow chart of an information transmission method provided in an embodiment of the present application. The execution subject of the method can be any module or device with information processing function, for example, Figure 1 The privacy compliance component shown in can be used as the sender of the authorization result. Figure 2 As shown, the method includes:

[0052] Step S201: Determine the user's authorization result for the privacy policy.

[0053] The privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list.

[0054] Before generating the authorization text corresponding to the authorization result, you can first determine the authorization result of the privacy policy. Specifically, when a user opens the application for the first time, or the application's privacy policy is updated, or when the user reaches a preset time since the last authorization, the privacy compliance component will obtain the privacy policy from the privacy compliance server and display it on the user's terminal for the user to authorize the operation.

[0055] Optionally, a privacy policy may include a list of at least one type of personal information.

[0056] In one example, a privacy policy may include only a list of personal information that the application expects to collect; or only a list of personal information that the application expects to share with third parties; or it may also include a list of personal information that the application expects to collect and a list of personal information that the application expects to share with third parties. Here, third-party sharing can be used as a type, which includes multiple lists: an affiliate sharing list (also known as an affiliate APP list), an SDK sharing list (also known as an embedded SDK list), and a partner sharing list (also known as a partner third-party list).

[0057] In another example, the related party sharing list, SDK sharing list, and partner sharing list can all be used as different types. For example, the privacy policy can specifically include the following four types of personal information lists: a list of personal information that the application expects to collect, a related party sharing list, an SDK sharing list, and a partner sharing list.

[0058] Each list can include at least one piece of personal information. Users can select the personal information they wish to authorize based on their needs, allowing the privacy compliance component to obtain the user's authorization results. The authorization results indicate the user's authorization status for the collection of personal information in each list.

[0059] Optionally, the authorization result may include the user agreeing to authorize all personal information in at least one list, the user refusing to authorize all personal information in at least one list, or the user selecting and authorizing some personal information in at least one list. That is, the authorization result may be one of the above three situations, or a combination of any two or all of the above three situations.

[0060] Optionally, if a user agrees to authorize all personal information in at least one list, it means that the user can authorize all personal information in the entire privacy policy or just one list. If a user refuses to authorize all personal information in at least one list, it means that the user can refuse to authorize all personal information in the entire privacy policy or just one list.

[0061] Step S202: Generate an authorization text corresponding to the authorization result according to the type of the list in the privacy policy, and send it to the receiving end; wherein the authorization text is used to indicate the privacy policy and the authorization result.

[0062] The authorization text may be in the form of a string or other forms. Depending on the type of list in the privacy policy, an authorization text corresponding to the authorization result may be generated. When the type of list in the privacy policy is a list of personal information that the application expects to collect, an authorization text corresponding to the list may be generated; when the type of list in the privacy policy is a list of personal information shared with a third party, an authorization text corresponding to the list may be generated. As the type of list in the privacy policy changes, the authorization text may also change accordingly.

[0063] Optionally, generating an authorization text corresponding to the authorization result and sending it to the receiving end may include: after generating the authorization text corresponding to the authorization result, sending the authorization text directly to the receiving end; or, after generating the authorization text corresponding to the authorization result, encoding the authorization text, and sending the encoded authorization text to the receiving end.

[0064] The authorization text may be in the form of binary text, which may include multiple segments. After generating the authorization text corresponding to the authorization result, the authorization text may be sent directly to the receiving end, which has the advantage of a simple process. However, directly transmitting binary text has the disadvantages of having a large number of bits and a low information density, especially when a user authorizes a partial list of personal information. Each personal information list contains multiple scenarios, and each scenario corresponds to multiple pieces of personal information, which will result in a longer binary authorization text. Based on the above problem, the binary text can be encoded, and multiple bits in the binary text can be converted into one character to shorten the length of the binary text and increase the information density of the authorization text.

[0065] Optionally, a suitable encoding bit offset can be introduced, and 6 bits can be used as a unit of measurement for information volume, so that the binary text can be encoded into common uppercase and lowercase characters and numbers. For example, printable characters such as "AZ, az, 0-9, +, / " can be selected for easy storage and transmission.

[0066] For example, after obtaining the binary authorization text, every 6 bits may be converted into a character, such as 000000 corresponding to A, 000001 corresponding to B, 000010 corresponding to C, and so on, to obtain the encoded text and transmit it.

[0067] By using 6-bit encoding instead of the conventional 8-bit encoding method and mapping the binary text to multiple printable characters, the final text can be easily stored and transmitted, further improving the efficiency and accuracy of transmission.

[0068] Optionally, the receiving end can be a privacy compliance server. The user terminal sends the authorization text to the privacy compliance server through the privacy compliance component, so that the privacy compliance server can parse the authorization text to obtain the user's authorization result. For example, the privacy compliance server obtains the user's consent authorization result according to the protocol rules.

[0069] In addition, the receiving end can also be the provider's terminal. For example, when the provider is a corporate client, the receiving end can also be the corporate client's terminal. After receiving the authorization text, the privacy compliance server sends the authorization text to the corporate client for display, so that the corporate client can promptly understand the user's authorization status of the privacy policy.

[0070] The above method supports both blanket and partial authorization of the user's privacy policy. Furthermore, this solution allows for the use of concise authorization text to describe complex dual-list information. This allows for not only blanket authorization results, but also detailed authorization results for personal information and authorization results for third-party sharing of personal information. Different authorization scenarios can yield authorization texts of varying lengths, meeting transmission requirements in diverse scenarios.

[0071] In summary, the information transmission method provided in this embodiment determines the user's authorization result for the privacy policy, generates an authorization text corresponding to the authorization result according to the type of the list in the privacy policy, and sends it to the receiving end; wherein the authorization text is used to indicate the privacy policy and the authorization result, and different authorization texts can be obtained according to changes in the list type in the privacy policy, so that complex list information can be described through the authorization text, meeting the transmission requirements of different scenarios, and realizing fast and accurate recording and transmission of the user's authorization results, thereby improving transmission efficiency.

[0072] In one or more embodiments of the present application, optionally, the authorization text includes a basic text and a list text, which are used to indicate the privacy policy and the authorization result respectively;

[0073] Generate authorization text corresponding to the authorization result based on the type of list in the privacy policy, including:

[0074] According to the type of the list in the privacy policy and the authorization result, the type of the list to be processed is determined, where the list to be processed is a list containing personal information that has not been fully authorized and / or not fully rejected by the user; according to the type of the list to be processed, the authorization text corresponding to the authorization result; wherein the list text contained in the authorization text is the list text corresponding to the type of the list to be processed.

[0075] The authorization text needs to record a lot of information. In order to improve transmission efficiency, the authorization text can be divided into two parts, namely the basic text and the list text. Figure 3 A schematic diagram of the structure of an authorization document provided in an embodiment of the present application is shown as follows: Figure 3 As shown, there is only one base text. Manifest texts may or may not exist, or may include multiple manifest texts, such as Manifest Text 1, Manifest Text 2, and so on. The manifest texts require large amounts of transmission and storage. The base text contains at least one field that can be used to represent privacy policy information. If a partially authorized manifest exists, there can be at least one manifest text, with one manifest corresponding to each type of manifest text.

[0076] When a user authorizes, there may be a situation where all or none of the personal information in a certain list is authorized. If a corresponding list text is also generated for the above authorization result, there will be a problem of high computational complexity. Based on the above situation, the type of list to be processed can be determined based on the type of list and the authorization result. Among them, the list to be processed can be a list containing personal information that has not been fully authorized by the user; or, the list to be processed can be a list containing personal information that has not been fully rejected by the user; or, the list to be processed can be a list containing personal information that has not been fully authorized or fully rejected by the user, that is, a list in which some personal information is authorized. For example, a list that is fully authorized or fully rejected by the user does not belong to the list to be processed. Among them, the list to be processed will correspond to a type, such as a list of personal information that the application expects to collect or a list of personal information shared with a third party.

[0077] After determining the type of the list to be processed, the authorization text corresponding to the authorization result can be generated. By generating the corresponding authorization text for the list to be processed, the amount of calculation can be reduced. Optionally, when the list to be processed only includes the type of personal information list that the application expects to collect, only the basic text and the list text corresponding to the personal information list are generated according to the authorization result. When the list to be processed only includes the personal information list shared by a third party, only the basic text and the list text corresponding to the personal information list shared by the third party are generated according to the authorization result. When there is no list to be processed, the authorization text may only include the basic text.

[0078] If the privacy policy and authorization results are not stored separately, a large JSON file can be used to describe the personal information list and the third-party shared personal information list. This will result in a large amount of stored data, resulting in high network transmission and local storage overhead. Furthermore, as the number of authorized users increases, the amount of authorization result data received by the privacy compliance server will become very bloated.

[0079] In addition, considering that the authorization results need to be frequently stored and transmitted, by dividing the authorization text into two parts and parsing them according to the prescribed protocol, the authorization results and privacy policy can be combined and decoded to obtain the user's consent result, making the obtained authorization text very concise.

[0080] By storing the privacy policy and authorization results separately, a shorter basic text can be used to indicate the privacy policy, and an adjustable amount of manifest text can be used to indicate the authorization results. Therefore, under appropriate circumstances, it is not necessary to generate and send corresponding manifest results for each manifest, thereby reducing the amount of data stored and sent, and alleviating the overhead of network transmission and data storage.

[0081] In one or more embodiments of the present application, optionally, the basic text is also used to indicate whether the user agrees to authorize or refuses to authorize all personal information in at least one list.

[0082] Based on the above embodiment, to improve the accuracy of the generated authorization text, a preset field may be added to the basic text to indicate whether the user agrees to authorize or refuses to authorize all personal information in at least one list. Agreeing to authorize all personal information in a list is called a full authorization, and refusing to authorize all personal information in a list is called a full rejection.

[0083] The list of indications may be one or more, and may include only indications of full authorization, only indications of full rejection, or both. A preset number of fields may be set, and each field may be set to a preset value to indicate full authorization or full rejection.

[0084] For example, there may be two preset fields, one for indicating whether the user fully authorizes the personal information list and the other for indicating whether the personal information list shared with a third party is fully authorized. For example, a value of 1 in the preset field indicates full authorization, and a value of 0 in the preset field indicates partial authorization.

[0085] In another example, the number of preset fields may be one, which is used to indicate whether the user fully authorizes the personal information in the entire privacy policy.

[0086] In another example, the number of preset fields can be four, indicating whether the user fully authorizes the personal information list, whether the user fully authorizes the personal information list shared by a third party, whether the user fully rejects the personal information list, whether the user fully rejects the personal information list shared by a third party, etc.

[0087] Optionally, for a certain type of manifest, if the authorization text does not contain the manifest text corresponding to the manifest, and the basic text does not contain an indicator bit indicating whether the manifest is fully authorized or fully rejected, a default value can be used, for example, the default value is that the manifest is fully rejected.

[0088] By indicating in the basic text whether the user fully authorizes or fully rejects the list, the privacy compliance server can quickly and accurately know the list that is fully authorized or fully rejected after receiving the authorization text. There is no need to query the authorization status of each personal information in the list from the authorization text, which improves the parsing efficiency and accuracy.

[0089] In one or more embodiments of the present application, optionally, the basic text specifically includes the following fields:

[0090] The protocol version field is used to indicate the version of the protocol used to generate the authorization text based on the authorization result;

[0091] The privacy version field is used to indicate the version of the privacy policy;

[0092] The full quantity indication field includes indication bits corresponding to one or more types of lists. The indication bits corresponding to any type of list include at least one of the following:

[0093] Full authorization indicator, used to indicate whether all personal information in the list has been authorized by the user;

[0094] The full rejection indicator is used to indicate whether all personal information in the list has been rejected by the user.

[0095] Optionally, the base text can be a fixed-length basic information segment. The base text can contain multiple fields, representing privacy policy and agreement information. The protocol refers to the encoding / decoding protocol. When the protocol changes, the rules for generating the authorization text based on the authorization result also change.

[0096] Figure 4 A schematic diagram of the structure of a basic text provided in an embodiment of the present application, wherein the basic text may include a protocol version field, a privacy version field, and a full amount indication field, and the full amount indication field corresponds to Figure 4 The full authorization indication bit for the personal information list, the full authorization indication bit for the third-party sharing list, the full rejection indication bit for the personal information list, and the full rejection indication bit for the third-party sharing list.

[0097] The privacy compliance component can generate authorization text based on the authorization result according to the protocol, and the privacy compliance server can parse the authorization text into the authorization result according to the protocol. The protocol can include multiple versions, and the protocol version can be identified in the base text through the protocol version field, which can be represented as version.

[0098] The basic text may also include a privacy version field, which indicates the version of the privacy policy, that is, the version of the personal information list and the version of the personal information list shared with a third party. This field may be represented as privacyListVersion.

[0099] The user terminal and privacy compliance server store the version information of the privacy policy, as well as metadata for the personal information list and the personal information list shared with third parties. Optionally, the metadata for the personal information list may include: scenario number information, and the number and description of the personal information list requiring authorization in each scenario. The metadata for the personal information list shared with third parties may include: the third-party number, the number, name, and description of the scenario associated with each third-party number, and the number and description of the personal information list requiring authorization in each scenario node.

[0100] The user terminal can generate an authorization text based on the metadata information and transmit it to the privacy compliance server. After receiving the authorization text, the privacy compliance server can parse the authorization text to obtain the user's authorization result. Specifically, the privacy compliance server compares the privacy version field in the base text with the version information of the stored privacy policy to determine the privacy policy to which the authorization text refers. It also determines the version of the encoding / decoding protocol based on the protocol version field in the base text and parses the authorization text based on the determined encoding / decoding protocol.

[0101] In addition, the basic text may also include at least one of a full authorization indicator and a full rejection indicator. The full authorization indicator indicates whether the user authorizes all personal information in the list. This indicator may include an indicator for the personal information list and an indicator for the personal information list shared with a third party.

[0102] The full rejection indicator indicates whether the user refuses to authorize all personal information in the list. The indicator can also include an indicator for the personal information list and an indicator for the personal information list shared with a third party.

[0103] Setting the full indication field can reduce the setting of list fields, improve the efficiency of generating authorization fields and the efficiency of parsing authorization texts by the privacy compliance server. By setting the protocol version field and privacy version field in the basic text to accurately determine the privacy policy and decoding protocol, the user's authorization status can be accurately parsed, further improving parsing efficiency and accuracy.

[0104] Further, such as Figure 4 As shown, the basic text may also include:

[0105] The certificate service identification field cmpId is used to indicate the identification of the server that provides the certificate function for the authorization result; the certificate service version field cmpVersion is used to indicate the version number of the certificate function; the creation time field created is used to indicate the creation time of the authorization text.

[0106] Setting the ID field for the certificate service in the basic text can identify the service provider providing the certificate service, making it easier for the privacy compliance server to record the service provider providing the certificate service. By setting the ID field for the certificate service version, the version number of the certificate service can be determined, facilitating later statistical calculations, such as the number of users authorized for different versions of the certificate function. By setting the creation time, the privacy compliance server can record the user's authorization time, making it easier to accurately determine the summary and credentials corresponding to the authorization result based on the authorization time, facilitating verification.

[0107] In one or more embodiments of the present application, optionally, if at least one indicator bit in the full indication field indicates a positive result, the authorization text specifically includes the basic text and the list text corresponding to the following list: other lists other than the list corresponding to the at least one indicator bit.

[0108] After determining the base text, the manifest text can be determined based on the content of the full-quantity indication field in the base text. If a full-quantity indication field indicates a positive result, indicating that the user authorizes or rejects all personal information in the manifest corresponding to that indication field, the manifest text corresponding to that manifest can be omitted to improve the efficiency of generating the authorization text.

[0109] Specifically, the full indication field contains multiple indicator bits. When at least one indicator bit is positive, the authorization text includes the basic text and the manifest text, where the manifest text is a list other than the list corresponding to the at least one indicator bit. For example, when the full authorization indicator bit for the personal information list is positive, the authorization text includes the basic text and the manifest text corresponding to the personal information list shared by the third party.

[0110] Optionally, the numerical value of the full authorization indicator and / or the full rejection indicator includes a first numerical value and a second numerical value, which indicates yes when it is the first numerical value and no when it is the second numerical value; when at least one of the full indicator bits is the first numerical value, the list text of the list corresponding to the indicator bit is omitted in the authorization text.

[0111] Exemplarily, the first value is 1 and the second value is 0. Then, when a full amount indicator is 1, the list text of the list corresponding to the indicator is omitted.

[0112] Specifically, when determining the indication result of the full indication field, it can be determined by the result of page rendering. Among them, when the user needs to perform an authorization operation on a list, the privacy compliance component will obtain the privacy policy from the privacy compliance server and render it on the user terminal page. When the user agrees to fully authorize the content displayed on the page, the privacy compliance component will obtain the result of the full authorization, and then it can be determined that the full authorization indicator corresponding to the list is the first value; on the contrary, when the user agrees to partially authorize the content displayed on the page, it can be determined that the full authorization indicator corresponding to the list is the second value. In addition, the method of determining the value corresponding to the full rejection indication bit is similar to the above process and will not be repeated here.

[0113] When it is determined that the full indication field corresponding to the list is a positive result, there is no need to set the list text corresponding to the list, and there is no need to parse it when the privacy compliance server is performing parsing.

[0114] The full indication field can be used to determine the authorization status of a list. When it is fully authorized or fully denied, there is no need to add list text for the list, which reduces the length of the authorization text. While ensuring accuracy, it can reduce the generation time of the authorization text and improve the efficiency of generating the authorization text. At the same time, the efficiency of parsing the authorization text by the privacy compliance server will also be improved.

[0115] In one or more embodiments of the present application, each list may optionally be configured with at least one scenario; each scenario may be configured with at least one item of personal information that is expected to be collected in that scenario; and a process of generating a list text corresponding to a list may include:

[0116] Determine the number of authorized scenes in the list; and generate corresponding list text according to the number of authorized scenes.

[0117] Current privacy policies all provide blanket consent and authorization, and are unable to categorize personal information according to specific scenarios. In reality, when users authorize personal information in a privacy policy, they usually want to allow applications or third parties to collect some personal information, but do not want applications or third parties to collect all personal information.

[0118] Based on the above problem, at least one scenario can be set in the list, and for each scenario, at least one item of personal information expected to be collected in the scenario can be set.

[0119] For example, taking live broadcast software as an example, the scenarios in which live broadcast software needs to obtain user personal information may include: modifying personal data scenarios, creating live broadcast rooms, watching live broadcasts, and payment scenarios. For each scenario, a corresponding index can be set, that is, a list of personal information that needs to be collected in that scenario. For the scenario of modifying personal data, the index information may include: avatar information, name information, mobile phone number, address and other information; for the scenario of creating a live broadcast room, the index information may include: location information, camera information and voice information; for the scenario of watching live broadcasts, the index information may include location information and network information; for the scenario of payment, the index information may include: user name, mobile phone account, bill information and balance information, etc. Through the above settings, users can not only authorize in a package authorization manner, but also agree to authorization in categories according to scenarios or purposes.

[0120] Based on the above setting of the scenes in the list, the process of generating the list text may be: determining the number of authorized scenes in the list, and determining the list text based on the number of authorized scenes.

[0121] For example, for the above live broadcast software, when the user partially or fully authorizes the personal information in the three scenarios in the personal information list, it can be determined that the number of authorized scenarios is 3.

[0122] After the number of authorized scenes is determined, a manifest text may be generated, that is, the content of the manifest text is related to the number of authorized scenes.

[0123] By distinguishing by scenario in the list, authorization can be implemented in different categories according to the scenario. For unauthorized scenarios, the corresponding fields can be omitted in the list text, thereby further saving the amount of data in the authorization text and further improving the efficiency of generating and parsing the authorization text.

[0124] In one or more embodiments of the present application, optionally, the list text corresponding to the list includes:

[0125] A number of scenes field, used to indicate the number of authorized scenes in the list; and

[0126] N scenario detail fields, where N is the number of authorized scenarios; each scenario detail field includes: a scenario identification field, used to indicate the identification of the scenario; and an authorization field, used to indicate the personal information that agrees to be authorized under the scenario.

[0127] Figure 5 A structural diagram of a list text for a personal information list provided in an embodiment of the present application is shown as follows: Figure 5 As shown, the manifest text includes a scenario number field and a scenario details field. In this embodiment, the scenario number field can be represented as privacyNumbers, indicating the number of authorized scenarios in the manifest. Authorization here includes full authorization and partial authorization, that is, personal information in a certain scenario is fully authorized or personal information in a certain scenario is partially authorized.

[0128] The scene detail field is a circular body of data. Each scene detail field includes a scene identification field and an authorization field. When the scene quantity field is N, the number of scene detail fields is also N. Figure 5 As shown, the Scenario Quantity field indicates that the number of scenarios is 2, so the number of Scenario Details fields is also 2. The Scenario Details field is used to indicate the user's authorization status for each authorized scenario. Specifically, the Scenario Details field is set based on the number of authorized scenarios. Specifically, the Scenario Details field is set for authorized scenarios, and is not set for unauthorized scenarios.

[0129] Among them, the scenario identification field can be expressed as scenarioId, which indicates the identification of the scenario, such as the authorized scenario ID. According to the scenario identification field, all personal information that the application or third party expects to collect in the scenario can be determined. For each scenario identification field, an authorization field can be set, and the authorization field indicates the authorization status of all personal information in the corresponding authorization scenario. According to the authorization field and the scenario identification field, the specific personal information authorized by the user can be accurately determined. In order to facilitate the parsing of the privacy compliance server, the position of the scenario identification field and the authorization field in the scenario detail field can be limited, with the scenario identification field set in front and the authorization field set in the back.

[0130] It should be noted that when the number of scenarios field is 0, it means that the length of the scenario details field is 0. Therefore, there is no need to parse the list text to determine that the user has refused to authorize all personal information in the list. When the number of scenarios field is not 0, the scenario details field needs to be parsed.

[0131] By setting the scenario quantity field and the scenario detail field in the above manner, the scenario detail field can be set in a targeted manner, which can save the data volume of the authorization list text, further save the data volume of the authorization text, and improve the parsing efficiency of the privacy compliance server.

[0132] In one or more embodiments of the present application, the authorization field may optionally include: a full authorization field, used to indicate whether all personal information in the scenario is fully authorized;

[0133] If only part of the personal information is authorized in this scenario, the authorization field also includes: an index field, each bit in the index field is used to represent each piece of personal information in this scenario, and the value of each bit is used to indicate whether the corresponding personal information is authorized.

[0134] The full authorization field can be represented as pcFullGrant. When all personal information in the corresponding scenario is fully authorized, the value of the full authorization field can be set to a first value; when only part of the personal information in the corresponding scenario is authorized or none of the personal information is authorized, the value of the full authorization field can be set to a second value. For example, the first value can be 1 and the second value can be 0.

[0135] Optionally, if only some personal information is authorized or all personal information is denied in this scenario, the authorization field may include an index field. That is, when the full authorization field is the second value, the authorization field may also include an index field, represented as privacies scenario. The index field may have multiple digits, corresponding to each piece of personal information in the scenario. The value of each digit in the index field is determined based on the user's authorization status for each piece of personal information.

[0136] For example, when the value of a bit in the index field is a first value, it indicates that the user has authorized the personal information corresponding to that bit; when the value of a bit in the index field is a second value, it indicates that the user has not authorized the personal information corresponding to that bit. For example, the first value may be 1, and the second value may be 0.

[0137] like Figure 5As shown, the scene identification fields are scene identification ID1 and scene identification ID2. For each scene identification, a field is set to indicate whether the scene is fully authorized, that is, whether scene ID1 is fully authorized and whether scene ID2 is fully authorized. When this field is 0, it is necessary to set the personal information consent status of each index bit ID; when this field is 1, there is no need to set the index field.

[0138] Optionally, the number of digits in the index field can be set to a fixed value. This fixed value can be set based on actual circumstances. For example, if it is set to M, it means that a maximum of M types of personal information can be set for each scenario. When the number of personal information corresponding to a scenario is N, and N is less than M, only the values ​​of the first N items are set, and the last M items are set to the second value. For example, if M is 12 and N is 4, the first four items in the index field can be set to 1 or 0 based on the user's authorization, and the last 8 bits are set to 0.

[0139] Alternatively, the index fields corresponding to different scenarios may be different, and the length of a specific index field may be equal to the amount of personal information in the scenario. When there are only M items of personal information in a scenario, the corresponding index field may be M bits.

[0140] The setting of the index field allows the authorization result of each piece of personal information in the scenario to be described with 1 bit, which can effectively control the length of the authorization text.

[0141] When the full authorization field determines that the user has authorized all personal information in the scenario, there is no need to set the index field.

[0142] Optionally, the order of the scenario identification field and the authorization field can be set according to actual needs. For example, in addition to Figure 5 The scheme shown can also be set in the following order: full authorization field, scenario identification field, index field.

[0143] Optionally, the authorization field may also include: a full rejection field, which is used to indicate whether all personal information in the scenario is rejected. Accordingly, the authorization field includes the index field only when some personal information is authorized in the scenario.

[0144] By setting the full authorization field through the authorization field, when the user fully authorizes a certain scenario, the length of the manifest text can be reduced, which facilitates the transmission of the authorization text and further improves the efficiency of generating and parsing the authorization text. In addition, by setting the index field, the user's authorization status of personal information for a certain scenario can be accurately represented.

[0145] Optionally, the list text corresponding to the list of personal information that the application expects to collect can be implemented using the above solution.

[0146] Optionally, when there is a third party, a manifest text corresponding to the third party may be generated. The specific process is as follows.

[0147] Optionally, the list of personal information expected to be shared with a third party includes at least one type of list; each type of list corresponds to at least one third party; each third party corresponds to at least one item of personal information expected to be shared with the third party; the list text corresponding to each type of list specifically includes:

[0148] A third party quantity field is used to indicate the number of authorized third parties in the list; and

[0149] K third-party fields, where K is the number of authorized third parties. Each third-party field includes: a third-party identification field, used to indicate the third-party's identity; and a third-party full authorization field, used to indicate whether all personal information corresponding to the third party is authorized.

[0150] If only part of the personal information of the third party is authorized, the third party field also includes: a scene quantity field and a scene detail field.

[0151] Optionally, the list of personal information you wish to share with third parties may include the following three types: an affiliate sharing list, an SDK sharing list, and a partner sharing list. For each type of list, at least one third party may be set, and each third party may be set with at least one item of personal information you wish to share with that third party. For example, an SDK sharing list may include three third-party SDKs, each of which may be set with multiple scenarios, and each scenario may be set with at least one item of personal information that needs to be collected.

[0152] The following describes the third-party SDK as a third-party type.

[0153] The manifest text may include: a third-party quantity field, which represents the number of authorized third-party SDKs in the manifest, expressed as sdkNumbers. When there are M authorized third-party SDKs, there are M third-party fields, each of which is used to represent the authorized personal information corresponding to each third party. Specifically, the identification field can be expressed as SDKID; the third-party full authorization field can be expressed as scFullGrant. The value setting of the third-party full authorization field is similar to the setting method of the full authorization field described above and will not be repeated here.

[0154] When it is determined through the third-party full authorization field that only part of the personal information of a third party is authorized, it is also necessary to set the scenario number field scenaryNumbers, which indicates the number of scenarios for which consent is granted. The scenario detail field may include a scenario identifier and an authorization field, wherein the authorization field includes a full authorization field, which means that when it is determined based on the full authorization field that the user is only authorized for part of the personal information under the scenario, the authorization field may also include an index field. The specific implementation of the authorization field is similar to the list text corresponding to the above-mentioned personal information and will not be repeated here.

[0155] Figure 6 A structural diagram of a list text of a personal information list shared with a third-party SDK provided in an embodiment of the present application, such as Figure 6 As shown, the list text includes the number of third-party SDKs (third-party quantity field), authorized SDKID1 (identification field), whether SDKID1 is fully authorized (third-party full authorization field), the number of scenarios approved by SDKID1 (scene quantity field), scene ID1 authorized under SDKID1 (scene identification), whether the scene ID1 of SDKID1 is fully authorized (full authorization field), and when whether the scene ID1 of SDKID1 is fully authorized is not fully authorized, it also includes the personal information consent status of each index position ID (index field).

[0156] In one or more embodiments of the present application, optionally, the basic text and the list text, and adjacent list texts are separated by preset characters.

[0157] Since the generated authorization text may contain a base text and multiple manifest texts, if the generated authorization text is directly stored or transmitted, the privacy compliance server needs to traverse each field in the authorization text to determine the base text and each manifest text when parsing. When only a certain manifest text needs to be parsed, the manifest text cannot be quickly determined using the above method. Based on the above problem, preset characters can be set between the base text and the manifest text, and between adjacent manifest texts, so that the base text and each manifest text can be quickly determined based on the preset characters. There is no restriction on the form of the preset characters.

[0158] For example, when the authorization text is an encoded operation, the authorization text may be in the following format: "'CPQKMgHPQKMgHBgA.AAENAwCwAAAAAAAAAIAA.DAEYDADAART'". When the second list text needs to be queried, the position of the second preset character is first determined, and the authorization text after the second preset character is the second list text.

[0159] By splicing the various parts of the text using preset characters, the list text to be queried can be quickly determined during parsing, which can improve the parsing efficiency of the authorization text.

[0160] In an embodiment of the present application, the content of the authorization text can be adaptively adjusted according to the type of list in the privacy agreement. In one example, when a double list is included in the privacy agreement (a list of personal information that the application expects to collect and a list of personal information shared with a third party), the last field of the basic text can include 4 bits, indicating the full authorization and full rejection of the double list respectively. In the case where neither of the double lists is fully authorized or fully rejected, two list texts can be set to indicate the specific authorization status of the double list.

[0161] In another example, a privacy agreement may include a list of personal information that the application expects to collect and a list of personal information shared with third parties. The list of personal information shared with third parties includes a list shared with affiliates, a list shared with SDKs, and a list shared with partners. In this case, there may be four list texts, each representing the specific authorization status of each list.

[0162] In actual applications, the types and number of lists included in the privacy policy can be set according to relevant laws and regulations and customer needs, and the embodiments of this application do not impose specific restrictions on this.

[0163] Optionally, in one or more embodiments of the present application, determining the result of the user's authorization of the privacy policy may include:

[0164] Obtaining and displaying the privacy policy; wherein the privacy policy is displayed in a tree structure, the tree structure sequentially including the following multiple layers: list, third party, scenario, personal information; the nodes in each layer are child nodes of the nodes in the previous layer;

[0165] Obtaining a user's consent or rejection operation on at least one node in the tree structure, and determining the user's authorization result for the privacy policy based on the user's operation;

[0166] The user's approval or rejection of the parent node is used to update the corresponding full authorization field in the authorization text.

[0167] The privacy compliance component retrieves the application's privacy policy from the privacy compliance server or local storage and displays it to the user. To facilitate user authorization, the privacy policy can be displayed in a tree structure. This tree structure can be configured in multiple levels, such as checklists, third parties, scenarios, and personal information.

[0168] When obtaining the user's consent or rejection of the tree structure, the authorization result of the privacy policy can be determined. When the user consents to or rejects a parent node, the full authorization field in the user's authorization text can be determined. For example, when the user consents to the list of personal information that the application expects to collect, the corresponding full authorization field in the base text can be modified; when the user fully authorizes a certain scenario in the personal information list, the full authorization field corresponding to the scenario in the corresponding list text can be modified.

[0169] Among them, the nodes contained in each layer are the child nodes of the previous layer. For example, a scene node can contain 12 child nodes, and each child node corresponds to a piece of personal information that is expected to be collected. When the user directly authorizes a scene, all 12 nodes under the scene will be authorized, and the full authorization field corresponding to the scene identifier can be directly determined.

[0170] The above method can conveniently and quickly determine the user's authorization result for the privacy policy, further improving the efficiency of the privacy compliance component in generating authorization text.

[0171] Figure 7 A flowchart of another information transmission method provided in an embodiment of the present application, which can be applied to the receiving end of the authorization text, such as the privacy compliance service end, such as Figure 7 As shown, the method includes:

[0172] Step 701: Obtain the authorization text corresponding to the user's authorization result for the privacy policy sent by the sender; wherein the privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list.

[0173] Step 702: Determine the authorization result based on the authorization text and the type of the list in the privacy policy.

[0174] In one or more embodiments of the present application, optionally, the authorization text includes a basic text and a list text, which are used to indicate the privacy policy and the authorization result respectively;

[0175] Determine the authorization result based on the authorization text and the type of the list in the privacy policy, including:

[0176] Determine the type of the list to be processed based on the type of list and the authorization text in the privacy policy, where the list to be processed is a list containing personal information that has not been fully authorized and / or not fully rejected by the user; the list text contained in the authorization text is the list text corresponding to the type of list to be processed;

[0177] The authorization result is determined according to the type of the list to be processed.

[0178] The process of parsing the authorization text to obtain the authorization result in this embodiment can be viewed as the reverse process of generating the authorization text based on the authorization result in the aforementioned embodiment. Using the rules and principles described in the aforementioned embodiment, the receiving end can restore the user's authorization result and perform operations such as storing and securing the authorization result.

[0179] The implementation principle and technical effects of the information transmission method provided in this embodiment can be found in the aforementioned embodiments and will not be described again here.

[0180] Corresponding to the above method, an embodiment of the present application further provides an information transmission device, applied to a transmitting end, the device comprising:

[0181] The first determination module is used to determine the user's authorization result for the privacy policy; wherein the privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list.

[0182] A processing module is used to generate an authorization text corresponding to the authorization result according to the type of the list in the privacy policy, and send it to the receiving end; wherein the authorization text is used to indicate the privacy policy and the authorization result.

[0183] The present application also provides another information transmission device, which is applied to a receiving end and includes:

[0184] The acquisition module is used to obtain the authorization text corresponding to the user's authorization result for the privacy policy sent by the sender; wherein, the privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list.

[0185] The second determining module is used to determine the authorization result according to the authorization text and the type of the list in the privacy policy.

[0186] Figure 8 A structural diagram of an information transmission system provided in an embodiment of the present application includes: a privacy compliance server and a privacy compliance component.

[0187] The privacy compliance server is used to obtain a privacy policy input by a provider of an application; wherein the privacy policy includes a list of at least one type of personal information.

[0188] The privacy compliance component is built into the application and is used to: display the privacy policy and obtain the user's authorization result for the privacy policy; wherein the authorization result is used to indicate whether the user authorizes the collection of personal information in each list; and generate the authorization text corresponding to the authorization result based on the type of list in the privacy policy.

[0189] The privacy compliance server is also used to obtain the authorization text and to verify the authorization result based on the authorization text.

[0190] The specific implementation principles and technical effects of the devices and systems provided in the embodiments of the present application can be found in the aforementioned embodiments and will not be repeated here.

[0191] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 9 As shown, the electronic device of this embodiment may include:

[0192] at least one processor 901; and

[0193] a memory 902 communicatively connected to the at least one processor 901;

[0194] The memory 902 stores instructions that can be executed by the at least one processor 901, and the instructions are executed by the at least one processor 901 to enable the electronic device to execute the method as described in any of the above embodiments.

[0195] Optionally, the memory 902 may be independent or integrated with the processor 901 .

[0196] The implementation principle and technical effects of the electronic device provided in this embodiment can be found in the aforementioned embodiments and will not be described in detail here.

[0197] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions. When a processor executes the computer-executable instructions, the method described in any of the above embodiments is implemented.

[0198] An embodiment of the present application further provides a computer program product, including a computer program, which implements the method described in any of the aforementioned embodiments when executed by a processor.

[0199] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of modules is merely a logical function division. In actual implementation, other division methods may be used. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not implemented.

[0200] The above-mentioned integrated module implemented in the form of a software functional module can be stored in a computer-readable storage medium. The above-mentioned software functional module is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) or a processor to perform some steps of the method described in each embodiment of the present application.

[0201] It should be understood that the above-mentioned processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor. The memory may include high-speed RAM memory, and may also include non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0202] The storage medium may be implemented by any type of volatile or non-volatile memory device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0203] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic device or a main control device.

[0204] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0205] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0206] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0207] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. An information transmission method, characterized in that: include: Determining the user's authorization result for the privacy policy; wherein the privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list; each list is configured with at least one scenario; and each scenario is configured with at least one item of personal information that is expected to be collected in that scenario; According to the type of the list in the privacy policy, generate the authorization text corresponding to the authorization result, encode the authorization text with 6 bits, and send the encoded authorization text to the receiving end; wherein, the authorization text is used to indicate the privacy policy and the authorization result; the type of the list in the privacy policy includes at least one of the following types of personal information lists: a list of personal information that the application expects to collect, a list of personal information shared with a third party; the authorization text includes a basic text and a list text, which are used to indicate the privacy policy and the authorization result respectively; the basic text and the list text, as well as adjacent list texts, are separated by preset characters; the list text is generated according to the number of authorized scenarios in the list; the list text corresponding to the list includes: a scenario number field, which is used to indicate the number of authorized scenarios in the list; and N scenario detail fields, where N is the number of authorized scenarios; wherein each scenario detail field includes: a scenario identification field, which is used to indicate the identification of the scenario; and an authorization field, which is used to indicate the personal information that agrees to be authorized under the scenario; The basic text specifically includes the following fields: a full indication field, including indication bits corresponding to one or more types of lists; the indication bits corresponding to any type of list include at least one of the following: a full authorization indication bit, used to indicate whether all personal information in the list is authorized by the user; a full rejection indication bit, used to indicate whether all personal information in the list is rejected by the user.

2. The method according to claim 1, characterized in that Generate authorization text corresponding to the authorization result based on the type of list in the privacy policy, including: Determine the type of the list to be processed based on the type of the list in the privacy policy and the authorization result, where the list to be processed is a list containing personal information that has not been fully authorized and / or not fully rejected by the user; According to the type of the list to be processed, an authorization text corresponding to the authorization result is generated; wherein the list text included in the authorization text is the list text corresponding to the type of the list to be processed.

3. The method according to claim 2, characterized in that The basic text is also used to indicate whether the user agrees to authorize or refuses to authorize all personal information in at least one list.

4. The method according to claim 3, characterized in that The basic text specifically includes the following fields: The protocol version field is used to indicate the version of the protocol used to generate the authorization text based on the authorization result; The Privacy Version field is used to indicate the version of the privacy policy.

5. The method according to claim 4, characterized in that If at least one indicator bit in the full indication field indicates a positive result, the authorization text specifically includes the basic text and the list text corresponding to the following lists: other lists other than the list corresponding to the at least one indicator bit.

6. The method according to claim 2, characterized in that The process of generating a list text corresponding to a list includes: determining the number of authorized scenes in the list; Generate corresponding manifest text based on the number of authorized scenarios.

7. The method according to claim 1, characterized in that The authorization field includes: a full authorization field, which is used to indicate whether all personal information in the scenario is fully authorized; If only part of the personal information is authorized in this scenario, the authorization field also includes: an index field, each bit in the index field is used to represent each piece of personal information in this scenario, and the value of each bit is used to indicate whether the corresponding personal information is authorized.

8. An information transmission method, characterized in that: include: Obtaining authorization text corresponding to the user's authorization result for the privacy policy sent by the sender; wherein the privacy policy includes at least one type of personal information list; the authorization result is used to indicate whether the user authorizes the collection of personal information in each list, wherein the authorization text is 6-bit encoded text; each list is set with at least one scenario; and each scenario is set with at least one item of personal information expected to be collected in that scenario; Determine the authorization result according to the authorization text and the type of the list in the privacy policy; The types of lists in the privacy policy include at least one of the following types of personal information lists: a list of personal information that the application expects to collect, and a list of personal information shared with third parties; the authorization text includes a basic text and a list text, which are respectively used to indicate the privacy policy and the authorization result; the basic text and the list text, as well as adjacent list texts, are separated by preset characters; the list text is generated based on the number of authorized scenarios in the list; the list text corresponding to the list includes: a scenario number field, which is used to indicate the number of authorized scenarios in the list; and N scenario detail fields, where N is the number of authorized scenarios; wherein each scenario detail field includes: a scenario identification field, which is used to indicate the identification of the scenario; and an authorization field, which is used to indicate the personal information that is consented to be authorized under the scenario; The basic text specifically includes the following fields: a full indication field, including indication bits corresponding to one or more types of lists; the indication bits corresponding to any type of list include at least one of the following: a full authorization indication bit, used to indicate whether all personal information in the list is authorized by the user; a full rejection indication bit, used to indicate whether all personal information in the list is rejected by the user.

9. A privacy compliance system, characterized in that: include: Privacy compliance server and privacy compliance components; The privacy compliance server is configured to obtain a privacy policy input by the application provider; wherein the privacy policy includes at least one type of personal information list; each list corresponds to at least one scenario; and each scenario corresponds to at least one item of personal information that is expected to be collected in that scenario; The privacy compliance component is built into the application and is used to: display the privacy policy and obtain the user's authorization result for the privacy policy; wherein the authorization result is used to indicate whether the user authorizes the collection of personal information in each list; and generate an authorization text corresponding to the authorization result based on the type of list in the privacy policy, wherein the authorization text is 6-bit encoded text; The privacy compliance server is further used to: obtain the authorization text and implement the certification of the authorization result according to the authorization text; the types of lists in the privacy policy include at least one of the following types of personal information lists: a list of personal information that the application expects to collect, a list of personal information shared by a third party; the authorization text includes a basic text and a list text, which are respectively used to indicate the privacy policy and the authorization result; the basic text and the list text, as well as adjacent list texts, are separated by preset characters; the list text is generated according to the number of authorized scenarios in the list; the list text corresponding to the list includes: a scenario number field, which is used to indicate the number of authorized scenarios in the list; and N scenario detail fields, where N is the number of authorized scenarios; wherein each scenario detail field includes: a scenario identification field, which is used to indicate the identification of the scenario; an authorization field, which is used to indicate the personal information that agrees to be authorized under the scenario; The basic text specifically includes the following fields: a full indication field, including indication bits corresponding to one or more types of lists; the indication bits corresponding to any type of list include at least one of the following: a full authorization indication bit, used to indicate whether all personal information in the list is authorized by the user; a full rejection indication bit, used to indicate whether all personal information in the list is rejected by the user.

10. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively coupled to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the electronic device to perform the method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions. When a processor executes the computer-executable instructions, the method according to any one of claims 1 to 8 is implemented.

12. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images