Card cross-device interaction method and electronic device

Abstract

A card cross-device interaction method and an electronic device, the method comprising: a first electronic device displaying preview information of at least one card of a second electronic device, the preview information of the at least one card comprising preview information of a first card, the first card belonging to a first application in the second electronic device; the first electronic device receiving a first operation for the preview information of the first card; in response to the first operation, the first electronic device sending a first request for adding the first card to the second electronic device; the first electronic device obtaining card information corresponding to the first card sent by the second electronic device; based on the card information corresponding to the first card, the first electronic device adding the first card, thereby realizing component-level cross-device interaction between the first electronic device and the second electronic device.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202211059255.6, filed on August 31, 2022, entitled "A Card Cross-Device Interaction Method and Electronic Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of electronic technology, and in particular to a card cross-device interaction method and electronic device. Background Technology

[0004] As the variety and number of smart devices increase, more and more users are demanding richer and more flexible inter-device interactions. Current inter-device interaction methods are relatively costly, requiring customized development of interactive applications for each device, which is labor-intensive and has significant limitations.

[0005] Currently, electronic devices can only achieve cross-device interaction at the application level, while in-application components, such as widgets, application micro-widgets, or cards, cannot achieve cross-device interaction. Summary of the Invention

[0006] This application provides a card cross-device interaction method and an electronic device for realizing cross-device interaction at the application component level.

[0007] Firstly, this application provides a method for cross-device card interaction. The method includes: a first electronic device displaying preview information of at least one card from a second electronic device, the preview information of the at least one card including preview information of a first card, the first card belonging to a first application in the second electronic device; the first electronic device receiving a first operation on the preview information of the first card; responding to the first operation, the first electronic device sending a first request to the second electronic device to add the first card; the first electronic device obtaining card information corresponding to the first card sent by the second electronic device; and adding the first card based on the card information corresponding to the first card. This method enables component-level cross-device interaction between the first and second electronic devices without requiring the same application to be installed on both devices.

[0008] In one possible implementation, after the first electronic device obtains the card information corresponding to the first card sent by the second electronic device, the first electronic device can also display the card information corresponding to the first card, so that the user can see the card information corresponding to the first card.

[0009] In one possible implementation, the first electronic device may also receive a second operation on the first card; in response to the second operation, the first electronic device deletes the first card and sends a second request to the second electronic device to delete the first card; the first electronic device receives a deletion completion message from the second electronic device, which is used to notify the second electronic device that the cache information related to the first card has been deleted, so that after the first electronic device deletes the first card, the cache space on the second electronic device can also be released.

[0010] In one possible implementation, the first electronic device can further receive a third operation on the first card. In response to the third operation, the first electronic device sends a third request to the second electronic device for updating the first card. The first electronic device receives card information from the second electronic device for updating the first card, and updates the first card based on the card information. This method enables the first card on the first electronic device to be updated synchronously after the first card on the second electronic device is updated.

[0011] In one possible implementation, before the first electronic device displays preview information of at least one card from the second electronic device, the method further includes: the first electronic device receiving a fourth operation; in response to the fourth operation, the first electronic device sending a fourth request to the second electronic device for querying the card; and the first electronic device receiving preview information of at least one card from the second electronic device. In this way, preview information of at least one card on the second electronic device can be synchronized on the first electronic device through querying.

[0012] In one possible implementation, the first electronic device and the second electronic device are located in the same network, so that the first electronic device and the second electronic device can communicate directly, providing security for information transmission.

[0013] In one possible implementation, the preview information of the first card is the same as the card information displayed on the first card; or, the preview information of the first card is different from the card information displayed on the first card.

[0014] Secondly, this application provides a method for cross-device card interaction. The method includes: a first electronic device displaying a card preview interface, the card preview interface including card information of at least one card from a second electronic device, the card information of the at least one card including card information of a first card, the first card belonging to a first application in the second electronic device; the first electronic device receiving a fifth operation on the card information of the first card; and in response to the fifth operation, the first electronic device adding the first card and displaying the first card on its desktop. This method enables component-level cross-device interaction between the first and second electronic devices, and cross-device interaction can be achieved without installing the same application on both devices.

[0015] Thirdly, this application provides a method for cross-device card interaction. The method includes: a first electronic device displaying a first card from a first application of a second electronic device; the first electronic device receiving a first operation on the first card; in response to the first operation, the first electronic device sending a card add request to the second electronic device; the first electronic device obtaining card information corresponding to the first card sent by the second electronic device; and the first electronic device displaying the first card. This method allows the card from the second electronic device to be displayed on the first electronic device, achieving component-level cross-device interaction without requiring the first application to be installed on the first electronic device.

[0016] In one possible implementation, the first electronic device does not have the first application installed.

[0017] Fourthly, this application also provides an apparatus comprising modules / units for performing any of the possible design methods described in any of the foregoing aspects. These modules / units can be implemented in hardware or by hardware executing corresponding software.

[0018] Fifthly, this application provides an electronic device including a processor and a memory. The memory stores one or more computer programs; when the one or more computer programs stored in the memory are executed by the processor, the electronic device is able to implement the foregoing aspects and any possible design methods related to those aspects.

