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

By adjusting the data management permissions of smart watches according to the user's age group, the problem of being unable to adapt to the needs of users of different age groups in the existing technology is solved, and data security and user experience are improved.

WO2024234712A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/072556
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-17
Filing Date
2024-01-16
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

The existing data management solutions for wearable devices such as smart watches cannot meet the data control permission needs of users of different age groups, resulting in poor user experience and insufficient data security.

Method used

By determining the user's age group, matching suitable data management solutions, and controlling the operation permissions of the watch and mobile phone, ensuring data security and user experience. The specific method includes recording the user's age information in the account cloud, determining the user's age group based on the age group tag, and displaying or hiding corresponding controls on the watch and mobile phone, allowing or prohibiting data access and collection permissions.

Benefits of technology

It realizes dynamic adjustment of data management permissions based on user age, improves user experience, ensures data security, and meets the data management needs of users of different age groups.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024072556_21112024_PF_FP_ABST
    Figure CN2024072556_21112024_PF_FP_ABST
Patent Text Reader

Abstract

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. The method applied to a first electronic device comprises: determining the age bracket of a user; if the age bracket of the user falls within a first age bracket, displaying a first control, wherein the first control is used for controlling the permission of a second electronic device for obtaining first data, and the second electronic device is used for managing the first electronic device; in response to an operation of the user on the first control, allowing or forbidding the second electronic device to obtain the first data; and if the age of the user falls within a second age bracket, skipping displaying the first control. Therefore, the electronic device can adaptively match a data management scheme for a user according to the age bracket of the user, and display corresponding control permission.
Need to check novelty before this filing date? Find Prior Art

Description

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

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on May 17, 2023, with application number 202310560257.1 and application name “Data Management Method, System, Electronic Device and Computer-Readable Medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present invention relates to the field of terminal technology, and in particular to a data management method, system, electronic device and computer-readable medium. Background Art

[0003] With the development of terminal technology, wearable devices suitable for different age groups are becoming increasingly common, such as smartwatches. These devices typically require a connection to a mobile device such as a phone, which then authorizes the phone to manage data on the device. For example, if a child is using a smartwatch, the corresponding user managing the data on the smartwatch through the phone could be the child's parent.

[0004] However, the current data management solutions for wearable devices such as smart watches are relatively simple, and cannot adapt to users of different age groups to adjust the control rights of mobile phones and watches over related data.

[0005] Summary of the Invention

[0006] This application provides a data management method, system, electronic device, and computer-readable medium. This solution can adaptively adjust the matching data management solution based on the age group of the user of the managed device, such as a watch, to control the operating permissions of the managed device and the corresponding operating permissions of the bound management device, thereby improving the user experience while ensuring data security.

[0007] 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 user's age group belongs to the first age group, displaying a first control, the first control being used to control the permission of a second electronic device to obtain first data, and the second electronic device being used to manage the first electronic device; in response to the user's operation of the first control, allowing or prohibiting the second electronic device from obtaining the first data; if the user's age belongs to the second age group, not displaying the first control.

[0008] For example, the first electronic device may be a watch, and the second electronic device may be a mobile phone. The mobile phone can manage the watch through an installed smart care application. The watch can match a data management solution for managing data and / or applications on the watch based on the user's current age group. This data management solution can allocate some control permissions to the watch, and correspondingly allocate other control permissions to the mobile phone.

[0009] For example, if the first age group is adults aged 18 or above, the watch can display the first control after configuring the watch-side permissions according to the data management solution that matches the adult stage. In this case, the first electronic device, such as a watch, can allow the watch user to operate the first control.

[0010] The second age group may include children under the age of 14 and adolescents aged 14 to 18. After configuring watch-side permissions according to the data management solution corresponding to the child or adolescent stage, the watch may not display the first control. In this case, the first electronic device, such as a watch, may not allow the watch user to operate the first control.

[0011] In a possible implementation of the first aspect above, determining the user's age group includes: sending a first query request to a first cloud server, wherein the first query request is used to obtain an age group tag in information related to a first account used by the user, wherein the age group tag is determined based on the user's age information recorded in the information related to the first account; and determining the user's age group based on the obtained age group tag.

[0012] For example, the first cloud server may be an account cloud, and the first account may be a watch account. The account cloud may store information related to the watch account used by the user of the first electronic device. Furthermore, the account cloud may determine the current age group of the watch user based on the watch user's age information, such as date of birth, recorded in the watch account related information, and add a corresponding age group tag to the watch user related information. In this way, the first electronic device, such as a watch, may query the account cloud for the user's age group tag to determine the user's age group.

[0013] In a possible implementation of the first aspect above, the first age group includes a third age group and a fourth age group, wherein the age intervals corresponding to the third age group and the fourth age group are continuous intervals, and the age of the third age group is higher than the age of the fourth age group, and the above method includes: if the user's age group belongs to the third age group, displaying a second control, 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 user's operation on the second control, allowing or prohibiting the first electronic device from collecting and reporting the second data; if the user's age group belongs to the fourth age group, not displaying the second control.

[0014] For example, if the third age group is a teenager aged 14 or above but under 18, the watch can display the second control after configuring the watch-side permissions according to the data management solution corresponding to the teenager stage. In this case, the first electronic device, such as a 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," which is not limited here.

[0015] The fourth age group is children under 14 years old. After the watch configures the watch-side permissions according to the data management solution corresponding to the child stage, the second control may not be displayed. In this case, the first electronic device, such as a watch, may not allow the watch user to operate the second control.

[0016] In a possible implementation of the first aspect above, the second data includes log data generated when the user uses the first electronic device, and the log data includes any one of the user's behavior log and the error log of the first electronic device.

[0017] In a possible implementation of the first aspect, the age intervals corresponding to the first age group and the second age group are continuous intervals, and the age of the first age group is higher than the age of the second age group; and

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

[0019] For example, the first label may be an adult stage label, the second label may be a teenager stage label, and the third label may be a child stage label.

[0020] In a possible implementation of the first aspect above, the first control is a switch control, and in response to a user operation on the first control, allowing or prohibiting the second electronic device from obtaining the first data includes: in response to a first operation in which the user sets the state of the first control to an on state, allowing the second electronic device to obtain the first data; in response to a second operation in which the user sets the state of the first control to an off state, prohibiting the second electronic device from obtaining the first data.

[0021] In a possible implementation of the first aspect above, in response to the user's operation on the second control, allowing or prohibiting the first electronic device from collecting and reporting the second data includes: in response to the user's third operation of setting the state of the second control to the on state, allowing the first electronic device to collect and report the second data; in response to the user's fourth operation of setting the state of the second control to the off state, prohibiting the first electronic device from collecting and reporting the second data.

[0022] In a possible implementation of the first aspect above, the first control includes any one of the following: a control corresponding to synchronizing the location information of the first electronic device to the second cloud server; a control corresponding to synchronizing the motion information recorded by the first electronic device to the second cloud server; a control corresponding to synchronizing the address book stored on the first electronic device to the second cloud server; a control corresponding to synchronizing the album data of the first electronic device to the second cloud server; a control corresponding to synchronizing text messages received by the first electronic device by strangers to the second cloud server; and a control for controlling whether the first electronic device is allowed to automatically answer call requests.

[0023] The second cloud server may be, for example, a children's cloud. The watch and the mobile phone may establish communication connections with the children's cloud respectively.

[0024] In a possible implementation of the first aspect above, the first data includes any one of the following data collected or stored by the first electronic device: location information; movement records; address book; album data; stranger text messages.

[0025] In a second aspect, the present application provides a data management method, which is applied to a second electronic device, where the second electronic device is used to manage a first electronic device. The method includes: 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 used 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; in response to the second user's operation of setting the state of the first control to the on state, the second electronic device obtains the first data of the first electronic device.

[0026] That is, the first electronic device and the second electronic device can mutually exclusively display their respective control permissions based on corresponding data management solutions.

[0027] In a possible implementation of the second aspect above, the method also includes: confirming that the first electronic device displays the second control and the second electronic device does not display the second control, wherein the second control is used to control the authority of the first electronic device to collect and report the second data; confirming that the first electronic device does not display the second control and the second electronic device displays the second control.

[0028] In a third aspect, the present application provides a data management system, including 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 based on the first communication connection and the second communication connection to execute the data management method provided by the above-mentioned first aspect and various possible implementations of the first aspect; the second electronic device is based on the first communication connection and the second communication connection to execute the data management method provided by the above-mentioned second aspect and various possible implementations of the first aspect.

