CN113260996A

CN113260996A - Data display method

Info

Publication number: CN113260996A
Application number: CN201880100356.9A
Authority: CN
Inventors: 王小松
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-12-29
Filing date: 2018-12-29
Publication date: 2021-08-13
Also published as: WO2020133477A1

Abstract

There is provided a data display method applied to a first application program having a first user interface, the first application program being provided on an electronic device, the data display method including: the method comprises the steps of requesting a server for a data hiding rule through a message, receiving the data hiding rule returned by the server, wherein the message comprises an identifier of a first application program and a user token, and applying the data hiding rule to sensitive data and carrying out hiding display on the sensitive data based on a semantic analysis result of candidate data.

Description

[ inventive name made by ISA according to rules 37.2 ] data display method

Technical Field

The present application relates to the field of information, and in particular, to a data display method, a corresponding storage medium, and an electronic device.

Background

In daily life, people can not avoid the need of using electronic equipment to check private or sensitive information which is felt by some individuals in a public environment, and the people can inevitably be peeped at the information which is not wanted to be disclosed by the individuals, so that the peeped people can feel embarrassed or uneasy, and the use experience of using tools such as chatting software or notebooks and the like in public occasions is reduced.

If the mobile phone is lent or lost, the sensitive information is more likely to be leaked, and the influence on the user is more serious.

At present, software such as chatting software, recordable tools and the like has a coarse-grained method for treating sensitive data, namely, a secondary password is added. Opening the cell phone requires a first-level password or fingerprint, and opening the APP or opening the privacy data in the APP requires a second-level password or fingerprint.

And a coded lock is added to the whole data, so that the use by a user is inconvenient.

Most of the encrypted data are not sensitive, for example, chat contents are added with a password lock, passwords are input for the chat contents A and B, even if the passwords are printed, the fingerprints need to be clicked, the operation is complicated, the use experience is reduced, and users do not want to use the passwords. If a password is used instead of a fingerprint, the memory burden of the user is also increased.

Disclosure of Invention

The embodiment of the application provides a fine-grained data hiding processing mechanism, anonymization is carried out on data fragments which are really sensitive to a user, and the user cannot be influenced to see. In addition, the data hiding processing mechanism carries out hiding processing on the candidate data through semantic analysis, and can provide more accurate and convenient hiding for different candidate data.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, a data display method is provided, where the data display method is applied to a first application program, the first application program has a first user interface, and the first application program is disposed on an electronic device, and the data display method includes:

step 1: requesting a data hiding rule from a server via a message, the message comprising an identification of a first application and a user token of a first user,

step 2: receiving a data hiding rule returned by the server, wherein the data hiding rule comprises a matching expression and a replacing rule,

and step 3: and applying the data hiding rule to sensitive data and hiding and displaying the sensitive data based on the semantic parsing result of the candidate data, wherein the candidate data is at least one part of data used for the first user interface, and the sensitive data is the candidate data matched with the data hiding rule. Hiding the display refers to displaying the result of at least partially replacing the data by applying a data hiding rule. The hidden display corresponds to a plaintext display, i.e., a form in which the data is not subjected to the hiding process. Matching expressions refer to sensitive data matching expressions, i.e., what format of data can be considered sensitive data applicable to the current rule. Both the matching expression and the replacement rule may be represented by a string, for example. The first user is a user logged in to the first application.

In some possible implementations, step 1 is performed during the launch of the first application.

In some possible implementations, the replacement rule is to replace the first portion of the sensitive data with a first character, e.g., "".

In some possible implementations, the candidate data is all data on the first user interface.

In some possible implementations, when the first application receives data, the received data is displayed in a plaintext for a first time period and then hidden for display in response to the received data matching the data hiding rule.

In some possible implementations, in response to the data of the hidden display being selected, the selected data is displayed in plain text.

In some possible implementations, in response to the data being hidden from display being selected, authentication is requested and the selected data is displayed in clear after the authentication is passed.

In some possible implementation manners, under the condition that the first user interface contains the data of the hidden display, whether the hiding is canceled is inquired in response to a first event, and all the data of the hidden display on the first user interface are displayed in clear text under the condition that the consent is obtained. The first event is, for example, a long-press fingerprint event. In some possible implementations, the manner in which concealment is resumed is also queried before the data of all of the concealed displays on the user interface is presented in the clear. Ways to recover the concealment include, for example, how long the concealment is recovered, and whether the recovery is automatic or manual.

In some possible implementations, the candidate data is selected data. By selected is meant that the data is selected by a user registered as a user in the first application or selected in any other way. In some possible implementations, a menu including a data hiding option is provided on condition that the data is detected to be selected, on condition that the data hiding option is selected, it is detected whether the data hiding option is selected for the first time since the first application was enabled on the electronic device, if so, authorization is requested and step 1 is performed based on the selected data after obtaining the authorization, and if not, step 1 is performed directly based on the selected data, wherein the message further includes the selected data, wherein the data hiding rule received in step 2 is a custom data hiding rule. In some possible implementations, a custom data hiding rule is received, the selected data is used as sensitive data, and the custom data hiding rule is applied to the sensitive data, where the custom data hiding rule is a data hiding rule generated by the server by performing semantic parsing on the selected data.

In some possible implementations, the candidate data is data received by the first application from outside the first application, on condition that the received data is detected to be sensitive data, checking whether the first application allows the data hiding processing, if so, directly applying the data hiding rule to the received data and performing hiding display, if not, requesting authorization for the data hiding processing, and applying the data hiding rule to the received data and performing hiding display after being authorized. Receiving from outside the first application means that this data is not collected within the first application, for example obtained by a user performing an input operation on the first application, but is generated externally and transmitted into the first application. According to the implementation mode, each station of the sensitive data on the transmission path can be subjected to hiding processing, so that a hiding chain is established, and privacy is better protected.

In some possible implementation manners, under the condition that it is detected that data to be sent to the outside of the first application program contains sensitive data specified by a custom data hiding rule, whether the custom data hiding rule is applied to a receiving party is inquired, if not, the data to be sent is sent normally, and if so, the data to be sent and the custom data hiding rule are sent together.

In some possible implementations, upon receipt of data and accompanying custom data-hiding rules, a query is made as to whether to apply the custom data-hiding rules to the new data and/or other data already displayed on or to be displayed on the user interface, and in response to a reply to the query, the custom data-hiding rules are applied to the new data and/or other data. Because the customized data hiding rule represents the preference of the sender and is not suitable for being directly applied to the data of the receiver, the customized data hiding rule is applied after the authorization of the receiver is proved. If the receiver replies to the query with a custom data hiding rule applied to other data, the rule is added to the local data hiding rule base. The local data hiding rule base refers to a data hiding rule base of an application program which receives data.

In some possible implementations, on condition that the received data and the accompanying custom data hiding rule are received, on condition that it is detected that the sender and the receiver of the received data belong to the same user, the custom data hiding rule is directly applied to the received data. The custom data hiding rules may also be added to a local data hiding rule base for application to other data displayed on the user interface and to be displayed on the user interface.

In some possible implementations, the data display method is integrated in the first application as a functional module, which requests the datamation hiding rule from the server via a communication module of the electronic device and executes the received data hiding rule.

In some possible implementations, the first application program communicates with a data hiding service provided by the electronic device across processes to request the data hiding service to apply the data display method to the candidate data, and receives, from the data hiding service, result data after applying the data display method, the result data being obtained after the data hiding service performs steps 1 to 3. The data hiding service provided by the electronic device can be implemented as an application program on the electronic device, and also implemented as a service in an application program framework layer (framework layer) in an operating system of the electronic device.

In some possible implementation manners, a data hiding plug-in is integrated in the first application program, the data hiding plug-in has cross-process communication capability, the first application program is in cross-process communication with a data hiding service provided by the electronic device by calling an interface of the data hiding plug-in to request the data hiding service to apply the data display method to candidate data, and result data obtained after the data hiding service performs the steps 1 to 3 is received from the data hiding service. The data hiding service provided by the electronic device can be realized as an application program on the electronic device and also as a service in an application program framework layer in an operating system of the electronic device.

In some possible implementations, the data hiding rule further includes a key to encrypt the sensitive data. This implementation mode makes not only can hide the ization with sensitive data and show, can also encrypt it at the bottom, has further promoted privacy protection intensity.

In some possible implementations, the first application program communicates with a data hiding service provided by the electronic device across processes to request the data hiding service to apply the data display method to candidate data, and receives, from the data hiding service, result data after applying the data display method, the result data being obtained after the data hiding service performs steps 1 to 3, the result data including data after applying the replacement rule processing and data after being encrypted with a key. In some possible implementations, the first application stores the encrypted data and provides the encrypted data to the data hiding service and requests decryption when clear text display is required. In some possible implementations, the first application does not store the encrypted data, stores only the replacement rule processed data, and provides the data hiding service with the replacement rule processed data and requests decryption when a clear text display is required. Here, the data hiding service stores encrypted data, finds corresponding encrypted data according to a mapping relationship between data processed by the replacement rule and the encrypted data, and executes a corresponding data hiding rule for decryption. The data hiding service provided by the electronic device can be realized as an application program on the electronic device and also as a service in an application program framework layer in an operating system of the electronic device.

In a second aspect, an embodiment of the present application provides a data display method, where the data display method is applied to a first application program, the first application program has a first user interface, and the first application program is disposed on an electronic device, and the data display method includes: in response to detecting that the data which is hidden and displayed on the first user interface is selected, a password for displaying the data which is hidden and displayed in a clear text mode is requested; and displaying the data in clear text in response to obtaining the valid password in the second time length.

In some possible implementation manners, the hidden display is restored after the data of the hidden display is displayed in the clear text for the third time.