[0019] Sixthly, this application also provides a computer-readable storage medium comprising a computer program that, when run on a terminal, causes the terminal to perform the methods of the foregoing aspects and any possible design involved in each aspect.

[0020] In a seventh aspect, this application also provides a method comprising a computer program product that, when the computer program product is run on a terminal, causes the terminal to perform the foregoing aspects and any possible design relating to those aspects. Attached Figure Description

[0021] Figure 1 This is a schematic diagram illustrating the application migration in existing technologies;

[0022] Figure 2 This is a schematic diagram illustrating the application migration in existing technologies;

[0023] Figure 3 This is a schematic diagram illustrating the application migration in existing technologies;

[0024] Figure 4 This is a schematic diagram of a card cross-device interaction system provided in an embodiment of this application;

[0025] Figure 5 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0026] Figure 6 A scenario diagram provided for an embodiment of this application;

[0027] Figure 7 This is a schematic diagram of a card cross-device interaction system provided in an embodiment of this application;

[0028] Figure 8 This is a schematic diagram of the card cross-device interaction method provided in an embodiment of this application;

[0029] Figure 9 This is a schematic diagram of the card cross-device interaction method provided in an embodiment of this application;

[0030] Figure 10 This is a schematic diagram of the card information acquisition process provided in an embodiment of this application;

[0031] Figure 11 This is a schematic diagram of the card adding process provided in an embodiment of this application;

[0032] Figure 12 This is a schematic diagram of the card deletion process provided in an embodiment of this application;

[0033] Figure 13 This is a schematic diagram of the card update process provided in an embodiment of this application;

[0034] Figure 14 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0036] First, some of the terms used in this application will be explained to enable those skilled in the art to understand them.

[0037] (1) Cards, also known as widgets or micro-components, provide a more granular service capability than applications (APPs). They directly display the services or content that users care about most in the form of interactive cards. Cards can be embedded in various APPs or interactive scenarios to better meet user needs. A card can be at least one page in a quick app or its corresponding native APP. When a user clicks on a card, they can jump to a service page in the corresponding quick app or APP. In addition, cards can also implement some functions of quick apps or their corresponding native APPs. For example, a music card can play, previous song, next song, or jump to the music app interface.

[0038] A card corresponds to a portion of the application's service functions. The application provider can break down the application's services into multiple service modules, with each service module corresponding to a card. Different cards are then pushed to users based on different service scenarios. Unless otherwise specified, the "application" referred to in this application can be a quick app or a native app; this application embodiment does not impose any limitations.

[0039] (2) The at least one involved in the embodiments of this application includes one or more; wherein, more than two means two or more.

[0040] In addition, it should be understood that in the description of this application, the words "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance or order.

[0041] To better understand the technical solutions provided in the embodiments of this application, the application scenarios of the embodiments of this application will be introduced first below.

[0042] With the rapid development of smart devices, the variety and number of smart devices in home, office, and learning scenarios are increasing. More and more users are demanding richer and more flexible inter-device interaction. For example, in a home setting, users may want to control TV applications via their mobile phones or tablets. This can be achieved by migrating TV applications to their phones or tablets, allowing them to control TV applications through the migrated apps. Currently, the main solutions for cross-device interaction are as follows.

[0043] Option 1, such as Figure 1As shown, after device A establishes a connection with device B, the application on device A is transferred to device B via local transfer or cloud download, thus achieving cross-device application migration. In this first scheme, the transfer granularity is relatively large, requiring an application-level connection, which impacts efficiency.

[0044] Option 2, such as Figure 2 As shown, both device A and device B have the same application 1 installed. After device A and device B establish a connection, application 1 on device A transmits business parameters to application 1 on device B. Upon receiving the parameters, application 1 on device B changes the interface to enable cross-device startup. This solution is not flexible enough, requiring both devices to have the same application, which limits its application scenarios.

[0045] Option 3, such as Figure 3 As shown, after device A and device B establish a connection, device A takes a screenshot in real time and then sends the screenshot data to device B. Device B directly displays the screenshot image transmitted by A. As long as the transmission frequency is high enough, a mirrored display of the screen can be achieved. This solution can only display images in a mirrored manner, occupies two devices, and requires the real-time transmission of a large amount of information, making it unstable.

[0046] All of the above solutions can only enable cross-device interaction of applications, while in-application components, such as widgets, application micro-widgets, or cards, cannot achieve cross-device interaction.

[0047] To address the aforementioned issues, this application provides a method for cross-device card interaction. A first electronic device displays at least one preview of information from a second electronic device. The preview information of the at least one card includes preview information of a first card, which belongs to a first application within the second electronic device. Then, the first electronic device receives a first operation on the preview information of the first card and, in response to the first operation, sends a first request to the second electronic device to add the first card. Subsequently, the first electronic device obtains card information corresponding to the first card sent by the second electronic device, and adds the first card based on this card information. This method enables component-level cross-device interaction between the first and second electronic devices without requiring them to have the same application installed.

