Pet interaction method and electronic device

Abstract

Disclosed in the embodiments of the present application are a pet interaction method and an electronic device. The method can be applied to a first electronic device. The method comprises: a first electronic device displaying a first interface, wherein the first interface comprises a first object, the first object is in a first state on the first interface, and the first interface comprises a lock screen interface; and upon detecting an unlocking operation on the first interface, the first electronic device displaying a second interface, wherein the second interface comprises the first object, the first object is in a second state on the second interface, the second state is different from the first state, and the second interface is a desktop. In the embodiments of the present application, a first object can be a system-level electronic pet, which can have system-level permissions, provide diverse functional interaction modes, and further realize cross-device movement, thereby improving the playability of the electronic pet.

Description

A pet interaction method and electronic device

[0001] This application claims priority to Chinese Patent Application No. 202411815768.4, filed on December 10, 2024, entitled "A Pet Interaction Method and Electronic Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminal technology, and in particular to a pet interaction method and electronic device. Background Technology

[0003] With the development of technology, electronic devices have gradually become an indispensable tool in people's lives. Desktop pets are software products that simulate real pets on the desktop of electronic devices, allowing them to interact with users and satisfy their emotional needs. Currently, there are many desktop pet applications (APPs) on the market; however, these desktop pet apps currently available have relatively simple interactive methods and functions, offering limited user experience. Summary of the Invention

[0004] This application provides a pet interaction method and an electronic device. The method can be applied to a first electronic device. The first electronic device displays a first interface, which includes a first object. The first object is in a first state on the first interface, and the first interface includes a lock screen. Upon detecting an unlock operation on the first interface, the first electronic device can display a second interface. This second interface includes the first object, and the first object is in a second state on the second interface, which is different from the first state. The second interface is a desktop. In this embodiment, the first object can be a system-level electronic pet. This system-level electronic pet can have system-level permissions, provide rich interactive functions, and enable cross-device movement, thus improving the playability of the electronic pet.

[0005] In a first aspect, this application provides a pet interaction method applied to a first electronic device. The method includes: the first electronic device displaying a first interface, the first interface including a first object, the first object being in a first state on the first interface, and the first interface including a lock screen interface; detecting an unlock operation on the first interface, and displaying a second interface, the second interface including the first object, the first object being in a second state on the second interface, the second state being different from the first state, and the second interface being a desktop.

[0006] The first electronic device can be the electronic device 100 shown in Figure 1, the first interface can be the lock screen interface, the first object can be the system-level electronic pet, the first state can be the state of the electronic pet on the lock screen interface, the second interface can be the desktop, and the second state can be the state of the electronic pet on the desktop.

[0007] In this embodiment of the application, the system-level electronic pet can have system-level permissions, provide a variety of interactive functions, and move across devices, thereby improving the playability of the electronic pet.

[0008] It should be noted that system-level permissions may include, but are not limited to, one or more of the following: voice interaction, application installation, application update, application uninstallation, power on, power off, and permission to change system settings. With these system-level permissions, the electronic pet will not remain in the background when the electronic device's screen is off, thus releasing occupied resources; when the screen is on, the electronic pet will be activated and will then retrieve resources from the operating system.

[0009] It's important to note that a system-level electronic pet is essentially a system application. Because a system-level electronic pet can access data from a unified desktop environment, including the Always On Display (AOD) interface, lock screen, desktop, control center, notification center, and status bar, as well as user interface (UI) elements such as application icons, application cards, and folder icons, it can further perceive the location of this unified desktop and its UI elements. This allows the system-level electronic pet to detect operations performed on this unified desktop and its UI elements, and consequently, control changes in the pet's state. In other words, the interactive functions provided by this system-level electronic pet can include interactions between the pet and the aforementioned unified desktop and its UI elements. It should be noted that the first and second interfaces mentioned above both belong to the unified desktop environment.

[0010] It should be noted that the Unified Desktop is a type of system software. The Unified Desktop may include one or more of the following: an AOD (Always-On Display) interface, a lock screen interface, a desktop, a control center, a notification center, a status bar, a multitasking interface, and a gesture module. This application embodiment does not limit the type or number of modules included in the Unified Desktop. Furthermore, the modules included in the Unified Desktop share a single process, and these modules can communicate internally with each other.

[0011] By implementing the method provided in the first aspect, the electronic device 100 can associate the state of the electronic pet with the user's operation on the unified desktop, so that when the operation on the unified desktop is detected, the electronic device 100 can control the state of the electronic pet to change, thereby improving the flexibility and fun of the electronic pet and enriching the interaction between the user and the electronic pet.

[0012] In conjunction with the first aspect, in some embodiments, the first state of the first object includes one or more of the following: the position of the first object, the shape of the first object, the expression of the first object, and the posture of the first object.

[0013] It should be noted that the state of the electronic pet may include one or more of the following: the electronic pet's location, the electronic pet's appearance, the electronic pet's expression, and the electronic pet's posture. This application embodiment does not limit the specific form in which the electronic pet's state is displayed. Specifically, a change in the electronic pet's location can be understood as the electronic pet moving to a certain position; a change in the electronic pet's appearance may include, but is not limited to, a change in body size; a change in expression may be, for example, from closed eyes to open eyes, from smiling to angry, etc.; and a change in posture may include, but is not limited to, a change in movement, such as from lying down to standing, from standing to walking, rotating, jumping, etc.

[0014] In conjunction with the first aspect, in some embodiments, the method further includes: when the first electronic device switches from displaying a first interface to displaying a second interface, the first object changes from a first state to a second state according to a first motion effect, wherein the parameters of the first motion effect include one or more of the following: a first moving speed and a first moving trajectory.

[0015] The first animation effect can be a dynamic effect that changes the state of the electronic pet between the first interface and the second interface.

[0016] It should be noted that the electronic pet's state can change according to animation effects, which can be dynamic effects showing the change of the electronic pet's state between two interfaces. The parameters of the animation effects can include one or more of the following: movement speed and movement trajectory. A change in the electronic pet's movement trajectory can be understood as the type of curve the electronic pet moves along, such as moving in a straight line or along a curve; a change in the electronic pet's movement speed can be understood as a change in the instantaneous speed of the electronic pet during movement. The electronic pet can move at a constant speed or with varying speed, and this embodiment does not limit this. It is understood that the aforementioned electronic pet's movement trajectory and movement speed can be preset, i.e., configured by the electronic pet application or operating system; or they can be specified by the user, and this embodiment does not limit the method of user specification.

[0017] In conjunction with the first aspect, in some embodiments, the lock screen interface is an always-on lock screen interface.

[0018] This always-on display (AOD) lock screen interface can be understood as an AOD interface.

[0019] In conjunction with the first aspect, in some embodiments, the lock screen interface is a lock screen interface that is on when the screen is lit. Before the first electronic device displays the first interface, the method further includes: displaying an always-on display (AOD) interface, the AOD interface including a first object, the first object being in a third state, the third state being different from the first state; and detecting an operation to light up the screen of the AOD interface.

[0020] The third state can be the status of the electronic pet on the AOD interface.

[0021] As shown in Figures 6A-6D, in some embodiments, the unified desktop may include an AOD (Ahead-of-Date) interface, and the operation detected by the electronic device 100 on the AOD interface may include turning on the screen. The first interface may include a lock screen interface, and the operation detected by the electronic device 100 on the first interface may include an unlocking operation. It should be noted that the lock screen interface can be a lock screen interface that is turned on. In response to the operation of turning on the screen of the AOD interface, the electronic device 100 can display the lock screen interface. Both the AOD interface and the lock screen interface include an electronic pet, but the state of the electronic pet on the lock screen interface has changed compared to the state of the electronic pet on the AOD interface. That is, the electronic pet is in a third state on the AOD interface and in a first state on the lock screen interface, and the third state is different from the first state. Optionally, when the electronic device 100 switches from displaying the AOD interface to displaying the lock screen interface, the electronic pet can change from the third state to the first state according to an animation effect. The parameters of the animation effect include one or more of the following: movement speed, movement trajectory. This application embodiment does not limit the form of the animation effect. The second interface may be a desktop. In response to the unlocking operation of the lock screen, the electronic device 100 can display the desktop. Both the lock screen and the desktop include the electronic pet, but the state of the electronic pet on the desktop changes compared to its state on the lock screen. That is, the electronic pet is in a first state on the lock screen and in a second state on the desktop, and the second state is different from the first state. Optionally, when the electronic device 100 switches from displaying the lock screen to displaying the desktop, the electronic pet can change from the first state to the second state according to a first animation effect. The parameters of the first animation effect include one or more of the following: a first movement speed and a first movement trajectory. This embodiment of the application does not limit the form of the first animation effect.

[0022] In the above embodiments, during the user's continuous operations of turning on the screen and unlocking the device, the AOD interface, lock screen interface, and desktop are displayed sequentially and continuously, and the status of the electronic pet displayed sequentially on the AOD interface, lock screen interface, and desktop also changes continuously.

[0023] It should be noted that the change in the electronic pet's state controlled by electronic device 100 specifically refers to a change in the electronic pet's state after detecting an operation on the unified desktop compared to the state before detecting the operation. Upon detecting an operation to light up the screen on the AOD interface, electronic device 100 can control the electronic pet's state to change from the third state to the first state, where the first state is different from the third state. Upon detecting a successful unlocking of the lock screen interface, electronic device 100 can control the electronic pet's state to change from the first state to the second state, where the second state is different from the first state. It can be understood that the second state can be different from the third state, or it can be the same as the third state.

[0024] In this way, since the AOD interface, lock screen interface, and desktop are all part of a unified desktop, the AOD interface, lock screen interface, and desktop share a single process, thereby avoiding cross-process calls to the electronic pet by the electronic device 100 when displaying the AOD interface, lock screen interface, and desktop in sequence.

[0025] In conjunction with the first aspect, in some embodiments, the desktop includes application icons, a first object is located around the application icons, and the method further includes: detecting an operation on the application icons, the first object on the desktop changing from a second state to a fourth state, the fourth state being different from the second state, wherein the operation on the application icons includes long-pressing the application icons, dragging the application icons, unloading the application icons, and clicking the application icons.

[0026] The fourth state can be the state of the electronic pet after detecting an action on the application icon.

[0027] In some embodiments, the desktop may include application icons, and the electronic pet may be located around the application icons, in which case the electronic pet may be in a second state. It should be noted that the electronic pet being displayed around the application icons can be understood as the distance between the electronic pet and the application icons being less than a preset distance (e.g., 0.5 cm), for example, the electronic pet being displayed on the application icons. Upon detecting an operation on the application icons, the electronic pet on the desktop can change from the second state to a fourth state, which is different from the second state. The operations detected by the electronic device 100 on the application icons may include long-pressing the application icon, dragging the application icon, uninstalling the application icon, and clicking the application icon. Furthermore, operations on the application icons may also include installing the application icon and updating the application icon. This embodiment does not limit the type of operation on the application icons. Optionally, the electronic pet can change from the second state to the fourth state according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed and movement trajectory. This embodiment does not limit the form of the animation effect.

[0028] In conjunction with the first aspect, in some embodiments, when the operation on the application icon is a long press on the application icon, the first expression of the first object in the fourth state changes relative to the second expression of the first object in the second state; when the operation on the application icon is dragging the application icon, the first position of the first object in the fourth state changes relative to the second position of the first object in the second state; and when the operation on the application icon is uninstalling the application icon, the third position of the first object in the fourth state changes relative to the fourth position of the first object in the second state.

[0029] The first emoticon can be the emoticon of the virtual pet after a long press operation on the app icon is detected; the second emoticon can be the emoticon of the virtual pet before a long press operation on the app icon is detected; the first position can be the position of the virtual pet after a drag operation on the app icon is detected; the second position can be the position of the virtual pet before a drag operation on the app icon is detected; the third position can be the position of the virtual pet after an uninstall operation on the app icon is detected; and the fourth position can be the position of the virtual pet before an uninstall operation on the app icon is detected.

[0030] For example, before detecting a long press on the app icon, the electronic device 100 can control the electronic pet to be in a sleeping state on the app icon. After detecting a long press on the app icon, the electronic device 100 can control the electronic pet to change from a sleeping state to a awake state.

[0031] For example, before detecting an operation to drag the application icon, the electronic device 100 can control the electronic pet to remain silent on the application icon. After detecting the operation to drag the application icon, the electronic device 100 can control the electronic pet to be dragged along with the application icon.

[0032] For example, before detecting the operation of uninstalling the application icon, the electronic device 100 can control the electronic pet to be in a sleeping state on the application icon. After detecting the operation of uninstalling the application icon, the electronic device 100 can control the electronic pet to leave the application icon and jump to another application icon.

[0033] In conjunction with the first aspect, in some embodiments, the desktop includes an application icon, and the method further includes: in response to a click operation on the application icon, displaying a third interface, the third interface including the user interface and status bar of the application corresponding to the application icon, the third interface further including a first object, the first object being displayed in the status bar.

[0034] The third interface can be the user interface after the click on the application icon is detected, and it can include the user interface and status bar of the application corresponding to the application icon.

[0035] In conjunction with the first aspect, in some embodiments, when the first object is displayed in the status bar, the first object is in a fifth state, which is different from the second state.

[0036] The fifth state can be the state of the electronic pet on the third interface.

[0037] In conjunction with the first aspect, in some embodiments, the method further includes: when the first electronic device switches from displaying a second interface to displaying a third interface, the first object changes from a second state to a fifth state according to a second motion effect, wherein the parameters of the second motion effect include one or more of the following: a second moving speed and a second moving trajectory.

[0038] The second animation effect can be a dynamic effect that changes the state of the electronic pet between the second and third interfaces.

[0039] As shown in Figures 12A-12C, in some embodiments, the operation on the application icon detected by the electronic device 100 may be a click on the application icon. In response to the click on the application icon, the electronic device 100 can launch the application corresponding to the application icon and display a third interface. This third interface may include the user interface and status bar of the application corresponding to the application icon. The third interface also includes an electronic pet, which can be displayed in the status bar. At this time, the electronic pet is in a fifth state, which is different from the second state. During the launch of the application corresponding to the application icon, the electronic device 100 can display the application's launch animation. It should be noted that after detecting the click on the application icon, launching the application requires a preset time (e.g., 0.2 seconds). During the waiting period for the application to launch, the electronic device 100 can display the application's launch animation. This launch animation adds a transition between the desktop and the third interface, which helps to facilitate a smooth transition of the user interface displayed by the electronic device 100 from the desktop to the third interface, improving the user experience. When displaying the application's launch animation, the electronic device 100 can control the electronic pet to change from being displayed around the application icon to being displayed within the launch animation. After launching the application corresponding to the application icon, the electronic device 100 can control the electronic pet's display position to change to the status bar. The user interface after the application is launched is displayed in full screen. That is, when the electronic device 100 switches from displaying the desktop to the application's user interface, the electronic pet can change from a second state to a fifth state according to a second animation effect. The parameters of the second animation effect include one or more of the following: a second movement speed, a second movement trajectory. This application embodiment does not limit the form of the second animation effect. For example, the application launch animation effect can be that the application window gradually enlarges until the application's user interface is displayed in full screen. After controlling the electronic pet to change from being displayed around the application icon to being displayed in the launch animation effect, the electronic device 100 can control the electronic pet to gradually move its position following the application window, and can control at least one of the electronic pet's appearance, posture, and expression to change during the electronic pet's movement. For example, during the electronic pet's movement, the electronic device 100 can control the electronic pet's size to gradually decrease until it enters the status bar, at which point the electronic pet's size stops decreasing, so that the electronic pet's size reaches its minimum size during the size change process when it enters the status bar. In addition to controlling the changes in the size of the electronic pet, the electronic device 100 can also control the changes in the posture of the electronic pet, such as rotating or jumping; the electronic device 100 can also control the changes in the facial expressions of the electronic pet, such as smiling or crying.

[0040] In conjunction with the first aspect, in some embodiments, the desktop wallpaper has a pet interactive element, the second state includes a fifth position of the first object, the fifth position being a position around the pet interactive element; the method further includes: the first object changing from the second state to a sixth state on the desktop, the sixth state including a sixth position of the first object, the sixth position being a position around a first user interface (UI) element, the first UI element including one or more of the following: application icon, application card, folder icon.

[0041] The fifth position can be the position around the pet interaction element, and the sixth state can be the state of the electronic pet around the first UI element on the desktop. The sixth position can be the position around the first UI element, and the first UI element can be elements such as application icons, application cards, and folder icons contained in the user interface.

[0042] As shown in Figures 16A-16B, in some embodiments, the unified desktop may include a desktop wallpaper containing pet interactive elements (e.g., pet bed, pet toys, pet food, etc.). The desktop may include an electronic pet in a second state, which may include a fifth position of the electronic pet, the fifth position being the position around the pet interactive elements; that is, the electronic pet may be displayed around the pet interactive elements. As mentioned above, the desktop wallpaper is the background image used by the desktop of the electronic device 100, located below the layer of first UI elements such as application icons, application cards, and folder icons. The electronic pet may be located on the same layer as the desktop wallpaper. The electronic device 100 can control the electronic pet to leave the area around the pet interactive elements. Optionally, before controlling the electronic pet to leave the area around the pet interactive elements, the electronic device 100 may detect an input operation on the desktop (e.g., a click operation on a non-UI element on the desktop). For example, the electronic pet leaving the vicinity of the pet interaction element can specifically include the electronic pet changing from a second state to a sixth state on the desktop. This sixth state can include the electronic pet's sixth position, which is a position around a first UI element. The first UI element can include one or more of the following: application icons, application cards, and folder icons. This embodiment does not limit the type of the first UI element. That is, the electronic pet can change from being displayed around the pet interaction element to being displayed around the first UI element. It should be noted that displaying the electronic pet around the pet interaction element can be understood as the distance between the electronic pet and the pet interaction element being less than a preset distance (e.g., 0.5 cm), for example, the electronic pet being displayed inside a pet bed. Displaying the electronic pet around the first UI element can be understood as the distance between the electronic pet and the first UI element being less than a preset distance (e.g., 0.5 cm), for example, the electronic pet being displayed on an application icon. Optionally, the electronic pet can change from the second state to the sixth state according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed and movement trajectory. This embodiment does not limit the form of the animation effect.

[0043] It should be noted that the electronic pet leaving the pet interaction element can include not only changing the electronic pet's display position from around the pet interaction element to around the first UI element, but also changing its display position from around the pet interaction element to a position on the desktop other than the first UI element. This application embodiment does not limit the display position of the electronic pet after leaving the pet interaction element.

[0044] It should be noted that HeYi Desktop can provide desktop wallpapers containing pet interactive elements. At the software level, the desktop wallpaper containing pet interactive elements is actually a software interface. This interface can be used to send data to the pet management module so that the pet management module can perceive the desktop wallpaper containing pet interactive elements, and thus enable the pet management module to interact with the pet interactive elements in the desktop wallpaper.

