Data management method and system, electronic equipment and computer readable medium

Abstract

The invention relates to the technical field of terminals, in particular to a data management method and system, electronic equipment and a computer readable medium. The method applied to first electronic equipment comprises the following steps: determining an age group of a user; if the age group of the user belongs to the first age group, a first control is displayed, the first control is used for controlling a second electronic device to obtain the authority of the first data, and the second electronic device is used for managing the first electronic device; in response to the operation of the user on the first control, allowing or forbidding the second electronic equipment to obtain the first data; and if the age of the user belongs to the second age group, not displaying the first control. Therefore, the electronic equipment can adaptively match the data management scheme for the user according to the age group of the user and display the corresponding control authority.

Description

[0001] This application is a divisional application, the original application's application number is 202310560257.1, the original application's date is May 17, 2023, and the entire contents of the original application are incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the technical field of terminals, and in particular to a data management method and system, an electronic device, and a computer readable medium. BACKGROUND

[0003] With the development of the terminal technology field, wearable devices suitable for different age groups are also increasing, such as smart watches and the like. Among them, smart watches and the like usually need to be connected with mobile terminals such as mobile phones, and the mobile phones are authorized to manage the data on the watches and the like. For example, when a user uses a smart watch is a child, the user who uses a mobile phone to manage the data on the smart watch can be the child's parent.

[0004] However, the current data management scheme for smart watches and the like is relatively single, and the data management scheme cannot adapt to the adjustment of the control authority of the related data by the mobile terminal and the watch terminal for users of different age groups. SUMMARY

[0005] The present application provides a data management method and system, an electronic device, and a computer readable medium. The scheme can adaptively adjust the matched data management scheme according to the age group of the user of the watch and the like to control the operation authority on the managed device and the operation authority on the corresponding bound management device, which is beneficial to improve the user's experience while ensuring data security.

[0006] In a first aspect, the present application provides a data management method applied to a first electronic device, the method comprising: determining the age group of a user; if the age group of the user belongs to a first age group, displaying a first control, the first control being used to control the authority of a second electronic device to obtain first data, the second electronic device being used to manage the first electronic device; in response to the operation of the user on the first control, allowing or prohibiting the second electronic device to obtain the first data; if the age of the user belongs to a second age group, not displaying the first control.

[0007] For example, the first electronic device described above can be a watch, and the second electronic device described above can be a mobile phone. The mobile phone can manage the watch through the installed smart care application. The watch can match a data management scheme suitable for the age group of the user of the watch according to the age group of the user of the watch at present, which is used to manage the data and / or application on the watch. The data management scheme can allocate a part of the control authority to the watch terminal, and correspondingly, another part of the control authority can be allocated to the mobile phone terminal.

[0008] For example, the first age stage is an adult stage of 18 years old or above. The watch can display the first control after the watch is configured with the watch-side permission according to the matched data management scheme corresponding to the adult stage. At this time, the first electronic device, for example, the watch, can allow the watch user to operate the first control.

[0009] The second age stage can include a child stage of 14 years old or below and an adolescent stage of 14 years old or above and 18 years old or below. The watch can not display the first control after the watch is configured with the watch-side permission according to the matched data management scheme corresponding to the child stage or the adolescent stage. At this time, the first electronic device, for example, the watch, can not allow the watch user to operate the first control.

[0010] In a possible implementation of the first aspect, determining the age stage of the user includes: sending a first query request to a first cloud server, where the first query request is used to obtain an age stage label in first account-related information of the user, and the age stage label is determined based on age information of the user recorded in the first account-related information; and determining the age stage of the user according to the obtained age stage label.

[0011] For example, the first cloud server can be an account cloud, and the first account can be a watch account. The account cloud can store watch account-related information of the user of the first electronic device. In addition, the account cloud can determine the age stage in which the watch user is currently located according to age information, for example, a birth date, of the watch user recorded in the watch account-related information, and add a corresponding age stage label in the watch user-related information. In this way, the first electronic device, for example, the watch, can query the age stage label of the user from the account cloud to determine the age stage of the user.

[0012] In a possible implementation of the first aspect, the first age stage includes a third age stage and a fourth age stage, the age intervals corresponding to the third age stage and the fourth age stage are continuous intervals, the age of the third age stage is higher than the age of the fourth age stage, and the method includes: if the age stage of the user belongs to the third age stage, displaying a second control, the second control being used to control the permission of the first electronic device to collect and report second data; in response to the operation of the second control by the user, allowing or prohibiting the first electronic device to collect and report the second data; and if the age stage of the user belongs to the fourth age stage, not displaying the second control.

[0013] For example, the third age group mentioned above refers to teenagers aged 14 to under 18. After configuring the watch's permissions according to the matching data management scheme corresponding to the teenager age group, the watch can display the second control mentioned above. At this time, the first electronic device, such as the watch, can allow the watch user to operate the second control. This second control can be, for example, a toggle control corresponding to "Join the User Experience Improvement Program," and is not limited here.

[0014] The fourth age group mentioned above refers to children under 14 years old. After configuring the watch's permissions according to the data management scheme corresponding to the child's age group, the second control mentioned above may not be displayed. In this case, the first electronic device, such as the watch, may not allow the watch user to operate the second control.

[0015] In one possible implementation of the first aspect above, the second data includes log data generated during the user's use of the first electronic device, and the log data includes either the user's behavior log or the error log of the first electronic device.

[0016] In one possible implementation of the first aspect described above, the age intervals corresponding to the first and second age groups are continuous intervals, and the age in the first age group is higher than the age in the second age group; and,

[0017] The age group labels include: a first label corresponding to the first age group, a second label corresponding to the third age group, and a third label corresponding to the fourth age group.

[0018] For example, the first label mentioned above could be an adult stage label, the second label mentioned above could be a teenager stage label, and the third label mentioned above could be a child stage label.

[0019] In one possible implementation of the first aspect above, the first control is a switch control, and, in response to the user's operation on the first control, allowing or disabling the second electronic device to acquire the first data includes: allowing the second electronic device to acquire the first data in response to a first operation in which the user sets the state of the first control to an on state; and disabling the second electronic device to acquire the first data in response to a second operation in which the user sets the state of the first control to a off state.

[0020] In one possible implementation of the first aspect above, in response to a user's operation on the second control, allowing or disabling the first electronic device to collect and report second data includes: in response to a third operation where the user sets the state of the second control to an on state, allowing the first electronic device to collect and report second data; and in response to a fourth operation where the user sets the state of the second control to a off state, disabling the first electronic device to collect and report second data.

[0021] In a possible implementation of the first aspect, the first control includes any of the following: a control for synchronizing location information of the first electronic device with the second cloud server; a control for synchronizing motion information recorded by the first electronic device with the second cloud server; a control for synchronizing a contact list stored on the first electronic device with the second cloud server; a control for synchronizing photo album data of the first electronic device with the second cloud server; a control for synchronizing a short message from an unknown person received by the first electronic device with the second cloud server; and a control for controlling whether the first electronic device is allowed to automatically answer a call request.

[0022] The second cloud server can be a child cloud, for example. The watch and the mobile phone can establish a communication connection with the child cloud, respectively.

[0023] In a possible implementation of the first aspect, the first data includes any of the following data collected or stored by the first electronic device: location information, motion record, contact list, photo album data, and short message from an unknown person.

[0024] In a second aspect, the present application provides a data management method applied to a second electronic device, the second electronic device being configured to manage a first electronic device. The method includes the following steps: confirming that the first electronic device displays a first control and the second electronic device does not display the first control, wherein the first control is configured to control the second electronic device's permission to obtain first data; confirming that the first electronic device does not display the first control and the second electronic device displays the first control; and in response to a second user's operation of setting the state of the first control to an open state, the second electronic device obtains the first data of the first electronic device.

[0025] That is, the first electronic device and the second electronic device can mutually display the control permission they have based on the corresponding data management scheme.

[0026] In a possible implementation of the second aspect, the method further includes the following steps: confirming that the first electronic device displays a second control and the second electronic device does not display the second control, wherein the second control is configured to control the first electronic device's permission to collect and report second data; and confirming that the first electronic device does not display the second control and the second electronic device displays the second control.

[0027] In a third aspect, the present application provides a data management system, comprising a first electronic device, a second electronic device, a first cloud server and a second cloud server, wherein the first electronic device and the second electronic device respectively establish a first communication connection with the first cloud server; the first electronic device and the second electronic device respectively establish a second communication connection with the second cloud server, and the first electronic device is configured to perform the data management method provided in the first aspect and various possible implementations of the first aspect based on the first communication connection and the second communication connection; the second electronic device is configured to perform the data management method provided in the second aspect and various possible implementations of the first aspect based on the first communication connection and the second communication connection.

[0028] In a fourth aspect, the present application provides an electronic device, comprising: one or more processors; one or more memories; and one or more programs stored in the one or more memories and configured to, working with the one or more processors, cause the electronic device to perform the data management method provided in the first aspect, the second aspect and various possible implementations.

[0029] In a fifth aspect, the present application provides a computer readable medium, wherein the readable medium stores instructions, and the instructions, when executed on a computer, cause the computer to perform the data management method provided in the first aspect, the second aspect and various possible implementations. BRIEF DESCRIPTION OF DRAWINGS

[0030] Figure 1 Fig. 1 shows an application scenario of a data management method provided by an embodiment of the present application.

[0031] Figure 2 Fig. 2 shows an implementation principle of a data management method provided by an embodiment of the present application.

[0032] Figure 3 Fig. 3 shows an interactive implementation flow of a data management method provided by an embodiment of the present application.

[0033] Figure 4 Fig. 4 shows a related interface change of collecting age information of a watch user in a process of newly creating a watch account provided by an embodiment of the present application.

[0034] Figure 5 Fig. 5 shows an interface of perfecting watch user information provided by an embodiment of the present application.

[0035] Figure 6A Fig. 6 shows a privacy center interface corresponding to a data management scheme A displayed by a watch after setting a watch end permission provided by an embodiment of the present application.