In a third aspect, an embodiment of the present application provides a data display method, where the data display method is applied to a first application program, the first application program has a first user interface, and the first application program is set on an electronic device, and the data display method includes: under the condition that the first user interface is displayed, whether the first user interface contains the data which is hidden and displayed or not is detected in response to the long-time fingerprint pressing event, whether hiding is cancelled or not is inquired under the condition that the first user interface contains the data which is hidden and displayed, and all the data which is hidden and displayed on the first user interface is displayed in a clear text mode in response to confirmation of cancelling hiding.

In a fourth aspect, an embodiment of the present application provides a data display method, where the data display method is applied to a first application program, the first application program has a first user interface, and the first application program is disposed on an electronic device, and the data display method includes: and detecting that the data displayed in the plaintext is selected, inquiring whether the selected data is agreed to be used for semantic analysis or not, responding to the agreement of the collected user, generating a self-defined data hiding rule based on the selected data, and hiding and displaying the selected data according to the self-defined data hiding rule.

In a fifth aspect, an embodiment of the present application provides a data display method, where the data display method is applied to a first application program, the first application program has a first user interface, and the first application program is disposed on an electronic device, and the data display method includes: and inquiring whether to accept the customized hiding rule accompanying the data or not based on the received data, and hiding and displaying the received data according to the customized hiding rule in response to the fact that the customized hiding rule is accepted.

In some possible implementations, the display method further includes: and inquiring whether the customized hiding rule is used for data except the received data or not in response to the collection of the accepted customized hiding rule, and storing the customized hiding rule in the first application program in response to the collection of the customized hiding rule used for the data except the received data.

A sixth aspect provides a computer storage medium comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the data display method of any one of the possible implementations of the first to fifth aspects. The computer storage medium is, for example, a non-volatile storage medium. Specifically, the data display method in any one of the following implementations may be performed:

in some possible implementations, the data display method is applied to a first application program, the first application program having a first user interface, the first application program being provided on an electronic device, and the data display method includes:

In some possible implementation manners, under the condition that the first user interface contains the data of the hidden display, whether the hiding is canceled or not is inquired in response to a first event, and all the data of the hidden display on the user interface are displayed in a plain text mode under the condition that the consent is obtained. The first event is, for example, a long-press fingerprint event. In some possible implementations, the manner in which concealment is resumed is also queried before the data of all of the concealed displays on the user interface is presented in the clear. Ways to recover the concealment include, for example, how long the concealment is recovered, and whether the recovery is automatic or manual.

In some possible implementations, the candidate data is selected data. By selected is meant that the data is selected by a user registered as a user in the first application or selected in any other way. In some possible implementations, a menu including a data hiding option is provided on condition that the data is detected to be selected, on condition that the data hiding option is selected, it is detected whether the data hiding option is selected for the first time since the first application was enabled on the electronic device, if so, authorization is requested and step 1 is performed based on the selected data after authorization is obtained, if not, step 1 is performed directly based on the selected data, wherein the message further includes the selected data. In some possible implementations, a custom data hiding rule is received, the selected data is used as sensitive data, and the custom data hiding rule is applied to the sensitive data, where the custom data hiding rule is a data hiding rule generated by the server by performing semantic parsing on the selected data.

In some possible implementations, upon receiving data and accompanying custom data-hiding rules, a query is made as to whether to apply the custom data-hiding rules to the new data and/or other data already displayed or to be displayed on the user interface, and in response to a reply to the query, the custom data-hiding rules are applied to the new data and/or other data. Because the customized data hiding rule represents the preference of the sender and is not suitable for being directly applied to the data of the receiver, the customized data hiding rule is applied after the authorization of the receiver is proved. If the receiver replies to the query with a custom data hiding rule applied to other data, the rule is added to the local data hiding rule base. The local data hiding rule base refers to a data hiding rule base of an application program which receives data.

In some possible implementations, the data display method is applied to a first application program, the first application program having a first user interface, the first application program being provided on the electronic device, and the data display method includes: in response to detecting that the data which is hidden and displayed on the first user interface is selected, a password for displaying the data which is hidden and displayed in a clear text mode is requested; and displaying the data in clear text in response to obtaining the valid password in the second time length.

In some possible implementations, the data display method is applied to a first application program, the first application program having a first user interface, the first application program being provided on the electronic device, and the data display method includes: under the condition that the first user interface is displayed, whether the first user interface contains the data which is hidden and displayed or not is detected in response to the long-time fingerprint pressing event, whether hiding is cancelled or not is inquired under the condition that the first user interface contains the data which is hidden and displayed, and all the data which is hidden and displayed on the first user interface is displayed in a clear text mode in response to confirmation of cancelling hiding.

In some possible implementations, the data display method is applied to a first application program, the first application program having a first user interface, the first application program being provided on the electronic device, and the data display method includes: and detecting that the data displayed in the plaintext is selected, inquiring whether the selected data is agreed to be used for semantic analysis or not, responding to the agreement of the collected user, generating a self-defined data hiding rule based on the selected data, and hiding and displaying the selected data according to the self-defined data hiding rule.

In some possible implementations, the data display method is applied to a first application program, the first application program having a first user interface, the first application program being provided on the electronic device, and the data display method includes: and inquiring whether to accept the customized hiding rule accompanying the data or not based on the received data, and hiding and displaying the received data according to the customized hiding rule in response to the fact that the customized hiding rule is accepted.

In a seventh aspect, an embodiment of the present application provides a computer program product, which when run on a computer, causes the computer to execute the data display method in any one of the possible implementation manners of the first to fifth aspects.

In an eighth aspect, an embodiment of the present application provides an electronic device, which includes a memory, a processor, and a first application program stored in the memory and executable on the processor, where the processor executes the first application program to enable the electronic device to implement the data display method in any possible implementation manner of the first to fifth aspects. Specifically, the data display method in any one of the following implementations may be performed:

In a ninth aspect, an embodiment of the present application provides a system for implementing data display, where the system includes an electronic device in any possible implementation manner of the eighth aspect, and a server, where the electronic device requests a server for a data hiding rule through a message, and the server provides the data hiding rule according to an identifier of a first application program and a user token in the message.

In some possible implementation manners, the message further includes candidate data, the server performs semantic analysis on the candidate data in the message to obtain keywords and variables, and a data hiding rule provided by the server specifies a replacement manner for the variables.

In some possible implementations, the server is a cloud server.

These and other aspects of the present application will be more readily apparent from the following description of the embodiment(s).

Drawings

Fig. 1 shows a flowchart of a data display method provided in an embodiment of the present application.

Fig. 2A and 2B illustrate the data display method provided in fig. 1.

Fig. 3A and 3B illustrate the data display method provided in fig. 1.

Fig. 4 shows a flowchart of a data display method provided in an embodiment of the present application.

Fig. 5A to 5D illustrate the data display method of fig. 4.

Fig. 6 illustrates a data display method provided in an embodiment of the present application.

Fig. 7A-7E illustrate a data display method provided by the embodiment of the present application in fig. 6.

Fig. 8A illustrates a data display method provided in an embodiment of the present application.

Fig. 8B illustrates the data display method in fig. 8A.

Fig. 9A-9E illustrate the data display method of fig. 8A.

Fig. 10 illustrates a data display method provided in an embodiment of the present application.

Fig. 11A-11C illustrate the data display method of fig. 10.

Fig. 12 and 13 illustrate a data display method provided by an embodiment of the present application.

Fig. 14A-14E illustrate the data display method of fig. 12 and 13.

Fig. 15 illustrates a data display method provided in an embodiment of the present application.

Fig. 16 shows an exemplary flow chart of the embodiment 1502 in fig. 15.

Fig. 17A-17F illustrate an exemplary implementation of

implementations

1502 and 1503 in fig. 15.

Fig. 18 shows a data display method provided in an embodiment of the present application.

Fig. 19A-19G illustrate the data display method of fig. 18.

Fig. 20 illustrates a data display method provided in an embodiment of the present application.

The electronic device 100 of fig. 21 exemplarily illustrates a structure of the electronic device.

Fig. 22 is a block diagram of the software configuration of the electronic device 100 in fig. 21.

Detailed Description

For ease of understanding, examples are given in part to illustrate concepts related to embodiments of the present application. As follows:

sensitive data (Sensitive data): the specific range of sensitive data depends to some extent on the specific application scenario of the product. Typical sensitive data includes authentication credentials (e.g., passwords, dynamic token cards, short message random passwords), bank account numbers, large volumes of personal data, and user communication content, among others. The term "data" as referred to herein includes any number, variable, character, etc., as long as it can be displayed on the user interface. The sensitive data may accordingly also comprise numbers, variables, characters, etc.

User password: the electronic device provides a plurality of user password modes such as fingerprint, FaceID, password, etc., and the fingerprint is only used for example, but not limited to use, and the password modes which may be provided by the electronic device in the future are all supported.

Hypertext transfer protocol secure (https): is a transport protocol for secure communications over a computer network.

User Interface (UI): the software is related to communication between a user and hardware, and aims to enable the user to conveniently and efficiently operate the hardware to achieve bidirectional interaction and complete work expected to be completed by the hardware. The user interface includes human-computer interaction and a graphical user interface.

Software development kit (software development kit, sdk): is a collection of development tools used by software engineers to build application software for a particular software package, software framework, hardware platform, operating system, etc.

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the description of the embodiments herein, "/" means "or" unless otherwise specified, for example, a/B may mean a or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more than two.

In the following, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first," "second," etc. may explicitly or implicitly include one or more of that feature. In the description of the embodiments of the present application, "a plurality" means two or more unless otherwise specified.