[0045] In conjunction with the first aspect, in some embodiments, the method further includes: detecting input to wake up the voice assistant, displaying a fourth interface, the fourth interface including a voice assistant application interface and a first object, the first object being displayed in a floating manner within the voice assistant application interface.

[0046] The fourth interface can be the user interface after the input to wake up the voice assistant is detected, and may include the voice assistant application interface and the electronic pet.

[0047] In some embodiments, the input for waking up the voice assistant can be voice input. In other embodiments, the input for waking up the voice assistant can be input applied to the electronic pet (e.g., petting the electronic pet).

[0048] It should be noted that the voice assistant's appearance on the electronic device 100 has been updated to that of an electronic pet. This means that the electronic pet displayed on the electronic device 100 has the permissions of a voice assistant, which may include, but is not limited to, one or more of the following: voice interaction, installing applications, updating applications, uninstalling applications, powering on, powering off, changing system settings, setting alarms, and scheduling appointments. Traditional voice assistants lack a concrete appearance and are rather impersonal to users. Using an electronic pet as the voice assistant's appearance on the electronic device 100 makes the voice assistant more tangible, thereby increasing the frequency with which users interact with the system software.

[0049] In conjunction with the first aspect, in some embodiments, when the first object is displayed floating in the voice assistant application interface, the first object is in a seventh state, which is different from the second state.

[0050] The seventh state can be the state of the electronic pet on the fourth interface.

[0051] When the electronic pet is displayed floating in the voice assistant application interface, it is in a seventh state, which differs from the second state. Optionally, the electronic pet can change from the second state to the seventh state according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed and movement trajectory. This embodiment does not limit the form of the animation effect. It should be noted that the input to wake up the voice assistant can be voice input or input applied to the electronic pet (e.g., petting the electronic pet). This embodiment does not limit the method of waking up the voice assistant.

[0052] In conjunction with the first aspect, in some embodiments, the first electronic device and the second electronic device establish a communication connection, and the method further includes: when the first electronic device detects that the user's interaction operation has been transferred from the first electronic device to the second electronic device, sending relevant parameters of the first object to the second electronic device, the relevant parameters of the first object being used to display the first object on the second electronic device.

[0053] The second electronic device can be any electronic device other than electronic device 100, such as electronic device 200. The type of electronic device 200 can be the same as that of electronic device 100, for example, both electronic device 200 and electronic device 100 are mobile phones; or the type of electronic device 200 can be different from that of electronic device 100, for example, electronic device 100 is a mobile phone and electronic device 200 is a tablet computer.

[0054] In some embodiments, electronic device 100 may establish a communication connection with electronic device 200, and electronic device 100 may display an electronic pet. When electronic device 100 detects that a user's interaction has shifted from electronic device 100 to electronic device 200, electronic device 100 may send relevant parameters of the electronic pet to electronic device 200. These parameters can be used to display the electronic pet on electronic device 200 and may include one or more of the following: the electronic pet's identifier, the electronic pet's installation package, the electronic pet's location, the electronic pet's appearance, the electronic pet's expression, and the electronic pet's posture. The interaction is an operation performed on the electronic pet (e.g., sliding the electronic pet towards electronic device 200 on the screen of electronic device 100), or an operation performed on electronic device 200 (e.g., touching the screen of electronic device 200), or an operation where electronic device 100 touches the NFC tag of electronic device 200.

[0055] It is understandable that the prerequisites for enabling electronic pets to move across devices may include, in addition to electronic devices 100 and 200 establishing a communication connection, one or more of the following: electronic devices 100 and 200 are logged into the same user account; electronic devices 100 and 200 both support electronic pets moving across devices; and the distance between electronic devices 100 and 200 is less than a preset distance (e.g., 10 meters).

[0056] It should be noted that electronic device 100 controls the electronic pet to move from electronic device 100 to electronic device 200 for display. Specifically, electronic device 100 can control the electronic pet to be displayed on electronic device 200 instead of on electronic device 100.

[0057] It should be noted that since the prerequisite for enabling electronic pets to move across devices can include electronic devices 100 and 200 being logged into the same user account, and as mentioned above, electronic pets associated with the same user account are the same, that is, electronic pets associated with the same user account have the same name, initial appearance, and address to the user, then the electronic pet displayed on electronic device 200 and the electronic pet displayed on electronic device 100 can be the same.

[0058] It should be noted that the electronic pet can have different interactive design effects on multiple electronic devices (such as electronic device 100 and electronic device 200) that move across devices. For example, in response to clicking an application icon, electronic device 100 or electronic device 200 can launch the application corresponding to the application icon. During the launch of the application, electronic device 100 or electronic device 200 can display the application's launch animation. If the electronic pet is on electronic device 100, when displaying the application's launch animation, electronic device 100 can control the electronic pet to change its display position from around the application icon to within the launch animation. After launching the application, electronic device 100 can control the electronic pet's display position to change to the status bar. If the electronic pet is on electronic device 200, when displaying the application's launch animation, electronic device 200 can control the electronic pet to change its display position directly from around the application icon to within the status bar.

[0059] In conjunction with the first aspect, in some embodiments, the relevant parameters of the first object include one or more of the following: the identifier of the first object, the program installation package of the first object, the location of the first object, the appearance of the first object, the expression of the first object, and the posture of the first object.

[0060] In conjunction with the first aspect, in some embodiments, the interactive operation is an operation performed on a first object, or an operation performed on a second electronic device, or an operation in which the first electronic device touches the second electronic device.

[0061] In a second aspect, this application provides an electronic device, which includes a processor and a memory; wherein the memory is coupled to the processor and is used to store a computer program, and when the processor executes the computer program, the electronic device performs the method described in any of the first aspects above.

[0062] Thirdly, this application provides a computer-readable storage medium storing a computer program that is executed by a processor to implement the method described in any of the first aspects above.

[0063] Fourthly, this application provides a computer program product that, when executed by a processor, implements the method described in any one of the first aspects above.

[0064] Fifthly, this application provides a chip including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, causing the chip to perform the method described in any of the first aspects above.

[0065] The solutions provided in the second to fifth aspects above are used to implement or cooperate with the methods provided in the first aspect above, and therefore can achieve the same or corresponding beneficial effects as the methods in the first aspect, which will not be elaborated here. Attached Figure Description

[0066] Figure 1 is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application;

[0067] Figure 2A is a schematic diagram of a software architecture provided in an embodiment of this application;

[0068] Figure 2B is a schematic diagram of the software architecture of a pet interaction method provided in an embodiment of this application;

[0069] Figure 3 is a flowchart illustrating a pet interaction method based on unlocking operation provided in an embodiment of this application;

[0070] Figures 4A and 4B are a set of interface diagrams provided in the embodiments of this application;

[0071] Figure 5 is a flowchart illustrating a pet interaction method based on screen lighting operation provided in an embodiment of this application;

[0072] Figures 6A-6D are another set of interface diagrams provided in the embodiments of this application;

[0073] Figures 7A-7C are another set of interface schematic diagrams provided in the embodiments of this application;

[0074] Figures 8A-8C are another set of interface diagrams provided in the embodiments of this application;

[0075] Figures 9A and 9B are another set of interface diagrams provided in the embodiments of this application;

[0076] Figures 10A-10C are another set of interface diagrams provided in the embodiments of this application;

[0077] Figure 11 is a flowchart illustrating a pet interaction method based on clicking an application icon, according to an embodiment of this application.

[0078] Figures 12A-12C are another set of interface diagrams provided in the embodiments of this application;

[0079] Figures 13A-13C are another set of interface diagrams provided in the embodiments of this application;

[0080] Figures 14A-14C are another set of interface diagrams provided in the embodiments of this application;

[0081] Figures 15A-15C are another set of interface schematic diagrams provided in the embodiments of this application;

[0082] Figures 16A-16B are another set of interface diagrams provided in the embodiments of this application;

[0083] Figures 17A-17F are another set of interface diagrams provided in the embodiments of this application;

[0084] Figures 18A-18B are another set of interface diagrams provided in the embodiments of this application;

[0085] Figures 19A-19D are another set of interface diagrams provided in the embodiments of this application;

[0086] Figures 20A and 20B are another set of interface diagrams provided in the embodiments of this application;

[0087] Figures 21A and 21B are another set of interface diagrams provided in the embodiments of this application. Detailed Implementation

[0088] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be a limitation of this application.

[0089] With the development of technology, electronic devices have gradually become an indispensable tool in people's lives. Desktop pets are software products that simulate real pets on the desktop of electronic devices, allowing them to interact with users and satisfy their emotional needs. Currently, there are many desktop pet applications (APPs) on the market; however, these desktop pet apps currently available have relatively simple interactive methods and functions, offering limited user experience.

[0090] Currently, electronic devices typically display desktop pets via floating windows. Third-party desktop pet apps can request a floating window from the operating system and then draw the desktop pet on that window. Upon detecting interaction with the desktop pet, the third-party app can control the pet to interact with the user. As mentioned earlier, this method has the following drawbacks: 1. These third-party desktop pet apps are easily killed and have limited permissions, making them unable to perform operations such as voice interaction, installing, updating, uninstalling, powering on, and powering off. Furthermore, the app's persistent background activity after the screen is off increases power consumption. 2. The interaction method is relatively simple. The third-party app's desktop pet can only interact with the user in a fixed window. Since the third-party app cannot perceive the positions of elements such as the status bar and application icons, the desktop pet cannot interact with these elements. Additionally, the third-party app's desktop pet cannot be displayed in Always On Display (AOD) interfaces. 3. The third-party app's desktop pet is limited to a single device and cannot be moved across devices.

[0091] To address the aforementioned issues, this application provides a pet interaction method and an electronic device, applicable to a first electronic device. The first electronic device displays a first interface, which includes a first object. The first object is in a first state on the first interface, which includes a lock screen. Upon detecting an unlock operation on the first interface, the first electronic device can display a second interface, which also includes the first object. The first object is in a second state on the second interface, different from the first state. The second interface is a desktop. In this application embodiment, the first object can be a system-level electronic pet. This system-level electronic pet can possess system-level permissions, provide rich interactive functions, and enable cross-device movement, thus improving the playability of the electronic pet.

[0092] It should be noted that system-level permissions may include, but are not limited to, one or more of the following: voice interaction, installing applications, updating applications, uninstalling applications, powering on, powering off, and changing system settings. With these system-level permissions, the electronic pet will not remain in the background after the first electronic device's screen is off, thus releasing the resources it occupies; when the first electronic device's screen is on, the electronic pet will be activated and will then retrieve resources from the operating system.

[0093] It should be noted that a system-level electronic pet is essentially a system application. Because a system-level electronic pet can acquire data from a unified desktop environment, such as the AOD interface, lock screen, desktop, control center, notification center, and status bar, as well as user interface (UI) elements like application icons, application cards, and folder icons, it can further perceive the location of the unified desktop and its UI elements. Therefore, the system-level electronic pet can detect operations performed on the unified desktop and its UI elements, and thus control changes in the pet's state. In other words, the interactive functions provided by this system-level electronic pet can include interactions between the pet and the aforementioned unified desktop and its UI elements. It should be noted that the first and second interfaces mentioned above both belong to the unified desktop environment.

[0094] It should be noted that the unified desktop is a system software. The unified desktop may include one or more of the following: an AOD interface, a lock screen interface, a desktop, a control center, a notification center, a status bar, a multitasking interface, and a gesture module. This application embodiment does not limit the type and number of modules included in the unified desktop. Furthermore, the modules included in the unified desktop share a single process, and these modules can communicate internally. The AOD interface is an interface that can still display key information such as time, date, and notifications when the electronic device 100 is in a screen-off state. The lock screen interface is the main screen interface when the electronic device 100 is locked, and may include basic information such as time, date, and battery level. The desktop is the main screen interface when the electronic device 100 is unlocked, and may include, but is not limited to, one or more of the following: wallpapers, application icons, folder icons, application cards, and widgets such as weather and clock. The control center is an interface that integrates multiple functions and settings, allowing users to quickly access and adjust various system configurations, such as WiFi, Bluetooth, volume, brightness, and network settings. For example, the electronic device 100 is a mobile phone, and the user can open the control center by swiping down from the top of the screen. The notification center is an interface for centrally managing and displaying all notifications from applications, the system, and other sources. For example, the electronic device 100 is a mobile phone, and the user can open the notification center by swiping down from the top of the screen. The status bar is a horizontal bar area that displays the current status of the system and notifications, and may include, but is not limited to, one or more of the following: current time, battery level information, network connection status such as WiFi signal strength and mobile data connection status, and application notifications. The multitasking interface can be displayed as a series of application windows, each application window being the user interface of an application running in the background. The user can quickly view and manage background applications through the multitasking interface, such as switching, closing, and locking applications. The gesture module may include, but is not limited to, gestures for controlling the electronic device 100 to perform corresponding operations, such as gestures to return to and exit applications, swipe up to enter multitasking, and swipe up to exit applications.

[0095] It should be noted that the state of the electronic pet may include one or more of the following: the electronic pet's location, the electronic pet's appearance, the electronic pet's expression, and the electronic pet's posture. This application embodiment does not limit the specific form in which the electronic pet's state is displayed. Specifically, a change in the electronic pet's location can be understood as the electronic pet moving to a certain position; a change in the electronic pet's appearance may include, but is not limited to, a change in body size; a change in expression may be, for example, from closed eyes to open eyes, from smiling to angry, etc.; and a change in posture may include, but is not limited to, a change in movement, such as from lying down to standing, from standing to walking, rotating, jumping, etc.

[0096] It should be noted that the electronic pet's state can change according to animation effects, which can be dynamic effects showing the change of the electronic pet's state between two interfaces. The parameters of the animation effects can include one or more of the following: movement speed and movement trajectory. A change in the electronic pet's movement trajectory can be understood as the type of curve the electronic pet moves along, such as moving in a straight line or along a curve; a change in the electronic pet's movement speed can be understood as a change in the instantaneous speed of the electronic pet during movement. The electronic pet can move at a constant speed or with varying speed, and this embodiment does not limit this. It is understood that the aforementioned electronic pet's movement trajectory and movement speed can be preset, i.e., configured by the electronic pet application or operating system; or they can be specified by the user, and this embodiment does not limit the method of user specification.

[0097] The method provided in this application embodiment allows the first electronic device to associate the state of the electronic pet with the user's operation on the unified desktop, so that when the operation on the unified desktop is detected, the first electronic device can control the state of the electronic pet to change, thereby improving the flexibility and fun of the electronic pet and enriching the interaction between the user and the electronic pet.

[0098] First, an electronic device 100 provided in the embodiments of this application will be introduced.

[0099] Figure 1 illustrates an electronic device 100 provided in an embodiment of this application.

[0100] In this embodiment, the first electronic device may be referred to as electronic device 100. Electronic device 100 may be various types of smart terminal devices including a display screen (i.e., a screen), and this embodiment does not limit the specific type of electronic device 100. For example, electronic device 100 may be a mobile phone, or it may be a mobile tablet computer, an in-vehicle tablet computer, a desktop computer, a laptop computer, a handheld computer, a laptop, a watch, etc.

[0101] As shown in Figure 1, the electronic device 100 may include a processor 210, an external memory interface 220, an internal memory 221, a Universal Serial Bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, antenna 1, antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, a sensor module 280, a camera 293, a display screen 294, and a subscriber identity module (SIM) card interface 295, etc. The sensor module 280 may include, but is not limited to, a pressure sensor 280A, a fingerprint sensor 280H, and a touch sensor 280K.

[0102] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0103] Processor 210 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0104] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

[0105] The processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. This memory can store instructions or data that the processor 210 has just used or that are used repeatedly. If the processor 210 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.

[0106] In this embodiment of the application, the processor 210 can be used to control the state of the electronic pet to change when the user's operation on the unified desktop is detected, wherein the operation on the unified desktop does not affect the electronic pet.

[0107] The external storage interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 210 through the external storage interface 220 to perform data storage functions. For example, music, photos, videos, and other data can be stored on the external memory card.

[0108] Internal memory 221 can be used to store one or more computer programs, which include instructions. Processor 210 can execute the instructions stored in internal memory 221, thereby causing electronic device 100 to perform the pet interaction methods provided in some embodiments of this application, as well as various functional applications and data processing. Internal memory 221 may include a program storage area and a data storage area. The program storage area may store the operating system; it may also store one or more applications (such as a gallery, contacts, etc.). The data storage area may store data created during the use of electronic device 100 (such as photos, contacts, etc.). Furthermore, internal memory 221 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0109] USB port 230 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 230 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as augmented reality (AR) devices.

[0110] The charging management module 240 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 240 receives charging input from the wired charger via a USB interface 230. In some wireless charging embodiments, the charging management module 240 receives wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 242, the charging management module 240 can also supply power to the electronic device 100 via the power management module 241.

[0111] The power management module 241 connects the battery 242, the charging management module 240, and the processor 210. The power management module 241 receives input from the battery 242 and / or the charging management module 240, providing power to the processor 210, internal memory 221, external memory, display screen 294, camera 293, and wireless communication module 260. The power management module 241 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 241 may also be located within the processor 210. In other embodiments, the power management module 241 and the charging management module 240 may be housed in the same device.

[0112] The wireless communication function of electronic device 100 can be implemented through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor.

[0113] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0114] The mobile communication module 250 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 250 may include at least one filter, switch, power amplifier, low-noise amplifier, etc. The mobile communication module 250 can receive electromagnetic waves via the antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to the modem processor for demodulation. The mobile communication module 250 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via the antenna. In some embodiments, at least some functional modules of the mobile communication module 250 may be housed in the processor 210. In some embodiments, at least some functional modules of the mobile communication module 250 and at least some modules of the processor 210 may be housed in the same device.

[0115] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor displays images or videos via the display screen 294. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 210 and may be housed within the same device as the mobile communication module 250 or other functional modules.

[0116] The wireless communication module 260 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (WiFi) networks), Bluetooth (BT), global navigation satellite systems, frequency modulation, near field communication (NFC), infrared technology, and ultra-wideband (UWB). The wireless communication module 260 can be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via an antenna, frequency-modulates and filters the electromagnetic wave signals, and sends the processed signal to the processor 210. The wireless communication module 260 can also receive signals to be transmitted from the processor 210, frequency-modulate and amplify them, and then convert them into electromagnetic waves for radiation via the antenna. For example, the wireless communication module 260 may include a Bluetooth module, a WiFi module, etc.

[0117] In some embodiments, a portion of the antenna of the electronic device 100 is coupled to the mobile communication module 250, and another portion of the antenna is coupled to the wireless communication module 260, enabling the electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Millimeter Wave (mmWave), BitTorrent, Global Navigation Satellite System (GNSS), WLAN, NFC, Frequency Modulation (FM), UWB, and / or Infrared (IR) technology, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0118] In some embodiments, electronic device 100 can establish a communication connection with electronic device 200 via antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor. After establishing a communication connection with electronic device 200, when electronic device 100 detects that a user's interaction has transferred from electronic device 100 to electronic device 200, electronic device 100 can send relevant parameters of the electronic pet to electronic device 200 based on the communication connection. These relevant parameters can be used to display the electronic pet on electronic device 200 and may include one or more of the following: the electronic pet's identifier, the electronic pet's program installation package, the electronic pet's location, the electronic pet's appearance, the electronic pet's expression, and the electronic pet's posture. The interaction can be an operation performed on the electronic pet, an operation performed on electronic device 200, or an operation where electronic device 100 touches electronic device 200.