[0036] Figure 6BFig. 8 shows a privacy center interface corresponding to the data management scheme B displayed by the watch after setting the watch end permission according to an embodiment of the present application.

[0037] Figure 6C Fig. 9 shows an interface corresponding to the data management scheme C displayed by the watch after setting the watch end permission according to an embodiment of the present application.

[0038] Figure 7A Fig. 10 shows a privacy center interface corresponding to the data management scheme A displayed by the watch after setting the mobile phone end permission according to an embodiment of the present application.

[0039] Figure 7B Fig. 11 shows a privacy center interface corresponding to the data management scheme B displayed by the watch after setting the mobile phone end permission according to an embodiment of the present application.

[0040] Figure 7C Fig. 12 shows a privacy center interface corresponding to the data management scheme C displayed by the watch after setting the mobile phone end permission according to an embodiment of the present application.

[0041] Figure 8 Fig. 13 shows an interaction implementation flow of another data management method according to an embodiment of the present application.

[0042] Figure 9 Fig. 14 shows a growth notification interface change displayed by the watch according to an embodiment of the present application when detecting that the watch user enters the youth stage or the adult stage.

[0043] Figure 10A Fig. 15 shows a related interface change of the mobile phone displaying a privacy change notification according to an embodiment of the present application.

[0044] Figure 10B Fig. 16 shows a related interface change of the watch displaying a privacy change notification according to an embodiment of the present application.

[0045] Figure 11 Fig. 17 shows an architecture of a data management system for implementing the above data management method according to an embodiment of the present application.

[0046] Figure 12 Fig. 18 shows an implementation flow of a data management method according to an embodiment of the present application.

[0047] Figure 13 Fig. 19 shows a structure of an electronic device according to an embodiment of the present application.

[0048] Figure 14 Fig. 20 shows a software system structure block diagram of a mobile phone 100 according to an embodiment of the present application. DETAILED DESCRIPTION

[0049] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described in detail below with the reference to the accompanying drawings and specific embodiments.

[0050] Figure 1 According to the embodiments of the present application, an application scenario diagram of a data management method is shown.

[0051] As shown in Figure 1 The scenario includes a mobile phone 100 and a watch 200. The watch 200 can be a smart watch for children, and the mobile phone 100 can be installed with an APP for managing the watch 200, such as a smart care application 101.

[0052] When the watch 200 is used for the first time, the watch 200 can be bound to a mobile phone account through the mobile phone 100, and a watch account needs to be newly created or logged in for the watch 200, so as to use the full functions of the watch 200. The full functions refer to all the functions supported by the watch 200. The mobile phone user who logs in the mobile phone account on the mobile phone 100 to use the smart care application 101 can be a parent user, and the watch user who logs in the watch account on the watch 200 to use the full functions of the watch 200 can be a child user. The mobile phone account information and the watch account information can be synchronously uploaded to an account cloud 300a. At the same time, the mobile phone 100 and the watch 200 can also respectively establish a communication connection with a child cloud 300b for managing child-related data. For example, the smart care application 101 running on the mobile phone 100 can access the child cloud 300b through Wi-Fi or a cellular data network supported by a SIM card of the mobile phone; the watch 200 can access the child cloud 300b through Wi-Fi or a cellular data network supported by a SIM card of the watch. In this way, the mobile phone 100 can view, share or operate to turn on or off the data or related data on the watch 200 based on authorization.

[0053] When the user of the watch 200 grows up to the next age stage, for example, the user grows up from the current child stage to the adolescent stage, the user can wish to manage part of the personal data on the watch 200 by himself / herself, or to operate to turn on or off the switches of the corresponding functions on the watch 200, etc. At this time, the data control authority of the mobile phone 100 on the watch 200 and the control authority of the watch 200 on its own data need to be adaptively adjusted.

[0054] As described above, the current data management scheme for managing the data on the watch 200 described above cannot meet the data management needs of users in different age stages.

[0055] To address the aforementioned problems, this application provides a data management method. Specifically, this method pre-sets data management schemes tailored to different age groups based on their management capabilities and needs regarding data on wearable devices such as watches. For example, refer to... Figure 2 As shown, for users under 14 years old, data management solution A can be used. Solution A can preset mobile device permissions including control over privacy data on the watch, control over the collection and reporting of user behavior logs and error logs by authorized watches, and control over whether to enable certain data synchronization switches, etc., while preset watch device permissions do not include control over the above-mentioned content. For users aged 14 to 18, data management solution B can be used. Solution B can preset mobile device permissions including control over certain data synchronization switches on the watch, and preset watch device permissions including control over privacy data on the watch and control over the collection and reporting of user behavior logs and error logs by authorized watches, etc. For users aged 18 and above, data management solution C can be used. Solution C can preset watch device permissions including control over the aforementioned privacy data, control over the collection and reporting of user behavior logs and error logs by authorized watches, and control over whether to enable certain data synchronization switches, while preset mobile device permissions do not include control over the above-mentioned content.

[0056] The switch for collecting user behavior logs and error logs during watch usage can be simply referred to as... Figure 2 The "authorization switch" shown could be, for example, the switch corresponding to "join the user experience improvement program". The aforementioned behavior log could record data such as the frequency and duration of user usage of certain watch functions, while the error log could record data such as the time and type of functional malfunctions that occurred during watch operation. No restrictions are imposed here.

[0057] In this way, when a wearable device such as a watch is used for the first time, the user's age information can be obtained, and a data management solution corresponding to the user's age group can be matched to meet the data management needs of users of different ages. Furthermore, as the watch is used by the same user for an extended period, it can detect changes in the user's age group by polling the account cloud. When it detects that the user has reached a new age group, the watch can proactively match a data management solution corresponding to that age group, thus meeting the user's changing data management needs as they grow older.

[0058] It can be understood that in other embodiments, the ages for identifying the child stage, the teenager stage and the adult stage, such as 14 years old and 18 years old, can also be other preset ages, which are not limited herein.

[0059] It can be understood that, in view of the connection between the watch and the mobile phone and the authorization relationship that the mobile phone manages the relevant data on the watch, Figure 2 The mobile phone side permission shown can also be referred to as a management side permission, which can also be a control permission possessed by an intelligent care application (APP) installed on the mobile phone. Correspondingly, Figure 2 The watch side permission shown can also be referred to as a managed side permission. The managed side permission can correspond to the permission of the user of the watch to directly operate and manage the relevant data on the watch, such as operation access, authorization of other administrators to view private data on the watch, authorization to collect watch data of behavior logs and error logs in the process of using the watch by the user, and management of the state of some data synchronization switches on the watch, which are not limited herein.

[0060] In other embodiments, the data management scheme provided in the present application can also include more or less data management schemes corresponding to different age groups, and the authorization permissions of the mobile phone side or the watch side to manage the corresponding data in each data management scheme can also adopt other reasonable allocation manners, which are not limited herein. Figure 2 The data management scheme shown can also include more or less data management schemes corresponding to different age groups, and the authorization permissions of the mobile phone side or the watch side to manage the corresponding data in each data management scheme can also adopt other reasonable allocation manners, which are not limited herein.

[0061] It can be understood that the private data on the watch and other wearable devices described above can include but is not limited to location data, motion data, address book data, album data and short message data collected or recorded by the watch. The data synchronization switches described above can be corresponding switches for obtaining or viewing the private data, such as a watch location switch, a motion recording switch, an address book switch, an album switch and a stranger short message switch. The switch control permission for authorizing the watch to collect and report behavior logs and error logs in the process of using the watch by the user can be corresponding switch control permissions for a watch user experience improvement plan for the watch and a user experience improvement plan for other wearable devices, which are not limited herein.

[0062] It can be understood that the wearable devices applicable to the data management scheme provided in the present application can include but are not limited to smart watches, smart bracelets, smart glasses, wired earphones, wireless earphones (for example, TWS Bluetooth earphones, neck-hung Bluetooth earphones, head-mounted Bluetooth earphones), smart ankle bracelets, smart rings, smart necklaces, augmented reality (AR) devices, virtual reality (VR) devices and the like, and the specific form of the wearable device is not specially limited herein.

[0063] The mobile terminal for managing data on a wearable device such as a watch, to which the data management scheme provided in the present application is applicable, can include but is not limited to a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a netbook, and a smart television, a server, an in-vehicle device, and other electronic devices embedded or coupled with one or more processors and capable of accessing a network.

[0064] As an example, the following continues to take the watch 200 as the managed device and the mobile phone 100 as the management device. The specific implementation process of the data management scheme provided in the present application is specifically described.

[0065] It can be understood that, in the application scenarios shown above, Figure 1 In the application scenarios shown above, the watch 200 in the embodiments of the present application can be a children's watch customized for the growth of children. In other application scenarios, the watch 200 in the embodiments of the present application can also be a smart watch or the like capable of supporting replacement of watch cases to adapt to users of different age groups. This is not limited herein.

[0066] It should be further stated that the steps in the methods and processes in the embodiments of the present application are numbered for ease of reference, rather than to limit the sequence, and if there is a sequence between the steps, the written description shall prevail.

[0067] Based on the application scenarios shown above, Figure 1 Based on the application scenarios shown above, Figure 3 An interactive flow diagram for implementing the data management method provided in the embodiments of the present application is shown.

[0068] As shown in Figure 3 The interactive flow mainly describes the specific implementation process of matching the data management scheme suitable for the age group for the watch user when the watch 200 is first used. The interactive flow mainly involves the interaction between the mobile phone 100, the watch 200, the account cloud 300a, and the children's cloud 300b. In other embodiments, in order to distinguish the description, the above-mentioned account cloud 300a can also be described as a first cloud server, and the above-mentioned children's cloud 300b can also be described as a second cloud server.

[0069] Specifically, Figure 3 The interactive flow shown in

[0070] 301: The mobile phone 100 logs in the mobile phone account.