[0048] The technical solutions in this application embodiment can be applied to card-based cross-device interaction systems. Figure 4 This can be a schematic diagram of a card-to-device interaction system in this application embodiment. The card-to-device interaction system may include multiple electronic devices, and any two electronic devices can communicate through a distributed communication system. For example, such as... Figure 4The diagram shows only the first electronic device and the second electronic device, which can communicate with each other to obtain each other's card information.

[0049] In other embodiments, the card-to-device interaction system may also include a server, such as Figure 4 As shown, both the first electronic device and the second electronic device can communicate with the server. The card information on both the first electronic device and the second electronic device can be uploaded to the server. When the first electronic device needs to obtain the card information on the second electronic device, the first electronic device can obtain the card information of the second electronic device from the server.

[0050] It should be noted that, in the embodiments of this application, as Figure 4 The card-based cross-device interaction system shown may also include more electronic devices, such as third electronic devices, fourth electronic devices, etc. The embodiments of this application do not limit the number of electronic devices.

[0051] The electronic devices involved in the embodiments of this application, such as... Figure 4 The first or second electronic device can be any electronic device that supports service card functionality. For example, it can be a portable electronic device containing functions such as a personal digital assistant and / or music player, such as a mobile phone, tablet, or wearable device with wireless communication capabilities (such as a smartwatch). Exemplary embodiments of the portable electronic device include, but are not limited to, those equipped with... Alternatively, it can be a portable electronic device with another operating system. The aforementioned portable electronic device can also be other portable electronic devices, such as a laptop computer with a touch-sensitive surface (e.g., a touch panel). It should also be understood that in some other embodiments of this application, the aforementioned electronic device may not be a portable electronic device, but rather a desktop computer with a touch-sensitive surface (e.g., a touch panel).

[0052] Typically, electronic devices support a variety of applications. These may include one or more of the following: travel apps, drawing apps, presentation apps, word processing apps, game apps, phone apps, video player apps, music player apps, email apps, shopping apps, instant messaging apps, photo management apps, camera apps, browser apps, calendar apps, clock apps, payment apps, and health management apps. Instant messaging apps, in particular, can be diverse, including SMS apps, MMS apps, various email apps, WeChat, Tencent QQ, WhatsApp Messenger, Line, Instagram, Kakao Talk, and DingTalk. Users can use instant messaging apps to send text, voice messages, images, video files, and other files to other contacts.

[0053] The applications supported by the electronic device can be native applications (apps) or quick apps; this application embodiment does not impose specific limitations. The electronic device can also support cards corresponding to these applications, such as cards corresponding to order logistics services in shopping applications, or cards corresponding to ticketing information in travel applications. Furthermore, in addition to supporting cards corresponding to installed applications, the electronic device can also support cards corresponding to applications that are not currently installed.

[0054] The following is a schematic diagram illustrating the structure of an electronic device used in this application, using a mobile phone as an example.

[0055] Please see Figure 5 The mobile phone 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0056] The processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors. The solution provided in this application embodiment can be implemented by the processor 110 controlling or calling other components. The controller may be the central nervous system and command center of the mobile phone 100. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0057] The mobile phone 100 can implement display functions through a GPU, a display screen 194, and an application processor. The display screen 194 is used to display images, videos, etc. For example, the display screen 194 can display the main interface of the terminal screen, or the lock screen interface, or the negative one screen interface, or the user interface of the system's built-in communication application, or the user interface of other third-party applications, and display the service cards described in the embodiments of this application on these display interfaces.

[0058] The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU performs mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information. For example, the GPU performs graphics rendering based on card information, data, etc., to generate the cards to be displayed.

[0059] The display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the mobile phone 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0060] The wireless communication function of mobile phone 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.

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

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

[0063] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0064] The wireless communication module 160 can provide solutions for wireless communication applications on the mobile phone 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0065] The charging management module 140 receives charging input from the charger. The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0066] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the mobile phone 100. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

[0067] The internal memory 121 can be used to store computer executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the mobile phone 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the mobile phone 100 (such as audio data, phonebook, etc.). Furthermore, the internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

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

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

[0070] The card cross-device interaction method provided in this application is applicable to scenarios such as a home environment with multiple smart home devices. If a user wants to operate a certain application on a smart home device using a mobile terminal, the service functions of that application on the smart home device can be migrated to the mobile terminal. For example, the mobile terminal can display a list of cards that all applications of the smart home device can provide. The card list includes preview information of at least one card. When the mobile terminal receives a click operation on a preview in the card list, in response to the click operation, it obtains a list of all card specifications that the application of the smart home device to which the preview belongs can provide, and then selects one card specification to add to the desktop. A card belonging to the smart home device is generated on the mobile terminal's desktop, thereby facilitating the user to operate the smart home device's application through the card migrated to the mobile terminal.