[0119] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 270, speaker 270A, receiver 270B, microphone 270C, headphone jack 270D, and application processor.

[0120] The audio module 270 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 270 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 270 may be located in the processor 210, or some functional modules of the audio module 270 may be located in the processor 210.

[0121] The speaker 270A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or make hands-free calls through the speaker 270A.

[0122] The receiver 270B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a telephone call or voice message, the receiver 270B can be brought close to the ear to listen to the voice.

[0123] Microphone 270C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 270C, inputting the sound signal into microphone 270C. Electronic device 100 may have at least one microphone 270C. In some embodiments, electronic device 100 may have two microphones 270C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic device 100 may also have three, four, or more microphones 270C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.

[0124] The headphone jack 270D is used to connect wired headphones. The headphone jack 270D can be a USB 230 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0125] In this embodiment, the electronic device 100 can detect input to wake up the voice assistant via the audio module 270. Further, the electronic device 100 can wake up the voice assistant and display a fourth interface, which may include a voice assistant application interface and an electronic pet, the electronic pet being displayed in a floating position within the voice assistant application interface. When the electronic pet is displayed in a floating position within the voice assistant application interface, the electronic pet's state (seventh state) changes compared to its state on the desktop (second state).

[0126] Electronic device 100 can realize display functions through GPU, display screen 294, and application processor, such as an electronic pet on a display-in-one desktop. GPU is a microprocessor for image processing, connected to display screen 294 and application processor. GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 210 may include one or more GPUs, which execute instructions to generate or modify display information.

[0127] The display screen 294 is used to display images, videos, etc. The display screen 294 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 294, where N is a positive integer greater than 1. It should be noted that a display screen can also be referred to as a screen.

[0128] In this embodiment, the electronic device 100 can display a first interface via a GPU, a display screen 294, and an application processor. This first interface may include an electronic pet, and the electronic pet is in a first state on the first interface. The first interface may also include a lock screen. Upon detecting an unlock operation on the first interface, the electronic device 100 can display a second interface via the GPU, the display screen 294, and the application processor. This second interface may include the electronic pet, and the electronic pet is in a second state on the second interface, which is different from the first state; this second interface is the desktop.

[0129] In some embodiments, when the electronic device 100 switches from displaying a first interface to displaying a second interface, the electronic pet can change from a first state to a second state according to a first animation effect. The parameters of the first animation effect include one or more of the following: a first moving speed and a first moving trajectory. In other embodiments, the above-mentioned lock screen interface is an always-on lock screen interface, which can be understood as an AOD interface. In other embodiments, the above-mentioned lock screen interface can be a lock screen interface that is on. Before the electronic device 100 displays the first interface, the electronic device 100 can display an AOD interface through the GPU, display screen 294, and application processor, etc. The AOD interface includes an electronic pet, which is in a third state, different from the first state; then, the electronic device 100 can detect the operation of turning on the screen of the first interface.

[0130] In other embodiments, the desktop includes application icons, with the electronic pet located around them. Upon detecting an operation on an application icon, the electronic pet on the desktop can change from a second state to a fourth state, which is different from the second state. The operation on the application icon can include long-pressing, dragging, unloading, or clicking. For example, when the operation is a long press, the electronic pet's first expression in the fourth state changes relative to its second expression in the second state; when the operation is dragging, the electronic pet's first position in the fourth state changes relative to its second position in the second state; and when the operation is unloading, the electronic pet's third position in the fourth state changes relative to its fourth position in the second state. In other embodiments, in response to clicking an application icon, the electronic device 100 can display a third interface via a GPU, display screen 294, and application processor. This third interface can be the user interface and status bar of the application corresponding to the application icon. The third interface may also include the electronic pet, which is displayed in the status bar. When the electronic pet is displayed in the status bar, its state (fifth state) changes compared to its state on the desktop (second state). The application corresponding to the application icon can be a system application or a third-party application; this embodiment does not limit this. During the process of the electronic device 100 switching from displaying the second interface to displaying the third interface, the electronic device 100 can display the application's startup animation through the GPU, display screen 294, and application processor, etc., and the electronic pet can change from being displayed around the application icon to being displayed within the startup animation. After displaying the third interface, the electronic pet can change from being displayed within the startup animation to being displayed in the status bar.

[0131] In other embodiments, the desktop wallpaper contains pet interactive elements (such as pet beds, pet toys, pet food, etc.), and the electronic pet is located around the pet interactive elements (i.e., the distance between the electronic pet and the pet interactive elements is less than a preset threshold (e.g., 1 cm)). At this time, the electronic pet is in a second state. The electronic pet can change from being displayed around the pet interactive elements on the desktop to being displayed around the first UI element (i.e., the distance between the electronic pet and the first UI element is less than a preset threshold (e.g., 1 cm)). At this time, the electronic pet is in a sixth state. The first UI element may include one or more of the following: application icons, application cards, folder icons. This application embodiment does not limit the type of the first UI element.

[0132] In other embodiments, upon detecting input to wake up the voice assistant, the electronic device 100 can wake up the voice assistant and display a fourth interface via the GPU, display screen 294, and application processor. The fourth interface may include a voice assistant application interface and an electronic pet, which floats within the voice assistant application interface. While the electronic pet is floating within the voice assistant application interface, it may be in a seventh state, which differs from the second state.

[0133] Electronic device 100 can perform shooting functions through ISP, camera 293, video codec, GPU, display 294 and application processor.

[0134] The ISP (Image Signal Processor) is used to process data fed back from the camera 293. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, converting it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and color. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 293.

[0135] Camera 293 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 100 may include one or N cameras 293, where N is a positive integer greater than 1.

[0136] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.

[0137] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG)-1, MPEG-2, MPEG-3, MPEG-4, etc.

[0138] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0139] In this embodiment, the electronic device 100 can capture facial images via an ISP, camera 293, video codec, GPU, display screen 294, and application processor. Then, the electronic device 100 can utilize the captured facial features to unlock the device; the electronic device 100 can also recognize the user's facial expressions based on the captured images, allowing the electronic pet to interact with the user based on their expressions.

[0140] The SIM card interface 295 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 295 to make contact with and separate from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 295 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 295 simultaneously. The types of these multiple cards can be the same or different. The SIM card interface 295 is also compatible with different types of SIM cards. The SIM card interface 295 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100. In some embodiments, the electronic device 100 may not include the SIM card interface 295.

[0141] Pressure sensor 280A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 280A can be disposed on display screen 294. There are many types of pressure sensors 280A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 280A, the capacitance between the electrodes changes. Electronic device 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 294, electronic device 100 detects the intensity of the touch operation based on pressure sensor 280A. Electronic device 100 can also calculate the touch position based on the detection signal from pressure sensor 280A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example, when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0142] The fingerprint sensor 280H is used to collect fingerprints. The electronic device 100 can utilize the characteristics of the collected fingerprint to achieve fingerprint unlocking, accessing application locks, taking photos with fingerprints, answering calls with fingerprints, etc. In some embodiments, the electronic device 100 can unlock with fingerprints using the fingerprint sensor 280H.

[0143] Touch sensor 280K, also known as a touch panel or touch-sensitive surface, can be located on display screen 294. The touch sensor 280K and display screen 294 together form a touchscreen, also called a "touchscreen." Touch sensor 280K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 294. In other embodiments, touch sensor 280K may also be located on the surface of electronic device 100, in a different position than display screen 294.

[0144] In this embodiment, the electronic device 100 can detect operations on the unified desktop via the pressure sensor 280A and the touch sensor 280K. In some embodiments, the electronic device 100 can detect operations on application icons (including but not limited to long-pressing an application icon, dragging an application icon, uninstalling an application icon, and clicking an application icon) via the pressure sensor 280A and the touch sensor 280K. In other embodiments, the electronic device 100 can also detect the operation of turning on the AOD interface via the pressure sensor 280A and the touch sensor 280K. In other embodiments, the electronic device 100 can also detect the unlocking operation of the lock screen via the pressure sensor 280A and the touch sensor 280K. In other embodiments, the electronic device 100 can also detect user interaction operations via the pressure sensor 280A and the touch sensor 280K, which may include operations performed on an electronic pet.

[0145] The structure of electronic device 200 is the same as that of electronic device 100, and will not be described again here.

[0146] The software architecture diagrams provided in the embodiments of this application will be described in detail below.

[0147] Figure 2A illustrates an exemplary software architecture provided by an embodiment of this application.

[0148] The electronic device provided in this application embodiment can run an operating system (OS). This operating system can be various operating systems used in the industry, such as an operating system based on OpenHarmony, like HarmonyOS; or other operating systems such as Android. TM An operating system can refer to the iOS mobile operating system; it can also refer to various open-source operating systems or their derivatives, such as Linux OS, and other embedded operating systems; it can also refer to future new operating systems, such as artificial intelligence (AI) operating systems. An operating system is a set of interconnected system software programs that manage and control the operation of electronic devices, utilize and run hardware and software resources, and provide public services to organize user interactions. In electronic devices, the operating system connects downwards to the physical hardware layer and upwards to provide a runtime environment for application software.

[0149] An operating system typically includes a kernel layer, a middleware layer, and an application layer. The application layer includes applications, which can include system applications and third-party applications. The middleware layer includes a suite of software providing various services to application developers, or frameworks providing services such as databases, multimedia, and graphics, or capabilities such as distributed scheduling and system scaling. For example, the middleware layer may include a framework layer and / or a system service layer. The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The system service layer includes the system's core capabilities, providing services to applications through the framework layer. The kernel layer is the layer between hardware and software. The kernel layer may include hardware drivers and the operating system kernel. In addition to providing hardware drivers, the kernel layer also supports functions such as memory management and system process management.

[0150] The electronic devices we use in our daily lives come in various types and forms, and are applied in a wide range of scenarios. Therefore, based on the different forms and functions of electronic devices, different application scenarios, and different user needs, the operating systems used in these devices may also differ. The basic functions implemented by the electronic device provided in this application can be implemented using a general-purpose operating system or a dedicated operating system. To more clearly illustrate the implementation of the embodiments of this application under a specific operating system, the architecture of HarmonyOS is shown below. Those skilled in the art can deduce the implementation of the embodiments of this application under other specific operating systems, such as Android. TM Implementation under operating systems, etc.

[0151] The software architecture of electronic devices can be divided into several layers. In some embodiments, from bottom to top, these layers are: kernel layer, system service layer, framework layer, and application layer. Layers communicate with each other through software interfaces. System functions can be tailored, added, or combined at the subsystem level depending on the deployment scenario of different device forms. Each subsystem can also be tailored, added, or combined at the functional level.

[0152] Kernel layer:

[0153] The Kernel Abstraction Layer (KAL) provides basic kernel capabilities to upper layers by shielding the differences between multiple kernels, including but not limited to process / thread management, memory management, file system, network management, and peripheral device management.

[0154] Kernel Subsystem: Supports the selection of a suitable OS kernel for different resource-constrained devices, including but not limited to Linux kernel, HarmonyOS kernel, LiteOS (Lite Operating System), etc.

[0155] Driver Subsystem: The driver framework is the foundation for the open system hardware ecosystem, providing unified peripheral access capabilities and a framework for driver development and management. The driver framework includes: display drivers, camera drivers, audio drivers, Bluetooth drivers, sensor drivers, etc.

[0156] System service layer:

[0157] The system service layer comprises the core capabilities of the system, providing services to applications through the framework layer. This layer includes, but is not limited to, the following subsystems:

[0158] The system's basic capability subsystem set provides fundamental capabilities for the operation, scheduling, and migration of distributed applications across multiple devices. This set may include distributed soft bus, distributed data management, distributed task scheduling, and Ark multi-language runtime; it may also include multi-modal input subsystem, graphics subsystem, security subsystem, and AI business subsystem.

[0159] Basic software service subsystem set: provides public and general software services; the basic software service subsystem set may include event notification subsystem, telephone service subsystem, multimedia subsystem, etc.

[0160] Enhanced Software Service Subsystem Set: Provides differentiated enhanced software services for different devices; the enhanced software service subsystem set may include proprietary business subsystems for smart screens, proprietary business subsystems for wearables, proprietary business subsystems for the Internet of Things (IoT), etc.

[0161] Hardware service subsystem set: Provides hardware services; the hardware service subsystem set may include location service subsystem, user IAM (Identity and Access Management) subsystem, wearable proprietary hardware service subsystem, biometric identification, IoT proprietary hardware service subsystem, etc.

[0162] Distributed task scheduling enables distributed service management (discovery, synchronization, registration, and invocation), supporting remote startup, remote invocation, remote connection, and migration of applications across devices.

[0163] Distributed data management enables data synchronization, data storage, data sharing, and data access across all scenarios and devices.

[0164] The distributed soft bus provides communication-related capabilities for seamless interconnection between multiple devices, including: WLAN service capabilities, Bluetooth service capabilities, soft bus, inter-process communication RPC (Remote Procedure Call), and StarFlash communication capabilities.

[0165] Ark Multilingual Runtime is a unified compilation runtime platform designed to support the joint compilation and execution of multiple programming languages ​​and multiple chip platforms.

[0166] Framework layer:

[0167] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The framework layer includes: the ArkUI framework (which provides a complete infrastructure for UI development of system applications, including UI functions such as components, layouts, animations, and interactive events, as well as a real-time interface preview tool), the user application framework, and the Ability framework (an Ability is a lightweight application; the Ability framework schedules and manages the operation and lifecycle of Abilities). Different devices may have different operating systems, and the APIs they support may also differ.

[0168] The HarmonyOS API is a series of open capabilities provided to support HarmonyOS application development. The HarmonyOS API can be set at the framework layer or independently of the framework layer. The HarmonyOS API includes the Audio API (audio service), Push API (push service), and Account API (account service), among others.

[0169] Application layer:

[0170] Applications can include system apps and extended / third-party apps. System apps can include the desktop, control bar, settings, contacts, phone, camera, etc., while extended / third-party apps can include social networking, travel, etc.

[0171] Figure 2B illustrates, exemplarily, the software architecture of a pet interaction method provided in an embodiment of this application.

[0172] As shown in Figure 2B, the middleware layer may include a pet management module and a unified desktop. The pet management module may include a pet data module, a pet drawing module, and a system management service. It should be noted that, as mentioned above, the middleware layer may include a framework layer and / or a system service layer. The pet management module can belong to either the framework layer or the system service layer; that is, the pet data module, pet drawing module, and system management service can each belong to either the framework layer or the system service layer. The unified desktop can also belong to either the framework layer or the system service layer.

[0173] The pet management module can receive basic data about the electronic pet from the pet data module, and also receive desktop layout data from the unified desktop. The pet management module can also control the electronic pet's state to change according to animation effects based on the basic data and desktop layout data. That is, the pet management module can control at least one of the following changes based on the electronic pet's basic data, desktop layout data: position, appearance, expression, and posture. During the process of the electronic pet's state changing, the pet management module can also control one or more of the following changes based on the electronic pet's basic data and desktop layout data: movement trajectory and movement speed. The changes in the electronic pet's position can be understood as the location to which the electronic pet moves. As shown in Figures 12A-12C, when displaying the application's startup animation, the electronic device 100 can control the electronic pet to change its display from around the application icon to within the startup animation. After launching the application corresponding to the application icon, the electronic device 100 can control the electronic pet's display position to change to the status bar. Changes in the electronic pet's appearance can include, but are not limited to, changes in body size. Changes in the electronic pet's expression can be, for example, from closed eyes to open eyes, from smiling to angry, etc. Changes in the electronic pet's posture can include, but are not limited to, changes in movement, such as from lying down to standing, from standing to walking, rotating, jumping, etc. Changes in the electronic pet's movement trajectory can be understood as the type of curve the electronic pet moves along, such as moving in a straight line or moving along a curve. Changes in the electronic pet's movement speed can be understood as changes in the instantaneous speed of the electronic pet during movement. The electronic pet can move at a constant speed or at a variable speed, and this embodiment does not limit this. It is understood that the movement trajectory and speed of the electronic pet can be preset, i.e., configured by the electronic pet application or operating system; or, it can be specified by the user. This application embodiment does not limit the user-specified method. After controlling the electronic pet's state to change according to the animation based on the electronic pet's basic data and desktop layout data, the pet management module can also be used to send relevant parameters of the electronic pet to the pet drawing module. The relevant parameters of the electronic pet can include one or more of the following: the electronic pet's identifier, the electronic pet's program installation package, the electronic pet's location, the electronic pet's appearance, the electronic pet's expression, and the electronic pet's posture, so that the pet drawing module can draw the electronic pet based on the relevant parameters of the electronic pet.

[0174] The pet data module can be used to send basic data about the electronic pet to the pet management module. This basic data may include, but is not limited to, the electronic pet's name, initial appearance, and how the electronic pet addresses the user. It is understood that the electronic pet's basic data is linked to the user account; that is, electronic pets associated with the same user account are identical, meaning they share the same name, initial appearance, and way of addressing the user. The user account can be used to identify the user, and may be, for example, a mobile phone number. Optionally, the electronic pet's basic data can be fixed or updated. For example, when a user changes their electronic pet, they can choose to reset the pet's name, initial appearance, and how the pet addresses them. Furthermore, the electronic pet's basic data can be updated based on the user's settings.

[0175] The pet drawing module receives parameters of the electronic pet from the pet management module and draws the electronic pet based on these parameters. After drawing the electronic pet, the pet drawing module can also send the completed electronic pet to the unified desktop so that the unified desktop can display the electronic pet.

[0176] The system management service can be used to provide system-level permissions to the pet management module, enabling the electronic device 100 to perform system functions through the electronic pet. For example, the electronic pet can function as a voice assistant. Upon detecting input to wake up the voice assistant, the electronic device 100 can wake up the voice assistant and display a fourth interface. The fourth interface may include a voice assistant application interface and the electronic pet, which can be displayed floating within the voice assistant application interface. When the electronic pet is displayed floating within the voice assistant application interface, its state changes compared to its state on the desktop. For example, the fourth interface can be seen in Figures 17A-17F below, which will not be elaborated upon here.