[0071] Exemplarily, the mobile phone 100 can run an application capable of managing the watch, such as a smart care application, in response to a user operation. Further, the user can operate to log in a mobile phone account on a corresponding login interface of the smart care application, so as to establish a communication connection between the mobile phone 100 and the account cloud 300a. It can be understood that the mobile phone 100 can prompt the user to log in the mobile phone account when the smart care application is run for the first time, and a corresponding prompt interface can refer to an existing mobile phone account login interface, which will not be described herein.

[0072] 302: The mobile phone 100 detects a user operation of binding the watch, and displays a corresponding binding operation interface.

[0073] Exemplarily, the user can operate to bind the watch on a relevant interface of the smart care application displayed by the mobile phone 100. After detecting a user operation of indicating to bind the watch, the mobile phone 100 can display a relevant interface for verifying watch information to be bound, such as a scanning page. The scanning page can be used to scan a device identification code displayed on the watch 200 to be bound. The device identification code can be a two-dimensional code, a bar code, or the like containing device identification information, which is not limited herein.

[0074] For example, the user can run the smart care application by clicking an icon of the smart care application on a desktop of the mobile phone 100. Further, the user can operate to bind the watch 200 on a corresponding interface of the smart care application displayed by the mobile phone 100. For example, the user can operate to open a scanning page on the corresponding interface of the smart care application, and hold the mobile phone 100 to scan a device identification code displayed on the watch 200, so as to obtain device identification information of the watch 200. By using the device identification information, the mobile phone 100 can request to bind with the watch 200 indicated by the device identification information through the account cloud. The specific binding process can refer to steps 304 to 309 described below, which will not be described herein.

[0075] It can be understood that the smart care application and other applications capable of managing the watch running on the mobile phone 100 can provide multiple binding modes for the user to operate, which are not limited herein.

[0076] 303: The mobile phone 100 receives watch account information input by the user, and logs in a watch account for the watch.

[0077] Exemplarily, the user can operate to input the watch account information on the interface displayed by the mobile phone 100 for prompting to log in the watch account. Correspondingly, the mobile phone 100 can log in the watch account for the watch 200 to be connected when receiving the watch account information input by the user. The watch account is different from the mobile phone account logged in by the mobile phone 100 in the step 301, and the watch account can be a device account logged in on the watch 200, and the mobile phone account can be another device account logged in on the mobile phone 100 or an account for logging in the smart care application. The watch account information can include the account name set for the watch user, the mobile phone number specified for verification when the account is newly created, the login password set correspondingly, the age information of the watch user, etc., which are not limited herein.

[0078] It can be understood that when the mobile phone 100 is initially bound with the watch 200, or when the watch 200 is first used, the mobile phone account logged in by the smart care application on the mobile phone 100 can be a newly created / watch logged-in watch account for the watch 200 to be bound. The watch account can be an account registered based on the SIM card installed on the watch 200, or an account registered through an email, which are not limited herein. Taking the watch account registered by the SIM card as an example, if the SIM card installed on the watch 200 is not registered with the watch account, the mobile phone account can be a newly created watch account for the watch 200. If the SIM card installed on the watch 200 is registered with the watch account, the mobile phone account can be the watch account logged in by the watch 200.

[0079] Reference Figure 4 As shown, the user can select to newly create the watch account 411 on the interface 410 displayed by the mobile phone 100 for logging in the watch account. During the creation, the mobile phone 100 can display the age information collection interface 420 to collect the age information input by the user, for example Figure 4 the birth date "2018-08-18" as shown. Further, the age information can be recorded in the related information of the newly created watch account as a basis for determining the age of the user subsequently.

[0080] It can be understood that in some embodiments, if the age information input by the user indicates that the watch user has reached 14 years old and is no longer in the child stage when the watch account is newly created, a corresponding prompt interface can be displayed to inform the user that other accounts can be created.

[0081] It can be understood that if the age of the watch user is less than 14 years old, in the child stage, the newly created watch account can also be displayed as a child account. The account cloud 300a can correspondingly manage the related information of the child account under the mobile phone account corresponding to the login of the mobile phone 100, for example, the related information of the child account is associated and stored in the related information of the watch account. At this time, the mobile phone account can be a parent account. If the user is 14 years old or older, no longer in the child stage, the user can also select other accounts created by the user to continue to create to log in to the watch 200. But when the account is synchronized to the account cloud 300a for storage, the account cloud 300a can store the related information of the account independently, and no longer store it in association with the related information of the mobile phone account. And after the other account created by the above process logs in to the watch 200, the watch 200 can continue to establish a binding relationship with the mobile phone 100. At this time, the watch 200 can still match the above data management scheme B or data management scheme C for the watch user based on the age information that the user is 14 years old or older.

[0082] With reference to the foregoing Figure 4 As shown, the user can also select to log in to the existing account 412 in the interface 410 of the mobile phone 100 displaying the watch account login, and log in to the registered watch account for the watch 200. Further, in the subsequent steps, the related information of the logged-in existing account can provide the recorded age information of the watch user, which will not be repeated here.

[0083] 304: The mobile phone 100 sends the watch account information to the account cloud 300a.

[0084] Exemplarily, after receiving the watch account information input by the user, the mobile phone 100 can send the corresponding information to the account cloud 300a for account information verification.

[0085] 305: The account cloud 300a confirms that the watch account login is successful.

[0086] Exemplarily, the account cloud 300a can check whether the received watch account information matches the registered watch account information, and then confirm whether the watch account is logged in successfully. It can be understood that in the process of creating a new watch account, the account cloud 300a can create a new account for the newly created watch account to record the account name, mobile phone number, password and other information input by the newly created watch account. Among them, the account cloud 300a can receive the newly created watch account information, and according to the age information input by the user, such as the date of birth, judge the age stage that the watch user is currently in. In other embodiments, after the user completes the creation of the watch account by operating the mobile phone 100, the user can also operate to perfect the personal information of the watch user, at this time the account cloud 300a can judge the age stage that the watch user is currently in according to the age information set by the user when perfecting the information, such as the birthday. After the account cloud 300a judges the corresponding age stage, it can add an age stage tag to the corresponding watch account information to indicate the age stage that the corresponding watch user is in. The rule of the account cloud 300a for judging the age stage that the user is in according to the user's age information can be preset on the account cloud 300a. In the process of the growth of the watch user, the account cloud 300a can update and maintain the age stage that the user is currently in for the watch 200 to query.

[0087] For example, with reference to the above Figure 2 If the age of the watch user is 12 years old, it can be determined that the watch user is in the child stage (<14 years old). If the age of the watch user is 15 years old, it can be determined that the watch user is in the adolescent stage (14 to 18 years old). If the age of the watch user is 19 years old, it can be determined that the watch user is in the adult stage (≥18 years old). This is not limited.

[0088] It can be understood that in the process of the growth of the watch user, the account cloud 300a can continuously maintain the age stage that the watch user is in. When the age stage of the watch user changes, the watch 200 can detect the corresponding age stage change when querying the age stage that the watch user is in from the account cloud 300a.

[0089] 306: The watch 200 polls and obtains the binding request from the account cloud 300a.

[0090] Exemplarily, the watch 200 can start polling the account cloud server when the device identification code is displayed to confirm with the account cloud 300a whether there is a mobile phone scanning code request to bind the watch. If so, the watch 200 can obtain the corresponding binding request. Further, the watch 200 can poll the account cloud 300a whether the watch 200 and the mobile phone 100 are successfully bound in the process of the mobile phone 100 logging in the watch account. When the account cloud 300a feeds back the message of successful binding, the watch 200 can end the polling.

[0091] The polling process can be triggered based on a timing condition, which can be preset to poll every 200 ms, etc. The polling process can also be triggered based on a corresponding broadcast message received from the account cloud 300a, which is not limited herein. It can be understood that if the account cloud 300a does not feedback a binding success message, the watch 200 can gradually extend the polling interval, which is not limited herein.

[0092] 307: The watch 200 confirms the binding of the mobile phone 100.

[0093] Exemplarily, the watch 200 can display a corresponding confirmation interface when obtaining the binding request initiated by the mobile phone 100, and the user can perform a confirmation operation on the confirmation interface to complete the binding process of the watch 200 to the mobile phone 100. The binding process is, for example, a process in which the watch 200 binds the smart care application running on the mobile phone 100.

[0094] It can be understood that in other embodiments, the execution process of the above steps 301 to 307 can also be described as a process of establishing a communication connection between the mobile phone 100, the account cloud 300a, the child cloud 300b, and the watch 200. In the process of logging in the mobile phone account, the mobile phone 100 can establish a communication connection with the account cloud 300a. In the process of running the smart care application to bind the watch 200 and logging in the watch account, the watch 200 can establish a communication connection with the account cloud 300a, and the mobile phone 100 and the watch 200 can establish a communication connection with the child cloud 300b.

[0095] 308: The watch 200 synchronizes a notification message of the binding success to the child cloud 300b.

[0096] Exemplarily, after confirming the binding of the smart care application running on the mobile phone 100, the watch 200 can synchronize the notification message of the binding success to the child cloud 300b. For example, the watch 200 can synchronize a notification message of the binding success to the child cloud 300b.

[0097] 309: The mobile phone 100 polls and obtains the binding success message from the child cloud 300b.

[0098] Exemplarily, after the mobile phone 100 displays the corresponding binding operation interface in the above step 302, the mobile phone 100 can start polling the child cloud server to confirm whether the watch 200 confirms the binding of the smart care application. The polling process can also be understood as a process of confirming whether the smart care application running on the mobile phone 100 is successfully bound to the watch 200.

[0099] It can be understood that after obtaining the binding success message, the mobile phone 100 can display a corresponding prompt interface.