[0071] In some embodiments, the preview information of the card may not be the actual card information, but can be understood as a default card template. For example, consider displaying a preview of a weather card on a smart TV on a mobile phone. If the current weather card on the smart TV displays "Shanghai, 28℃," the mobile phone displays a preview template for that weather card, which includes a default city name (e.g., Beijing) and a default temperature (e.g., 25℃). Even after the weather card on the smart TV is updated, for example to "Shanghai, 15℃," the mobile phone will still display "Beijing, 25℃." If the preview of the weather card is displayed on a laptop, it will also use the default card template: "Beijing, 25℃." Of course, the preview information of the weather card may not be the default place name and temperature; it can be represented by default text, default icons, or default images. This application does not limit the specific form of the card's preview information.

[0072] In other embodiments, the card preview information can also be the actual card information, without limitation. For example, when mobile phone 100 enters the card preview interface, mobile phone 100 can obtain the card information of applications of other electronic devices to display the actual card information corresponding to that application on the card preview interface.

[0073] Figure 6An exemplary set of user interfaces is shown. A mobile terminal displays a desktop interface 601, which may include multiple applications and cards. When the mobile terminal receives an operation, such as a swipe operation from the lower left corner of the screen of an electronic device towards the center of the screen, a full service interface 602 is displayed in response to the operation. The full service interface 602 displays cross-device services, such as preview information of cards for various applications on the mobile terminal itself. The full service interface 602 may also include device information for a smart screen in the living room and a mobile smart screen in the kitchen. When the mobile terminal displays the full service interface 602 including card information for various applications on its own device, and then receives a swipe operation to the right, the mobile terminal switches to displaying a user interface 603 in response to the swipe operation. The user interface 603 includes preview information of cards for various applications on the smart screen in the living room.

[0074] In some other embodiments, if a rightward swipe operation is received again, the user interface switches to displaying preview information of various application cards on the mobile smart screen in the kitchen. For example, user interface 603 includes preview information of Huawei Video cards. When the mobile terminal receives a click operation on the preview information of Huawei Video cards, user interface 604 is displayed. User interface 604 includes a list of Huawei Video cards that can be provided by the smart screen in the living room. Huawei Video cards can have different specifications, including card size, card refresh time interval, card name, card description, and other card customization information. User interface 604 may also include a control for adding to the desktop. When the mobile terminal receives a click operation on the control for adding to the desktop, a card belonging to the Huawei Video application on the smart screen in the living room is generated and added to the desktop application. The mobile terminal then displays desktop interface 605, which includes the Huawei Video application card.

[0075] In the above scenario, before displaying the card list information that all applications on the smart home device can provide on the mobile terminal, the mobile terminal can first obtain the card list information that all applications on the smart home device can provide. There are various ways to obtain the card list information, including but not limited to the possible implementation methods provided below.

[0076] One possible implementation is that each smart home device can upload a list of cards that all its applications can provide to a cloud server, and then the mobile terminal can obtain the list of cards that all applications of each smart home device can provide from the server.

[0077] In a second possible implementation, after a mobile terminal discovers smart home devices within the same network, it can obtain a list of cards available from all applications on those devices. Here, the "same network" identifier is connected within the same network environment. When the cards on a smart home device within the network are updated, the corresponding cards on the mobile device are updated synchronously. In this second implementation, the mobile terminal and smart home devices within the same network can communicate directly, resulting in higher security.

[0078] In the above scenario, the mobile terminal is the electronic device of the card user, and the smart home device is the electronic device of the card provider. In the embodiments of this application, the card user is an application that needs to display the card, and the card provider is an application that provides card display and business logic. It may or may not have the ability to display the card.

[0079] Please see Figure 7 This is a schematic diagram of the system architecture of the card cross-device interaction system provided in the embodiments of this application.

[0080] like Figure 7 As shown, the system architecture includes electronic devices for the card user and electronic devices for the card provider, wherein the electronic devices for the card user are, for example, those described above. Figure 6 The mobile terminal in the scenario shown, and the electronic device of the card provider, are exemplified by the one described above. Figure 6 Smart home devices in the scene shown.

[0081] like Figure 7 As shown, both the electronic devices of the card user and the electronic devices of the card provider can include card management services, package management systems, meta-capability component management systems, and distributed communication systems. Among them:

[0082] Card management service is used to manage functions such as adding, querying, updating and deleting cards, as well as storing cached card information.

[0083] The meta-capability component management system is responsible for the startup and lifecycle management of the applications that host the cards.

[0084] The package management system is used to manage card specifications, application information, resource information, etc.

[0085] A distributed communication system is used to establish cross-device links and obtain data information from cross-device cards.

[0086] Based on the above Figure 7 The card-based cross-device interaction system shown is Figure 8 An exemplary flowchart illustrating a method for cross-device card interaction is provided. For ease of distinction, Figure 8The card management service in the electronic device of the card user is referred to as the first card management service, and the card management service in the electronic device of the card provider is referred to as the second card management service; the package management system in the electronic device of the card user is referred to as the first package management system, and the package management system in the electronic device of the card provider is referred to as the second package management system.

[0087] like Figure 8 As shown, the card cross-device interaction method includes the following steps:

[0088] S1, the card usage direction, the first package management system queries the card list and card specification information.

[0089] S2, the first package management system synchronizes the card list and card specification information of the second electronic device through a distributed communication system.