[0029] In a fourth aspect, the present application provides an electronic device comprising: one or more processors; one or more memories; one or more memories storing one or more programs, which, when executed by one or more processors, enables the electronic device to execute the data management method provided in the first aspect, the second aspect and various possible implementations.

[0030] In a fifth aspect, the present application provides a computer-readable medium having instructions stored thereon, which, when executed on a computer, causes the computer to execute the data management method provided in the first aspect, the second aspect, and various possible implementations described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] FIG1 is a schematic diagram showing an application scenario of a data management method provided in an embodiment of the present application.

[0032] FIG2 is a schematic diagram showing the implementation principle of a data management method provided in an embodiment of the present application.

[0033] FIG3 is a flow chart showing an interactive implementation of a data management method according to an embodiment of the present application.

[0034] FIG4 is a schematic diagram showing changes in interfaces related to collecting the age information of a watch user during a process of creating a new watch account provided by an embodiment of the present application.

[0035] FIG5 is a schematic diagram of an interface for improving watch user information provided in an embodiment of the present application.

[0036] Figure 6A shows a schematic diagram of the privacy center interface corresponding to data management solution A displayed on the watch after setting the watch-side permissions provided in an embodiment of the present application.

[0037] Figure 6B shows a schematic diagram of the privacy center interface corresponding to data management solution B displayed on the watch after setting the watch-side permissions provided in an embodiment of the present application.

[0038] FIG6C is a schematic diagram showing an interface corresponding to data management solution C displayed on the watch after setting watch-side permissions according to an embodiment of the present application.

[0039] Figure 7A shows a schematic diagram of the privacy center interface corresponding to data management solution A displayed on the watch after setting the mobile phone permissions provided in an embodiment of the present application.

[0040] Figure 7B shows a schematic diagram of the privacy center interface corresponding to data management solution B displayed on the watch after setting the mobile phone permissions provided in an embodiment of the present application.

[0041] Figure 7C shows a schematic diagram of the privacy center interface corresponding to data management solution C displayed on the watch after setting the mobile phone permissions provided in an embodiment of the present application.

[0042] FIG8 is a schematic diagram showing an interactive implementation flow of another data management method provided in an embodiment of the present application.

[0043] FIG9 is a schematic diagram showing the changes in the growth notification interface displayed on the watch when it is detected that the watch user has entered the teenage stage or the adult stage, as provided in an embodiment of the present application.

[0044] FIG10A is a schematic diagram showing the changes in the interface of a mobile phone displaying a privacy change notification provided by an embodiment of the present application.

[0045] FIG10B is a schematic diagram showing the changes in the relevant interfaces of the watch displaying the privacy change notification provided in an embodiment of the present application.

[0046] FIG11 is a schematic diagram showing the architecture of a data management system for implementing the above-mentioned data management method provided in an embodiment of the present application.

[0047] FIG12 is a schematic diagram showing an implementation flow of a data management method provided in an embodiment of the present application.

[0048] FIG13 is a schematic structural diagram of an electronic device provided in an embodiment of the present application.

[0049] FIG14 shows a block diagram of the software system structure of a mobile phone 100 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to make the purpose, 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 reference to the accompanying drawings and specific implementation methods.

[0051] FIG1 shows a schematic diagram of an application scenario of a data management method according to an embodiment of the present application.

[0052] As shown in Figure 1, the scenario includes a mobile phone 100 and a watch 200. The watch 200 may be a children's smart watch, and accordingly, an APP for managing the watch 200, such as the smart care application 101, may be installed on the mobile phone 100.

[0053] When using the watch 200 for the first time, you can log in to your mobile phone account on your phone 100 and bind it to the watch 200. You also need to create a new watch account for the watch 200 and log in to it in order to access the full functionality of the watch 200. This full functionality refers to all functions supported by the watch 200. The mobile phone user who logs in to their mobile phone account on the phone 100 and uses the Smart Care app 101 can be a parent user, while the watch user who logs in to their watch account on the watch 200 and uses the full functionality of the watch can be a child user. Both the mobile phone account information and the watch account information can be synchronously uploaded to the account cloud 300a. Simultaneously, the phone 100 and the watch 200 can each establish communication connections with the child cloud 300b, which manages child-related data. For example, the Smart Care app 101 running on the phone 100 can access the child cloud 300b via Wi-Fi or a cellular data network supported by the phone's SIM card; the watch 200 can access the child cloud 300b via Wi-Fi or a cellular data network supported by the watch's SIM card. In this way, the mobile phone 100 can view, share, or turn on or off the data or related data switches on the watch 200 based on the authorization.

[0054] When the user of the watch 200 grows to the next age stage, for example, from the current childhood stage to the adolescent stage, the user may want to manage some personal data on the watch 200 by himself, or turn on or off the corresponding functions on the watch 200 by himself. In this case, the control authority of the mobile phone 100 over the data on the watch 200 and the control authority of the watch 200 over its own data need to be adaptively adjusted.

[0055] As mentioned above, the current data management solution for managing the data on the watch 200 cannot meet the data management needs of users of different age groups.

[0056] In order to solve the above problems, the present application provides a data management method. Specifically, the method presets data management schemes that match users of different age groups based on their management capabilities and management needs for data on wearable devices such as watches used by users of different age groups. For example, as shown in reference to Figure 2, for users under the age of 14, data management scheme A can be used. Scheme A can preset mobile phone permissions including control permissions for privacy data on the watch, switch control permissions for the authorized watch to collect and report the user's behavior logs and error logs during the use of the watch, and whether to turn on some data synchronization switches, etc., and preset watch-side permissions do not include control permissions for the above content. For users who are over 14 years old but under 18 years old, data management scheme B can be used. Scheme B can preset mobile phone permissions including control permissions for some data synchronization switches on the watch, etc., and preset watch-side permissions including control permissions for privacy data on the watch and switch control permissions for the authorized watch to collect and report the user's behavior logs and error logs during the use of the watch, etc. For users who are 18 years of age or older, they can use Data Management Plan C. Plan C can preset watch-side permissions including the above-mentioned privacy data, the switch control permission for the authorized watch to collect and report the user's behavior logs and error logs during the use of the watch, and the control permission for whether to turn on some data synchronization switches, etc., and the preset mobile phone permissions do not include the various control permissions for the above-mentioned content.

[0057] The switch for collecting the user's behavior log and error log during the use of the watch can be simply referred to as the "authorization switch" shown in Figure 2. This switch can, for example, be the switch corresponding to "Join the User Experience Improvement Program." The above-mentioned behavior log can record, for example, the frequency and duration of the user's use of certain watch functions, and other related data. The error log can record, for example, the time and type of functional failures that occur during the operation of the watch. This is not limited here.

[0058] 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 the user, thereby meeting the data management needs of users of different age groups on wearable devices such as watches. Furthermore, during the long-term use of the watch by the same user, the watch can monitor changes in the user's age group by polling the account cloud, etc. When it detects that the user has grown to the next age group, the watch can proactively match the user with the corresponding data management solution for the next age group, thereby meeting the user's corresponding data management needs as the user grows to different age groups.

[0059] It is understandable that in other embodiments, the ages used to identify the childhood stage, the adolescent stage, and the adult stage, such as 14 years old and 18 years old, may also be other preset ages, which are not limited here.

[0060] It can be understood that, in view of the management relationship between the watch and the mobile phone and authorizing the mobile phone to manage the relevant data on the watch, the mobile phone-side permissions shown in Figure 2 can also be called management-side permissions, and the management-side permissions can also be the control permissions of applications such as smart care (application, APP) installed on the mobile phone. Correspondingly, the watch-side permissions shown in Figure 2 can also be called managed-side permissions. Among them, the managed-side permissions can correspond to the permissions of the user of the watch to directly operate and manage 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 during the user's use of the watch, and management of the status of some data synchronization switches on the watch, etc., which are not limited here.

[0061] In other embodiments, the data management solution provided in the present application may also include more or fewer data management solutions corresponding to different age groups than those shown in FIG2 , and each data management solution may also adopt other reasonable allocation methods for the authorization authority to manage corresponding data on the mobile phone or watch side, which is not limited here.

[0062] It is understood that the private data on the aforementioned wearable devices, such as watches, may include but is not limited to location data, exercise data, address book data, photo album data, and SMS data collected or recorded by the watches. The aforementioned data synchronization switches may be corresponding switches for obtaining or viewing the aforementioned private data, such as a watch location switch, exercise record switch, address book switch, photo album switch, and stranger SMS switch. The aforementioned switch control authority for authorizing the watch to collect and report the user's behavior logs and error logs during the use of the watch may be switch control authority corresponding to the user experience improvement plan for the watch and the user experience improvement plan for other wearable devices, and is not limited here.