[0100] After the mobile phone 100 completes the binding of the watch account for the watch 200 in performing the above step 303, the mobile phone 100 can display a corresponding binding success interface to inform the user. After the binding is successful, the user can also operate the watch user information on the mobile phone 100, for example, select a "perfect watch user information" option on the binding success interface displayed on the mobile phone 100, and the like. Correspondingly, the mobile phone 100 can display a corresponding perfect information interface 510 on the mobile phone 100, as shown in FIG. 5. Figure 5 The user can set the birthday of the watch user on the interface 510, and the setting process can correct the age information that is not input or is input incorrectly when the account is newly created. In some embodiments, the user can also set the avatar, nickname, mobile phone number, gender, and weight, height, and the like of the watch user on the perfect information interface 510, which is not limited herein.

[0101] Correspondingly, when the watch 200 is bound with the smart care APP run by the mobile phone 100, the watch 200 can also display a corresponding binding success interface.

[0102] 310: The watch 200 queries the account cloud 300a to determine the age stage in which the watch user currently stays.

[0103] Exemplarily, the watch 200 can query the account cloud 300a to determine the age stage in which the watch user currently stays every time the watch 200 is charged. In other embodiments, the watch 200 can also periodically poll the account cloud 300a to determine the age stage in which the watch user currently stays.

[0104] 311: The watch 200 matches the data management scheme for the watch user, and sets the watch end permission correspondingly.

[0105] Exemplarily, continuing to refer to the above Figure 2 As shown in FIG. 6, when the watch 200 queries that the watch user stays in the child stage (<14 years old), the watch 200 can match the data management scheme A for the watch user, as shown in FIG. 6. Figure 2 The scheme A can preset the mobile end permission to include the control permission of the privacy data on the watch 200, the switch control permission of the authorized watch collecting and reporting the behavior log and error log of the user in using the watch, and some data synchronization switches. Meanwhile, the scheme A can preset the watch end permission to not include the control permission of the above aspects.

[0106] When the watch 200 queries that the watch user stays in the youth stage (14 to 18 years old), the watch 200 can match the data management scheme B for the watch user. The scheme B can preset the mobile end permission to only include the control permission of some data synchronization switches on the watch. Meanwhile, the scheme B can preset the watch end permission to include the switch control permission of the privacy data on the watch, the authorized watch collecting and reporting the behavior log and error log of the user in using the watch.

[0107] When Watch200 detects that the user is an adult (≥18 years old), it can be used to match data management solution C. Solution C can preset watch-side permissions including control over privacy data on the watch, control over the authorized watch to collect and report user behavior logs and error logs during watch use, and control over some data synchronization settings. However, Solution C can preset mobile phone-side permissions that do not include control over the above aspects.

[0108] After the Watch200 sets its own watch-side permissions according to the matched data management scheme, users can open the "Privacy Center" interface on the Watch200.

[0109] As an example, Figures 6A to 6C According to the embodiments of this application, the relevant interface diagrams of the watch 200 after setting watch terminal permissions according to different matching data management schemes are shown respectively.

[0110] like Figure 6A As shown in the example above, if watch 200 matches the data management solution A corresponding to the childhood stage for the watch user, then watch 200 can display the following in response to the user opening the "Privacy Center" interface: Figure 6A The privacy center interface 610 shown is shown. This interface 610 can display only content that does not involve children's user privacy data, the on / off control permissions for authorized watches to collect and report user behavior logs and error logs during watch use, and data synchronization switches, such as "User Agreement" and "Privacy Statement".

[0111] If the watch 200 is matched with data management solution B corresponding to the adolescent stage for the watch user, then the watch 200 can display the following in response to the user opening the relevant interface of the "Privacy Center": Figure 6B The privacy center interface shown is 620. (And...) Figure 6A Compared to the interface 610 shown, Figure 6B The privacy center interface 620 shown may display an authorization switch 741, which may display options such as "Join the Watch User Experience Improvement Program". In some embodiments, the interface 620 may also display a "Stop Using the Children's Watch" option 622, allowing teenagers to unbind the watch from their mobile phone 100 on the watch 200. In other embodiments, the interface 620 may also display a "Children's Watch Notification" option 623, allowing teenagers to view watch usage-related notifications on the watch 200, etc., which will not be elaborated here.

[0112] If the watch 200 matches the watch user to the data management scheme B corresponding to the adolescent stage, the watch 200 can display the privacy center interface 630 shown in Figure 6C as shown in response to the operation of the user opening the privacy center related interface. Compared with the interface 620 shown in Figure 6B as shown in Figure 6C The "data management" option 631 can be further displayed on the privacy center interface 630 shown in. After the user clicks the option 631, the watch 200 can correspondingly display the data management interface 640.

[0113] As shown in Figure 6C The data management interface 640 can display multiple data synchronization switches, such as the watch location switch 641, the motion record switch 642, the address book switch 643, the album switch 644, the stranger SMS switch 645, the automatic call answering switch 646, and the like.

[0114] It can be understood that in other embodiments, the watch 200 can also display other different styles of privacy center interfaces in response to user operations after setting the watch end permissions of itself according to the matched data management scheme, which is not limited here.

[0115] 312: The watch 200 synchronizes the matched data management scheme to the child cloud 300b.

[0116] Exemplarily, the watch 200 can synchronize the matched data management scheme to the child cloud 300b when setting the watch end permissions of itself according to the matched data management scheme.

[0117] 313: The mobile phone 100 requests the latest data management scheme from the child cloud 300b.

[0118] Exemplarily, the child cloud 300b stores the data management scheme synchronized by the watch 200 after receiving the scheme, and the mobile phone 100 can request the latest data management scheme from the child cloud 300b in response to the operation of the user opening the smart care application.

[0119] 314: The mobile phone 100 sets the mobile phone end permissions based on the obtained data management scheme.

[0120] Exemplarily, the watch 200 can synchronize the data management scheme matched for the watch user to the child cloud 300b. The mobile phone 100 can request the latest data management scheme from the child cloud 300b in response to the user displaying the related management interface of the bound watch 200, such as the device management interface of the smart care application. Further, the mobile phone 100 can refresh the display content on the corresponding device management interface according to the obtained latest data management scheme.

[0121] In some embodiments, after the smart watch 200 and the smart care application running on the mobile phone 100 are successfully paired, the user can operate the corresponding function controls on the relevant interface of the smart care application displayed on the mobile phone 100 to manage the data and / or applications on the watch 200. For example, the user can open the "Watch Settings" function on the relevant interface of the smart care application and click the "Privacy Center" option to make the mobile phone display the privacy center interface corresponding to the different data management schemes obtained above.

[0122] refer to Figure 7A As shown, if mobile phone 100 obtains data management scheme A, the mobile phone's permissions include the ability to control privacy data on watch 200, the ability to control the collection and reporting of user behavior logs and error logs during watch use by the authorized watch, and the ability to control some data synchronization switches. After setting the corresponding mobile phone permissions, refer to... Figure 7A As shown, users can enable or disable the switch 711 corresponding to "Join the Watch User Experience Improvement Program" on the Privacy Center interface 710 to authorize the watch to collect and report user behavior logs and error logs during watch use. Users can also click the "Data Management" option 712 on this interface 710 to display the corresponding data management interface 720 on the phone 100. All switches displayed on this interface 720, such as watch location 721, activity recording 722, contacts 723, photo album 724, and data synchronization switches such as stranger SMS 725 and allow automatic answering 726, can be enabled or disabled by the user.

[0123] refer to Figure 7B As shown, if mobile phone 100 obtains data management scheme B, the mobile phone permissions include the ability to control privacy data on watch 200, the ability to control the collection and reporting of user behavior logs and error logs during watch use by the authorized watch, and the ability to control some data synchronization switches. After setting the corresponding mobile phone permissions, the user can... Figure 7B Clicking the "Data Management" option 731 on the privacy center interface 730 will display the corresponding data management interface on the phone 100. This data management interface can be referenced from the above. Figure 7A As shown in the data management interface 720, all switches on this interface, such as those for watch location, activity records, contacts, photo album, and data synchronization (e.g., allowing stranger messages, allowing automatic call answering), can still be controlled by the mobile phone user. However, because data management scheme B disables the permission control on the mobile phone to collect and report user behavior logs and error logs during watch use, the switch control 732 corresponding to "Join the Watch User Experience Improvement Program" on the privacy center interface 730 displayed on the mobile phone 100 can be grayed out, indicating that user operation is not allowed.

[0124] If the mobile phone 100 acquires the data management scheme C, the mobile phone side can correspondingly close the switch control permission of the private data on the watch 200, the switch control permission of collecting and reporting the behavior log and the error log of the user using the watch by the watch, and the control permission of some data synchronization switches, that is, the permission of the mobile phone side is no control permission. After setting the permission of the mobile phone side, since the data management scheme C correspondingly closes the switch control permission of collecting and reporting the behavior log and the error log of the user using the watch by the watch in the permission of the mobile phone side, the switch control element corresponding to "join the watch user experience improvement plan" on the privacy center interface displayed by the mobile phone 100 can be in the grayed-out state as shown in the above Figure 7B In addition, the "data management" option 731 shown in the above Figure 7B may also be displayed in the grayed-out state. If the user clicks the grayed-out "data management" option, the data management interface correspondingly displayed by the mobile phone 100 can refer to the above Figure 7C . All the switches displayed on the data management interface 740, such as the watch position 741, the motion record 742, the address book 743, the album 744, the stranger message 745, the automatic call answering 746, and the data synchronization switches, can be displayed in the grayed-out state at this time, indicating that the operation is not allowed.

[0125] It can be understood that based on the interaction process of the above steps 301 to 314, when the watch 200 is used for the first time, based on the age information of the watch user recorded by the newly created / logged-in watch account, the data management scheme corresponding to the corresponding age group can be matched for the watch user to manage the permission of the mobile phone side and the permission of the watch side respectively. In this way, the watch 200 and the like can meet the data management needs of users of different age groups, and can adapt to the data management ability of users of different age groups to ensure the security of data or applications on the watch and the like.

