Man-machine interaction method and system for autonomously uploading mobile phone sensor data

By developing APPs on smartphones, displaying and managing data items and their attributes that can be uploaded independently, the problem of users being unable to control smartphone data uploads independently is solved, the transparency and user autonomy of data uploads are achieved, and the user experience is improved. .

CN118972490APending Publication Date: 2024-11-15樊丽华
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410962511.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-18
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

Users cannot independently control and transparently understand the upload of smartphone data, including data types and uses, resulting in a lack of transparency and user autonomy in the data upload process.

Method used

By developing corresponding APPs on the user's mobile phone and the data collector's mobile phone, displaying data items and their attributes that can be uploaded independently, guiding users to select and agree to the data upload permissions, ensuring users' independent control and transparent understanding of the data.

Benefits of technology

It improves users' interactive experience of data upload, and through the user's independent selection and consent to data upload permissions, it ensures that the data upload process is transparent and controllable, and enhances users' judgment and management of data value.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118972490A_ABST
    Figure CN118972490A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a man-machine interaction method and system for autonomously uploading mobile phone sensor data, and the method comprises the steps: responding to the click operation of a user on a first APP, and enabling the first APP to display at least one piece of data which can be autonomously uploaded to the user; in response to a selection operation of a user on a certain item of data capable of being uploaded autonomously, the first APP searches and displays the attribute of the selected data in the data attribute list, and guides the user to feed back the permission expected to be exchanged after the selected data is uploaded according to the attribute; the mobile phone of the data collection party displays expected exchange permissions fed back by a plurality of users for the selected data through a second APP, and obtains a final exchange permission which can be provided by the data collection party; the first APP displays the final exchange permission to a user, and the first APP automatically uploads the selected data in response to a data uploading agreement operation of the user for the final exchange permission.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of human-computer interaction, and in particular to a human-computer interaction method and system for autonomously uploading mobile phone sensor data. Background Art

[0002] With the development of smart phones, personal data in mobile phones has become a very important data resource. In most mobile phones, when a function needs to obtain personal data, it only displays a general question to the mobile phone user: "Do you allow access to xx (such as camera, location, etc.) of the mobile phone?" The user does not know what kind of data will be uploaded, nor can he independently and transparently control the upload of mobile phone data and the use of uploaded data. Summary of the invention

[0003] The embodiment of the present invention provides a human-computer interaction method and system for autonomously uploading mobile phone sensor data to solve the above technical problems.

[0004] In a first aspect, an embodiment of the present invention provides a human-computer interaction method for autonomously uploading mobile phone sensor data, comprising:

[0005] The user's mobile phone displays the first APP for autonomously uploading mobile phone sensor data;

[0006] In response to a user clicking operation on the first APP, the first APP displays to the user at least one item of data that can be uploaded autonomously, a mobile phone sensor from which the data is sourced, and a purpose of the data after it is uploaded;

[0007] In response to a user's selection operation of a certain data that can be uploaded autonomously, the first APP assumes that the user preliminarily approves the data source and purpose, searches for and displays the attributes of the selected data in a data attribute list, and guides the user to provide the permissions that he or she expects to obtain after uploading the selected data based on the attribute feedback, wherein the data attribute list includes data name, data description, data purpose, data collector, privacy risk level, whether the user needs to open the sensor's read permission, data type, and data upload deadline;

[0008] The data collector's mobile phone displays the permissions that multiple users expect to obtain in exchange for the selected data feedback through the second APP, and obtains the final exchange permissions that the data collector can provide;

[0009] The first APP displays the final exchange permission to the user, and displays the user whose expected exchange permission is lower than the final exchange permission as a user who can upload data independently; in response to the user's consent to upload data for the final exchange permission, the first APP calls the sensor permission opening page on the mobile phone according to the data attribute list, and guides the user to click the permission opening button of the sensor of the selected data source independently;

[0010] In response to the user clicking the permission release button, the first APP calls the sensor of the selected data source according to the attribute list, and automatically uploads the selected data according to the data upload deadline in the attribute list.

[0011] In a second aspect, an embodiment of the present invention provides a human-computer interaction system for autonomously uploading mobile phone sensor data, including: a user's mobile phone and a data collector's mobile phone:

[0012] The user's mobile phone is used to display a first APP for autonomously uploading mobile phone sensor data; in response to a user's click operation on the first APP, the first APP displays to the user at least one item of data that can be autonomously uploaded, the mobile phone sensor from which the data comes, and the purpose of the data after being uploaded; in response to a user's selection operation on a certain item of data that can be autonomously uploaded, the first APP assumes that the user preliminarily recognizes the source and purpose of the data, searches for and displays the attributes of the selected data in a data attribute list, and guides the user to feedback the permissions expected to be obtained after uploading the selected data based on the attribute feedback, wherein the data attribute list includes data name, data description, data purpose, data collector, privacy risk level, whether the user needs to open sensor read permissions, data type, and data upload deadline;

[0013] The mobile phone of the data collector is used to display the permissions that multiple users expect to obtain in exchange for the selected data feedback through the second APP, and obtain the final exchange permissions that the data collector can provide;

[0014] The user's mobile phone is also used to display the final exchange permission to the user through the first APP. In response to the user's consent to upload data for the final exchange permission, the first APP calls the sensor permission opening page on the mobile phone according to the data attribute list, and guides the user to independently click the permission opening button of the sensor of the selected data source; in response to the user clicking the permission opening button, the first APP calls the sensor of the selected data source according to the attribute list, and automatically uploads the selected data according to the data upload deadline in the attribute list.