[0177] The unified desktop may include one or more of the following: an AOD (Always-On Display) interface, a lock screen interface, a desktop, a control center, a notification center, a status bar, a multitasking interface, and a gesture module. This application embodiment does not limit the type or number of modules included in the unified desktop. Furthermore, the modules included in the unified desktop share a single process, and these modules can communicate internally. The AOD interface is an interface that can still display key information such as time, date, and notifications when the electronic device 100 is in a screen-off state. The lock screen interface is the main screen interface when the electronic device 100 is locked, and may include basic information such as time, date, and battery level. The desktop is the main screen interface when the electronic device 100 is unlocked, and may include, but is not limited to, one or more of the following: wallpapers, application icons, folder icons, application cards, and widgets such as weather and clock. The control center is an interface that integrates multiple functions and settings, allowing users to quickly access and adjust various system configurations, such as WiFi, Bluetooth, volume, brightness, and network settings. For example, the electronic device 100 is a mobile phone, and the user can open the control center by swiping down from the top of the screen. The notification center is an interface for centrally managing and displaying all notifications from applications, the system, and other sources. For example, the electronic device 100 is a mobile phone, and the user can open the notification center by swiping down from the top of the screen. The status bar is a horizontal bar area that displays the current status of the system and notifications, and may include, but is not limited to, one or more of the following: current time, battery level information, network connection status such as WiFi signal strength and mobile data connection status, and application notifications. The multitasking interface can be displayed as a series of application windows, each application window being the user interface of an application running in the background. The user can quickly view and manage background applications through the multitasking interface, such as switching, closing, and locking applications. The gesture module may include, but is not limited to, gestures for controlling the electronic device 100 to perform corresponding operations, such as gestures to return to and exit applications, swipe up to enter multitasking, and swipe up to exit applications.

[0178] In this embodiment, the unified desktop can be used to send desktop layout data to the pet management module. This desktop layout data may include, but is not limited to, the layout of the unified desktop, the system status of the electronic device 100, and user operations on the unified desktop. The layout of the unified desktop may include, but is not limited to, one or more of the following: application icons, folder icons, application cards, and the form and location of the status bar. For example, as shown in FIG17A, the electronic device 100 can display a user interface 350. A status bar is displayed at the top of the screen, which may include, but is not limited to, the current time, battery level indication information, and network connection status such as WiFi signal strength and mobile data connection status. Optionally, the user interface 350 may include, but is not limited to, the current date, time, and weather. Below the current date, time, and weather, one or more application icons (e.g., music application icon, settings application icon, etc.) and folder icons may be included, wherein the folder icons may contain one or more application icons. Below the one or more application icons and folder icons, a page indicator is also included, which is used to indicate the positional relationship between the currently displayed page and other pages. Optionally, multiple tray icons (such as dialer app icon, messaging app icon, browser app icon, camera app icon, etc.) are displayed below the page indicator, and these tray icons can remain displayed when switching pages. The system status of the electronic device 100 may include, but is not limited to, whether the electronic device 100 is unlocked or whether the screen is off. User operations on the unified desktop may include, but are not limited to, turning the screen on, turning the screen off, unlocking, long-pressing an app icon, dragging an app icon, uninstalling an app icon, clicking an app icon, installing an app icon, updating an app icon, activating the voice assistant, pulling down the notification center, and pulling down the control center. Furthermore, the unified desktop can also be used to receive completed electronic pets sent by the pet drawing module, which can be displayed on the unified desktop.

[0179] The application layer can receive basic data about the electronic pet input by the user. This basic data may include, but is not limited to, the electronic pet's name, initial appearance, and how the electronic pet addresses the user. After receiving the basic data, the application layer can send it to the middleware layer so that the middleware layer can process it. For example, the application layer can send the basic data to the pet data module in the middleware layer. Furthermore, the application layer can receive a completed electronic pet from the middleware layer, which can then be displayed within the application's application.

[0180] The following will describe in detail, with reference to the flowchart, a series of graphical user interfaces provided in the embodiments of this application.

[0181] Figure 3 illustrates the flowchart of a pet interaction method based on unlocking operation provided in an embodiment of this application.

[0182] As shown in Figure 3, the method may include:

[0183] S101, Electronic device 100 displays a first interface, the first interface includes a first object, and the first object is in a first state on the first interface.

[0184] S102, An unlocking operation on the first interface is detected, and the electronic device 100 displays a second interface. The second interface includes a first object, and the first object is in a second state on the second interface.

[0185] As mentioned above, in the embodiments of this application, the first object can be a system-level electronic pet, hereinafter referred to as an electronic pet.

[0186] As mentioned above, in the embodiments of this application, both the first interface and the second interface belong to the unified desktop.

[0187] As shown in Figures 4A-4B, in some embodiments, the first interface may include a lock screen interface, and the operation detected by the electronic device 100 on the first interface may include an unlock operation. It should be noted that the lock screen interface can be a lock screen that is on or off, and the off-screen lock screen interface can be understood as an AOD interface. This application embodiment does not limit the type of lock screen interface. The second interface may be a desktop. In response to the unlock operation on the lock screen interface, the electronic device 100 may display the desktop. Both the lock screen interface and the desktop include an electronic pet, but the state of the electronic pet on the desktop changes compared to its state on the lock screen interface. That is, the electronic pet is in a first state on the lock screen interface and in a second state on the desktop, and the second state is different from the first state. Optionally, when the electronic device 100 switches from displaying the lock screen interface to displaying the desktop, the electronic pet can change from the first state to the second state according to a first animation effect. The parameters of the first animation effect include one or more of the following: a first movement speed and a first movement trajectory. This application embodiment does not limit the form of the first animation effect. It should be noted that users can unlock the desktop from the lock screen using fingerprint, face unlock, password, pattern unlock, or directly access the desktop without unlocking the lock screen. The method of unlocking the desktop from the lock screen is related to the user's security settings, and this application embodiment does not limit the unlocking method.

[0188] For example, as shown in FIG4A, the electronic device 100 can display a user interface 110, which can be the lock screen interface of the electronic device 100. The user interface 110 can include an electronic pet in a first state (e.g., a pet 111 in an agitated state, with its eyes open, one paw raised, and the other paw lowered). This embodiment of the application does not limit the electronic pet in the first state in the lock screen interface. Optionally, the user interface 110 can also include a fingerprint recognition area 112, which can be used to collect the user's fingerprint. When the collected fingerprint information matches the fingerprint information stored in the electronic device 100 (i.e., unlocking is successful), the electronic device 100 is triggered to unlock and enter the desktop. It should be noted that in addition to fingerprint unlocking, users can also unlock and enter the desktop by face unlocking, password unlocking, pattern unlocking, or directly entering the desktop without unlocking. The way a user unlocks and enters the desktop is related to the user's security settings. This embodiment of the application does not limit the unlocking method.

[0189] In some embodiments, the electronic device 100 may receive an unlocking operation from a user, such as an unlocking operation performed by the user on the fingerprint recognition area 112. In response to this operation, if the collected fingerprint information matches the fingerprint information stored in the electronic device 100 (i.e., unlocking is successful), the electronic device 100 may display a desktop (e.g., the user interface 120 shown in FIG4B).

[0190] For example, as shown in FIG4B, the electronic device 100 can display a user interface 120, which can be the desktop of the electronic device 100. The electronic device 100 can display a desktop, or it can display a user interface other than the desktop; this embodiment does not limit this. The user interface 120 may include an electronic pet in a second state (e.g., an active pet 121 with its eyes open and its paws raised). The second state is different from the first state. Furthermore, this embodiment does not limit the electronic pet in the second state on the desktop after unlocking.

[0191] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0192] Figure 5 illustrates, exemplarily, the flow of a pet interaction method based on screen lighting operation provided in an embodiment of this application.

[0193] As shown in Figure 5, the method may include:

[0194] S201, Electronic device 100 displays an AOD interface, the AOD interface includes a first object, the first object is in a third state.

[0195] S202, An operation to turn on the screen of the AOD interface is detected, and the electronic device 100 displays a first interface, the first interface including a first object, and the first object is in a first state on the first interface.

[0196] S203, An unlocking operation on the first interface is detected, and the electronic device 100 displays a second interface, which includes a first object, and the first object is in a second state on the second interface.

[0197] As mentioned above, in the embodiments of this application, the first object can be a system-level electronic pet, hereinafter referred to as an electronic pet.

[0198] As mentioned above, in the embodiments of this application, both the first interface and the second interface belong to the unified desktop.

[0199] As shown in Figures 6A-6D, in some embodiments, the unified desktop may include an AOD (Ahead-of-Date) interface, and the operation detected by the electronic device 100 on the AOD interface may include turning on the screen. The first interface may include a lock screen interface, and the operation detected by the electronic device 100 on the first interface may include an unlocking operation. It should be noted that the lock screen interface can be a lock screen interface that is turned on. In response to the operation of turning on the screen of the AOD interface, the electronic device 100 can display the lock screen interface. Both the AOD interface and the lock screen interface include an electronic pet, but the state of the electronic pet on the lock screen interface has changed compared to the state of the electronic pet on the AOD interface. That is, the electronic pet is in a third state on the AOD interface and in a first state on the lock screen interface, and the third state is different from the first state. Optionally, when the electronic device 100 switches from displaying the AOD interface to displaying the lock screen interface, the electronic pet can change from the third state to the first state according to an animation effect. The parameters of the animation effect include one or more of the following: movement speed, movement trajectory. This application embodiment does not limit the form of the animation effect. The second interface may be a desktop. In response to the unlocking operation of the lock screen, the electronic device 100 can display the desktop. Both the lock screen and the desktop include the electronic pet, but the state of the electronic pet on the desktop changes compared to its state on the lock screen. That is, the electronic pet is in a first state on the lock screen and in a second state on the desktop, and the second state is different from the first state. Optionally, when the electronic device 100 switches from displaying the lock screen to displaying the desktop, the electronic pet can change from the first state to the second state according to a first animation effect. The parameters of the first animation effect include one or more of the following: a first movement speed and a first movement trajectory. This embodiment of the application does not limit the form of the first animation effect.

[0200] For example, as shown in FIG6A, the electronic device 100 can display a user interface 130, which can be the AOD interface of the electronic device 100. The user interface 130 can include an electronic pet in a third state (e.g., a sleeping pet 131 with its eyes closed and paws down). This embodiment of the application does not limit the electronic pet in the third state in the AOD interface. In addition, the user interface 130 may also include a power button (e.g., button 132), which can be used to turn on the screen and trigger the electronic device 100 to turn on the screen and enter the lock screen interface.

[0201] In some embodiments, the electronic device 100 may receive a user's operation to turn on the screen, such as an operation on the power button (e.g., button 132), and in response to the operation, the electronic device 100 may display a lock screen interface (e.g., user interface 140 shown in FIG6B).

[0202] For example, as shown in FIG6B, the electronic device 100 can display a user interface 140, which can be the lock screen interface of the electronic device 100. The user interface 140 can include an electronic pet (e.g., a pet 141 in a sleeping state, with its eyes open and paws down). The state of the electronic pet is different from the third state. This embodiment of the application does not limit the state of the electronic pet in the lock screen interface after the screen is lit. Optionally, the user interface 140 can also include a fingerprint recognition area 142, which can be used to collect the user's fingerprint. When the collected fingerprint information matches the fingerprint information stored in the electronic device 100 (i.e., unlocking is successful), the electronic device 100 is triggered to unlock and enter the desktop. It should be noted that in addition to fingerprint unlocking, users can also unlock and enter the desktop by face unlocking, password unlocking, pattern unlocking, or directly entering the desktop without unlocking. The way a user unlocks and enters the desktop is related to the user's security settings. This embodiment of the application does not limit the unlocking method.

[0203] In some embodiments, when a user initiates an unlocking operation (e.g., when a user touches the fingerprint recognition area 142 for less than a preset duration (e.g., 0.5 seconds)), the electronic device 100 may display a lock screen interface (e.g., the user interface 110 shown in FIG6C).

[0204] For example, as shown in FIG6C, the electronic device 100 can display a user interface 110, which can be the lock screen interface of the electronic device 100. The user interface 110 can include an electronic pet in a first state (e.g., pet 111, with its eyes open, one paw raised, and the other paw lowered). Optionally, the first state can be different from or the same as the state of pet 141 in the user interface 140. This application embodiment does not limit the electronic pet in the first state. Optionally, the user interface 110 can also include a fingerprint recognition area 112, which can be used to collect the user's fingerprint. When the collected fingerprint information matches the fingerprint information stored in the electronic device 100 (i.e., unlocking is successful), the electronic device 100 is triggered to unlock and enter the desktop. It should be noted that in addition to fingerprint unlocking, users can also unlock and enter the desktop by face unlocking, password unlocking, pattern unlocking, or directly entering the desktop without unlocking. The way a user unlocks and enters the desktop is related to the user's security settings. This application embodiment does not limit the unlocking method.

[0205] In some embodiments, the electronic device 100 may receive an unlocking operation from a user, such as an unlocking operation performed by the user on the fingerprint recognition area 112. In response to this operation, if the collected fingerprint information matches the fingerprint information stored in the electronic device 100 (i.e., unlocking is successful), the electronic device 100 may display a desktop (e.g., the user interface 120 shown in FIG6D).

[0206] For example, as shown in FIG6D, the electronic device 100 can display a user interface 120, which can be the desktop of the electronic device 100. The electronic device 100 can display a desktop, or it can display a user interface other than the desktop; this embodiment does not limit this. The user interface 120 may include an electronic pet in a second state (e.g., an active pet 121 with its eyes open and its paws raised). The second state is different from the first state, and this embodiment does not limit the electronic pet in the second state on the desktop after unlocking.

[0207] In the above embodiments, during the user's continuous operations of turning on the screen and unlocking the device, the AOD interface, lock screen interface, and desktop are displayed sequentially and continuously, and the status of the electronic pet displayed sequentially on the AOD interface, lock screen interface, and desktop also changes continuously.

[0208] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0209] It should be noted that the change in the electronic pet's state controlled by electronic device 100 specifically refers to a change in the electronic pet's state after detecting an operation on the unified desktop compared to the state before detecting the operation. Upon detecting an operation to light up the screen on the AOD interface, electronic device 100 can control the electronic pet's state to change from the third state to the first state, where the first state is different from the third state. Upon detecting a successful unlocking of the lock screen interface, electronic device 100 can control the electronic pet's state to change from the first state to the second state, where the second state is different from the first state. It can be understood that the second state can be different from the third state, or it can be the same as the third state.

[0210] In this way, since the AOD interface, lock screen interface, and desktop are all part of a unified desktop, the AOD interface, lock screen interface, and desktop share a single process, thereby avoiding cross-process calls to the electronic pet by the electronic device 100 when displaying the AOD interface, lock screen interface, and desktop in sequence.

[0211] As shown in Figures 7A-7C, in some embodiments, the unified desktop may include a lock screen interface, and the operation on the lock screen interface detected by the electronic device 100 may include an unlocking operation. It should be noted that the lock screen interface can be a screen-on lock screen interface or a screen-off lock screen interface, which can be understood as an AOD interface. This application embodiment does not limit the type of lock screen interface. In response to the unlocking operation on the lock screen interface, if the electronic device 100 fails to unlock, the electronic device 100 may display an unlock failure interface. Both the lock screen interface and the unlock failure interface include an electronic pet, but the state of the electronic pet on the unlock failure interface changes compared to its state on the lock screen interface. Optionally, when the electronic device 100 switches from displaying the lock screen interface to displaying the unlock failure interface, the state of the electronic pet may change according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed and movement trajectory. This application embodiment does not limit the form of the animation effect. If the electronic device 100 fails to unlock and displays an unlock failure interface, the electronic device 100 can continue to receive unlocking operations. If the electronic device 100 still fails to unlock, it can display a multiple unlock failure interface. Both the unlock failure interface and the multiple unlock failure interface include the electronic pet, but the state of the electronic pet in the multiple unlock failure interface changes compared to its state in the unlock failure interface. Optionally, when the electronic device 100 switches from displaying the unlock failure interface to displaying the multiple unlock failure interface, the state of the electronic pet can change according to an animation effect. The parameters of the animation effect include one or more of the following: movement speed and movement trajectory. This application embodiment does not limit the form of the animation effect.

[0212] It should be noted that the change in the electronic pet's state specifically refers to a change in the electronic pet's state after an operation on the unified desktop is detected, compared to the electronic pet's state before the operation was detected. Similarly, a change in the electronic pet's state on the unlock failure screen compared to its state on the lock screen, and a change in the electronic pet's state on the multiple unlock failure screens compared to its state on the lock screen, can be understood as the electronic pet's state on the multiple unlock failure screens differing from its state on the lock screen, or it can be the same as its state on the lock screen.

[0213] For example, as shown in FIG7A, the electronic device 100 can display a user interface 110, which can be the lock screen interface of the electronic device 100. The user interface 110 can include an electronic pet (e.g., a pet 111 in an agitated state, with its eyes open, one paw raised, and the other paw lowered). This embodiment of the application does not limit the state of the electronic pet in the lock screen interface. Optionally, the user interface 110 can also include a fingerprint recognition area 112, which can be used to collect the user's fingerprint. If the collected fingerprint information does not match the fingerprint information stored in the electronic device 100 (i.e., unlocking fails), the electronic device 100 is triggered to enter the unlocking failure interface. It should be noted that in addition to fingerprint unlocking, users can also use face unlocking, password unlocking, and pattern unlocking. The user's unlocking method is related to the user's security settings, and this embodiment of the application does not limit the unlocking method.

[0214] In some embodiments, the electronic device 100 may receive an unlocking operation from a user, such as an unlocking operation performed by the user on the fingerprint recognition area 112. In response to this operation, if the collected fingerprint information does not match the fingerprint information stored in the electronic device 100 (i.e., unlocking fails), the electronic device 100 may display an unlocking failure interface (e.g., the user interface 150 shown in FIG7B).

[0215] For example, as shown in FIG7B, the electronic device 100 can display a user interface 150, which may include an electronic pet (e.g., a pet 151 in a quiet state, with its eyes open and paws down). This embodiment does not limit the state of the electronic pet in the unlock failure interface. Optionally, the user interface 150 may also include a fingerprint recognition area 152, which can be used to collect the user's fingerprint. If the collected fingerprint information does not match the fingerprint information stored in the electronic device 100 (i.e., multiple (e.g., two) unlock failures), the electronic device 100 is triggered to enter the multiple unlock failure interface. It should be noted that in addition to fingerprint unlocking, users can also use face unlocking, password unlocking, and pattern unlocking. The unlocking method is related to the user's security settings, and this embodiment does not limit the unlocking method. Optionally, the user interface 150 may also include relevant information for prompting the user of unlock failure, such as prompt information 153, which may be "Unlock failed, please try again!". In some examples, the above prompts may not be conveyed to the user in the form of text, but in other ways, such as through voice broadcast.

[0216] In some embodiments, the electronic device 100 may continue to receive unlocking operations from the user, such as the user's unlocking operation on the fingerprint recognition area 152. In response to this operation, if the collected fingerprint information still does not match the fingerprint information stored in the electronic device 100 (i.e., multiple (e.g., two) unlocking failures), the electronic device 100 may display a multiple unlocking failure interface (e.g., the user interface 160 shown in FIG7C).

[0217] For example, as shown in FIG7C, the electronic device 100 may display a user interface 160, which may include an electronic pet (e.g., a sleeping pet 161 with its eyes closed and paws down). This embodiment does not limit the state of the electronic pet in the multiple unlock failure interface. Optionally, the user interface 160 may also include relevant information to prompt the user of multiple unlock failures, such as prompt message 162, which may be "Unlock failed again, please wait one minute and try again!". In some examples, the above prompt message may not be conveyed to the user in a text-based manner, but in other ways, such as through voice broadcast.