[0126] It can be understood that in the process of the watch 200 being continuously used by the user, as the user grows up, when the watch user grows up to the next age group, the data management method provided by the present application can also adaptively update the data management scheme for the watch user. The specific implementation process of adaptively updating the data management scheme as the user grows up will be described in detail below with reference to the corresponding drawings.

[0127] Figure 8 According to an embodiment of the present application, another interaction flow diagram is shown, which mainly describes the specific implementation process of adaptively updating the data management scheme as the user grows up in the process of the watch 200 being continuously used by the user.

[0128] As Figure 8The interaction flow shown mainly involves interactions among the mobile phone 100, the watch 200, the account cloud 300a, and the child cloud 300b. In some embodiments, specifically, the mobile phone 100, the watch 200, the account cloud 300a, and the child cloud 300b implement the above-mentioned age-based data management scheme. Figure 3 After the interaction flow shown, the implementation of the above-mentioned age-based data management scheme can be continued. Figure 8 After the interaction flow shown, the implementation of the above-mentioned age-based data management scheme can be continued.

[0129] Specifically, Figure 8 The interaction flow shown can include the following steps:

[0130] 801: The watch 200 queries the account cloud 300a about the age stage in which the watch user is currently in.

[0131] Exemplarily, the watch 200 can also query the account cloud 300a about the age stage in which the watch user is currently in each time the watch 200 is charged, or query the account cloud 300a about the age stage in which the watch user is currently in by periodically polling the account cloud 300a. For details, reference can be made to the related description in the above-mentioned step 310, which will not be repeated here.

[0132] 802: The watch 200 detects that the age stage in which the watch user is in has changed to the next age stage.

[0133] Exemplarily, the watch 200 can compare the age stage in which the watch user is in based on the query with the age stage previously queried. If different, it indicates that the watch 200 detects that the age stage in which the watch user is in has changed to the next age stage.

[0134] For the foregoing example, in the growth process of the watch user, the watch user can experience age stage changes from the child stage to the adolescent stage, and from the adolescent stage to the adult stage. For example, when the watch user grows up from the child stage to 14 years old, the account cloud 300a can change the age stage in which the watch user is in to the next age stage, i.e., the adolescent stage. For another example, when the watch user grows up from the adolescent stage to 18 years old, the account cloud 300a can change the age stage in which the watch user is in to the next age stage, i.e., the adult stage.

[0135] Correspondingly, when the watch 200 queries the account cloud 300a about the age stage in which the watch user is in, the watch 200 can query the updated information on the account cloud 300a indicating that the watch user has entered the next age stage.

[0136] 803: The watch 200 displays a notification that the data management scheme is about to change, for confirmation by the watch user.

[0137] Exemplarily, the watch 200 can generate and display a data management scheme change notification according to the detected age stage change, i.e., the watch user grows into the next age stage, for the user to confirm whether to change the corresponding data management scheme. The data management scheme change notification can be in the form of prompting that the account information has changed, the privacy statement has changed, or the user agreement has changed, etc. It can be understood that the timing of the watch 200 displaying the above-mentioned change notification can be the first day when the watch user grows into the next age stage, or when the watch 200 first queries from the account cloud 300a that the age stage of the watch user has changed to the next age stage, which is not limited herein.

[0138] As an example, referring to FIG. 9, if the watch 200 detects that the watch user has entered the youth stage or the adult stage, the watch 200 can display a privacy center notification 910. The display manner of the notification 910 can be a message pop-up window, or a notification bar of the watch 200, which is not limited herein. The content of the privacy center notification 910 can be “Your account information has changed, please click to view details.”, etc. Figure 9

[0139] If the watch 200 detects that the watch user has entered the youth stage, the user clicks the content of the above-mentioned privacy center notification 910, and the watch 200 can further display a watch notification interface 920. The user clicks an “agree” control 921 on the watch notification interface 920, and the watch 200 can trigger the start of data management scheme change. The user clicks a “cancel” control 922 on the above-mentioned watch notification interface 920, and the data scheme change is not triggered. At this time, the watch 200 can display a corresponding notification interface to remind the user to unbind the watch 200 from the smart care application. Details are not repeated herein.

[0140] If the watch 200 detects that the watch user has entered the adult stage, the user clicks the content of the above-mentioned privacy center notification 910, and the watch 200 can display a data authorization interface 930. The content displayed on the interface 930 can be, for example, “Your account information has changed, do you agree to keep the data switch state set by the parent?” and “You can modify the switch state through “Settings” > “About Watch” > “Privacy Center” > “Data Management” in the future.”, etc. After reading the above-mentioned notification content, the user can click an “agree” control 931 to accept the switch state set by the user on the corresponding interface of the smart care application of the mobile phone 100. The user can also click a “cancel” control 932 on the above-mentioned data authorization interface 930 to reset the data synchronization switch state on the watch 200. The watch 200 detects that the user clicks the “cancel” control 932, and can display a corresponding notification interface to remind the user to unbind the watch 200 from the smart care application, which is not repeated herein. Figure 9 ​The data management interface 940 is shown. On the interface 940, the user can check the switch state of each data synchronization switch, for example, check the switch corresponding to "exercise record" and "stranger message" to indicate that the switch is set to the on state. After completing the settings, the user can click the "complete" control 941 to close the data management interface 940.

[0141] In other embodiments, the user can also click Figure 9 The "all clear" control 911 on the privacy center notification 910 can be ignored. It can be understood that after the user ignores the above privacy center notification, the watch 200 can display the content of the above privacy center notification 910 again when it is next charged or used, to remind the user to confirm. In other embodiments, after the user ignores the above privacy center notification, the watch 200 can also directly display Figure 9 The watch notification interface 920 or the data authorization interface 930 shown, to guide the user to trigger the data management scheme change caused by the change in age.

[0142] In some embodiments, the watch 200 can notify the smart care application running on the mobile phone 100 through the child cloud 300b when generating the corresponding data management scheme change notification. The mobile phone 100 can also display a corresponding notification interface when receiving the corresponding notification. The notification interface can display, for example, "Dear XXX parent, you are welcome! Your child XXX will soon be one year old, and can use more functions and services through the watch account, including self-agree or revoke related data changes, etc." or "Dear XXX parent, you are welcome! Your child XXX will soon be an adult, and can manage the watch account and related data, including watch location, exercise health, address book, photo album, and stranger message." to remind the mobile phone user to know the change process caused by the growth of the watch user to the corresponding age, which is not limited here.

[0143] 804: The watch 200 detects the user's confirmation of the change operation.

[0144] Exemplarily, with reference to the above Figure 9 For example, the watch 200 detects that the user clicks the "agree" control on the watch notification interface 920 or the data authorization interface 930, indicating that the user confirms the change, that is, the operation of confirming the change can be detected. At this time, the watch 200 can continue to perform the following step 805 to match the data management scheme to be changed for the watch user.

[0145] 805: The watch 200 matches the data management scheme corresponding to the next age for the watch user.

[0146] Exemplarily, the watch 200 can match the data management scheme according to the current changed age stage of the watch user, i.e., the next age stage. For example, if the next age stage is the teenager stage, the watch user can be matched with the data management scheme B; if the next age stage is the adult stage, the watch user can be matched with the data management scheme C, and so on.

[0147] The specific matching process can refer to the related description in step 311 described above, and will not be repeated here.

[0148] 806: The watch 200 sets the watch end permission according to the data management scheme corresponding to the next age stage.

[0149] Specifically, the setting of the watch end permission and the related interface displayed by the watch 200 according to the matched data management scheme can refer to the related description in step 311 described above, and will not be repeated here.

[0150] 807: The watch 200 synchronizes the data management scheme corresponding to the next age stage to the child cloud 300b.

[0151] 808: The mobile phone 100 requests the latest data management scheme from the child cloud 300b.

[0152] 809: The mobile phone 100 sets the mobile phone end permission based on the obtained data management scheme.

[0153] The specific implementation process of steps 807 to 809 described above can refer to the related description in steps 312 to 314 described above, and the related interface displayed by the mobile phone 100 after setting the mobile phone end permission can also refer to the related description in step 314 described above, and will not be repeated here.

[0154] 810: The mobile phone 100 receives the operation of the user indicating to display the related interface for managing the watch.

[0155] Exemplarily, the mobile phone 100 can run the smart care application in response to the operation of the user opening the smart care application, and display the related management interface provided by the smart care application for managing the watch 200. At this time, the mobile phone 100 can trigger the execution process of steps 811 to 818 described below when displaying the running smart care application.

[0156] 811: The mobile phone 100 requests the child cloud 300b to obtain the age information of the watch user.

[0157] Exemplarily, the mobile phone 100 can request the age information of the watch user from the child cloud 300b. It can be understood that, in order to facilitate the management of the related information of the watch account, the watch account information stored on the account cloud 300b can only be accessed, inquired and acquired by the watch 200 or the child cloud 300b authorized by the watch 200. When the mobile phone 100 needs to acquire the age information of the watch user, the child cloud 300b can request the age information from the account cloud 300a.

[0158] 812: The child cloud 300b acquires the age information of the watch user based on the authorization token provided by the watch.

[0159] Exemplarily, the child cloud 300b can access the account cloud 300a to acquire the age information of the watch user based on the authorization token, such as a resource token (RT), acquired in the process of interacting with the watch 200.

[0160] In other embodiments, after the watch 200 establishes a binding relationship with the smart care application on the mobile phone 100, the watch 200 can also provide the above authorization token to the mobile phone 100, or the account cloud 300a can also provide an interface for the mobile phone 100 to access the watch account information, so that the mobile phone 100 can acquire the age information of the watch user at any time. The present application does not limit this.

[0161] 813: The child cloud 300b sends the acquired age information to the mobile phone 100.

[0162] Exemplarily, after obtaining the age information of the watch user, the child cloud 300b can return the age information to the mobile phone 100.

[0163] 814: The mobile phone 100 updates the age information of the watch user and determines whether the notification condition is met.

[0164] If the determination result is yes, the following step 815 can be executed to notify the user to confirm whether the age is correct.