[0063] It can be understood that the wearable devices to which the data management solution provided in this application is applicable may include but are not limited to smart watches, smart bracelets, smart glasses, wired headphones, wireless headphones (for example, TWS Bluetooth headphones, neck-hanging Bluetooth headphones, head-mounted Bluetooth headphones), smart anklets, smart rings, smart necklaces, augmented reality (AR) devices, virtual reality (VR) devices, etc. This application does not impose any special restrictions on the specific form of the wearable device.

[0064] The data management solution provided in this application is applicable to mobile terminals for managing data on wearable devices such as watches, and may include but are not limited to mobile phones, tablet computers, desktop computers, laptops, handheld computers, netbooks, as well as smart TVs, servers, car equipment, and other electronic devices that are embedded or coupled with one or more processors and can access the network.

[0065] As an example, the following continues to take the watch 200 as the managed device and the mobile phone 100 as the managing device as an example to specifically describe the specific implementation process of the data management solution provided by this application.

[0066] It is understood that in the application scenario shown in FIG1 above, the watch 200 in the embodiment of the present application can be a children's watch customized for children's growth. In other application scenarios, the watch 200 in the embodiment of the present application can also be a smart watch that supports interchangeable watch cases to adapt to users of different age groups, etc. This is not limited here.

[0067] It should also be 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 order of precedence. If there is a sequence between the steps, the written description shall prevail.

[0068] Based on the application scenario shown in FIG1 above, FIG3 shows a schematic diagram of an interactive process for implementing the data management method provided in an embodiment of the present application.

[0069] As shown in Figure 3, the interaction process primarily describes the specific implementation process of matching a data management solution appropriate for the watch user's age group when the watch 200 is first used. This interaction process primarily involves the interaction between the phone 100, the watch 200, the account cloud 300a, and the child cloud 300b. In other embodiments, to differentiate descriptions, the account cloud 300a may also be described as the first cloud server, and the child cloud 300b may also be described as the second cloud server.

[0070] Specifically, the interaction process shown in FIG3 may include the following steps:

[0071] 301: Mobile phone 100 logs in to the mobile phone account.

[0072] For example, in response to a user operation, the mobile phone 100 can run an application capable of managing the watch, such as the Smart Care application. Furthermore, the user can log in to their mobile phone account on the corresponding login interface of the Smart Care application to establish a communication connection between the mobile phone 100 and the account cloud 300a. It is understood that when the mobile phone 100 first runs the Smart Care application, it can prompt the user to log in to their mobile phone account. The corresponding reminder interface can refer to existing mobile phone account login interfaces and is not further described in this application.

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

[0074] For example, a user can bind a watch to a specific interface on the smart care app displayed on the phone 100. Upon detecting the user's request to bind the watch, the phone 100 can display an interface for verifying the watch information to be bound, such as a scan code page. This scan code page can be used to scan the device identification code displayed on the watch 200 to be bound. This device identification code can be a QR code, barcode, or other similar code containing device identification information, without limitation.

[0075] For example, the user can click the Smart Care app icon on the phone 100 desktop to launch the Smart Care app. Furthermore, the user can bind the watch 200 to the Smart Care app on the corresponding interface displayed on the phone 100. For example, the user can open the QR code scanning page on the Smart Care app interface and scan the device identification code displayed on the watch 200 with the phone 100 to obtain the device identification information of the watch 200. Using this device identification information, the phone 100 can request binding with the watch 200 indicated by the device identification information through the account cloud. The detailed binding process is described in steps 304 to 309 below and is not detailed here.

[0076] It is understandable that the smart care application running on the mobile phone 100 and other applications capable of managing the watch can provide multiple binding methods for the user to operate, which is not limited here.

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

[0078] For example, the user can input the watch account information on the relevant interface displayed on the mobile phone 100 that prompts the user to log in to the watch account. Accordingly, when the mobile phone 100 receives the watch account information input by the user, it can log in the watch account for the watch 200 to be connected. This watch account is different from the mobile phone account logged in by the mobile phone 100 in the above step 301. The watch account can be a device account logged in on the watch 200, and the above mobile phone account can be another device account logged in on the mobile phone 100, or an account used to log in to the smart care application. The above watch account information may include the account name set for the watch user, the mobile phone number specified for verification when creating a new account, the corresponding login password, and the age information of the watch user, etc., which are not limited here.

[0079] It is understood that when the mobile phone 100 is first bound to the watch 200, or when the watch 200 is used for the first time, the mobile phone account corresponding to the login of the smart care application on the mobile phone 100 can be used to create / login a watch account for the watch 200 to be bound. The watch account can be an account registered based on the SIM card number installed in the watch 200, or an account registered via email, without limitation. Taking the watch account registered with the SIM card as an example, if the SIM card installed in the watch 200 has not been registered as a watch account, the mobile phone account can be used to create a new watch account for the watch 200. If the SIM card installed in the watch 200 has already been registered as a watch account, the mobile phone account can be used to log in to the registered watch account for the watch 200.

[0080] As shown in Figure 4 , a user can select Create a New Watch Account 411 on the watch account login screen 410 displayed on the phone 100. During this creation process, the phone 100 can display an Age Information Collection screen 420 to collect the user's input age information, such as the birth date "August 18, 2018" shown in Figure 4 . This age information can then be recorded in the relevant information of the newly created watch account, serving as a basis for subsequently determining the user's age.

[0081] It is understandable that in some embodiments, when creating a new watch account, if the age information entered by the user indicates that the watch user is over 14 years old and is no longer in the childhood stage, a corresponding prompt interface may be displayed to inform the user that he or she can create another account.

[0082] It will be appreciated that if the watch user is under 14 years old and is in the child stage, the newly created watch account may also be displayed as a child account. Account cloud 300a may manage the relevant information of the child account under the corresponding mobile phone account logged in on mobile phone 100, for example, by associating and storing the relevant information of the child account with the relevant information of the watch account. In this case, the mobile phone account may be a parent account. If the user is over 14 years old and no longer in the child stage, other accounts that the user chooses to create can also be used to log in to watch 200. However, when these accounts are synchronized and stored on account cloud 300a, account cloud 300a may store the relevant information of these accounts independently and no longer associate them with the relevant information of the mobile phone account. Furthermore, after the other accounts created in the above process log in to watch 200, watch 200 can continue to establish a binding relationship with mobile phone 100. In this case, watch 200 can still match the watch user with the aforementioned data management solution B or data management solution C based on the user's age information of over 14 years old.

[0083] Continuing with FIG4 , the user can also select Login Existing Account 412 on the watch account login interface 410 displayed on the mobile phone 100 to log in a registered watch account for the watch 200. Furthermore, in subsequent steps, the relevant information of the logged-in existing account can provide the recorded age information of the watch user, which is not detailed here.

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

[0085] For example, after receiving the watch account information input by the user, the mobile phone 100 may send the corresponding information to the account cloud 300a for account information verification.

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

[0087] For example, the account cloud 300a can verify whether the received watch account information matches the registered watch account information, thereby confirming whether the watch account login is successful. It is understood that during 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 entered for the newly created watch account. Specifically, upon receiving the newly created watch account information, the account cloud 300a can determine the watch user's current age group based on the user's age information, such as date of birth. In other embodiments, after the user completes the creation of the watch account using the mobile phone 100, they may also complete the watch user's personal information. In this case, the account cloud 300a can determine the watch user's current age group based on the age information provided by the user when completing the information, such as birthday. After determining the corresponding age group, the account cloud 300a can add an age group tag to the corresponding watch account information to indicate the age group of the corresponding watch user. The rules for the account cloud 300a to determine the user's age group based on the user's age information can be preset in the account cloud 300a. As the watch user grows, the account cloud 300a can update and maintain the user's current age group in real time for the watch 200 to query.

[0088] For example, referring to FIG2 , if the watch user is 12 years old, the user's age group can be determined to be children (<14 years old). If the watch user is 15 years old, the user's age group can be determined to be adolescent (14 to 18 years old). If the watch user is 19 years old, the user's age group can be determined to be adults (≥18 years old). No restrictions are imposed here.

[0089] It is understood that as the watch user grows up, the account cloud 300a can continuously maintain the age group of the watch user. When the age group of the watch user changes, the watch 200 can detect the corresponding age group change when querying the account cloud 300a for the age group of the watch user.

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