The technical scheme of the embodiment of the application is suitable for any application with a human-computer interaction interface and any electronic equipment with a communication function. The applications may be, for example, social tools (texting, circle of friends, group chat, etc.), media tools (micro blogging, etc.), financial tools (fund transaction app, fund management app, stock transaction app, etc.), privacy management tools (diary, ledger, etc.). The electronic device having a communication function may be a smart phone, a portable phone, a game machine, a television, a display unit, a vehicle (an automobile, a subway, a train, a ship, an aircraft, etc.), a notebook computer, a laptop computer, a tablet Personal Computer (PC), a Personal Media Player (PMP) device, a Personal Digital Assistant (PDA), a home health monitor, and the like. The electronic device may be implemented as a communication electronic device having a wireless communication function, hereinafter simply referred to as an electronic device.

The electronic device-type electronic device may communicate with an external electronic device such as a server or the like, or perform an operation by interworking with the external electronic device. The network may be, but is not limited to, a mobile or cellular communication network, a Local Area Network (LAN), a Wireless Local Area Network (WLAN), a Wide Area Network (WAN), the internet, a Small Area Network (SAN), and the like.

Fig. 1 shows a flowchart of a data display method provided in an embodiment of the present application. App1 is installed on the electronic device. App1 may be an application pre-installed when an electronic device product leaves a factory, an application installed by a user of the electronic device downloaded from an application market (e.g., huashi application market, apple App store, etc.), an application installed by an installation package received by the electronic device through a wireless connection or a mobile hard disk, or the like. In the present embodiment, app1 is implemented as a social chat tool. App1 is implemented to be able to use the data display method provided by the embodiment of the present application. The method is integrated into app1, for example, by a developer of app1 writing the method as code into a program of app1 to provide an app1 version with a data hiding function. Another exemplary method may be to provide the method to a developer of app1 as sdk, and the developer may then cause app1 to call sdk an interface to enable integration of the data display method into app 1. sdk may be provided by any software vendor.

As shown in fig. 1, app1 starts and requests a data hiding rule by an initialization process of app1, and particularly the starting of app1 is triggered by, for example, a user of the electronic device manually clicking on app 1. App1 interacts with the server via the wireless communication module of the electronic device, for example, according to the https protocol, to request the data hiding rule from the server. The wireless communication module is communicatively connected with the server, for example, via wifi, bluetooth, cellular network, etc. The server is, for example, a remote server, which is implemented as a cloud server in this embodiment, and performs information and data interaction with the electronic device through a cellular network. The request may include information of app1, such as whether it is social or financial service, or personal information of the user of the electronic device, so as to obtain a data hiding rule that accurately matches the current application and user requirements. In some implementations, the "settings" menu of app1 can select whether to turn on the data hiding service. If the service is not started when the app1 is started, the app1 does not request the cloud server for the data hiding rule in the starting process, and if the data hiding service is detected to be started in the running process of the app1, the data hiding rule is requested from the cloud server. In some embodiments, when app1 is initialized, an http request message is constructed, and a header url of the http request message is a user rule directory, such as "https:// xxx.com/user/123/rules", carrying parameters such as a user token and an app identifier. App1 sends an http request to a server through a communication module of the electronic device. And the server receives the request, checks the user token, and searches the data hiding rule of the user in the database according to the message request after the user token passes the check. The server returns the found data hiding rule to app 1. The user token refers to data for verifying the identity of the user.

In response to the request by app1 for the data hiding rule, the cloud server returns a corresponding data hiding rule, for example, having the following format:

anonymous_rule_list(ruleID,regularExpression,replace,execute,type)

ruleID；

regularExpression；

replace；

execute；

type。

where ruleID refers to the ID of the rule, such as a serial number, name, etc. regular expression refers to sensitive data matching expressions, i.e., what format of data can be considered as sensitive data applicable to the current rule. Such as the identity card expression: ([1-9] \ d {3}) \ d {13} [ \ d xX x ], states that data is considered to be an identification number if the data satisfies the number beginning of "1-9, followed by 3 digits, followed by 13 digits, the last digit being either a number or an upper and lower case letter x, and x written in various special characters, such as ㄨ, x, X, x, x". Replace refers to a hiding rule of sensitive data, for example, all characters after the first digit of the identity card are replaced by "". Execute refers to an execution mode of hiding processing, for example, automatic hiding processing is performed when sensitive data matching a current rule is detected, whether a user wants to hide processing is queried after sensitive data matching the current rule is detected, hiding processing is manually triggered by the user, and the like. Hereinafter, the data subjected to the display hiding process is referred to as a hidden display, and the original data not subjected to the display hiding process is referred to as a plain display. Type refers to the Type of rule, such as a server preset rule or a user-defined rule. The user-defined rule means that the user is defined and uploaded to the cloud before the request. The benefit of hiding the rules from the cloud storage data and opening calls to all authorized apps is that it is not necessary for each app to generate and manage the rules individually, but it is also simpler for the user, since the same rule package that fits his/her preferences can be used for all apps. In other embodiments, the information hiding rules are generated and stored by app1 itself, so that app1 does not have to request the rules at startup. In other embodiments, the information hiding rules are generated and stored by an information hiding service plug-in the electronic device, and the app1 requests the rules from the information hiding service plug-in of the electronic device at startup.

As shown in fig. 1, app1 receives and stores a hidden processing rule returned by the cloud via a wireless communication module of the electronic device. In App1, the hidden processing rule may be stored before the current startup, and in this case, a step of requesting the cloud for the hidden processing rule at the startup is not essential. App1 may further store multiple sets of hidden processing rules, which may include a rule requested from the cloud at startup, or a rule stored in App1 before this startup.

Returning to the embodiment shown in fig. 1, in the initialization process of app1, the process calls a historical chat record from the database of app1 in response to the user clicking a specific chat window, checks data in the chat record, finds that the card number password matches the sensitive data corresponding to the data hiding rule stored in the process, then replaces the characters after the 4 th digit of the password with a 'x' according to the replacement rule provided by the 'replace' element in the rule, and displays the historical chat record after hiding, as shown in fig. 2B. In other embodiments, the card number may be displayed in plain text (as shown in fig. 2A), and the card number may be hidden and displayed after a specific time interval, for example, 3s to 30s (as shown in fig. 2B). In other embodiments, the replacement rule may be replacing part of the characters of the sensitive data with dots, transparentizing the display and playing a mosaic, etc. Fig. 3A and 3B illustrate a data hiding scenario for an email app in one implementation. Fig. 3A shows the plaintext historical mail loaded after the email app initializes, and fig. 3B shows the display after the email app replaces the sensitive data, i.e., the characters after the 4 th character of the card number, with "", according to the stored data hiding rule.

In some implementations, the replacement of sensitive data is implemented by regular expression replacement. The current high-level languages are all supported by regular expression matching replacement.

In the embodiment shown in fig. 1, app1 has only one database storing plaintext, so the loaded history is plaintext and can be hidden and displayed after the app1 performs hiding processing on the plaintext. In yet other embodiments, app1 also has a database that stores the data after the hiding process. The loaded history may itself carry the hidden data and be displayed directly.

Returning to fig. 1, after app1 is started, a user inputs and receives data in a chat action, the data is presented on a chat interface in a character form, the chat UI requests the process to check whether the data contains sensitive data when detecting new data input, the process determines the sensitive data according to a data hiding rule stored in app1, hides the sensitive data, and notifies the UI to display a plaintext first, and displays the data after hiding after a certain duration. In this embodiment, the data after the hiding process is displayed after the plaintext 30s is displayed, so that the user has an opportunity to know the full view of the data. Not shown in the figure, if the process determines that the newly input data does not contain sensitive data according to the data hiding rule stored in app1, the process notifies the UI of displaying a plaintext. Not shown in the figure, when app1 receives data sent from the outside, for example, a message sent from a chat object of a local user, and a new data input is detected by the chat UI, the process is requested to check whether the data includes sensitive data, the process determines the sensitive data according to the data hiding rule stored in app1, hides the sensitive data, and notifies the UI of displaying in plaintext first, and hides the sensitive data after a certain time. In some embodiments, the data block that is hidden is tagged in the background so that the entire data block is considered to be selected when any of the subsequent display areas of the data block are selected.

Fig. 4 shows a flowchart of a data display method provided in an embodiment of the present application. In step 401, App1 detects that the hidden display data presented on the chat window UI thereof is selected, for example, the hidden data area is touched, clicked, flicked, etc. by the user, and the action is regarded as the selected action according to the data display method applied by App1, then App1 requests a password for allowing the data to be displayed in plaintext in step 402. Such as a fingerprint, Face ID, password, answer questions, etc. If a valid password is obtained within a prescribed time, app1 displays the hidden data in plain text. If a valid password is not obtained within a predetermined time, app1 prompts that the password is invalid and keeps the hidden display.

The data display method of fig. 4 is illustrated in fig. 5A to 5D. In fig. 5A, the chat window UI display of app1 contains data of a hidden display, where the data is a card number. And the chat window UI detects a user click event, the text control of the app1 responds to the click event, logic processing is carried out, and the data block to which the click part belongs is identified to be the data block which is subjected to hiding processing. For example, when the data block is marked during the hiding process and any one of the display areas corresponding to the data block is clicked, the entire data block is considered to be selected. The tag may be background data and the foreground invisible, i.e. invisible to the user of the electronic device. In this embodiment, app1 is configured to require authentication to allow viewing of the plaintext of the data, and then app1 invokes a fingerprint authentication interface in the operating system of the electronic device, popping up a pressed fingerprint window, as shown in fig. 5B, intended to request a fingerprint input as a password. If the fingerprint of the authorized user is acquired within the specified time, as shown in fig. 5C, the hidden data block is displayed in plain text, as shown in fig. 5D. The prescribed time is, for example, 10 s. Not shown in the figure is that if the fingerprint of the authorized user is collected in the specified time, the hidden data block is displayed in plain text. In some embodiments, if app1 is configured to change the data in the hidden display to the plaintext display without authentication, the steps shown in fig. 5B and 5C may be omitted, that is, the data block after the hidden process is detected to be selected and the plaintext display is performed. In some embodiments, it may be set in the "set" option of app1 whether or not the function of changing the data of the hidden display to a clear display needs to be authenticated, and how to authenticate.

