WO2023142935A1 - 应用组件管理方法及相关设备 - Google Patents

应用组件管理方法及相关设备 Download PDF

Info

Publication number
WO2023142935A1
WO2023142935A1 PCT/CN2023/070583 CN2023070583W WO2023142935A1 WO 2023142935 A1 WO2023142935 A1 WO 2023142935A1 CN 2023070583 W CN2023070583 W CN 2023070583W WO 2023142935 A1 WO2023142935 A1 WO 2023142935A1
Authority
WO
WIPO (PCT)
Prior art keywords
electronic device
application component
application
information
interface
Prior art date
Application number
PCT/CN2023/070583
Other languages
English (en)
French (fr)
Inventor
王志强
陈晓晓
顾兵
丁雅玲
周送乐
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023142935A1 publication Critical patent/WO2023142935A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues

Definitions

  • the present application relates to the field of terminal technology, and in particular to a method for managing application components and related equipment.
  • Embodiments of the present application provide a method for managing application components and related devices, which can solve the problem that cross-device application components cannot be viewed on the local device, and improve user experience.
  • an embodiment of the present application provides a method for displaying application components, which is applied to a first electronic device, and the method includes: the first electronic device receives application component information from the second electronic device, and the application component information includes the first application component information, the first application component is an application component of the second electronic device; the first electronic device displays the first application component based on the information of the first application component.
  • the information of the first application component can be used to display the first application component, and can include the component identification of the first application component (such as the package name and module name of the application component), the description information of the first application component (such as the preview of the application component) Figures, titles, dimensions, etc.) etc.
  • the embodiment of the present application provides a method for displaying application components
  • the electronic device that is, the local device
  • the application components provided by the remote device can solve the problem that the cross-device application components cannot be viewed on the local device and improve user experience.
  • the information of the first application component includes the installation package of the first application component, and the first electronic device displays the first application component based on the information of the first application component.
  • An installation package of an application component displays the first application component; wherein, the first application component displays first content, the first content is generated by the first electronic device based on first data, and the first data is the Obtained from the installation package of an application component.
  • the electronic device can statically display the first application component, that is, the electronic device can display static information (that is, the first content) of the first application component.
  • the information of the first application component includes the installation package of the first application component and the second data
  • the first electronic device displays the first application component based on the information of the first application component, specifically including: the first The electronic device installs and displays the first application component based on the installation package of the first application component and the second data; wherein, the first application component displays second content, and the second content is generated by the first electronic device based on the second data, The second data is generated by the second electronic device when running the first application component.
  • the electronic device can dynamically display the first application component, that is, the electronic device can display dynamic information (ie, the second content) of the first application component.
  • the method further includes: the first electronic device detects that the user adds the first application component to the desktop , the first electronic device displays the first application component on the desktop.
  • the electronic device can add the first application component to the desktop display, and the user can view the first application component on the desktop.
  • the method further includes: the first electronic device detects that the user opens the application component management interface, and responds to In this operation, the first electronic device displays the application component management interface, wherein the application component management interface includes identification options, and the identification options include the identification options of the second electronic device; Operation: the first electronic device displays the first application component based on the information of the first application component, specifically comprising: in response to the operation, the first electronic device displays the first application component on the application component management interface based on the information of the first application component.
  • the application component management interface displays the application components of the second electronic device, and the application components of the second electronic device include the first application component.
  • the electronic device can display the application components on the second electronic device for the user to view.
  • the method further includes: the first electronic device detects that the user opens the application component management interface, and responds to In this operation, the first electronic device displays the application component management interface; the first electronic device displays the first application component based on the information of the first application component, which specifically includes: the first electronic device displays the first application component on the application component management interface based on the information of the first application component A first application component; wherein, the application component management interface further displays a second application component, and the second application component is an application component of the first electronic device.
  • the electronic device can display both the application components of the local machine and the application components of other electronic devices on the same interface.
  • the method further includes: the first electronic device detects that the user searches for keywords on the search interface, In response to this operation, the first electronic device acquires application component information related to the keyword, and the application component information related to the keyword includes information about the first application component; the first electronic device displays the first application component information based on the first application component information.
  • An application component specifically includes: the first electronic device displays the first application component on the search interface based on the information of the first application component.
  • the electronic device After the electronic device detects that the user searches for a keyword on the search interface, it can display application components related to the keyword.
  • the method before the first electronic device receives the application component information from the second electronic device, the method further includes: the first electronic device detects that a preset condition is triggered, and the preset condition includes any of the following: Items: the operation of the user opening the application component management interface, the user's operation of searching for keywords on the search interface, booting, restarting, locking and unlocking, and system update; in response to a preset condition being triggered, the first electronic device sends a message to the second electronic device Sending a first request, where the first request is used to instruct the second electronic device to send application component information to the first electronic device.
  • the electronic device can acquire application component information from other electronic devices after the preset condition is triggered, so that the user can view the application components on other electronic devices.
  • the first electronic device displays the identifier of the second electronic device on the first application component.
  • the method before the first electronic device receives the application component information from the second electronic device, the method further includes: the first electronic device establishes a communication connection with the second electronic device, and confirms that the second electronic device as a trusted device.
  • the first electronic device can obtain the application component information of the second electronic device based on the communication connection, and confirm that the second electronic device is a trusted device, which can ensure security.
  • an embodiment of the present application provides a method for displaying application components, which is applied to a second electronic device, and the method includes: the second electronic device receives a first request from the first electronic device, and the first request is used to indicate that the second electronic device The second electronic device sends application component information to the first electronic device, wherein the application component information includes information about the first application component, and the first application component is an application component of the second electronic device; the second electronic device sends the application component to the first electronic device Component information.
  • the information of the first application component includes an installation package of the first application component.
  • the information of the first application component further includes second data
  • the method further includes: the second electronic device runs the first application component, and generate the second data.
  • the method before the second electronic device receives the first request from the first electronic device, the method further includes: the second electronic device establishes a communication connection with the first electronic device, and confirms that the first electronic device as a trusted device.
  • the present application provides a communication system, which includes: a first electronic device and a second electronic device; the second electronic device is used to send application component information to the first electronic device; the first electronic device is used to Receive application component information, the application component information includes information of a first application component, the first application component is an application component of the second electronic device; the first electronic device is further configured to display the first application component based on the information of the first application component.
  • an embodiment of the present application provides an electronic device, which includes one or more processors and one or more memories; wherein, the one or more memories are coupled to the one or more processors, and one or more A plurality of memories are used to store computer program codes, and the computer program codes include computer instructions.
  • the electronic device executes any of the possible implementations of the first aspect or the second aspect above. described method.
  • an embodiment of the present application provides a computer storage medium, the computer storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are run on the electronic device, the electronic device executes the above-mentioned first aspect or The method described in any possible implementation of the second aspect.
  • an embodiment of the present application provides a computer program product, which, when running on a computer, causes the computer to execute the method described in any possible implementation manner of the first aspect or the second aspect above.
  • FIG. 1 is a schematic diagram of a local device displaying application components on a desktop provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • FIG. 3A is a schematic diagram of a software architecture of a local device provided in an embodiment of the present application.
  • FIG. 3B is a schematic diagram of the software architecture of another local device provided by the embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a method for managing application components provided by an embodiment of the present application
  • Fig. 5 is a schematic diagram of a possible cooperation mode between internal modules in the process of establishing a trusted connection between the local device and the remote device provided by the embodiment of the present application;
  • FIG. 6 is a schematic diagram of a desktop of a local device provided in an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a remote device displaying application components on an application component management interface according to an embodiment of the present application
  • Fig. 8 is a schematic diagram of a possible cooperation mode among internal modules in the process of obtaining and saving application component information of a remote device by a local device according to an embodiment of the present application;
  • FIG. 9A is a schematic diagram of displaying application components of the local device on the application component management interface provided by an embodiment of the present application.
  • FIG. 9B is a schematic diagram of a local device statically displaying remote device application components on the application component management interface provided by an embodiment of the present application;
  • FIG. 9C is another schematic diagram of the local device statically displaying the application components of the remote device on the application component management interface provided by the embodiment of the present application;
  • Fig. 10 is a schematic diagram of a possible cooperation mode between internal modules when the local device statically displays the application components of the remote device on the application component management interface provided by the embodiment of the present application;
  • FIG. 11A is a schematic diagram of a remote device displaying application components on a desktop according to an embodiment of the present application
  • FIG. 11B is a schematic diagram of a local device dynamically displaying remote device application components on the application component management interface provided by an embodiment of the present application;
  • FIG. 11C is another schematic diagram of the local device dynamically displaying the application components of the remote device on the application component management interface provided by the embodiment of the present application;
  • 12A-12B are schematic diagrams of a user interface for adding a remote device application component to the desktop of the local device for display according to an embodiment of the present application;
  • Fig. 13 is a schematic diagram of a possible cooperation mode between internal modules in the process of dynamically displaying the application components of the remote device on the application component management interface of the local device provided by the embodiment of the present application;
  • FIG. 14A is a schematic diagram of a search interface of a local device provided in an embodiment of the present application.
  • Fig. 14B is a schematic diagram of a local device automatically recommending and statically displaying remote device application components on the search interface provided by the embodiment of the present application;
  • Fig. 15 is a schematic diagram of a possible cooperation mode between internal modules when the local device statically displays the application components of the remote device on the search interface provided by the embodiment of the present application;
  • Fig. 16 is a schematic diagram of a local device automatically recommending and dynamically displaying application components of a remote device on a search interface provided by an embodiment of the present application;
  • Fig. 17 is a schematic diagram of a possible cooperation mode between internal modules in the process of dynamically displaying the application components of the remote device on the search interface provided by the embodiment of the present application;
  • FIG. 18 is a schematic structural diagram of a local device provided by an embodiment of the present application.
  • UI user interface
  • the term "user interface (UI)” in the following embodiments of this application is a medium interface for interaction and information exchange between an application program or an operating system and a user, and it realizes the difference between the internal form of information and the form acceptable to the user. conversion between.
  • the user interface is the source code written in a specific computer language such as java and extensible markup language (XML).
  • the source code of the interface is parsed and rendered on the electronic device, and finally presented as content that can be recognized by the user.
  • the commonly used form of user interface is the graphical user interface (graphic user interface, GUI), which refers to the user interface related to computer operation displayed in a graphical way. It may be text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, Widgets, and other visible interface elements displayed on the display screen of the electronic device.
  • Application component (Application Widget, App Widget), also called card or service card or service component (Service Widget) or application widget or application widget, is the business module A of the electronic device (business end, such as an application program ) is a small window or widget provided on the interface of module B (the host side, such as the desktop).
  • Application components are usually used to display the important information of the application on the desktop of the electronic device to realize a certain business feature of the application. Users can use the application component through shortcut gestures to achieve one-step direct access to services and reduce hierarchical jumps the goal of.
  • An application component is a form of interface presentation, usually independently customized by a third party (such as a developer of an application program), that is, independent from the customization of the application program corresponding to the application component.
  • application components can be used to embed in other applications as part of their interface display, for example, it can allow users (such as desktop applications) to embed application components into their own interfaces (such as embedded in the activity components of the Android operating system) to display.
  • the application component corresponding to the application is independent of the application, that is, the application component corresponding to the application is not the application interface of the application, but the application component corresponding to the application Data interaction with the application can be performed to update or add important information or operations of the application to application components, so as to achieve direct service and reduce the level of experience.
  • an application component based on the Android operating system can be called an ongoing card
  • an application component based on the Hongmeng operating system can be called a service card, such as form ability (FA).
  • FA form ability
  • FIG. 1 exemplarily shows an application component provided by an electronic device 100 and displayed in a user interface 110 (ie, a desktop).
  • an application component can display one or more types of information.
  • the application component 111 displays There are three kinds of information: location information (for example, Qixia District, Nanjing), temperature information (for example, 22 degrees), and movement step information (for example, 6888 steps).
  • location information for example, Qixia District, Nanjing
  • temperature information for example, 22 degrees
  • movement step information for example, 6888 steps
  • the application component is just a term used in the embodiment of the present application, and its representative meaning has been recorded in the embodiment of the present application, and its name does not constitute any limitation to the embodiment of the present application.
  • application components can only be used on the local device. If users want to use these application components on other remote devices, they need to manually install the applications that provide these application components on the remote device, and then use the desktop The provided widget selects the corresponding application component to add to the desktop for display. Finally, it may be necessary to manually set the configuration of the application component according to user needs (such as setting the display location of the weather application component, setting the display country of the calendar application component, etc. ), the operation is cumbersome, and the flexibility is poor. Users cannot view and use cross-device application components on the local device like viewing and using the application components of the local device, and lack the experience of viewing and using application components across devices. The application scenarios of components are limited and the user experience is poor.
  • the embodiment of the present application provides a method for managing application components.
  • An electronic device that is, the local device
  • the electronic device can establish a trusted connection with one or more remote devices, and through the trusted connection, the electronic device can obtain the one or more The application component information list provided by the remote device, and based on the application component information list, one or more application components provided by the remote device can be displayed and used, so as to solve the problem of being unable to view and use cross-device applications on the local device Component issues, improve user experience.
  • Solution 1 (the electronic device 100 statically displays the application component when it detects that the user is viewing the application component on the desktop):
  • the electronic device 100 (that is, the local device) can obtain the static information of the application components provided by the one or more remote devices through the trusted connection established with the one or more remote devices.
  • the electronic device 100 may statically display the application component provided by the remote device based on the above static information.
  • Solution 2 (the electronic device 100 dynamically displays the application component when it detects that the user is viewing the application component on the desktop):
  • the electronic device 100 (that is, the local device) can obtain the static information and dynamic information (also referred to as personalized data), in the scenario where it is detected that the user views an application component provided by a certain remote device on the desktop, the electronic device 100 may dynamically display the application component provided by the remote device based on the above static information and dynamic information.
  • the static information and dynamic information also referred to as personalized data
  • Solution 3 (the electronic device 100 statically displays the application component when it detects a specific scene associated with one or more application components):
  • the electronic device 100 (that is, the local device) can obtain the static information of the application components provided by the one or more remote devices through the trusted connection established with the one or more remote devices, In a specific scene associated with the component (for example, a scene where the user enters a keyword associated with one or more application components to search, etc.), the electronic device 100 may automatically recommend and statically display the application related to the specific scene based on the above static information.
  • Application components including application components of the local device, and/or application components of the remote device establishing a trusted connection with the local device).
  • Solution 4 (the electronic device 100 dynamically displays the application component when it detects a specific scene associated with one or more application components):
  • the electronic device 100 (that is, the local device) can obtain the static information and dynamic information (also referred to as personalized data), when detecting a specific scene associated with one or more application components (for example, a scene where the user enters a keyword associated with one or more application components to search, etc.), the electronic device 100 may base on the above static information and dynamic information to automatically recommend and dynamically display the application components associated with the above specific scenarios (including the application components of the local device, and/or the application components of the remote device establishing a trusted connection with the local device).
  • the static information and dynamic information also referred to as personalized data
  • the electronic device 100 may base on the above static information and dynamic information to automatically recommend and dynamically display the application components associated with the above specific scenarios (including the application components of the local device, and/or the application components of the remote device establishing a trusted connection with the local device).
  • Fig. 2 exemplarily shows a communication system provided by an embodiment of the present application.
  • the communication system may include: multiple electronic devices.
  • the communication system may also be referred to as a distributed system.
  • the multiple electronic devices included in the communication system are all intelligent terminal devices, and may be of various types.
  • the embodiment of the present application does not limit the specific types of the multiple electronic devices.
  • the plurality of electronic devices may include mobile phones, and may also include tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, smart screens, wearable devices, augmented reality (Augmented Reality, AR) devices, Virtual reality (Virtual Reality, VR) devices, artificial intelligence (AI) devices, car machines, smart headsets, game consoles, can also include Internet of Things (IOT) devices, smart home devices such as smart water heaters, smart Lamps, smart air conditioners, or smart sports equipment, smart medical devices such as blood pressure machines, etc.
  • IOT Internet of Things
  • Multiple electronic devices in the communication system can be connected by logging in with the same account.
  • multiple electronic devices can log in to the same Huawei account, and remotely connect and communicate through the server.
  • the account can be a mobile phone number, an email address, a user-defined user name, a user name assigned by an APP server, a user name used for login in an APP in an electronic device, and the like.
  • Multiple electronic devices in the communication system can also log in to different accounts, but they are connected through binding. After an electronic device logs in to an account, it can be bound to other electronic devices logged in with different accounts or not logged in in the device management application, and then these electronic devices can communicate with each other through the device management application.
  • Multiple electronic devices in the communication system can also establish connections by scanning two-dimensional codes, near field communication (near field communication, NFC) touching, searching for Bluetooth devices, etc. There is no limitation here.
  • the communication connections established between multiple electronic devices in the communication system may include but not limited to: wired connections, wireless connections such as Bluetooth (bluetooth, BT) connections, wireless local area networks (wireless local area networks, WLAN) Such as wireless fidelity point-to-point (wireless fidelity point to point, Wi-Fi P2P) connection, near field communication (near field communication, NFC) connection, infrared technology (infrared, IR) connection, and remote connection (such as established through the server connection) and so on.
  • wireless connections such as Bluetooth (bluetooth, BT) connections, wireless local area networks (wireless local area networks, WLAN)
  • wireless fidelity point-to-point wireless fidelity point to point, Wi-Fi P2P
  • NFC near field communication
  • infrared technology infrared, IR
  • each electronic device in the communication system can form a network (that is, a network) according to a certain communication protocol and networking strategy, so that each electronic device in the communication system can communicate with each other.
  • Multiple electronic devices in the communication system can be configured with different software operating systems (Operating System, OS), including but not limited to etc. in, It is Huawei's Hongmeng system.
  • OS software operating systems
  • the multiple electronic devices can all be configured with the same software operating system, for example, they can all be configured
  • the software operating systems of many electronic devices are , the communication system can be regarded as a hyper terminal.
  • FIG. 3A exemplarily shows a software architecture of an electronic device 100 involved in the process of displaying application components provided by the embodiment of the present application (taking the Android system as an example).
  • the electronic device 100 may include an application layer and a framework layer.
  • the application layer may include a series of application programs. As shown in FIG. 3A , the application layer may include desktops (host end) and other business applications (service end) other than the desktop.
  • desktops host end
  • service end business applications
  • the desktop can include an application component host module (App Widget Host) and an application component host view module (App Widget Host View).
  • App Widget Host an application component host module
  • App Widget Host View an application component host view module
  • the application component host module is an interface provided by the desktop (host end), which can be used to support application components embedded in the desktop (host end), and can save the interface logic information of application components;
  • the application component host view module includes remote view Module (RemoteView), the application component host view module can be used to display the application component based on the description about the application component in the remote view module, and the remote view module can be used to obtain the interface logic information of the application component saved in the application component host module, Application components are displayed in the application component host view module.
  • RemoteView remote view Module
  • service may include a service module (Service), an application component provider (RemoteViewProvider), a remote view module (RemoteView), and AndroidManifest.xml files, etc.
  • RemoteViewProvider an application component provider
  • RemoteView Remote view module
  • AndroidManifest.xml files etc.
  • the service module can be used to provide related services required by the application
  • the application component provider is a broadcast receiver (BroadcastReceiver), which can be used to receive broadcast messages for updating the application component interface
  • the remote view module can be used to describe the application component view information, such as various information required to update the application component interface, etc.
  • the AndroidManifest.xml file includes the configuration information of the application, which can be used to describe each module in the application (such as service module, application component provider, remote view modules, etc).
  • the framework layer can provide an application programming interface (application programming interface, API) and a programming framework for applications in the application layer.
  • the framework layer includes some predefined functions.
  • the framework layer may include an application component management module (App Widget Manager), an application component service module (App Widget Service) and the like.
  • App Widget Manager an application component management module
  • App Widget Service an application component service module
  • the application component management module can be used to provide a channel for application component data and event interaction between the business end and the host end, and the application component service module can be used to be responsible for the management of application components (such as loading application components, deleting application components, processing timing events, etc.).
  • the application component host view module on the host side will send an application component interface update event to the business side in the form of a broadcast message, and the business side will create a service through the service module and notify the update interface Send it to the remote view module through the application component provider, the remote view module will generate various information required to update the interface, and send the various information required to update the interface to the application component management module of the framework layer, and the application component management module will Call some methods provided by the application component service module to send various information required to update the interface to the application component host module on the host side.
  • the application component host module will update the application component based on various information required to update the interface and pass the application component
  • the host view module is used to display the updated application component interface on the host side.
  • the application component management module in the framework layer above provides a channel for the host and business to interact with application component data and events.
  • the container Container
  • the data of the business is completed.
  • a container is a software program that can provide an operating environment for an application component and manage a life cycle of the application component.
  • the current application component management module only realizes the management of the application components of the local device, and does not realize the management of cross-device application components. Moreover, the interface logic information of the application components and the modules required for the event processing process are packaged in the application package , is not separated from the application package.
  • the embodiment of the present application provides another software architecture of the electronic device 100 .
  • FIG. 3B exemplarily shows a software architecture of an electronic device 100 involved in the application component management method provided by the embodiment of the present application.
  • the electronic device 100 may include an application layer, a framework layer, a system service layer, a kernel and a hardware platform layer, and a network communication hardware layer.
  • the application layer may include a series of application programs. As shown in FIG. 3B , the application layer may include a desktop (host end) and other business applications (service end) except the desktop.
  • the desktop can provide a container for injecting application components, display application components, and support application components to be embedded and run on the desktop.
  • application component packages also called application component installation packages
  • application packages also called application program installation packages
  • the application component package is separated from the application package, and the application component package only contains the business logic and services involved in the application component.
  • the application component package can be decoupled from the application package, lightweight, and It can be installed independently, that is, even if the application corresponding to the application component is not installed on the electronic device, the electronic device can also install the application component.
  • the application component Since the application component is not a separate user interface program, it must be embedded in a certain program (ie, the host end) before it can run.
  • the host end of the application component can be a desktop, that is, the application component can Embedded into the desktop to run.
  • the embodiment of the present application only takes the desktop as an example of the host end of the application component, and the host end of the application component may also be other application programs, which is not limited in the embodiment of the present application.
  • the framework layer can provide an application programming interface (application programming interface, API) and a programming framework for applications in the application layer.
  • the framework layer includes some predefined functions.
  • the framework layer may include an application component management service module and a package management service module (PackageManagerService, PMS).
  • PackageManagerService PMS
  • the application component management service module can be used to manage the application component information list of the local device and the available application component information list of one or more remote devices that establish a trusted connection with the local device, etc., and can be used by the desktop (host) transfer;
  • the package management service module can be used to manage various application component packages and application packages, and can provide package installation, package registration, package information management and other capabilities.
  • the system service layer is a set of core capabilities of the system, and the system service layer can provide services to applications in the application layer through the framework layer.
  • the system service layer may include a device management module, a distributed data management module, an application component information database, a data communication soft bus, and a security verification management module.
  • the device management module can be used to manage the device information of the local device and the device information of one or more remote devices that have established a trusted connection with the local device, and can provide related APIs to the upper module.
  • the distributed data management module can provide cross-device data synchronization capabilities and service APIs to synchronize business data for upper-level business applications.
  • the application component information database may be used to store the application component packages and the corresponding personalized data of the local device and one or more remote devices establishing a trusted connection with the local device.
  • the data communication soft bus can provide capabilities such as device registration, device discovery, device connection, and device communication based on network connection information.
  • the security verification management module can verify the legitimacy of the remote device based on the device certificate, account number, signature and other information to ensure that the remote device is a trusted device, and can provide related APIs, and can also perform trusted verification on the application component package information .
  • the kernel and the hardware platform layer may include a hardware abstraction layer (Hardware Abstraction Layer), a kernel, and a driver.
  • a hardware abstraction layer Hardware Abstraction Layer
  • kernel a kernel
  • driver a driver
  • the hardware abstraction layer runs in user space (UserSpace), encapsulates the kernel layer driver, and provides a call interface to the upper layer.
  • the kernel layer is the layer between hardware and software.
  • the kernel layer can include display driver, camera driver, audio driver, sensor driver, Bluetooth driver, etc.
  • the kernel and hardware platform layers may include a kernel abstract layer (kernel abstract layer, KAL) and a driver subsystem.
  • KAL includes multiple kernels, such as the kernel Linux Kernel of the Linux system, the lightweight IoT system kernel LiteOS, etc.
  • the driver subsystem may include a Hardware Driver Foundation (HDF).
  • HDF Hardware Driver Foundation
  • the hardware driver framework can provide a unified peripheral access capability and a driver development and management framework.
  • the multi-core kernel layer can select the corresponding kernel for processing according to the requirements of the system.
  • the network communication hardware layer may include hardware such as a Wi-Fi module and a Bluetooth module, for realizing communication between different devices.
  • the desktop can rely on the application component management service module to obtain a full list of application component information, wherein the full list of application component information can include the list of application component information of the local device, and/or establish a trusted connection with the local device A list of application component information of one or more remote devices.
  • the application component management service module can rely on the package management service module to obtain application component information, and can also rely on the device management module to obtain a list of trusted devices that have been networked (that is, the list of one or more remote devices that have established a trusted connection with the local device). device information list).
  • the package management service module can rely on the distributed data management module to synchronize the full application component information of the networked trusted devices to the local device.
  • the device management module can rely on the data communication soft bus to obtain device information (such as device categories, etc.) of trusted devices that have been networked, and can also rely on the security verification management module to verify the legitimacy of the remote device to ensure that the remote device is a trusted device , where the trusted device may include, but not limited to, a device under the same network as the local device, or a device logged in with the same account as the local device.
  • the distributed data management module can rely on the data communication soft bus for cross-device data synchronization, and can also rely on the security verification management module to perform trusted verification of application component information.
  • the data communication soft bus can rely on the kernel and hardware platform layer to realize network communication between devices through network communication hardware.
  • the driver may rely on the network communication hardware layer to implement network communication between devices (for example, wireless communication such as Wi-Fi communication and Bluetooth communication, or wired communication).
  • devices for example, wireless communication such as Wi-Fi communication and Bluetooth communication, or wired communication.
  • FIG. 3A and FIG. 3B are merely exemplary, and should not impose any limitation on the software architecture of the electronic device 100 in the embodiment of the present application.
  • the system architecture of the electronic device 100 may also adopt a layered structure different from the example shown in FIG. 3A and FIG. 3B , or each layer may also include more or fewer modules. , or a combination of multiple different module modes, etc., which are not limited in this embodiment of the present application.
  • the electronic device 100 may also include all or part of the modules shown in FIG. 3A and all or part of the modules shown in FIG. 3B , which is not limited in this embodiment of the present application.
  • FIG. 4 exemplarily shows a specific flow of a method for managing application components provided by an embodiment of the present application.
  • the method may be applied to a communication system including an electronic device 100 (ie, a local device) and an electronic device 200 (ie, a remote device).
  • a communication system including an electronic device 100 (ie, a local device) and an electronic device 200 (ie, a remote device).
  • an electronic device 100 ie, a local device
  • an electronic device 200 ie, a remote device. The specific steps of this method are described in detail below:
  • a trusted connection needs to be established between the electronic device 100 and the electronic device 200. Only after the trusted communication connection is established can the steps in the following phases 2 and 3 be continued. , to achieve the purpose of displaying application components across devices.
  • a possible implementation manner of establishing a trusted connection between the electronic device 100 and the electronic device 200 may be the implementation described in the following stage 1 (step S401-step S405), which will be described in detail below:
  • Phase 1 Establish a trusted connection phase
  • the electronic device 100 detects an event triggering the establishment of a trusted connection, and in response to the event, the electronic device 100 sends a request for establishing a connection and a request for obtaining device information of the electronic device 200 to the electronic device 200 .
  • the above-mentioned event that triggers the establishment of a trusted connection may be an operation (such as a finger sliding operation, etc.) that triggers the display of the application component management interface (that is, the user interface for displaying and managing the application components of the local device and the remote device) on the desktop. /command (such as voice command, etc.), or the user triggers the operation of establishing a communication connection between the electronic device 100 and the electronic device 200 through the interface of the "Settings" application program, etc., which are not limited in this embodiment of the present application.
  • the electronic device 100 may also be triggered to establish a trusted connection with the electronic device 200 based on a certain characteristic timing of the system (for example, after rebooting, after unlocking the lock screen, after system update, etc.).
  • the electronic device 200 establishes a communication connection 1 with the electronic device 100, and sends the device information of the electronic device 200 to the electronic device 100.
  • the electronic device 200 After the electronic device 200 receives the request for establishing a connection and obtaining the device information of the electronic device 200 sent by the electronic device 100 , it can establish a communication connection 1 with the electronic device 100 and send the device information of the electronic device 200 to the electronic device 100 . information.
  • the device information of the electronic device 200 may include but not limited to the device type, device name, device identification (Identity Document, ID), serial number, media access control address, device model and other information of the electronic device 200. This is not limited.
  • both the request for establishing a connection and the request for obtaining device information of the electronic device 200 may carry the device information of the electronic device 100 .
  • the device information of the electronic device 100 may include but not limited to the device type, device name, device ID, serial number, media access control address, device model and other information of the electronic device 100, which is not limited in this embodiment of the present application.
  • the electronic device 100 performs credible verification on the electronic device 200 based on the device information of the electronic device 200, and if the credible verification succeeds, it determines that the communication connection 1 is a trusted connection.
  • the electronic device 100 can perform credible verification on the electronic device 200 based on the device information of the electronic device 200, wherein the information verified by the credible verification process includes but not It is limited to information such as the device certificate of the electronic device 200 and the account number logged in.
  • the credible verification succeeds, it is determined that the electronic device 200 is a credible device, and the communication connection 1 is a credible connection.
  • the electronic device 200 may also perform credible verification on the electronic device 100 in the above manner.
  • each step in the following phase 2 and phase 3 can be executed based on the trusted connection.
  • a possible cooperation mode between the various modules inside the electronic device 100 and the electronic device 200 in the above-mentioned phase of establishing a trusted connection is exemplarily introduced below with reference to FIG. 5 :
  • Step 1 The desktop of the electronic device 100 detects an event that triggers the establishment of a trusted connection. After that, the desktop can call the application component management service module of the electronic device 100 to obtain a list of device information.
  • the above-mentioned event triggering the establishment of a trusted connection may be the user's operation of sliding a finger on the desktop as shown in FIG. 6 .
  • Step 2 the application component management service of the electronic device 100 can access the device management module to request the device management module to obtain the device information list.
  • Step 3 The device management module of the electronic device 100 can access the data communication soft bus to request to obtain the remote device information (ie, the device information of the electronic device 200 ).
  • Step 4 the data communication soft bus of the electronic device 100 can request the electronic device 200 to establish a connection and obtain remote device information through the kernel and hardware platform layer, and the network communication hardware layer.
  • the data communication soft bus of the electronic device 200 can receive the request for establishing a connection and the request for obtaining remote device information sent by the electronic device 100 through the kernel, the hardware platform layer, and the network communication hardware layer. After that, the electronic device 200 can pass Call the data communication soft bus to establish a connection with the electronic device 100 , and send the device information of the electronic device 200 to the electronic device 100 .
  • Step 6 After the electronic device 100 receives the device information of the electronic device 200, the device management module of the electronic device 100 can call the security verification management module to request the security verification management module to perform credible verification on the electronic device 200. If the credible verification If successful, it can be determined that the connection established between the electronic device 100 and the electronic device 200 is a trusted connection.
  • the electronic device 100 may obtain and store application component information of the electronic device 200 based on the trusted connection.
  • a possible implementation manner for the electronic device 100 to obtain and save the application component information of the electronic device 200 may be the implementation described in the following stage 2 (step S406-step S410), which will be described in detail below:
  • Phase 2 Obtain and save application component information phase
  • the electronic device 100 detects an event triggering the acquisition of application component information, and in response to the event, the electronic device 100 sends a request to the electronic device 200 for obtaining the application component information.
  • the above-mentioned event triggering the acquisition of application component information may include, but not limited to, the user’s operation on the desktop to trigger the display of the application component management interface (that is, the user interface for displaying and managing the application components of the local device and the remote device) (such as sliding a finger operation, etc.)/instructions (such as voice commands, etc.).
  • the user s operation on the desktop to trigger the display of the application component management interface (that is, the user interface for displaying and managing the application components of the local device and the remote device) (such as sliding a finger operation, etc.)/instructions (such as voice commands, etc.).
  • the electronic device 100 may also be triggered to obtain application component information from the electronic device 200 based on a fixed timing.
  • the application component information is acquired from the electronic device 200 .
  • the electronic device 100 may also be triggered to obtain application component information from the electronic device 200 based on a certain characteristic timing of the system (such as power-on, restart, lock screen unlock, system update, etc.). Events for obtaining application component information are not limited.
  • the electronic device 200 queries the application component information list 1 (that is, the local application component information list of the electronic device 200 ), and sends the application component information list 1 to the electronic device 100 .
  • the application component information list 1 that is, the local application component information list of the electronic device 200
  • the electronic device 200 After the electronic device 200 receives the request for obtaining application component information sent by the electronic device 100 , it can query all local application component information of the electronic device 200 , and all the local application component information of the electronic device 200 can form the application component information list 1 . After the query is completed, the electronic device 200 may send the application component information list 1 to the electronic device 100 .
  • the interface currently displayed by the electronic device 200 is an application component management interface, which may include all local application components of the electronic device 200 , such as sports and health application components and schedule application components.
  • the above application component information list 1 may include sports health application component information and schedule application component information.
  • step S408-step S409 may be executed periodically, without triggering the execution after the electronic device 100 sends a request for acquiring application component information.
  • the above-mentioned application component information list 1 may not include all the local application component information of the electronic device 200, but only include part of the local application component information of the electronic device 200 (for example, some application component information commonly used by the electronic device 200 ).
  • the electronic device 100 saves the application component information list 1.
  • the electronic device 100 may save the application component information list 1, so that when the user wants to view the application components of the electronic device 200 on the electronic device 100, Application components of the electronic device 200 may be displayed based on the application component information list 1 .
  • a possible cooperation mode between the electronic device 100 and each module inside the electronic device 200 in the above-mentioned phase of obtaining and saving application component information is exemplarily introduced below with reference to FIG. 8 :
  • Step 1 The desktop of the electronic device 100 detects an event that triggers the acquisition of application component information. After that, the desktop can call the application component management service module of the electronic device 100 to obtain a list of application component information.
  • the above-mentioned event that triggers the acquisition of application component information may be the user's operation of sliding a finger on the desktop as shown in FIG. 6 .
  • Step 2 the application component management service of the electronic device 100 can access the package management service module to request the package management service module to obtain the application component information list.
  • the list of application component information may include: a list of local application component information of the electronic device 100 (such as a list of all local application component information of the electronic device 100), a list of local application component information of the electronic device 200 (such as a list of all local application component information of the electronic device 200). list of application component information).
  • Step 3 the package management service module of the electronic device 100 can access the distributed data management module to request to obtain the list of application component information of the local device and the remote device.
  • the application component information list of the local device is the local application component information list of the electronic device 100, and the distributed data management module can directly query it in the application component information database, while the application component information list of the remote device (that is, the electronic device 200 local application component information list) needs to be obtained through the following steps 4-9.
  • Step 4 the distributed data management module of the electronic device 100 can access the data communication soft bus to request to obtain the application component information of the remote device (ie, the local application component information of the electronic device 200).
  • the data communication soft bus of the electronic device 100 can request the electronic device 200 to obtain remote device information based on the trusted connection established with the electronic device 200 in advance (ie, through the kernel and hardware platform layer, network communication hardware layer).
  • Step 6 The data communication soft bus of the electronic device 200 may receive the request from the electronic device 100 to acquire the application component information of the electronic device 200 through the kernel, hardware platform layer, and network communication hardware layer.
  • Step 7 the data communication soft bus of the electronic device 200 can access the distributed data management module to request to acquire the application component information of the electronic device 200 .
  • the distributed data management module of the electronic device 200 may directly query the application component information of the electronic device 200 in the application component information database. After the query is completed, the application component information of the electronic device 200 may be sent to the electronic device 100 based on the trusted connection established with the electronic device 100 in advance.
  • the application component information of the electronic device 200 may include information such as remote application component package 1, remote application component package 2, . . . , remote application component package n shown in FIG. 8 .
  • Step 9 After receiving the application component information of the electronic device 200, the electronic device 100 may save the application component information of the electronic device 200 in the application component information database through the distributed data management module.
  • the application component information of the electronic device 200 acquired by the electronic device 100 is an application component package corresponding to each application component of the electronic device 200 .
  • the electronic device 100 can also obtain the application program information of the electronic device 200, where the application program information can include the application package and application package corresponding to each application program of the electronic device 200 component package, or the application program information may include an application package corresponding to each application program of the electronic device 200, wherein the application package may include an application component package. Afterwards, the electronic device 100 may display the application components of the electronic device 200 based on the acquired application program information of the electronic device 200 .
  • the electronic device 100 When the electronic device 100 detects that the user wants to view the application component information list, it may display the application components of the local device (that is, the electronic device 100 ) based on the application component information obtained in the second stage above, and/or, communicate with the local An application component of one or more remote devices (eg, electronic device 200 ) that establishes a trusted connection with the terminal device.
  • the local device that is, the electronic device 100
  • the electronic device 100 may display the application components of the local device (that is, the electronic device 100 ) based on the application component information obtained in the second stage above, and/or, communicate with the local An application component of one or more remote devices (eg, electronic device 200 ) that establishes a trusted connection with the terminal device.
  • a possible implementation manner of displaying application components on the electronic device 100 may be the implementation manner described in the following stage three (step S411-step S412), which will be described in detail below:
  • Phase 3 Display Application Components Phase
  • the electronic device 100 detects the operation of the user viewing the application components of the electronic device 200, and in response to the operation, the electronic device 200 displays the electronic device 200 based on the application component information list 1 (ie, the local application component information list of the electronic device 200) application components.
  • the application component information list 1 ie, the local application component information list of the electronic device 200
  • the electronic device 100 may detect the user's operation of opening the application component management interface (for example, the user's operation of sliding the finger on the desktop as shown in FIG.
  • the user interface 910 is shown, and the user interface may be an application component management interface.
  • the application component management interface can display not only the local application components of the electronic device 100 , but also display the application components of one or more remote devices (for example, all application components of the electronic device 200 ) that establish a trusted connection with the electronic device 100 .
  • the electronic device 100 can display the application components (such as local application component 1, local application component 2. Local application component 3, local application component 4, etc.).
  • the application components such as local application component 1, local application component 2. Local application component 3, local application component 4, etc.
  • the electronic device 100 opens the application component management interface, only the identification option of the electronic device 100 (such as the "local” option 911) and the electronic The device 100 establishes the identification options of one or more remote devices (for example, "My Tablet” option 912, etc.) of trusted connections.
  • the identification option of the electronic device 100 is selected, or establishes a trusted connection with the electronic device 100
  • the application component corresponding to the electronic device will be correspondingly displayed in the application component management interface.
  • FIG. 9A when the identification option of the local machine (that is, the electronic device 100) is selected, the local application components of the electronic device 100 are displayed in the application component management interface; as shown in FIG.
  • the electronic device 100 may have acquired and saved the application component information list of other remote devices including the electronic device 200 that has established a trusted connection with the electronic device 100 in the background, or when the user opens the electronic device 100
  • the electronic device 100 is triggered to obtain the application component information list of other remote devices that have established a trusted connection with the electronic device 100, including the electronic device 200, and save it.
  • the identification option of the electronic device 200 is selected
  • the electronic device 100 may display the application components of the electronic device 200 on the application component management interface based on the stored application component information list of the electronic device 200 .
  • this method is to execute the third stage after the above-mentioned stage two (that is, the stage of obtaining and saving the application component information) is executed.
  • the list of application component information about other electronic devices has been pre-saved, it can be
  • the application component information list of the electronic device is loaded in the application component management interface at a faster speed, which can enable the user to view the application components of other electronic devices more quickly, and the user experience is better.
  • the electronic device 100 when the electronic device 100 detects that the identification option of the electronic device 200 is selected, it may then obtain the application component information list of the electronic device 200 from the electronic device 200, and based on the obtained application component information list of the electronic device 200 in the electronic
  • the application components of the electronic device 200 are displayed on the application component management interface corresponding to the identification option of the device 200 . That is to say, this way is to execute the above-mentioned stage two (that is, the stage of obtaining and saving application component information) after step S411 in stage three is executed. In this way, between the electronic device 100 and other multiple When the remote device establishes a trusted connection, the network traffic and power consumption generated by the electronic device 100 obtaining the application component information list of other remote devices can be reduced, which is beneficial to saving resources.
  • the identification options of the electronic device 100 and the identification options of the electronic device 200 are generated by the electronic device 100 based on the device information of the electronic device 100 and the device information of the electronic device 200 respectively.
  • the application component management interface displays the application components
  • the identification of the electronic device corresponding to the application component can also be displayed on each application component, so that the user can know which application component is provided by electronic equipment.
  • the application component management interface can also simultaneously display the application components of the local machine and the application components of other remote devices that have established a trusted connection with the local machine, and the user can use each application component to The identification of the corresponding electronic device displayed on the screen can be used to distinguish which electronic device provides the application component.
  • the embodiment of the present application does not limit the display manner of the user interface displaying the application components.
  • the electronic device 100 (that is, the local device) can establish a trusted connection with one or more remote devices (such as the electronic device 200), and through the trusted connection, the electronic device 100 can obtain
  • the list of application component information provided by the one or more remote devices can display the application components provided by the one or more remote devices based on the list of application component information, which can solve the problem that the user cannot view cross-device Application component issues to improve user experience.
  • Step 1 the desktop of the electronic device 100 detects that the user views the operation of the application component of a specific device (such as the electronic device 100 or the electronic device 200, etc.), and then the desktop can call the application component management service module of the electronic device 100 to obtain the application component Information List.
  • a specific device such as the electronic device 100 or the electronic device 200, etc.
  • Step 2 the application component management service module of the electronic device 100 can access the package management service module to request the package management service module to obtain the application component information list.
  • Step 3 the package management service module of the electronic device 100 can access the distributed data management module to request to obtain the list of application component information of the local device and the remote device.
  • the package management service module can also only request the distributed data management module to obtain the application component information list of the above-mentioned specific device, instead of all devices (that is, the local device and all remote devices that have established trusted connections with the local device) device) application component information list.
  • Step 4 The distributed data management module of the electronic device 100 can obtain the application component information list in the application component information database, and then return the obtained application component information list to the desktop for displaying the application components of the corresponding electronic device.
  • the distributed data management module may obtain only the application component information list of the above-mentioned specific device, or may obtain the application component information list of all devices (that is, the local device and all remote devices that have established trusted connections with the local device).
  • the application component information database can store the application component information list of the local device and the application component information list of one or more remote devices that have established a trusted connection with the local device obtained by the local device , as shown in FIG. 10 , the application component information list of each electronic device may include the device type of the electronic device, the device ID of the electronic device, and one or more application component packages provided by the electronic device, wherein the application Compared with the application entity itself, the component package is a lightweight installation package. In this way, the distributed data management module can query the application component package under the corresponding electronic device based on the device ID and/or device type.
  • the electronic device 100 (local device) is a mobile phone
  • the device type recorded in the application component information list of the electronic device 100 is a mobile phone
  • the device ID is XX (that is, the device ID of the electronic device 100)
  • the packages are local application component package 1, local application component package 2, ..., local application component package n
  • the electronic device 200 (remote device) is a tablet
  • the device type recorded in the application component information list of the electronic device 200 is a tablet
  • the device ID is XXX (that is, the device ID of the electronic device 200)
  • the application component packages provided by the electronic device 200 are remote application component package 1, remote application component package 2, . . . , remote application component package n.
  • each application component package may include static information of the application component corresponding to the application component package, and the static information may include preset information that the application component can present (such as title information such as location, temperature, etc. , size information, etc.), excluding user data, that is, the information that the application component can present in the preview mode (or in the initialization state) (such as the preview image, title, size, etc. of the application component), and does not include Can change over time or user behavior.
  • preset information that the application component can present such as title information such as location, temperature, etc. , size information, etc.
  • user data that is, the information that the application component can present in the preview mode (or in the initialization state) (such as the preview image, title, size, etc. of the application component), and does not include Can change over time or user behavior.
  • both the application component 913 and the application component 914 in FIG. 9B present static information, wherein the static information in the application component 913 may include location information (such as "region.city”), temperature information (such as “temperature”), step information (such as "0 step”), etc.; the static information in the application component 914 may include schedule information (such as "XX schedule tomorrow", “schedule 1", “schedule 2"), etc. .
  • FIG. 9B uses the aforementioned solution 1 (the electronic device 100 statically displays the application components in the scene where the user is viewing the application components on the desktop) to display the application components of the remote device that establishes a trusted connection with the electronic device 100.
  • the electronic device 100 can only obtain static information of application components in the above-mentioned phase 2 (that is, the phase of obtaining and saving application component information), and then statically display the application components on the remote device based on the static information.
  • the electronic device 100 may not obtain the installation package of the application component, but only obtain relevant information for statically displaying the application component, which can save system resources.
  • the relevant information may include the component identification of the application component and the description information of the application component; wherein, the component identification of the application component may include the package name and module name of the application component, and the package name, for example, com.xxx.xxx.sporthealth , which can indicate that the application corresponding to the application component is running healthy, and the module name, for example, com.xxx.xxx.weather, can indicate that the application component is a weather application component; wherein, the description information of the application component can include but is not limited to The preview image, title (such as sports health, weather, location, etc.), size and other information of application components.
  • the electronic device 100 can then obtain the installation package of the application component from the remote device, and after obtaining the installation package of the application component, it can The application component is installed, and after the installation is completed, the application component can be added to the desktop for display.
  • the application component package corresponding to the application component can also be associated with the dynamic information of the application component, and the dynamic information can include that the user is using the application component
  • the information presented by the specific data that is, user data, which can also be called personalized data
  • the specific data can be the type of information (such as location, exercise steps, etc.) The corresponding data will change with time or user behavior.
  • the application component 913 sports and health application component
  • the application component 914 switchedule application component
  • FIG. 9B the difference from Figure 9B is that since the user has started using the two application components, the two application components will generate dynamic information, and further, the corresponding dynamic information will be displayed on the two application components Information, for example, the application component 913 displays the area where the user is located (such as "Qixia District.
  • Nanjing the temperature in the area where the user is located (such as “22 degrees”), the number of steps the user currently moves (such as “6888 steps”), etc.;
  • the application component 914 displays the number of the user's schedules for tomorrow (for example, “2 schedules for tomorrow"), the specific schedule for tomorrow (for example, "annual sales description", "next year's budget report”), and the like.
  • the electronic device 100 dynamically displays the application component
  • the difference between the aforementioned solution two and the aforementioned solution one is that while the electronic device 100 obtains the static information of the application component in the above-mentioned phase two (that is, the phase of obtaining and saving the application component information), if the application component also includes a dynamic information, it is also necessary to obtain the dynamic information of the application component, and save both the static information and the dynamic information of the application component, and then dynamically display the application component on the remote device based on the static information and dynamic information of the application component.
  • Obtaining the dynamic information of the application components can display the application components consistent with the state of the remote device.
  • the two application components shown in FIG. 11B are application components including dynamic information. It can be seen from FIG. 11B and FIG.
  • the status of the application components is consistent, so that the user can view the real-time status of the application components on the remote device on the local device, which is convenient and quick, and improves user experience.
  • the identification of the electronic device corresponding to the application component can also be displayed on each application component, so that the user can know which electronic device provides the application component. of.
  • the application component management interface can also display the application components of the local machine and the application components of other remote devices that have established a trusted connection with the machine, and the user can use each application component
  • the identification of the corresponding electronic device displayed on the screen can be used to distinguish which electronic device provides the application component.
  • the embodiment of the present application does not limit the display manner of the user interface displaying the application components.
  • an application component including only static information may be called a static application component
  • an application component including dynamic information such as the application component shown in FIG. 11B
  • Dynamic application components may be called Dynamic application components.
  • the static display method of application components shown in Figure 9B only allows the user to view the available application components provided by the remote device on the local device, but cannot allow the user to view these applications on the local device.
  • the real-time status of the components on the remote device Compared with the static display of the application components, the dynamic display of the application components shown in Figure 11B allows the user to view the available applications provided by the remote device on the local device. What are the components, and the user can view the real-time status of these application components on the remote device on the local device (that is, the status of the application component displayed on the local device is consistent with the status of the application component displayed on the remote device), Further improved user experience.
  • the dynamic application component shown in FIG. 11B can not only be displayed on the application component management interface of the local device, but can also be added to the desktop of the local device for display.
  • the electronic device 100 may detect the user's operation (such as a long press operation) on the sports and health application component, and in response to the operation, the electronic device 100 may display a window 1210, and the window 1210 may include an option 1211 (for example, "inject into local"). Further, the electronic device 100 may detect an operation (for example, a click operation) of the user on the option 1211, and respond to the operation, as shown in FIG.
  • the electronic device 100 may add a sports and health application component to the desktop for display.
  • the user can also add the application component to the desktop of the local device for display by dragging and dropping. The specific operation is not limited.
  • the application components of the remote device can be directly displayed on the desktop of the local device, and the user can view the status of the application components on the remote device more conveniently, further improving user experience.
  • FIG. 10 shows that when the electronic device 100 detects that the user is viewing the application component on the desktop and statically displays the application component (such as the application component shown in FIG. 9B ), the internal modules 13, the following exemplifies how the electronic device 100 dynamically displays the application components (such as the application components shown in FIG. 11B ) when the electronic device 100 detects that the user is viewing the application components on the desktop.
  • Step 1 the desktop of the electronic device 100 detects that the user views the operation of the application component of a specific device (such as the electronic device 100 or the electronic device 200, etc.), and then the desktop can call the application component management service module of the electronic device 100 to obtain the application component Information List.
  • a specific device such as the electronic device 100 or the electronic device 200, etc.
  • Step 2 the application component management service module of the electronic device 100 can access the package management service module to request the package management service module to obtain the application component information list.
  • Step 3 the package management service module of the electronic device 100 can access the distributed data management module to request to obtain the list of application component information of the local device and the remote device.
  • the package management service module can also only request the distributed data management module to obtain the application component information list of the above-mentioned specific device, instead of all devices (that is, the local device and all remote devices that have established trusted connections with the local device) device) application component information list.
  • Step 4 the distributed data management module of the electronic device 100 may acquire the application component information list in the application component information database.
  • the dynamic information of the application component may also be stored in the application component information database.
  • the application component information database may also be stored in the application component information database.
  • the personalized data is illustrated below: Assume that the electronic device whose device type is a tablet stored in the application component information database is the electronic device 200, and the application component corresponding to the remote application component package 1 under the electronic device is the sports health application component in FIG. 11B, and the application component corresponding to the remote application component package 2 is the schedule application component in FIG. For example, "Qixia District. Nanjing"), the temperature data of the user's area (such as "22 degrees"), the user's current exercise step data (such as "6888 steps”), etc.
  • Personalized data 2 can include the display in the calendar application component The user's tomorrow's schedule number data (such as “tomorrow 2 schedules"), tomorrow's specific schedule data (such as “annual sales description", “next year's budget report”), etc.
  • the distributed data management module can return it to the package management service module, so as to perform subsequent steps.
  • Step 5 the package management service module of the electronic device 100 installs the application components including the personalized data.
  • the package management service module can determine whether the application component package in the returned application component information list is associated with personalized data (that is, determine which application component includes dynamic information ), if so, the package management service module needs to install the application component, that is, the package management service module is responsible for installing the application component including dynamic information.
  • Application components that do not include dynamic information do not need to be installed, and they still only display static information on the local device.
  • Step 6 The application component management service module of the electronic device 100 injects the successfully installed application components including dynamic information into the application component container (such as the desktop).
  • the application component container such as the desktop
  • the application component management service module can inject it into the application component container, so that the application component can run in the container.
  • the application component management interface may be a user interface provided by the desktop application, and then the application component container may be provided by the desktop application.
  • each application can provide one or more containers. If the application only provides one container, multiple user interfaces of the application can share one container. In this case, each user interface of the application can independently use one or more containers, for example, multiple application components displayed in the application component management interface can be injected into the same container, or can be injected into multiple containers (e.g. a container injected into an application component).
  • the application program providing the application component container is an example of a desktop application program, and is not limited thereto.
  • Other application programs may also provide the application component container, which is not limited in this embodiment of the present application.
  • Step 7 The application component including the personalization data on the remote device reads the personalization data from the package management service module.
  • the application component can start running and read its corresponding personalized data from the package management service module. In this way, the application displayed on the electronic device 100 The component state can be consistent with the application component state displayed on the remote device.
  • the application component information of the electronic device 200 acquired by the electronic device 100 is the application component package corresponding to each application component of the electronic device 200 and the dynamic information of the application component.
  • the electronic device 100 can also obtain the application program information of the electronic device 200 and the dynamic information of the application components, wherein the application program information can include each application program of the electronic device 200 The corresponding application package and application component package, or the application program information may include the application package corresponding to each application program of the electronic device 200, wherein the application package may include the application component package. Afterwards, the electronic device 100 may display the application components of the electronic device 200 based on the acquired application program information and dynamic information of the application components of the electronic device 200 .
  • the electronic device 100 dynamically displays the application component on the remote device
  • the electronic device 100 installs the application component, in order to view the status of the application component on the remote device in real time
  • the electronic device 100 can periodically (for example, every 1 second, 10 seconds, 30 seconds, 1 minute, etc.) acquire user data (ie personalized data) generated during the running process of the application component from the remote device.
  • the electronic device 100 may not install the application component, or may install the application component.
  • the electronic device 100 may use the installation package of the application component through the package management service module. (that is, the application component package) to install the application component.
  • the application component When the application component is installed, the user can also add the application component to the desktop for display in the manner shown in Figure 12A; if the application component is not installed, when the user uses the When the application component is added to the desktop for display, the electronic device 100 will install the application component, and the application component can be displayed on the desktop after the installation is completed.
  • the electronic device 100 may also detect a specific scenario associated with one or more application components (for example, a scenario where the user enters a keyword associated with one or more application components to search, etc.) Automatically recommend to the user and statically display/dynamically display one or more application components associated with the above-mentioned specific scenario (ie, the aforementioned solution 3 and solution 4).
  • a specific scenario associated with one or more application components for example, a scenario where the user enters a keyword associated with one or more application components to search, etc.
  • the electronic device 100 may display a user interface 1310, which may be a user interface (ie, a search interface) in a search scenario, and the user interface may include a search Box 1311 , search option 1312 .
  • the electronic device 100 may detect that the user enters the word "sports" in the search box 1311 and clicks the search option 1312. In response to this operation, the electronic device 100 may use the word "sports" as a keyword in the local application component information database The fuzzy query matches the application components related to the keyword.
  • the electronic device 100 can be displayed in the area exemplarily shown in FIG. 14B
  • one or more application components for example, application component 1411 related to the word "sports" are statically displayed, that is, the electronic device 100 may only display static information of the one or more application components.
  • the one or more application components may be local application components of the electronic device 100 , or may be application components of a remote device establishing a trusted connection with the electronic device 100 .
  • the electronic device 100 may also display an application program 1412 in the area 1410, and the application program may be an application program providing the application component 1411, or an application program related to "sports" but not an application program providing the application component 1411 program.
  • Step 1 The electronic device 100 detects that the user queries the operation of the application component related to the keyword on a specific interface (such as a search interface). After that, the application program corresponding to the specific interface can call the application component management service module of the electronic device 100 to Query the application component information related to the keyword.
  • a specific interface such as a search interface
  • the above-mentioned user's operation of querying the application components related to the keyword may be an operation of the user inputting a keyword (such as "sports") in the search box 1311 shown in FIG. 14A and clicking the search option 1312 .
  • a keyword such as "sports”
  • the above-mentioned specific interface may be provided by a system application (that is, an application that cannot be uninstalled or whose App ID is less than 10000), or it may be provided by a third-party application (that is, an application other than the system application). This is not limited.
  • Step 2 the application component management service module of the electronic device 100 can access the package management service module to request the package management service module to query the application component information related to the keyword.
  • Step 3 the package management service module of the electronic device 100 can access the distributed data management module to request querying the application component information of the local device and the remote device related to the keyword.
  • Step 4 The distributed data management module of the electronic device 100 can query the application component information of the local device and the remote device related to the keyword in the application component information database. If the application component information related to the keyword can be queried, Then the distributed data management module can return the queried application component information related to the keyword to a specific interface for displaying the application component related to the keyword.
  • the application component information of the remote device stored in the application component information database is acquired by the electronic device 100 from the remote device, and the specific acquisition process can refer to the relevant content of the process of obtaining the application component information in the aforementioned solution 1, which will not be repeated here. .
  • the application component information database does not save the personalized data of the application component associated with the application component package
  • the application component information related to the keyword queried above is also The dynamic information of the application components will not be included, and only the static information of the application components will be included. Furthermore, the electronic device 100 will only statically display the application components related to the keyword based on the static information of the application components.
  • Solution 4 is introduced below (the electronic device 100 dynamically displays application components when detecting a specific scene associated with one or more application components):
  • the electronic device 100 may detect that the user enters the word "sports" in the search box 1311 and clicks the search option 1312. In response to this operation, the electronic device 100 can use the word "sports" as a keyword to fuzzily query and match application components related to the keyword in the local application component information database. component), the electronic device 100 can dynamically display one or more application components (such as application component 1611) related to the word "sports" in the area 1610 exemplarily shown in FIG. 16 , that is, the electronic device 100 can display this one or dynamic information about multiple application components. Wherein, the one or more application components may be local application components of the electronic device 100 , or may be application components of a remote device establishing a trusted connection with the electronic device 100 .
  • the electronic device 100 may also display an application program 1612 in the area 1610.
  • the application program may be an application program providing the application component 1611, or an application program related to "sports" but not an application program providing the application component 1611 program.
  • FIG. 16 and FIG. 14B that the application component 1611 shown in FIG. 16 and the application component 1411 shown in FIG. 14B are the same application component. The difference is that the application component shown in FIG. 14B is only its Static information, and its dynamic information is shown in Figure 16.
  • the static display method of the application components in Figure 14B can only let the user know what application components are related to the keywords entered by the user on the local device, but cannot let the user know the information on the remote device on the local device.
  • the real-time status of these application components Compared with the static display of application components, the dynamic display of application components in Figure 16 can let the user know on the local device which application components are related to the keywords entered by the user. , and allows the user to know the real-time status of these application components on the remote device on the local device (that is, the status of the application component displayed on the local device is consistent with the status of the application component displayed on the remote device), which further improves the user experience.
  • the following is an example of how the electronic device 100 dynamically displays the application components (such as the application components shown in FIG. Possible collaborations:
  • Step 1 The electronic device 100 detects the operation of the application component related to the user's query keyword on a specific interface (such as a search interface). After that, the application program corresponding to the specific interface can call the application component management service module of the electronic device 100 to query Application component information related to the keyword.
  • a specific interface such as a search interface
  • the above-mentioned operation of the user to query the application components related to the keyword may be an operation in which the user enters the keyword (for example, the word "sports") in the search box 1311 shown in FIG. 14A and clicks the search option 1312 .
  • the above-mentioned specific interface may be provided by a system application (that is, an application that cannot be uninstalled or whose App ID is less than 10000), or it may be provided by a third-party application (that is, an application other than the system application). This is not limited.
  • Step 2 the application component management service module of the electronic device 100 can access the package management service module to request the package management service module to query the application component information related to the keyword.
  • Step 3 the package management service module of the electronic device 100 can access the distributed data management module to request querying the application component information of the local device and the remote device related to the keyword.
  • Step 4 The distributed data management module of the electronic device 100 may query the application component information of the local device and the remote device related to the keyword in the application component information database.
  • the application component information of the remote device stored in the application component information database is acquired by the electronic device 100 from the remote device, and the specific acquisition process can refer to the relevant content of the process of obtaining the application component information in the second solution, and will not be repeated here. .
  • the dynamic information of the application component may also be stored in the application component information database.
  • Personalized data For the introduction of the personalized data, reference may be made to the related content in FIG. 13 , which will not be repeated here.
  • the distributed data management module can query the application component information related to the keyword in the application component information database, the distributed data management module can further return the queried application component information related to the keyword to the package management service module for the next steps.
  • Step 5 the package management service module of the electronic device 100 installs the application components including the personalized data.
  • the package management service module can determine whether the application component package in the returned application component information related to keywords is associated with personalized data ( That is, determine which application component includes dynamic information), and if so, the package management service module needs to install the application component, that is, the package management service module is responsible for installing the application component including personalized data.
  • Application components that do not include dynamic information do not need to be installed, and they still only display static information on the local device.
  • Step 6 The application component management service module of the electronic device 100 injects the successfully installed application components including dynamic information into the application component container (such as the search interface).
  • the application component management service module can inject it into the application component container, so that the application component can run in the container.
  • application components including dynamic information are injected into application component containers corresponding to the search interface.
  • Step 7 The application component including the personalization data on the remote device reads the personalization data from the package management service module.
  • the application component can start to run and read its corresponding personalized data from the package management service module.
  • the electronic device The state of the application component displayed on 100 may be consistent with the state of the application component displayed on the remote device.
  • the event that triggers the electronic device 100 to acquire application component information from the electronic device 200 may also include: the electronic device 100 detects that the user searches for keywords on the search interface.
  • the first electronic device may be the electronic device 100 (the local device), the second electronic device may be the electronic device 200 (the remote device), and the first application component may be the application component on the electronic device 200 , the installation package of the first application component may also be called the first application component package, the first content may be the static information of the first application component, the first data may be data for displaying the static information of the first application component, and the first The second content may be the dynamic information of the first application component, the second data may be data (such as personalized data) for displaying the dynamic information of the first application component, and the second application component may be an application component on the electronic device 100,
  • the first request may be a request for acquiring application component information in step S407 in FIG. 4 .
  • a schematic structural diagram of an electronic device 100 provided in an embodiment of the present application is introduced below.
  • FIG. 18 exemplarily shows the structure of an electronic device 100 provided in the embodiment of the present application.
  • the electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, a display screen 194, and a subscriber identification module (subscriber identification module, SIM) card interface 195, etc.
  • SIM subscriber identification module
  • the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, bone conduction sensor 180M, etc.
  • the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100 .
  • the electronic device 100 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components.
  • the illustrated components can be realized in hardware, software or a combination of software and hardware.
  • the processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU) wait. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.
  • application processor application processor, AP
  • modem processor graphics processing unit
  • GPU graphics processing unit
  • image signal processor image signal processor
  • ISP image signal processor
  • controller memory
  • video codec digital signal processor
  • DSP digital signal processor
  • baseband processor baseband processor
  • neural network processor neural-network processing unit, NPU
  • the controller may be the nerve center and command center of the electronic device 100 .
  • the controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.
  • a memory may also be provided in the processor 110 for storing instructions and data.
  • the memory in processor 110 is a cache memory.
  • the memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided, and the waiting time of the processor 110 is reduced, thereby improving the efficiency of the system.
  • processor 110 may include one or more interfaces.
  • the interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous transmitter (universal asynchronous receiver/transmitter, UART) interface, mobile industry processor interface (mobile industry processor interface, MIPI), general-purpose input and output (general-purpose input/output, GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and /or universal serial bus (universal serial bus, USB) interface, etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • PCM pulse code modulation
  • UART universal asynchronous transmitter
  • MIPI mobile industry processor interface
  • GPIO general-purpose input and output
  • subscriber identity module subscriber identity module
  • SIM subscriber identity module
  • USB universal serial bus
  • the I2C interface is a bidirectional synchronous serial bus, including a serial data line (serial data line, SDA) and a serial clock line (derail clock line, SCL).
  • processor 110 may include multiple sets of I2C buses.
  • the processor 110 can be respectively coupled to the touch sensor 180K, the charger, the flashlight, the camera 193 and the like through different I2C bus interfaces.
  • the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 and the touch sensor 180K communicate through the I2C bus interface to realize the touch function of the electronic device 100 .
  • the I2S interface can be used for audio communication.
  • processor 110 may include multiple sets of I2S buses.
  • the processor 110 may be coupled to the audio module 170 through an I2S bus to implement communication between the processor 110 and the audio module 170 .
  • the audio module 170 can transmit audio signals to the wireless communication module 160 through the I2S interface, so as to realize the function of answering calls through the Bluetooth headset.
  • the PCM interface can also be used for audio communication, sampling, quantizing and encoding the analog signal.
  • the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface.
  • the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to realize the function of answering calls through the Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.
  • the UART interface is a universal serial data bus used for asynchronous communication.
  • the bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication.
  • a UART interface is generally used to connect the processor 110 and the wireless communication module 160 .
  • the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to realize the Bluetooth function.
  • the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface, so as to realize the function of playing music through the Bluetooth headset.
  • the MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 .
  • MIPI interface includes camera serial interface (camera serial interface, CSI), display serial interface (display serial interface, DSI), etc.
  • the processor 110 communicates with the camera 193 through the CSI interface to realize the shooting function of the electronic device 100 .
  • the processor 110 communicates with the display screen 194 through the DSI interface to realize the display function of the electronic device 100 .
  • the GPIO interface can be configured by software.
  • the GPIO interface can be configured as a control signal or as a data signal.
  • the GPIO interface can be used to connect the processor 110 with the camera 193 , the display screen 194 , the wireless communication module 160 , the audio module 170 , the sensor module 180 and so on.
  • the GPIO interface can also be configured as an I2C interface, I2S interface, UART interface, MIPI interface, etc.
  • the USB interface 130 is an interface conforming to the USB standard specification, specifically, it can be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like.
  • the USB interface 130 can be used to connect a charger to charge the electronic device 100 , and can also be used to transmit data between the electronic device 100 and peripheral devices. It can also be used to connect headphones and play audio through them. This interface can also be used to connect other terminal devices, such as AR devices.
  • the interface connection relationship between the modules shown in the embodiment of the present application is only a schematic illustration, and does not constitute a structural limitation of the electronic device 100 .
  • the electronic device 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.
  • the charging management module 140 is configured to receive a charging input from a charger.
  • the charger may be a wireless charger or a wired charger.
  • the charging management module 140 can receive charging input from the wired charger through the USB interface 130 .
  • the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 100 . While the charging management module 140 is charging the battery 142 , it can also supply power to the electronic device 100 through the power management module 141 .
  • the power management module 141 is used for connecting the battery 142 , the charging management module 140 and the processor 110 .
  • the power management module 141 receives the input from the battery 142 and/or the charging management module 140 to provide power for the processor 110 , the internal memory 121 , the external memory, the display screen 194 , the camera 193 , and the wireless communication module 160 .
  • the power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle times, and battery health status (leakage, impedance).
  • the power management module 141 may also be disposed in the processor 110 .
  • the power management module 141 and the charging management module 140 may also be set in the same device.
  • the wireless communication function of the electronic device 100 can be realized by the antenna 1 , the antenna 2 , the mobile communication module 150 , the wireless communication module 160 , a modem processor, a baseband processor, and the like.
  • Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in electronic device 100 may be used to cover single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas.
  • Antenna 1 can be multiplexed as a diversity antenna of a wireless local area network.
  • the antenna may be used in conjunction with a tuning switch.
  • the mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the electronic device 100 .
  • the mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like.
  • the mobile communication module 150 can receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation.
  • the mobile communication module 150 can also amplify the signals modulated by the modem processor, and convert them into electromagnetic waves and radiate them through the antenna 1 .
  • at least part of the functional modules of the mobile communication module 150 may be set in the processor 110 .
  • at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be set in the same device.
  • a modem processor may include a modulator and a demodulator.
  • the modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal.
  • the demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator sends the demodulated low-frequency baseband signal to the baseband processor for processing.
  • the low-frequency baseband signal is passed to the application processor after being processed by the baseband processor.
  • the application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194 .
  • the modem processor may be a stand-alone device. In some other embodiments, the modem processor may be independent from the processor 110, and be set in the same device as the mobile communication module 150 or other functional modules.
  • the wireless communication module 160 can provide wireless local area networks (wireless local area networks, WLAN) (such as wireless fidelity (Wireless Fidelity, Wi-Fi) network), bluetooth (bluetooth, BT), global navigation satellite, etc. applied on the electronic device 100.
  • System global navigation satellite system, GNSS
  • frequency modulation frequency modulation, FM
  • near field communication technology near field communication, NFC
  • infrared technology infrared, IR
  • the wireless communication module 160 may be one or more devices integrating at least one communication processing module.
  • the wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 .
  • the wireless communication module 160 can also receive the signal to be sent from the processor 110 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.
  • the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology.
  • the wireless communication technology may include global system for mobile communications (GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC , FM, and/or IR techniques, etc.
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • code division multiple access code division multiple access
  • CDMA broadband Code division multiple access
  • WCDMA wideband code division multiple access
  • time division code division multiple access time-division code division multiple access
  • TD-SCDMA time-division code division multiple access
  • the GNSS may include a global positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a Beidou navigation satellite system (beidou navigation satellite system, BDS), a quasi-zenith satellite system (quasi -zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).
  • GPS global positioning system
  • GLONASS global navigation satellite system
  • Beidou navigation satellite system beidou navigation satellite system
  • BDS Beidou navigation satellite system
  • QZSS quasi-zenith satellite system
  • SBAS satellite based augmentation systems
  • the electronic device 100 realizes the display function through the GPU, the display screen 194 , and the application processor.
  • the GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering.
  • Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.
  • the display screen 194 is used to display images, videos and the like.
  • the display screen 194 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 or an active matrix organic light emitting diode (active-matrix organic light emitting diode, AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diodes (quantum dot light emitting diodes, QLED), etc.
  • the electronic device 100 may include 1 or N display screens 194 , where N is a positive integer greater than 1.
  • the electronic device 100 can realize the shooting function through the ISP, the camera 193 , the video codec, the GPU, the display screen 194 and the application processor.
  • the ISP is used for processing the data fed back by the camera 193 .
  • the light is transmitted to the photosensitive element of the camera through the lens, and the light signal is converted into an electrical signal, and the photosensitive element of the camera transmits the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye.
  • ISP can also perform algorithm optimization on image noise, brightness, etc.
  • ISP can also optimize the exposure, color temperature and other parameters of the shooting scene.
  • the ISP may be located in the camera 193 .
  • Camera 193 is used to capture still images or video.
  • the object generates an optical image through the lens and projects it to the photosensitive element.
  • the photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor.
  • CMOS complementary metal-oxide-semiconductor
  • the photosensitive element converts the light signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal.
  • the ISP outputs the digital image signal to the DSP for processing.
  • DSP converts digital image signals into standard RGB, YUV and other image signals.
  • the electronic device 100 may include 1 or N cameras 193 , where N is a positive integer greater than 1.
  • Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the energy of the frequency point.
  • Video codecs are used to compress or decompress digital video.
  • the electronic device 100 may support one or more video codecs.
  • the electronic device 100 can play or record videos in various encoding formats, for example: moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4 and so on.
  • MPEG moving picture experts group
  • the NPU is a neural-network (NN) computing processor.
  • NN neural-network
  • Applications such as intelligent cognition of the electronic device 100 can be realized through the NPU, such as image recognition, face recognition, speech recognition, text understanding, and the like.
  • the external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, so as to expand the storage capacity of the electronic device 100.
  • the external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. Such as saving music, video and other files in the external memory card.
  • the internal memory 121 may be used to store computer-executable program codes including instructions.
  • the processor 110 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the internal memory 121 .
  • the internal memory 121 may include an area for storing programs and an area for storing data.
  • the stored program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like.
  • the storage data area can store data created during the use of the electronic device 100 (such as audio data, phonebook, etc.) and the like.
  • the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like.
  • the electronic device 100 can implement audio functions through the audio module 170 , the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playback, recording, etc.
  • the audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal.
  • the audio module 170 may also be used to encode and decode audio signals.
  • the audio module 170 may be set in the processor 110 , or some functional modules of the audio module 170 may be set in the processor 110 .
  • Speaker 170A also referred to as a "horn" is used to convert audio electrical signals into sound signals.
  • Electronic device 100 can listen to music through speaker 170A, or listen to hands-free calls.
  • Receiver 170B also called “earpiece” is used to convert audio electrical signals into sound signals.
  • the receiver 170B can be placed close to the human ear to receive the voice.
  • the microphone 170C also called “microphone” or “microphone” is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can put his mouth close to the microphone 170C to make a sound, and input the sound signal to the microphone 170C.
  • the electronic device 100 may be provided with at least one microphone 170C. In some other embodiments, the electronic device 100 may be provided with two microphones 170C, which may also implement a noise reduction function in addition to collecting sound signals. In some other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and realize directional recording functions, etc.
  • the earphone interface 170D is used for connecting wired earphones.
  • the earphone interface 170D may be a USB interface 130, or a 3.5mm open mobile terminal platform (open mobile terminal platform, OMTP) standard interface, or a cellular telecommunications industry association of the USA (CTIA) standard interface.
  • OMTP open mobile terminal platform
  • CTIA cellular telecommunications industry association of the USA
  • the pressure sensor 180A is used to sense the pressure signal and convert the pressure signal into an electrical signal.
  • the pressure sensor 180A may be located on the display screen 194 .
  • pressure sensors 180A such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors.
  • a capacitive pressure sensor may be comprised of at least two parallel plates with conductive material.
  • the electronic device 100 determines the intensity of pressure according to the change in capacitance.
  • the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A.
  • the electronic device 100 may also calculate the touched position according to the detection signal of the pressure sensor 180A.
  • touch operations acting on the same touch position but with different touch operation intensities may correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view short messages is executed. When a touch operation whose intensity is greater than or equal to the first pressure threshold acts on the icon of the short message application, the instruction of creating a new short message is executed.
  • the gyro sensor 180B can be used to determine the motion posture of the electronic device 100 .
  • the angular velocity of the electronic device 100 around three axes may be determined by the gyro sensor 180B.
  • the gyro sensor 180B can be used for image stabilization. Exemplarily, when the shutter is pressed, the gyro sensor 180B detects the shaking angle of the electronic device 100, calculates the distance that the lens module needs to compensate according to the angle, and allows the lens to counteract the shaking of the electronic device 100 through reverse movement to achieve anti-shake.
  • the gyro sensor 180B can also be used for navigation and somatosensory game scenes.
  • the air pressure sensor 180C is used to measure air pressure.
  • the electronic device 100 calculates the altitude based on the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.
  • the magnetic sensor 180D includes a Hall sensor.
  • the electronic device 100 may use the magnetic sensor 180D to detect the opening and closing of the flip leather case.
  • the electronic device 100 when the electronic device 100 is a clamshell machine, the electronic device 100 can detect opening and closing of the clamshell according to the magnetic sensor 180D.
  • features such as automatic unlocking of the flip cover are set.
  • the acceleration sensor 180E can detect the acceleration of the electronic device 100 in various directions (generally three axes).
  • the magnitude and direction of gravity can be detected when the electronic device 100 is stationary. It can also be used to identify the posture of the electronic device 100, and can be applied to applications such as horizontal and vertical screen switching, pedometers, etc.
  • the distance sensor 180F is used to measure the distance.
  • the electronic device 100 may measure the distance by infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 may use the distance sensor 180F for distance measurement to achieve fast focusing.
  • Proximity light sensor 180G may include, for example, light emitting diodes (LEDs) and light detectors, such as photodiodes.
  • the light emitting diodes may be infrared light emitting diodes.
  • the electronic device 100 emits infrared light through the light emitting diode.
  • Electronic device 100 uses photodiodes to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it may be determined that there is an object near the electronic device 100 . When insufficient reflected light is detected, the electronic device 100 may determine that there is no object near the electronic device 100 .
  • the electronic device 100 can use the proximity light sensor 180G to detect that the user is holding the electronic device 100 close to the ear to make a call, so as to automatically turn off the screen to save power.
  • the proximity light sensor 180G can also be used in leather case mode, automatic unlock and lock screen in pocket mode.
  • the ambient light sensor 180L is used for sensing ambient light brightness.
  • the electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness.
  • the ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures.
  • the ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in the pocket, so as to prevent accidental touch.
  • the fingerprint sensor 180H is used to collect fingerprints.
  • the electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access to application locks, take pictures with fingerprints, answer incoming calls with fingerprints, and the like.
  • the temperature sensor 180J is used to detect temperature.
  • the electronic device 100 uses the temperature detected by the temperature sensor 180J to implement a temperature treatment strategy. For example, when the temperature reported by the temperature sensor 180J exceeds the threshold, the electronic device 100 may reduce the performance of the processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection.
  • the electronic device 100 when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to avoid abnormal shutdown of the electronic device 100 caused by the low temperature.
  • the electronic device 100 boosts the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.
  • Touch sensor 180K also known as "touch panel”.
  • the touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a “touch screen”.
  • the touch sensor 180K is used to detect a touch operation on or near it.
  • the touch sensor can pass 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 the display screen 194 .
  • the touch sensor 180K may also be disposed on the surface of the electronic device 100 , which is different from the position of the display screen 194 .
  • the bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire the vibration signal of the vibrating bone mass of the human voice. The bone conduction sensor 180M can also contact the human pulse and receive the blood pressure beating signal. In some embodiments, the bone conduction sensor 180M can also be disposed in the earphone, combined into a bone conduction earphone.
  • the audio module 170 can analyze the voice signal based on the vibration signal of the vibrating bone mass of the vocal part acquired by the bone conduction sensor 180M, so as to realize the voice function.
  • the application processor can analyze the heart rate information based on the blood pressure beating signal acquired by the bone conduction sensor 180M, so as to realize the heart rate detection function.
  • the keys 190 include a power key, a volume key and the like.
  • the key 190 may be a mechanical key. It can also be a touch button.
  • the electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100 .
  • the motor 191 can generate a vibrating reminder.
  • the motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback.
  • touch operations applied to different applications may correspond to different vibration feedback effects.
  • the motor 191 may also correspond to different vibration feedback effects for touch operations acting on different areas of the display screen 194 .
  • Different application scenarios for example: time reminder, receiving information, alarm clock, games, etc.
  • the touch vibration feedback effect can also support customization.
  • the indicator 192 can be an indicator light, and can be used to indicate charging status, power change, and can also be used to indicate messages, missed calls, notifications, and the like.
  • the SIM card interface 195 is used for connecting a SIM card.
  • the SIM card can be connected and separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195 .
  • the electronic device 100 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1.
  • SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card etc. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards may be the same or different.
  • the SIM card interface 195 is also compatible with different types of SIM cards.
  • the SIM card interface 195 is also compatible with external memory cards.
  • the electronic device 100 interacts with the network through the SIM card to implement functions such as calling and data communication.
  • the electronic device 100 adopts an eSIM, that is, an embedded SIM card.
  • the eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100 .
  • the electronic device 100 shown in FIG. 18 is merely an example, and that the electronic device 100 may have more or fewer components than those shown in FIG. 18, two or more components may be combined, or Different component configurations are possible.
  • the various components shown in Figure 18 may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.
  • the structure of the electronic device 200 may be the same as or similar to that of the electronic device 100.
  • the relevant content about the structure of the electronic device 200 please refer to the related text description of the structure of the electronic device 100 shown in FIG. 18 , which will not be repeated here.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part 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 the computer, the processes or functions according to the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, DSL) or wireless (eg, infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (solid state disk, SSD)), etc.
  • the processes can be completed by computer programs to instruct related hardware.
  • the programs can be stored in computer-readable storage media.
  • When the programs are executed may include the processes of the foregoing method embodiments.
  • the aforementioned storage medium includes: ROM or random access memory RAM, magnetic disk or optical disk, and other various media that can store program codes.

Abstract

本申请公开了一种应用组件管理方法及相关设备，电子设备(即本端设备)可以获取这一个或多个远端设备提供的应用组件信息，并可以基于该应用组件信息来显示和使用这一个或多个远端设备提供的应用组件，从而可以解决在本端设备上无法查看跨设备应用组件的问题，提高用户体验。

Description

应用组件管理方法及相关设备
本申请要求于2022年01月28日提交中国国家知识产权局、申请号为202210109589.3、申请名称为“应用组件管理方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及终端技术领域，尤其涉及一种应用组件管理方法及相关设备。
背景技术
随着智能电子设备的普及和互联网技术的发展，智能手机、笔记本电脑、平板电脑等电子设备已经成为人们日常生活中不可或缺的产品。为满足用户日益增长的使用需求，这些电子设备上安装的应用程序(Application,APP)的种类和数量也日益增多。通常，这些应用程序的入口均以桌面图标的形式显示在电子设备的桌面上。除了桌面图标，当前一些电子设备生产厂商还提供了桌面应用组件功能，这些桌面应用组件不仅可以作为应用程序的入口，而且它相比于传统的应用程序来说，具备更清晰的视觉，更自由的布局，更灵活的尺寸，更丰富的内容、支持个性化定制等特征，可以将应用程序的内容轻量、快速、高效呈现，支持用户快捷操作，实现服务一步直达。
然而，目前应用组件的应用场景较为受限，用户体验差。
发明内容
本申请实施例提供了一种应用组件管理方法及相关设备，可以解决在本端设备上无法查看跨设备应用组件的问题，提高用户体验。
第一方面，本申请实施例提供了一种应用组件显示方法，应用于第一电子设备，该方法包括：第一电子设备接收来自第二电子设备的应用组件信息，应用组件信息包括第一应用组件的信息，第一应用组件是所述第二电子设备的应用组件；第一电子设备基于第一应用组件的信息显示第一应用组件。其中，第一应用组件的信息可以用于显示第一应用组件，可以包括第一应用组件的组件标识(例如应用组件的包名和模块名)、第一应用组件的描述信息(例如应用组件的预览图、标题、尺寸等信息)等。
本申请实施例通过提供一种应用组件显示方法，电子设备(即本端设备)可以获取一个或多个远端设备提供的应用组件信息，并可以基于该应用组件信息来显示这一个或多个远端设备提供的应用组件，从而可以解决在本端设备上无法查看跨设备应用组件的问题，提高用户体验。
在一种可能的实现方式中，第一应用组件的信息包括第一应用组件的安装包，第一电子设备基于第一应用组件的信息显示第一应用组件，具体包括：第一电子设备基于第一应用组件的安装包显示第一应用组件；其中，第一应用组件上显示有第一内容，第一内容是第一电子设备基于第一数据生成的，第一数据是第一电子设备在第一应用组件的安装包中获取的。
这样，电子设备可以静态显示第一应用组件，即电子设备可以显示第一应用组件的静态 信息(即第一内容)。
在一种可能的实现方式中，第一应用组件的信息包括第一应用组件的安装包和第二数据，第一电子设备基于第一应用组件的信息显示第一应用组件，具体包括：第一电子设备基于第一应用组件的安装包和第二数据安装并显示第一应用组件；其中，第一应用组件上显示有第二内容，第二内容是第一电子设备基于第二数据生成的，第二数据是所述第二电子设备在运行所述第一应用组件时生成的。
这样，电子设备可以动态显示第一应用组件，即电子设备可以显示第一应用组件的动态信息(即第二内容)。
在一种可能的实现方式中，在第一电子设备基于第一应用组件的信息显示第一应用组件之后，该方法还包括：第一电子设备检测到用户将第一应用组件添加到桌面的操作，第一电子设备在桌面显示第一应用组件。
这样，电子设备可以将第一应用组件添加到桌面显示，用户在桌面就可以查看第一应用组件。
在一种可能的实现方式中，在第一电子设备基于第一应用组件的信息显示第一应用组件之前，该方法还包括：第一电子设备检测到用户打开应用组件管理界面的操作，响应于该操作，第一电子设备显示应用组件管理界面，其中，应用组件管理界面包括标识选项，标识选项包括第二电子设备的标识选项；第一电子设备检测到用户针对第二电子设备的标识选项的操作；第一电子设备基于第一应用组件的信息显示第一应用组件，具体包括：响应于该操作，第一电子设备在应用组件管理界面基于第一应用组件的信息显示第一应用组件。其中，应用组件管理界面上显示第二电子设备的应用组件，第二电子设备的应用组件包括第一应用组件。
这样，电子设备可以在用户点击第二电子设备的标识选项之后，显示第二电子设备上的应用组件，供用户查看。
在一种可能的实现方式中，在第一电子设备基于第一应用组件的信息显示第一应用组件之前，该方法还包括：第一电子设备检测到用户打开应用组件管理界面的操作，响应于该操作，第一电子设备显示应用组件管理界面；第一电子设备基于第一应用组件的信息显示第一应用组件，具体包括：第一电子设备在应用组件管理界面基于第一应用组件的信息显示第一应用组件；其中，应用组件管理界面还显示有第二应用组件，第二应用组件是第一电子设备的应用组件。
这样，电子设备在同一个界面既可以显示本机的应用组件，也可以显示其他电子设备的应用组件。
在一种可能的实现方式中，在第一电子设备基于第一应用组件的信息显示第一应用组件之前，该方法还包括：第一电子设备检测到用户在搜索界面上搜索关键字的操作，响应于该操作，第一电子设备获取与关键字相关的应用组件信息，与关键字相关的应用组件信息包括第一应用组件的信息；第一电子设备基于第一应用组件的信息显示所述第一应用组件，具体包括：第一电子设备在搜索界面基于第一应用组件的信息显示第一应用组件。
这样，电子设备在检测到用户在搜索界面搜索关键字的操作后，可以显示出与该关键字 相关的应用组件。
在一种可能的实现方式中，在第一电子设备接收来自第二电子设备的应用组件信息之前，该方法还包括：第一电子设备检测到预设条件被触发，预设条件包括以下任意一项：用户打开应用组件管理界面的操作、用户在搜索界面上搜索关键字的操作、开机、重启、锁屏解锁、系统更新；响应于预设条件被触发，第一电子设备向第二电子设备发送第一请求，第一请求用于指示第二电子设备向第一电子设备发送应用组件信息。
这样，电子设备可以在预设条件被触发后向其他电子设备获取应用组件信息，以便用户可以查看到其他电子设备上的应用组件。
在一种可能的实现方式中，第一电子设备在第一应用组件上显示第二电子设备的标识。
这样，便于用户分辨出第一应用组件是哪个电子设备上的。
在一种可能的实现方式中，在第一电子设备接收来自第二电子设备的应用组件信息之前，该方法还包括：第一电子设备与第二电子设备建立通信连接，并确认第二电子设备为可信设备。
这样，第一电子设备可以基于上述通信连接获取到第二电子设备的应用组件信息，并且确认第二电子设备为可信设备，可以保证安全性。
第二方面，本申请实施例提供了一种应用组件显示方法，应用于第二电子设备，该方法包括：第二电子设备接收来自第一电子设备的第一请求，第一请求用于指示第二电子设备向第一电子设备发送应用组件信息，其中，应用组件信息包括第一应用组件的信息，第一应用组件是第二电子设备的应用组件；第二电子设备向第一电子设备发送应用组件信息。
在一种可能的实现方式中，第一应用组件的信息包括第一应用组件的安装包。
在一种可能的实现方式中，第一应用组件的信息还包括第二数据，在第二电子设备向第一电子设备发送应用组件信息之前，该方法还包括：第二电子设备运行第一应用组件，并生成第二数据。
在一种可能的实现方式中，在第二电子设备接收来自第一电子设备的第一请求之前，该方法还包括：第二电子设备与第一电子设备建立通信连接，并确认第一电子设备为可信设备。
第三方面，本申请提供了一种通信系统，该通信系统包括：第一电子设备和第二电子设备；第二电子设备用于向第一电子设备发送应用组件信息；第一电子设备用于接收应用组件信息，应用组件信息包括第一应用组件的信息，第一应用组件是第二电子设备的应用组件；第一电子设备还用于基于第一应用组件的信息显示第一应用组件。
第四方面，本申请实施例提供了一种电子设备，该电子设备包括一个或多个处理器和一个或多个存储器；其中，一个或多个存储器与一个或多个处理器耦合，一个或多个存储器用于存储计算机程序代码，计算机程序代码包括计算机指令，当一个或多个处理器执行计算机 指令时，使得电子设备执行上述第一方面或第二方面任一项可能的实现方式中所述的方法。
第五方面，本申请实施例提供了一种计算机存储介质，该计算机存储介质存储有计算机程序，计算机程序包括程序指令，当程序指令在电子设备上运行时，使得电子设备执行上述第一方面或第二方面任一项可能的实现方式中所述的方法。
第六方面，本申请实施例提供了一种计算机程序产品，当计算机程序产品在计算机上运行时，使得计算机执行上述第一方面或第二方面任一项可能的实现方式中所述的方法。
附图说明
图1是本申请实施例提供的一种本端设备在桌面显示应用组件的示意图；
图2是本申请实施例提供的一种通信系统的示意图；
图3A是本申请实施例提供的一种本端设备的软件架构示意图；
图3B是本申请实施例提供的另一种本端设备的软件架构示意图；
图4是本申请实施例提供的一种应用组件管理方法的流程示意图；
图5是本申请实施例提供的一种本端设备与远端设备建立可信连接过程中内部各个模块之间可能的协作方式示意图；
图6是本申请实施例提供的一种本端设备的桌面示意图；
图7是本申请实施例提供的一种远端设备在应用组件管理界面显示应用组件的示意图；
图8是本申请实施例提供的一种本端设备获取并保存远端设备应用组件信息过程中内部各个模块之间可能的协作方式示意图；
图9A是本申请实施例提供的一种本端设备在应用组件管理界面显示本端设备应用组件的示意图；
图9B是本申请实施例提供的一种本端设备在应用组件管理界面静态显示远端设备应用组件的示意图；
图9C是本申请实施例提供的另一种本端设备在应用组件管理界面静态显示远端设备应用组件的示意图；
图10是本申请实施例提供的一种本端设备在应用组件管理界面静态显示远端设备应用组件过程中内部各个模块之间可能的协作方式示意图；
图11A是本申请实施例提供的一种远端设备在桌面显示应用组件的示意图；
图11B是本申请实施例提供的一种本端设备在应用组件管理界面动态显示远端设备应用组件的示意图；
图11C是本申请实施例提供的另一种本端设备在应用组件管理界面动态显示远端设备应用组件的示意图；
图12A-图12B是本申请实施例提供的一种将远端设备应用组件添加到本端设备的桌面上进行显示的用户界面示意图；
图13是本申请实施例提供的一种本端设备在应用组件管理界面动态显示远端设备应用组件过程中内部各个模块之间可能的协作方式示意图；
图14A是本申请实施例提供的一种本端设备的搜索界面示意图；
图14B是本申请实施例提供的一种本端设备在搜索界面自动推荐并静态显示远端设备应 用组件的示意图；
图15是本申请实施例提供的一种本端设备在搜索界面静态显示远端设备应用组件过程中内部各个模块之间可能的协作方式示意图；
图16是本申请实施例提供的一种本端设备在搜索界面自动推荐并动态显示远端设备应用组件的示意图；
图17是本申请实施例提供的一种本端设备在搜索界面动态显示远端设备应用组件过程中内部各个模块之间可能的协作方式示意图；
图18是本申请实施例提供的一种本端设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。其中，在本申请实施例的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；文本中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，另外，在本申请实施例的描述中，“多个”是指两个或多于两个。
应当理解，本申请的说明书和权利要求书及附图中的术语“第一”、“第二”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本申请中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是，本申请所描述的实施例可以与其它实施例相结合。
本申请以下实施例中的术语“用户界面(user interface，UI)”，是应用程序或操作系统与用户之间进行交互和信息交换的介质接口，它实现信息的内部形式与用户可以接受形式之间的转换。用户界面是通过java、可扩展标记语言(extensible markup language，XML)等特定计算机语言编写的源代码，界面源代码在电子设备上经过解析，渲染，最终呈现为用户可以识别的内容。用户界面常用的表现形式是图形用户界面(graphic user interface，GUI)，是指采用图形方式显示的与计算机操作相关的用户界面。它可以是在电子设备的显示屏中显示的文本、图标、按钮、菜单、选项卡、文本框、对话框、状态栏、导航栏、Widget等可视的界面元素。
为便于理解，首先对本申请实施例中涉及的“应用组件”这一概念进行说明。
应用组件(Application Widget,App Widget)，也可以称为卡片或服务卡片或服务组件(Service Widget)或应用微件或应用小组件，是电子设备的业务模块A(业务端，例如某个应用程序)在模块B(宿主端，例如桌面)界面上提供的一种小窗口或小部件。应用组件通常用于将应用程序(Application)的重要信息展示在电子设备的桌面上，实现应用程序的某个业务特性，用户可以通过快捷手势使用应用组件，以达到服务一步直达、减少层级跳转的目的。
应用组件是一种界面展示形式，通常是由第三方(例如应用程序的开发者)独立定制，即独立于该应用组件对应的应用程序定制。其中，应用组件可用于嵌入到其他应用程序中作为其界面的一部分显示，例如可以允许使用方(如桌面应用程序)将应用组件嵌入到自己的界面(如嵌入至安卓操作系统的activity组件)中进行显示。也就是说，对于任一应用程序，该应用程序对应的应用组件与该应用程序是相互独立的，即该应用程序对应的应用组件不是该应用程序的应用界面，但该应用程序对应的应用组件可以与该应用程序进行数据交互，以将该应用程序的重要信息或操作等更新或添加到应用组件，从而达到服务直达，减少体验层级的目的。例如，基于安卓操作系统设置的应用组件可以称为进行中卡片(ongoing card)，基于鸿蒙操作系统设置的应用组件可以称为服务卡片，如form ability(FA)。
图1示例性示出了电子设备100提供的显示在用户界面110(即桌面)中的一个应用组件，通常应用组件可以显示有一种或多种信息，从图1可以看出，应用组件111显示有三种信息：位置信息(例如南京栖霞区)、温度信息(例如22度)、运动步数信息(例如6888步)。这样，通过将该应用组件显示在桌面上，用户可以直接查看到上述显示在该应用组件中的信息，无需进入提供该应用组件的应用程序来查看这些信息，方便快捷。同时，用户还可以直接点击该应用组件进入提供该应用组件的应用程序来查看更多详细信息或执行其他任务。
应用组件只是本申请实施例中所使用的一个词语，其代表的含义在本申请实施例中已经记载，其名称并不能对本申请实施例构成任何限制。
目前，应用组件通常只能在本端设备上使用，用户如果想要在其他远端设备上使用这些应用组件，则需要手动到远端设备上先安装提供这些应用组件的应用程序，然后通过桌面提供的窗口小工具选择对应的应用组件来添加到桌面上进行显示，最后可能还需要根据用户需求手动设置该应用组件的配置(例如设置天气应用组件的显示地点、设置日历应用组件的显示国家等)，操作繁琐，灵活性差，用户不能像查看、使用本端设备的应用组件那样来在本端设备上查看、使用跨设备的应用组件，缺少应用组件跨设备查看、使用的体验，从而导致应用组件的应用场景受限，用户体验差。
本申请实施例提供了一种应用组件管理方法，电子设备(即本端设备)可以与一个或多个远端设备建立可信连接，通过该可信连接，电子设备可以获取这一个或多个远端设备提供的应用组件信息列表，并可以基于该应用组件信息列表来显示和使用这一个或多个远端设备提供的应用组件，从而可以解决在本端设备上无法查看、使用跨设备应用组件的问题，提高用户体验。
本申请实施例提供的应用组件管理方法，主要包括以下四种方案：
方案一(电子设备100在检测到用户在桌面查看应用组件的场景下静态显示应用组件)：
电子设备100(即本端设备)可以通过与一个或多个远端设备建立的可信连接获取这一个或多个远端设备提供的应用组件的静态信息，在检测到用户在桌面查看某个远端设备提供的应用组件的场景下，电子设备100可以基于上述静态信息来静态显示该远端设备提供的应用组件。
方案二(电子设备100在检测到用户在桌面查看应用组件的场景下动态显示应用组件)：
电子设备100(即本端设备)可以通过与一个或多个远端设备建立的可信连接获取这一个或多个远端设备提供的应用组件的静态信息和动态信息(也可以称为个性化数据)，在检测到用户在桌面查看某个远端设备提供的应用组件的场景下，电子设备100可以基于上述静态信息和动态信息来动态显示该远端设备提供的应用组件。
方案三：(电子设备100在检测到与一个或多个应用组件相关联的特定场景下静态显示应用组件)：
电子设备100(即本端设备)可以通过与一个或多个远端设备建立的可信连接获取这一个或多个远端设备提供的应用组件的静态信息，在检测到与一个或多个应用组件相关联的特定场景(例如用户输入与一个或多个应用组件相关联的关键字进行搜索的场景等)下，电子设备100可以基于上述静态信息自动推荐并静态显示与上述特定场景相关联的应用组件(包括本端设备的应用组件，和/或，与本端设备建立可信连接的远端设备的应用组件)。
方案四：(电子设备100在检测到与一个或多个应用组件相关联的特定场景下动态显示应用组件)：
电子设备100(即本端设备)可以通过与一个或多个远端设备建立的可信连接获取这一个或多个远端设备提供的应用组件的静态信息和动态信息(也可以称为个性化数据)，在检测到与一个或多个应用组件相关联的特定场景(例如用户输入与一个或多个应用组件相关联的关键字进行搜索的场景等)下，电子设备100可以基于上述静态信息和动态信息自动推荐并动态显示与上述特定场景相关联的应用组件(包括本端设备的应用组件，和/或，与本端设备建立可信连接的远端设备的应用组件)。
后续实施例中会详细说明上述四种方案，这里先不展开。
下面，首先介绍本申请实施例提供的一种通信系统。
图2示例性示出了本申请实施例提供的一种通信系统。
如图2所示，该通信系统可以包括：多个电子设备。该通信系统也可以称为分布式系统。
该通信系统中包括的多个电子设备均为智能终端设备，可以为各种类型，本申请实施例对该多个电子设备的具体类型不作限制。例如，该多个电子设备可以包括手机，还可以包括平板电脑、桌面型计算机、膝上型计算机、手持计算机、笔记本电脑、智慧屏、可穿戴式设备、增强现实(Augmented Reality,AR)设备、虚拟现实(Virtual Reality,VR)设备、人工智能(Artificial Intelligence,AI)设备、车机、智能耳机，游戏机，还可以包括物联网(Internetof Things,IOT)设备，智能家居设备如智能热水器、智能灯具、智能空调，或智能运动设备器械、智能医疗器械如血压机等。
该通信系统中的多个电子设备之间可以通过登录相同的账号进行连接。例如，多个电子设备可以登录同一华为账号，并通过服务器来远程连接并通信。账号可以是手机号，电子邮箱号，自定义的用户名，APP服务器分配的用户名，电子设备中某个APP中的登录使用的用户名等。
该通信系统中的多个电子设备也可以登录不同账号，但通过绑定的方式进行连接。一个电子设备登录账号后，可以在设备管理应用中，绑定登录不同账号或未登录的其他电子设备，之后这些电子设备之间可以通过该设备管理应用通信。
该通信系统中的多个电子设备还可以通过扫描二维码、近场通信(near field communication，NFC)碰一碰、搜索蓝牙设备等方式建立连接，这里不做限制。
总的来说，该通信系统中的多个电子设备之间建立的通信连接可以包括但不限于：有线连接、无线连接例如蓝牙(bluetooth，BT)连接、无线局域网(wireless local area networks，WLAN)例如无线保真点对点(wireless fidelity point to point，Wi-Fi P2P)连接、近距离无线通信(near field communication，NFC)连接，红外技术(infrared，IR)连接，以及远程连接(例如通过服务器建立的连接)等等。
此外，该通信系统中的多个电子设备也可以结合上述任意几种方式来连接并通信，本申请实施例对此不做限制。也即是说，该通信系统中的各个电子设备可以按照一定的通信协议和组网策略组建网络(即组网)，使得该通信系统中的各个电子设备之间可以互相通信。
该通信系统中的多个电子设备可以配置不同的软件操作系统(OperatingSystem,OS)，包括但不限于
Figure PCTCN2023070583-appb-000001
等等。其中，
Figure PCTCN2023070583-appb-000002
为华为的鸿蒙系统。该多个电子设备可以都配置相同的软件操作系统，例如可以均配置
Figure PCTCN2023070583-appb-000003
在多个电子设备的软件操作系统均为
Figure PCTCN2023070583-appb-000004
时，该通信系统可以看作一个超级终端。
下面介绍本申请实施例提供的电子设备100的两种软件架构示意图。
图3A示例性示出了本申请实施例提供的应用组件显示过程涉及的一种电子设备100的软件架构(以Android系统为例)。
如图3A所示，电子设备100可以包括应用层和框架层。
应用层可以包括一系列应用程序，如图3A所示，应用层可以包括桌面(宿主端)、除桌面之外的其他业务应用(业务端)。
桌面(宿主端)可以包括应用组件宿主模块(App Widget Host)、应用组件宿主视图模块(App Widget Host View)。
其中，应用组件宿主模块是桌面(宿主端)提供的一个接口，可以用于支持应用组件嵌入到桌面(宿主端)，并可以保存应用组件的界面逻辑信息；应用组件宿主视图模块中包括远程视图模块(RemoteView)，应用组件宿主视图模块可以用于基于远程视图模块中关于应用组件的描述来显示应用组件，远程视图模块可以用于获取在应用组件宿主模块中保存的应用组件的界面逻辑信息，以供应用组件宿主视图模块来显示应用组件。
除桌面之外的其他业务应用(业务端)可以包括服务模块(Service)、应用组件提供器(RemoteViewProvider)、远程视图模块(RemoteView)以及AndroidManifest.xml文件等。
其中，服务模块可以用于提供该应用所需的相关服务，应用组件提供器是一个广播接收器(BroadcastReceiver)，可以用于接收更新应用组件界面的广播消息，远程视图模块可以用于描述应用组件的视图信息，例如更新应用组件界面所需的各种信息等，AndroidManifest.xml文件中包括该应用的配置信息，可以用于描述该应用中的各个模块(例如服务模块、应用组件提供器、远程视图模块等)。
框架层可以为应用层的应用程序提供应用编程接口(application programming interface，API)和编程框架。框架层包括一些预先定义的函数。
如图3A所示，框架层可以包括应用组件管理模块(App Widget Manager)、应用组件服 务模块(App Widget Service)等。
其中，应用组件管理模块可以用于为业务端和宿主端提供应用组件数据和事件交互的通道，应用组件服务模块可以用于负责应用组件的管理工作(例如加载应用组件、删除应用组件、处理定时事件等)。
继续参阅图3A，在应用组件界面需要更新时，宿主端的应用组件宿主视图模块会以广播消息的形式向业务端发送应用组件界面更新事件，业务端会通过服务模块创建一个服务并把更新界面通知通过应用组件提供器发送至远程视图模块，远程视图模块会生成更新界面所需的各种信息，并把更新界面所需的各种信息发送至框架层的应用组件管理模块，应用组件管理模块会调用应用组件服务模块提供的一些方法来把更新界面所需的各种信息发送至宿主端的应用组件宿主模块，应用组件宿主模块会基于更新界面所需的各种信息来更新应用组件并通过应用组件宿主视图模块来将更新后的应用组件界面显示在宿主端。
可以看出，上述框架层中的应用组件管理模块为宿主端和业务端提供了应用组件数据和事件交互的通道，通过将应用组件嵌入到宿主端提供的容器(Container)中，完成业务端数据在宿主端的自主显示和事件处理过程。其中，容器是一种软件程序，可以为应用组件提供运行环境，并管理应用组件的生命周期。
但是，目前应用组件管理模块只实现了本端设备的应用组件的管理，并没有实现跨设备应用组件的管理，而且，应用组件的界面逻辑信息和事件处理过程所需模块都打包在了应用包中，并没有与应用包分离。
基于上述问题，本申请实施例提供了另一种电子设备100的软件架构。
图3B示例性示出了本申请实施例提供的应用组件管理方法涉及的一种电子设备100的软件架构。
如图3B所示，电子设备100可以包括应用层、框架层、系统服务层、内核及硬件平台层、网络通信硬件层。
应用层可以包括一系列应用程序，如图3B所示，应用层可以包括桌面(宿主端)、除桌面之外的其他业务应用(业务端)。
桌面(宿主端)可以提供注入应用组件的容器，显示应用组件，支持应用组件嵌入并在桌面运行。
与图3A不同的是，除桌面之外的其他业务应用(业务端)中可以包括应用组件包(也可以称为应用组件的安装包)和应用包(也可以称为应用程序的安装包)，也即是说，将应用组件包与应用包分离开来，应用组件包中只包含应用组件所涉及的业务逻辑和服务，这样，应用组件包可以从应用包中解耦，轻型化，并可以独立安装，也即是说，即使电子设备上未安装应用组件对应的应用，该电子设备也可以安装该应用组件。
由于应用组件不是一个单独的用户界面程序，因此，它必须嵌入在某个程序(即宿主端)中才可以运行，在本申请实施例中，应用组件的宿主端可以为桌面，即应用组件可以嵌入到桌面来运行。
可以理解的是，本申请实施例仅仅以桌面作为应用组件的宿主端为例，应用组件的宿主端还可以是其他应用程序，本申请实施例对此不作限定。
框架层可以为应用层的应用程序提供应用编程接口(application programming interface，API)和编程框架。框架层包括一些预先定义的函数。
如图3B所示，框架层可以包括应用组件管理服务模块和包管理服务模块(PackageManagerService,PMS)。
应用组件管理服务模块可以用于管理本端设备的应用组件信息列表以及与本端设备建立可信连接的一个或多个远端设备的可用的应用组件信息列表等，可以被桌面(宿主端)调用；
包管理服务模块可以用于管理各种应用组件包和应用包，可以提供包安装、包注册、包信息管理等能力。
系统服务层是系统的核心能力集合，系统服务层可以通过框架层对应用层的应用程序提供服务。
如图3B所示，系统服务层可以包括设备管理模块、分布式数据管理模块、应用组件信息数据库、数据通信软总线、安全验证管理模块。
设备管理模块可以用于管理本端设备的设备信息以及与本端设备建立可信连接的一个或多个远端设备的设备信息等，并可以提供相关的API给上层模块。
分布式数据管理模块可以提供跨设备数据同步能力和服务的API等，为上层业务应用同步业务数据。
应用组件信息数据库可以用于存储本端设备以及与本端设备建立可信连接的一个或多个远端设备的应用组件包和其对应的个性化数据。
数据通信软总线可以基于网络连接信息来提供设备注册、设备发现、设备连接、设备通信等能力。
安全验证管理模块可以基于设备证书、账号、签名等信息来验证远端设备的合法性，确保该远端设备为可信设备，并可以提供相关API，还可以对应用组件包信息进行可信验证。
如图3B所示，内核及硬件平台层可以包括硬件抽象层(HardwareAbstraction Layer)、内核以及驱动等。
硬件抽象层运行于用户空间(UserSpace)，对内核层驱动进行封装，向上层提供调用接口。
内核层是硬件和软件之间的层。内核层可以包括显示驱动，摄像头驱动，音频驱动，传感器驱动、蓝牙驱动等。在一些实施例中，内核及硬件平台层可以包括内核抽象层(kernel abstract layer，KAL)和驱动子系统。KAL下包括多个内核，如Linux系统的内核Linux Kernel、轻量级物联网系统内核LiteOS等。驱动子系统则可以包括硬件驱动框架(Hardware Driver Foundation，HDF)。硬件驱动框架能够提供统一外设访问能力和驱动开发、管理框架。多内核的内核层可以根据系统的需求选择相应的内核进行处理。
如图3B所示，网络通信硬件层可以包括Wi-Fi模块、蓝牙模块等硬件，用于实现不同设备之间的通信。
继续参阅图3B，本申请实施例提供的应用组件管理方法涉及的上述各个模块之间的协作关系如下：
桌面(宿主端)可以依赖应用组件管理服务模块来获取全量应用组件信息列表，其中，全量应用组件信息列表可以包括本端设备的应用组件信息列表，和/或，与本端设备建立可信 连接的一个或多个远端设备的应用组件信息列表。
应用组件管理服务模块可以依赖包管理服务模块获取应用组件信息，还可以依赖设备管理模块获取已组网的可信设备列表(即与本端设备建立可信连接的一个或多个远端设备的设备信息列表)。
包管理服务模块可以依赖分布式数据管理模块将已组网的可信设备的全量应用组件信息同步至本端设备。
设备管理模块可以依赖数据通信软总线获取已组网的可信设备的设备信息(例如设备类别等)，还可以依赖安全验证管理模块验证远端设备的合法性，确保远端设备是可信设备，其中，可信设备可以包括但不限于与本端设备在同一网络下的设备、与本端设备登录同一账号的设备。
分布式数据管理模块可以依赖数据通信软总线进行跨设备数据同步，还可以依赖安全验证管理模块对应用组件信息进行可信验证。
数据通信软总线可以依赖内核及硬件平台层来通过网络通信硬件实现设备之间的网络通信。
驱动可以依赖网络通信硬件层来实现设备之间的网络通信(例如Wi-Fi通信、蓝牙通信等无线通信，或，有线通信)。
可以理解的是，图3A和图3B仅仅是示例性的，不应该对本申请实施例中电子设备100的软件架构产生任何的限定。例如，在本申请另一些实施例中，电子设备100的系统架构也可以采用与图3A和图3B所示的例子中不同的分层结构，或者每层还可以包括更多或者更少的模块、或者多种不同模块方式的组合等，本申请实施例对此不作限定。电子设备100还可以同时包括图3A中所示的全部或部分模块以及图3B中所示的全部或者部分模块，本申请实施例对此也不作限定。
容易理解，本申请实施例涉及的其他电子设备的软件架构可以与电子设备100的软件架构相同或不同，本申请实施例对此不作限定。
基于上述图3B所示的软件架构，下面对本申请实施例提供的一种应用组件管理方法的具体流程进行详细介绍。
图4示例性示出了本申请实施例提供的一种应用组件管理方法的具体流程。
如图4所示，该方法可以应用于包括电子设备100(即本端设备)、电子设备200(即远端设备)的通信系统。下面详细介绍该方法的具体步骤：
首先，在本申请实施例中，电子设备100与电子设备200之间需要建立可信连接，在建立完成可信通信连接的前提下，才可以继续执行下述阶段二和阶段三中的各个步骤，以实现跨设备显示应用组件的目的。
示例性地，电子设备100与电子设备200之间建立可信连接的一种可能的实现方式可以为下述阶段一(步骤S401-步骤S405)中描述的实现方式，下面详细介绍：
阶段一：建立可信连接阶段
S401-S402、电子设备100检测到触发建立可信连接的事件，响应于该事件，电子设备100向电子设备200发送建立连接的请求、获取电子设备200的设备信息的请求。
其中，上述触发建立可信连接的事件可以是用户在桌面触发显示应用组件管理界面(即显示、管理本端设备和远端设备的应用组件的用户界面)的操作(例如手指上滑操作等)/指令(例如语音指令等)，或，用户通过“设置”应用程序的界面触发电子设备100与电子设备 200建立通信连接的操作，等等，本申请实施例对此不作限定。
在一些实施例中，还可以基于系统某个特征时机(例如开机重启、锁屏解锁后、系统更新后等等)来触发电子设备100与电子设备200建立可信连接。
S403-S404、电子设备200与电子设备100建立通信连接1，并向电子设备100发送电子设备200的设备信息。
具体地，电子设备200接收到电子设备100发送的建立连接的请求、获取电子设备200的设备信息的请求之后，可以与电子设备100建立通信连接1，并向电子设备100发送电子设备200的设备信息。
其中，电子设备200的设备信息可以包括但不限于电子设备200的设备类型、设备名称、设备标识(Identity Document,ID)、序列号、媒体访问控制地址、设备型号等信息，本申请实施例对此不作限定。
其中，上述建立连接的请求、获取电子设备200的设备信息的请求中均可以携带有电子设备100的设备信息。电子设备100的设备信息可以包括但不限于电子设备100的设备类型、设备名称、设备ID、序列号、媒体访问控制地址、设备型号等信息，本申请实施例对此不作限定。
S405、电子设备100基于电子设备200的设备信息对电子设备200进行可信验证，若可信验证成功，则确定通信连接1为可信连接。
具体地，电子设备100接收到电子设备200发送的电子设备200的设备信息之后，可以基于电子设备200的设备信息对电子设备200进行可信验证，其中，可信验证过程验证的信息包括但不限于电子设备200的设备证书、登录的账号等信息。
进一步地，若可信验证成功，则确定电子设备200为可信设备，且上述通信连接1为可信连接。
在一些实施例中，电子设备200也可以利用上述方式对电子设备100进行可信验证。
至此，电子设备100与电子设备200完成建立可信通信连接。进一步地，可以基于该可信连接来执行下述阶段二和阶段三中的各个步骤。
下面结合图5示例性介绍在上述建立可信连接阶段电子设备100与电子设备200内部各个模块之间的一种可能的协作方式：
步骤1、电子设备100的桌面检测到触发建立可信连接的事件，之后，桌面可以调用电子设备100的应用组件管理服务模块，以获取设备信息列表。
示例性地，上述触发建立可信连接的事件可以为图6所示的用户在桌面手指上滑的操作。
步骤2、电子设备100的应用组件管理服务可以访问设备管理模块，以请求设备管理模块获取设备信息列表。
步骤3、电子设备100的设备管理模块可以访问数据通信软总线，以请求获取远端设备信息(即电子设备200的设备信息)。
步骤4、电子设备100的数据通信软总线可以通过内核及硬件平台层、网络通信硬件层 向电子设备200请求建立连接、请求获取远端设备信息。
步骤5、电子设备200的数据通信软总线可以通过内核及硬件平台层、网络通信硬件层接收到电子设备100发送的建立连接的请求、获取远端设备信息的请求，之后，电子设备200可以通过调用数据通信软总线来与电子设备100建立连接，并向电子设备100发送电子设备200的设备信息。
步骤6、电子设备100在接收到电子设备200的设备信息之后，电子设备100的设备管理模块可以调用安全验证管理模块，以请求安全验证管理模块对电子设备200进行可信验证，若可信验证成功，则可以确定电子设备100与电子设备200建立的连接为可信连接。
电子设备100与电子设备200建立可信连接之后，电子设备100可以基于该可信连接获取电子设备200的应用组件信息，并进行保存。
示例性地，电子设备100获取并保存电子设备200的应用组件信息的一种可能的实现方式可以为下述阶段二(步骤S406-步骤S410)中描述的实现方式，下面详细介绍：
阶段二：获取并保存应用组件信息阶段
S406-S407、电子设备100检测到触发获取应用组件信息的事件，响应于该事件，电子设备100向电子设备200发送获取应用组件信息的请求。
其中，上述触发获取应用组件信息的事件可以包括但不限于用户在桌面触发显示应用组件管理界面(即显示、管理本端设备和远端设备的应用组件的用户界面)的操作(例如手指上滑操作等)/指令(例如语音指令等)。
在一些实施例中，还可以基于固定时机来触发电子设备100向电子设备200获取应用组件信息，例如，电子设备100可以每隔一段时间向电子设备200获取一次应用组件信息，即基于固定周期来向电子设备200获取应用组件信息。在另一些实施例中，还可以基于系统某个特征时机(例如开机、重启、锁屏解锁、系统更新等等)来触发电子设备100向电子设备200获取应用组件信息，本申请实施例对触发获取应用组件信息的事件不作限定。
S408-S409、电子设备200查询应用组件信息列表1(即电子设备200本地的应用组件信息列表)，并向电子设备100发送该应用组件信息列表1。
具体地，电子设备200接收到电子设备100发送的获取应用组件信息的请求之后，可以查询电子设备200本地的所有应用组件信息，电子设备200本地的所有应用组件信息可以组成应用组件信息列表1。查询完成后，电子设备200可以向电子设备100发送该应用组件信息列表1。
示例性地，如图7所示，电子设备200当前显示的界面为应用组件管理界面，该界面可以包括电子设备200本地的所有应用组件，例如运动健康应用组件、日程应用组件。在这种情况下，上述应用组件信息列表1中可以包括运动健康应用组件信息、日程应用组件信息。
在一些实施例中，上述步骤S408-步骤S409可以周期性执行，而不需要电子设备100发送获取应用组件信息的请求后再触发执行。
在一些实施例中，上述应用组件信息列表1中也可以不包括电子设备200本地的所有应用组件信息，而仅仅包括电子设备200本地的部分应用组件信息(例如电子设备200常用的 一些应用组件信息)。
S410、电子设备100保存应用组件信息列表1。
具体地，电子设备100接收到电子设备200发送的应用组件信息列表1之后，可以保存该应用组件信息列表1，以便在用户想要在电子设备100上查看电子设备200的应用组件的情况下，可以基于该应用组件信息列表1来显示电子设备200的应用组件。
下面结合图8示例性介绍在上述获取并保存应用组件信息阶段电子设备100与电子设备200内部各个模块之间的一种可能的协作方式：
步骤1、电子设备100的桌面检测到触发获取应用组件信息的事件，之后，桌面可以调用电子设备100的应用组件管理服务模块，以获取应用组件信息列表。
示例性地，上述触发获取应用组件信息的事件可以为图6所示的用户在桌面手指上滑的操作。
步骤2、电子设备100的应用组件管理服务可以访问包管理服务模块，以请求包管理服务模块获取应用组件信息列表。
其中，应用组件信息列表可以包括：电子设备100本地的应用组件信息列表(例如电子设备100本地的所有应用组件信息的列表)、电子设备200本地的应用组件信息列表(例如电子设备200本地的所有应用组件信息的列表)。
步骤3、电子设备100的包管理服务模块可以访问分布式数据管理模块，以请求获取本端设备和远端设备的应用组件信息列表。
其中，本端设备的应用组件信息列表为电子设备100本地的应用组件信息列表，分布式数据管理模块可以直接在应用组件信息数据库中查询到，而远端设备的应用组件信息列表(即电子设备200本地的应用组件信息列表)需要通过下述步骤4-步骤9来获取到。
步骤4、电子设备100的分布式数据管理模块可以访问数据通信软总线，以请求获取远端设备应用组件信息(即电子设备200本地的应用组件信息)。
步骤5、电子设备100的数据通信软总线可以基于提前与电子设备200建立的可信连接(即通过内核及硬件平台层、网络通信硬件层)向电子设备200请求获取远端设备信息。
步骤6、电子设备200的数据通信软总线可以通过内核及硬件平台层、网络通信硬件层接收到电子设备100发送的获取电子设备200的应用组件信息的请求。
步骤7、电子设备200的数据通信软总线可以访问分布式数据管理模块，以请求获取电子设备200的应用组件信息。
步骤8、电子设备200的分布式数据管理模块可以直接在应用组件信息数据库中查询电子设备200的应用组件信息。查询完成后，可以基于提前与电子设备100建立的可信连接向电子设备100发送电子设备200的应用组件信息。
其中，电子设备200的应用组件信息可以包括图8所示的远端应用组件包1、远端应用组件包2、…、远端应用组件包n等信息。
步骤9、电子设备100在接收到电子设备200的应用组件信息之后，可以通过分布式数据管理模块将电子设备200的应用组件信息保存在应用组件信息数据库中。
在本申请实施例中，电子设备100获取的电子设备200的应用组件信息为电子设备200的每一个应用组件对应的应用组件包。
在一些实施例中，由于应用组件是应用程序提供的，电子设备100也可以获取电子设备200的应用程序信息，其中应用程序信息中可以包括电子设备200的每一个应用程序对应的应用包和应用组件包，或者，应用程序信息中可以包括电子设备200的每一个应用程序对应的应用包，其中应用包中可以包括应用组件包。之后，电子设备100可以基于获取到电子设备200的应用程序信息来显示电子设备200的应用组件。
电子设备100在检测到用户想要查看应用组件信息列表的情况下，可以基于上述阶段二获取到的应用组件信息来显示本端设备(即电子设备100)的应用组件，和/或，与本端设备建立可信连接的一个或多个远端设备(例如电子设备200)的应用组件。
示例性地，电子设备100显示应用组件的一种可能的实现方式可以为下述阶段三(步骤S411-步骤S412)中描述的实现方式，下面详细介绍：
阶段三：显示应用组件阶段
S411-S412、电子设备100检测到用户查看电子设备200的应用组件的操作，响应于该操作，电子设备200基于应用组件信息列表1(即电子设备200本地的应用组件信息列表)显示电子设备200的应用组件。
示例性地，电子设备100可以检测到用户打开应用组件管理界面的操作(例如图6所示的用户在桌面手指上滑的操作)，响应于该操作，电子设备100可以显示图9A示例性所示的用户界面910，该用户界面可以为应用组件管理界面。该应用组件管理界面不仅可以显示电子设备100本地的应用组件，还可以显示与电子设备100建立可信连接的一个或多个远端设备的应用组件(例如电子设备200的所有应用组件)。
如图9A所示，在一种可能的实现方式中，电子设备100在打开应用组件管理界面之后，可以默认显示本机(即电子设备100)的应用组件(例如本地应用组件1、本地应用组件2、本地应用组件3、本地应用组件4等)。
在另一种可能的实现方式中，电子设备100在打开应用组件管理界面之后，可以先在该应用组件管理界面中只显示电子设备100的标识选项(例如“本机”选项911)以及与电子设备100建立可信连接的一个或多个远端设备的标识选项(例如“我的平板”选项912等)，当电子设备100的标识选项被选中时，或，与电子设备100建立可信连接的某个远端设备的标识选项被选中时，再在该应用组件管理界面中相应地显示该电子设备对应的应用组件。如图9A所示，当本机(即电子设备100)的标识选项被选中时，应用组件管理界面中显示电子设备100本地的应用组件；如图9B所示，当电子设备100检测到用户查看电子设备200的应用组件的操作(例如用户点击图9A所示的“我的平板”选项912的操作)，使得电子设备 200的标识选项(例如“我的平板”选项912)被选中时，应用组件管理界面中显示电子设备200的应用组件(例如应用组件913、应用组件914)。
在这种情况下，电子设备100可以在后台已经获取并保存包括电子设备200在内的与电子设备100建立可信连接的其他远端设备的应用组件信息列表，或者当用户打开电子设备100的应用组件管理界面时，再触发电子设备100获取包括电子设备200在内的与电子设备100建立可信连接的其他远端设备的应用组件信息列表，并进行保存，当电子设备200的标识选项被选中时，电子设备100可以基于已经保存的电子设备200的应用组件信息列表，在应用组件管理界面显示电子设备200的应用组件。也即是说，这种方式是上述阶段二(即获取并保存应用组件信息阶段)执行完之后再执行阶段三，这样，由于关于其他电子设备的应用组件信息列表都已经预先保存了，所以可以以较快的速度在应用组件管理界面中加载电子设备的应用组件信息列表，这可以使得用户更快速的查看到其他电子设备的应用组件，用户体验更好。
或者，电子设备100也可以在检测到电子设备200的标识选项被选中时，再去向电子设备200获取电子设备200的应用组件信息列表，并基于获取到的电子设备200的应用组件信息列表在电子设备200的标识选项对应的应用组件管理界面中显示电子设备200的应用组件。也即是说，这种方式是阶段三中步骤S411执行完之后再执行上述阶段二(即获取并保存应用组件信息阶段)，这样，在电子设备100与包括电子设备200在内的其他多个远端设备建立可信连接的情况下，可以减少电子设备100获取其他远端设备的应用组件信息列表产生的网络流量及电量消耗，有利于节约资源。
其中，上述电子设备100的标识选项和电子设备200的标识选项均分别是电子设备100基于电子设备100的设备信息、电子设备200的设备信息生成的。
可选地，如图9A和图9B所示，应用组件管理界面在显示应用组件时，还可以在每个应用组件上显示有该应用组件对应电子设备的标识，便于用户获知该应用组件是哪个电子设备提供的。
可选地，用户在退出图9B所示“我的平板”选项对应的用户界面后一段预设时间段内(例如30s、1分钟等等)再打开应用组件管理界面时，还是可以直接显示图9B所示“我的平板”选项对应的用户界面，而不是默认显示“本机”选项对应的用户界面。
可选地，如图9C示例性所示，应用组件管理界面也可以同时显示本机的应用组件、以及与本机建立可信连接的其他远端设备的应用组件，用户可以通过每个应用组件上显示的对应电子设备的标识来区分该应用组件是哪个电子设备提供的。
需要说明的是，本申请实施例对显示应用组件的用户界面的显示方式不作限定。
通过实施上述图4所示的方法，电子设备100(即本端设备)可以与一个或多个远端设备(例如电子设备200)建立可信连接，通过该可信连接，电子设备100可以获取这一个或多个远端设备提供的应用组件信息列表，并可以基于应用组件信息列表来显示这一个或多个远端设备提供的应用组件，从而可以解决用户在本端设备上无法查看跨设备应用组件的问题，提高用户体验。
下面结合图10示例性介绍在上述显示应用组件阶段电子设备100内部各个模块之间的一种可能的协作方式：
步骤1、电子设备100的桌面检测到用户查看特定设备(例如电子设备100或电子设备200等)的应用组件的操作，之后，桌面可以调用电子设备100的应用组件管理服务模块，以获取应用组件信息列表。
步骤2、电子设备100的应用组件管理服务模块可以访问包管理服务模块，以请求包管理服务模块获取应用组件信息列表。
步骤3、电子设备100的包管理服务模块可以访问分布式数据管理模块，以请求获取本端设备和远端设备的应用组件信息列表。
可选地，包管理服务模块也可以只向分布式数据管理模块请求获取上述特定设备的应用组件信息列表，而不是全部设备(即本端设备以及与本端设备建立可信连接的全部远端设备)的应用组件信息列表。
步骤4、电子设备100的分布式数据管理模块可以在应用组件信息数据库中获取应用组件信息列表，之后，可以将获取到的应用组件信息列表返回桌面用于显示对应电子设备的应用组件。
其中，分布式数据管理模块可以只获取上述特定设备的应用组件信息列表，也可以获取全部设备(即本端设备以及与本端设备建立可信连接的全部远端设备)的应用组件信息列表。
继续参阅图10，应用组件信息数据库中可以保存有本端设备的应用组件信息列表、以及本端设备获取到的与本端设备建立可信连接的一个或多个远端设备的应用组件信息列表，如图10所示，每个电子设备的应用组件信息列表中可以包括该电子设备的设备类型、该电子设备的设备ID、以及该电子设备提供的一个或多个应用组件包，其中，应用组件包相比于其应用实体本身而言是个轻型化的安装包。这样，分布式数据管理模块可以基于设备ID和/或设备类型来查询对应电子设备下的应用组件包。
假设电子设备100(本端设备)为手机，则电子设备100的应用组件信息列表中记录的设备类型为手机、设备ID为XX(即电子设备100的设备ID)、电子设备100提供的应用组件包为本地应用组件包1、本地应用组件包2、…、本地应用组件包n；假设电子设备200(远端设备)为平板，则电子设备200的应用组件信息列表中记录的设备类型为平板、设备ID为XXX(即电子设备200的设备ID)、电子设备200提供的应用组件包为远端应用组件包1、远端应用组件包2、…、远端应用组件包n。
在本申请实施例中，每一个应用组件包中均可以包括该应用组件包对应的应用组件的静态信息，静态信息可以包括该应用组件能够呈现出来的预设信息(例如位置、气温等标题信息、尺寸信息、等等)，而不包括用户数据，即该应用组件在预览模式下(或在初始化状态下)能够呈现出来的信息(例如应用组件的预览图、标题、尺寸等信息)，不会随着时间或用户的行为而发生变化。
参阅图9B，容易看出，应用组件913和应用组件914在图9B中均呈现的是静态信息，其中，应用组件913中的静态信息可以包括位置信息(例如“地区.城市”)、气温信息(例如“温度”)、步数信息(例如“0步”)等；应用组件914中的静态信息可以包括日程信息(例如“明天XX个日程”、“日程1”、“日程2”)等。
容易看出，图9B是使用前述方案一(电子设备100在检测到用户在桌面查看应用组件的场景下静态显示应用组件)来显示与电子设备100建立可信连接的远端设备的应用组件的，也即是说，电子设备100可以在上述阶段二(即获取并保存应用组件信息阶段)中只获取应用组件的静态信息，然后基于该静态信息来静态显示远端设备上的应用组件。
在一些实施例中，在静态显示应用组件的情况下，电子设备100也可以不获取应用组件的安装包，而是只获取用于静态显示应用组件的相关信息即可，这样可以节省系统资源，减少成本浪费，该相关信息可以包括应用组件的组件标识，应用组件的描述信息；其中，应用组件的组件标识可以包括应用组件的包名和模块名，包名，例如，com.xxx.xxx.sporthealth，可以表示该应用组件对应的应用程序为运行健康，模块名，例如，com.xxx.xxx.weather，可以表示该应用组件为天气类应用组件；其中，应用组件的描述信息可以包括但不限于应用组件的预览图、标题(例如运动健康、天气、位置等)、尺寸等信息。在这种情况下，若电子设备100检测到用户将应用组件添加到桌面的操作，则电子设备100可以再向远端设备获取该应用组件的安装包，获取到该应用组件的安装包之后可以安装该应用组件，安装完成之后可以将该应用组件添加到桌面进行显示。
在用户开始使用某个应用组件(例如用户将某个应用组件添加到桌面等)之后，该应用组件对应的应用组件包还可以关联有该应用组件的动态信息，动态信息可以包括用户在使用该应用组件过程中产生的具体数据(即用户数据，也可以称为个性化数据)呈现出来的信息，该具体数据可以是该应用组件能够呈现出来的信息类型(例如位置、运动步数等)实际对应的数据，会随着时间或用户的行为而发生变化。
示例性地，如图11A所示，图9B中的应用组件913(运动健康应用组件)和应用组件914(日程应用组件)均被用户添加到了电子设备200(远端设备)的桌面，即用户已经开始使用这两个应用组件。可以看出，与图9B不同的是，由于用户已经开始使用这两个应用组件，因此，这两个应用组件会产生动态信息，进一步地，这两个应用组件上均会显示有相应的动态信息，例如，应用组件913上显示了用户所在区域(例如“栖霞区.南京”)、用户所在区域的气温(例如“22度”)、用户当前运动步数(例如“6888步”)等；又例如，应用组件914上显示了用户明天的日程安排个数(例如“明天2个日程”)、明天的具体日程安排(例如“全年销售说明”、“明年预算汇报”)等。
为了在电子设备100(本端设备)上也可以显示出远端设备上包括动态信息的应用组件，我们可以使用前述方案二(电子设备100在检测到用户在桌面查看应用组件的场景下动态显示应用组件)来实现，前述方案二与前述方案一不同的是，电子设备100在上述阶段二(即获取并保存应用组件信息阶段)中获取应用组件的静态信息的同时，如果应用组件还包括动态信息，则还需要获取应用组件的动态信息，并将应用组件的静态信息和动态信息都保存下 来，然后基于应用组件的静态信息和动态信息来动态显示远端设备上的应用组件，后续只需要获取应用组件的动态信息即可显示出与远端设备状态一致的应用组件。
参阅图11B，图11B中显示的这两个应用组件均为包括动态信息的应用组件，从图11B和图11A中可以看出，电子设备100上显示的应用组件状态与电子设备200上显示的应用组件状态一致，这样，用户可以在本端设备上就可以查看到远端设备上的应用组件的实时状态，方便快捷，提高用户体验。
可选地，如图11B所示，应用组件管理界面在显示应用组件时，还可以在每个应用组件上显示有该应用组件对应电子设备的标识，便于用户获知该应用组件是哪个电子设备提供的。
可选地，用户在退出图11B所示“我的平板”选项对应的用户界面后一段预设时间段内(例如30s、1分钟等等)再打开应用组件管理界面时，还是可以直接显示图11B所示“我的平板”选项对应的用户界面，而不是默认显示“本机”选项对应的用户界面。
可选地，如图11C示例性所示，应用组件管理界面也可以同时显示本机的应用组件、以及与本机建立可信连接的其他远端设备的应用组件，用户可以通过每个应用组件上显示的对应电子设备的标识来区分该应用组件是哪个电子设备提供的。
需要说明的是，本申请实施例对显示应用组件的用户界面的显示方式不作限定。
在本申请实施例中，只包括静态信息的应用组件(例如图9B所示的应用组件)可以称为静态应用组件，包括动态信息的应用组件(例如图11B所示的应用组件)可以称为动态应用组件。
容易看出，图9B所示的这种应用组件的静态显示方式仅仅可以让用户在本端设备查看到远端设备提供的可用应用组件有哪些，而无法让用户在本端设备查看到这些应用组件在远端设备上的实时状态，相比于应用组件的静态显示方式，图11B所示的这种应用组件的动态显示方式既可以让用户在本端设备查看到远端设备提供的可用应用组件有哪些，又可以让用户在本端设备查看到这些应用组件在远端设备上的实时状态(即本端设备上显示的应用组件状态与远端设备上显示的该应用组件状态一致)，进一步提高了用户体验。
在一些实施例中，图11B所示的动态应用组件不仅可以在本端设备的应用组件管理界面显示，也可以添加到本端设备的桌面上进行显示。示例性地，参阅图12A，假设用户想要将运动健康应用组件添加到桌面，则电子设备100可以检测到用户针对运动健康应用组件的操作(例如长按操作)，响应于该操作，电子设备100可以显示窗口1210，窗口1210中可以包括选项1211(例如“注入到本地”)，进一步地，电子设备100可以检测到用户针对选项1211的操作(例如点击操作)，响应于该操作，如图12B所示，电子设备100可以将运动健康应用组件添加到桌面进行显示。在一种可能的实现方式中，用户也可以通过拖拽操作将应用组件添加到本端设备的桌面上进行显示，本申请实施例对用户将应用组件添加到本端设备的桌面上进行显示的具体操作不作限定。
这样，本端设备的桌面上就可以直接显示远端设备的应用组件，用户可以更加便捷地查看远端设备上的应用组件状态，进一步提高了用户体验。
参阅图10，容易看出，图10示出的是电子设备100在检测到用户在桌面查看应用组件的场景下静态显示应用组件(例如图9B所示的应用组件)时其内部各个模块之间的一种可能的协作方式，下面结合图13示例性介绍电子设备100在检测到用户在桌面查看应用组件的场景下动态显示应用组件(例如图11B所示的应用组件)时其内部各个模块之间的一种可能的协作方式：
步骤1、电子设备100的桌面检测到用户查看特定设备(例如电子设备100或电子设备200等)的应用组件的操作，之后，桌面可以调用电子设备100的应用组件管理服务模块，以获取应用组件信息列表。
步骤2、电子设备100的应用组件管理服务模块可以访问包管理服务模块，以请求包管理服务模块获取应用组件信息列表。
步骤3、电子设备100的包管理服务模块可以访问分布式数据管理模块，以请求获取本端设备和远端设备的应用组件信息列表。
可选地，包管理服务模块也可以只向分布式数据管理模块请求获取上述特定设备的应用组件信息列表，而不是全部设备(即本端设备以及与本端设备建立可信连接的全部远端设备)的应用组件信息列表。
步骤4、电子设备100的分布式数据管理模块可以在应用组件信息数据库中获取应用组件信息列表。
可以看出，与图10不同的是，在应用组件包括动态信息(即个性化数据)的情况下，应用组件信息数据库中还可以保存有应用组件的动态信息(例如图13中的个性化数据1、个性化数据2)。
继续参阅图13，下面对个性化数据进行举例说明：假设应用组件信息数据库中保存的设备类型为平板的电子设备为电子设备200，该电子设备下的远端应用组件包1对应的应用组件为图11B中的运动健康应用组件，远端应用组件包2对应的应用组件为图11B中的日程应用组件，那么，个性化数据1则可以包括运动健康应用组件中显示的用户所在区域数据(例如“栖霞区.南京”)、用户所在区域的气温数据(例如“22度”)、用户当前运动步数数据(例如“6888步”)等，个性化数据2则可以包括日程应用组件中显示的用户明天的日程安排个数数据(例如“明天2个日程”)、明天的具体日程安排数据(例如“全年销售说明”、“明年预算汇报”)等。
分布式数据管理模块在获取到应用组件信息列表之后可以将其返回给包管理服务模块，以便执行后续步骤。
步骤5、电子设备100的包管理服务模块安装包括个性化数据的应用组件。
具体地，包管理服务模块接收到分布式数据管理模块返回的应用组件信息列表之后，可以判断返回的应用组件信息列表中的应用组件包是否关联有个性化数据(即判断哪个应用组件包括动态信息)，若是，则包管理服务模块则需要安装该应用组件，即包管理服务模块负责 安装包括动态信息的应用组件。
对于不包括动态信息的应用组件则不需要安装，其在本端设备上依然只显示静态信息。
步骤6、电子设备100的应用组件管理服务模块将已安装成功的包括动态信息的应用组件注入应用组件容器(例如桌面)。
在包管理服务模块安装完包括动态信息的应用组件之后，应用组件管理服务模块可以将其注入应用组件容器中，以便应用组件可以在容器中运行。
在本申请实施例中，应用组件管理界面可以是桌面应用程序提供的一个用户界面，那么，应用组件容器可以是桌面应用程序提供的。
需要说明的是，每个应用程序可以提供一个或多个容器，在应用程序只提供一个容器的情况下，该应用程序的多个用户界面可以共用一个容器，在应用程序可以提供多个容器的情况下，该应用程序的每个用户界面可以独立使用一个或多个容器，例如，应用组件管理界面中显示的多个应用组件可以被注入到同一个容器中，也可以被注入到多个容器中(例如一个容器注入一个应用组件)。
在图11B所示的实施例中，提供应用组件容器的应用程序以桌面应用程序为例，不限于此，也可以是其他应用程序来提供应用组件容器，本申请实施例对此不作限定。
步骤7、远端设备上包括个性化数据的应用组件向包管理服务模块读取个性化数据。
具体地，在将远端设备应用组件安装并注入应用组件容器后，该应用组件可以开始运行，并向包管理服务模块读取其对应的个性化数据，这样，电子设备100上显示的该应用组件状态就可以与远端设备上显示的该应用组件状态一致。
在本申请实施例中，电子设备100获取的电子设备200的应用组件信息为电子设备200的每一个应用组件对应的应用组件包和应用组件的动态信息。
在一些实施例中，由于应用组件是应用程序提供的，电子设备100也可以获取电子设备200的应用程序信息和应用组件的动态信息，其中应用程序信息中可以包括电子设备200的每一个应用程序对应的应用包和应用组件包，或者，应用程序信息中可以包括电子设备200的每一个应用程序对应的应用包，其中应用包中可以包括应用组件包。之后，电子设备100可以基于获取到电子设备200的应用程序信息和应用组件的动态信息来显示电子设备200的应用组件。
电子设备100在动态显示远端设备上的应用组件时，在电子设备100安装了该应用组件之后，后续为了可以实时地查看到远端设备上的该应用组件状态，电子设备100可以周期性地(例如每隔1秒、10秒、30秒、1分钟等等)向远端设备获取该应用组件运行过程产生的用户数据(即个性化数据)。
电子设备100在静态显示远端设备上的应用组件时，电子设备100可以不安装该应用组件，也可以安装该应用组件，例如，电子设备100可以通过包管理服务模块利用该应用组件的安装包(即应用组件包)来安装该应用组件。在安装了该应用组件的情况下，用户也可以 通过图12A所示的方式将该应用组件添加到桌面进行显示；在未安装该应用组件的情况下，当用户通过图12A示例性所示的方式将该应用组件添加到桌面进行显示时，电子设备100会安装该应用组件，安装完成后可以在桌面上显示该应用组件。
前述实施例介绍的是电子设备100在检测到用户主动在桌面上通过应用组件管理界面查看应用组件的场景下静态显示/动态显示应用组件的过程(即前述方案一和方案二)，在本申请的其他一些实施例中，电子设备100还可以在检测到与一个或多个应用组件相关联的特定场景(例如用户输入与一个或多个应用组件相关联的关键字进行搜索的场景等)下自动给用户推荐并静态显示/动态显示与上述特定场景相关联的一个或多个应用组件(即前述方案三和方案四)。
其中，电子设备100执行前述方案三和方案四时，电子设备100与远端设备建立可信连接的过程、向远端设备获取并保存应用组件信息的过程均与前述方案一和方案二相同，可以参照前述内容，在此不再赘述，只是显示应用组件的过程与前述方案一和方案二不同，下面以用户输入与一个或多个应用组件相关联的关键字进行搜索的场景为例分别介绍前述方案三和方案四显示应用组件的过程：
首先介绍方案三(电子设备100在检测到与一个或多个应用组件相关联的特定场景下静态显示应用组件)：
参阅图14A和图14B，示例性地，如图14A所示，电子设备100可以显示用户界面1310，该用户界面可以为搜索场景下的一个用户界面(即搜索界面)，该用户界面可以包括搜索框1311、搜索选项1312。电子设备100可以检测到用户在搜索框1311中输入“运动”两字并点击搜索选项1312的操作，响应于该操作，电子设备100可以将“运动”两字作为关键字在本地应用组件信息数据库模糊查询匹配与该关键字相关的应用组件，若匹配成功(即电子设备100匹配到了与该关键字相关的一个或多个应用组件)，则电子设备100可以在图14B示例性所示的区域1410中静态显示与“运动”两字相关的一个或多个应用组件(例如应用组件1411)，即电子设备100可以只显示这一个或多个应用组件的静态信息。其中，这一个或多个应用组件可以是电子设备100本地的应用组件，也可以是与电子设备100建立可信连接的远端设备的应用组件。
可选地，电子设备100还可以在区域1410中显示应用程序1412，该应用程序可以是提供应用组件1411的应用程序，也可以是与“运动”相关的应用程序但不是提供应用组件1411的应用程序。
下面结合图15示例性介绍电子设备100在检测到与一个或多个应用组件相关联的特定场景下静态显示应用组件(例如图14B所示的应用组件)时其内部各个模块之间的一种可能的协作方式：
步骤1、电子设备100在特定界面(例如搜索界面)检测到用户查询与关键字相关的应用组件的操作，之后，该特定界面对应的应用程序可以调用电子设备100的应用组件管理服务模块，以查询与关键字相关的应用组件信息。
示例性，上述用户查询与关键字相关的应用组件的操作可以是用户在图14A所示的搜索框1311中输入关键字(例如“运动”两字)并点击搜索选项1312的操作。
其中，上述特定界面可以是系统应用(即不可卸载或应用标识App ID小于10000的应用) 提供的，也可以是第三方应用(即除系统应用之外的应用)提供的，本申请实施例对此不作限定。
步骤2、电子设备100的应用组件管理服务模块可以访问包管理服务模块，以请求包管理服务模块查询与关键字相关的应用组件信息。
步骤3、电子设备100的包管理服务模块可以访问分布式数据管理模块，以请求查询与关键字相关的本端设备和远端设备的应用组件信息。
步骤4、电子设备100的分布式数据管理模块可以在应用组件信息数据库中查询与关键字相关的本端设备和远端设备的应用组件信息，若可以查询到与关键字相关的应用组件信息，则分布式数据管理模块可以把查询到的与关键字相关的应用组件信息返回特定界面用于显示与关键字相关的应用组件。其中，应用组件信息数据库中保存的远端设备的应用组件信息是电子设备100向远端设备获取的，具体获取过程可以参照前述方案一中获取应用组件信息过程的相关内容，在此不再赘述。
从图15所示的实施例中可以看出，由于应用组件信息数据库中没有保存与应用组件包相关联的应用组件的个性化数据，因此，上述查询到的与关键字相关的应用组件信息也就不会包括应用组件的动态信息，只会包括应用组件的静态信息，进一步地，电子设备100也就只会基于应用组件的静态信息来静态显示与关键字相关的应用组件。
下面介绍方案四(电子设备100在检测到与一个或多个应用组件相关联的特定场景下动态显示应用组件)：
参阅图14A和图16，示例性地，如图14A所示，电子设备100可以检测到用户在搜索框1311中输入“运动”两字并点击搜索选项1312的操作，响应于该操作，电子设备100可以将“运动”两字作为关键字在本地应用组件信息数据库模糊查询匹配与该关键字相关的应用组件，若匹配成功(即电子设备100匹配到了与该关键字相关的一个或多个应用组件)，则电子设备100可以在图16示例性所示的区域1610中动态显示与“运动”两字相关的一个或多个应用组件(例如应用组件1611)，即电子设备100可以显示这一个或多个应用组件的动态信息。其中，这一个或多个应用组件可以是电子设备100本地的应用组件，也可以是与电子设备100建立可信连接的远端设备的应用组件。
可选地，电子设备100还可以在区域1610中显示应用程序1612，该应用程序可以是提供应用组件1611的应用程序，也可以是与“运动”相关的应用程序但不是提供应用组件1611的应用程序。
从图16和图14B中可以看出，图16中所示的应用组件1611和图14B所示的应用组件1411是同一个应用组件，不同的是，该应用组件在图14B中显示的只是其静态信息，而在图16中显示的是其动态信息。
容易看出，图14B这种应用组件的静态显示方式仅仅可以让用户在本端设备获知与用户 所输入的关键字相关的应用组件有哪些，而无法让用户在本端设备获知远端设备上的这些应用组件的实时状态，相比于应用组件的静态显示方式，图16这种应用组件的动态显示方式既可以让用户在本端设备获知与用户所输入的关键字相关的应用组件有哪些，又可以让用户在本端设备获知远端设备上的这些应用组件的实时状态，(即本端设备上显示的应用组件状态与远端设备上显示的该应用组件状态一致)，进一步提高了用户体验。
下面结合图17示例性介绍电子设备100在检测到与一个或多个应用组件相关联的特定场景下动态显示应用组件(例如图16所示的应用组件)时其内部各个模块之间的一种可能的协作方式：
步骤1、电子设备100在特定界面(例如搜索界面)检测到用户查询关键字相关的应用组件的操作，之后，该特定界面对应的应用程序可以调用电子设备100的应用组件管理服务模块，以查询与关键字相关的应用组件信息。
示例性，上述用户查询关键字相关的应用组件的操作可以是用户在图14A所示的搜索框1311中输入关键字(例如“运动”两字)并点击搜索选项1312的操作。
其中，上述特定界面可以是系统应用(即不可卸载或应用标识App ID小于10000的应用)提供的，也可以是第三方应用(即除系统应用之外的应用)提供的，本申请实施例对此不作限定。
步骤2、电子设备100的应用组件管理服务模块可以访问包管理服务模块，以请求包管理服务模块查询与关键字相关的应用组件信息。
步骤3、电子设备100的包管理服务模块可以访问分布式数据管理模块，以请求查询与关键字相关的本端设备和远端设备的应用组件信息。
步骤4、电子设备100的分布式数据管理模块可以在应用组件信息数据库中查询与关键字相关的本端设备和远端设备的应用组件信息。
其中，应用组件信息数据库中保存的远端设备的应用组件信息是电子设备100向远端设备获取的，具体获取过程可以参照前述方案二中获取应用组件信息过程的相关内容，在此不再赘述。
可以看出，与图15不同的是，在应用组件包括动态信息(即个性化数据)的情况下，应用组件信息数据库中还可以保存有应用组件的动态信息(例如图17中的个性化数据1、个性化数据2)。关于个性化数据的介绍可以参照图13中的相关内容，在此不再赘述。
分布式数据管理模块若可以在应用组件信息数据库中查询到与关键字相关的应用组件信息，则分布式数据管理模块可以进一步地把查询到的与关键字相关的应用组件信息返回给包管理服务模块，以便执行后续步骤。
步骤5、电子设备100的包管理服务模块安装包括个性化数据的应用组件。
具体地，包管理服务模块接收到分布式数据管理模块返回的与关键字相关的应用组件信息之后，可以判断返回的与关键字相关的应用组件信息中的应用组件包是否关联有个性化数 据(即判断哪个应用组件包括动态信息)，若是，则包管理服务模块则需要安装该应用组件，即包管理服务模块负责安装包括个性化数据的应用组件。
对于不包括动态信息的应用组件则不需要安装，其在本端设备上依然只显示静态信息。
步骤6、电子设备100的应用组件管理服务模块将已安装成功的包括动态信息的应用组件注入应用组件容器(例如搜索界面)。
在包管理服务模块安装完包括动态信息的应用组件之后，应用组件管理服务模块可以将其注入应用组件容器中，以便应用组件可以在容器中运行。
可以理解，在图16所示的实施例中，包括动态信息的应用组件是注入到搜索界面对应的应用组件容器中的。
步骤7、远端设备上包括个性化数据的应用组件向包管理服务模块读取个性化数据。
具体地，在将远端设备上包括个性化数据的应用组件安装并注入应用组件容器后，该应用组件可以开始运行，并向包管理服务模块读取其对应的个性化数据，这样，电子设备100上显示的该应用组件状态就可以与远端设备上显示的该应用组件状态一致。
在前述方案三和前述方案四中，触发电子设备100获取向电子设备200获取应用组件信息的事件还可以包括：电子设备100检测到用户在搜索界面上搜索关键字的操作。
在本申请实施例中，第一电子设备可以是电子设备100(本端设备)，第二电子设备可以是电子设备200(远端设备)，第一应用组件可以是电子设备200上的应用组件，第一应用组件的安装包也可以称为第一应用组件包，第一内容可以为第一应用组件的静态信息，第一数据可以是用于显示第一应用组件的静态信息的数据，第二内容可以为第一应用组件的动态信息，第二数据可以是用于显示第一应用组件的动态信息的数据(例如个性化数据)，第二应用组件可以是电子设备100上的应用组件，第一请求可以是图4中步骤S407中获取应用组件信息的请求。
下面介绍本申请实施例提供的一种电子设备100的结构示意图。
图18示例性示出了本申请实施例中提供的一种电子设备100的结构。
如图18所示，电子设备100可以包括：处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及用户标识模块(subscriber identification module，SIM)卡接口195等。其中传感器模块180可以包括压力传感器180A，陀螺仪传感器180B，气压传感器180C，磁传感器180D，加速度传感器180E，距离传感器180F，接近光传感器180G，指纹传感器180H，温度传感器180J，触摸传感器180K，环境光传感器180L，骨传导传感器180M等。
可以理解的是，本申请实施例示意的结构并不构成对电子设备100的具体限定。在本申请另一些实施例中，电子设备100可以包括比图示更多或更少的部件，或者组合某些部件， 或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
其中，控制器可以是电子设备100的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处理器110刚用过或循环使用的指令或数据。如果处理器110需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器110的等待时间，因而提高了系统的效率。
在一些实施例中，处理器110可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
I2C接口是一种双向同步串行总线，包括一根串行数据线(serial data line，SDA)和一根串行时钟线(derail clock line，SCL)。在一些实施例中，处理器110可以包含多组I2C总线。处理器110可以通过不同的I2C总线接口分别耦合触摸传感器180K，充电器，闪光灯，摄像头193等。例如：处理器110可以通过I2C接口耦合触摸传感器180K，使处理器110与触摸传感器180K通过I2C总线接口通信，实现电子设备100的触摸功能。
I2S接口可以用于音频通信。在一些实施例中，处理器110可以包含多组I2S总线。处理器110可以通过I2S总线与音频模块170耦合，实现处理器110与音频模块170之间的通信。在一些实施例中，音频模块170可以通过I2S接口向无线通信模块160传递音频信号，实现通过蓝牙耳机接听电话的功能。
PCM接口也可以用于音频通信，将模拟信号抽样，量化和编码。在一些实施例中，音频模块170与无线通信模块160可以通过PCM总线接口耦合。在一些实施例中，音频模块170也可以通过PCM接口向无线通信模块160传递音频信号，实现通过蓝牙耳机接听电话的功能。所述I2S接口和所述PCM接口都可以用于音频通信。
UART接口是一种通用串行数据总线，用于异步通信。该总线可以为双向通信总线。它将要传输的数据在串行通信与并行通信之间转换。在一些实施例中，UART接口通常被用于连接处理器110与无线通信模块160。例如：处理器110通过UART接口与无线通信模块160中的蓝牙模块通信，实现蓝牙功能。在一些实施例中，音频模块170可以通过UART接口向无线通信模块160传递音频信号，实现通过蓝牙耳机播放音乐的功能。
MIPI接口可以被用于连接处理器110与显示屏194，摄像头193等外围器件。MIPI接口 包括摄像头串行接口(camera serial interface，CSI)，显示屏串行接口(display serial interface，DSI)等。在一些实施例中，处理器110和摄像头193通过CSI接口通信，实现电子设备100的拍摄功能。处理器110和显示屏194通过DSI接口通信，实现电子设备100的显示功能。
GPIO接口可以通过软件配置。GPIO接口可以被配置为控制信号，也可被配置为数据信号。在一些实施例中，GPIO接口可以用于连接处理器110与摄像头193，显示屏194，无线通信模块160，音频模块170，传感器模块180等。GPIO接口还可以被配置为I2C接口，I2S接口，UART接口，MIPI接口等。
USB接口130是符合USB标准规范的接口，具体可以是Mini USB接口，Micro USB接口，USB Type C接口等。USB接口130可以用于连接充电器为电子设备100充电，也可以用于电子设备100与外围设备之间传输数据。也可以用于连接耳机，通过耳机播放音频。该接口还可以用于连接其他终端设备，例如AR设备等。
可以理解的是，本申请实施例示意的各模块间的接口连接关系，只是示意性说明，并不构成对电子设备100的结构限定。在本申请另一些实施例中，电子设备100也可以采用上述实施例中不同的接口连接方式，或多种接口连接方式的组合。
充电管理模块140用于从充电器接收充电输入。其中，充电器可以是无线充电器，也可以是有线充电器。在一些有线充电的实施例中，充电管理模块140可以通过USB接口130接收有线充电器的充电输入。在一些无线充电的实施例中，充电管理模块140可以通过电子设备100的无线充电线圈接收无线充电输入。充电管理模块140为电池142充电的同时，还可以通过电源管理模块141为电子设备100供电。
电源管理模块141用于连接电池142，充电管理模块140与处理器110。电源管理模块141接收电池142和/或充电管理模块140的输入，为处理器110，内部存储器121，外部存储器，显示屏194，摄像头193，和无线通信模块160等供电。电源管理模块141还可以用于监测电池容量，电池循环次数，电池健康状态(漏电，阻抗)等参数。在其他一些实施例中，电源管理模块141也可以设置于处理器110中。在另一些实施例中，电源管理模块141和充电管理模块140也可以设置于同一个器件中。
电子设备100的无线通信功能可以通过天线1，天线2，移动通信模块150，无线通信模块160，调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。电子设备100中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块150可以提供应用在电子设备100上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块150可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块150可以由天线1接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块150还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块150的至少部分功能模块可以被设置于处理器110中。在一些实施例中，移动通信模块150的至少部分功能模块可以与处理器110的至少部分模块被设置在同一个器件中。
调制解调处理器可以包括调制器和解调器。其中，调制器用于将待发送的低频基带信号调制成中高频信号。解调器用于将接收的电磁波信号解调为低频基带信号。随后解调器将解调得到的低频基带信号传送至基带处理器处理。低频基带信号经基带处理器处理后，被传递给应用处理器。应用处理器通过音频设备(不限于扬声器170A，受话器170B等)输出声音信 号，或通过显示屏194显示图像或视频。在一些实施例中，调制解调处理器可以是独立的器件。在另一些实施例中，调制解调处理器可以独立于处理器110，与移动通信模块150或其他功能模块设置在同一个器件中。
无线通信模块160可以提供应用在电子设备100上的包括无线局域网(wireless local area networks，WLAN)(如无线保真(wireless fidelity，Wi-Fi)网络)，蓝牙(bluetooth，BT)，全球导航卫星系统(global navigation satellite system，GNSS)，调频(frequency modulation，FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。无线通信模块160可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块160经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器110。无线通信模块160还可以从处理器110接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
在一些实施例中，电子设备100的天线1和移动通信模块150耦合，天线2和无线通信模块160耦合，使得电子设备100可以通过无线通信技术与网络以及其他设备通信。所述无线通信技术可以包括全球移动通讯系统(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)，BT，GNSS，WLAN，NFC，FM，和/或IR技术等。所述GNSS可以包括全球卫星定位系统(global positioning system，GPS)，全球导航卫星系统(global navigation satellite system，GLONASS)，北斗卫星导航系统(beidou navigation satellite system，BDS)，准天顶卫星系统(quasi-zenith satellite system，QZSS)和/或星基增强系统(satellite based augmentation systems，SBAS)。
电子设备100通过GPU，显示屏194，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏194和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器110可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
显示屏194用于显示图像，视频等。显示屏194包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)，有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode的，AMOLED)，柔性发光二极管(flex light-emitting diode，FLED)，Miniled，MicroLed，Micro-oLed，量子点发光二极管(quantum dot light emitting diodes，QLED)等。在一些实施例中，电子设备100可以包括1个或N个显示屏194，N为大于1的正整数。
电子设备100可以通过ISP，摄像头193，视频编解码器，GPU，显示屏194以及应用处理器等实现拍摄功能。
ISP用于处理摄像头193反馈的数据。例如，拍照时，打开快门，光线通过镜头被传递到摄像头感光元件上，光信号转换为电信号，摄像头感光元件将所述电信号传递给ISP处理，转化为肉眼可见的图像。ISP还可以对图像的噪点，亮度等进行算法优化。ISP还可以对拍摄场景的曝光，色温等参数优化。在一些实施例中，ISP可以设置在摄像头193中。
摄像头193用于捕获静态图像或视频。物体通过镜头生成光学图像投射到感光元件。感光元件可以是电荷耦合器件(charge coupled device，CCD)或互补金属氧化物半导体(complementary metal-oxide-semiconductor，CMOS)光电晶体管。感光元件把光信号转换成电信号，之后将电信号传递给ISP转换成数字图像信号。ISP将数字图像信号输出到DSP加工 处理。DSP将数字图像信号转换成标准的RGB，YUV等格式的图像信号。在一些实施例中，电子设备100可以包括1个或N个摄像头193，N为大于1的正整数。
数字信号处理器用于处理数字信号，除了可以处理数字图像信号，还可以处理其他数字信号。例如，当电子设备100在频点选择时，数字信号处理器用于对频点能量进行傅里叶变换等。
视频编解码器用于对数字视频压缩或解压缩。电子设备100可以支持一种或多种视频编解码器。这样，电子设备100可以播放或录制多种编码格式的视频，例如：动态图像专家组(moving picture experts group，MPEG)1，MPEG2，MPEG3，MPEG4等。
NPU为神经网络(neural-network，NN)计算处理器，通过借鉴生物神经网络结构，例如借鉴人脑神经元之间传递模式，对输入信息快速处理，还可以不断的自学习。通过NPU可以实现电子设备100的智能认知等应用，例如：图像识别，人脸识别，语音识别，文本理解等。
外部存储器接口120可以用于连接外部存储卡，例如Micro SD卡，实现扩展电子设备100的存储能力。外部存储卡通过外部存储器接口120与处理器110通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器121可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。处理器110通过运行存储在内部存储器121的指令，从而执行电子设备100的各种功能应用以及数据处理。内部存储器121可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统，至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储电子设备100使用过程中所创建的数据(比如音频数据，电话本等)等。此外，内部存储器121可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。
电子设备100可以通过音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，以及应用处理器等实现音频功能。例如音乐播放，录音等。
音频模块170用于将数字音频信息转换成模拟音频信号输出，也用于将模拟音频输入转换为数字音频信号。音频模块170还可以用于对音频信号编码和解码。在一些实施例中，音频模块170可以设置于处理器110中，或将音频模块170的部分功能模块设置于处理器110中。
扬声器170A，也称“喇叭”，用于将音频电信号转换为声音信号。电子设备100可以通过扬声器170A收听音乐，或收听免提通话。
受话器170B，也称“听筒”，用于将音频电信号转换成声音信号。当电子设备100接听电话或语音信息时，可以通过将受话器170B靠近人耳接听语音。
麦克风170C，也称“话筒”，“传声器”，用于将声音信号转换为电信号。当拨打电话或发送语音信息时，用户可以通过人嘴靠近麦克风170C发声，将声音信号输入到麦克风170C。电子设备100可以设置至少一个麦克风170C。在另一些实施例中，电子设备100可以设置两个麦克风170C，除了采集声音信号，还可以实现降噪功能。在另一些实施例中，电子设备100还可以设置三个，四个或更多麦克风170C，实现采集声音信号，降噪，还可以识别声音来源，实现定向录音功能等。
耳机接口170D用于连接有线耳机。耳机接口170D可以是USB接口130，也可以是3.5mm的开放移动终端设备平台(open mobile terminal platform，OMTP)标准接口，美国蜂窝电信工业协会(cellular telecommunications industry association of the USA，CTIA)标准接口。
压力传感器180A用于感受压力信号，可以将压力信号转换成电信号。在一些实施例中， 压力传感器180A可以设置于显示屏194。压力传感器180A的种类很多，如电阻式压力传感器，电感式压力传感器，电容式压力传感器等。电容式压力传感器可以是包括至少两个具有导电材料的平行板。当有力作用于压力传感器180A，电极之间的电容改变。电子设备100根据电容的变化确定压力的强度。当有触摸操作作用于显示屏194，电子设备100根据压力传感器180A检测所述触摸操作强度。电子设备100也可以根据压力传感器180A的检测信号计算触摸的位置。在一些实施例中，作用于相同触摸位置，但不同触摸操作强度的触摸操作，可以对应不同的操作指令。例如：当有触摸操作强度小于第一压力阈值的触摸操作作用于短消息应用图标时，执行查看短消息的指令。当有触摸操作强度大于或等于第一压力阈值的触摸操作作用于短消息应用图标时，执行新建短消息的指令。
陀螺仪传感器180B可以用于确定电子设备100的运动姿态。在一些实施例中，可以通过陀螺仪传感器180B确定电子设备100围绕三个轴(即，x，y和z轴)的角速度。陀螺仪传感器180B可以用于拍摄防抖。示例性的，当按下快门，陀螺仪传感器180B检测电子设备100抖动的角度，根据角度计算出镜头模组需要补偿的距离，让镜头通过反向运动抵消电子设备100的抖动，实现防抖。陀螺仪传感器180B还可以用于导航，体感游戏场景。
气压传感器180C用于测量气压。在一些实施例中，电子设备100通过气压传感器180C测得的气压值计算海拔高度，辅助定位和导航。
磁传感器180D包括霍尔传感器。电子设备100可以利用磁传感器180D检测翻盖皮套的开合。在一些实施例中，当电子设备100是翻盖机时，电子设备100可以根据磁传感器180D检测翻盖的开合。进而根据检测到的皮套的开合状态或翻盖的开合状态，设置翻盖自动解锁等特性。
加速度传感器180E可检测电子设备100在各个方向上(一般为三轴)加速度的大小。当电子设备100静止时可检测出重力的大小及方向。还可以用于识别电子设备100姿态，应用于横竖屏切换，计步器等应用。
距离传感器180F，用于测量距离。电子设备100可以通过红外或激光测量距离。在一些实施例中，拍摄场景，电子设备100可以利用距离传感器180F测距以实现快速对焦。
接近光传感器180G可以包括例如发光二极管(LED)和光检测器，例如光电二极管。发光二极管可以是红外发光二极管。电子设备100通过发光二极管向外发射红外光。电子设备100使用光电二极管检测来自附近物体的红外反射光。当检测到充分的反射光时，可以确定电子设备100附近有物体。当检测到不充分的反射光时，电子设备100可以确定电子设备100附近没有物体。电子设备100可以利用接近光传感器180G检测用户手持电子设备100贴近耳朵通话，以便自动熄灭屏幕达到省电的目的。接近光传感器180G也可用于皮套模式，口袋模式自动解锁与锁屏。
环境光传感器180L用于感知环境光亮度。电子设备100可以根据感知的环境光亮度自适应调节显示屏194亮度。环境光传感器180L也可用于拍照时自动调节白平衡。环境光传感器180L还可以与接近光传感器180G配合，检测电子设备100是否在口袋里，以防误触。
指纹传感器180H用于采集指纹。电子设备100可以利用采集的指纹特性实现指纹解锁，访问应用锁，指纹拍照，指纹接听来电等。
温度传感器180J用于检测温度。在一些实施例中，电子设备100利用温度传感器180J检测的温度，执行温度处理策略。例如，当温度传感器180J上报的温度超过阈值，电子设备100执行降低位于温度传感器180J附近的处理器的性能，以便降低功耗实施热保护。在另一些实施例中，当温度低于另一阈值时，电子设备100对电池142加热，以避免低温导致电子 设备100异常关机。在其他一些实施例中，当温度低于又一阈值时，电子设备100对电池142的输出电压执行升压，以避免低温导致的异常关机。
触摸传感器180K，也称“触控面板”。触摸传感器180K可以设置于显示屏194，由触摸传感器180K与显示屏194组成触摸屏，也称“触控屏”。触摸传感器180K用于检测作用于其上或附近的触摸操作。触摸传感器可以将检测到的触摸操作传递给应用处理器，以确定触摸事件类型。可以通过显示屏194提供与触摸操作相关的视觉输出。在另一些实施例中，触摸传感器180K也可以设置于电子设备100的表面，与显示屏194所处的位置不同。
骨传导传感器180M可以获取振动信号。在一些实施例中，骨传导传感器180M可以获取人体声部振动骨块的振动信号。骨传导传感器180M也可以接触人体脉搏，接收血压跳动信号。在一些实施例中，骨传导传感器180M也可以设置于耳机中，结合成骨传导耳机。音频模块170可以基于所述骨传导传感器180M获取的声部振动骨块的振动信号，解析出语音信号，实现语音功能。应用处理器可以基于所述骨传导传感器180M获取的血压跳动信号解析心率信息，实现心率检测功能。
按键190包括开机键，音量键等。按键190可以是机械按键。也可以是触摸式按键。电子设备100可以接收按键输入，产生与电子设备100的用户设置以及功能控制有关的键信号输入。
马达191可以产生振动提示。马达191可以用于来电振动提示，也可以用于触摸振动反馈。例如，作用于不同应用(例如拍照，音频播放等)的触摸操作，可以对应不同的振动反馈效果。作用于显示屏194不同区域的触摸操作，马达191也可对应不同的振动反馈效果。不同的应用场景(例如：时间提醒，接收信息，闹钟，游戏等)也可以对应不同的振动反馈效果。触摸振动反馈效果还可以支持自定义。
指示器192可以是指示灯，可以用于指示充电状态，电量变化，也可以用于指示消息，未接来电，通知等。
SIM卡接口195用于连接SIM卡。SIM卡可以通过插入SIM卡接口195，或从SIM卡接口195拔出，实现和电子设备100的接触和分离。电子设备100可以支持1个或N个SIM卡接口，N为大于1的正整数。SIM卡接口195可以支持Nano SIM卡，Micro SIM卡，SIM卡等。同一个SIM卡接口195可以同时插入多张卡。所述多张卡的类型可以相同，也可以不同。SIM卡接口195也可以兼容不同类型的SIM卡。SIM卡接口195也可以兼容外部存储卡。电子设备100通过SIM卡和网络交互，实现通话以及数据通信等功能。在一些实施例中，电子设备100采用eSIM，即：嵌入式SIM卡。eSIM卡可以嵌在电子设备100中，不能和电子设备100分离。
应当理解的是，图18所示电子设备100仅是一个范例，并且电子设备100可以具有比图18中所示的更多的或者更少的部件，可以组合两个或多个的部件，或者可以具有不同的部件配置。图18中所示出的各种部件可以在包括一个或多个信号处理和/或专用集成电路在内的硬件、软件、或硬件和软件的组合中实现。
其中，电子设备200的结构可以与电子设备100的结构相同或相似，关于电子设备200的结构的相关内容可以参照图18所示的电子设备100的结构的相关文字描述，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当 使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。
以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (17)

  1. 一种应用组件显示方法，应用于第一电子设备，其特征在于，所述方法包括：
    所述第一电子设备接收来自第二电子设备的应用组件信息，所述应用组件信息包括第一应用组件的信息，所述第一应用组件是所述第二电子设备的应用组件；
    所述第一电子设备基于所述第一应用组件的信息显示所述第一应用组件。
  2. 根据权利要求1所述的方法，其特征在于，所述第一应用组件的信息包括所述第一应用组件的安装包，所述第一电子设备基于所述第一应用组件的信息显示所述第一应用组件，具体包括：
    所述第一电子设备基于所述第一应用组件的安装包显示所述第一应用组件；
    其中，所述第一应用组件上显示有第一内容，所述第一内容是所述第一电子设备基于第一数据生成的，所述第一数据是所述第一电子设备在所述第一应用组件的安装包中获取的。
  3. 根据权利要求1所述的方法，其特征在于，所述第一应用组件的信息包括所述第一应用组件的安装包和第二数据，所述第一电子设备基于所述第一应用组件的信息显示所述第一应用组件，具体包括：
    所述第一电子设备基于所述第一应用组件的安装包和所述第二数据安装并显示所述第一应用组件；
    其中，所述第一应用组件上显示有第二内容，所述第二内容是所述第一电子设备基于所述第二数据生成的，所述第二数据是所述第二电子设备在运行所述第一应用组件时生成的。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，在所述第一电子设备基于所述第一应用组件的信息显示所述第一应用组件之后，所述方法还包括：
    所述第一电子设备检测到用户将所述第一应用组件添加到桌面的操作，所述第一电子设备在所述桌面显示所述第一应用组件。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，在所述第一电子设备基于所述第一应用组件的信息显示所述第一应用组件之前，所述方法还包括：
    所述第一电子设备检测到用户打开应用组件管理界面的操作，响应于所述操作，所述第一电子设备显示所述应用组件管理界面，其中，所述应用组件管理界面包括标识选项，所述标识选项包括第二电子设备的标识选项；
    所述第一电子设备检测到用户针对所述第二电子设备的标识选项的操作；
    所述第一电子设备基于所述第一应用组件的信息显示所述第一应用组件，具体包括：响应于所述操作，所述第一电子设备在所述应用组件管理界面基于所述第一应用组件的信息显示所述第一应用组件。
  6. 根据权利要求1-4任一项所述的方法，其特征在于，在所述第一电子设备基于所述第一应用组件的信息显示所述第一应用组件之前，所述方法还包括：
    所述第一电子设备检测到用户打开应用组件管理界面的操作，响应于所述操作，所述第一电子设备显示所述应用组件管理界面；
    所述第一电子设备基于所述第一应用组件的信息显示所述第一应用组件，具体包括：
    所述第一电子设备在所述应用组件管理界面基于所述第一应用组件的信息显示所述第一应用组件；其中，所述应用组件管理界面还显示有第二应用组件，所述第二应用组件是所述第一电子设备的应用组件。
  7. 根据权利要求1-4任一项所述的方法，其特征在于，在所述第一电子设备基于第一应用组件的信息显示所述第一应用组件之前，所述方法还包括：
    所述第一电子设备检测到用户在搜索界面上搜索关键字的操作，响应于所述操作，所述第一电子设备获取与所述关键字相关的应用组件信息，所述与所述关键字相关的应用组件信息包括所述第一应用组件的信息；
    所述第一电子设备基于第一应用组件的信息显示所述第一应用组件，具体包括：
    所述第一电子设备在所述搜索界面基于第一应用组件的信息显示所述第一应用组件。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，在所述第一电子设备接收来自第二电子设备的应用组件信息之前，所述方法还包括：
    所述第一电子设备检测到预设条件被触发，所述预设条件包括以下任意一项：用户打开应用组件管理界面的操作、用户在搜索界面上搜索关键字的操作、开机、重启、锁屏解锁、系统更新；
    响应于所述预设条件被触发，所述第一电子设备向所述第二电子设备发送第一请求，所述第一请求用于指示所述第二电子设备向所述第一电子设备发送所述应用组件信息。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述第一电子设备在所述第一应用组件上显示所述第二电子设备的标识。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，在所述第一电子设备接收来自第二电子设备的应用组件信息之前，所述方法还包括：
    所述第一电子设备与所述第二电子设备建立通信连接，并确认所述第二电子设备为可信设备。
  11. 一种应用组件显示方法，应用于第二电子设备，其特征在于，所述方法包括：
    所述第二电子设备接收来自第一电子设备的第一请求，所述第一请求用于指示所述第二电子设备向所述第一电子设备发送应用组件信息，其中，所述应用组件信息包括第一应用组件的信息，所述第一应用组件是所述第二电子设备的应用组件；
    所述第二电子设备向所述第一电子设备发送所述应用组件信息。
  12. 根据权利要求11所述的方法，其特征在于，所述第一应用组件的信息包括所述第一应用组件的安装包。
  13. 根据权利要求12所述的方法，其特征在于，所述第一应用组件的信息还包括第二数据，在所述第二电子设备向所述第一电子设备发送所述应用组件信息之前，所述方法还包括：
    所述第二电子设备运行所述第一应用组件，并生成所述第二数据。
  14. 根据权利要求11-13任一项所述的方法，其特征在于，在所述第二电子设备接收来自第一电子设备的第一请求之前，所述方法还包括：
    所述第二电子设备与所述第一电子设备建立通信连接，并确认所述第一电子设备为可信设备。
  15. 一种通信系统，其特征在于，所述通信系统包括：第一电子设备和第二电子设备；
    所述第二电子设备用于向所述第一电子设备发送应用组件信息；
    所述第一电子设备用于接收所述应用组件信息，所述应用组件信息包括第一应用组件的信息，所述第一应用组件是所述第二电子设备的应用组件；
    所述第一电子设备还用于基于所述第一应用组件的信息显示所述第一应用组件。
  16. 一种电子设备，其特征在于，所述电子设备包括一个或多个处理器和一个或多个存储器；其中，所述一个或多个存储器与所述一个或多个处理器耦合，所述一个或多个存储器用于存储计算机程序代码，所述计算机程序代码包括计算机指令，当所述一个或多个处理器执行所述计算机指令时，使得所述电子设备执行如权利要求1-10或11-14中任一项所述的方法。
  17. 一种计算机存储介质，其特征在于，所述计算机存储介质存储有计算机程序，所述计算机程序包括程序指令，当所述程序指令在电子设备上运行时，使得所述电子设备执行如权利要求1-10或11-14中任一项所述的方法。
PCT/CN2023/070583 2022-01-28 2023-01-05 应用组件管理方法及相关设备 WO2023142935A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210109589.3A CN116560535A (zh) 2022-01-28 2022-01-28 应用组件管理方法及相关设备
CN202210109589.3 2022-01-28

Publications (1)

Publication Number Publication Date
WO2023142935A1 true WO2023142935A1 (zh) 2023-08-03

Family

ID=87470551

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/070583 WO2023142935A1 (zh) 2022-01-28 2023-01-05 应用组件管理方法及相关设备

Country Status (2)

Country Link
CN (1) CN116560535A (zh)
WO (1) WO2023142935A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102546736A (zh) * 2010-12-08 2012-07-04 中国电信股份有限公司 widget应用之间的通信方法和系统
CN104243535A (zh) * 2013-05-10 2014-12-24 英特尔移动通信有限责任公司 用于在第一设备和第二设备之间传送数据的方法
US10564988B1 (en) * 2017-12-22 2020-02-18 Intuit Inc. Deploying cross-platform applications on mobile devices with native and web components
CN111221845A (zh) * 2019-12-31 2020-06-02 华为技术有限公司 一种跨设备信息搜索方法及终端设备
CN112083867A (zh) * 2020-07-29 2020-12-15 华为技术有限公司 一种跨设备的对象拖拽方法及设备
CN112231025A (zh) * 2019-03-06 2021-01-15 华为终端有限公司 Ui组件显示的方法及电子设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102546736A (zh) * 2010-12-08 2012-07-04 中国电信股份有限公司 widget应用之间的通信方法和系统
CN104243535A (zh) * 2013-05-10 2014-12-24 英特尔移动通信有限责任公司 用于在第一设备和第二设备之间传送数据的方法
US10564988B1 (en) * 2017-12-22 2020-02-18 Intuit Inc. Deploying cross-platform applications on mobile devices with native and web components
CN112231025A (zh) * 2019-03-06 2021-01-15 华为终端有限公司 Ui组件显示的方法及电子设备
CN111221845A (zh) * 2019-12-31 2020-06-02 华为技术有限公司 一种跨设备信息搜索方法及终端设备
CN112083867A (zh) * 2020-07-29 2020-12-15 华为技术有限公司 一种跨设备的对象拖拽方法及设备

Also Published As

Publication number Publication date
CN116560535A (zh) 2023-08-08

Similar Documents

Publication Publication Date Title
WO2021013158A1 (zh) 显示方法及相关装置
KR102470275B1 (ko) 음성 제어 방법 및 전자 장치
WO2020192714A1 (zh) 显示设备控制页面的方法、相关装置及系统
WO2020259452A1 (zh) 一种移动终端的全屏显示方法及设备
WO2020108356A1 (zh) 一种应用显示方法及电子设备
WO2021000804A1 (zh) 锁定状态下的显示方法及装置
WO2020155014A1 (zh) 智能家居设备分享系统、方法及电子设备
WO2020238728A1 (zh) 智能终端的登录方法及电子设备
CN113885759A (zh) 通知消息处理方法、设备、系统及计算机可读存储介质
WO2021253975A1 (zh) 应用程序的权限管理方法、装置和电子设备
CN113961157B (zh) 显示交互系统、显示方法及设备
WO2021052204A1 (zh) 基于通讯录的设备发现方法、音视频通信方法及电子设备
WO2022068819A1 (zh) 一种界面显示方法及相关装置
WO2022068483A1 (zh) 应用启动方法、装置和电子设备
WO2020224447A1 (zh) 一种在联系人中添加智能家居设备的方法及系统
WO2021036898A1 (zh) 折叠屏设备中应用打开方法及相关装置
WO2021159746A1 (zh) 文件共享方法、系统及相关设备
WO2021218429A1 (zh) 应用窗口的管理方法、终端设备及计算机可读存储介质
CN114124980B (zh) 一种启动应用的方法、设备、系统、终端及存储介质
WO2022253158A1 (zh) 一种用户隐私保护方法及装置
WO2022228180A1 (zh) 一种应用的管理方法和电子设备
CN115022982B (zh) 多屏协同无感接入方法、电子设备及存储介质
WO2022062902A1 (zh) 一种文件传输方法和电子设备
WO2023142935A1 (zh) 应用组件管理方法及相关设备
WO2023142940A1 (zh) 应用组件分享方法及相关设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23745820

Country of ref document: EP

Kind code of ref document: A1