[0091] For example, when the device identification code is displayed, watch 200 can begin polling the account cloud server to confirm with account cloud 300a whether a mobile phone has scanned the code to request watch binding. If so, watch 200 can receive the corresponding binding request. Furthermore, watch 200 can poll account cloud 300a to determine whether the binding between watch 200 and phone 100 is successful during the process of the phone 100 logging into the watch account. When account cloud 300a returns a successful binding message, watch 200 can end the polling.

[0092] The polling processes described above can be triggered based on a timing condition, such as a preset polling interval of 200ms, or based on a corresponding broadcast message received from the account cloud 300a, without limitation. It is understood that if the account cloud 300a does not provide a successful binding message, the watch 200 can gradually extend the polling interval, without limitation in this application.

[0093] 307: Watch 200 confirms binding with mobile phone 100.

[0094] For example, when the watch 200 receives the binding request initiated by the mobile phone 100, it can display a corresponding confirmation interface, and the user can confirm the operation on the confirmation interface to complete the process of binding the watch 200 to the mobile phone 100. The binding process is, for example, the process of binding the watch 200 to the smart care application running on the mobile phone 100.

[0095] It is understood that in other embodiments, the execution of steps 301 to 307 can also be described as the process of establishing a communication connection between the mobile phone 100, the account cloud 300a, the child cloud 300b, and the watch 200. Specifically, when the mobile phone 100 logs into the mobile phone account, a communication connection can be established with the account cloud 300a. When the mobile phone 100 runs the smart care app to bind the watch 200 and logs into the watch account, the watch 200 can establish a communication connection with the account cloud 300a, and simultaneously, the mobile phone 100 and the watch 200 can establish a communication connection with the child cloud 300b.

[0096] 308: The watch 200 sends a notification message of successful synchronization binding to the children's cloud 300b.

[0097] For example, after confirming the binding smart care application running on the mobile phone 100, the watch 200 can synchronously notify the child cloud 300b that the binding with the smart care application has been completed. For example, the watch 200 can synchronize a notification message of successful binding to the child cloud 300b.

[0098] 309: The mobile phone 100 polls the children's cloud 300b and obtains a binding success message.

[0099] For example, after executing step 302 and displaying the corresponding binding operation interface, the mobile phone 100 may start polling the child cloud server to confirm with the child cloud 300b whether the watch 200 has confirmed the binding of the smart care application. This polling process can also be understood as the process of the mobile phone 100 confirming whether the running smart care application and the watch 200 are successfully bound.

[0100] It is understandable that after obtaining the binding success message, the mobile phone 100 may display a corresponding prompt interface.

[0101] After the mobile phone 100 completes the binding of creating / logging in a watch account for the watch 200 when executing the above step 303, it can display the corresponding binding success interface to inform the user. After the binding is successful, the user can also operate on the mobile phone 100 to complete the watch user information, such as selecting the "Complete watch user information" option on the binding success interface displayed by the mobile phone 100. Accordingly, the mobile phone 100 can use the complete information interface 510 shown in Figure 5. The user can set the watch user's birthday on this interface 510. This setting process can correct the age information that was not entered or entered incorrectly when creating a new account. In some embodiments, the user can also operate on the complete information interface 510 to set the watch user's avatar, nickname, mobile phone number, gender, weight, height and other information, without limitation here.

[0102] Correspondingly, when the watch 200 is bound to the smart care APP running on the mobile phone 100, the watch 200 can also display the corresponding binding success interface.

[0103] 310: The watch 200 queries the account cloud 300a for the watch user's current age group.

[0104] For example, the watch 200 may query the account cloud 300a each time it is charged to find out the age group the watch user is currently in. In other embodiments, the watch 200 may also periodically poll the account cloud 300a to find out the age group the watch user is currently in.

[0105] 311: Watch 200 matches the data management solution for the watch user and sets the watch-side permissions accordingly.

[0106] For example, referring to Figure 2 above, if watch 200 detects that the watch user is a child (less than 14 years old), it can match the watch user with data management solution A shown in Figure 2. Solution A can pre-set mobile phone permissions to include control over private data on watch 200, authorization for the watch to collect and report user behavior logs and error logs during watch use, and some data synchronization controls. At the same time, Solution A can also pre-set watch-side permissions to exclude control over the aforementioned aspects.

[0107] If watch 200 detects that the watch user is a teenager (14 to 18 years old), it can match the watch user with Data Management Plan B. Plan B can pre-set phone-side permissions to only include control over some data synchronization switches on the watch. At the same time, Plan B can pre-set watch-side permissions to include control over private data on the watch and the ability to authorize the watch to collect and report user behavior logs and error logs during watch use.

[0108] When watch 200 detects that the watch user is an adult (≥18 years old), it can match the watch with data management solution C. Solution C can pre-set watch-side permissions, including control over private data on the watch, authorization for the watch to collect and report user behavior logs and error logs during watch use, and control of some data synchronization switches. Solution C can also pre-set phone-side permissions to exclude control over the aforementioned aspects.

[0109] After the watch 200 sets its own watch-side permissions according to the matched data management plan, the user can operate on the watch 200 to open the relevant interface of the "Privacy Center".

[0110] As an example, Figures 6A to 6C respectively show schematic diagrams of relevant interfaces after the watch 200 sets corresponding watch-side permissions according to different matched data management schemes according to an embodiment of the present application.

[0111] As shown in FIG6A , for the aforementioned example, if watch 200 is matched to data management plan A corresponding to the child stage for the watch user, then in response to the user opening the "Privacy Center" interface, watch 200 may display the privacy center interface 610 shown in FIG6A . This interface 610 may only display content that does not involve the child user's private data, the control permission for authorizing the watch to collect and report the user's behavior logs and error logs during watch use, and the data synchronization switch, such as the "User Agreement" and "Privacy Statement."

[0112] If the watch 200 matches the data management plan B corresponding to the adolescent stage for the watch user, the watch 200 can display the privacy center interface 620 shown in Figure 6B in response to the user's operation of opening the "Privacy Center" related interface. Compared with the interface 610 shown in Figure 6A, the privacy center interface 620 shown in Figure 6B can display an authorization switch 741, and the switch 741 can display, for example, "Join the watch user experience improvement plan". In some embodiments, the above interface 620 can also display a "Stop using children's watch" option 622 for the watch user in the adolescent stage to operate on the watch 200 to unbind from the mobile phone 100. In other embodiments, the above interface 620 can also display a "Children's Watch Notification" option 623 for the watch user in the adolescent stage to view the notification content related to the use of the watch on the watch 200, etc., which will not be repeated here.

[0113] If watch 200 matches the watch user with Data Management Plan B, which corresponds to the adolescent stage, watch 200 may display Privacy Center interface 630 shown in FIG6C in response to the user opening the "Privacy Center" interface. Compared to interface 620 shown in FIG6B , Privacy Center interface 630 shown in FIG6C may further display a "Data Management" option 631. After the user clicks on option 631, watch 200 may display Data Management interface 640.

[0114] As shown in FIG6C , the data management interface 640 may display multiple data synchronization switches, such as a watch location switch 641 , a motion record switch 642 , an address book switch 643 , an album switch 644 , a stranger text message switch 645 , and an automatic answering switch 646 .

[0115] It is understandable that in other embodiments, after the watch 200 sets its own watch-side permissions according to the matched data management plan, it can also display other different styles of privacy center interfaces in response to user operations, which is not limited here.

[0116] 312: The watch 200 synchronizes the matched data management solution to the children's cloud 300b.

[0117] For example, when the watch 200 sets its own watch-side permissions according to the matched data management solution, the matched data management solution can be synchronously sent to the children's cloud 300b.

[0118] 313: The mobile phone 100 requests the latest data management solution from the children's cloud 300b.

[0119] For example, after receiving the data management plan synchronized by the watch 200, the children's cloud 300b stores the plan. When the mobile phone 100 responds to the user's operation of opening the smart care application, it can first request the latest data management plan from the children's cloud 300b.

[0120] 314: The mobile phone 100 sets mobile phone permissions based on the acquired data management plan.

[0121] For example, the watch 200 can synchronize the data management plan matched for the watch user to the Child Cloud 300b. When the mobile phone 100 displays the relevant management interface for the bound watch 200, such as the device management interface of the smart care application, in response to the user, it can request the latest data management plan from the Child Cloud 300b. Furthermore, the mobile phone 100 can refresh the display content on the corresponding device management interface based on the latest data management plan obtained.