[0090] The card list includes preview information for at least one card, card specifications such as card name, card refresh rate, card resources, card size, etc., where card size is such as square or rectangular, four-grid or six-grid, etc.

[0091] exist Figure 8 The example only shows one second electronic device. The first packet management system synchronizes the card list and card specification information of all applications included in the second electronic device through a distributed communication system. In some other embodiments, when multiple second electronic devices are in the same network as the first electronic device, the first packet management system synchronizes the card list and card specification information of the applications included in the multiple second electronic devices through a distributed communication system.

[0092] S3, the card uses the first card management service to send an add card request.

[0093] For example, the card provider is a video player application, and the card user is a desktop application. For instance, the add card request is used to request the addition of a remote control card for the video player application.

[0094] S4, the first card management service obtains the remote interface proxy of the card provider through a distributed communication system.

[0095] S5, the first card management service communicates directly with the card provider through a remote interface proxy to perform card addition operations.

[0096] For example, taking a video player application as the card provider and a desktop application as the card user, the card addition request in S3 above is used to request the addition of a remote control card for the video player application. The card addition operation in S5 can be implemented in the following way: the first card management service obtains the layout information and display data information of the remote control card through a remote interface proxy, and then the first card management service returns the obtained layout information and display data information of the remote control card to the card user. The card user renders and generates the remote control card based on the layout information and display data information of the remote control card.

[0097] S6: After the card user adds a card, the card is displayed.

[0098] Taking the remote control card as an example, users can use the remote control card added by the card user. The remote control card includes a pause / play button to operate the video player application provided by the card provider. For example, if the video player application on the second electronic device is playing a video, the user can click the pause / play button on the remote control card on the first electronic device to pause the video playback on the second electronic device. Clicking the pause / play button again will allow the video player application on the second electronic device to resume playing the video.

[0099] After S6, the first card management service can also perform card deletion and update operations through a remote interface proxy. Taking the case where a card user adds a remote control card from a card provider as an example, the deletion operation can be implemented as follows: When the card user receives an operation to delete the remote control card, it deletes the card user's remote control card and sends a deletion message to the card provider through the remote interface proxy. This deletion message can carry the identifier of the remote control card to be deleted. After receiving the deletion message, the card provider deletes the layout information and display data information of the remote control card locally cached in the second electronic device to which the card provider belongs.

[0100] The following example uses the card user's electronic device as the first electronic device and the card provider's electronic device as the remote electronic device to introduce the card cross-device interaction method provided in this application.

[0101] like Figure 9 As shown, the card cross-device interaction method includes the following steps:

[0102] Step 901: The first electronic device displays preview information of at least one card from at least one remote electronic device.

[0103] Before step 901, the first electronic device can communicate with at least one remote electronic device through a distributed communication system to obtain preview information of at least one card of at least one remote electronic device. Alternatively, it can first obtain the remote interface proxy of each remote electronic device through the distributed communication system, and then communicate directly with the corresponding remote electronic device through the remote interface proxy of each remote electronic device to obtain the preview information of the card of the corresponding remote electronic device.

[0104] When there is a remote electronic device, the first electronic device can obtain preview information of at least one card on the remote electronic device; when there are multiple remote electronic devices, the first electronic device can obtain preview information of at least one card on multiple remote electronic devices.

[0105] Before step 901 above, the first electronic device can first obtain preview information of at least one card from at least one remote electronic device. The following example, using device A as the first electronic device and devices B, C, ..., N as the at least one remote electronic device, illustrates the process of obtaining preview information of at least one card from at least one remote electronic device in step 901. Figure 10 As shown, the acquisition process includes the following steps:

[0106] S1, the card uses the direction package management system to initiate a card query request.

[0107] In some embodiments, a card query request can be triggered by a user action, such as when the first electronic device receives a click action from an application targeting the card user, triggering the card query request; or, for example, when the user interface of the first electronic device has a control that can trigger a card query request, a card query request is triggered after a click action is received on the control; or, for example, when the first electronic device is connected to a network, it can trigger a card query request, after which the first electronic device can send the card query request to a second electronic device that is in the same network as the first electronic device.

[0108] This card query request is used to query the card list and card specification information of all devices in the network.

[0109] S2, the packet management system will send a request to the distributed communication system to synchronize and query the card list and card specification information of all devices in the network.

[0110] S3, after synchronizing all card lists and card specification information, the distributed communication system transmits the device information and the card specification information of the corresponding card to the requesting device A.

[0111] S4, the packet management system, transmits the card preview information and card specification information returned by the distributed communication system to the card user.

[0112] This example demonstrates how a single device can obtain preview information and card specification information from other devices within the network, which can then be used for subsequent operations on specific cards.

[0113] In this embodiment of the application, the card to be added to the first electronic device is called the first card, the remote electronic device to which the first card belongs is called the second electronic device, at least one remote electronic device in the above step 901 includes the second electronic device, the preview information of at least one card includes the preview information of the first card, and the first card belongs to the first application in the second electronic device.

[0114] Step 902: The first electronic device receives a first operation for preview information of the first card.