Fig. 6 illustrates a data display method provided in an embodiment of the present application. The method shown in fig. 4 is suitable for changing the data of the hidden display into the plaintext display one by one. Fig. 6 provides a shortcut if the current chat window UI contains multiple pieces of hidden processed data and the user wants them all in the clear. App1 subscribes to a long-press fingerprint event from the operating system of the electronic device at the time of startup. When the chat interface UI of App1 is displayed, if App1 detects that a long-press fingerprint event occurs in step 601, in response to the event, App1 detects whether the currently displayed chat interface UI includes data hidden therein.

If it is detected that the data of the hidden display is included in the current chat interface UI, a query is provided as to whether the hidden display is to be cancelled in step 608. In response to the reply not canceling the hidden display in step 609, the query ends in step 609 and the hidden display on the chat interface UI is maintained. In step 610, in response to the response of canceling the hidden display, the data of all hidden displays included in the current chat interface UI is displayed in plain text. In some embodiments, the query of whether to cancel the hidden display in step 608 may further include a query of how to restore the hidden display, such as how long to restore automatically, whether to restore manually, and the like.

In response to the long-press fingerprint event, if it is detected that the data displayed in the current chat interface UI does not contain the hidden data, it is checked in step 603 whether the data displayed in the chat interface UI contains sensitive data, and if not, it is selected in step 604 not to respond to the long-press fingerprint event. If the data displayed on the chat interface UI includes sensitive data, it is considered that the data that should be hidden and displayed is converted into a clear text display by the previous action, and then it is queried in step 605 whether to restore the hidden and displayed data. If the collected answer is negative, the query is ended in step 606, and the clear text display on the chat interface UI is maintained. If the collected answer is positive, all sensitive data on the chat interface UI is hidden and displayed in step 607.

Fig. 7A-7E illustrate a data display method provided by the embodiment of the present application in fig. 6. In fig. 7A, app1 detects a long-press fingerprint event, e.g., a long press for more than 3 s. App1 detects whether or not a hidden display is included on the current chat window UI. If the detection result proves that the UI includes the hidden display, the app1 pops up an inquiry box, as shown in fig. 7B, to inquire whether to cancel the hidden display and how to recover, wherein the recovery modes include automatic recovery after 1min, automatic recovery after 5min, and manual recovery. If a request for any recovery mode is collected, the request is considered to be a request for willing to cancel the hidden display. In response to collecting the request for manual recovery, app1 changes the hidden display of all data on the current chat window UI to a clear display, as shown in FIG. 7C. When app1 detects a long-press fingerprint event, for example, a long-press for 3s or more, app1 detects data on the current chat window UI, and if it is found that sensitive data conforming to the concealment rule is contained but not concealed from display, provides a query as to whether to restore the concealed display, for example, in the form of a pop-up box as shown in fig. 7D. In response to collecting the request for restoring the hidden display, app1 hides all sensitive data on the current chat window UI, as shown in fig. 7E.

Fig. 8A illustrates a data display method provided in an embodiment of the present application. In step 801, app1 detects that data displayed in plain text on the currently displayed UI is selected, for example, in a manner of a data block, for example, a text is long-pressed, and then app1 provides an option including hiding. If app1 detects that the hiding option is selected, interpreted that the user is to add a custom data hiding rule based on the data block, app1 detects whether the user is using the function for the first time. If it is the first time this function is used, app1 provides an authorization query in step 802, i.e. whether the user agrees to provide the selected data for semantic parsing. If the user disagreement is received and the authorization is unsuccessful, the inquiry is finished, and the app1 keeps the plaintext display of the selected data. If the user agrees to authorize successfully in step 803, the selected data is sent to the cloud server in step 804 for semantic parsing to generate the customized data hiding rule. The word trained AI can distinguish sensitive words, such as variables, derogatory words, etc., within the data. For example, the cloud server generates user-level data hiding rules by AI analyzing semantics. App1 receives the new data hiding rule from the cloud server at step 805. App1 adds the rule to the local rule base of App1 in step 806, and hides and displays all data on the UI that conforms to the sensitive data defined by the rule according to the rule. The custom data hiding rule may have the same format as the preset rule provided by the cloud server, as introduced in describing fig. 1. In some embodiments, the app1 may perform semantic parsing on data selected by a user to generate a customized data hiding rule, or send the data to a data hiding plug-in the electronic device system to perform semantic parsing to generate a customized data hiding rule. For example, at present, the semantic parsing capabilities of cell phone assistants and smart AIs of various large manufacturers are relatively mature, such as microsoft mini ice and apple siri, have conversation capabilities, and can analyze which parts in a sentence to be anonymized have changing capabilities, which parts are different from person to person, which parts are common terms, and which parts are to be concealed are common parts different from person to person. In some implementations, the custom data hiding rule may also be manually edited by the user, for example, in the data hiding setting of app1, the rule manually edited by the user is received. Specifically, app1 provides an edit template, including three parts "start", "end", and "contain", and receives the content that the user has filled in on these parts to generate rules.

Fig. 8B exemplarily illustrates the data display method in fig. 8A. App1 detects that a piece of data on the UI is selected, and then provides a "data hiding" option. App1 detects that the "data hiding" option is selected. App1 detects whether the user applies the data hiding function to the freely selected data for the first time. If the data hiding rule is the first time, the app1 requests the authorization of the user, and after the authorization is obtained, the selected data is loaded into a message and sent to a cloud server to request the user-level user-defined data hiding rule. If not, the app1 directly loads the selected data into a message and sends the message to the cloud server to request the user-level customized data hiding rule. The message sent by App1 to the cloud server may have the following structure:

message type: requesting generation of custom data-hiding rules

Message content: identity card 876543 "

A user token: 12345

App identification: 0002.

where the "message content" item is a block of data selected by the user and the user token is an identification of the user and its rights. And the cloud server performs semantic analysis on the message content after receiving the message. For example, "ID 876543," the initial result of semantic parsing is that "ID" is a noun, which is used as a keyword, "876543" is a variable, which is used as a sample of the keyword "ID". The preliminary results are then subjected to matching analysis, and the final result is that "identity card" matches the privacy key and "876543" matches the generation rule of the identity card. And then the cloud server generates the user-defined data hiding rule contained in the message according to the final result. The custom data hiding rule has, for example, the following structure:

numbering: shaping numbers;

matching an expression: a character string;

alternative expressions: a character string;

the execution mode is as follows: enumerating;

type (2): and (6) enumeration.

Where a number refers to the number assigned to the rule, for example an integer number. The matching expression is a string of characters representing the data format for which the rule applies, for example, beginning with three characters "ID cards", followed by 17 digits, followed by a 1 digit number or letter "x". The substitution expression is an expression representing a substitution rule for the original data, for example, a 4 th character is substituted with "×". The execution mode is described by enumeration, the enumerated objects comprise automatic detection data and automatic application of the rule, the rule is applied after the automatic detection data and the authorization are obtained, and the data is detected and the rule is applied after the user manually selects the data and requests the hiding. Type refers to the rule type, illustrated by enumeration, where enumerated objects include presets and customizations. For current rules, the type should be custom.

The cloud server adds the newly generated rule to the user's data hiding rule set and returns the new rule to app 1. App1 adds the new rule to a local rule base, and executes the rule to perform data hiding processing and hidden display on the data selected by the user.

Fig. 9A to 9E exemplarily illustrate the data display method in fig. 8A. App1 is implemented as a diary in this embodiment. As shown in fig. 9A, app1 currently displays a diary browsing interface UI. The user interface may also be a diary edit UI, and the present embodiment is not limited herein. As shown in fig. 9B, app1 detects that a block of plaintext data "height 160cm, weight 60 kg" is selected. As shown in fig. 9C, app1 provides a pop-up box including a "hide" option, and app1 detects that the "hide" option is selected by clicking. App1 interprets the selection of the "hiding" option as a request for hiding and displaying the selected data block, and needs to generate a data hiding rule based on the data block to realize the hiding and displaying. The data hiding rule generated based on the data block selected by the user may be referred to as a user-defined data hiding rule. App1 detects whether the current user adds the user-defined data hiding rule for the first time, if so, App1 provides a popup box and requests the user to perform semantic parsing authorization on the selected data block, as shown in fig. 9D. After detecting that the user authorizes by clicking 'consent', App1 sends the selected data block to a cloud server for analysis and rule generation. App1 receives a rule returned from the cloud server, which identifies the numbers in "height 160cm, weight 60 kg" as variables and replaces them with "+". App1 refreshes the display of the diary browsing interface UI according to the rule, in which the data block is hidden and displayed, as shown in fig. 9E. App1 also adds the rule to a locally stored rule base, and then detects a data block in the format of "height + number, weight + number" on the UI interface of App1, and also recognizes it as sensitive data, and replaces and conceals the number portion with "+". After identifying the sensitive data, app1 allows the sensitive data to be displayed in the clear for a certain time, for example, 30s, and then concealably displays the sensitive data, so that the user can check the content sent by the user or understand the received content.