[0218] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0219] In some embodiments, the desktop may include application icons, and the electronic pet may be located around the application icons, in which case the electronic pet may be in a second state. It should be noted that the electronic pet being displayed around the application icons can be understood as the distance between the electronic pet and the application icons being less than a preset distance (e.g., 0.5 cm), for example, the electronic pet being displayed on the application icons. Upon detecting an operation on the application icons, the electronic pet on the desktop can change from the second state to a fourth state, which is different from the second state. The operations detected by the electronic device 100 on the application icons may include long-pressing the application icon, dragging the application icon, uninstalling the application icon, and clicking the application icon. Furthermore, operations on the application icons may also include installing the application icon and updating the application icon. This embodiment does not limit the type of operation on the application icons. Optionally, the electronic pet can change from the second state to the fourth state according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed and movement trajectory. This embodiment does not limit the form of the animation effect.

[0220] As shown in Figures 8A-8C, in some embodiments, the operation on the application icon detected by the electronic device 100 can be a long press operation. It should be noted that a long press operation specifically refers to touching the application icon for more than a preset duration (e.g., 2 seconds). Optionally, before the electronic pet is located around the application icon, the electronic pet can move from a non-UI element on the desktop to the area around the application icon. The non-UI element on the desktop can be a location other than an application icon, folder icon, or application card. Before detecting a long press operation, the electronic device 100 can control the electronic pet to be in a second state around the application icon. After detecting a long press operation, the electronic device 100 can control the electronic pet to change from the second state to a fourth state. When the operation on the application icon is a long press, the first expression of the electronic pet in the fourth state changes compared to the second expression of the electronic pet in the second state. For example, before detecting a long press operation, the electronic device 100 can control the electronic pet to be in a sleeping state on the application icon. After detecting a long press operation, the electronic device 100 can control the electronic pet to change from the sleeping state to a awake state.

[0221] For example, as shown in FIG8A, the electronic device 100 can display a user interface 120, which can be the desktop of the electronic device 100. The user interface 120 can include an electronic pet (e.g., an active pet 121 with its eyes open and its hands raised) located at a non-UI element on the desktop. This application embodiment does not limit the state of the electronic pet in the user interface 120.

[0222] In some embodiments, the electronic device 100 can control the electronic pet to move from a non-UI element on the desktop to around the application icon and display the user interface 210 as shown in FIG8B.

[0223] For example, as shown in FIG8B, the electronic device 100 can display a user interface 210, which may include one or more application icons (e.g., icon 211) and folder icons. The folder icons may contain one or more application icons, and the one or more application icons can be used to receive operations on the applications corresponding to the application icons (including but not limited to uninstalling applications, installing applications, updating applications, and launching applications). In addition, the user interface 210 may also include an electronic pet in a second state (e.g., a sleeping pet 212 with its eyes closed and paws down). This embodiment of the application does not limit the electronic pet in the second state located around the application icons.

[0224] In some embodiments, the electronic device 100 may receive a long press operation by a user on an application icon (e.g., icon 211) (e.g., touching the application icon for more than a preset duration (e.g., 2 seconds)). In response to this operation, the electronic device 100 may display the user interface 220 as shown in FIG8C.

[0225] For example, as shown in FIG8C, the electronic device 100 may display a user interface 220, which may include an application icon (e.g., icon 221) that can be long-pressed. In addition, the user interface 220 may also include an electronic pet in a fourth state (e.g., a pet 222 in a woken-up state, with its eyes open and paws down). The fourth state is different from the second state, and this application embodiment does not limit the electronic pet in the fourth state.

[0226] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0227] As shown in Figures 9A and 9B, in some embodiments, the operation on the application icon detected by the electronic device 100 can be a dragging operation. It should be noted that before detecting a dragging operation, the electronic device 100 can also detect a long-press operation on the application icon. Before detecting a dragging operation, the electronic device 100 can control the electronic pet to be in a second state around the application icon. After detecting a dragging operation, the electronic device 100 can control the electronic pet to change from the second state to a fourth state. When the operation on the application icon is dragging, the first position of the electronic pet in the fourth state changes relative to the second position of the electronic pet in the second state. For example, before detecting a dragging operation, the electronic device 100 can control the electronic pet to be in a quiet state on the application icon. After detecting a dragging operation, the electronic device 100 can control the electronic pet to be dragged along with the application icon.

[0228] For example, as shown in FIG9A, the electronic device 100 may display a user interface 220, which may include an application icon (e.g., icon 221) that can be long-pressed. In addition, the user interface 220 may also include an electronic pet in a second state (e.g., a pet 222 in a quiet state, with its eyes open and paws down). This embodiment of the application does not limit the electronic pet in the second state.

[0229] In some embodiments, the electronic device 100 may receive a drag operation by a user on an application icon (e.g., icon 221), and in response to the operation, the electronic device 100 may display a user interface 230 as shown in FIG9B.

[0230] For example, as shown in FIG9B, the electronic device 100 may display a user interface 230, which may include draggable application icons (e.g., icon 231). Furthermore, the user interface 230 may also include an electronic pet in a fourth state (e.g., a pet 232 dragged along with icon 231, the pet 232 having its eyes open and its paws down). The fourth state differs from the second state, and this embodiment does not limit the electronic pet in the fourth state.

[0231] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0232] As shown in Figures 10A-10C, in some embodiments, the operation on the application icon detected by the electronic device 100 may be an operation to uninstall the application icon. It should be noted that before detecting the operation to uninstall the application icon, the electronic device 100 may also detect an operation to long-press the application icon. Before detecting the operation to uninstall the application icon, the electronic device 100 may control the electronic pet to be located around the application icon. After detecting the operation to uninstall the application icon, the electronic device 100 may control the electronic pet to leave the uninstalled application icon (i.e., control the electronic pet's state to change). When the operation on the application icon is to uninstall the application icon, the third position of the electronic pet in the fourth state changes relative to the fourth position of the electronic pet in the second state. For example, before detecting the operation to uninstall the application icon, the electronic device 100 may control the electronic pet to be in a sleeping state on the application icon. After detecting the operation to uninstall the application icon, the electronic device 100 may control the electronic pet to leave the application icon and jump to another application icon.

[0233] For example, as shown in FIG10A, the electronic device 100 can display a user interface 210, which may include one or more application icons (e.g., icon 211) and folder icons. The folder icons may contain one or more application icons, and the one or more application icons can be used to receive operations on the applications corresponding to the application icons (including but not limited to uninstalling applications, installing applications, updating applications, and launching applications). In addition, the user interface 210 may also include an electronic pet in a second state (e.g., a pet 212 in a sleeping state, with its eyes closed and paws down). This embodiment of the application does not limit the electronic pet in the second state.

[0234] In some embodiments, the electronic device 100 may receive a long press operation by a user on an application icon (e.g., icon 211) (e.g., touching the application icon for more than a preset time (e.g., 2 seconds)). In response to this operation, the electronic device 100 may display the user interface 240 as shown in FIG10B.

[0235] For example, as shown in FIG10B, the electronic device 100 can display a user interface 240, which may include an uninstallation control (e.g., control 241) and a sharing control. The uninstallation control can be used to uninstall the application corresponding to the application icon, and the sharing control can be used to share the application corresponding to the application icon with other users. In addition, the user interface 240 may also include an electronic pet (e.g., a pet 242 in a woken-up state, with its eyes open and paws down). Optionally, the state of the electronic pet may be different from or the same as the second state. This application embodiment does not limit the state of the electronic pet in the user interface 240.

[0236] In some embodiments, the electronic device 100 may receive a user input operation (e.g., a click) on an uninstallation control (e.g., control 241), and in response to this operation, the electronic device 100 may display a user interface 250 as shown in FIG10C. In other embodiments, the electronic device 100 may receive a user input operation (e.g., a click) on a share control, and in response to this operation, the electronic device 100 may control the state of the electronic pet to change relative to the state of the electronic pet in the user interface 240. It should be noted that the state of the electronic pet may change differently depending on the operation performed on different controls (e.g., control 241 and the share control) in the user interface 240. For example, in response to a user operation on control 241, the electronic pet may move from application icon 211 to application icon 251; in response to a user operation on the share control, the electronic pet may move from application icon 211 to a non-UI element on the desktop.

[0237] For example, as shown in FIG10C, the electronic device 100 can display a user interface 250, which may include one or more application icons (e.g., icon 251) and folder icons. The folder icons may contain one or more application icons, and these application icons can be used to receive operations on the applications corresponding to the application icons (including but not limited to uninstalling applications, installing applications, updating applications, and launching applications). Furthermore, the user interface 250 may also include an electronic pet that has left the uninstalled application icon (e.g., a pet 252 that has jumped onto icon 251, with its eyes open and paws down). This electronic pet is in a fourth state. The electronic pet that has left the uninstalled application icon may also jump to a non-UI element on the desktop instead of jumping around other application icons. This embodiment of the application does not limit the electronic pet that has left the uninstalled application icon.

[0238] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0239] Figure 11 illustrates, exemplarily, the flow of a pet interaction method based on clicking an application icon, provided in an embodiment of this application.

[0240] As shown in Figure 11, the method may include:

[0241] S301, Electronic device 100 displays a second interface, the second interface including a first object, the first object being in a second state on the second interface.

[0242] S302, In response to a click on an application icon, the electronic device 100 displays a third interface, the third interface including a first object, the first object being in a fifth state on the third interface.

[0243] As mentioned above, in the embodiments of this application, the first object can be a system-level electronic pet, hereinafter referred to as an electronic pet.

[0244] In some embodiments, the desktop may include application icons, and the electronic pet may be located around the application icons, in which case the electronic pet may be in a second state. It should be noted that the electronic pet being displayed around the application icons can be understood as the distance between the electronic pet and the application icons being less than a preset distance (e.g., 0.5 cm), for example, the electronic pet being displayed on the application icons. Upon detecting an operation on the application icons, the electronic pet on the desktop can change from the second state to a fourth state, which is different from the second state. The operations detected by the electronic device 100 on the application icons may include long-pressing the application icon, dragging the application icon, uninstalling the application icon, and clicking the application icon. Furthermore, operations on the application icons may also include installing the application icon and updating the application icon. This embodiment does not limit the type of operation on the application icons. Optionally, the electronic pet can change from the second state to the fourth state according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed and movement trajectory. This embodiment does not limit the form of the animation effect.

[0245] As shown in Figures 12A-12C, in some embodiments, the operation on the application icon detected by the electronic device 100 may be a click on the application icon. In response to the click on the application icon, the electronic device 100 can launch the application corresponding to the application icon and display a third interface. This third interface may include the user interface and status bar of the application corresponding to the application icon. The third interface also includes an electronic pet, which can be displayed in the status bar. At this time, the electronic pet is in a fifth state, which is different from the second state. During the launch of the application corresponding to the application icon, the electronic device 100 can display the application's launch animation. It should be noted that after detecting the click on the application icon, launching the application requires a preset time (e.g., 0.2 seconds). During the waiting period for the application to launch, the electronic device 100 can display the application's launch animation. This launch animation adds a transition between the desktop and the third interface, which helps to facilitate a smooth transition of the user interface displayed by the electronic device 100 from the desktop to the third interface, improving the user experience. When displaying the application's launch animation, the electronic device 100 can control the electronic pet to change from being displayed around the application icon to being displayed within the launch animation. After launching the application corresponding to the application icon, the electronic device 100 can control the electronic pet's display position to change to the status bar. The user interface after the application is launched is displayed in full screen. That is, when the electronic device 100 switches from displaying the desktop to the application's user interface, the electronic pet can change from a second state to a fifth state according to a second animation effect. The parameters of the second animation effect include one or more of the following: a second movement speed, a second movement trajectory. This application embodiment does not limit the form of the second animation effect. For example, the application launch animation effect can be that the application window gradually enlarges until the application's user interface is displayed in full screen. After controlling the electronic pet to change from being displayed around the application icon to being displayed in the launch animation effect, the electronic device 100 can control the electronic pet to gradually move its position following the application window, and can control at least one of the electronic pet's appearance, posture, and expression to change during the electronic pet's movement. For example, during the electronic pet's movement, the electronic device 100 can control the electronic pet's size to gradually decrease until it enters the status bar, at which point the electronic pet's size stops decreasing, so that the electronic pet's size reaches its minimum size during the size change process when it enters the status bar. In addition to controlling the changes in the size of the electronic pet, the electronic device 100 can also control the changes in the posture of the electronic pet, such as rotating or jumping; the electronic device 100 can also control the changes in the facial expressions of the electronic pet, such as smiling or crying.

[0246] For example, as shown in FIG12A, the electronic device 100 can display a user interface 260, which may include one or more application icons (e.g., icon 261) and folder icons. The folder icons may contain one or more application icons, and the one or more application icons can be used to receive operations on the applications corresponding to the application icons (including but not limited to uninstalling applications, installing applications, updating applications, and launching applications). In addition, the user interface 260 may also include an electronic pet in a second state, such as an active pet 262, whose eyes are open and its paws are raised. This embodiment of the application does not limit the electronic pet in the second state.

[0247] In some embodiments, the electronic device 100 may receive an input operation (e.g., a click) performed by a user on an application icon (e.g., icon 261), and in response to the operation, the electronic device 100 may display a user interface 270 as shown in FIG12B.

[0248] For example, as shown in FIG12B, the electronic device 100 can display a user interface 270, which may include an application window (e.g., window 271). The area of ​​this window is relatively small, i.e., smaller than a preset area. This embodiment does not limit the specific value of the preset area. When the window area is small, a scaled-down version of the application's user interface can be displayed within the window. For example, window 271 may display a scaled-down version of the settings application's user interface corresponding to icon 261. It should be noted that when the window area is small, a preset image corresponding to the application's user interface can also be displayed within the window. This preset image can be a black screen, a white screen, or a grayscale image, etc. If the window displays a preset image corresponding to the application's user interface, the electronic device 100 can replace the preset image with the application's user interface after the application is launched. Optionally, when the window area is small, the window may have a certain degree of transparency. As the window area increases, the transparency gradually decreases, thus showcasing the application window gradually appearing from nothing. In addition, the user interface 270 may also include an electronic pet in the startup animation. The electronic pet in the startup animation can gradually move its position following the application window, and at least one of the electronic pet's appearance, posture, and expression can change during the movement. For example, an active pet 272 has its eyes open and its hands raised. The pet 272 can gradually move its position following the window 271, and its size gradually decreases during the movement. This application embodiment does not limit the electronic pet in the startup animation.

[0249] In some embodiments, the electronic device 100 may gradually enlarge the application window (e.g., window 271) until the window is displayed in full screen, i.e., the user interface 280 shown in FIG12C is displayed.

[0250] For example, as shown in FIG12C, the electronic device 100 may display a user interface 280, which may include an electronic pet in a fifth state in the status bar, such as an active pet 281. The active pet 281 has its eyes open and its paws raised. The size of the pet 281 stops shrinking when it enters the status bar, reaching its minimum size during the size change process. This embodiment of the application does not limit the electronic pet located in the status bar. In addition, the user interface 280 may also include a return control (e.g., control 282), which can be used to exit the user interface of the application, for example, switching the user interface displayed by the electronic device 100 from the application's user interface to the desktop.

[0251] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0252] Optionally, the startup animation for each application can be different. For example, each application can have its own unique startup animation, and the status changes of the virtual pet can also be different accordingly.

[0253] It should be noted that, in addition to the application window gradually enlarging until the application's user interface is displayed in full screen, the application's startup animation can also be the application window gradually appearing while the desktop gradually fades out. In this case, the electronic pet's state change can be, for example, the electronic pet gradually changing from a blurry display to a clear display as the application window gradually appears. This application embodiment does not limit the specific type of application startup animation.

[0254] It should be noted that the application's user interface can also have other display methods. For example, after launching the application, the electronic device 100 can enter split-screen mode, and the display screen of the electronic device 100 can be divided into two areas. The application's user interface is displayed in one area, and other user interfaces (such as the desktop) are displayed in the other area. For example, if the application's user interface is displayed in the upper area, the electronic pet's state change can be, for example, the electronic pet's position gradually increasing as the application window enlarges, moving from the launch animation to entering the status bar; if the application's user interface is displayed in the lower area, the electronic pet's state change can also be, for example, the electronic pet's position gradually increasing as the application window enlarges, moving from the launch animation to entering the sidebar. This application embodiment does not limit the display form of the application's user interface.

[0255] As shown in Figures 13A-13C, in some embodiments, the unified desktop may include a multitasking interface. This multitasking interface can be displayed as a series of application windows, each application window representing a user interface for an application running in the background. Users can quickly view and manage background applications through the multitasking interface, such as switching, closing, or locking applications.

[0256] The electronic device 100 can display a third interface, which may include the user interface of the application corresponding to the application icon (e.g., the user interface of the settings application), a status bar, and an electronic pet, which can be displayed in the status bar. At this time, the electronic pet is in a fifth state. Upon detecting an operation to enter a multitasking interface (e.g., a user swiping up from the bottom of the screen), the electronic device 100 can display the multitasking interface, which includes the electronic pet, but the electronic pet's state in the multitasking interface changes compared to the fifth state. Optionally, when the electronic device 100 switches from displaying the third interface to displaying the multitasking interface, the electronic pet's state can change according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed, movement trajectory. This embodiment does not limit the form of the animation effect. Operations on the unified desktop detected by the electronic device 100 may include sliding application windows. In response to sliding application windows, the electronic device 100 can switch the application window located in the middle of the display screen from the window of the first application to the window of the second application, and the application window located in the middle of the display screen can be fully displayed. It should be noted that the multitasking interface before and after swiping the application window includes the electronic pet. Before switching the application window located in the center of the display from the window of the first application to the window of the second application, the electronic pet can be located around the window of the first application. After switching the application window located in the center of the display from the window of the first application to the window of the second application, the electronic pet can be located around the window of the second application. It should be noted that the electronic pet being displayed around the application window can be understood as the distance between the electronic pet and the application window being less than a preset distance (e.g., 0.5 cm), for example, the electronic pet being displayed on the application window. It can be understood that the electronic device 100 can control the electronic pet to always be located around the application window in the center of the display. Optionally, the state of the electronic pet can change according to an animation effect, the parameters of which include one or more of the following: movement speed, movement trajectory. This application embodiment does not limit the form of the animation effect.

[0257] For example, as shown in FIG13A, the electronic device 100 may display a user interface 280, which may include an electronic pet in the fifth state in the status bar, such as an active pet 281, whose eyes are open and whose hands are raised. This application embodiment does not limit the electronic pet located in the status bar.

[0258] In some embodiments, the electronic device 100 may receive an operation to enter a multitasking interface (e.g., a user swiping up from the bottom of the screen), and in response to the operation, the electronic device 100 may display a multitasking interface (e.g., user interface 310 shown in FIG13B).