[0115] The first operation can be a click operation, or it can be another operation that triggers a request to add the first card to a second electronic device. The type of the first operation is not limited here.

[0116] Step 903: In response to the first operation, the first electronic device sends a first request to the second electronic device.

[0117] The first request is used to add a first card from a second electronic device to a first electronic device. For example, the first request carries the identifier of the application carrying the first card and the identifier of the first card itself. If it is a repeat request to add the first card, the first request may only carry the identifier of the first card.

[0118] In step 904, the second electronic device responds to the first request by sending the layout information and display data information corresponding to the first card to the first electronic device.

[0119] The layout information may include various layout identifiers, such as layout A, layout B, layout C, etc. For example, the resource information corresponding to layout A is a landscape image, and the resource information corresponding to layout B is a portrait image.

[0120] This displayed data information can, for example, show relevant parameters for a card.

[0121] Step 905: The first electronic device obtains the resource information corresponding to the first card.

[0122] For example, resource information may include, but is not limited to, image resources, layout resources, etc. If the first electronic device has local resource information corresponding to the first card, it can directly obtain the resource information corresponding to the first card from its local device. If the first electronic device does not have local resource information corresponding to the first card, it can obtain the resource information from the second electronic device through a distributed communication system.

[0123] Step 906: The first electronic device generates the first card based on the layout information, display data information and resource information corresponding to the first card.

[0124] Step 907: The first electronic device adds the first card.

[0125] In some other embodiments, the first electronic device may also display card information on a preview interface, and then add the first card after receiving the card information for the first card. It should be understood that adding the first card may include displaying the first card.

[0126] Through the above embodiments, component-level cross-device interaction can be achieved between the first electronic device and the second electronic device without requiring the first electronic device and the second electronic device to install the same application.

[0127] In some other embodiments, the first electronic device may also display the first card of the first application of the second electronic device. The first electronic device receives a first operation on the first card and then, in response to the first operation, sends a card add request to the second electronic device. The first electronic device obtains the card information corresponding to the first card sent by the second electronic device and displays the first card, thereby realizing cross-device interaction at the component level. Moreover, cross-device interaction can be achieved without installing the first application on the first electronic device.

[0128] After the first electronic device receives the preview information for the first card in step 902, the card adding process can be implemented through steps 903 to 907. The following is based on the above... Figure 7 The card cross-device interaction system shown uses a first electronic device as device A and a second electronic device as device B as an example to introduce the card adding process in detail with specific examples.

[0129] like Figure 11 As shown, the card adding process includes the following steps:

[0130] S1, the card user of device A initiates a card retrieval request to the first card management service. This card retrieval request is used to request the addition of card 1 from the card provider.

[0131] For example, the card user could be a desktop application.

[0132] s2, after receiving the card retrieval request, the first card management service calls the card retrieval interface provided by the card provider of device B.

[0133] Before the first card management service calls the card retrieval interface provided by the card provider of device B, if the first card management service has already obtained the card provider's remote interface proxy through the distributed communication system, then the first card management service can directly communicate with the card provider through the card retrieval interface in the card interface proxy, where the remote interface proxy includes the card retrieval interface. If the first card management service has not yet obtained the card provider's remote interface proxy, then it can first obtain the card provider's remote interface proxy through the distributed communication system, and then communicate directly with the card provider through the card interface proxy, i.e., call the card retrieval interface.

[0134] S3, the card provider of device B initializes the layout information and display data information of card 1 in the card acquisition interface according to its own business logic, and then returns the layout information and display data information to the first card management service of device A.

[0135] S4, the first card management service of device A queries the first package management system for the card resource information corresponding to card 1 that needs to be displayed.

[0136] Card resource information includes, for example, image resources and layout resources.

[0137] S5, the first package management system obtains card resource information.

[0138] In one possible implementation, the first package management system queries whether resource information corresponding to card 1 exists locally. If resource information corresponding to card 1 exists locally, it retrieves the resource information corresponding to card 1 from the local cache. If resource information corresponding to card 1 does not exist locally, it determines whether the resource information corresponding to card 1 is less than or equal to 10M. If the resource information corresponding to card 1 is less than or equal to 10M, it loads the application installation package using cloud transmission and retrieves the resource information from the installation package. If the resource information corresponding to card 1 is greater than 10M, it uses the local network transmission method, that is, it transmits the resource information corresponding to card 1 in the application installation package separately through a distributed communication system to reduce the amount of data transmitted.

[0139] S6, the first package management system will send the resource information of card 1 obtained back to the first card management service.

[0140] S7, the first card management service of device A, combines the layout information and display data information returned by the card provider in device B, and the resource information returned by the first package management system of device A, to create a card instance that can be directly displayed, and then returns the card instance to the card user of device A so that the card user can display the card.

[0141] The above example demonstrates how cards can be added and displayed across devices.

[0142] In some other embodiments, the first electronic device can also delete the added card. Taking the deletion of the first card in step 907 as an example, the first electronic device receives a second operation for the first card, which is used to delete the first card. In response to the second operation, the first electronic device deletes the first card and sends a deletion message to the second electronic device. After receiving the deletion message, the second electronic device deletes the layout information and display data information cached locally.