Fig. 10 illustrates a data display method provided in an embodiment of the present application. In this embodiment, app1 is implemented such that the data hiding service can be turned on or off in its "set" option. In step 1001, app1 receives new data, e.g., a new message. In step 1002, app1 detects that the data is compared with the data hiding rule stored in app1, and if the data is determined not to be sensitive data specified by the rule, the process returns to step 1001 to wait for the next time new data is received. If it is determined in step 1002 that the data is sensitive data specified by the rule, it is checked in step 1003 whether the data hiding option of app1 is on, and if so, the data is hidden and displayed in step 1004. If it is checked in step 1003 that the data hiding option is off, it is queried in step 1005 whether to hide the data, which is done by querying the user, for example, by a pop-up box. If no is acquired, that is, the concealment process is not performed, the process returns to step 1001 to wait for the next new data reception. If yes is collected, i.e. the concealment process is agreed to, app1 checks in step 1006 whether the data concealment option has never been turned on since this app1 was enabled on the current electronic device. If it has been turned on, the data is processed for hiding in step 1007 and is displayed for hiding. If it has never been turned on, authorization for the data hiding option is requested in step 1008. If no authorization is collected, e.g. the user clicks on a not willing authorization, the process returns to step 1001 to wait for the next time to receive new data. If authorization is acquired, the data is hidden from processing and hidden from display in step 1009.

Fig. 11A-11C illustrate the data display method of fig. 10. In this embodiment, app1 is implemented such that the data hiding service can be turned on or off in its "set" option. As shown in fig. 11A, app1 receives a data block in the format of data + card number. The data block should be determined as sensitive data according to the data hiding rule stored in app1, so that the sensitive data is directly hidden and displayed under the condition that the data hiding service is turned on. However, the current app1 is set to turn off the data hiding service. When receiving the data block, app1 compares the data block with the data hiding rule stored in app1, and if the data block is sensitive data as a result of the comparison, app1 pops up a box to inquire whether to hide the data block, as shown in fig. 11A. In other embodiments, the sent data block is provided with a tag which is printed by the sender and is identified as sensitive data, when app1 recognizes the tag, the data block is compared with the data hiding rule stored by the app1, and if the comparison result shows that the data block is also sensitive data according to the data hiding rule stored by app1, the app1 pops up to inquire whether to hide the data block. The establishment of a hidden chain can be provided by checking whether the received data is sensitive data, namely the sensitive data is hidden on a plurality of nodes of a transmission path of the sensitive data, so that the protection of the sensitive data is enhanced. Returning to fig. 11A, if the answer collected by app1 to whether to perform the hiding processing is affirmative, app1 detects whether its data hiding service has never been turned on, and if not, app1 pops up to request authorization for the data hiding service, as shown in fig. 11B. After the authorization is acquired, App1 performs hiding processing and hiding display on the sensitive data according to the corresponding rule, as shown in fig. 11C.

Fig. 12 and 13 illustrate a data display method provided by an embodiment of the present application, which provides a way to establish a hidden chain on a transmission path of data.

As shown in fig. 12, in step 1201, app1 detects that the data transmission key is triggered, and checks whether sensitive data specified by the user-defined data hiding rule is included in the data to be transmitted before transmitting the data. If it is determined in step 1202 that sensitive data specified by the user-defined data hiding rule is not included, then the data is sent out normally in step 1203. If it is determined that sensitive data specified by the user-defined data hiding rule is included, then a query is made in step 1204 as to whether the user-defined data hiding rule is intended for the data recipient. If a reply to the query is collected that the rule is not willing to be applied to the recipient, then the data is sent out normally in step 1205. If a response to the query is collected that the rule is willing to be used for the recipient, the rule is issued with the data in step 1206.

As shown in fig. 13, in step 1301, app2 receives new data and detects that there is a sender-defined data hiding rule sent along with the data. App2 asks whether to accept the rule in step 1302. If the answer to the query is collected that the rule is not accepted, then the data is processed normally in step 1303. If the answer to the query is collected as accepting the rule, then in step 1304 it is queried whether the rule is to be used for data other than the current data, and if the answer to the query is collected as unwilling to use the rule for data other than the current data, then in step 1306 the data is displayed hidden according to the rule after it is displayed in clear for a specified period of time, e.g., 30 seconds. If the answer is collected as willing to use the rule for other data, then in step 1305 the rule is added to the local data hiding rule base in app2 and in step 1306 the data is hidden for display according to the rule after it is displayed in clear for a certain length of time, e.g. 30 s.

The sender app1 and the receiver app2 may be the same app or may be different apps. Whether app1 and app2 are the same or different, the implementation of the method of this embodiment is not affected, and thus the application is not limited thereto.

In some embodiments, the receiving party forwards the data, and the data display method shown in fig. 12 and 13 is also applied. A recipient refers to app2 that receives the data.

In some embodiments, the sender sends the data in a group, which is equivalent to sending a block of data to each of a plurality of group users, and for each pair of sender and receiver, the data display method shown in fig. 12 and 13 is applied. The sender refers to app1 that emits data, and the receiver refers to app2 that receives data.

In some implementation forms, if the sender detects that the sender and the receiver belong to the same user, when the sender detects that sensitive data containing the customized data hiding rule in data to be sent, the sender does not ask whether the rule is to be applied to the receiver any more, but adds the customized data hiding rule to the data and then sends the data directly. And stores the rule to a local rule base and applies it to subsequent data on the recipient. The sender refers to app1 that emits data, and the receiver refers to app2 that receives data.

Fig. 14A-14E illustrate the data display method of fig. 12 and 13. As shown in fig. 14A, app1 is implemented as a social tool, currently displaying a chat window. When app1 detects that the "send" key is triggered, app1 checks the data in the send message edit box. If it is detected that the sent message contains sensitive data matching the user-defined data hiding rules stored locally in the app1, the app1 suspends the issuance of the message and pops up a box asking if it is desired that the recipient also hides the message, as shown in fig. 14B. If app1 collects that the user clicks "no", that is, the recipient is not expected to hide the message, the message is sent out normally. If the app1 collects that the user clicks yes, that is, the receiver wants to hide the message, the corresponding custom data hiding rule is added to the structure of the message, as shown in fig. 14C, and then the message is sent out.

As shown in fig. 14D, if the app2 of the receiving party receives a message containing the sender-defined data hiding rule, the app1 pops up a box to inquire whether to receive the defined data hiding rule. If app2 collects "no", i.e. does not accept the custom data hiding rule, app2 processes the message normally. If app2 collects "yes," i.e., accepts the custom data hiding rule, then app2 pops up to ask if the rule is intended for the message only, for all messages sent by the sender, or for all messages on app2, as shown in fig. 14E. Regardless of which collected application rule is selected, after displaying the message in plain text for a certain time, for example, 30s, app2 conceals and displays the message according to the custom data hiding rule. If the selection is collected for all messages sent by the sender or for all messages on app2, app2 also adds the custom data hiding rules to the local rule base for future use.

Fig. 15 illustrates a data display method provided in an embodiment of the present application. app1 is set on the electronic device.

In embodiment 1501, the data display method is integrated as a functional module in the code of app 1. Specifically, the data display method may be integrated into app1 as a data hiding plug-in service. The data hiding plug-in service may be implemented in a piece of code or a package of code. The data hiding plug-in service requests a data hiding rule from the cloud server, the electronic device provides communication capability, and the data hiding plug-in service executes the data hiding rule acquired from the cloud by itself, for example, detects the sensitive data according to the rule, replaces a part of the sensitive data with a specified character, and displays the replaced sensitive data. The implementation 1501 mode relies on the effort of app1 developers to write and integrate code, and different apps require developers to write code and integrate separately.

In embodiment 1502, app1 communicates with the electronic device across processes to obtain a data hiding service provided by the electronic device. app1 requests a data hiding rule from the data hiding service, the rule being locally stored by the data hiding service or downloaded from a cloud server, or the data hiding service requests semantic parsing from the cloud server and receives a user-level custom data hiding rule. The data hiding service executes a data hiding rule acquired from the cloud, for example, detects sensitive data according to the rule and replaces a part of the sensitive data with a prescribed character, and provides the replaced sensitive data to the app1 for display. In embodiment 1502, since the data hiding rules are obtained and executed by the data hiding service from the cloud, it is not necessary to write code for the data hiding function in each app as long as the app has a cross-process communication capability for requesting the data hiding service, for example, cross-process communication by aid dl technology provided by the Android system.

In the implementation form 1503, a data hiding plug-in is integrated into app1, and app1 acquires a data hiding service provided by the electronic device via the plug-in. The plug-in the app1 has the cross-process communication capability, so that the app1 can communicate with the data hiding service provided by the electronic device only by calling the plug-in interface. The data hiding plug-in provides a control for hiding data, and the control comprises a window for hiding display, a query box, a menu related to data hiding and the like. The data hiding plug-in requests a data hiding rule from the data hiding service, wherein the rule is locally stored by the data hiding service or downloaded from the cloud server, or the data hiding service requests semantic parsing from the cloud server and receives a user-level self-defined data hiding rule. The data hiding service executes a data hiding rule acquired from the cloud, for example, detects sensitive data according to the rule and replaces a part of the sensitive data with a prescribed character, and provides the replaced sensitive data to the data hiding plug-in for display. In the implementation form 1503, it is not only unnecessary to write code of a data hiding function in each app, but also unnecessary for the app to have a cross-process communication capability, further reducing the burden on the app developer.

In

implementations

1502 and 1503, the data hiding service provided by the electronic device may be implemented as an app on the electronic device, as well as a service in an application framework layer (framework layer) in the operating system of the electronic device.

Fig. 16 shows an exemplary flow chart of the embodiment 1502 in fig. 15. The "use data hiding" in the "setting" option of App1 is turned on, and then App1 makes an application for the data hiding service provided by the electronic device. app1 receives a privacy statement and an authorization request from the data hiding service. App1 relays the authorization request to the user and obtains authorization. App1 passes the authorization statement to the data hiding service. App1 receives a reply of success of the service application from the data hiding service, the reply being obtained based on: the data hiding service requests a cloud server to create a data hiding account for the user, and receives a data hiding rule preset on the cloud server from the cloud server and stores the data hiding rule locally. App1 makes a data hiding request to the data hiding service when new data is detected, and receives a result of the hiding process, which is obtained by the data hiding service applying a data hiding rule to data. App1 presents the result after the data hiding process on the UI. In some implementation forms, when the data hiding account is created, the app initiating the account creating request selects what account to use for authorization, and the account creating process may be simplified by using the account of the app itself or by using three-party account authorization, such as huashi account and other authorization, and the account is mainly used for creating user-level anonymous rules. The three-party authorization follows the oauth2.0 standard and is not described in detail herein.