[0259] For example, as shown in FIG13B, the electronic device 100 can display a user interface 310, which may include a complete window of a first application (e.g., window 311) and a partial window of a second application. The area of ​​the window of the first application is small, that is, the area of ​​the window of the first application is smaller than a preset area. This embodiment does not limit the specific value of the preset area or the number and type of application windows. When the area of ​​the window of the first application is small, a scaled-down version of the user interface of the first application can be displayed within the window of the first application. For example, a scaled-down version of the user interface of the settings application can be displayed within window 311. In addition, the user interface 310 may also include an electronic pet located around the window of the first application. The electronic pet can gradually move its position as the window of the first application slides, and at least one of the shape, posture, and expression of the electronic pet can change during the movement. For example, an active pet 312 has its eyes open and its hands raised. For example, if window 311 slides to the left, pet 312 can move to the right to keep pet 312 always in the center of the display screen. It should be noted that the state of the electronic pet is different from the fifth state. For example, pet 281 in the fifth state is located in the status bar, while pet 312 is located on the window of the first application, and pet 312 is larger than pet 281 in the fifth state. This application embodiment does not limit the electronic pet located around the window of the first application.

[0260] In some embodiments, the electronic device 100 may receive an operation (e.g., a leftward swipe) to switch the window of an application located in the middle of the display screen from the window of a first application (e.g., window 311) to the window of a second application (e.g., window 321). In response to this operation, the electronic device 100 may display the user interface 320 shown in FIG13C.

[0261] For example, as shown in FIG13C, the electronic device 100 can display a user interface 320, which may include a complete window of a second application (e.g., window 321) and a partial window of a first application. The area of ​​the window of the second application is smaller, that is, the area of ​​the window of the second application is smaller than a preset area. This embodiment does not limit the specific value of the preset area or the number and type of application windows. When the area of ​​the window of the second application is smaller, a scaled-down version of the user interface of the second application can be displayed within the window of the second application. For example, a scaled-down version of the user interface of a calculator application can be displayed within window 321. In addition, the user interface 320 may also include an electronic pet located around the window of the second application. The electronic pet can gradually move its position as the window of the second application slides, and at least one of the shape, posture, and expression of the electronic pet can change during the movement. For example, an active pet 322 has its eyes open and its hands raised. For example, if window 321 slides to the left, pet 322 can move to the right to keep pet 322 always in the center of the display screen. It should be noted that the state of the electronic pet is different from the state of the electronic pet located around the window of the first application. For example, pet 312 is located on the window of the first application, and pet 322 is located on the window of the second application. It should also be noted that at least one of the appearance, posture, and expression of the electronic pets located around the windows of different applications can be different. For example, the electronic pet located on the window of the first application can have a smiling expression, while the electronic pet located on the window of the second application can have a crying expression. This application embodiment does not limit the electronic pet located around the window of the second application.

[0262] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0263] Conversely, the electronic device 100 can display a multitasking interface. Upon detecting a selection operation on an application window (e.g., a user's click operation on a settings application window), the electronic device 100 can display a third interface (e.g., the user interface of the settings application). Both the multitasking interface and the third interface include the electronic pet, but the electronic pet's state on the third interface changes compared to its state on the multitasking interface (e.g., the electronic pet's display position changes from the settings application window to the status bar).

[0264] As shown in Figures 14A-14C, in some embodiments, the unified desktop may include a multitasking interface, which may be displayed as a series of application windows. Each application window may be a user interface for an application running in the background. Users can quickly view and manage applications running in the background through the multitasking interface, such as switching, closing, locking applications, etc.

[0265] Electronic device 100 can display a desktop (e.g., user interface 120), which includes an electronic pet. The electronic pet can be in a second state at this time. Upon detecting an operation to enter a multitasking interface (e.g., a user swiping up from the bottom of the screen), electronic device 100 can display the multitasking interface, which includes the electronic pet. However, the electronic pet's state in the multitasking interface changes compared to the second state. Optionally, when electronic device 100 switches from displaying the desktop to displaying the multitasking interface, the electronic pet's state can change according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed, movement trajectory. This embodiment does not limit the form of the animation effect. Operations on the unified desktop detected by electronic device 100 can include swiping an application window. In response to swiping an application window, electronic device 100 can switch the application window located in the middle of the display screen from the window of the first application to the window of the second application. The application window located in the middle of the display screen can be fully displayed. It should be noted that both the multitasking interface before and after swiping the application window include the electronic pet. Before switching the window of the application located in the center of the display screen from the window of the first application to the window of the second application, the electronic pet can be located around the window of the first application. After switching the window of the application located in the center of the display screen from the window of the first application to the window of the second application, the electronic pet can be located around the window of the second application. It should be noted that the electronic pet being displayed around the application window can be understood as the distance between the electronic pet and the application window being less than a preset distance (e.g., 0.5 cm), for example, the electronic pet being displayed on the application window. It is understood that the electronic device 100 can control the electronic pet to always be located around the application window in the center of the display screen. Optionally, the state of the electronic pet can change according to an animation effect, the parameters of which include one or more of the following: movement speed, movement trajectory. This application embodiment does not limit the form of the animation effect.

[0266] For example, as shown in FIG14A, the electronic device 100 may display a user interface 120, which may be the desktop of the electronic device 100. The user interface 120 may include an electronic pet in a second state (e.g., an active pet 121 with its eyes open and its hands raised). This application embodiment does not limit the electronic pet in the second state.

[0267] In some embodiments, the electronic device 100 may receive an operation to enter a multitasking interface (e.g., a user swiping up from the bottom of the screen), and in response to the operation, the electronic device 100 may display a multitasking interface (e.g., user interface 310 shown in FIG14B).

[0268] For example, as shown in FIG14B, the electronic device 100 can display a user interface 310, which may include a complete window of a first application (e.g., window 311) and a partial window of a second application. The area of ​​the window of the first application is small, that is, the area of ​​the window of the first application is smaller than a preset area. This embodiment does not limit the specific value of the preset area or the number and type of application windows. When the area of ​​the window of the first application is small, a scaled-down version of the user interface of the first application can be displayed within the window of the first application. For example, a scaled-down version of the user interface of the settings application can be displayed within window 311. In addition, the user interface 310 may also include an electronic pet located around the window of the first application. The electronic pet can gradually move its position as the window of the first application slides, and at least one of the shape, posture, and expression of the electronic pet can change during the movement. For example, an active pet 312 has its eyes open and its hands raised. For example, if window 311 slides to the left, pet 312 can move to the right to keep pet 312 always in the center of the display screen. It should be noted that the state of the electronic pet is different from the second state. For example, in the second state, pet 121 is located in the status bar, while pet 312 is located on the window of the first application, and the size of pet 312 is smaller than that of pet 121 in the second state. This application embodiment does not limit the electronic pet located around the window of the first application.

[0269] In some embodiments, the electronic device 100 may receive an operation (e.g., a leftward swipe) to switch the window of an application located in the middle of the display screen from the window of a first application (e.g., window 311) to the window of a second application (e.g., window 321). In response to this operation, the electronic device 100 may display the user interface 320 as shown in FIG14C.

[0270] For example, as shown in FIG14C, the electronic device 100 can display a user interface 320, which may include a complete window of a second application (e.g., window 321) and a partial window of a first application. The area of ​​the window of the second application is smaller, that is, the area of ​​the window of the second application is smaller than a preset area. This embodiment does not limit the specific value of the preset area or the number and type of application windows. When the area of ​​the window of the second application is smaller, a scaled-down version of the user interface of the second application can be displayed within the window of the second application. For example, a scaled-down version of the user interface of a calculator application can be displayed within window 321. In addition, the user interface 320 may also include an electronic pet located around the window of the second application. The electronic pet can gradually move its position as the window of the second application slides, and at least one of the shape, posture, and expression of the electronic pet can change during the movement. For example, an active pet 322 has its eyes open and its hands raised. For example, if window 321 slides to the left, pet 322 can move to the right to keep pet 322 always in the center of the display screen. It should be noted that the state of the electronic pet is different from the state of the electronic pet located around the window of the first application. For example, pet 312 is located on the window of the first application, and pet 322 is located on the window of the second application. It should also be noted that at least one of the appearance, posture, and expression of the electronic pets located around the windows of different applications can be different. For example, the electronic pet located on the window of the first application can have a smiling expression, while the electronic pet located on the window of the second application can have a crying expression. This application embodiment does not limit the electronic pet located around the window of the second application.

[0271] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0272] Conversely, electronic device 100 can display a multitasking interface. Upon detecting a return to the desktop operation, electronic device 100 can display the desktop. Both the aforementioned multitasking interface and desktop include the electronic pet, but the electronic pet's state on the desktop has changed compared to its state on the multitasking interface (for example, the electronic pet's display position changes from the settings application window to the desktop).

[0273] As shown in Figures 15A-15C, in some embodiments, the electronic device 100 can display a third interface. This third interface may include the user interface of the application corresponding to the application icon (e.g., the user interface of the settings application), a status bar, and an electronic pet, which can be displayed in the status bar. The electronic pet is currently in its fifth state. The operation detected by the electronic device 100 on the unified desktop can be a return-to-desktop operation. In response to the return-to-desktop operation, the electronic device 100 can switch from displaying the third interface to displaying the desktop. The desktop may include the electronic pet, which is currently in its second state, different from the fifth state. During the switch from the third interface to the desktop, the electronic device 100 can display a return-to-desktop animation. It should be noted that after detecting the return-to-desktop operation, a preset time (e.g., 0.2 seconds) is required for the switch. During the wait for the return-to-desktop, the electronic device 100 can display a return-to-desktop animation. This animation adds a transition between the third interface and the desktop, promoting a smooth and natural transition of the user interface from the third interface to the desktop, thus improving the user experience. When displaying the animation of returning to the desktop, the electronic device 100 can control the electronic pet to change its display from the status bar to the desktop. After switching from displaying the third interface to displaying the desktop, the electronic device 100 can control the electronic pet's display position to change to the vicinity of the application icon. This application icon can be the icon of the application whose user interface was previously displayed on the desktop. That is, when the electronic device 100 switches from displaying the third interface to the desktop, the electronic pet can change from the fifth state to the second state according to the animation. The parameters of the animation include one or more of the following: movement speed and movement trajectory. This application embodiment does not limit the form of the animation. It should be noted that after switching from displaying the third interface to displaying the desktop, in addition to controlling the electronic pet's display position to change to the vicinity of the application icon, the electronic device 100 can also control the electronic pet's display position to change to the desktop (a position on the desktop other than the application icon). This application embodiment does not limit the display position of the electronic pet after the user interface displayed by the electronic device 100 switches to the desktop. For example, the animation for returning to the desktop could be that the application window gradually shrinks until it disappears, while the desktop is fully displayed. After controlling the electronic pet to change its display from the status bar to the desktop return animation, the electronic device 100 can control the electronic pet to gradually move its position following the application window, and can control at least one of the electronic pet's appearance, posture, and expression to change during the movement of the electronic pet.For example, during the movement of the electronic pet, the electronic device 100 can control the electronic pet's size to gradually increase until it enters the desktop, at which point the increase stops, ensuring the electronic pet reaches its maximum size during the size change process upon entering the desktop. Besides controlling the electronic pet's size, the electronic device 100 can also control the electronic pet's posture, such as rotating or jumping; the electronic device 100 can also control the electronic pet's facial expressions, such as smiling or crying. It should be noted that the above-mentioned return-to-desktop operation can be a swipe up from the bottom of the display screen (bottom left, middle, or right), a click on the Home button, a click on the return control, etc. This embodiment does not limit the type of return-to-desktop operation.

[0274] For example, as shown in FIG15A, the electronic device 100 may display a user interface 280, which may include an electronic pet in a fifth state in the status bar, such as an active pet 281 with its eyes open and hands raised. This embodiment of the application does not limit the electronic pet located in the status bar. In addition, the user interface 280 may also include a return control (e.g., control 282), which can be used to exit the user interface of the application, for example, switching the user interface displayed by the electronic device 100 from the third interface to the desktop.

[0275] In some embodiments, the electronic device 100 may receive an operation to return to the desktop, such as a user input operation (e.g., a click) on a return control (e.g., control 282), and in response to the operation, the electronic device 100 may display a user interface 270 as shown in FIG15B.

[0276] For example, as shown in FIG15B, the electronic device 100 can display a user interface 270, which may include an application window (e.g., window 271). In this case, the area of ​​the window is small, that is, the area of ​​the window is smaller than a preset area. This embodiment does not limit the specific value of the preset area. When the window area is small, a scaled-down version of the application's user interface can be displayed within the window. For example, window 271 can display a scaled-down version of the user interface of the settings application corresponding to icon 261. It should be noted that when the window area is small, a preset image corresponding to the application's user interface can also be displayed within the window. This preset image can be a black screen, a white screen, or a grayscale image, etc. Optionally, when the window area is small, the window can have a certain degree of transparency. As the window area decreases, the transparency within the window gradually increases, which can demonstrate the display effect of the application window gradually disappearing from view. In addition, the user interface 270 may also include an electronic pet in the animation of returning to the desktop. The electronic pet in the animation of returning to the desktop can gradually move its position with the application window, and at least one of the electronic pet's appearance, posture, and expression can change during the movement. For example, the active pet 272 has its eyes open and its hands raised. The pet 272 can gradually move its position with the window 271, and its size gradually increases during the movement. This application embodiment does not limit the electronic pet in the animation of returning to the desktop.

[0277] In some embodiments, the electronic device 100 may gradually shrink the application window (e.g., window 271) until it disappears, while fully displaying the desktop, i.e., displaying the user interface 260 as shown in FIG15C.

[0278] For example, as shown in FIG15C, the electronic device 100 can display a user interface 260, which may include one or more application icons (e.g., icon 261) and folder icons. The folder icons may contain one or more application icons, and these application icons can be used to receive operations on the applications corresponding to the application icons (including but not limited to uninstalling, installing, updating, and launching applications). Furthermore, the user interface 260 may also include an electronic pet in a second state, such as an active pet 262. In this active state, the pet 262 has its eyes open and its paws raised. The size of the pet 262 stops increasing when it enters the desktop, reaching its maximum size during the size change process. This embodiment does not limit the electronic pet in the second state. It should be noted that after switching from displaying the third interface to displaying the desktop, the electronic device 100 can control the display position of the electronic pet to change to the vicinity of the application icon, and can also control the display position of the electronic pet to change to the desktop (the position on the desktop other than the application icon). This application embodiment does not limit the display position of the electronic pet after the user interface displayed by the electronic device 100 is switched to the desktop.

[0279] Optionally, upon receiving an operation to return to the desktop, the electronic device 100 can switch the application corresponding to the application icon to the background or exit the application; this embodiment does not limit this. Taking switching the application to the background as an example, after the user interface displayed by the electronic device 100 switches to the desktop, if the electronic device 100 receives another operation to launch the application corresponding to the application icon (e.g., icon 261) (e.g., the settings application), it can launch the application corresponding to the application icon again. During the process of launching the application corresponding to the application icon, the electronic device 100 can again display the application's launch animation. While displaying the application's launch animation, the electronic device 100 can again control the electronic pet to change its display position from around the application icon to within the launch animation. After launching the application corresponding to the application icon, the electronic device 100 can again control the electronic pet's display position to change to the status bar. It should be noted that, in this case, since the application corresponding to the application icon is always running in the background, after receiving the operation to launch the application corresponding to the application icon (e.g., icon 261) (e.g., the settings application), the electronic device 100 can launch the application corresponding to the application icon (e.g., icon 261) (e.g., the settings application) and display the third interface (e.g., user interface 280) without waiting for a long time. Furthermore, the time required to launch the application when the application corresponding to the application icon is always running in the background (i.e., the display time of the launch animation when the application corresponding to the application icon is always running in the background) can be different from the time required to launch the application when the application corresponding to the application icon is launched for the first time (i.e., the display time of the launch animation when the application corresponding to the application icon is launched for the first time). For example, the time required to launch the application when the application corresponding to the application icon is always running in the background (i.e., the display time of the launch animation when the application corresponding to the application icon is always running in the background) can be shorter than the time required to launch the application when the application corresponding to the application icon is launched for the first time (i.e., the display time of the launch animation when the application corresponding to the application icon is launched for the first time). When displaying the application's launch animation, the electronic device 100 can control the electronic pet to change its display position from around the application icon to within the launch animation more quickly than when the application is launched for the first time, even when the application is running in the background. After launching the application corresponding to the application icon, the electronic device 100 can control the electronic pet's display position to change to the status bar more quickly than when the application is launched for the first time, even when the application is running in the background.

[0280] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0281] Optionally, the animation for returning to the home screen can be different for each application. For example, each application can have its own unique animation for returning to the home screen, and the status changes of the virtual pet can also be different accordingly.

[0282] It should be noted that the animation effect of returning to the desktop can be, in addition to the application window gradually shrinking until it disappears and the desktop is fully displayed, the application window can also gradually disappear and the desktop gradually appears. In this case, the state change of the electronic pet can be, for example, the electronic pet gradually changes from clear display to blurry display as the application window gradually disappears. The embodiments of this application do not limit the specific type of animation effect of returning to the desktop.

[0283] In the above embodiments, the desktop is used as an example. The desktop includes application icons, and the electronic device 100 can detect operations on the application icons on the desktop (e.g., launching the application corresponding to the application icon by clicking it), thereby controlling the state of the electronic pet to change. It should be noted that the unified desktop may also include a sidebar, which may also include application icons, and the electronic pet may be located around the application icons in the sidebar. When an operation is received on an application icon in the sidebar, the electronic device 100 can control the state of the electronic pet to change, the principle of which is the same as described above and will not be repeated here. The unified desktop may also include system applications, such as the negative one screen, which may also include application icons, and the electronic pet may be located around the application icons in the negative one screen. When an operation is received on an application icon in the negative one screen, the electronic device 100 can control the state of the electronic pet to change, the principle of which is the same as described above and will not be repeated here.

[0284] In the above embodiments, taking an application icon as an example, the electronic device 100 can detect operations on the application icon (e.g., launching the application corresponding to the application icon by clicking it), thereby controlling the state of the electronic pet to change. It should be noted that the electronic device 100 can also detect operations on UI elements of the unified desktop other than application icons and control the state of the electronic pet accordingly, such as application cards. Application cards can be located on the desktop, the negative one screen, or other user interfaces, and the electronic pet can be located around the application card. When an operation is received on an application card, the electronic device 100 can control the state of the electronic pet to change, the principle of which is the same as described above and will not be repeated here. It should be noted that the electronic pet being displayed around an application card can be understood as the distance between the electronic pet and the application card being less than a preset distance (e.g., 0.5 cm), for example, the electronic pet being displayed on the application card.