[0015] The embodiment of the present invention provides a human-computer interaction method for autonomously uploading mobile phone sensor data, which encapsulates the information collected by the smart phone sensor into data items that can be autonomously uploaded, and defines data attributes from multiple dimensions, so that autonomous uploading and interaction of data items are possible. This embodiment guides the user to input the willingness to autonomously upload each data through the first APP on the user's mobile phone, and feedback the authority expected to be exchanged; the data collector compares the exchange authority feedback by all users for each data item through the second APP on the mobile phone, and determines the exchange authority that can be provided in combination with the actual data use, and then negotiates with the user through the first APP whether to agree to upload the data in exchange for the final exchange authority. In the prior art, the user's value judgment on the data on the mobile phone is through questionnaires or text messages, and data collection is mostly achieved using external devices; while this embodiment guides the user to autonomously input the authority expected to be exchanged for each data through the mobile phone APP, and can understand the expectations of other users, truly feel and participate in the entire process of data evaluation, uploading and exchange of authority, and improve the user's interactive experience of data uploading. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0017] Figure 1 This is an architecture diagram of a human-computer interaction system for autonomously uploading mobile phone sensor data provided by an embodiment of the present invention;

[0018] Figure 2 It is a flow chart of a human-computer interaction method for autonomously uploading mobile phone sensor data provided by an embodiment of the present invention;

[0019] Figure 3 This is a schematic diagram of a guide interface for introducing the purpose of data upload provided by an embodiment of the present invention;

[0020] Figure 4 It is a schematic diagram of a guide interface for introducing mobile phone sensors involved in uploading data provided by an embodiment of the present invention;

[0021] Figure 5 This is a schematic diagram of a guide interface for introducing data items that can be uploaded autonomously and provided by a mobile phone sensor, provided in an embodiment of the present invention;

[0022] Figure 6 This is a schematic diagram of a "All Data Items" page under the system homepage of a first APP provided by an embodiment of the present invention;

[0023] Figure 7 is a schematic diagram of a specific page of a data item provided by an embodiment of the present invention;

[0024] Figure 8 is a schematic diagram of a "all data items" page in a second APP provided by an embodiment of the present invention;

[0025] Fig. 9 It is a formulation interface for the final exchange permission of a data item in a second APP provided by an embodiment of the present invention;

[0026] Fig.10 This is a schematic diagram of a page of “all data items” after being updated in a first APP provided by an embodiment of the present invention;

[0027] Fig.11 This is a schematic diagram of a pop-up interface when a user cannot upload a certain data item in a first APP provided by an embodiment of the present invention;

[0028] Fig.12 is a flow chart of another human-computer interaction method for autonomously uploading mobile phone sensor data provided by an embodiment of the present invention;

[0029] Fig.13 This is a flow chart of another human-computer interaction method for autonomously uploading mobile phone sensor data provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be described clearly and completely below. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work belong to the scope of protection of the present invention.

[0031] In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicating the orientation or positional relationship, are based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first", "second", and "third" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance.

[0032] In the description of the present invention, it is also necessary to explain that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0033] An embodiment of the present invention provides a human-computer interaction method for autonomously uploading sensor data of a mobile phone. In order to illustrate the method, a human-computer interaction system supporting the implementation of the method is first introduced. Figure 1 is an architecture diagram of a human-computer interaction system for autonomously uploading mobile phone sensor data provided by an embodiment of the present invention, such as Figure 1 As shown, the system includes mobile phones of multiple users, servers and mobile phones of data collectors. The users here refer to ordinary smart phone users, and the data collectors refer to institutions or devices that need to collect mobile phone data of certain users, such as a data analysis and mining agency, a company or a third-party server. This embodiment uses a mobile phone APP to display the mobile phone sensor data that can be uploaded to the user, and guides the user to understand the attributes, uses and values ​​of the uploaded data, so that the user can independently control the authority and method of uploading data. Among them, the above-mentioned mobile phone APP includes two types, one installed on the user's mobile phone, called the first APP, and the other installed on the mobile phone of the data collector, called the second APP. The two APPs exchange data through the server and negotiate the relevant information of data upload. In some embodiments, the mobile phone of the data collector can also be replaced by other electronic devices such as a PC, a server, and the second APP can also be replaced by a web page or client installed on a PC or a server, which is not specifically limited in this embodiment.

[0034] Based on the above system architecture, Figure 2 1 is a flowchart of a human-computer interaction method for autonomously uploading mobile phone sensor data provided by an embodiment of the present invention. The method is applicable to the case of negotiating and uploading user data in a smart phone, and is executed by the user mobile phone, the data collector mobile phone and the server in the above-mentioned interactive system. Figure 2 As shown, the method specifically includes:

[0035] S110 . The user's mobile phone displays a first APP for autonomously uploading mobile phone sensor data.

[0036] Exemplarily, this embodiment takes the Android (Android 8.0, SDK API level 26) system as an example and develops an APP named "My Data". Mobile phone users can click on the APP to learn about the relevant information of uploading mobile phone sensor data and perform related operations.

[0037] S120. In response to a user clicking operation on the first APP, the first APP displays to the user at least one item of data that can be uploaded autonomously, the mobile phone sensor from which the data comes, and the purpose of the data after it is uploaded.

[0038] In this embodiment, the data to be uploaded is mainly the mobile phone sensor data, and optionally, it can include 49 data collected by 14 types of mobile phone sensors. In a specific implementation, after the user clicks on the "My Data" APP, the APP first displays the basic functions of the APP to the user through a guide interface, which includes the purpose of data upload (such as Figure 3 As shown), the mobile phone sensors involved (such as Figure 4 As shown in the figure), and the data items that these mobile phone sensors can upload autonomously (such as Figure 5 As shown in the figure, only 15 items of data are selected as examples). Optionally, the guidance interface may also include an introduction to the process of users independently selecting and uploading data to help users understand the concept and process of data interaction.