[0122] In some embodiments, after the watch 200 is successfully bound to the smart care application running on the mobile phone 100, 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 operate the relevant interface of the smart care application to open the "Watch Settings" function and click the "Privacy Center" option to display the privacy center interface corresponding to the different data management solutions obtained above.

[0123] As shown in Figure 7A , if the mobile phone 100 obtains Data Management Plan A, the mobile phone permissions include control over private data on the watch 200, authorization to collect and report user behavior and error logs during watch use, and control over certain data synchronization switches. After setting the corresponding mobile phone permissions, as shown in Figure 7A , the user can toggle the "Join the Watch User Experience Improvement Program" switch 711 on or off on the Privacy Center interface 710 to authorize the watch to collect and report user behavior and error logs during watch use. The user can also click the "Data Management" option 712 on this interface 710 to display the corresponding Data Management interface 720 on the mobile phone 100. All switches displayed on this interface 720, such as the watch location 721, exercise history 722, address book 723, photo album 724, and data synchronization switches such as stranger text messages 725 and automatic call answering 726, can be turned on or off by the user.

[0124] As shown in FIG7B , if the mobile phone 100 obtains Data Management Plan B, the mobile phone permissions include control over private data on the watch 200, control over the authorized watch's ability to collect and report the user's watch behavior and error logs, and control over certain data synchronization switches. After setting the corresponding mobile phone permissions, the user can click the "Data Management" option 731 on the Privacy Center interface 730 shown in FIG7B to display the corresponding data management interface on the mobile phone 100. This data management interface can be similar to the data management interface 720 shown in FIG7A . At this point, all switches on this interface, such as the watch location, exercise history, address book, photo album, stranger text messages, and automatic answering data synchronization switches, can still be turned on or off by the mobile phone user. However, because Data Management Plan B disables the control over the authorized watch's ability to collect and report the user's watch behavior and error logs, 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 may appear grayed out, indicating that user access is not permitted.

[0125] If the mobile phone 100 obtains the data management solution C, the mobile phone can correspondingly close the switch control authority for the privacy data on the watch 200, the switch control authority for the watch to collect and report the user's behavior logs and error logs during the use of the watch, and the control authority for some data synchronization switches, that is, the mobile phone authority is no control authority. After setting the corresponding mobile phone authority, since the data management solution C corresponds to closing the switch control authority for the watch to collect and report the user's behavior logs and error logs during the use of the watch in the mobile phone authority, the switch control corresponding to "Join the Watch User Experience Improvement Program" on the privacy center interface displayed by the mobile phone 100 can refer to the grayed-out state shown in Figure 7B above, and the user is not allowed to operate. In addition, the "Data Management" option 731 shown in Figure 7B above can also be displayed in a grayed-out state. If the user clicks the grayed-out "Data Management" option, the corresponding data management interface displayed by the mobile phone 100 can refer to that shown in Figure 7C. All switches displayed on the data management interface 740, such as watch position 741, exercise record 742, address book 743, photo album 744, stranger text messages 745, allow automatic answering 746 and other data synchronization switches, can be displayed in gray at this time, indicating that operation is not allowed.

[0126] It can be understood that based on the interactive process of steps 301 to 314 above, when the watch 200 is used for the first time, based on the watch user's age information recorded in the newly created / logged-in watch account, the watch user can be matched with the corresponding data management solution for the corresponding age group to manage the mobile phone and watch permissions separately. In this way, the watch 200 and other wearable devices can meet the data management needs of users of different age groups and can adapt to the data management capabilities of users of different age groups to ensure the security of data or applications on wearable devices such as watches.

[0127] It is understood that as the user of watch 200 continues to use the watch, as the user ages, when the watch user reaches the next age group, the data management method provided in this application can also be used to adaptively update the data management solution for the watch user. The specific implementation process of the data management solution that adapts to user growth will be described in detail below with reference to the corresponding figures.

[0128] FIG8 shows another interactive process diagram according to an embodiment of the present application. The interactive process mainly describes the specific implementation process of updating the data management solution to adapt to the user's growth during the continuous use of the watch 200 by the user.

[0129] As shown in Figure 8 , this interaction process primarily involves interactions between the phone 100, watch 200, account cloud 300a, and child cloud 300b. Specifically, in some embodiments, after implementing the interaction process shown in Figure 3 , the phone 100, watch 200, account cloud 300a, and child cloud 300b can continue to implement the interaction process shown in Figure 8 to monitor user age changes and adjust data management plans for watch users who are about to enter the next age group.

[0130] Specifically, the interaction process shown in FIG8 may include the following steps:

[0131] 801: The watch 200 queries the account cloud 300a for the watch user's current age group.

[0132] For example, the watch 200 may query the account cloud 300a for the current age group of the watch user each time it is charged, or may query the account cloud 300a for the current age group of the watch user by periodically polling the account cloud 300a. For details, please refer to the relevant description in the above step 310 and will not be repeated here.

[0133] 802: The watch 200 detects that the watch user's age group changes to the next age group.

[0134] For example, the watch 200 can compare the age group of the queried watch user with the age group queried previously. If they are different, it means that the watch 200 detects that the age group of the watch user has changed to the next age group.

[0135] In the aforementioned example, as the watch user grows up, they may experience age changes from childhood to adolescence, and then from adolescence to adulthood. For example, when the watch user grows from childhood to 14 years old, account cloud 300a can change the watch user's age group to the next age group, adolescence. For another example, when the watch user grows from adolescence to 18 years old, account cloud 300a can change the watch user's age group to the next age group, adulthood.

[0136] Accordingly, when the watch 200 queries the account cloud 300a about the age group of the watch user, it can query the updated relevant information on the account cloud 300a indicating that the watch user has entered the next age group.

[0137] 803: The watch 200 displays a notification that the data management plan is about to change for the watch user to confirm.

[0138] For example, based on a detected age group change, i.e., a change from the watch user's age group to the next age group, the watch 200 can generate and display a corresponding data management plan change notification for the user to confirm whether the data management plan should be changed. This data management plan change notification can be provided by notifying the user of changes to account information, privacy statements, or user agreements. It is understood that the watch 200 can display this change notification on the first day the watch user reaches the next age group, or when the account cloud 300a first detects that the watch user's age group has changed to the next age group. This is not a limitation.

[0139] As an example, referring to FIG9 , if the watch 200 detects that the watch user has entered the adolescent or adult stage, it may display a privacy center notification 910. This notification 910 may be displayed as a pop-up message or in the notification bar of the watch 200, without limitation. The content of the privacy center notification 910 may be, for example, "Your account information has changed. Please click to view details."

[0140] If the watch 200 detects that the watch user has entered adolescence, the user clicks on the content of the privacy center notification 910, which will cause the watch 200 to further display a watch notification interface 920. The user clicks the "Agree" control 921 on the watch notification interface 920, which will trigger the start of the data management plan change on the watch 200. If the user clicks the "Cancel" control 922 on the watch notification interface 920, the data plan change will not be 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. This will not be repeated here.

[0141] If the watch 200 detects that the watch user has entered adulthood, the user clicks on the privacy center notification 910, causing the watch 200 to display a data authorization interface 930. This interface 930 may display content such as, "Your account information has changed. Do you agree to retain the data synchronization settings set by your parents?" and "You can later modify the settings through Settings > About Watch > Privacy Center > Data Management." After reading the notification, the user can click on "Agree" 931 to accept the settings set on the smart care app on the phone 100. The user can also click on "Cancel" 932 on the data authorization interface 930 to reset the data synchronization settings on the watch 200. When the watch 200 detects that the user has clicked on "Cancel" 932, it may display the data management interface 940 shown in FIG. On this interface 940, the user can select the corresponding settings for each data synchronization switch. For example, selecting the switches for "Exercise Record" and "SMS from Strangers" indicates that the switches are turned on. After completing the settings, the user can click the “Done” control 941 to close the data management interface 940 .

[0142] In other embodiments, the user may also click the "Clear All" control 911 on the Privacy Center Notification 910 shown in FIG9 to ignore the above Privacy Center Notification. It is understood that after the user ignores the above Privacy Center Notification, the watch 200 may display the content of the above Privacy Center Notification 910 again the next time it is charged or turned on to remind the user to confirm. In other embodiments, after the user ignores the above Privacy Center Notification, the watch 200 may also directly display the watch notification interface 920 or the data authorization interface 930 shown in FIG9 the next time it is charged or turned on to guide the user to trigger the change of the data management plan caused by the change of age group.