Fig. 17A-17F illustrate exemplary implementations of the data hiding service of the electronic device in

implementations

1502 and 1503 in fig. 15. As shown in fig. 17A, the data hiding service includes a data hiding app management module, a data hiding rule module, and a data hiding service setting module. In response to detecting that the data-hiding app management module is selected, the data hiding service displays a UI, shown in fig. 17B, listing all apps on the electronic device that may be hidden using the data. The services provided by the data hiding service can be made available to the app by checking the app on the UI. It is of course also possible to stop servicing a particular app by deselecting it. In FIG. 17C, it is detected that the data-hiding rule management module is selected, and the data-hiding service jumps to the UI shown in FIG. 17D, on which all locally stored data-hiding rules are listed. Rules can be selected, deselected and deleted on the UI. Selecting means applying the rule to the service-capable apps, deselecting means stopping applying the rule to the service-capable apps, and deleting means no longer storing the rule. In FIG. 17E, it is detected that the data-hiding service management module is selected, and the data-hiding service jumps to the UI shown in FIG. 17F, on which the option to enable and disable the data-hiding service is provided.

Fig. 18 shows a data display method provided in an embodiment of the present application. App1 detects that a user requests to encrypt data, and App1 requests a data hiding service provided by the electronic device to encrypt the data. The data hiding service provided by the electronic device may be implemented as an app on the electronic device, and also implemented as a service in an application framework layer (framework layer) in an operating system of the electronic device, which is not limited in this embodiment. If the cloud server detects that the user requests the encryption service for the first time according to the request sent by app1, an authorization request is sent to app 1. App1 receives an authorization request of the data hiding service for the encryption service and requests authorization from a user. App1 collects the user's authorization and passes the authorization to the data hiding service. If the cloud server detects that the user's authorization has been obtained once and the authorization is still valid, the step of requesting authorization may be omitted. Next, the data hiding service requests the cloud server to encrypt the data. The cloud server obtains the user-level encryption rule by performing semantic analysis on the data. Encryption rules include replacing certain portions of data with certain characters for hidden display, and providing keys for converting data into ciphertext. For example, the hidden display portion in the encryption rule may transform the original data "bank card number 12345" into "bank card number x" through partial replacement, and the key in the encryption rule may transform the original data "bank card number 12345" into a ciphertext such as "123UGHF82341HJ" through a reversible symmetric or asymmetric encryption algorithm. For convenience of description, data for hiding display is referred to as hidden data, and data encrypted with a key is referred to as encrypted data. The data hiding service receives the encryption rules from the cloud server and stores the encryption rules to a local rule base. App1 receives confirmation of success of the encryption service application from the data hiding service. App1 applies for data encryption to the data hiding service, and receives hidden data and encrypted data generated by the data hiding service according to an encryption rule. App1 stores the ciphertext data and displays the data in a hidden manner. App1 may store the hidden data or not store the hidden data, which is not limited in this embodiment. App1 requests the data hiding service to decrypt the encrypted data in response to detecting the user request. The data hiding service decrypts the data based on the encryption rule and returns the decrypted data to app 1. And App1 receives the decrypted data and displays the data in a plain text, and restores the data to a hidden display after a specific time, for example, 30 s. App1 does not store raw data or plaintext data in the present embodiment.

Fig. 19A-19G illustrate the data display method of fig. 18. As shown in fig. 19A, app1 is implemented as a diary. App1 detects that a piece of data is selected, and then provides a menu option including "encrypt". In response to the capture "encrypt" option being clicked on, app1 checks whether the encryption function was first enabled since app1 was installed for use. If not, app1 requests the data hiding service on the electronic device to encrypt the selected data according to the method in fig. 18 and hides the display data as shown in fig. 19C. If it is first enabled, app1 pops up a box requesting user authorization for cryptographic services. The scope of user authorization is to allow data requesting cryptographic services to be sent outside app1 for analysis for cryptographic service purposes.

As shown in fig. 19D, app1 detects that the ciphertext data of the hidden display is clicked, and interprets that the user wants to decrypt the data. The app1 popup then requests a fingerprint to be pressed for authentication, as shown in fig. 19E. App1 collects a long fingerprint event, as shown in fig. 19F, and then App1 verifies whether the fingerprint is valid. If the verification is passed, app1 requests decryption to the data hiding service, and displays the received decrypted data in plain text, as shown in fig. 19G. App1 does not store plaintext data or decrypted data, but stores only ciphertext data. After the decrypted data is displayed in the plain text for a certain time, for example, 30s, App1 restores the decrypted data to the hidden display according to the stored ciphertext data. The ciphertext data may be stored by a data hiding service. The data hiding service may be provided by a manufacturer of the electronic device or may be provided by a third party. In other embodiments, the data hiding service is integrated into the app1 in the manner of sdk, and the electronic device only needs to provide a communication function, so that the app1 communicates with the cloud server and obtains the encryption rule, and the app1 performs encryption and decryption through its own data hiding service execution rule.

Fig. 20 illustrates a data display method provided in an embodiment of the present application. The data display method shown in fig. 20 is similar to the data display method shown in fig. 18, in which the data hiding services provided by the electronic devices all provide encryption services for app 1. For clarity, the differences between the method of FIG. 20 and the method of FIG. 18 are primarily discussed herein. In the method of fig. 18, the data hiding service does not store data, processes the data using the encryption rule, and sends the hidden data and the encrypted data to app 1. App1 stores encrypted data, and may or may not store hidden data. And when the plaintext display is required, the encrypted data is sent to the hiding service for decryption. In the method of fig. 20, the data hiding service stores the encrypted data, and sends the encrypted data and the hidden data to app 1. App1 stores not encrypted data but only hidden data. When the app1 needs to display in a clear text, the hidden data is sent to the data hiding service, the data hiding service finds corresponding encrypted data according to the mapping relation between the hidden data and the stored encrypted data, and the data is sent to the app1 after being decrypted.

The data display methods shown in fig. 1-20 may be arbitrarily combined to become a more elaborate data display method. Any combination of the data display methods shown in fig. 1-20 is also a data display method provided by the embodiments of the present application

As described above, the data display method provided by the embodiment of the present application can be used in an electronic device. Fig. 21 is an exemplary structure of the electronic device 2100. (the reference numerals in FIGS. 21 and 22 are shown in the drawings and changed uniformly after finishing once)

The electronic device 2100 may include a processor 2110, an external memory interface 2120, an internal memory 2121, a USB interface 2130, a charging management module 2140, a power management module 2141, a battery 2142, an antenna 1, an antenna 2, a mobile communication module 2150, a wireless communication module 2160, an audio module 2170, a speaker 2170A, a receiver 2170B, a microphone 2170C, an earphone interface 2170D, a sensor module 2180, keys 2190, a motor 2191, an indicator 2192, a camera 2193, a display 2194, a SIM card interface 195, and the like. The sensor module 2180 may include a pressure sensor 2180A, a gyroscope sensor 2180B, an air pressure sensor 2180C, a magnetic sensor 2180D, an acceleration sensor 2180E, a distance sensor 2180F, a proximity light sensor 2180G, a fingerprint sensor 2180H, a temperature sensor 2180J, a touch sensor 2180K, an ambient light sensor 2180L, a bone conduction sensor 2180M, and the like.

It is to be understood that the illustrated configuration of the embodiment of the present invention does not specifically limit the electronic device 2100. In other embodiments of the present application, the electronic device 2100 may include more or fewer components than illustrated, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 2110 may include one or more processing units, such as: the processor 2110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a Neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

The controller can be, among other things, a neural hub and a command center of the electronic device 2100. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 2110 for storing instructions and data. In some embodiments, the memory in processor 2110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 2110. If the processor 2110 needs to use the instruction or data again, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 2110 thereby increasing the efficiency of the system.

In some embodiments, processor 2110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 2110 may include multiple sets of I2C buses. The processor 2110 may be coupled to the touch sensor 2180K, the charger, the flash, the camera 2193, etc. through different I2C bus interfaces. For example: the processor 2110 may be coupled with the touch sensor 2180K through an I2C interface, so that the processor 2110 and the touch sensor 2180K communicate through an I2C bus interface to realize a touch function of the electronic device 2100.

The I2S interface may be used for audio communication. In some embodiments, processor 2110 may include multiple sets of I2S buses. The processor 2110 may be coupled with the audio module 2170 through an I2S bus to enable communication between the processor 2110 and the audio module 2170. In some embodiments, the audio module 2170 may communicate audio signals to the wireless communication module 2160 through the I2S interface, enabling answering calls through a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 2170 and the wireless communication module 2160 may be coupled by a PCM bus interface. In some embodiments, the audio module 2170 may also deliver audio signals to the wireless communication module 2160 through the PCM interface, enabling answering calls through a bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is typically used to connect the processor 2110 with the wireless communication module 2160. For example: the processor 2110 communicates with a bluetooth module in the wireless communication module 2160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 2170 may transmit the audio signal to the wireless communication module 2160 through the UART interface, so as to realize the function of playing music through the bluetooth headset.