[0165] If the determination result is no, the above step 810 can be returned.

[0166] Exemplarily, the mobile phone 100 can update the locally recorded age information based on the received age information of the watch user, and determine whether the age of the watch user satisfies a preset notification condition. The notification condition can be, for example, that the watch user is within a preset number of days before changing to a next age stage. For example, the mobile phone 100 can perform the following step 815 to perform notification when the age of the watch user reaches 14 years old within 30 days, i.e., the watch user is within 30 days before changing to a youth stage. The preset number of days can be 30 days, or 28 days, 15 days, or other reasonable preset values, which are not limited herein.

[0167] 815: The mobile phone 100 notifies the user to confirm whether the age is correct.

[0168] Exemplarily, the mobile phone 100 can display a corresponding notification interface after confirming that the received age information of the watch user satisfies the notification condition, for example, display an interface for reminding the user to check the age information or other interfaces for notifying the user to confirm whether the age is correct. Details are not described herein.

[0169] 816: The mobile phone 100 detects an operation of modifying the age of the watch user.

[0170] 817: The mobile phone 100 synchronizes the modified age information to the account cloud 300a.

[0171] 818: The account cloud 300a updates the age stage in which the watch user is currently located.

[0172] Exemplarily, the account cloud 300a can update the age information stored in the cloud space after receiving the modified age information of the watch user input by the user through the smart care application on the mobile phone 100. For example, the account cloud 300a replaces the previously stored birthday with the modified birthday of the watch user. Further, the account cloud 300a can determine the age stage in which the user is currently located based on the modified age information, and update the age stage label marked for the watch user.

[0173] It can be understood that in the embodiments of the present application, the management of the privacy data mainly includes changes of the user agreement and the privacy declaration. The user can enter the privacy center through the watch 200 or the mobile phone 100, and view the user agreement and the privacy declaration, which are not described herein. When the user agreement or the privacy declaration is changed, the user can be notified through the related interface of the watch 200 or the mobile phone 100. Different data management schemes can have different notification manners and notification contents on the watch 200 or the mobile phone 100. The embodiments of the present application can set different privacy center entrances on the watch side and the mobile phone side, so as to separate the user agreement and the privacy declaration of the watch 200 from the smart care application on the mobile phone 100, and authorize the user agreement and the privacy declaration of the watch 300 when the watch 200 is bound. Details are as follows:

[0174] Watch side: When the smart care application on the phone 100 binds the watch, the watch user agreement and privacy declaration can be authorized, and the change notification can be supported. The privacy center entry can be added on the watch 200 to view and manage the watch user agreement and privacy declaration. Meanwhile, the watch 200 can support the independently controlled data collection control, including the watch location, motion data, address book, photo album, and stranger SMS data synchronization switch. In different data authorization schemes, the on / off state of the above data synchronization switch can not be allowed or allowed to be set on the watch side. For details, refer to the related description in step 311 above.

[0175] Phone side: The privacy center entry can be added on the corresponding interface of the smart care application to view and manage the watch user agreement and privacy declaration. Meanwhile, the smart care application of the phone 100 can also support the independently controlled data collection switch, including the watch location, motion data, address book, photo album, and stranger SMS data synchronization switch. In different data authorization schemes, the on / off state of the above data synchronization switch can not be allowed or allowed to be set on the phone side. For details, refer to the related description in step 314 above. This will not be repeated here.

[0176] It can be understood that when the user agreement or the privacy declaration is changed, the child cloud 300b can notify the watch 200 and the phone 100 based on the communication connection between them. When the user confirms the above change through the phone 100 or the watch 200, the corresponding stored user agreement or privacy declaration related data flag information on the child cloud 300b can be changed accordingly. In this way, when the age information of the watch user changes or grows to the next age segment, the child cloud 300b can update the user agreement or privacy declaration after the user agrees to the change to the phone 100 or the watch 200 based on the change of the above flag information.

[0177] For different data authorization schemes, for example, when the age of the watch user is less than 14 years old, refer to the above Figure 2 It is shown that the child cloud 300b can notify the phone 100 of the above change, and the phone 100 displays the corresponding interface to notify the user. The notification interface can refer to Figure 10A It is shown.

[0178] As Figure 10AAs shown, after receiving the privacy change notification message from the child cloud 300b, the mobile phone 100 can display the change notification 1011 on the daemon interface 1010 of the running smart care application. At this time, the user can click the change details, watch user agreement, statement on watch service and privacy, etc. in the change notification 1011 to view the detailed content. After the user reviews the changed related content, the user can click the "agree" control 1012 on the change notification 1011 to agree to the change of the related content. In some embodiments, the user can also click the "cancel" control 1013 on the change notification 1011 to refuse the change, at which time the mobile phone 100 can display a prompt box 1021 on the daemon interface 1020.

[0179] With continued reference to Figure 10A As shown, the prompt box 1021 can display, for example, "Do not agree to update the change, you will not be able to view and manage the watch information of XXXX. If you confirm, please first unbind the watch to avoid affecting the normal use of the watch" and the like to guide the user to click the "agree" control 1012 in the change notification 1011. In some embodiments, the user can click the "view change" control 1022 on the daemon interface 1020 to view the change content related to the "change details", "watch user agreement", "statement on watch service and privacy" and the like, which will not be described here. The user can also click the "unwind watch" control 1023, at which time the mobile phone 100 can have a related interface of the unbinding control for the user to operate to unbind the smart care application running on the mobile phone 100 from the watch 200.

[0180] When the age of the watch user reaches or exceeds 14 years old, the child cloud 300b can notify the watch 200 of the change of the privacy, and the watch 200 can display a corresponding interface to notify the user. The notification interface can refer to Figure 2 As shown, the child cloud 300b can notify the watch 200 of the change of the privacy, and the watch 200 can display a corresponding interface to notify the user. The notification interface can refer to Figure 10B As shown.

[0181] As shown Figure 10B As shown, after receiving the privacy change notification message from the child cloud 300b, the watch 200 can display a privacy center notification 1040. The content of the notification 1040 can be "We have updated the privacy statement and user agreement to provide better service" and the like. The user can click the content of the notification 1040 to view the detailed notification. At this time, the watch 200 can display the content related to "change details", "watch user agreement", "statement on watch service and privacy" in response to the user operation. After the user reviews the changed related content, the user can operate to agree or refuse the change of the related content. If the user refuses the change of the related content, the watch 200 can further display a related notification prompting the user to unbind the watch, which will not be described here.

[0182] Figure 11 According to an embodiment of the present application, a schematic diagram of a data management system for implementing the above data management method is shown.

[0183] As shown in Figure 11 , the data management system 1100 can include an account cloud 300a, a watch 200, a child cloud 300b, and a mobile phone 100, wherein the smart care application 101 can be run on the mobile phone 100.

[0184] Specifically, the mobile phone user can operate to open the smart care application 101, and operate to bind the watch 200. During the binding process, the smart care application 101 can create a new watch account or log in to the watch account for the watch 200, and the corresponding watch account information and login status can be synchronized to the account cloud 300a. The account cloud 300a can determine the age group of the watch user by using the age information in the watch account information, and can add an age group label to the watch user or the corresponding watch account information.

[0185] The watch 200 can access the account cloud 300a through Wi-Fi or a cellular data network supported by the watch SIM card, and can obtain the age group of the watch user recorded by the watch account, and match a data management scheme corresponding to the age group of the watch user.

[0186] The system of the watch 200 can install a toolkit 201, a settings application 202, a data synchronization switch 203, etc. Among them, the watch 200 can transmit an authorization token to the child cloud 300b through the account toolkit 201, so that the child cloud 300b queries the age information of the watch user recorded by the watch account from the account cloud 300a. The watch 200 can query the age group of the watch user from the account cloud 300a through the privacy center in the settings application 202, synchronize the data synchronization switch state between the watch 200 and the child cloud 300b, and push growth notifications to the child cloud 300b. Among them, the synchronization of the data synchronization switch state between the watch 200 and the child cloud 300b can be completed when the watch 200 and the smart care application 101 are bound or when a change notification is received. The change notification can be a notification corresponding to the change of the switch state of the data synchronization switch, etc. The above growth notification can be the notification pushed by the child cloud 300b to the smart care application on the mobile phone 100 in the example in the above step 803, etc., which is not limited here.

[0187] The settings application 202 of the watch 200 can also display the corresponding interface in response to the operation of the watch user viewing the privacy statement or the user agreement. For details, please refer to the related description in the above Figures 6A to 6C , which will not be repeated here.

[0188] Correspondingly, the watch 200 can also include a database for synchronizing the personal privacy data of the watch user collected on the watch 200. The privacy center of the watch 200 can synchronize the personal privacy data of the watch user collected to the database, and the state of the data synchronization switch set by the user on the watch 200, etc. The database can be default transmittable to the value corresponding to the data switch state on the watch 200, and the user can also set the transmission channel of the database to the data / switch state through the watch 200, which is not limited herein. The watch 200 can determine whether to upload the privacy data on the watch to the child cloud 300b according to the switch state recorded in the database.

[0189] The child cloud 300b can obtain the age information of the watch user from the account cloud 300a according to the token, for the smart care application 101 to query. The child cloud 300b can determine whether to synchronize the privacy data on the watch to the smart care application 101 according to the switch state of the data synchronization switch.

[0190] The mobile phone 100 can run the smart care application 101 in response to the user operation. The smart care application 101 and the child cloud 300b can establish a communication connection through Wi-Fi or a cellular data network supported by the SIM card of the mobile phone. The smart care application 101 can also query the age information of the watch user from the child cloud 300b, obtain the growth notification pushed by the child cloud 300b, and synchronize the switch state of the data synchronization switch to the child cloud 300b, etc.