[0143] In some embodiments, the watch 200 can notify the smart care application running on the mobile phone 100 through the children's cloud 300b while generating the corresponding data management scheme change notification. When the mobile phone 100 receives the corresponding notification, it can also display the corresponding notification interface. The notification interface can, for example, display "Dear XXX parents, hello! Your child XXX is about to grow up one year old and can use more functions and services through the watch account, including self-approval or revocation of relevant data changes, etc.", or display "Dear XXX parents, hello! Your child XXX is about to become an adult and can manage the watch account and related data on his own, including watch location, sports health, address book, photo album, stranger text messages" and other content to remind mobile phone users to be aware of the change process caused by the above-mentioned watch users growing to the corresponding age group, without limitation here.

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

[0145] For example, referring to FIG. 9 , if the watch 200 detects that the user has clicked the "Agree" control on the watch notification interface 920 or the data authorization interface 930, indicating that the user has confirmed the change, the user's confirmation of the change can be detected. At this point, the watch 200 can proceed to step 805 below to match the data management solution to be changed for the watch user.

[0146] 805: The watch 200 matches the data management solution corresponding to the next age group for the watch user.

[0147] For example, the watch 200 can match the data management solution to the watch user's current age group, i.e., the next age group. For example, if the next age group is a teenager, the watch user can be matched with data management solution B; if the next age group is an adult, the watch user can be matched with data management solution C, and so on.

[0148] The specific matching process can be referred to the relevant description in the above step 311 and will not be described in detail here.

[0149] 806: The watch 200 sets the watch-side permissions according to the data management plan corresponding to the next age group.

[0150] Specifically, according to the matched data management plan, the watch-side permissions and the corresponding related interfaces displayed on the watch 200 can be set by referring to the relevant description in the above step 311, which will not be repeated here.

[0151] 807: The watch 200 synchronizes the data management plan corresponding to the next age group to the children's cloud 300b.

[0152] 808: The mobile phone 100 requests the latest data management solution from the children's cloud 300b.

[0153] 809: The mobile phone 100 sets mobile phone permissions based on the acquired data management plan.

[0154] The specific implementation process of the above steps 807 to 809 can refer to the relevant descriptions in the above steps 312 to 314 respectively. The relevant interface displayed after the mobile phone 100 sets the mobile phone permissions can also refer to the relevant description in the above step 314, which will not be repeated here.

[0155] 810: The mobile phone 100 receives a user instruction to display an interface related to managing the watch.

[0156] For example, in response to the user opening the smart care application, the mobile phone 100 may run the smart care application and display a management interface provided by the smart care application for managing the watch 200. At this time, when the mobile phone 100 displays the running smart care application, it may trigger the execution of steps 811 to 818 described below.

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

[0158] For example, mobile phone 100 can request the watch user's age information from Child Cloud 300b. It should be understood that to facilitate management of watch account-related information, the watch account information stored on Account Cloud 300b can only be accessed, queried, and retrieved by watch 200 or Child Cloud 300b authorized by watch 200. When mobile phone 100 needs to obtain the watch user's age information, it can request the age information from Account Cloud 300a through Child Cloud 300b.

[0159] 812: The children's cloud 300b obtains the age information of the watch user based on the authorization token provided by the watch.

[0160] For example, the child cloud 300b can access the account cloud 300a to obtain the age information of the watch user based on the authorization token, such as the resource token (RT), obtained during the interaction with the watch 200.

[0161] In other embodiments, after the watch 200 establishes a binding relationship with the smart care application on the mobile phone 100, the watch 200 may also provide the aforementioned authorization token to the mobile phone 100, or the account cloud 300a may also provide an interface for the mobile phone 100 to access the watch account information, so that the mobile phone 100 can obtain the watch user's age information at any time. This application does not impose any restrictions on this.

[0162] 813: The children's cloud 300b sends the acquired age information to the mobile phone 100.

[0163] For example, after obtaining the age information of the watch user, the children's cloud 300b can return the age information to the mobile phone 100.

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

[0165] If the result of the judgment is yes, the following step 815 may be executed to notify the user to confirm whether the age is correct;

[0166] If the judgment result is no, then the process may return to step 810 .

[0167] For example, based on the received age information of the watch user, the mobile phone 100 can update the locally recorded age information and determine whether the watch user's age at this time meets a preset notification condition. The notification condition can be, for example, within a preset number of days before the watch user's age group changes to the next age group. For example, within 30 days before the watch user reaches the age of 14, that is, within 30 days before the watch user's age group changes to the adolescent stage, the mobile phone 100 can execute the following step 815 to notify. The above preset number of days can be 30 days, or it can be a reasonable preset value such as 28 days or 15 days, and is not limited here.

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

[0169] For example, after confirming that the received watch user age information meets the notification conditions, the mobile phone 100 may display a corresponding notification interface, such as displaying an interface to remind the user to check the age information or other notifications to the user to confirm whether the age is correct.

[0170] 816: The mobile phone 100 detects an operation to modify the age of the watch user.

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

[0172] 818: The account cloud 300a updates the current age group of the watch user.

[0173] For example, after receiving the modified age information of the watch user entered by the user via the smart care app on the mobile phone 100, the account cloud 300a can update the age information stored in the cloud space. For example, the account cloud 300a can replace the previously stored birthday with the modified birthday of the watch user. Furthermore, the account cloud 300a can determine the user's current age group based on the modified age information and update the age group tag associated with the watch user.

[0174] It can be understood that in the embodiment of the present application, the management of privacy data mainly includes changes in user agreements and privacy statements. Users can enter the privacy center on the watch 200 or mobile phone 100 to view the user agreement and privacy statement, which will not be elaborated here. When the user agreement or privacy statement changes, the user can be notified through the relevant interface of the watch 200 or mobile phone 100. Different specific data management schemes may correspond to different notification methods and notification contents on the watch 200 or mobile phone 100. In the embodiment of the present application, different privacy center entrances can be set for the watch side and the mobile phone side to separate the user agreement and privacy statement of the watch 200 from the smart care application on the mobile phone 100, and the watch user agreement and privacy statement can be authorized for the watch 300 when binding the watch 200. The details are as follows:

[0175] Watch side: When the smart care app on mobile phone 100 is bound to the watch, the watch user agreement and privacy statement can be authorized, and change notifications can be supported. A privacy center entrance can be added to the watch 200 to view and manage the watch user agreement and privacy statement. At the same time, the watch 200 can support independently controlled data acquisition controls, including data synchronization switches for watch location, exercise data, address book, photo album, stranger text messages, etc. In different data authorization schemes, the switch status of the above data synchronization switches can be set on the watch side or not. For details, please refer to the relevant description in the above step 311.

[0176] On the phone side: A privacy center entry can be added to the corresponding interface of the smart care app to view and manage the watch user agreement and privacy statement. Furthermore, the smart care app on phone 100 can also support independently controlled data collection switches, including synchronization of watch location, exercise data, address book, photo album, stranger text messages, and other data. In different data authorization schemes, the on / off status of these data synchronization switches can be set on the phone side, either to or not. For details, please refer to the relevant description in step 314 above. This is not detailed here.

[0177] It will be appreciated that when changes are made to the user agreement or privacy statement, Child Cloud 300b can notify both the watch 200 and the phone 100 based on the communication connection between them. Once the user confirms the changes via the phone 100 or watch 200, the flag information associated with the user agreement or privacy statement stored on Child Cloud 300b can be changed accordingly. Thus, if the watch user's age changes or they reach a new age group, Child Cloud 300b can update the phone 100 or watch 200 with the user's consent to the changed user agreement or privacy statement based on the change in the flag information.

[0178] For different data authorization schemes, for example, when the watch user is under 14 years old, as shown in FIG2 , the children's cloud 300b can notify the mobile phone 100 of the above changes, and the mobile phone 100 can display a corresponding interface to notify the user. The notification interface can be shown in FIG10A .

[0179] As shown in FIG10A , after receiving the privacy change notification message from the Child Cloud 300b, the mobile phone 100 may display a change notification 1011 on the guardian interface 1010 of the running smart care application. At this point, the user can click on "Change Details," "Watch User Agreement," "Statement on Watch Services and Privacy," and other content in the change notification 1011 to view the details. After reviewing the relevant content after the change, the user can click on the "Agree" control 1012 on the change notification 1011 to agree to the change. In some embodiments, the user can also click on the "Cancel" control 1013 on the change notification 1011 to reject the change, at which point the mobile phone 100 may display a prompt box 1021 on the guardian interface 1020.