[0285] As shown in Figures 16A-16B, in some embodiments, the unified desktop may include a desktop wallpaper containing pet interactive elements (e.g., pet bed, pet toys, pet food, etc.). The desktop may include an electronic pet in a second state, which may include a fifth position of the electronic pet, the fifth position being the position around the pet interactive elements; that is, the electronic pet may be displayed around the pet interactive elements. As mentioned above, the desktop wallpaper is the background image used by the desktop of the electronic device 100, located below the layer of first UI elements such as application icons, application cards, and folder icons. The electronic pet may be located on the same layer as the desktop wallpaper. The electronic device 100 can control the electronic pet to leave the area around the pet interactive elements. Optionally, before controlling the electronic pet to leave the area around the pet interactive elements, the electronic device 100 may detect an input operation on the desktop (e.g., a click operation on a non-UI element on the desktop). For example, the electronic pet leaving the vicinity of the pet interaction element can specifically include the electronic pet changing from a second state to a sixth state on the desktop. This sixth state can include the electronic pet's sixth position, which is a position around a first UI element. The first UI element can include one or more of the following: application icons, application cards, and folder icons. This embodiment does not limit the type of the first UI element. That is, the electronic pet can change from being displayed around the pet interaction element to being displayed around the first UI element. It should be noted that displaying the electronic pet around the pet interaction element can be understood as the distance between the electronic pet and the pet interaction element being less than a preset distance (e.g., 0.5 cm), for example, the electronic pet being displayed inside a pet bed. Displaying the electronic pet around the first UI element can be understood as the distance between the electronic pet and the first UI element being less than a preset distance (e.g., 0.5 cm), for example, the electronic pet being displayed on an application icon. Optionally, the electronic pet can change from the second state to the sixth state according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed and movement trajectory. This embodiment does not limit the form of the animation effect.

[0286] For example, as shown in FIG16A, the electronic device 100 can display a user interface 330, which can be the desktop of the electronic device 100. The user interface 330 can include an electronic pet in a second state located around a pet interaction element (e.g., a sleeping pet 331 with its eyes closed and paws down, sleeping inside a pet bed). This embodiment of the application does not limit the electronic pet in a second state located around the pet interaction element. In addition, the user interface 330 can also include a wallpaper, which can contain pet interaction elements (e.g., pet interaction element 332). The pet interaction elements can be used for the electronic pet to interact with, for example, the pet 331 sleeping inside the pet interaction element 332. It should be noted that the type of pet interaction element can be related to the shape of the electronic pet. For example, if the electronic pet is shaped like a cat, the pet interaction element can be a cat bed, a cat tree, a cat toy, or dried fish, etc. As another example, if the electronic pet is shaped like a dog, the pet interaction element can be a dog bed, a bone, or a flying saucer, etc. This application does not limit the types of elements that allow interaction with pets.

[0287] In some embodiments, the electronic device 100 can control the electronic pet to leave the vicinity of the pet interaction element and display the user interface 340 as shown in FIG16B. Optionally, before controlling the electronic pet to leave the vicinity of the pet interaction element, the electronic device 100 can detect input operations on the desktop (e.g., click operations on non-UI elements on the desktop).

[0288] For example, as shown in FIG16B, the electronic device 100 can display a user interface 340, which can be the desktop of the electronic device 100. The user interface 340 can include an electronic pet in a sixth state located around a first UI element (e.g., an active pet 341 with its eyes open and hands raised, the pet 341 on an application icon). This embodiment of the application does not limit the type of electronic pet in a sixth state located around the first UI element. In addition, the user interface 340 may also include one or more first UI elements (e.g., icon 342), wherein the first UI element can be used to receive operations on the application corresponding to the first UI element (including but not limited to uninstalling the application, installing the application, updating the application, and launching the application). This embodiment of the application does not limit the type of first UI element.

[0289] It should be noted that the electronic pet leaving the pet interaction element can include not only changing the electronic pet's display position from around the pet interaction element to around the first UI element, but also changing its display position from around the pet interaction element to a position on the desktop other than the first UI element. This application embodiment does not limit the display position of the electronic pet after leaving the pet interaction element.

[0290] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0291] It should be noted that HeYi Desktop can provide desktop wallpapers containing pet interactive elements. At the software level, the desktop wallpaper containing pet interactive elements is actually a software interface. This interface can be used to send data to the pet management module so that the pet management module can perceive the desktop wallpaper containing pet interactive elements, and thus enable the pet management module to interact with the pet interactive elements in the desktop wallpaper.

[0292] As shown in Figures 17A and 17B, in some embodiments, the desktop may not include the electronic pet. Upon detecting input to wake up the voice assistant, the electronic device 100 can wake up the voice assistant and display a fourth interface. This fourth interface includes a voice assistant application interface and the electronic pet, which floats within the voice assistant application interface. It should be noted that the voice assistant's image on the electronic device 100 is updated to the electronic pet; that is, the electronic pet displayed on the electronic device 100 has the permissions of the voice assistant. These permissions may include, but are not limited to, one or more of the following: voice interaction, installing applications, updating applications, uninstalling applications, powering on, powering off, changing system settings, setting alarms, and scheduling. Traditional voice assistants lack a concrete image and are relatively impersonal to users. Using an electronic pet as the voice assistant's image on the electronic device 100 makes the voice assistant more tangible, thereby increasing the frequency of user interaction with the system software.

[0293] In some embodiments, the input for waking up the voice assistant can be voice input. For example, as shown in FIG17A, the electronic device 100 can display a user interface 350, which can be the desktop of the electronic device 100. The electronic device 100 can display a desktop, or it can display a user interface other than the desktop; this embodiment does not limit this. Optionally, the user interface 350 may include, but is not limited to, the current date, time, and weather. Below the current date, time, and weather, one or more application icons (e.g., music application icon, settings application icon, etc.) and folder icons may be included, wherein the folder icons may contain one or more application icons, and the one or more application icons can be used to receive operations on the applications corresponding to the application icons (including but not limited to uninstalling applications, installing applications, updating applications, launching applications). Below the one or more application icons and the folder icons, a page indicator is also included, which is used to indicate the positional relationship between the currently displayed page and other pages. Optionally, multiple tray icons (e.g., dialer application icon, messaging application icon, browser application icon, camera application icon, etc.) are displayed below the page indicator, and the tray icons can remain displayed when switching pages. In some embodiments, the page indicator may not be part of the page and may exist independently; this application does not limit this.

[0294] In some embodiments, the electronic device 100 can detect voice input to wake up the voice assistant. In response to this operation, the electronic device 100 can wake up the voice assistant and display a fourth interface, such as the user interface 360 ​​shown in FIG17B.

[0295] For example, as shown in FIG17B, the electronic device 100 may display a user interface 360, which may include a voice assistant application user interface and a floating electronic pet (such as pet 361). The electronic pet serves as the image of the voice assistant, can receive and process user input (such as voice input, text input, image input, etc.), exercise system-level permissions, and implement system functions.

[0296] As shown in Figures 17C-17D, in some embodiments, the desktop may include an electronic pet. Upon detecting input to wake up the voice assistant, the electronic device 100 can wake up the voice assistant and display a fourth interface. This fourth interface includes a voice assistant application interface and an electronic pet, which floats within the voice assistant application interface. When the electronic pet floats within the voice assistant application interface, it is in a seventh state, which differs from the second state. Optionally, the electronic pet can change from the second state to the seventh state according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed, movement trajectory. This application embodiment does not limit the form of the animation effect. It should be noted that the voice assistant's image in the electronic device 100 is updated to an electronic pet; that is, the electronic pet displayed in the electronic device 100 has the permissions of the voice assistant. These permissions may include, but are not limited to, one or more of the following: voice interaction, installing applications, updating applications, uninstalling applications, powering on, powering off, changing system settings, setting alarms, and scheduling. Traditional voice assistants lack a concrete image and are relatively impersonal to users. Electronic pets, as the image of voice assistants in electronic devices 100, can make voice assistants more concrete, thereby increasing the frequency of users using system software.

[0297] In other embodiments, the input for waking up the voice assistant can be input applied to the electronic pet (e.g., petting the electronic pet). Exemplarily, as shown in FIG17C, the electronic device 100 can display a user interface 120, which can be the desktop of the electronic device 100. The electronic device 100 can display a desktop, or it can display a user interface other than a desktop; this embodiment does not limit this. The user interface 120 may include an electronic pet (e.g., pet 121), which can be used to receive input for waking up the voice assistant (e.g., petting the electronic pet); this embodiment does not limit the state of the electronic pet.

[0298] In some embodiments, the electronic device 100 can detect input that activates the voice assistant on the electronic pet (e.g., petting the electronic pet). In response to this operation, the electronic device 100 can activate the voice assistant and display a fourth interface, for example, user interface 360 ​​as shown in FIG17D. The fourth interface can be referred to FIG17B above, and will not be described again here.

[0299] As shown in Figures 17E-17F, in some embodiments, the desktop may include an electronic pet. Upon detecting input to wake up the voice assistant, the electronic device 100 can wake up the voice assistant and display a fourth interface. This fourth interface includes a voice assistant application interface and the electronic pet, which is displayed floating within the voice assistant application interface. When the electronic pet is displayed floating within the voice assistant application interface, it is in a seventh state, which differs from the second state. Optionally, the electronic pet can change from the second state to the seventh state according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed, movement trajectory. This embodiment does not limit the form of the animation effect. It should be noted that the input to wake up the voice assistant can be voice input or input applied to the electronic pet (e.g., petting the electronic pet). This embodiment does not limit the method of waking up the voice assistant.

[0300] For example, as shown in FIG17E, the electronic device 100 can display a user interface 120, which can be the desktop of the electronic device 100. The electronic device 100 can display a desktop, or it can display a user interface other than the desktop; this embodiment does not limit this. The user interface 120 may include an electronic pet (e.g., an active pet 121 with its eyes open and paws raised); this embodiment does not limit the state of the electronic pet. Optionally, the electronic pet can be used to receive input to wake up a voice assistant (e.g., petting the electronic pet).

[0301] In some embodiments, the electronic device 100 may detect input that wakes up the voice assistant (voice input or input acting on the electronic pet (e.g., petting the electronic pet)). In response to this operation, the electronic device 100 may wake up the voice assistant and display a fourth interface, such as the user interface 370 shown in FIG17F.

[0302] For example, as shown in FIG17F, the electronic device 100 may display a user interface 370, which may include a voice assistant application user interface and an electronic pet (such as pet 371, whose eyes are open and whose hands are raised, and whose size is smaller than that of pet 121 in user interface 120) located on the voice assistant application user interface. The embodiments of this application do not limit the state of the electronic pet.

[0303] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0304] As shown in Figures 18A-18B, in some embodiments, the unified desktop may include a desktop and a control center. Operations detected by the electronic device 100 on the unified desktop may include accessing the control center. In response to the access to the control center, the electronic device 100 may display the control center. Both the desktop and the control center include an electronic pet, but the electronic pet's state in the control center changes compared to its state on the desktop. Optionally, when the electronic device 100 switches from displaying the desktop to displaying the control center, the electronic pet's state may change according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed, movement trajectory. This application embodiment does not limit the form of the animation effect. It should be noted that the operation to access the control center can be a swipe down from the top of the screen or a specific gesture operation; this application embodiment does not limit this. After the electronic pet changes from being displayed on the desktop to being displayed in the control center, the electronic pet's state may change in response to operations on controls in the control center. For example, in response to operations on controls in the control center, the electronic pet may move to the operated control, and during the movement of the electronic pet, at least one of its appearance, posture, and expression may change. For example, in response to a click on the Bluetooth control, the electronic pet can jump onto the Bluetooth control. In addition to controlling the electronic pet's position and changing its posture, the electronic device 100 can also control the electronic pet's size to change, such as becoming larger or smaller; the electronic device 100 can also control the electronic pet's facial expressions to change, such as smiling or crying.

[0305] For example, as shown in FIG18A, the electronic device 100 can display a user interface 120, which can be the desktop of the electronic device 100. The electronic device 100 can display the desktop, or it can display a user interface other than the desktop; this embodiment does not limit this. The user interface 120 may include an electronic pet (e.g., a pet 121 with its eyes open and its paws raised); this embodiment does not limit the state of the electronic pet.

[0306] In some embodiments, the electronic device 100 may receive an operation to access the control center (e.g., a user swiping down from the top of the screen), and in response to such operation, the electronic device 100 may display the user interface 410 as shown in FIG18B.

[0307] For example, as shown in FIG18B, the electronic device 100 may display a user interface 410, which may include an electronic pet (e.g., a pet 411 with its eyes open, one paw raised, and the other paw lowered). This embodiment of the application does not limit the state of the electronic pet. Furthermore, the user interface 410 may also include one or more controls (e.g., WiFi controls, Bluetooth controls, etc.).

[0308] In some embodiments, the state of the electronic pet changes in response to an operation on a control in the control center. For example, in response to an operation on a control in the control center, the electronic pet can move onto the operated control, and at least one of the electronic pet's appearance, posture, and expression can change during the movement. For instance, in response to a click on a Bluetooth control, the electronic pet can jump onto the Bluetooth control. In addition to controlling the electronic pet's position and posture, the electronic device 100 can also control changes in the electronic pet's size, such as increasing or decreasing its size; the electronic device 100 can also control changes in the electronic pet's expression, such as smiling or crying.

[0309] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0310] As shown in Figures 19A-19D, in some embodiments, the unified desktop may include a desktop and a notification center. Operations detected by the electronic device 100 on the unified desktop may include accessing the notification center. In response to the access to the notification center, the electronic device 100 may display the notification center. Both the desktop and the notification center include an electronic pet, but the state of the electronic pet in the notification center changes compared to its state on the desktop. Optionally, when the electronic device 100 switches from displaying the desktop to displaying the control center, the state of the electronic pet may change according to an animation effect. The parameters of this animation effect include one or more of the following: movement speed, movement trajectory. This application embodiment does not limit the form of the animation effect. Optionally, the electronic pet may be located around the notification in the notification center. It should be noted that the operation of accessing the notification center can be a swipe-down operation from the top of the screen, and this application embodiment does not limit this. It should be noted that the electronic pet being located around the notification in the notification center can be understood as the distance between the electronic pet and the notification being less than a preset distance (e.g., 0.5 cm). For example, the electronic pet is displayed on the notification. After the electronic pet changes its display from the desktop to the notification center, its state can change in response to an operation on a notification in the notification center. For example, in response to a left swipe operation on a notification in the notification center, the electronic pet can move to the left following the swiped notification, and at least one of its appearance, posture, or expression can change during this movement. For instance, the electronic device 100 can control the electronic pet's size to change, such as increasing or decreasing; the electronic device 100 can also control the electronic pet's posture to change, such as rotating or jumping; and the electronic device 100 can also control the electronic pet's expression to change, such as smiling or crying. For example, in response to a deletion operation on a notification in the notification center, the electronic pet can leave the deleted notification, and after leaving the deleted notification, at least one of its appearance, posture, or expression can change. For example, the electronic device 100 can control the electronic pet's size to change, such as becoming larger or smaller; the electronic device 100 can also control the electronic pet's posture to change, such as rotating or jumping; the electronic device 100 can also control the electronic pet's facial expressions to change, such as smiling or crying.

[0311] For example, as shown in FIG19A, the electronic device 100 can display a user interface 120, which can be the desktop of the electronic device 100. The electronic device 100 can display a desktop, or it can display a user interface other than the desktop; this embodiment does not limit this. The user interface 120 may include an electronic pet (e.g., a pet 121 with its eyes open and its paws raised); this embodiment does not limit the state of the electronic pet.

[0312] In some embodiments, the electronic device 100 may receive an operation to access the notification center (e.g., a user swiping down from the top of the screen), and in response to this operation, the electronic device 100 may display the user interface 420 as shown in FIG19B.

[0313] For example, as shown in FIG19B, the electronic device 100 may display a user interface 420, which may include one or more notifications (e.g., notification 421 pushed by a bank app, notification pushed by a mobile payment app). Furthermore, the user interface 420 may also include an electronic pet located around the notification (e.g., pet 422, with its eyes open, one paw raised and the other lowered, and the pet 422 being smaller than the pet 121 in the user interface 120). This embodiment does not limit the state of the electronic pet.

[0314] In some embodiments, the electronic device 100 may receive an operation on a notification in the notification center (e.g., a swipe-left operation), and in response to the operation, the electronic device 100 may display a user interface 430 as shown in FIG19C.

[0315] For example, as shown in FIG19C, the electronic device 100 may display a user interface 430, which may include one or more notifications (e.g., notification 431 pushed by a bank app, notification pushed by a mobile payment app). The user interface 430 may also include an electronic pet (e.g., pet 432, with its eyes open, one paw raised, and the other paw lowered) that moves around and follows the notification. This embodiment does not limit the state of the electronic pet. Furthermore, the user interface 430 may include a delete control (e.g., control 433), which can be used to delete the selected notification. After deleting the selected notification, the electronic device 100 no longer displays the deleted notification in the notification center.

[0316] In some embodiments, the electronic device 100 may receive a deletion operation on a notification in the notification center (e.g., clicking the control 433), and in response to the operation, the electronic device 100 may display the user interface 440 as shown in FIG19D.

[0317] For example, as shown in FIG19D, the electronic device 100 may display a user interface 440, which may include one or more notifications (e.g., a notification 441 pushed by a mobile payment app). Furthermore, the user interface 440 may also include an electronic pet that has left the deleted notification (e.g., a pet 442 located on notification 441, with its eyes open, one paw raised, and the other paw lowered). Besides being located around other undeleted notifications, the electronic pet leaving the deleted notification may also be located in a non-notification location within the notification center; this embodiment of the application does not impose limitations on the electronic pet leaving the deleted notification.

[0318] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0319] In some embodiments, electronic device 100 may establish a communication connection with electronic device 200, and electronic device 100 may display an electronic pet. When electronic device 100 detects that a user's interaction has shifted from electronic device 100 to electronic device 200, electronic device 100 may send relevant parameters of the electronic pet to electronic device 200. These parameters can be used to display the electronic pet on electronic device 200 and may include one or more of the following: the electronic pet's identifier, the electronic pet's installation package, the electronic pet's location, the electronic pet's appearance, the electronic pet's expression, and the electronic pet's posture. The interaction is an operation performed on the electronic pet (e.g., sliding the electronic pet towards electronic device 200 on the screen of electronic device 100), or an operation performed on electronic device 200 (e.g., touching the screen of electronic device 200), or an operation where electronic device 100 touches the NFC tag of electronic device 200. In this context, the type of electronic device 200 can be the same as that of electronic device 100, for example, both electronic devices 200 and 100 can be mobile phones; alternatively, the types of electronic devices 200 and 100 can be different, for example, electronic device 100 can be a mobile phone while electronic device 200 can be a tablet computer. It is understood that the prerequisites for enabling the electronic pet to move across devices include, in addition to electronic devices 100 and 200 establishing a communication connection, one or more of the following: electronic devices 100 and 200 are logged into the same user account; both electronic devices 100 and 200 support cross-device movement of the electronic pet; and the distance between electronic devices 100 and 200 is less than a preset distance (e.g., 10 meters). It should be noted that electronic device 100 controlling the electronic pet to move from electronic device 100 to electronic device 200 for display can specifically include electronic device 100 controlling the electronic pet to be displayed on electronic device 200 instead of on electronic device 100. It should be noted that since the prerequisite for enabling electronic pets to move across devices can include electronic devices 100 and 200 being logged into the same user account, and as mentioned above, electronic pets associated with the same user account are identical—that is, electronic pets associated with the same user account have the same name, initial appearance, and way of addressing the user—the electronic pet displayed on electronic device 200 can be the same as the electronic pet displayed on electronic device 100. It should also be noted that electronic pets can have different interactive design effects on multiple electronic devices (e.g., electronic devices 100 and 200) that move across devices. For example, in response to clicking an application icon, electronic device 100 or electronic device 200 can launch the application corresponding to the application icon.During the launch of the application corresponding to the application icon, electronic device 100 or electronic device 200 can display the application's launch animation. If the electronic pet is on electronic device 100, when displaying the application's launch animation, electronic device 100 can control the electronic pet to change its display location from around the application icon to within the launch animation. After launching the application corresponding to the application icon, electronic device 100 can control the electronic pet's display location to change to the status bar. If the electronic pet is on electronic device 200, when displaying the application's launch animation, electronic device 200 can control the electronic pet to change its display location directly from around the application icon to within the status bar.