MIPI interfaces may be used to connect the processor 2110 with peripheral devices such as a display screen 2194, a camera 2193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, the processor 2110 and the camera 2193 communicate via a CSI interface to enable the capture functionality of the electronic device 2100. The processor 2110 and the display screen 2194 communicate through the DSI interface to implement the display function of the electronic device 2100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 2110 with the camera 2193, the display 2194, the wireless communication module 2160, the audio module 2170, the sensor module 2180, and/or the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

The USB interface 2130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface may be used to connect a charger to charge the electronic device 2100, and may also be used to transfer data between the electronic device 2100 and a peripheral device. And the earphone can also be used for connecting an earphone and playing audio through the earphone. The interface may also be used to connect other electronic devices, such as AR devices and the like.

It is to be understood that the connection relationship between the modules according to the embodiment of the present invention is only illustrative, and is not limited to the structure of the electronic device 2100. In other embodiments of the present application, the electronic device 2100 may also adopt different interface connection manners or a combination of interface connection manners in the above embodiments.

The charging management module 2140 is configured to receive a charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 2140 may receive charging input from a wired charger via a USB interface. In some wireless charging embodiments, the charging management module 2140 may receive a wireless charging input through a wireless charging coil of the electronic device 2100. The charging management module 2140 may also supply power to the electronic device via the power management module 2141 while charging the battery 2142.

The power management module 2141 is configured to connect the battery 2142, the charging management module 2140 and the processor 2110. The power management module 2141 receives input from the battery 2142 and/or the charge management module 2140, and provides power to the processor 2110, the internal memory 2121, the external memory, the display 2194, the camera 2193, the wireless communication module 2160, and the like. The power management module 2141 may also be used to monitor parameters such as battery capacity, battery cycle number, battery state of health (leakage, impedance), etc. In other embodiments, the power management module 2141 may also be disposed in the processor 2110. In other embodiments, the power management module 2141 and the charging management module 2140 may be disposed in the same device.

The wireless communication function of the electronic device 2100 may be implemented by the antenna module 1, the antenna module 2, the mobile communication module 2150, the wireless communication module 2160, a modem processor, a baseband processor, and the like.

The

antennas

1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 2100 can be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the cellular network antenna may be multiplexed into a wireless local area network diversity antenna. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 2150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc. applied to the electronic device 2100. The mobile communication module 2150 may include at least one filter, a switch, a power Amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 2150 may receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit the electromagnetic waves to the modem processor for demodulation. The mobile communication module 2150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 2150 may be provided in the processor 2110. In some embodiments, at least some of the functional modules of the mobile communication module 2150 may be provided in the same device as at least some of the modules of the processor 2110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 2170A, the receiver 2170B, etc.) or displays an image or video through the display screen 2194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be separate from the processor 2110, and may be located in the same device as the mobile communication module 2150 or other functional modules.

The wireless communication module 2160 may provide solutions for wireless communication applied to the electronic device 2100, including Wireless Local Area Networks (WLAN), Bluetooth (BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 2160 may be one or more devices integrating at least one communication processing module. The wireless communication module 2160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signal, and transmits the processed signal to the processor 2110. Wireless communication module 2160 may also receive signals to be transmitted from processor 2110, frequency modulate, amplify, and convert to electromagnetic radiation via antenna 2.

In some embodiments, the antenna 1 and the mobile communication module 2150 of the electronic device 2100 are coupled and the antenna 2 and the wireless communication module 2160 are coupled such that the electronic device 2100 can communicate with networks and other devices via wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The electronic device 2100 implements a display function by a GPU, a display screen 2194, and an application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 2194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 2110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 2194 is used to display images, videos, and the like. The display screen 2194 includes a display panel. The display panel may be an LCD (liquid crystal display), an OLED (organic light-emitting diode), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), or the like. In some embodiments, the electronic device 2100 may include 1 or N display screens, N being a positive integer greater than 1.

The electronic device 2100 may implement a shooting function through an ISP, a camera 2193, a video codec, a GPU, a display screen 2194, an application processor, and the like.

The ISP is used to process data fed back by the camera 2193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 2193.

The camera 2193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the electronic device 2100 may include 1 or N cameras, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the electronic device 2100 selects at a frequency bin, the digital signal processor is used to perform a fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. The electronic device 2100 may support one or more video codecs. As such, the electronic device 2100 may play or record video in a variety of encoding formats, such as: MPEG1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent recognition of the electronic device 2100 can be implemented by the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 2120 may be used for connecting an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device 2100. The external memory card communicates with the processor 2110 through an external memory interface 2120, implementing a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

Internal memory 2121 may be used to store computer-executable program code, which includes instructions. The processor 2110 performs various functional applications and data processing of the electronic device 2100 by executing instructions stored in the internal memory 2121. The memory 2121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The storage data area may store data (e.g., audio data, a phone book, etc.) created during use of the electronic device 2100, and the like. Further, the memory 2121 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like.

The electronic device 2100 may implement audio functions through the audio module 2170, speaker 2170A, headphones 2170B, microphone 2170C, headset interface 2170D, and application processor, among other things. Such as music playing, recording, etc.

The audio module 2170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 2170 may also be used to encode and decode audio signals. In some embodiments, the audio module 2170 may be provided in the processor 2110, or a part of the functional modules of the audio module 2170 may be provided in the processor 2110.

Speaker 2170A, also known as a "horn," is used to convert audio electrical signals into sound signals. The electronic device 2100 may listen to music through the speaker 2170A or listen to a hands-free call.

The receiver 2170B, also called "earpiece", is used to convert the audio electrical signal into an acoustic signal. When the electronic device 2100 answers a phone call or voice information, it can answer the voice by placing the receiver 2170B close to the human ear.

Microphone 2170C, also known as a "microphone," is used to convert acoustic signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal into the microphone 2170C by making a sound by approaching the microphone 2170C with the human mouth. The electronic device 2100 may be provided with at least one microphone 2170C. In other embodiments, the electronic device 2100 may be provided with two microphones to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 2100 may further include three, four, or more microphones to collect sound signals, reduce noise, identify sound sources, perform directional recording, and so on.

The earphone interface 2170D is for connecting a wired earphone. The earphone interface may be a USB interface, or may be an open mobile electronic device platform (OMTP) standard interface of 3.5mm, or a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 2180A is used for sensing pressure signal and converting the pressure signal into electric signal. In some embodiments, the pressure sensor 2180A may be disposed on the display screen 2194. Pressure sensor 2180A

Such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 2180A, the capacitance between the electrodes changes. The electronic device 2100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 2194, the electronic apparatus 2100 detects the intensity of the touch operation from the pressure sensor 2180A. The electronic apparatus 2100 may also calculate the position of the touch from the detection signal of the pressure sensor 2180A. In some embodiments, the touch operations that are applied to the same touch position but different touch operation intensities may correspond to different operation instructions. For example: and when the touch operation with the touch operation intensity smaller than the first pressure threshold value acts on the short message application icon, executing an instruction for viewing the short message. And when the touch operation with the touch operation intensity larger than or equal to the first pressure threshold value acts on the short message application icon, executing an instruction of newly building the short message.

The gyroscope sensor 2180B may be used to determine a motion pose of the electronic device 2100. In some embodiments, the angular velocity of electronic device 2100 about three axes (i.e., the x, y, and z axes) may be determined by gyroscope sensors 2180B. The gyro sensor 2180B may be used to photograph anti-shake. Illustratively, when the shutter is pressed, the gyro sensor 2180B detects a shake angle of the electronic device 2100, calculates a distance that the lens module needs to compensate according to the shake angle, and allows the lens to counteract the shake of the electronic device 2100 through a reverse motion, thereby achieving anti-shake. The gyroscope sensor 2180B can also be used for navigation and body feeling of a game scene.

The air pressure sensor 2180C is used to measure air pressure. In some embodiments, the electronic device 2100 calculates altitude, aiding in positioning and navigation from barometric pressure values measured by the barometric pressure sensor 2180C.

The magnetic sensor 2180D includes a hall sensor. The electronic device 2100 may detect the opening and closing of the flip holster with the magnetic sensor 2180D. In some embodiments, when the electronic device 2100 is a flip phone, the electronic device 2100 may detect the opening and closing of the flip according to the magnetic sensor 2180D. And then according to the opening and closing state of the leather sheath or the opening and closing state of the flip cover, the automatic unlocking of the flip cover is set.

Acceleration sensor 2180E may detect the magnitude of acceleration of electronic device 2100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the electronic device 2100 is stationary. The method can also be used for recognizing the posture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 2180F for measuring distance. The electronic device 2100 may measure distance by infrared or laser. In some embodiments, taking a picture of a scene, the electronic device 2100 may utilize the distance sensor 2180F for ranging to achieve fast focus.

The proximity light sensor 2180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 2100 emits infrared light outward through the light emitting diode. The electronic device 2100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 2100. When insufficient reflected light is detected, the electronic device 2100 can determine that there are no objects near the electronic device 2100. The electronic device 2100 may use the proximity light sensor 2180G to detect that the user holds the electronic device 2100 close to the ear for talking, so as to turn off the screen automatically to save power. The proximity light sensor 2180G may also be used in holster mode, pocket mode to unlock and lock the screen automatically.

The ambient light sensor 2180L is used to sense ambient light brightness. The electronic device 2100 may adaptively adjust the brightness of the display screen 2194 based on the perceived ambient light level. The ambient light sensor 2180L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 2180L may also cooperate with the proximity light sensor 2180G to detect whether the electronic device 2100 is in a pocket or not, so as to prevent accidental touch.

The fingerprint sensor 2180H is used for collecting fingerprints. The electronic device 2100 can utilize the collected fingerprint characteristics to implement fingerprint unlocking, access an application lock, fingerprint photographing, fingerprint incoming call answering, and the like.