[0180] Continuing with reference to FIG10A , the prompt box 1021 may display, for example, content such as “If you do not agree to the update changes, you will not be able to view and manage XXXX’s watch information. If you confirm, please unbind the watch first to avoid affecting the normal use of the watch” to guide the user to click the “Agree” control 1012 in the above change notification 1011. In some embodiments, the user can click the “View Changes” control 1022 on the guardian interface 1020 to view the above-mentioned “Change Details”, “Watch User Agreement”, “Statement on Watch Services and Privacy” and other related changes, which will not be repeated here. The user can also click the “Unbind Watch” control 1023. At this time, the mobile phone 100 may have a related interface for the unbinding control for the user to operate to unbind the smart care application running on the mobile phone 100 from the watch 200.

[0181] When the watch user reaches or exceeds 14 years old, as shown in FIG2 , the child cloud 300b can notify the watch 200 of the above change, and the watch 200 will display a corresponding interface to notify the user. The notification interface can be shown in FIG10B .

[0182] As shown in Figure 10B, after receiving the privacy change notification message notified by the Children's Cloud 300b, the watch 200 can display the privacy center notification 1040. The content of the notification 1040 can be "In order to provide better service, we have updated the privacy statement and user agreement", etc. The user can click on the content of the notification 1040 to view the detailed notification. At this time, the watch 200 can display the content of "Change Details", "Watch User Agreement", and "Statement on Watch Services and Privacy" in response to the user's operation. After the user reviews the relevant content after the change, he can agree or reject the change of the relevant content. If the user rejects the change of the relevant content, the watch 200 can further display relevant notifications to remind the user to unbind the watch, etc., which will not be repeated here.

[0183] FIG11 shows a schematic diagram of the architecture of a data management system for implementing the above-mentioned data management method according to an embodiment of the present application.

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

[0185] Specifically, a mobile phone user can open the smart care app 101 and bind the watch 200. During the binding process, the smart care app 101 creates a new watch account for the watch 200 and logs in the watch account. The corresponding watch account information and login status are then synchronized to the account cloud 300a. The account cloud 300a uses the age information in the watch account information to determine the watch user's age group and add an age group tag to the watch user or the corresponding watch account information.

[0186] The watch 200 accesses the account cloud 300a via Wi-Fi or a cellular data network supported by the watch SIM card, and can obtain the age group of the watch user recorded in the corresponding watch account in real time, and match the watch user with a data management plan corresponding to his or her age group.

[0187] The watch 200 system can be installed with a toolkit 201, a settings application 202, a data synchronization switch 203, and more. The watch 200 can transmit an authorization token to the Child Cloud 300b via the Account Toolkit 201, allowing the Child Cloud 300b to query the Account Cloud 300a for information such as the watch user's age, as recorded in the watch account. The watch 200 can use the Privacy Center in the Settings application 202 to query the Account Cloud 300a for the watch user's age group, the status of the data synchronization switch between the watch 200 and the Child Cloud 300b, and push growth notifications to the Child Cloud 300b. The data synchronization switch status between the watch 200 and the Child Cloud 300b can be synchronized when the watch 200 is bound to the Smart Care application 101 or when a change notification is received. This change notification can be, for example, a notification corresponding to a change in the data synchronization switch status. The growth notification can be, for example, the notification pushed by the Child Cloud 300b to the Smart Care application on the mobile phone 100, as exemplified in step 803 above, without limitation.

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

[0189] Correspondingly, the watch 200 may also include a data / switch status database for synchronizing the watch user's personal privacy data collected on the watch 200. The privacy center of the watch 200 can synchronize the watch user's personal privacy data collected, as well as the status of the data synchronization switch set by the user on the watch 200, to this database. The database may default to enabling transmission of values ​​corresponding to the data switch status on the watch 200. The user may also disable the database's transmission channel for data / switch status through settings on the watch 200, without limitation. The watch 200 can decide whether to upload the watch's private data, etc., to the children's cloud 300b based on the switch status recorded in this database.

[0190] The child cloud 300b can obtain the age information of the watch user from the account cloud 300a according to the token for query by the smart care application 101. The child cloud 300b can decide whether to synchronize the private data on the watch to the smart care application 101 according to the switch status of the data synchronization switch.

[0191] The mobile phone 100 can launch the smart care application 101 in response to user operations. The smart care application 101 can establish a communication connection with the child cloud 300b via Wi-Fi or a cellular data network supported by the mobile phone's SIM card. The smart care application 101 can also query the child cloud 300b for the watch user's age information, receive growth notifications pushed by the child cloud 300b, and synchronize the status of the data synchronization switch with the child cloud 300b.

[0192] It can be understood that the specific interaction process between the account cloud 300a, watch 200, child cloud 300b and mobile phone 100 in the data management system 1100 shown in Figure 11 can refer to the relevant descriptions of each step in the interaction process shown in Figures 3 and 8 above, and will not be repeated here.

[0193] Based on the data management system shown in FIG11 , FIG12 shows a schematic diagram of an implementation flow of another data management method according to an embodiment of the present application.

[0194] It is understood that the execution entity of each step of the process shown in Figure 12 can be the data management system 1100 shown in Figure 11. The mobile phone 100 running the smart care application 101 included in the system 1100 can be called the management device, and the watch 200 can be called the managed device.

[0195] Specifically, the process shown in FIG12 may include the following steps:

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

[0197] The specific implementation process of establishing the binding relationship can refer to the relevant descriptions in steps 301 to 309 shown in Figure 3 above, and will not be repeated here.

[0198] 1202: Determine an initial data management plan based on the age group of the user of the managed device.

[0199] The specific implementation process of determining the initial data management solution can refer to the relevant descriptions in steps 310 to 314 shown in FIG3 , and will not be described in detail here.

[0200] 1203: Detect changes in the age group of users of managed devices.

[0201] For example, the user of the managed device may be the watch user. The specific implementation process of detecting the age change of the user of the managed device may refer to the relevant description in step 801 shown in FIG8 , which will not be repeated here.

[0202] 1204: Determine whether the age group of the user of the managed device has changed.

[0203] If the judgment result is yes, that is, the age group of the user of the managed device has changed, the data management system 1100 may further execute the implementation process of the following steps 1205 to 1207.

[0204] If the judgment result is no, that is, the age group of the user of the managed device has not changed, the data management system 1100 may return to the above step 1203 to continue detecting whether the age group of the user of the managed device has changed.

[0205] For example, the age change of the user of the managed device may be from childhood to adolescence, or from adolescence to adulthood, etc., correspondingly describing the change process between two adjacent age groups. The above determination process can be specifically described in the relevant description of the detection process in step 802 shown in Figure 8 above, and will not be repeated here.

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

[0207] 1206: Match the corresponding data authorization plan according to the user's age group and make changes.

[0208] For example, the data management solution A can be matched with the user's age group a, the data management solution B can be matched with the user's age group b, the data management solution C can be matched with the user's age group c, and so on, the data management solution N can be matched with the user's age group n.

[0209] It can be understood that determining the age group of the user based on the user's age information and matching the corresponding data management plan to each age group can be flexibly set according to actual needs, and this application does not impose any restrictions here.

[0210] 1207: End of data authorization change plan.

[0211] The above steps 1205 to 1207 are the specific implementation process of the user matching data management plan of the managed device and changing it. Please refer to the relevant description in steps 803 to 809 shown in Figure 8 above, and will not be repeated here.

[0212] FIG13 shows a schematic block diagram of the structure of an electronic device 1300 according to an embodiment of the present application.

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

[0214] The electronic device 1300 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging 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 button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0215] It should be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 1300. In other embodiments of the present application, the electronic device 1300 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0216] The processor 110 may include one or more processing units. For example, the processor 110 may 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). The different processing units may be independent devices or integrated into one or more processors.

[0217] The controller can generate an operation control signal based on the instruction opcode and timing signal to complete the control of instruction fetching and instruction execution. In the embodiment of the present application, the processor 110 can control instruction fetching and instruction execution through the controller to implement the data management method provided by the embodiment of the present application. For example, the processor 110 can control instruction fetching and instruction execution through the controller to implement the steps corresponding to the steps implemented by the mobile phone 100 or the watch 200 in the interaction process shown in Figures 3 or 8 above.

[0218] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0219] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may 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.

[0220] USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. USB interface 130 can be used to connect a charger to charge electronic device 1300 and to transfer data between electronic device 1300 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as AR devices.

[0221] It is understood that the interface connection relationship between the modules illustrated in the embodiment of the present invention is merely an illustrative illustration and does not constitute a structural limitation on the electronic device 1300. In other embodiments of the present application, the electronic device 1300 may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0222] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the electronic device 1300. While charging the battery 142, the charging management module 140 can also provide power to the electronic device via the power management module 141.

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