[0143] Based on the above Figure 7 The card cross-device interaction system shown uses a first electronic device as device A and a second electronic device as device B as an example to introduce the card deletion process in detail with specific examples.

[0144] like Figure 12 As shown, the card deletion process includes the following steps:

[0145] S1, the card user of device A initiates a card deletion request to the first card management service. This card deletion request is used to request the deletion of card 1.

[0146] s2, after receiving the card deletion request, the first card management service of device A deletes card 1.

[0147] S3, the first card management service calls the card deletion interface provided by the card provider of device B.

[0148] Before the first card management service calls the card delete interface provided by the card provider of device B, if the first card management service has already obtained the card provider's remote interface proxy through the distributed communication system, then the first card management service can communicate directly with the card provider through the card interface proxy, which includes the card delete interface. If the first card management service has not yet obtained the card provider's remote interface proxy, then it can first obtain the card provider's remote interface proxy through the distributed communication system, and then communicate directly with the card provider through the card interface proxy, i.e., call the card delete interface.

[0149] S4, the card provider of device B notifies the second card management service to delete the layout information and display data information of card 1.

[0150] After the first electronic device sends a first request to the second electronic device to add the first card, the second electronic device sends the layout information and display data information of card 1 to the first electronic device and caches the layout information and display data information of card 1 locally. When the first electronic device deletes card 1, it sends a deletion message to the second electronic device. After receiving the deletion message, the second electronic device deletes the layout information and display data information of card 1, thereby freeing up cache space.

[0151] S5, the card provider of device B returns a deletion completion message to the first card management service of device A through the card deletion interface.

[0152] In some other embodiments, after step 907, the card added by the first electronic device is updated on the second electronic device. The first electronic device can actively update the added card, for example, the first electronic device can periodically update the added card.

[0153] Taking updating the first card as an example, the first electronic device receives a third operation on the first card. The third operation is used to update the first card in the first electronic device. In response to the third operation, the first electronic device sends a third request to the second electronic device. The third request is used to request to update the first card. For example, the third request carries the identifier of the application carrying the first card and the identifier of the first card.

[0154] Based on the above Figure 7 The card cross-device interaction system shown uses a first electronic device as device A and a second electronic device as device B as an example to introduce the card update process in detail with specific examples.

[0155] like Figure 13 As shown, the card update process includes the following steps:

[0156] S1, the card user of device A initiates a third request to the first card management service, which is used to request an update of card 1 from the card provider.

[0157] S2, after receiving the request to obtain the third card, the first card management service calls the card update interface provided by the card provider of device B.

[0158] Before the first card management service calls the card delete interface provided by the card provider of device B, if the first card management service has already obtained the card provider's remote interface proxy through the distributed communication system, then the first card management service can communicate directly with the card provider through the card interface proxy, which includes the card update interface. If the first card management service has not yet obtained the card provider's remote interface proxy, then it can first obtain the card provider's remote interface proxy through the distributed communication system, and then communicate directly with the card provider through the card interface proxy, i.e., call the card update interface.

[0159] S3, the card provider of device B initializes the layout information and display data information of card 1 in the card update interface according to its own business logic, and then returns the layout information and display data information to the first card management service of device A.

[0160] S4, the first card management service of device A queries the first package management system for the updated card resource information corresponding to card 1 that needs to be displayed.

[0161] S5, the first package management system obtains the updated card resource information.

[0162] In one possible implementation, the first package management system queries whether updated card resource information corresponding to card 1 exists locally. If updated resource information corresponding to card 1 exists locally, it retrieves the updated resource information corresponding to card 1 from the local cache. If updated resource information corresponding to card 1 does not exist locally, it determines whether the updated resource information corresponding to card 1 is less than or equal to 10M. If the updated resource information corresponding to card 1 is less than or equal to 10M, it loads the application installation package using cloud transmission and retrieves the updated resource information from the installation package. If the resource information corresponding to card 1 is greater than 10M, it uses the local network transmission method, that is, through a distributed communication system, it separately transmits the updated resource information corresponding to card 1 in the application installation package to reduce the amount of data transmitted.

[0163] S6, the first package management system will send the updated resource information of card 1 back to the first card management service.

[0164] S7, the first card management service of device A, combines the layout information and display data information returned by the card provider in device B, and the updated resource information returned by the first package management system of device A, and creates a card instance that can be directly displayed and returns it to the card user of device A so that the card user can display the updated card 1.

[0165] The methods provided in the embodiments of this application above are described from the perspective of the terminal as the executing entity. To implement the functions of the methods provided in the embodiments of this application above, the terminal may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0166] Based on the above embodiments and the same concept, this application also provides a terminal for executing the steps performed by the terminal in the above method embodiments. For related features, please refer to the above method embodiments, which will not be repeated here.

[0167] Please see Figure 14 The electronic device includes one or more processors 1401 and a memory 1402, wherein the memory 1402 stores program instructions that, when executed by the device, can implement the method steps in the embodiments of this application.

[0168] The processor 1401 can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads instructions from the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0169] The specific implementation details of the device can be found in the method section above, and will not be repeated here.