[0039] Furthermore, after the guide interface is displayed, the APP homepage is entered. Optionally, the APP homepage is as follows Figure 6 As shown in the figure, the display of the system homepage includes 4 top navigation bars: all data items, categories, how to feedback the permissions expected in exchange, how to upload data and obtain the exchange permissions. Among them, under the "all data items" page, the personal data commonly used on smartphones are encapsulated as separate data items, and each data item is described by 8 attributes, namely data name, data description, upload purpose, data collector, privacy risk, permission, sensor and upload period. These attributes can be stored in the data attribute list in the background. For example, the attributes of 49 data items are shown in Table 1.

[0040] Table 1 49 data items and their attributes

[0041]

[0042]

[0043]

[0044] Specifically, the sensor in the data attribute indicates the mobile phone sensor of the data source, and the data description is based on the mobile phone sensor of the data source, and describes the data item in more detail. Permission refers to whether the upload of a certain data item requires the access permission of the mobile phone sensor in the Android system, and its value is "yes" or "no". The data collector describes to whom the collected data upload will be provided, and the upload purpose refers to the purpose of the data after it is uploaded, including physiological and psychological analysis, personalized advertising, exercise suggestions, and improved user experience. The upload period quantifies the length of time during the data collection period (measured in days, such as 7 days of data upload allowed in Table 1). Privacy risk reflects the risk level of personal data, and 1 and 5 represent the lowest and highest privacy risks respectively. It should be noted that the "permissions obtained in exchange" and "permissions expected to be obtained in exchange" in the above embodiment refer to other rewards that users expect to obtain by uploading a piece of data; and the "permissions" in Table 1, that is, the "read permission" in "whether the user needs to open the sensor's read permission", refers to the settings or operations that users need to perform when uploading a piece of data (data cannot be uploaded without operation). These two permissions are different and should be distinguished.

[0045] More specifically, combined Figure 6 Each data item can be displayed on the "All Data Items" page in the form of a card with 1 row and 2 columns. Each card represents a data item. The top of the card is the data name, and the bottom of the card is: You have not yet provided feedback on the permissions you expect to obtain for this data. Data items with different privacy risks use different card background colors.

[0046] S130. In response to the user's selection operation on a certain data that can be uploaded autonomously, the first APP assumes that the user preliminarily approves the source and purpose of the data, searches for and displays the attributes of the selected data in the data attribute list, and guides the user to upload the permissions he or she hopes to obtain after the selected data is uploaded based on the attribute feedback.

[0047] Combination Figure 6 When the user clicks on a data item card on the "All Data Items" page, the user will be taken to the page for that data item. Figure 7 The page displays the following contents from top to bottom: data name, data card, and a reminder "You have not yet provided feedback for the permissions you wish to obtain for this data", and a "Feedback for permissions" button is displayed at the bottom of the card. Through such a page for specific data items, users are guided to provide feedback for the permissions they wish to obtain for each data item, which can only be provided once and cannot be modified.

[0048] S140. Multiple user mobile phones send, through their respective first APPs, to the server the permissions that each user hopes to obtain in exchange after uploading various data.

[0049] When a user enters a data item card that does not have feedback in exchange for permissions, and clicks the "Feedback in exchange for permissions" button at the bottom of the card (such as Figure 7 As shown), the first APP first checks whether the data requires the sensor's read permission to be opened. If the "Permission" column corresponding to the data in the data attribute list is "Yes", the first APP calls the sensor permission opening page on the mobile phone according to the data attribute list, and guides the user to independently click the permission opening button of the sensor of the selected data source. In response to the user clicking the permission opening button, the user can provide feedback in exchange for permission. If the user does not open the permission, the operation of providing feedback in exchange for permission will not be able to be performed. If the "Permission" column corresponding to the data in the data attribute list is "No", the user can directly provide feedback in exchange for permission.

[0050] The permissions that each user expects to obtain in exchange for each data feedback are uploaded to the server in real time, and the server's exchange permission list will record the permissions that all users expect to obtain in exchange for each data feedback.

[0051] S150: The server preliminarily recommends permissions that can be exchanged for various data according to the number of feedback users and the distribution pattern of feedback content.

[0052] In this embodiment, the server can provide preliminary suggestions for the permissions that can be exchanged for each data according to the default calculation method. According to different types of permissions to be exchanged, this embodiment provides the following two optional implementation methods:

[0053] In the first optional implementation, the expected exchange rights reported by the user are the expected exchange income, such as WeChat payment income. At this time, in a specific implementation, the server can arrange the expected exchange income of each user for the same data feedback in order from low to high, and select the first 1 / 3 of the users as the users who can upload, and the lowest income among the expected exchange income reported by the last 2 / 3 of the users is initially suggested as the income that the data can be exchanged for. For example, the expected exchange income of each user for the same data feedback is 1, 2, 3, 3.2, 4, 5, 6, 7, 8, then the users who feedback 1, 2, 3 are users who can upload, and the lowest income of 3.2 among other users is the income that the data can be exchanged for. At this time, the initial suggestion of the exchange right can be understood as a demarcation point for exchange income, and users below the demarcation point are defaulted as users who can upload data. In practical applications, the above two proportions 1 / 3 and 2 / 3 can also be adjusted according to the total income that the data collector can provide, and this embodiment is not particularly limited.

[0054] In another specific embodiment, the server can fit a linear regression equation through the WeChat payment income expected to be exchanged for various data feedbacks accumulated by multiple users during the operation of the system. The equation takes the expected WeChat payment income as the dependent variable, and the attributes of the uploaded data and the user attributes as the independent variables. The equation is used to characterize the relationship between the WeChat payment income of the data line and the data itself and the user characteristics. Optionally, the server can use the stepwise regression method in SPSS to establish a regression model for data items in exchange for income based on the collected data. In the regression process, for continuous variables (such as age), the original value can be used as input. For ordinal variables (for example, the number of hours a smartphone is used per day), values ​​1-n can be used to represent different levels (n refers to the number of levels). For categorical variables (for example, upload purposes), they can be converted into n-1 "dummy variables", which use a series of Boolean values ​​to represent the values ​​of the original categorical variables. The output of the model can be interpreted as the expected income of a specific user for the corresponding product. Among them, the regression model of all variables includes:

[0055] y=β0+β1*x1+β2*x2+β3*x3+β4*x4+β5*x5+β6*x6+β7*x7+β8*x8+β9*x9+β10* x10+β11*x11+β12*x12+β13*x13+β14*x14+β15*x15+β16*x16+β17*x17 (Formula 1)

[0056] Among them, y represents the benefit of the data item, x1 represents privacy risk, x2 represents permission, x3 represents the purpose of uploading, x4 represents age, x5 represents monthly living expenses, x6 represents the time of using smartphones every day, x7 represents neuroticism, x8 represents conscientiousness, x9 represents agreeableness, x10 represents openness, x11 represents extraversion, x12 represents familiarity with data types (data types correspond to sensors), x13 represents ethnicity, x14 represents gender, x15 represents monthly income, x16 represents education level, and x17 represents marriage; β0, β1, β2, β3, β4, β5, β6, β7, β8, β10, β11, β12, β13, β14, β15, β16, and β17 are regression coefficients. It is worth mentioning that in the fitting of the regression model, if a certain independent variable (such as data attribute) is always a fixed value, it can be excluded from the independent variable range of the model. For example, the independent variables in Formula 1 only include three data attributes. Furthermore, the variables with high significant effects in the model were screened according to the fitting results, and the variables with low significant effects were deleted from the model. Finally, for student users, 14 variables x1-x14 were retained, and for non-student users, 17 variables x1-x17 were retained. The final regression models for student and non-student participants are shown in Formulas 2 and 3 in Table 2.

[0057] Table 2 Regression models for students and non-students

[0058]

[0059] Significance level*α=.05**α=.01***α=.001

[0060] The server substitutes the attributes of different users and the attributes of the data to be recommended into formula (2) or formula (3), and can preliminarily recommend the WeChat payment benefits that can be exchanged for each data. More specifically, in the fitting process of the above model, the student users and non-student users participating in the feedback should also meet the diversity of the group. In a specific implementation, the users selected by the server include 181 students (69 males, 112 females) and 34 non-students (14 males, 20 females). All of them use Android smartphones every day. All students are freshmen on campus, with an average age of 18.6 years old (SD = 0.9). Among them, 113 are Han and 68 are ethnic minorities. Their average living cost is 1,241 yuan per month (SD = 552 yuan). Non-student participants were recruited from the capital of a province using the snowball method. There are 3 Han and 31 ethnic minorities. The average age is 39.9 years old (SD = 10.8). The average monthly income is 6,066 yuan (SD = 3,360 yuan).

[0061] In the second optional implementation mode, the rights that the user feedback expects to exchange are the read rights of other data that are expected to be exchanged, and the purpose after reading the data. At this time, the server can match the other data that can be exchanged with the feedback user through the data uploaded by multiple users accumulated during the operation of the system and the data purposes recognized by the uploading users. Exemplarily, if more than a set number of users expect to be able to exchange the read rights of the same other data after uploading a certain data, it indicates that many users have the demand for the same other data. At this time, the server can count the data purposes that the users who exceed the set number feedback the most times for the same other data. If the data purposes that are the most times match the data purposes recognized by the uploading users of the same other data, the server will preliminarily recommend the read rights and data purposes of the same other data as the rights that the data can exchange. The recommended permissions may not be exactly the same as the expected permissions that the user initially feedbacks for a certain data (mainly because the data purposes are different), but it represents the conventional data purposes of most users for the same other data, and is consistent with the purposes of the uploader, and has certain usage significance and recommendation value.

[0062] S160. The mobile phone of the data collector reads the permissions that each user expects to obtain in exchange for the selected data from the server through the second APP, as well as the permissions that the server preliminarily recommends that the selected data can be obtained in exchange, and displays them.

[0063] The data collector can log in to the second APP as a system administrator and specify a time period for each user to provide feedback on a certain data item in exchange for the permissions they hope to obtain. After the time period ends, the second APP reads the number of people who have provided feedback and the content of the feedback from the server in real time. At this time, on the "All Data Items" page of the second APP, the number of people who have provided feedback is displayed under the card of each data item. Taking the exchange of permissions in the form of income as an example, Figure 8 A page showing all data items of a second APP is displayed, and the number of people who have given feedback and the initial recommended benefits are shown under the card for each data item.

[0064] It should be noted that in this embodiment, S150 can also be omitted, that is, the server only receives and stores the information fed back by each user, and does not recommend the permissions that can be exchanged for each data. Accordingly, in S160, the mobile phone of the data collector can read the permissions that each user expects to exchange for the selected data feedback from the server through the second APP.

[0065] S170. In response to the final exchange authority that can be provided for the selected data input by the data collector, the second APP determines the users whose expected exchange authority is lower than the final exchange authority as users who can upload autonomously, and uploads the user information and the final exchange authority to the server; the server updates the authority that can be exchanged for the selected data to the final exchange authority.

[0066] Continuing with the example of exchanging rights for income, combined with Figure 8 , the data collector clicks on the card of a data item on the "All Data Items" page to enter the final exchange permission setting interface for the data item, such as Fig. 9 As shown. The interface displays the data name from top to bottom, as well as a "View All Benefits" button; when the system administrator clicks the "View All Benefits" button, the expected benefits reported by all users are displayed in a grid view on the interface and arranged in ascending order, with a single line showing the serial number and double lines showing the expected benefits. The page prompts the system administrator to select the location of the final benefit (i.e., the final exchange of permissions) based on the actual benefits that can be provided. After the system administrator clicks on a certain value of benefits, the second APP can determine the users who have reached an agreement on the permissions that can be exchanged for the data (i.e., users who can upload independently), as well as the final exchange permissions. These users are the users who can upload the data. Exemplarily, taking the exchange of permissions in the form of benefits as an example, the users who have reached an agreement are users whose expected benefits are less than the final benefits.