[0224] The wireless communication function of the electronic device 1300 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0225] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 1300 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

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

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

[0228] Electronic device 1300 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

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

[0230] 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. The ISP is used to process data fed back by the camera 193 .

[0231] Camera 193 is used to capture still images or video. The lens generates an optical image of an object and projects it onto a photosensitive element. The photosensitive element converts the optical signal into an electrical signal, which is then transmitted to the ISP for conversion 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 an image signal in a standard format, such as RGB or YUV.

[0232] The digital signal processor is used to process digital signals. In addition to processing 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.

[0233] Video codecs are used to compress or decompress digital video. Electronic device 1300 may support one or more video codecs. This allows electronic device 1300 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0234] 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.

[0235] The internal memory 121 can be used to store computer executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store an operating system, applications required for at least one function, etc. The data storage area may store data created during the use of the electronic device 1300, etc. In an embodiment of the present application, the application stored in the program storage area may be a smart care application for managing a watch, and the data stored in the data storage area may be the latest data management solution collected and received during the operation of the smart care application by the electronic device 1300. Based on the latest data management solution, the electronic device 1300 may set corresponding mobile phone permissions. No limitation is imposed here.

[0236] In addition, the internal memory 121 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 1300 by running instructions stored in the internal memory 121 and / or instructions stored in a memory provided in the processor. In an embodiment of the present application, for example, the processor 110 of the electronic device 1300 may run instructions stored in the internal memory 121 for executing the steps corresponding to the steps implemented by the mobile phone 100 or the watch 200 in the interaction process shown in Figures 3 or 8 above, so as to match corresponding data management solutions for watch users of different age groups to manage data or switch status on the watch.

[0237] The electronic device 1300 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0238] The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air 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, etc., which will not be elaborated here.

[0239] The buttons 190 include a power button, a volume button, and the like. The buttons 190 may be mechanical buttons or touch buttons. The electronic device 1300 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 1300.

[0240] Motor 191 can generate vibration prompts.

[0241] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0242] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or disconnected from the electronic device 1300 by inserting or removing the SIM card into or from the SIM card interface 195 .

[0243] FIG14 shows a block diagram of a software system structure of a mobile phone 100 according to an embodiment of the present application.

[0244] 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. In the embodiment of the present invention, the Android system with a layered architecture is used as an example to illustrate the software structure of the mobile phone 100.

[0245] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0246] As shown in Figure 14, the application layer may include a series of application packages. The application packages may include smart care, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications. The smart care application is bound to the watch 200 and interacts with the child cloud 300b and the account cloud 300a to implement the data management method provided in the embodiment of the present application.

[0247] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0248] As shown in FIG14 , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

[0249] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0250] Content providers are used to store and retrieve data and make it accessible to applications. This data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0251] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0252] The phone manager is used to provide communication functions of the mobile phone 100, such as management of call status (including answering, hanging up, etc.).

[0253] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0254] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0255] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

[0256] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0257] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0258] The system library can include multiple functional modules, such as surface manager, media libraries, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

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

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

[0261] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0262] A 2D graphics engine is a drawing engine for 2D drawings.

[0263] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0264] The embodiments of the present application also provide a computer program product for implementing the data management method provided in the above embodiments.

[0265] The various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can be implemented as computer program modules or module codes executed on a programmable system, which includes 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.

[0266] A computer program module 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 having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

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

[0268] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, instructions may be distributed over a network or through other computer-readable media. Therefore, a machine-readable medium may include any mechanism for storing or transmitting information in a machine (e.g., computer) readable form, including but not limited to floppy disks, optical disks, optical discs, read-only memories (CD-ROMs), magneto-optical disks, read-only memories (ROMs), random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or a tangible machine-readable memory for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in electrical, optical, acoustic, or other forms of propagation signals. Accordingly, machine-readable media includes any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (eg, a computer).

[0269] References in the specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one exemplary implementation or technique disclosed according to the embodiment of the present application. The appearances of the phrase "in one embodiment" in various places in the specification do not necessarily all refer to the same embodiment.

[0270] The disclosure of the embodiments of the present application also relates to an operating device for executing the text. The device can be constructed specifically for the required purpose or it can include a general-purpose computer that is 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 a floppy disk, an optical disk, a CD-ROM, a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic or optical card, an application-specific integrated circuit (ASIC) or any type of medium suitable for storing electronic instructions, and each can be coupled to a computer system bus. In addition, the computer mentioned in the specification can include a single processor or can be an architecture involving multiple processors for increased computing power.

[0271] In addition, the language used in this specification has been primarily selected for readability and instructional purposes and may not be selected to describe or limit the disclosed subject matter. Therefore, the present disclosure of embodiments is intended to illustrate, not to limit, the scope of the concepts discussed herein.

Claims

1. A data management method, applied to a first electronic device, characterized in that: include: determining an age group of the first user; If the age group of the first user belongs to the first age group, display a first control, the first control is used to control the permission of the second electronic device to obtain the first data, and the second electronic device is used to manage the first electronic device; In response to the first user's operation on the first control, allowing or prohibiting the second electronic device from acquiring the first data; If the age of the first user belongs to the second age group, the first control is not displayed.

2. The method according to claim 1, characterized in that The determining the age group of the first user includes: Sending a first query request to a first cloud server, wherein the first query request is used to obtain an age group label in information related to a 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 information related to the first account; The age group of the first user is determined according to the acquired age group label.

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 age group and the fourth age group are continuous intervals, the age of the third age group is higher than the age of the fourth age group, and the method includes: If the age group of the first user belongs to the third age group, displaying a second control, where the second control is used to control the authority of the first electronic device to collect and report second data; In response to the first user's operation on the second control, allowing or prohibiting the first electronic device from collecting and reporting the second data; If the age group of the first user belongs to the fourth age group, the second control is not displayed.

4. The method according to claim 3, characterized in that The second data includes log data generated when the first user uses the first electronic device, and the log data includes any one of a behavior log of the first user and an error log of the first electronic device.

5. The method according to claim 3, characterized in that: The age intervals corresponding to the first age group and the second age group are continuous intervals, and the age of the first age group is higher than the age of 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 allowing or prohibiting the second electronic device from acquiring the first data in response to the first user's operation on the first control includes: In response to a first operation by a first user to set the state of the first control to an on state, allowing the second electronic device to obtain the first data; In response to a second operation by the first user to set the state of the first control to a closed state, the second electronic device is prohibited from acquiring the first data.

7. The method according to claim 3, characterized in that The allowing or prohibiting the first electronic device from collecting and reporting the second data in response to the first user's operation on the second control includes: In response to a third operation of the first user setting the state of the second control to an on state, allowing the first electronic device to collect and report the second data; In response to a fourth operation of the first user setting the state of the second control to a closed 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: A control for synchronizing the location information of the first electronic device to a second cloud server; A control for synchronizing the motion information recorded by the first electronic device to a second cloud server; Used to synchronize controls corresponding to the address book stored on the first electronic device to the second cloud server; A control corresponding to the album data of the first electronic device is used to synchronize with the second cloud server; Used to synchronize controls corresponding to stranger text messages received by the first electronic device to the second cloud server; A control for controlling 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; exercise records; address book; photo album data; text messages from strangers.

10. The method according to claim 9, characterized in that The allowing or prohibiting 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: 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 used to control the second electronic device's permission to obtain the first data; Confirming that the first electronic device does not display the first control, and the second electronic device displays the first control; In response to the second user setting the state of the first control to an on state, the second electronic device acquires the first data of the first electronic device.

12. The method according to claim 11, characterized in that The method further comprises: 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 used to control the authority of the first electronic device to collect and report second data; It is confirmed that the first electronic device does not display the second control, and the second electronic device displays the second control.

13. A data management system, characterized in that: The system comprises 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 used to execute the data management method according to any one of claims 1 to 10 based on the first communication connection and the second communication connection; The second electronic device is used to execute the data management method according to 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 store one or more programs, and when the one or more programs are executed by the one or more processors, the electronic device executes the data management method according to any one of claims 1 to 12.

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

Citation Information

Patent Citations

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

    CN119004430A

  • Information display method anddevice, equipment and storage medium

    CN111459587A

  • Information processing method and device, equipment and storage medium

    CN111782971A

  • Method and device for controlling mother-son machine and mother-son machine system

    CN113656769A

  • Unlocking permission processing method and system

    CN113742688A