[0191] It can be understood that the specific interaction process between the account cloud 300a, the watch 200, the child cloud 300b, and the mobile phone 100 in the data management system 1100 shown in the above Figure 11 The specific interaction process between the account cloud 300a, the watch 200, the child cloud 300b, and the mobile phone 100 in the data management system 1100 shown in the above Figure 3 and Figure 8 The specific interaction process between the account cloud 300a, the watch 200, the child cloud 300b, and the mobile phone 100 in the data management system 1100 shown in the above

[0192] Based on the data management system shown in the above Figure 11 , Figure 12 According to the embodiments of the present application, another embodiment of the implementation flow diagram of the data management method is shown.

[0193] It can be understood that the execution subject of each step of the flow shown in the above Figure 12 may be the data management system 1100 shown in the above Figure 11 . Among them, the mobile phone 100 running the smart care application 101 included in the system 1100 can be referred to as a management device, and the watch 200 can be referred to as a managed device.

[0194] Specifically, the flow shown in the above Figure 12 may include the following steps:

[0195] 1201: The management device establishes a binding relationship with the managed device.

[0196] The specific implementation process of the above establishing a binding relationship can refer to the related description in steps 301-309 shown in the above Figure 3 and will not be described here.

[0197] 1202: Determine an initial data management scheme according to the age group of the user of the managed device.

[0198] The specific implementation process of the above determining an initial data management scheme can refer to the related description in steps 310-314 shown in the above Figure 3 and will not be described here.

[0199] 1203: Detect a change in the age group of the user of the managed device.

[0200] Exemplarily, the user of the managed device can be the watch user described above. The specific implementation process of the above detecting a change in the age group of the user of the managed device can refer to the related description in step 801 shown in the above Figure 8 and will not be described here.

[0201] 1204: Determine whether the age group of the user of the managed device changes.

[0202] If the determination result is yes, that is, the age group of the user of the managed device changes, the data management system 1100 can further perform the implementation process of steps 1205-1207 described below.

[0203] If the determination result is no, that is, the age group of the user of the managed device does not change, the data management system 1100 can return to the above step 1203 and continue to detect whether the age group of the user of the managed device changes.

[0204] Exemplarily, the change in the age group of the user of the managed device can be a change from the child stage to the adolescent stage, or a change from the adolescent stage to the adult stage, and the corresponding description is the change process of the two adjacent age groups. The above determination process can refer to the related description of the detection process in step 802 shown in the above Figure 8 and will not be described here.

[0205] 1205: Start changing the data authorization scheme.

[0206] 1206: Change according to the corresponding data authorization scheme matched according to the age group of the user.

[0207] For example, age segment a corresponding to the user can match data management scheme A, age segment b corresponding to the user can match data management scheme B, age segment c corresponding to the user can match data management scheme C, …, age segment n corresponding to the user can match data management scheme N.

[0208] It can be understood that determining the age segment in which the user is located according to the age information of the user, and matching the corresponding data management scheme according to each age segment, can be flexibly set according to actual needs, and the present application does not limit this.

[0209] 1207: End of changing the data authorization scheme.

[0210] The above steps 1205 to 1207 are the specific implementation process of matching and changing the data management scheme for the user of the managed device, and the related description in steps 803 to 809 shown in the above Figure 8

[0211] Figure 13 According to an embodiment of the present application, a structural schematic block diagram of an electronic device 1300 is shown.

[0212] In the embodiment of the present application, the electronic device 1300 can be the mobile phone 100 in the above example, or the watch 200 in the above example. In other embodiments, the electronic device 1300 can be any electronic device for implementing the data management method provided by the present application.

[0213] The electronic device 1300 can include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0214] It can be understood that the structure shown in the embodiment of the present application does not constitute a specific limitation on the electronic device 1300. In other embodiments of the present application, the electronic device 1300 can include more or fewer components than shown, or combine certain components, or split certain components, or different arrangement of components. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0215] ​The processor 110 can include one or more processing units, for example: the processor 110 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units can be independent devices, or can be integrated in one or more processors.

[0216] The controller can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching instructions and executing instructions. In the embodiments of the present application, the processor 110 can control the fetching of instructions and the execution of instructions through the controller to implement the data management method provided in the embodiments of the present application. For example, the processor 110 can control the fetching of instructions and the execution of instructions through the controller to implement the steps corresponding to the mobile phone 100 or the watch 200 in the interaction process shown in the above embodiments. Figure 3 Or Figure 8 The controller can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching instructions and executing instructions. In the embodiments of the present application, the processor 110 can control the fetching of instructions and the execution of instructions through the controller to implement the data management method provided in the embodiments of the present application. For example, the processor 110 can control the fetching of instructions and the execution of instructions through the controller to implement the steps corresponding to the mobile phone 100 or the watch 200 in the interaction process shown in the above embodiments.

[0217] The processor 110 can also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can save instructions or data that have just been used or are used repeatedly by the processor 110. If the processor 110 needs to use the instructions or data again, it can directly call from the above-mentioned memory. This avoids repeated access and reduces the waiting time of the processor 110, thereby improving the efficiency of the system.

[0218] In some embodiments, the processor 110 can include one or more interfaces. The interfaces can include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (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.

[0219] The USB interface 130 is an interface conforming to the USB standard specification, and can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 1300, and can also be used to transmit data between the electronic device 1300 and a peripheral device. It can also be used to connect earphones to play audio through the earphones. The interface can also be used to connect other electronic devices, such as AR devices, etc.

[0220] It can be understood that the interface connection relationship between the modules shown in the embodiments of the present application is only illustrative and does not constitute a structural limitation of the electronic device 1300. In some other embodiments of the present application, the electronic device 1300 can also use different interface connection methods or a combination of multiple interface connection methods.

[0221] The charging management module 140 is configured to receive charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input through the wireless charging coil of the electronic device 1300. The charging management module 140 can charge the battery 142 while also providing power to the electronic device through the power management module 141.

[0222] The power management module 141 is configured to connect the battery 142 and the charging management module 140 to the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 can also be configured to monitor parameters such as battery capacity, battery cycle count, battery health (leakage, impedance), and the like. In some embodiments, the power management module 141 can also be integrated into the processor 110. In some other embodiments, the power management module 141 and the charging management module 140 can be integrated into the same device.

[0223] The wireless communication functionality of the electronic device 1300 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor, and the like.

[0224] The antenna 1 and the antenna 2 are configured to transmit and receive electromagnetic signals. Each antenna in the electronic device 1300 can be configured to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna for wireless local area networks. In some other embodiments, the antennas can be used in combination with a tuning switch.

[0225] The mobile communication module 150 can provide solutions for wireless communication including 2G / 3G / 4G / 5G, and the like, applied to the electronic device 1300. The wireless communication module 160 can provide solutions for wireless communication including wireless local area networks (WLAN) (e.g., wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) technology, and the like, applied to the electronic device 1300.

[0226] In some embodiments, the antenna 1 of the electronic device 1300 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, such that the electronic device 1300 can communicate with networks and other devices through wireless communication technologies.

[0227] The electronic device 1300 implements a display function through a GPU, a display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 can include one or more GPUs that execute program instructions to generate or change display information.

[0228] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel.

[0229] The electronic device 1300 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor, etc. The ISP is used to process data fed back by the camera 193.

[0230] The camera 193 is used to capture still images or videos. An object generates an optical image through a lens and projects it to a photosensitive element. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into a standard image signal in RGB, YUV, etc. format.

[0231] The digital signal processor is used to process digital signals, in addition to being able to process digital image signals, it can also process other digital signals. For example, when the electronic device 1300 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy, etc.

[0232] The video codec is used to compress or decompress digital videos. The electronic device 1300 can support one or more video codecs. In this way, the electronic device 1300 can play or record videos in multiple encoding formats, such as: moving picture experts group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0233] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 1300. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function.

[0234] The internal memory 121 can be used to store computer executable program codes including instructions. The internal memory 121 can include a program storage area and a data storage area. The program storage area can store an operating system, application programs required by at least one function, and the like. The data storage area can store data created during use of the electronic device 1300, and the like. In the embodiments of the present application, the application program stored in the program storage area can be a smart care application for managing the watch, and the data stored in the data storage area can be the latest data management scheme collected by the electronic device 1300 during running of the smart care application. Based on the latest data management scheme, the electronic device 1300 can correspondingly set the mobile phone terminal permission. This is not limited herein.

[0235] In addition, the internal memory 121 can include a high-speed random access memory, and can also include a non-volatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), and the like. The processor 110 executes various function applications and data processing of the electronic device 1300 by running instructions stored in the internal memory 121 and / or instructions stored in the memory disposed in the processor. In the embodiments of the present application, for example, the processor 110 of the electronic device 1300 can run the instructions stored in the internal memory 121 for performing the steps of the interaction process shown in FIG. 6, or the instructions stored in the memory disposed in the processor for performing the steps of the interaction process shown in FIG. 6. Figure 3 or Figure 8 The instructions of the steps correspondingly implemented by the mobile phone 100 or the watch 200 in the interaction process shown in the figure are used to match the corresponding data management scheme for the watch user in different age groups to manage the data or on-off state on the watch.

[0236] The electronic device 1300 can realize audio functions such as music playing, recording, and the like through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like.

[0237] The sensor module 180 can include a pressure sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like, which are not described herein.

[0238] The key 190 includes a power-on key, a volume key, and the like. The key 190 can be a mechanical key. It can also be a touch key. The electronic device 1300 can receive a key input and generate a key signal input related to user settings and function control of the electronic device 1300.

[0239] The motor 191 can generate a vibration prompt.

[0240] The indicator 192 can be an indicator light, which can be used to indicate the charging status, the power change, and can also be used to indicate messages, missed calls, notifications, etc.

[0241] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or pulled out of the SIM card interface 195 to realize contact and separation with the electronic device 1300.

[0242] Figure 14 According to an embodiment of the present application, a software system structure block diagram of a mobile phone 100 is shown.

[0243] The software system of the mobile phone 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present application takes the Android system with a layered architecture as an example to exemplarily illustrate the software structure of the mobile phone 100.