The temperature sensor 2180J is used to detect temperature. In some embodiments, electronic device 2100 implements a temperature processing strategy using the temperature detected by temperature sensor 2180J. For example, when the temperature reported by temperature sensor 2180J exceeds a threshold, electronic device 2100 performs a reduction in performance of a processor located near temperature sensor 2180J to reduce power consumption and implement thermal protection. In other embodiments, the electronic device 2100 heats the battery 2142 when the temperature is below another threshold to avoid a low temperature causing the electronic device 2100 to shutdown abnormally. In other embodiments, the electronic device 2100 performs boosting of the output voltage of the battery 2142 when the temperature is below yet another threshold to avoid abnormal shutdown due to low temperature.

The touch sensor 2180K is also called a "touch panel". The touch sensor 2180K may be disposed on the display screen 2194, and the touch sensor 2180K and the display screen 2194 form a touch screen, which is also referred to as a "touch screen". The touch sensor 2180K is used to detect a touch operation applied thereto or nearby. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through the display screen 2194. In other embodiments, the touch sensor 2180K may be disposed on a surface of the electronic device 2100 at a different position than the display screen 2194.

The bone conduction sensor 2180M may acquire a vibration signal. In some embodiments, the bone conduction sensor 2180M may acquire a vibration signal of a human vocal part vibrating a bone mass. The bone conduction sensor 2180M can also contact human body pulse to receive blood pressure pulse signals. In some embodiments, the bone conduction sensor 2180M may also be disposed in a headset. The audio module 2170 may analyze a voice signal based on the vibration signal of the bone mass vibrated by the sound part acquired by the bone conduction sensor 2180M, so as to implement a voice function. The application processor can analyze heart rate information based on the blood pressure beating signals acquired by the bone conduction sensor 2180M to realize a heart rate detection function.

The keys 2190 include a power-on key, a volume key, and the like. The keys may be mechanical keys. Or may be touch keys. The electronic device 2100 may receive a key input, and generate a key signal input related to user setting and function control of the electronic device 2100.

The motor 2191 may generate a vibration cue. The motor 2191 may be used for incoming call vibration prompting or may be used for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 2191 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 2194. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 2192 may be an indicator light, may be used to indicate a state of charge, a change in power, may also be used to indicate a message, a missed call, a notification, or the like.

The SIM card interface 195 is used to connect a Subscriber Identity Module (SIM). The SIM card can be brought into and out of contact with the electronic device 2100 by being inserted into or pulled out of the SIM card interface. The electronic device 2100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. Multiple cards can be inserted into the same SIM card interface at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 2100 interacts with a network through the SIM card to implement functions such as a call and data communication. In some embodiments, the electronic device 2100 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the electronic device 2100, and cannot be separated from the electronic device 2100.

The software system of the electronic device 2100 may employ a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present invention uses an Android system with a layered architecture as an example to exemplarily illustrate a software structure of the electronic device 2100.

Fig. 22 is a block diagram of a software configuration of the electronic device 2100 in fig. 21.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom.

The application layer may include a series of application packages.

As shown in fig. 22, the application packages may include camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc. applications.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 22, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 2100. Such as management of call status (including on, off, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The workflow of the software and hardware of the electronic device 2100 is illustratively described below in connection with viewing a scene of hidden content.

When the user needs to check the hidden content, the user touches the hidden part of the word string, and when the touch sensor 2180K receives a touch operation, a corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into an original input event (including touch coordinates, a time stamp of the touch operation, and other information). The raw input events are stored at the kernel layer. And the application program framework layer acquires the original input event from the kernel layer and identifies the control corresponding to the input event. Taking the touch operation as a touch click operation, taking a control corresponding to the click operation as a text control which is displayed in a hidden manner as an example, the text control calls an interface of a system layer, a fingerprint authorization window is started, a user presses a fingerprint, the system checks the fingerprint of the user and then calls a callback method of the text control, if the system check fingerprint is judged to pass in the callback method, a database interface is called to inquire an original text, the database interface indexes a message text according to a message id keyword and returns the message text to the text control, the text control calls an interface of an application frame layer to display the original text on a display screen, meanwhile, the text control calls the interface of the application frame layer to start a timer of 30s, when the timer is overtime, the application frame layer calls the callback method of the text control, the callback method calls the database interface to inquire a cached hidden text or calls the hidden interface to acquire the hidden text, and calling an application framework layer interface to display the original text on the display screen.

Embodiments of the present application further provide a computer storage medium, which includes computer instructions, and when the computer instructions are run on an electronic device, the electronic device is caused to execute the data display method provided in the embodiments of the present application. The computer storage medium is, for example, a non-volatile storage medium.

Embodiments of the present application further provide a computer program product, which when running on a computer, causes the computer to execute the data display method provided by the embodiments of the present application.

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product may include one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic Disk), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, read only memory, random access memory, magnetic or optical disk, etc. for storing program codes.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A data display method applied to a first application having a first user interface, the first application being provided on an electronic device, the data display method comprising:

step 1: requesting a data hiding rule from a server through a message, the message including an identification of the first application and a user token,

step 2: receiving a data hiding rule returned by the server, wherein the data hiding rule comprises a matching expression and a replacement rule,

and step 3: and applying the data hiding rule to sensitive data and hiding and displaying the sensitive data based on a semantic parsing result of the candidate data, wherein the candidate data is at least one part of data used for the first user interface, and the sensitive data is the candidate data matched with the data hiding rule.
The data display method according to claim 1, wherein step 1 is performed during the start-up of the first application.
The data display method according to claim 1 or 2, wherein the candidate data is all data on the first user interface.
The data display method according to any one of claims 1 to 3, wherein when the first application receives data, the received data is displayed in plain text for a first period of time in response to the received data matching a data hiding rule.
The data display method according to any one of claims 1 to 4, wherein, in a condition that the first user interface contains the data of the hidden display, in response to a first event, whether to cancel the hiding is queried, and all the data of the hidden display on the first user interface are displayed in clear text under the condition that approval is obtained.
The data display method according to claim 1, characterized in that, in the condition that the data is detected to be selected, a menu comprising a data hiding option is provided, in the condition that the data hiding option is selected, it is detected whether the data hiding option is selected for the first time since the first application was enabled on the electronic device, if so, authorization is requested and step 1 is performed based on the selected data after obtaining the authorization, if not, step 1 is performed directly based on the selected data, wherein the message further comprises the selected data, wherein the data hiding rule received in step 2 is a custom data hiding rule.
The data display method according to any one of claims 1 to 6, wherein the candidate data is data received by the first application from outside the first application, and upon detection that the received data is sensitive data, the first application is checked whether or not to allow data hiding processing, and if so, the data hiding rule is directly applied to the received data and hidden display is performed, and if not, authorization for data hiding processing is requested, and after being authorized, the data hiding rule is applied to the received data and hidden display is performed.
The data display method according to claim 6, wherein, under the condition that it is detected that the data to be sent to the outside of the first application program contains sensitive data specified by the custom data hiding rule, it is queried whether to apply the custom data hiding rule to a receiving party, if not, the data to be sent is sent normally, and if so, the data to be sent and the custom data hiding rule are sent together.
Method for displaying data according to claim 8, characterized in that on condition of receiving data and accompanying said custom data hiding rules, it is queried whether to apply said custom data hiding rules to the received data and/or to other data already displayed on the user interface or to be displayed on the user interface, said custom data hiding rules being applied to said received data and/or to said other data in reply to the query.
A data display method applied to a first application having a first user interface, the first application being provided on an electronic device, the data display method comprising:

in response to detecting that the data which is hidden and displayed on the first user interface is selected, a password for displaying the data which is hidden and displayed in a plain text mode is requested;

and displaying the data in clear text in response to obtaining a valid password within the second time length.
The data display method according to claim 10, wherein the hidden display is restored after the data of the hidden display is displayed in a clear text for a third time period.
A data display method applied to a first application having a first user interface, the first application being provided on an electronic device, the data display method comprising:

detecting whether the first user interface includes data for hiding display in response to a long-press fingerprint event on a condition that the first user interface is displayed,

inquiring whether to cancel the hiding under the condition that the first user interface contains the data of the hiding display,

and responding to confirmation of un-hiding, and displaying all data hidden and displayed on the first user interface in a clear text mode.
A data display method applied to a first application having a first user interface, the first application being provided on an electronic device, the data display method comprising:

detecting that plaintext display data is selected, querying whether the selected data is approved for semantic parsing,

generating a custom data hiding rule based on the selected data in response to collecting user consent,

and hiding and displaying the selected data according to the user-defined data hiding rule.
A data display method applied to a first application having a first user interface, the first application being provided on an electronic device, the data display method comprising:

querying whether to accept the custom concealment rules accompanying the data based on the received data,

and in response to the fact that the user-defined hiding rule is accepted, hiding and displaying the received data according to the user-defined hiding rule.
The data display method of claim 14, wherein the display method further comprises: in response to collecting acceptance of the customized concealment rule, querying whether to use the customized concealment rule for data other than the received data,

and in response to collecting data other than the received data, applying the customized hiding rule to the first application program, storing the customized hiding rule in the first application program.
A computer storage medium comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the data display method of any one of claims 1 to 9 and 10 to 15.
A computer program product which, when run on a computer, causes the computer to perform the data display method of any one of claims 1 to 9 and 10 to 15.
An electronic device comprising a memory, a processor, and a first application stored on the memory and executable on the processor, wherein execution of the first application by the processor causes the electronic device to perform the data display method of any of claims 1 to 9 and 10 to 15.
A system for enabling data display, the system comprising an electronic device according to claim 18, and a server, the electronic device requesting data hiding rules from the server via a message, the server providing the data hiding rules based on an identity of a first application and a user token in the message.
The system according to claim 19, wherein the message further includes candidate data, the server performs semantic parsing on the candidate data in the message to obtain keywords and variables, and a data hiding rule provided by the server specifies a replacement manner for the variables.