[0067] Specifically, the grid view shows below: The selected position is x, the revenue is x, the feedback users before this position can upload data and obtain the revenue, the number of people is x, and a total of x yuan needs to be paid. After the system administrator clicks the new price, the grid shows below: The new position selected is x, the revenue is x, the feedback users before this position can upload data and obtain the revenue x, the number of people is x, and a total of x yuan needs to be paid. Calculate and display how much revenue the supply and demand pay, so that the system administrator can ensure that the total payment does not exceed the total amount that can actually be provided. After the system administrator clicks the "Submit" "Submit Final Revenue" button, the users who can upload the data and the final exchange rights are uploaded to the server in real time, and the exchange rights list on the server records the users who can upload each data and the final exchange rights.

[0068] If the exchange permission is expressed as the permission to read other data, then the user who reports that the other data he expects to exchange is less than the other data that the data collector can provide (i.e., the final exchange permission) can be determined as a user who can upload autonomously. For example, if the user expects to exchange for three other data, and the data collector can provide four other data (including the three other data expected by the user), then the user will be determined as a user who can upload autonomously.

[0069] S180. The first APP reads the permissions that the selected data can ultimately exchange for from the server, and displays them to the user.

[0070] After the system administrator determines the uploader and final exchange permissions for each data item, the first APP reads the uploader and exchange permissions for each data item from the exchange permission list of the server and updates it to the "All Data Items" page, such as Fig.10 At this time, the following information is displayed under each data card: can be uploaded / cannot be uploaded, final exchange permission, permission you expect to exchange, uploaded / not uploaded, exchange permission obtained / not obtained. It should be noted that due to space limitations, Figure 8 and Fig.10 Only 6 data attributes are displayed in the data card in the figure. Privacy risks are not displayed in the card and are only distinguished by different colors. In actual applications, privacy risks can also be displayed in the data card. A total of 7 data attributes are displayed. Different privacy risks can be distinguished by different colors (such as Figure 6 After the user clicks on a data card, the page displays the same information as the data card, and displays a "View Exchange Permission and Upload" button at the bottom (actually corresponding to Fig.11 ).

[0071] S190. In response to the user's consent to upload data, the first APP determines whether the selected data requires the user to open the sensor's read permission based on the data attribute list.

[0072] When the user clicks the "View Exchange Permissions and Upload" button, a pop-up interface displays the exchange permissions reported by all other users, including the permissions that users who can upload the data expect to exchange, the permissions that users who cannot upload the data expect to exchange, and the final exchange permissions. When the user cannot upload the data, a pop-up interface displays the permissions that all other users expect to exchange and a prompt that the data cannot be uploaded, such as Fig.11 When a user uploads a certain data, a pop-up interface displays all other permissions that the user wishes to obtain, and determines whether the data requires the user to open the sensor's read permission based on the data attribute list, that is, the "Permission" column corresponding to the data in the data attribute list is "Yes" or "No".

[0073] S200: Whether the selected data requires the user to open the sensor's reading permission, the selected data is added to the upload list of the first APP in different ways.

[0074] If the "Permission" column corresponding to the data in the data attribute list is "Yes", the first APP calls the sensor permission opening page on the mobile phone according to the data attribute list, and guides the user to click the permission opening button of the sensor of the selected data source. In response to the user clicking the permission opening button, the first APP adds the selected data to the upload list, and uploads the user information and data information to the server in real time, and the server records the data in the list to be uploaded. If the user does not open the permission, the subsequent data upload operation will not be possible.

[0075] If the "Permission" column corresponding to the data in the data attribute list is "No", the first APP directly adds the selected data to the upload list.

[0076] S210. The first APP displays the data items recorded in the upload list to the user through the upload list page; in response to the user clicking the upload button on the upload list page, the first APP uses the data items checked by the user on the upload list page as data to be uploaded, calls the sensor of the data source to be uploaded according to the attribute list, and automatically uploads the selected data according to the data upload deadline in the attribute list.

[0077] On the upload list page, all added data items are displayed in a list on the page. Optionally, the information of each item is displayed in 1 row and 4 columns. The contents of the 4 columns are check boxes, cards, data names, and final exchange permissions. The top of the page displays: a total of x items of data, and the bottom line displays check boxes, select all, selected (quantity), total (revenue), and an "Upload" button. When uploading data, users can first select the data to be uploaded by clicking the check box in front of each data item or clicking the check box in front of select all, and then click the "Upload" button. In addition, users can also delete data items on the upload list page. When the data list on the upload page changes, the data in the server's list to be uploaded will also be updated in real time.

[0078] Furthermore, when the user clicks the "Upload" button on the upload list page, the first APP automatically performs a second check on the permissions of each data item on the page to prevent the user from adding the data item to the upload list and then turning off the permission without uploading it. Therefore, another permission check is performed before uploading.

[0079] If a certain data requires permission, the first APP pops up an interface to guide the user to open the permission. If the user opens the permission, the user information and data information will be automatically uploaded to the server, and the data will begin to be collected and uploaded to the server. The upload time is the upload deadline displayed in the card; at the same time, the data of the user in the list to be uploaded in the server is deleted in real time, and the data of the user in the uploaded list is recorded in real time. If the user does not open the permission, the first APP will prompt the user to open it. If the user does not open it, it will prompt again after 1 hour, 2 hours and 3 hours. If the user does not open it after the prompt, the user will not be able to upload the data. Furthermore, during the upload period, it will be checked every day whether the user has turned on the sensor's read permission. If it is not turned on, the above prompt will be made to prevent the user from turning off the sensor's read permission during other uses of the mobile phone and being unable to upload data.

[0080] If the data does not require permission, the user and data information is automatically uploaded to the server, and the data begins to be collected and uploaded to the server. The upload time is the upload deadline displayed in the card. The data of the user in the list to be uploaded on the server is deleted in real time, and the data of the user in the uploaded list is recorded in real time.

[0081] Furthermore, if the sensor of the selected data source is a positioning sensor, the first APP automatically collects the selected data from the positioning sensor at a frequency of 1Hz and uploads it; if the sensor of the selected data source is a call record, the first APP automatically reads the log record of the user's call, analyzes the selected data from the read content and uploads it; if the sensor of the selected data source is APP usage, the first APP automatically reads the user's record of using all APPs, analyzes the selected data from the read content and uploads it; if the sensor of the selected data source is a camera, the first APP prompts the user to enter the first APP interface and turn on the front and rear cameras as required, collect the selected data and upload it; if the sensor of the selected data source is a microphone, the first APP automatically collects the selected data from the microphone at a frequency of 8kHz and uploads it. The data upload method is to transmit the encrypted POST api to the server using the HTTPS service, and the data is packaged and uploaded once every certain period of time.

[0082] S220: After the data is uploaded, in response to the user's operation of obtaining the final exchange permission, the first APP requests the server to check whether the data upload deadline has been met.

[0083] After the data is uploaded, the uploaded data is displayed in the form of a list on the "Exchanged Permissions" page of the first APP. The information of each data item in the page is displayed in 1 row and 4 columns. The contents of the 4 columns are the card, data name, exchanged permissions (the permissions the user hopes to exchange), and the prompt "xx permissions can be obtained / have been obtained after a certain month, day, hour, minute, and second." The top of the page shows: A total of items have been obtained. When the user clicks the "Exchange Permissions" button, the first APP requests the server to check whether the data upload deadline has been met.

[0084] S230. The server checks whether a data upload deadline for the selected data has been met based on the server time when the selected data is first received and the current server time.

[0085] This step uses the server time to calculate the data upload time to see if the time the user uploaded the data meets the time required by the data card, to avoid inconsistencies in the timestamps in each user's mobile phone, which may lead to errors in calculating the upload time. Of course, the inspection process can also be completed by the first APP, which can obtain the server time through a static method when uploading the selected data for the first time, and obtain the server time again when the user clicks "Exchange Permissions", and calculate whether the time the user uploaded the data meets the time required by the data card based on the difference between the two server times.

[0086] S240. If satisfied, the first APP provides the user with the final exchange authority; if not satisfied, the first APP converts the server time at which the final exchange authority can be obtained into the time of the user's mobile phone and displays it to the user.

[0087] On the "Exchanged Permissions" page, if an item in the list meets the upload deadline, the 4th column of the corresponding data item on the interface will display: xx permission has been obtained (for example, ¥ yuan has been obtained), and the information of the user and the data will be automatically uploaded to the server, and the contents of the exchanged permissions list on the server will be recorded; if an item in the list does not meet the upload deadline, the 4th column of the corresponding data item on the interface will display: can be obtained / received after a certain month, day, hour, minute, and second.

[0088] It should be noted that the final exchange rights in this embodiment are only a condition for determining whether the exchange is agreed with the user. When the exchange rights are finally provided to the user, if the exchange rights expected by the user are lower than the final exchange rights, only the rights expected to be exchanged can be provided to the user. For example, when the expected benefits of the user are less than the final benefits, the expected benefits can be provided; when the other data that the user expects to exchange is less than the data that the data collector can provide, the other data that the user expects to exchange can be provided.

[0089] At this point, S110-S240 has completed the entire process from self-selection to upload data, negotiation in exchange for permissions, data upload to exchange for other permissions. This process can also be combined with Fig.12 and Fig.13 To understand, the two attached figures show the interactive process of autonomously uploading mobile phone sensor data from different angles.

[0090] Furthermore, taking the exchange of rights in the form of benefits as an example, as the number of users accumulates, users who can eventually upload data items can be extracted from all users who give feedback on their expectations of exchange for benefits. The expected exchange benefits y given by these users, as well as the attributes of these users and the attributes of the data items for which the feedback is given, are used to fit the model described in Formula 1:

[0091] y=β0+β1*x1+β2*x2+β3*x3+β4*x4+β5*x5+β6*x6+β7*x7+β8*x8+β9*x9+β10* x10+β11*x11+β12*x12+β13*x13+β14*x14+β15*x15+β16*x16+β17*x17 (Formula 1)

[0092] The fitted model at this time better represents the relationship between the exchange benefits and the user attributes and data attributes when the user's willingness matches the data collector's ability. In the process of uploading new data (for example, the 50th data that can be uploaded appears), the attributes of the user using the first APP and the attributes of the new data can be substituted into formula (1), and the calculated exchange benefits can be directly displayed in the first APP as the final exchange permissions, eliminating the process of the data collector entering the final exchange permissions through the second APP.

[0093] In summary, this embodiment provides a human-computer interaction method for autonomously uploading mobile phone sensor data, which encapsulates the information collected by 14 sensors on the smartphone into 49 items of data that can be autonomously uploaded, and defines data attributes from 8 dimensions, making autonomous uploading and interaction of data items possible. This embodiment guides users to input their willingness to autonomously upload 49 items of data on their smartphones through the first APP "My Data" on the user's mobile phone, and feedback the permissions they expect to exchange; the data collector compares the exchange permissions feedback by all users for each data item through the second APP on the mobile phone, and determines the final exchange permissions that can be provided in combination with the actual data usage, and then negotiates with the user through the first APP whether to agree to upload data in exchange for the final exchange permissions.

[0094] Specifically, the data items in this embodiment cover 14 sensors on smartphones, including GPS, Bluetooth, temperature, call records, magnetic field, barometer, application usage, camera, accelerometer, light, microphone, WiFi, gyroscope and touch screen, etc., which greatly expands the scope of data that can be uploaded autonomously. At the same time, the data attribute dimensions defined in this embodiment are data name, sensor, data description, authority, data collector, upload purpose, upload period and privacy risk. Through these 8 attributes, the characteristics of personal data on smartphones can be fully described, making data more transparent, allowing users to understand data in a social context, intuitively understand the source of data, permissions to be opened and privacy risks, and provide convenience for users to upload data autonomously.

[0095] In addition, in the prior art, users make value judgments on data on their mobile phones through questionnaires or text messages, and data collection is mostly achieved using external devices; however, this embodiment uses a mobile phone APP to guide users to independently input the permissions they hope to obtain in exchange for various data, and can understand the expectations of other users, truly feel and participate in the entire process of data evaluation, uploading and exchanging permissions, thereby improving the user's interactive experience with data uploading.

[0096] Based on the same inventive concept, the embodiment of the present invention further provides Figure 1 The human-computer interaction system for autonomously uploading mobile phone sensor data shown includes a user's mobile phone and a data mobile phone.

[0097] The user's mobile phone is used to display a first APP for autonomously uploading mobile phone sensor data; in response to a user's click operation on the first APP, the first APP displays to the user at least one item of data that can be autonomously uploaded, the mobile phone sensor from which the data comes, and the purpose of the data after being uploaded; in response to a user's selection operation on a certain item of data that can be autonomously uploaded, the first APP assumes that the user preliminarily recognizes the source and purpose of the data, searches for and displays the attributes of the selected data in a data attribute list, and guides the user to feedback the permissions expected to be obtained after uploading the selected data based on the attribute feedback, wherein the data attribute list includes data name, data description, data purpose, data collector, privacy risk level, whether the user needs to open sensor read permissions, data type, and data upload deadline;

[0098] The mobile phone of the data collector is used to display the permissions that multiple users expect to obtain in exchange for the selected data feedback through the second APP, and obtain the final exchange permissions that the data collector can provide;

[0099] The user's mobile phone is also used to display the final exchange permission to the user through the first APP. In response to the user's consent to upload data for the final exchange permission, the first APP calls the sensor permission opening page on the mobile phone according to the data attribute list, and guides the user to independently click the permission opening button of the sensor of the selected data source; in response to the user clicking the permission opening button, the first APP calls the sensor of the selected data source according to the attribute list, and automatically uploads the selected data according to the data upload deadline in the attribute list.

[0100] This embodiment and the human-computer interaction method described in any of the above embodiments are based on the same inventive concept. Any limitation in the human-computer interaction method described in any of the above embodiments is applicable to this embodiment and can enable this embodiment to achieve the same beneficial effects.

[0101] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the technical solutions of the embodiments of the present invention.

Claims

1. A human-computer interaction method for autonomously uploading mobile phone sensor data, characterized in that: include: The user's mobile phone displays the first APP for autonomously uploading mobile phone sensor data; In response to a user clicking operation on the first APP, the first APP displays to the user at least one item of data that can be uploaded autonomously, a mobile phone sensor from which the data is sourced, and a purpose of the data after it is uploaded; In response to a user's selection operation of a certain data that can be uploaded autonomously, the first APP assumes that the user preliminarily approves the data source and purpose, searches for and displays the attributes of the selected data in a data attribute list, and guides the user to provide the permissions that he or she expects to obtain after uploading the selected data based on the attribute feedback, wherein the data attribute list includes data name, data description, data purpose, data collector, privacy risk level, whether the user needs to open the sensor's read permission, data type, and data upload deadline; The data collector's mobile phone displays the permissions that multiple users expect to obtain in exchange for the selected data feedback through the second APP, and obtains the final exchange permissions that the data collector can provide; The first APP displays the final exchange permission to the user, and displays the user whose expected exchange permission is lower than the final exchange permission as the user who can upload data autonomously; In response to the user who can upload data autonomously agreeing to upload data for the final permission exchange operation, the first APP calls the sensor permission opening page on the mobile phone according to the data attribute list, and guides the user who can upload data autonomously to autonomously click the permission opening button of the sensor of the selected data source; In response to the user who can upload data autonomously clicking the permission release button, the first APP calls the sensor of the selected data source according to the attribute list, and automatically uploads the selected data according to the data upload deadline in the attribute list.

2. The method according to claim 1, characterized in that Before the mobile phone of the data collector displays the permissions desired to be obtained by multiple users in exchange for the selected data feedback through the second APP, the method further includes: Multiple user mobile phones send the permissions that each user hopes to obtain after uploading various data to the server through their respective first APPs; The server preliminarily recommends the permissions that can be exchanged for each data according to the number of feedback users and the distribution pattern of feedback content.

3. The method according to claim 2, characterized in that The rights that are expected to be exchanged include the WeChat payment income that is expected to be exchanged; The server preliminarily recommends the permissions that can be exchanged for each data based on the number of feedback users and the distribution pattern of feedback content, including: The server accumulates the WeChat payment revenues that multiple users expect to obtain in exchange for various data feedbacks, and uses the WeChat payment revenues that are expected to be obtained in exchange as the dependent variable, and uses the attributes of the uploaded data and the user attributes as the independent variables to fit a linear regression equation; The server preliminarily suggests the WeChat payment income that can be exchanged for each data based on the linear regression equation.

4. The method according to claim 2, characterized in that: The permissions that are expected to be exchanged include permissions to read other data and data usage that are expected to be exchanged; The server preliminarily recommends the permissions that can be exchanged for each data based on the number of feedback users and the distribution pattern of feedback content, including: The server accumulates data uploaded by multiple users and data uses approved by the uploading users; If more than a set number of users expect to obtain the permission to read other data after uploading a certain data, then determine the data usage with the most feedback from more than a set number of users for the same other data; If the data usage with the highest number of times matches the data usage approved by the uploading user of the same other data, the server will preliminarily recommend the reading permission and data usage of the same other data as the permission that can be exchanged for the certain data.

5. The method according to claim 2, characterized in that: The mobile phone of the data collector displays the permissions that multiple users expect to obtain in exchange for the selected data feedback through the second APP, and obtains the final exchange permissions that the data collector can provide, including: The mobile phone of the data collector reads the permissions that each user expects to obtain in exchange for the selected data from the server through the second APP, as well as the permissions that the server initially recommends the selected data to obtain, and displays them; In response to the final exchange authority that can be provided for the selected data input by the data collector, the second APP determines the users whose expected exchange authority is lower than the final exchange authority as users who can upload autonomously, and uploads the user information and the final exchange authority to the server; The server updates the authority that can be exchanged for the selected data to the final exchange authority.

6. The method according to claim 5, characterized in that In response to the user who can upload data autonomously agreeing to upload data for the final permission exchange operation, the first APP calls the sensor permission opening page on the mobile phone according to the data attribute list to guide the user who can upload data autonomously to autonomously click the permission opening button of the sensor of the selected data source, including: In response to the user who is capable of autonomously uploading data agreeing to upload data, the first APP determines, according to the data attribute list, whether the selected data requires the user to open the sensor reading permission; If yes, the first APP calls the sensor permission opening page of the mobile phone according to the data attribute list to guide the user who can upload data autonomously to autonomously click the permission opening button of the sensor of the selected data source; If not, the first APP records the selected data into an upload list.

7. The method according to claim 6, characterized in that In response to the user who can upload data autonomously clicking the permission release button, the first APP calls the sensor of the selected data source according to the attribute list, including: In the case where the selected data requires the user to open the sensor's read permission, in response to the user who can upload data autonomously clicking the permission opening button, the first APP records the selected data into the upload list; The first APP displays the data items recorded in the upload list to the user who can upload data independently through the upload list page; In response to the user who can upload data autonomously clicking the upload button on the upload list page, the first APP uses the data items checked by the user on the upload list page as data to be uploaded, and calls the sensor of the source of the data to be uploaded according to the attribute list.

8. The method according to claim 1, characterized in that The first APP calls the sensor of the selected data source according to the attribute list, and automatically uploads the selected data according to the data upload deadline in the attribute list, including: If the sensor of the selected data source is a positioning sensor, the first APP automatically collects the selected data from the positioning sensor at a frequency of 1 Hz and uploads it; If the sensor of the selected data source is a call record, the first APP automatically reads the log record of the user's call, analyzes the read content to obtain the selected data, and uploads it; If the sensor of the selected data source is APP usage, the first APP automatically reads the user's records of using all APPs, analyzes the read content to obtain the selected data, and uploads it; If the sensor of the selected data source is a camera, the first APP prompts the user to enter the first APP interface and turn on the front and rear cameras as required to collect and upload the selected data; If the sensor of the selected data source is a microphone, the first APP automatically collects the selected data from the microphone at a frequency of 8 kHz and uploads it.

9. The method according to claim 1, after the first APP calls the sensor of the selected data source according to the attribute list in response to the user who can upload data autonomously clicking the permission opening button, and automatically uploads the selected data according to the data upload deadline in the attribute list, further comprising: After the data is uploaded, in response to the user who can upload data autonomously obtaining the final exchange permission, the first APP requests the server to check whether the data upload deadline has been met; The server checks whether a data upload deadline for the selected data has been met based on a server time when the selected data is first received and a current server time; If satisfied, the server provides the final exchange authority to the user who can upload data autonomously through the first APP; If it is not satisfied, the server will convert the server time that can obtain the final exchange permission into the time of the user's mobile phone through the first APP, and display it to the user who can upload data independently.

10. A human-computer interaction system for autonomously uploading mobile phone sensor data, characterized in that: include: User's mobile phone and data collector's mobile phone: The user's mobile phone is used to display a first APP for autonomously uploading mobile phone sensor data; in response to a user's click operation on the first APP, the first APP displays to the user at least one item of data that can be autonomously uploaded, the mobile phone sensor from which the data comes, and the purpose of the data after being uploaded; in response to a user's selection operation on a certain item of data that can be autonomously uploaded, the first APP assumes that the user preliminarily recognizes the source and purpose of the data, searches for and displays the attributes of the selected data in a data attribute list, and guides the user to feedback the permissions expected to be obtained after uploading the selected data based on the attributes, wherein the data attribute list includes data name, data description, data purpose, data collector, privacy risk level, whether the user needs to open sensor read permissions, data type, and data upload deadline; The mobile phone of the data collector is used to display the permissions that multiple users expect to obtain in exchange for the selected data feedback through the second APP, and obtain the final exchange permissions that the data collector can provide; The user's mobile phone is also used to display the final exchange authority to the user through the first APP, and display users whose expected exchange authority is lower than the final exchange authority as users who can upload data independently; in response to the user's consent to upload data for the final exchange authority, the first APP calls the sensor authority opening page on the mobile phone according to the data attribute list, and guides the user to click the authority opening button of the sensor of the selected data source independently; in response to the user clicking the authority opening button, the first APP calls the sensor of the selected data source according to the attribute list, and automatically uploads the selected data according to the data upload deadline in the attribute list.