[0320] As shown in Figures 20A-20B, in some embodiments, the user's interaction operation can be an operation acting on the electronic device 200. That is, the electronic device 100 can detect that the user has switched the electronic device they are using from the electronic device 100 to the electronic device 200. Specifically, before controlling the electronic pet to move from the electronic device 100 to the electronic device 200 for display, the electronic device 100 can detect that the electronic device 100 is in a screen-off state and the electronic device 200 is in a screen-on state, or, if both the electronic device 100 and the electronic device 200 are in a screen-on state, the electronic device 100 can detect that the time the electronic device 200 receives the operation is later than the time the electronic device 200 receives the operation. It should be noted that after the electronic device 100 and the electronic device 200 establish a communication connection, the electronic device 100 can send the status of its display screen (whether it is in a screen-off state) and / or the time the electronic device 100 receives the user operation to the electronic device 200 based on the communication connection; the electronic device 100 can also receive the status of its display screen (whether it is in a screen-off state) and / or the time the electronic device 200 receives the user operation sent by the electronic device 200 based on the communication connection. Furthermore, the electronic device 100 can decide whether to control the electronic pet to move from the electronic device 100 to the electronic device 200 for display based on the state of the electronic device 100's display screen (whether it is in a screen-off state) and / or the time when the electronic device 100 receives user operations, as well as the state of the electronic device 200's display screen (whether it is in a screen-off state) and / or the time when the electronic device 200 receives user operations sent by the electronic device 200.

[0321] For example, as shown in FIG20A, electronic device 100 is a mobile phone, and electronic device 200 is a tablet computer. Electronic device 100 can display a user interface 120, which can be the desktop of electronic device 100. Electronic device 100 can display a desktop, or it can display a user interface other than the desktop; this embodiment does not limit this. The user interface 120 can include an electronic pet (e.g., an active pet 121 with its eyes open and paws raised); this embodiment does not limit the state of the electronic pet. Electronic device 200 can display a user interface 510, which can be the desktop of electronic device 200, in which case the user interface 510 does not include an electronic pet. Electronic device 200 can display a desktop, or it can display a user interface other than the desktop; this embodiment does not limit this.

[0322] In some embodiments, electronic device 100 can detect that the user has switched the electronic device it is using from electronic device 100 to electronic device 200. For example, electronic device 100 can detect that electronic device 100 is in a screen-off state and electronic device 200 is in a screen-on state. Alternatively, when both electronic device 100 and electronic device 200 are in a screen-on state, electronic device 100 can detect that the time when electronic device 200 receives the operation is later than the time when electronic device 100 receives the operation. In response to the user's operation of switching the electronic device it is using from electronic device 100 to electronic device 200, electronic device 200 can display user interface 520 as shown in FIG20B, and electronic device 100 can display user interface 350 as shown in FIG20B. At this time, electronic device 200 can display that there is an electronic pet, while electronic device 100 can stop displaying the electronic pet.

[0323] For example, as shown in FIG20B, electronic device 200 can display user interface 520, which can be the desktop of electronic device 200. Electronic device 200 can display the desktop, or it can display a user interface other than the desktop; this embodiment does not limit this. The user interface 520 can include an electronic pet (e.g., an active pet 521 with its eyes open and paws raised); this embodiment does not limit the state of the electronic pet. It should be noted that after the electronic pet is moved from electronic device 100 to electronic device 200, the state of the electronic pet on electronic device 200 can be the same as or different from the state of the electronic pet on electronic device 100; this embodiment does not limit this. Electronic device 100 can display user interface 350, which can be the desktop of electronic device 100, in which case user interface 350 no longer includes the electronic pet. Electronic device 100 can display the desktop, or it can display a user interface other than the desktop; this embodiment does not limit this.

[0324] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0325] As shown in Figures 21A-21B, in some embodiments, the user's interaction can be the operation of electronic device 100 touching the NFC tag of electronic device 200, enabling cross-device connection between electronic device 100 and electronic device 200 for electronic pets. When electronic device 100 supports NFC and has an NFC reader function, and electronic device 200 has an NFC tag, in response to the user's operation of touching the NFC tag of electronic device 200 with electronic device 100, electronic device 100 can establish a communication connection with electronic device 200, and based on this communication connection, launch the system-level electronic pet APP on electronic device 200. The system-level electronic pet APP on electronic device 100 can synchronize data with the system-level electronic pet APP on electronic device 200, so that the electronic pet on electronic device 200 is identical to the electronic pet on electronic device 100. The NFC reader can be used to read NFC tag information, and the NFC tag can be used to exchange data with NFC-enabled electronic devices. It is understood that the prerequisites for enabling cross-device connection of electronic pets may include electronic device 100 supporting NFC and having an NFC reader function, and electronic device 200 having an NFC tag. As mentioned above, since the basic data of the electronic pet is bound to the user account, the prerequisites for enabling cross-device connectivity of the electronic pet may include, but are not limited to, one or more of the following: electronic device 100 and electronic device 200 are logged into the same user account, and the distance between electronic device 100 and electronic device 200 is less than a preset distance (e.g., 10 meters). It should be noted that the electronic pet can have different interactive design effects on multiple connected electronic devices (e.g., electronic device 100 and electronic device 200). For example, in response to clicking an application icon, electronic device 100 or electronic device 200 can launch the application corresponding to the application icon. During the launch of the application corresponding to the application icon, electronic device 100 or electronic device 200 can display the application's launch animation. If the electronic pet is on electronic device 100, when displaying the application's launch animation, electronic device 100 can control the electronic pet to change its display position from around the application icon to within the launch animation. After launching the application corresponding to the application icon, electronic device 100 can control the electronic pet's display position to change to the status bar. If the electronic pet is on the electronic device 200, when the application startup animation is displayed, the electronic device 200 can control the electronic pet to change from being displayed around the application icon to being displayed in the status bar.

[0326] For example, as shown in FIG21A, both electronic devices 100 and 200 are mobile phones. Electronic device 100 can display a user interface 120, which can be the desktop of electronic device 100. Electronic device 100 can display the desktop, or it can display a user interface other than the desktop; this embodiment does not limit this. The user interface 120 can include an electronic pet (e.g., an active pet 121 with its eyes open and paws raised); this embodiment does not limit the state of the electronic pet. Electronic device 200 can display a user interface 350, which can be the desktop of electronic device 200, in which case the user interface 350 does not include an electronic pet. Electronic device 200 can display the desktop, or it can display a user interface other than the desktop; this embodiment does not limit this.

[0327] In some embodiments, electronic device 100 can detect a user touching the NFC tag of electronic device 200 with electronic device 100. In response to this operation, electronic device 100 can establish a communication connection with electronic device 200 and launch a system-level electronic pet APP on electronic device 200 based on the communication connection. The system-level electronic pet APP on electronic device 100 can synchronize data with the system-level electronic pet APP on electronic device 200 so that the electronic pet on electronic device 200 is the same as the electronic pet on electronic device 100. In response to the user touching the NFC tag of electronic device 200 with electronic device 100, electronic device 200 can display user interface 120 as shown in FIG. 21B, and electronic device 100 can display user interface 350 as shown in FIG. 21B. At this time, electronic device 200 can display that there is an electronic pet, while electronic device 100 can stop displaying the electronic pet.

[0328] For example, as shown in FIG21B, electronic device 200 can display user interface 120, which can be the desktop of electronic device 200. Electronic device 200 can display the desktop, or it can display a user interface other than the desktop; this embodiment does not limit this. The user interface 120 can include an electronic pet (e.g., an active pet 121 with its eyes open and paws raised); this embodiment does not limit the state of the electronic pet. It should be noted that in some embodiments, after the electronic pet is moved from electronic device 100 to electronic device 200, the state of the electronic pet on electronic device 200 can be the same as or different from the state of the electronic pet on electronic device 100; this embodiment does not limit this. Electronic device 100 can display user interface 350, which can be the desktop of electronic device 100, in which case user interface 350 no longer includes the electronic pet. Electronic device 100 can display the desktop, or it can display a user interface other than the desktop; this embodiment does not limit this.

[0329] It should be noted that the embodiments of this application do not limit the electronic pets in different states in different user interfaces. Specifically, the embodiments of this application do not limit the electronic pet's position, appearance, expression, posture, etc., in different user interfaces. The embodiments of this application also do not limit the animation effects of the electronic pet when switching between different user interfaces; that is, the embodiments of this application do not limit the electronic pet's movement trajectory, movement speed, etc., when switching between different user interfaces.

[0330] It should be noted that the above embodiments only illustrate the display of one electronic pet on the electronic device 100. In other embodiments, the electronic device 100 may display multiple electronic pets, and the number of electronic pets displayed on the electronic device 100 can be set by the user; this application embodiment does not impose any limitations on this. If the electronic device 100 displays multiple electronic pets, the state change patterns of these multiple electronic pets may be the same or different; this application embodiment does not impose any limitations on this.

[0331] In some embodiments, the electronic device 100 can acquire the user's facial expressions through a front-facing camera. Furthermore, the electronic device 100 can control the electronic pet to interact with the user based on the user's facial expressions. For example, if the electronic device 100 acquires a happy smile from the user through the front-facing camera, the electronic device 100 can control the electronic pet to jump on the tabletop to achieve the effect of sensing and responding to the user's emotions.

[0332] In this embodiment, the electronic pet can have different interactive design effects on different types of electronic devices. For example, electronic device 100 is a mobile phone, and electronic device 200 is a tablet computer. In response to clicking an application icon, either electronic device 100 or electronic device 200 can launch the application corresponding to the application icon. During the launch of the application corresponding to the application icon, either electronic device 100 or electronic device 200 can display the application's launch animation. During the launch of the application corresponding to the application icon, the interactive design effect of the electronic pet on electronic device 100 is as follows: when displaying the application's launch animation, electronic device 100 can control the electronic pet to change from being displayed around the application icon to being displayed within the launch animation. After launching the application corresponding to the application icon, electronic device 100 can control the electronic pet's display position to change to the status bar. During the launch of the application corresponding to the application icon, the interactive design effect of the electronic pet on electronic device 200 is as follows: when displaying the application's launch animation, electronic device 200 can control the electronic pet to change directly from being displayed around the application icon to being displayed in the status bar.

[0333] In some embodiments, in addition to touch input, users can also interact with electronic devices through voice input and other methods. In response to the user's voice input, the electronic device can control a virtual pet to interact with the user.

[0334] Based on the embodiments of this application, the electronic pet can sense the user's operations on the unified desktop (e.g., the desktop) and its UI elements (e.g., application icons, application cards, folder icons), and provide corresponding feedback based on the sensed user operations on the unified desktop and its UI elements. For example, the electronic pet can sense the user's long-press operation on an application icon, and based on this long-press operation, switch from a sleeping state to a awake state.

[0335] Based on the embodiments of this application, electronic pets can also have system-level capabilities (such as changing system settings, moving across devices, and integrating with whole-house smart systems, etc.).

[0336] This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the steps performed by the electronic device in the above method embodiments, or the steps performed by the human-computer interaction module and the computing module.

[0337] This application also provides a computer program product that, when run on a terminal device, enables the terminal device to perform the steps executed by the electronic device in the above method embodiments.

[0338] This application also provides a chip system, which includes a processor coupled to a memory. The processor executes a computer program stored in the memory to implement the steps performed by the electronic device in any of the method embodiments of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0339] The term "user interface (UI)," or simply "interface," used in the specification and accompanying drawings of this application, refers to the medium through which an application or operating system interacts and exchanges information with the user. It facilitates the conversion between the internal form of information and a form acceptable to the user. The user interface of an application is written in source code using specific computer languages ​​such as Java or Extensible Markup Language (XML). This source code is parsed and rendered on the terminal device, ultimately presenting user-recognizable content, such as images, text, and buttons. Controls, also known as widgets, are the basic elements of the user interface. Typical controls include toolbars, menu bars, text boxes, buttons, scroll bars, images, and text. The attributes and content of controls in the interface are defined using tags or nodes, such as XML tags. <textview> 、 <imgview> 、 <videoview>Nodes define the controls contained in the interface. A node corresponds to a control or property in the interface, and after parsing and rendering, the node is presented as the content visible to the user. In addition, many applications, such as hybrid applications, often contain web pages within their interfaces. A web page, also known as a page, can be understood as a special control embedded in the application interface. Web pages are source code written in a specific computer language, such as Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), JavaScript (JS), etc. Web page source code can be loaded and displayed as user-readable content by a browser or a web page display component with browser-like functionality. The specific content contained in a web page is also defined through tags or nodes in the web page source code; for example, HTML uses tags or nodes to define the content. 、 、 <video> 、 <canvas>To define the elements and attributes of a webpage.

[0340] The most common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be an icon, window, control, or other interface element displayed on the screen of an electronic device. Controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

[0341] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0342] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0343] As used in the above embodiments, depending on the context, the term "when..." can be interpreted as meaning "if..." or "after..." or "in response to determining..." or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if (the stated condition or event) is detected" can be interpreted as meaning "if determining..." or "in response to determining..." or "when (the stated condition or event) is detected" or "in response to detecting (the stated condition or event)".

[0344] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.

[0345] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.< / canvas> < / video> < / videoview> < / imgview> < / textview>

Claims

1. A pet interaction method, applied to a first electronic device, characterized in that, The method includes: The first electronic device displays a first interface, the first interface includes a first object, the first object is in a first state on the first interface, and the first interface includes a lock screen interface; An unlock operation on the first interface is detected, and a second interface is displayed. The second interface includes the first object, and the first object is in a second state on the second interface. The second state is different from the first state, and the second interface is the desktop.

2. The method according to claim 1, characterized in that, The first state of the first object includes one or more of the following: the position of the first object, the shape of the first object, the expression of the first object, and the posture of the first object.

3. The method according to claim 1 or 2, characterized in that, The method further includes: When the first electronic device switches from displaying the first interface to displaying the second interface, the first object changes from the first state to the second state according to the first animation effect. The parameters of the first animation effect include one or more of the following: first moving speed and first moving trajectory.

4. The method according to any one of claims 1-3, characterized in that, The lock screen interface is the always-on lock screen interface.

5. The method according to any one of claims 1-3, characterized in that, The lock screen interface is a lock screen interface that is displayed when the screen is on. Before the first electronic device displays the first interface, the method further includes: The always-on lock screen interface is displayed, which includes the first object. The first object is in a third state, which is different from the first state. An operation to turn on the screen of the always-on lock screen interface was detected.

6. The method according to any one of claims 1-5, characterized in that, The desktop includes application icons, the first object is located around the application icons, and the method further includes: Upon detecting an operation on the application icon, the first object on the desktop changes from the second state to the fourth state, which is different from the second state. The operation on the application icon includes long-pressing the application icon, dragging the application icon, uninstalling the application icon, and clicking the application icon.

7. The method according to claim 6, characterized in that, When the operation on the application icon is a long press on the application icon, the first expression of the first object in the fourth state changes relative to the second expression of the first object in the second state; When the operation on the application icon is to drag the application icon, the first position of the first object in the fourth state changes relative to the second position of the first object in the second state; When the operation on the application icon is to uninstall the application icon, the third position of the first object in the fourth state changes relative to the fourth position of the first object in the second state.

8. The method according to any one of claims 1-7, characterized in that, The desktop includes application icons, and the method further includes: In response to a click on the application icon, a third interface is displayed. The third interface includes the user interface and status bar of the application corresponding to the application icon. The third interface also includes the first object, which is displayed in the status bar.

9. The method according to claim 8, characterized in that, When the first object is displayed in the status bar, the first object is in a fifth state, which is different from the second state.

10. The method according to claim 9, characterized in that, The method further includes: When the first electronic device switches from displaying the second interface to displaying the third interface, the first object changes from the second state to the fifth state according to the second animation effect. The parameters of the second animation effect include one or more of the following: second moving speed and second moving trajectory.

11. The method according to any one of claims 1-10, characterized in that, The desktop wallpaper contains pet interactive elements, and the second state includes a fifth position of the first object, the fifth position being the position surrounding the pet interactive element; the method further includes: The first object changes from the second state to the sixth state on the desktop. The sixth state includes the sixth position of the first object, which is a position around a first user interface (UI) element. The first UI element includes one or more of the following: application icon, application card, and folder icon.

12. The method according to any one of claims 1-11, characterized in that, The method further includes: Upon detecting input to wake up the voice assistant, a fourth interface is displayed. The fourth interface includes the voice assistant application interface and the first object, with the first object floating in the voice assistant application interface.

13. The method according to claim 12, characterized in that, When the first object is displayed floating in the voice assistant application interface, the first object is in a seventh state, which is different from the second state.

14. The method according to any one of claims 1-13, characterized in that, The first electronic device and the second electronic device establish a communication connection, and the method further includes: When the first electronic device detects that the user's interaction has been transferred from the first electronic device to the second electronic device, it sends the relevant parameters of the first object to the second electronic device. The relevant parameters of the first object are used to display the first object on the second electronic device.

15. The method according to claim 14, characterized in that, The relevant parameters of the first object include one or more of the following: the identifier of the first object, the program installation package of the first object, the location of the first object, the appearance of the first object, the expression of the first object, and the posture of the first object.

16. The method according to claim 14 or 15, characterized in that, The interactive operation is an operation performed on the first object, or an operation performed on the second electronic device, or an operation in which the first electronic device touches the second electronic device.

17. An electronic device, characterized in that, The electronic device includes a processor and a memory; wherein the memory is coupled to the processor and is used to store a computer program that, when executed by the processor, causes the electronic device to perform the method as described in any one of claims 1-16.

18. A computer storage medium, characterized in that, The computer storage medium stores a computer program that, when executed by a processor, causes the electronic device to perform the method as described in any one of claims 1-16.

19. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it causes the electronic device to perform the method as described in any one of claims 1-16.

Images