[0244] The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, which are an application layer, an application framework layer, an Android runtime and a system library, and a kernel layer.

[0245] As shown in Figure 14 , the application layer can include a series of application packages. The application package can include smart care, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc. Among them, the smart care application binds the watch 200 and interacts with the child cloud 300b and the account cloud 300a to realize the data management method provided in the embodiment of the present application

[0246] The application framework layer provides application programming interfaces (application programming interface, API) and programming frameworks for the applications of the application layer. The application framework layer includes some pre-defined functions.

[0247] As shown in Figure 14 , the application framework layer can include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc.

[0248] The window manager is used to manage the window program. The window manager can obtain the size of the display screen, judge whether there is a status bar, lock the screen, and intercept the screen, etc.

[0249] The content provider stores and retrieves data and makes it accessible to applications. The data can include videos, images, audio, dialed and received calls, browsing history and bookmarks, phonebook, etc.

[0250] The view system includes visual controls, such as controls that display text, controls that display pictures, etc. The view system can be used to build an application. A display interface can be composed of one or more views. For example, a display interface that includes a short message notification icon can include a view that displays text and a view that displays a picture.

[0251] The telephony manager is used to provide the communication functions of the phone 100. For example, management of call status (including call connection, call hang-up, etc.).

[0252] The resource manager provides various resources for applications, such as localized strings, icons, pictures, layout files, video files, etc.

[0253] The notification manager enables applications to display notification information in the status bar. The notification manager can be used to convey messages of the notification type, which can automatically disappear after a short period of time without user interaction. For example, the notification manager is used to notify of download completion, message reminders, etc. The notification manager can also be a notification that appears in the form of a chart or a scroll bar text in the top status bar of the system, such as a notification of an application running in the background, or a notification that appears in the form of a dialog window on the screen. For example, a text message is prompted in the status bar, a prompt sound is emitted, the electronic device vibrates, an indicator light flashes, etc.

[0254] The Android runtime includes a core library and a virtual machine. The Android runtime is responsible for scheduling and managing the Android system.

[0255] The core library includes two parts: one part is the function functions that the java language needs to call, and the other part is the core library of Android.

[0256] The application layer and the application framework layer run in the virtual machine. The virtual machine executes the java files of the application layer and the application framework layer into binary files. The virtual machine is used to perform functions such as management of object life cycle, stack management, thread management, security and exception management, and garbage collection.

[0257] The system library can include multiple functional modules. For example: a surface manager (surface manager), media libraries, a three-dimensional graphics processing library (for example: openGL ES), a 2D graphics engine (for example: SGL), etc.

[0258] The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

[0259] The media library supports a variety of commonly used audio, video format playback and recording, and static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0260] The three-dimensional graphics processing library is used to realize three-dimensional graphics drawing, image rendering, synthesis, and layer processing, etc.

[0261] The 2D graphics engine is a drawing engine for 2D drawing.

[0262] The kernel layer is a layer between hardware and software. The kernel layer at least includes display drivers, camera drivers, audio drivers, and sensor drivers.

[0263] The embodiment of the application further provides a computer program product for implementing the data management method provided in the above embodiment.

[0264] Embodiments of the mechanisms disclosed herein can be implemented in hardware, software, firmware, or some combination of these implementation approaches. Embodiments of the application can be implemented as computer program modules or module code executing on a programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0265] Computer program modules or module code can be applied to input instructions to perform the functions described herein and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system that has a processor, such as for example a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

[0266] Module code can be implemented in a high-level modular language or an object-oriented programming language to communicate with a processing system. When necessary, module code can also be implemented in assembly language or machine language. In fact, the mechanisms described in this application are not limited to the scope of any particular programming language. In any case, the language can be a compiled language or an interpreted language.

[0267] In some cases, the disclosed embodiments can be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments can also be implemented as instructions carried by or stored on a transitory or non-transitory machine-readable (e.g., computer-readable) medium, which can be read and executed by one or more processors. For example, the instructions can be distributed over the network or by other computer readable media. Thus, a machine-readable medium can include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including without limitation, floppy diskettes, optical disks, optical fiber, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or any type of media suitable for storing electronic instructions. Thus, a machine-readable medium includes any type of medium for propagating electronic instructions including without limitation, a carrier wave, an infrared signal, digital signal, or any other form of propagated signal suitable for a transmitting electronic instructions.

[0268] Reference throughout the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one example embodiment disclosed in this application. The appearance of the phrases "in one embodiment" or "in an embodiment" in various places throughout the specification are not necessarily all referring to the same embodiment.

[0269] The disclosure of the present application also relates to an apparatus for performing operations in text. The apparatus can be specially constructed for the required purposes, or it can comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer readable medium, such as, but not limited to any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, application specific integrated circuits (ASICs), or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus. Furthermore, the computers referred to in the specification can include a single processor or can be architectures employing multiple processors for increased computing capability.

[0270] Also, the language used in the specification has been principally selected for readability and instructional purposes and can not have been selected to delineate or circumscribe the disclosed subject matter. Accordingly, the present application embodiments are intended to be illustrative, but not limiting, of the scope of the concepts discussed herein.

Claims

1. A data management method applied to a first electronic device, characterized in that, include: If the first user's age group is a first age group, the first control is displayed. The first control is used to control the permission of the second electronic device to obtain the first data. The second electronic device is used to manage the first electronic device. In response to the first user's operation on the first control, adjust the second electronic device's permission to obtain the first data; If the first user's age belongs to the second age group, the first control will not be displayed.

2. The method according to claim 1, characterized in that, Determining the age range of the first user includes: Send a first query request to the first cloud server, wherein the first query request is used to obtain the age group label in the information related to the first account used by the first user, wherein the age group label is determined based on the age information of the first user recorded in the information related to the first account; Based on the obtained age group tags, the age group of the first user is determined.

3. The method according to claim 2, characterized in that, The first age group includes a third age group and a fourth age group, wherein the age intervals corresponding to the third and fourth age groups are continuous intervals, the age in the third age group is higher than the age in the fourth age group, and the method includes: If the first user's age group belongs to the third age group, a second control is displayed. The second control is used to control the permission of the first electronic device to collect and report the second data. In response to the first user's operation on the second control, adjust the permissions of the first electronic device to collect and report the second data; If the first user's age group belongs to the fourth age group, the second control will not be displayed.

4. The method according to claim 3, characterized in that, The second data includes log data generated during the first user's use of the first electronic device, and the log data includes either the first user's behavior log or the error log of the first electronic device.

5. The method according to claim 3, characterized in that, The age intervals corresponding to the first and second age groups are continuous intervals, and the age in the first age group is higher than the age in the second age group; and, The age group labels include: a first label corresponding to the first age group, a second label corresponding to the third age group, and a third label corresponding to the fourth age group.

6. The method according to claim 3, characterized in that, The first control is a switch control, and, The step of allowing or disabling the second electronic device to acquire the first data in response to an operation by the first user on the first control includes: In response to a first user setting the state of the first control to the enabled state, the second electronic device is allowed to acquire the first data; In response to a second operation by the first user setting the state of the first control to the off state, the second electronic device is prevented from acquiring the first data.

7. The method according to claim 3, characterized in that, The step of adjusting the permissions of the first electronic device to collect and report the second data in response to the first user's operation on the second control includes: In response to a third operation by the first user setting the state of the second control to the on state, the first electronic device is allowed to collect and report the second data; In response to a fourth operation by the first user setting the state of the second control to the off state, the first electronic device is prohibited from collecting and reporting the second data.

8. The method according to any one of claims 3 to 7, characterized in that, The first control includes any one of the following: Controls used to synchronize the location information of the first electronic device to the second cloud server; Controls used to synchronize the motion information recorded by the first electronic device to the second cloud server; Controls used to synchronize the address book stored on the first electronic device with the second cloud server; Controls used to synchronize the photo album data of the first electronic device to the second cloud server; Controls used to synchronize the stranger text messages received by the first electronic device with the second cloud server; A control used to control whether the first electronic device allows automatic answering of call requests.

9. The method according to claim 8, characterized in that, The first data includes any one of the following data collected or stored by the first electronic device: Location information; activity records; contacts; photo album data; text messages from strangers.

10. The method according to claim 9, characterized in that, The permission or prohibition of the first electronic device from collecting and reporting the second data includes: Allow or prohibit the first electronic device from reporting the collected second data to the first cloud server or the second cloud server.

11. A data management method applied to a second electronic device, characterized in that, The second electronic device is used to manage the first electronic device, and the method includes: When the first electronic device displays the first control, the second electronic device does not display the second control, wherein both the first control and the second control are used to control the permission of the second electronic device to obtain the first data; If the first electronic device does not display the first control, the second electronic device displays the second control; In response to the second user setting the state of the second control to the on state, the second electronic device acquires the first data from the first electronic device.

12. The method according to claim 11, characterized in that, The method further includes: When the first electronic device displays the third control, the second electronic device does not display the fourth control, wherein both the third control and the fourth control are used to control the permission of the first electronic device to collect and report the second data; If the first electronic device does not display the second control, the second electronic device displays the second control.

13. A data management system, characterized in that, It includes a first electronic device, a second electronic device, a first cloud server, and a second cloud server, wherein, The first electronic device and the second electronic device respectively establish a first communication connection with the first cloud server; The first electronic device and the second electronic device respectively establish a second communication connection with the second cloud server, and, The first electronic device, based on the first communication connection and the second communication connection, is used to execute the data management method according to any one of claims 1 to 10; The second electronic device is used to execute the data management method of claim 11 or 12 based on the first communication connection and the second communication connection.

14. An electronic device, characterized in that, include: One or more processors; One or more memories; the one or more memories storing one or more programs, which, when executed by the one or more processors, cause the electronic device to perform the data management method of any one of claims 1 to 12.

15. A computer-readable medium, characterized in that, The readable medium stores instructions that, when executed on a computer, cause the computer to perform the data management method according to any one of claims 1 to 12.

Images