[0170] Based on the same technical concept, this application embodiment also provides a chip, which is coupled to a memory in a device, so that the chip can call program instructions stored in the memory during operation to implement the above-described method of this application embodiment.

[0171] Based on the same technical concept, embodiments of this application also provide a computer storage medium, the computer-readable storage medium including a computer program, which, when run on an electronic device, causes the electronic device to perform the methods described in the embodiments of this application.

[0172] Based on the same technical concept, this application also provides a computer program product, which includes instructions that, when executed, cause a computer to perform the methods described in the embodiments of this application.

[0173] The various embodiments of this application can be used individually or in combination to achieve different technical effects.

[0174] The above description of the embodiments is merely used to provide a detailed introduction to the technical solutions of this application. However, the description of the embodiments is only for the purpose of helping to understand the methods of the embodiments of this application and should not be construed as a limitation on the embodiments of this application. Any variations or substitutions that can be easily conceived by those skilled in the art should be covered within the protection scope of the embodiments of this application.

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

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

[0177] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0178] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0179] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the technical objectives of this application, depending on actual needs.

[0180] The above description is merely a specific embodiment of this application. Any variations or substitutions conceived by those skilled in the art based on the specific embodiments provided in this application should be covered within the protection scope of this application.

Claims

1. A method for cross-device card interaction, characterized in that, The method includes: The first electronic device and the second electronic device are connected in communication. The first electronic device displays a desktop interface; After the first operation on the desktop interface, the first electronic device displays a cross-device service interface; wherein, the cross-device service interface includes the application name and / or application icon of the second electronic device application; In response to an operation applied to the cross-device service interface, the first electronic device displays a second cross-device service interface. This second interface includes preview information for at least one card, comprising preview information for a first card and preview information for a second card. Both the first and second cards belong to a first application within the second electronic device. The first and second cards have different card specifications, which include at least one of the following parameters: card size, card refresh rate, card name, and card description. The first application is not installed on the first electronic device, and the preview information and card specification information of the at least one card are obtained through a card interface with the second electronic device. The first electronic device receives a first add operation for preview information of the first card; In response to the first add operation, the first electronic device adds the first card.

2. The method as described in claim 1, characterized in that, The method further includes: The first electronic device receives device information corresponding to at least one card from the second electronic device; When the first electronic device displays preview information of the at least one card, it also displays device information corresponding to the first card.

3. The method as described in claim 1, characterized in that, The preview information of the first card is the same as the card information displayed on the first card; or, the preview information of the first card is a preset card template, and the preview information of the first card is different from the card information displayed on the first card.

4. The method as described in claim 2, characterized in that, The preview information of the first card is the same as the card information displayed on the first card; or, the preview information of the first card is a preset card template, and the preview information of the first card is different from the card information displayed on the first card.

5. The method according to any one of claims 1-4, characterized in that, Adding the first card to the first electronic device specifically includes: The first electronic device sends a first request to the second electronic device for adding the first card; The first electronic device obtains the card information corresponding to the first card sent by the second electronic device; Based on the card information corresponding to the first card, the first electronic device adds the first card.

6. The method as described in claim 5, characterized in that, After the first electronic device sends a first request to the second electronic device for adding the first card, the method further includes: The first electronic device acquires the layout information and display data information corresponding to the first card sent by the second electronic device.

7. The method according to any one of claims 1-4, characterized in that, Before the first electronic device displays preview information of at least one card, the first electronic device displays a first interface, the first interface including: The first electronic device displays the first card corresponding to the second electronic device and the first application; and / or, The first electronic device displays a third card corresponding to the first electronic device and the third application.

8. The method according to any one of claims 1-4, characterized in that, After the first electronic device obtains the card information corresponding to the first card sent by the second electronic device, it further includes: The first electronic device displays the first card on the desktop or the negative one screen.

9. The method according to any one of claims 1-4, characterized in that, The method further includes: The first electronic device receives a second operation targeting the first card; In response to the second operation, the first electronic device deletes the first card and sends a second request to the second electronic device to delete the first card; The first electronic device receives a deletion completion message from the second electronic device.

10. The method according to any one of claims 1-4, characterized in that, The method further includes: The first electronic device receives a third operation targeting the first card; In response to the third operation, the first electronic device updates the first card.

11. The method as described in claim 10, characterized in that, The first electronic device updates the first card specifically by: The first electronic device sends a third request to the second electronic device for updating the first card; The first electronic device receives card information sent by the second electronic device for updating the first card; Based on the card information used to update the first card, the first electronic device updates the first card.

12. The method according to any one of claims 1-4, characterized in that, The first electronic device and the second electronic device are located in the same network.

13. An electronic device, characterized in that, Including processor and memory; The memory stores one or more computer programs; When one or more computer programs stored in the memory are executed by the processor, the electronic device is able to perform the method as described in any one of claims 1 to 12.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program that, when run on a terminal, causes the electronic device to perform the method as described in any one of claims 1 to 12.

15. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed by a terminal, implement the method as described in any one of claims 1 to 12.

Images