WO2021249087A1 - 卡片分享方法、电子设备及通信*** - Google Patents

卡片分享方法、电子设备及通信*** Download PDF

Info

Publication number
WO2021249087A1
WO2021249087A1 PCT/CN2021/092985 CN2021092985W WO2021249087A1 WO 2021249087 A1 WO2021249087 A1 WO 2021249087A1 CN 2021092985 W CN2021092985 W CN 2021092985W WO 2021249087 A1 WO2021249087 A1 WO 2021249087A1
Authority
WO
WIPO (PCT)
Prior art keywords
card
application
application process
module
card module
Prior art date
Application number
PCT/CN2021/092985
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 荣耀终端有限公司
Priority to US17/794,165 priority Critical patent/US20230004259A1/en
Priority to EP21822929.2A priority patent/EP4024210A4/en
Publication of WO2021249087A1 publication Critical patent/WO2021249087A1/zh

Links

Images

Classifications

    • 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/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • 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
    • 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/0482—Interaction with lists of selectable items, e.g. menus
    • 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
    • G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
    • 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/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • 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/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • G06F3/04883—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures for inputting data by handwriting, e.g. gesture or text
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2203/00—Indexing scheme relating to G06F3/00 - G06F3/048
    • G06F2203/048—Indexing scheme relating to G06F3/048
    • G06F2203/04803—Split screen, i.e. subdividing the display area or the window area into separate subareas
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/36—Software reuse
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72415—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories for remote control of appliances

Definitions

  • This application relates to the field of communication technology, and in particular to a card sharing method, electronic equipment, and communication system.
  • Cards are a new service display technology that is widely used in electronic devices to facilitate users to quickly view service information of various applications.
  • the existing cards only support a limited combination of controls in the application, especially controls that are frequently used or have a deep control entry, and often appear in fixed positions on electronic devices.
  • the display method is single and fixed, and it is difficult to achieve a second time. Combine and share. Therefore, how to flexibly realize card sharing is a problem that needs to be solved urgently.
  • This application provides a card sharing method, electronic device, and communication system to realize the sharing of part of the card module or the entire card between applications of the same device, and also realize part of the card in the card across devices Sharing of modules or entire cards.
  • the present application provides a card sharing method, including: in response to a user's first operation, displaying an interface of a first application, where a first card is displayed in the interface of the first application, and the first card includes a first card module And the second card module, the interface resources of the first card are provided by the second application; in response to the user's second operation, a second message is sent to the third application, the second operation is associated with the first card module, and the second message Including the identification of the first card module; displaying the interface of the third application, the interface of the third application displays the first card module, and the interface resources of the first card module are provided by the fourth application.
  • the card can be split into multiple card modules and the card modules can be recombined, which not only realizes the sharing of part of the card module or the entire card between applications of the same device , It also realizes the sharing of part of the card module or the entire card in the card across devices, so that based on the user’s wishes, the card module or the entire card in the card can be used to provide users with what the user wants quickly and easily
  • the service content especially key information such as frequently used or cumbersome operation in the service content, meets the sharing needs of different scenarios and helps improve user experience.
  • the first card further includes: a third card module, the third card module is also displayed in the interface of the third application, and the interface resources of the third card module are provided by the fourth application. Therefore, in this application, the attributes of the card can be set to be recombinable, or the attributes of the card can be set to be non-recombinable.
  • the card module used to indicate the service content of the card or the key information of the card can be set to be non-recombinable.
  • the first application process can determine that the second card module and the third card module need to be displayed on the interface of the third application, or the third application is based on the information in the second message
  • the identification of the first card module can determine that the second card module and the third card module need to be displayed on the interface of the third application.
  • the first application, the second application, and the third application are different applications in the first device.
  • the first application process corresponds to the first application
  • the second application process corresponds to the second application
  • the third application process corresponds to the second application.
  • the application process corresponds to the third application
  • the fourth application process corresponds to the fourth application
  • the second application and the fourth application are the same application
  • the first application and the second application are different applications in the first device
  • the third application and the fourth application are different applications in the second device
  • the first device and the second device are different applications.
  • the devices are different
  • the first application process corresponds to the first application
  • the second application process corresponds to the second application
  • the third application process corresponds to the third application
  • the fourth application process corresponds to the fourth application. Therefore, the card sharing method of the present application is suitable for card sharing scenarios across devices, which is beneficial to provide different users with card display channels, and different devices provide resource support for their own cards, which reduces the dependence between different devices Performance, which realizes the decoupling between different devices.
  • the first application and the second application are different applications in the first device
  • the third application is a different application in the second device
  • the first device is different from the second device
  • the first device is different from the second device.
  • One application process corresponds to the first application
  • the second application process corresponds to the second application
  • the third application process corresponds to the third application
  • the fourth application process corresponds to the fourth application
  • the second application and the fourth application are the same application
  • the second application process corresponds to the third application.
  • the application process and the fourth application process are the same application process.
  • the card sharing method of the present application is suitable for card sharing scenarios between cross-devices, which is beneficial to provide different users with a display channel for cards, and the UI display of cards in different devices is supported by resources provided by one device, ensuring the card It can be displayed continuously in different devices.
  • the first message is sent to the second application process; the first drawing result is received from the second application process, and the first drawing result is rendered and drawn by the second application process based on the interface resources of the first card,
  • the interface resource of the first card is called by the second application process from the resource package collection based on the first message.
  • the resource package collection includes the interface resources of the first card module, the second card module and the third card module in the first card.
  • the interface resources of the fourth card module and the fifth card module in the second card the first card is displayed in the interface of the first application based on the first drawing result.
  • the first message includes: the identification of the first card.
  • the first message includes: the identification of the first card, the identification of the first card module, and the identification of the second card module. Therefore, the second application process can accurately determine the first card module and the second card module in the first card, and call the interface resources of the first card module and the second card module in the first card in time to realize the first card module and the second card module.
  • the rendering and drawing of a card enables the first application to quickly display the first card.
  • the first message further includes: a first address; the first drawing result sent to the first address is received from the second application process, and a possible implementation manner is provided for providing the first drawing result.
  • address sharing not only can the first drawing result be updated, but also the card sharing can be stopped to recycle the service.
  • the method further includes: sending the first message to the second application process when the first device has a resource package set. Therefore, when the first device does not have a resource pack set, the second application process cannot call the interface resources of the first card from the resource pack set. Therefore, it is beneficial to reduce unnecessary operations performed by the first device and save the first device.
  • the power consumption of a device also enables the first device to download the resource package collection in time, so as to quickly realize card sharing.
  • a third message is sent to the fourth application process; the second drawing result is received from the fourth application process, and the second drawing result is rendered and drawn by the fourth application process based on the interface resources of the first card module ,
  • the interface resource of the first card module is called by the fourth application process from the resource package collection based on the third message.
  • the resource package collection includes the first card module, the second card module and the third card module in the first card. Interface resources and the interface resources of the fourth card module and the fifth card module in the second card; the first card module is displayed in the interface of the third application based on the second drawing result.
  • the third message includes: the identification of the first card and the identification of the first card module.
  • the fourth application process can accurately determine the first card and the first card module, and call the interface resources of the first card module in the first card in time to realize the rendering and drawing of the first card module, so that the third application can Quickly display the first card module.
  • the third message further includes: a second address; the second drawing result sent to the second address is received from the fourth application process, so as to provide a possible implementation manner for providing the second drawing result.
  • address sharing not only can the second drawing result be updated, but also the card sharing can be stopped to recycle the service.
  • the method further includes: sending a third message to the fourth application process when it is determined that the third application process can display the card. Therefore, since the third application process cannot send the third message to the fourth application process when the third application process cannot display the card, it is beneficial to reduce unnecessary operations performed by the device where the third application process is located.
  • the power consumption of the device where the third application process is located is saved, and the device where the third application process is located can notify the user in time that the first application cannot share the card with the third application.
  • the resource package set also includes interface resources of the fifth application.
  • resource support is provided for the fifth application to realize interface display.
  • the interface of the first application includes: a first area and a second area; the first card is located in the first area, the first application page is located in the second area, and the interface resources of the first application page are created by the first area.
  • the interface of the first application is enriched, so that the first application can not only display one or more cards, but also display the first application page.
  • other applications such as the third application can also support the display of cards and application pages at the same time.
  • the first application includes any one of a home screen, a negative screen, a control center, a notification center, or a smart home application.
  • the first application can be various types of applications in the first device, which is conducive to enriching the channels for card display and card sharing.
  • the third application includes any one of a home screen, a negative screen, a control center, a notification center, or a smart home application.
  • the third application can be various types of applications in the first device or the second device, which is beneficial to enrich the channels for card display and card sharing.
  • the present application provides an electronic device including: at least one memory and at least one processor; the memory is used to store program instructions; the processor is used to call the program instructions in the memory to make the electronic device execute the first aspect and the first aspect Any possible method of card sharing in design.
  • this application provides a computer-readable storage medium on which a computer program is stored.
  • the computer program is executed by a processor to enable an electronic device to implement card sharing in any one of the first aspect and any one of the possible designs in the first aspect. method.
  • the present application provides a computer program product, including: execution instructions, the execution instructions are stored in a readable storage medium, at least one processor of an electronic device can read the execution instructions from the readable storage medium, and at least one processor Executing the execution instruction enables the electronic device to implement the card sharing method in the first aspect and any one of the possible designs in the first aspect.
  • the present application provides a communication system, including: a first device and a second device; the first device is installed with a first application, and the second device is installed with a third application; the first application is used to respond to a user
  • the first operation is to display the interface of the first application.
  • the interface of the first application displays the first card.
  • the first card includes the first card module and the second card module.
  • the interface resources of the first card are provided by the second application.
  • the first application is also used to send a second message to the third application in response to the user's second operation, the second operation is associated with the first card module, and the second message is used to indicate the first card module;
  • the third application Used to display the interface of the third application, the interface of the third application displays the first card module, and the interface resources of the first card module are provided by the fourth application.
  • FIG. 1 is a schematic structural diagram of an electronic device provided by an embodiment of this application.
  • 2a is a block diagram of the software structure of an electronic device provided by an embodiment of the application.
  • Figure 2b is a block diagram of the software structure of a card service engine provided by an embodiment of the application.
  • Figures 3a-31 are schematic diagrams of a human-computer interaction interface provided by an embodiment of this application.
  • 4a-4b are schematic diagrams of a human-computer interaction interface provided by an embodiment of this application.
  • 5a-5d are schematic diagrams of a human-computer interaction interface provided by an embodiment of this application.
  • 6a-6d are schematic diagrams of a human-computer interaction interface provided by an embodiment of this application.
  • FIG. 7 is a schematic diagram of an interface of a card provided by an embodiment of this application.
  • FIG. 8 is a schematic diagram of a code of a card module provided by an embodiment of this application.
  • 9a-9b are schematic diagrams of a human-computer interaction interface provided by an embodiment of this application.
  • 10a-10b are schematic diagrams of a human-computer interaction interface provided by an embodiment of this application.
  • FIG. 11 is a schematic diagram of code of an application program according to an embodiment of the application.
  • Fig. 12a is a schematic diagram of a scenario software architecture according to an embodiment of the application.
  • Figure 12b is a signaling interaction diagram of a card sharing method provided by an embodiment of this application.
  • Figures 13a-13b are schematic diagrams of a scenario software architecture according to an embodiment of the application.
  • FIG. 13c is a signaling interaction diagram of a card sharing method provided by an embodiment of this application.
  • 14a-14b are schematic diagrams of a scenario software architecture according to an embodiment of the application.
  • Figure 14c is a signaling interaction diagram of a card sharing method provided by an embodiment of this application.
  • 15a-15b are schematic diagrams of a scenario software architecture according to an embodiment of the application.
  • Figure 15c is a signaling interaction diagram of a card sharing method provided by an embodiment of the application.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • And/or describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the following at least one item (a) or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • At least one of a alone, b alone or c alone can mean: a alone, b alone, c alone, a combination of a and b, a combination of a and c, a combination of b and c, or a combination of a, b and c, where a, b, and c can be single or multiple.
  • the terms "first" and "second" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance.
  • This application provides a card sharing method, based on that the card can be split into multiple card modules and the card modules can be recombined, which not only realizes the sharing of part of the card modules or the entire card between applications of the same device, but also Part of the card module or the entire card in the card can be shared across devices, so that based on the user's wishes, the card module or the entire card in the card can be used to provide users with the services they want quickly and easily
  • the content especially key information such as frequently used or cumbersome operations in the service content, meets the sharing needs of different scenarios and is conducive to enhancing the user experience.
  • the electronic device may be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR)/virtual reality (VR) device, a notebook computer, an ultra-mobile personal computer (ultra-mobile personal computer).
  • computer UMPC
  • netbooks personal digital assistants (personal digital assistants, PDAs), smart TVs, smart screens, high-definition TVs, 4K TVs, smart speakers, smart projectors and other Internet of Things (IOT) devices, this application
  • IOT Internet of Things
  • FIG. 1 is a schematic structural diagram of an electronic device provided by an embodiment of this application.
  • the electronic device 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, and 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 jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193 , The display screen 194, and the 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, and ambient light Sensor 180L, bone conduction sensor 180M, etc.
  • the structure illustrated in this application does not constitute a specific limitation on the electronic device 100.
  • the electronic device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or arrange different components.
  • the illustrated components can be implemented in hardware, software, or a combination of software and hardware.
  • the processor 110 may include one or more processing units.
  • the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), and 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 processing unit (NPU) Wait.
  • AP application processor
  • modem processor modem processor
  • 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
  • NPU neural-network processing unit
  • the different processing units may be independent devices or integrated in one or more processors.
  • the controller may be the nerve center and command center of the electronic device 100.
  • the controller can generate operation control signals according to instruction operation codes and timing signals to complete the control of fetching instructions and executing instructions.
  • a memory may also be provided in the processor 110 to store instructions and data.
  • the memory in the processor 110 is a cache memory.
  • the memory can store instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. Repeated accesses are avoided, the waiting time of the processor 110 is reduced, and the efficiency of the system is improved.
  • the processor 110 may include one or more interfaces.
  • the interface can 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, and a universal asynchronous transmitter (universal asynchronous transmitter) interface.
  • 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/output
  • SIM subscriber identity module
  • USB Universal Serial Bus
  • the I2C interface is a bidirectional synchronous serial bus, which includes a serial data line (SDA) and a serial clock line (SCL).
  • the processor 110 may include multiple sets of I2C buses.
  • the processor 110 may couple the touch sensor 180K, charger, flash, camera 193, etc., respectively through different I2C bus interfaces.
  • the processor 110 may couple the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through the I2C bus interface to implement the touch function of the electronic device 100.
  • the I2S interface can be used for audio communication.
  • the processor 110 may include multiple sets of I2S buses.
  • the processor 110 may be coupled with the audio module 170 through an I2S bus to implement communication between the processor 110 and the audio module 170.
  • the audio module 170 may transmit audio signals to the wireless communication module 160 through an I2S interface, so as to realize the function of answering calls through a Bluetooth headset.
  • the PCM interface can also be used for audio communication to sample, quantize and encode analog signals.
  • the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface.
  • the audio module 170 may 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 two-way communication bus. It converts the data to be transmitted between serial communication and parallel communication.
  • the 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 may transmit audio signals to the wireless communication module 160 through a UART interface, so as to realize the function of playing music through a Bluetooth headset.
  • the MIPI interface can be used to connect the processor 110 with the display screen 194, the camera 193 and other peripheral devices.
  • the MIPI interface includes camera serial interface (camera serial interface, CSI), display serial interface (display serial interface, DSI), etc.
  • the processor 110 and the camera 193 communicate through a CSI interface to implement the shooting function of the electronic device 100.
  • the processor 110 and the display screen 194 communicate through a DSI interface to realize the display function of the electronic device 100.
  • the GPIO interface can be configured through 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 that complies with the USB standard specification, and specifically may be a Mini USB interface, a Micro USB interface, a USB Type C interface, and so on.
  • the USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and peripheral devices. It can also be used to connect earphones and play audio through earphones.
  • the interface can also be used to connect other electronic devices, such as AR devices.
  • the interface connection relationship between the modules illustrated in the present application is merely a schematic description, and does not constitute a structural limitation of the electronic device 100.
  • the electronic device 100 may also adopt different interface connection modes in the foregoing embodiments, or a combination of multiple interface connection modes.
  • the charging management module 140 is used to receive charging input from the charger.
  • the charger can be a wireless charger or a wired charger.
  • the charging management module 140 may receive the charging input of the wired charger through the USB interface 130.
  • the charging management module 140 may receive the wireless charging input through the wireless charging coil of the electronic device 100. While the charging management module 140 charges the battery 142, it can also supply power to the electronic device through the power management module 141.
  • the power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110.
  • the power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to 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 provided in the processor 110.
  • the power management module 141 and the charging management module 140 may also be provided in the same device.
  • the wireless communication function of the electronic device 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor.
  • the antenna 1 and the antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in the electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization.
  • antenna 1 can be multiplexed as a diversity antenna of a wireless local area network.
  • the antenna can be used in combination with a tuning switch.
  • the mobile communication module 150 may provide a wireless communication solution including 2G/3G/4G/5G and the like applied to the electronic device 100.
  • the mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like.
  • the mobile communication module 150 can receive electromagnetic waves by the antenna 1, and perform processing such as filtering, amplifying and transmitting the received electromagnetic waves to the modem processor for demodulation.
  • the mobile communication module 150 can also amplify the signal modulated by the modem processor, and convert it into electromagnetic wave radiation via the antenna 1.
  • at least part of the functional modules of the mobile communication module 150 may be provided 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 provided in the same device.
  • the modem processor may include a modulator and a demodulator.
  • the modulator is used to modulate the low frequency baseband signal to be sent into a medium and high frequency signal.
  • the demodulator is used to demodulate 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.
  • the low-frequency baseband signal is processed by the baseband processor and then passed to the application processor.
  • the application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays an image or video through the display screen 194.
  • the modem processor may be an independent device.
  • the modem processor may be independent of the processor 110 and be provided in the same device as the mobile communication module 150 or other functional modules.
  • the wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), and global navigation satellites.
  • WLAN wireless local area networks
  • BT wireless fidelity
  • GNSS global navigation satellite system
  • FM frequency modulation
  • NFC near field communication technology
  • 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 may also receive a signal to be sent from the processor 110, perform frequency modulation, amplify it, and convert it into electromagnetic waves to radiate through the antenna 2.
  • the antenna 1 of the electronic device 100 is coupled with the mobile communication module 150, and the antenna 2 is coupled with 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 (GPRS), 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 (LTE), BT, GNSS, WLAN, NFC , FM, and/or IR technology, etc.
  • the GNSS may include the global positioning system (GPS), the global navigation satellite system (GLONASS), the Beidou navigation satellite system (BDS), and the 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
  • BDS Beidou navigation satellite system
  • QZSS quasi-zenith satellite system
  • SBAS satellite-based augmentation systems
  • the electronic device 100 implements a display function through a GPU, a display screen 194, an application processor, and the like.
  • the GPU is a microprocessor for image processing, connected to the display 194 and the application processor.
  • the GPU is used to perform mathematical and geometric calculations and is used for graphics rendering.
  • the 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 adopt liquid crystal display (LCD), organic light-emitting diode (OLED), active matrix organic light-emitting diode or active-matrix organic light-emitting diode (active-matrix organic light-emitting diode).
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • active-matrix organic light-emitting diode active-matrix organic light-emitting diode
  • AMOLED flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (QLED), etc.
  • the electronic device 100 may include one or N display screens 194, and N is a positive integer greater than one.
  • the electronic device 100 can realize a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.
  • the ISP is used to process the data fed back from the camera 193. For example, when taking a picture, the shutter is opened, the light is transmitted to the photosensitive element of the camera through the lens, the light signal is converted into an electrical signal, and the photosensitive element of the camera transfers the electrical signal to the ISP for processing and is converted into an image visible to the naked eye.
  • ISP can also optimize the image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene.
  • the ISP may be provided in the camera 193.
  • the camera 193 is used to capture still images or videos.
  • the object generates an optical image through the lens and is projected 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 optical signal into an electrical signal, and then transfers the electrical signal to the ISP to convert it into a digital image signal.
  • ISP outputs digital image signals to DSP for processing.
  • DSP converts digital image signals into standard RGB, YUV and other formats of image signals.
  • the electronic device 100 may include one or N cameras 193, and N is a positive integer greater than one.
  • 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. In this way, the electronic device 100 can play or record videos in multiple encoding formats, such as: moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, and so on.
  • MPEG moving picture experts group
  • MPEG2 MPEG2, MPEG3, MPEG4, and so on.
  • NPU is a neural-network (NN) computing processor.
  • NN neural-network
  • the NPU can realize applications such as intelligent cognition of the electronic device 100, such as image recognition, face recognition, voice recognition, text understanding, and so on.
  • the external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100.
  • the external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example, save music, video and other files in an external memory card.
  • the internal memory 121 may be used to store computer executable program code, where the executable program code includes instructions.
  • the processor 110 executes various functional applications and data processing of the electronic device 100 by running instructions stored in the internal memory 121.
  • the internal memory 121 may include a storage program area and a storage data area.
  • the storage program area can store an operating system, at least one application program (such as a sound playback function, an image playback function, etc.) required by at least one function.
  • the data storage area can store data (such as audio data, phone book, etc.) created during the use of the electronic device 100.
  • 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, a flash memory device, a universal flash storage (UFS), and the like.
  • UFS universal flash storage
  • 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. For example, music playback, recording, etc.
  • the audio module 170 is used to convert digital audio information into an analog audio signal for output, and is also used to convert an analog audio input into a digital audio signal.
  • the audio module 170 can also be used to encode and decode audio signals.
  • the audio module 170 may be provided in the processor 110, or part of the functional modules of the audio module 170 may be provided in the processor 110.
  • the speaker 170A also called “speaker” is used to convert audio electrical signals into sound signals.
  • the electronic device 100 can listen to music through the speaker 170A, or listen to a hands-free call.
  • the receiver 170B also called a "handset" is used to convert audio electrical signals into sound signals.
  • the electronic device 100 answers a call or voice message, it can receive the voice by bringing the receiver 170B close to the human ear.
  • the microphone 170C also called “microphone”, “microphone”, is used to convert sound signals into electrical signals.
  • the user can make a sound by approaching the microphone 170C through the human mouth, and input the sound signal into the microphone 170C.
  • the electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C, which can implement noise reduction functions in addition to collecting sound signals. In other embodiments, the electronic device 100 may also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and realize directional recording functions.
  • the earphone interface 170D is used to connect wired earphones.
  • the earphone interface 170D may be a USB interface 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.
  • OMTP open mobile terminal platform
  • CTIA cellular telecommunications industry association
  • the pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal.
  • the pressure sensor 180A may be provided on the display screen 194.
  • the capacitive pressure sensor may include at least two parallel plates with conductive materials.
  • the electronic device 100 determines the intensity of the 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 that act on the same touch position but have different touch operation intensities can correspond to different operation instructions. For example: when a touch operation whose intensity is less than the first pressure threshold is applied to the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.
  • the gyro sensor 180B may be used to determine the movement posture of the electronic device 100.
  • the angular velocity of the electronic device 100 around three axes ie, x, y, and z axes
  • the gyro sensor 180B can be used for image stabilization.
  • the gyro sensor 180B detects the shake 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 shake of the electronic device 100 through a 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 can use the magnetic sensor 180D to detect the opening and closing of the flip holster.
  • the electronic device 100 can detect the opening and closing of the flip according to the magnetic sensor 180D. Then, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, features such as automatic unlocking of the flip cover are set.
  • the acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in various directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of electronic devices, and be used in applications such as horizontal and vertical screen switching, pedometers and so on.
  • the electronic device 100 can measure the distance by infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 may use the distance sensor 180F to measure the distance to achieve fast focusing.
  • the proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector such as a photodiode.
  • the light emitting diode may be an infrared light emitting diode.
  • the electronic device 100 emits infrared light to the outside through the light emitting diode.
  • the electronic device 100 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can 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 holds the electronic device 100 close to the ear to talk, so as to automatically turn off the screen to save power.
  • the proximity light sensor 180G can also be used in leather case mode, and the pocket mode will automatically unlock and lock the screen.
  • the ambient light sensor 180L is used to sense the brightness of the ambient light.
  • the electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived brightness of the ambient light.
  • 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 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 application locks, fingerprint photographs, fingerprint answering calls, and so on.
  • the temperature sensor 180J is used to detect temperature.
  • the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold value, the electronic device 100 reduces 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 due to 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 called “touch panel”.
  • the touch sensor 180K may be provided on the display screen 194, and the touch screen is composed of the touch sensor 180K and the display screen 194, which is also called a “touch screen”.
  • the touch sensor 180K is used to detect touch operations acting on or near it.
  • the touch sensor can pass the detected touch operation to the application processor to determine the type of touch event.
  • the 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.
  • 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 pulse signal.
  • the bone conduction sensor 180M may also be provided in the earphone, combined with the bone conduction earphone.
  • the audio module 170 can parse the voice signal based on the vibration signal of the vibrating bone block of the voice obtained by the bone conduction sensor 180M, and realize the voice function.
  • the application processor may analyze the heart rate information based on the blood pressure beating signal obtained by the bone conduction sensor 180M, and realize the heart rate detection function.
  • the button 190 includes a power-on button, a volume button, and so on.
  • the button 190 may be a mechanical button. 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 vibration prompts.
  • the motor 191 can be used for incoming call vibration notification, and can also be used for touch vibration feedback.
  • touch operations that act on different applications can correspond to different vibration feedback effects.
  • Acting on touch operations in different areas of the display screen 194, the motor 191 can also correspond to different vibration feedback effects.
  • Different application scenarios for example: time reminding, receiving information, alarm clock, games, etc.
  • the touch vibration feedback effect can also support customization.
  • the indicator 192 may be an indicator light, which may be used to indicate the charging status, power change, or to indicate messages, missed calls, notifications, and so on.
  • the SIM card interface 195 is used to connect to the SIM card.
  • the SIM card can be inserted into the SIM card interface 195 or pulled out from the SIM card interface 195 to achieve contact and separation with the electronic device 100.
  • the electronic device 100 may support 1 or N SIM card interfaces, and N is a positive integer greater than 1.
  • the SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc.
  • the same SIM card interface 195 can insert multiple cards at the same time. The types of the multiple cards can be the same or different.
  • the SIM card interface 195 can also be compatible with different types of SIM cards.
  • the SIM card interface 195 can also be compatible with external memory cards.
  • the electronic device 100 interacts with the network through the SIM card to implement functions such as call 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 software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture.
  • an Android system with a layered architecture is taken as an example to illustrate the software structure of the electronic device 100 by way of example.
  • this application does not limit the type of the operating system of the electronic device.
  • Android system Harmony Operating System (Harmony Operating System, Harmony OS), etc.
  • Fig. 2a is a block diagram of the software structure of an electronic device according to an embodiment of the application.
  • the layered architecture divides the software into several layers, each with a clear role and division of labor. Communication between layers through software interface.
  • the Android system is divided into four layers, from top to bottom, the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.
  • the application layer can include a series of application packages.
  • the application package can include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, game, shopping, travel, instant messaging (such as SMS), smart home, device control Wait for the application.
  • instant messaging such as SMS
  • smart home applications can be used to control or manage home devices with networking functions.
  • household appliances can include lights, televisions, and air conditioners.
  • household equipment can also include anti-theft door locks, speakers, sweeping robots, sockets, body fat scales, desk lamps, air purifiers, refrigerators, washing machines, water heaters, microwave ovens, rice cookers, curtains, fans, TVs, set-top boxes, Doors and windows, etc.
  • the application package may also include: home screen (ie desktop), negative one screen, control center, notification center, card application, card service application and other applications.
  • the negative one screen which can also be called “-1 screen” refers to sliding the screen to the right on the main screen of the electronic device until it slides to the user interface (UI) of the leftmost split screen.
  • a negative screen can be used to place some quick service functions and notification messages, such as global search, quick access to a certain page of the application (payment code, WeChat, etc.), instant information and reminders (express information, expenditure information, commuting traffic conditions) , Taxi trip information, schedule information, etc.) and follow-up trends (football stands, basketball stands, stock information, etc.).
  • the control center is the drop-down message notification bar of the electronic device, that is, the user interface displayed by the electronic device when the user performs a downward operation on the electronic device.
  • the notification center is the pull-up message notification bar of the electronic device, that is, the user interface displayed by the electronic device when the user performs an upward operation on the electronic device.
  • card application please refer to the content mentioned below, so I won’t repeat it here.
  • Card service applications are used to provide card services to support card UI display, card sharing between applications in the same device, and card sharing across devices, etc.
  • the application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer.
  • the application framework layer includes some predefined functions.
  • the application framework layer can include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, a card service engine, etc.
  • the window manager is used to manage window programs.
  • the window manager can obtain the size of the display screen, determine whether there is a status bar, lock the screen, take a screenshot, etc.
  • the content provider is used to store and retrieve data, and make these data accessible to applications.
  • the data may include video, image, audio, phone calls made and received, browsing history and bookmarks, phone book, etc.
  • the view system includes visual controls, such as controls that display text, controls that display pictures, and so on.
  • the view system can be used to build applications.
  • the display interface can be composed of one or more views.
  • a display interface that includes a short message notification icon may include a view that displays text and a view that displays pictures.
  • the phone manager is used to provide the communication function of the electronic device 100. For example, the management of the call status (including connecting, hanging up, etc.).
  • the resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and so on.
  • the notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and it can automatically disappear after a short stay without user interaction.
  • the notification manager is used to notify download completion, message reminders, and so on.
  • the notification manager can also be a notification that appears in the status bar at the top of the system in the form of a chart or a scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window.
  • prompt text information in the status bar sound a prompt sound, electronic device vibration, flashing indicator light, etc.
  • the card service engine is used to support the card service application to realize the rendering and display of the card, and is also used to process events and API calls.
  • Fig. 2b is a block diagram of the software structure of a card service engine provided by an embodiment of the application.
  • the card service engine may include: a front-end framework, a back-end engine, and a porting layout. in:
  • the front-end framework includes: service front-end and Javascript Engine.
  • the back-end engine includes: component, API, component tree, element tree, render tree, eventmanager, focus, theme, channel, animation, layout, image provider, and cardview.
  • the adaptation layer is used to interface with systems such as surface, event, vsync, lifecycle, etc., to adapt to the system libraries of different types of operating systems.
  • the Android runtime includes core libraries and virtual machines.
  • the Android runtime is responsible for the scheduling and management of the Android system.
  • the core library consists of two parts: one part is the function function that the java language needs to call, and the other part is the core library of the Android system.
  • the application layer and the application framework layer run in a virtual machine.
  • the virtual machine executes the java files of the application layer and the application framework layer as binary files.
  • the virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.
  • the system library can include multiple functional modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (for example: OpenGLES), 2D graphics engine (for example: SGL), etc.
  • the surface manager is used to manage the display subsystem and provides a combination of 2D and 3D layers for multiple applications.
  • the media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files.
  • the media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
  • the 3D graphics processing library is used to realize 3D graphics drawing, image rendering, synthesis, and layer processing.
  • the 2D graphics engine is a drawing engine for 2D drawing.
  • the kernel layer is the layer between hardware and software.
  • the kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.
  • the corresponding hardware interrupt is sent to the kernel layer.
  • the kernel layer processes the touch operation into the original input event (including touch coordinates, time stamp of the touch operation, etc.).
  • the original input events are stored in the kernel layer.
  • the application framework layer obtains the original input event from the kernel layer and identifies the control corresponding to the input event. Taking the touch operation as a touch click operation, and the control corresponding to the click operation is the control of the smart speaker icon as an example, the smart speaker application calls the interface of the application framework layer to start the smart speaker application, and then starts the audio driver by calling the kernel layer ,
  • the audio electrical signal is converted into a sound signal through the speaker 170A.
  • the structure illustrated in this application does not constitute a specific limitation on the electronic device 100.
  • the electronic device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or arrange different components.
  • the illustrated components can be implemented in hardware, software, or a combination of software and hardware.
  • the electronic device can share the card or the card module in the card with other applications of the electronic device to realize the card sharing between different applications of the same device, or share it with other electronic devices, and realize the cross-device sharing. Card sharing between.
  • this application shares the first card displayed by the first application in the first device to the second application in the first device.
  • Figures 3a-31 are schematic diagrams of a human-computer interaction interface provided by an embodiment of the application. Take the first device as a mobile phone, the first application as a smart home application in the mobile phone, the first card corresponds to the music playing service pushed by the smart home application, and the second application is a negative screen of the mobile phone as an example.
  • the first card includes: a card module 1, a card module 2, a card module 3, a card module 4, a card module 5, and a card module 6.
  • the card module 1 cannot be recombined.
  • the card module 2, the card module 3, the card module 4, the card module 5 and the card module 6 are all recombinable.
  • the card module 1 is used to indicate that the service corresponding to the card is the music playing service pushed by the smart speaker application, such as the smart speaker icon and the text "HUAWEI Sound X".
  • the card module 2 is used to indicate the Bluetooth connection function of the smart speaker, such as using the text "online” and the operation button of the Bluetooth icon to indicate.
  • Card module 3 used to indicate the name of the currently playing song of the smart speaker, switch songs and adjust the volume, such as the use of the song name "Baoao Tie Box", the operation button of the previous icon, the operation button of the play/pause icon, and The operation button of the next icon, the text "volume”, the volume icon, the sliding operation button for adjusting the volume, and the text "68%”.
  • the card module 4 is used to represent the music sound function of the smart speaker, such as using the text "music is sound” and the operation button of the earphone icon.
  • the card module 5 is used to indicate the voice skill function of the smart speaker, such as using the text "voice skill” and the operation button of the learning icon.
  • the card module 6 is used to indicate the stereo function of the smart speaker, such as the operation button with the text "stereo" and the stereo icon.
  • the card sharing method of the present application may include: Step 11 to Step 15.
  • Step 11 If the user wants to activate the first card in the smart home application, the user can click the icon of the smart home application on the display of the first device as shown in Figure 3b, and the display of the mobile phone is shown in Figure 3c Interface, the user clicks on the icon of the first card on the interface, where “HUAWEI Sound X” and the smart speaker icon are set together in a rounded rectangle to represent the icon of the first card.
  • the screen of the mobile phone displays as shown in Figure 3d.
  • the UI of the first card shown in order to provide users with the service content of the first card.
  • Step 12 If the user wants to view the first card, the user can perform a long-press operation on the blank space of the first card as shown in Figure 3d, and the screen of the mobile phone will display the interface as shown in Figure 3e.
  • Card module 2, card module 3, card module 4, card module 5, and card module 6 all display an option at the bottom right, which is used to indicate whether the corresponding card module is selected for sharing, such as the operation button of the box icon.
  • the long-press operation mentioned in this article can be understood as the operation that the user performs the operation for a duration that meets the preset duration.
  • Step 13 The user can check the online and voice skills service functions on the interface as shown in Figure 3e.
  • the user can click the box icon displayed by the card module 2 and the box icon displayed by the card module 5 respectively, and then the card module 2 corresponds to Both the box icon and the box icon corresponding to the card module 5 will have a check mark icon as shown in FIG. 3f.
  • the tick icon is used to indicate that the card module is selected and to be shared.
  • the user can continue to click the operation button with the text "share", and the display screen of the mobile phone will jump to the page shown in Figure 3g.
  • Step 14 As shown in Figure 3g, the page displays a preview area, cross-device sharing options, and local device sharing options.
  • the card module 1, the card module 2 and the card module 5 are displayed in the preview area.
  • the card module 1 is represented by the smart speaker icon and the text "HUAWEI Sound X”
  • the card module 2 is represented by the operation button of the Bluetooth icon
  • the card module 5 is represented by the operation button of the learning icon.
  • cross-device sharing options include: car icon, TV icon, mobile phone icon, tablet icon, watch icon, and notebook icon.
  • the car icon corresponds to the only car device
  • the TV icon corresponds to the TV
  • the cell phone icon corresponds to the mobile phone
  • the tablet icon corresponds to the tablet computer
  • the watch icon corresponds to the watch
  • the notebook icon corresponds to the notebook.
  • the sharing options of this device include: the operation button with the text “Add to Desktop”, the operation button with the text “Add to Negative Screen”, the operation button with “Add to Control Center” and the operation with the text "Add to Notification Center” Button.
  • this application does not limit the preview area, cross-device sharing options, and local device sharing options on the page on the respective shape, size, location layout, presentation content, number of devices, and device types, and other parameters. It should be noted that this page is not limited to the representation shown in FIG. 3g.
  • Step 15 If the user wants to share the first card to the negative screen, the user clicks on the operation button with the text "Add to negative screen" in the sharing options of this device, and the negative screen of the phone will display as
  • the card shown in FIG. 3h includes a card module 1, a card module 2, and a card module 5.
  • the negative screen is changed from the interface shown in Figure 3a to the interface shown in Figure 3h.
  • the interface adds a card including card module 1, card module 2 and card module 5.
  • the UI of the card is similar to The layout of the content displayed in the preview area is the same. In addition, the UI of the card can also be different from the layout of the content displayed in the preview area.
  • the user slides to the right on the display screen shown in FIG. 3b, and the display screen of the mobile phone displays the interface shown in FIG. 3a, that is, the negative screen of the mobile phone is the interface before the card is not shared.
  • the card of the TV in the living room displayed on the negative screen can be shared from the smart home application to the negative screen according to the description similar to step 11 to step 15, which will not be repeated here.
  • the negative screen of the mobile phone may not be turned on.
  • the rounded rectangular box displays operation buttons with the words "Negative screen not opened” and "Settings", so that the user knows in time that the first card cannot be shared to the negative screen because the negative screen is not opened.
  • the user can click the "Settings” operation button, and the screen of the mobile phone will display the "More Settings” interface, which displays the "Desktop Layout” setting operation button, the "Shake” switch operation button, and the “Icon
  • the switch operation button of the corner mark displays the switch operation button of “cyclic sliding” and the switch operation button of “HiBoard (negative one screen)”
  • the user can click the switch operation button of “HiBoard (negative one screen)” to set HiBoard (negative One screen) opens, as shown in Figure 3k.
  • the display screen of the mobile phone returns to the interface shown in Fig. 31, that is, the interface shown in Fig. 3g.
  • the card or the card module in the card can be shared between different applications of the same device, which is beneficial to provide users with cards through different display channels of the same device, which is convenient for users to find cards quickly, and avoids the control of service content.
  • the deep entrance leads to cumbersome and complicated user operations, allowing users to easily and quickly find the service content corresponding to the card, simplifying the user's complex operations, satisfying the user's high-frequency operation requirements, and improving the user's operating experience.
  • this application shares the first card displayed by the first application in the first device to the third application in the second device.
  • 4a-4b are schematic diagrams of a human-computer interaction interface provided by an embodiment of this application. Take the first device as the mobile phone, the first application as the smart home application in the mobile phone, the first card corresponds to the music playing service pushed by the smart home application, the second device is the car device, and the third application is the home screen of the car device as an example . Among them, the specific content of the first card can be referred to the description shown in FIG. 3a to FIG. 31, which will not be repeated here.
  • the card sharing method of the present application may include: Step 21-Step 25. Among them, the content described in step 21 to step 24 and step 11 to step 14 in FIG. 3a to FIG. 31, respectively, will not be repeated here.
  • Step 25 If the user wants to share the first card to the car device, as shown in Figure 4a, the user clicks the operation button of the car icon in the cross-device sharing option, and the main screen of the car device will display as shown in Figure 4b Including the card module 1, the card module 2 and the card module 5.
  • the main screen of the in-vehicle device is newly added with a card including the card module 1, the card module 2, and the card module 5.
  • the UI of the card is different from the layout of the content displayed in the preview area.
  • the UI of the card can also be the same as the layout of the content displayed in the preview area.
  • the card or the card module in the card can be shared between different devices, which is conducive to providing service content to users through the display channels of different devices, so that multiple users can simultaneously have control requirements in the form of cards, such as family members or Guests have temporary control requirements for the equipment at home, etc., which meets the sharing needs of different scenarios and enhances the user's operating experience.
  • scenario one and scenario two this application includes but is not limited to the user operations, interface layout, interface size, display content and other parameters mentioned in the above content.
  • the UI of the first card may be the same or different, which is not limited in this application.
  • scenario 1 and scenario 2 Based on the description of scenario 1 and scenario 2, if the user does not find the first card in the first application, the user can download and install the first card from a server such as the cloud download market, or download and install the first card from the local storage of the first device.
  • a server such as the cloud download market
  • the first card from the local storage of the first device.
  • this application does not limit it.
  • the following takes a smart home application as an example to illustrate the implementation process of the smart home application downloading the first card.
  • Figures 5a-5d are schematic diagrams of a human-computer interaction interface provided by an embodiment of the application. Taking the first device as a mobile phone, the first application as a smart home application in the mobile phone, and the first card corresponding to a music playing service pushed by the smart home application as an example.
  • the screen of the mobile phone displays the interface shown in Figure 5a instead of the interface shown in Figure 3c.
  • the user needs to download the first interface from the smart home application. card.
  • the user can click the add operation button, and the screen of the mobile phone displays the interface as shown in Figure 5b.
  • the interface includes added card options and all card options.
  • the added card options include: the desk lamp in the master bedroom, the air conditioning card in the living room, the plug card, the TV card in the living room, and the air purifier card. All cards include: the first card and the body fat scale card. It should be noted that the cards in the added card option can also be added to the smart home application with reference to the description shown in Figure 5a to Figure 5d, and will not be repeated here.
  • the user can click the add operation button on the first card, and the screen of the mobile phone displays an interface as shown in Figure 5c, and the first card is added to the added card options in this interface.
  • the user can click on an option, which is used to indicate that the card has been added, as shown in the check mark icon in Figure 5c.
  • the screen of the mobile phone displays the interface shown in Figure 5d, that is, the interface shown in Figure 3c, so A card is added to the smart home application to facilitate users to share the first card.
  • the smart home application can not only obtain the card name of the first card, but also the card module numbers of all card modules in the first card, that is, the card module of card module 1. Number, card module number of card module 2, card module number of card module 3, card module number of card module 4, card module number of card module 5, and card module number of card module 6.
  • the user can share all the card modules in the first card to the second application or the second device.
  • the user may also choose to add the card module in the first card to the smart home application, so as to flexibly display the UI of a single card to meet different display requirements.
  • the user can also choose to add a combination of the card module in the first card and the card module in the second card to the smart home application, which is conducive to flexibly displaying the UI of different cards to meet different display requirements.
  • FIGS. 6a-6d are schematic diagrams of a human-computer interaction interface provided by an embodiment of this application. Taking the first device as a mobile phone, the first application as a smart home application in the mobile phone, and the first card corresponding to a music playing service pushed by the smart home application as an example.
  • Including Card Module 2, Card Module 4, Card Module 5, and Card Module 6, and the bottom right of Card Module 2, Card Module 4, Card Module 5, and Card Module 6 on the interface all display an option, which is used to indicate Whether the corresponding card module is selected, such as the operation button of the box icon.
  • the user can click the box icon displayed by the card module 2 and the box icon displayed by the card module 5 on the interface as shown in Figure 6b, and the box icon displayed by the card module 2 and the box icon displayed by the card module 5 will both appear as The tick icon shown in Figure 6b.
  • the tick icon is used to indicate that the card module is selected.
  • the user can click the add operation button on the first card, and the screen of the mobile phone displays the interface shown in Figure 6c.
  • the first card is added to the added card option in this interface, and the interface
  • the icon corresponding to the card module 2 and the icon corresponding to the card module 5 in the first card are also displayed on the screen.
  • the user can click on an option, which is used to indicate that the card has been added, as shown in the tick icon shown in Figure 6c.
  • the screen of the mobile phone displays the interface shown in Figure 6d, so that the first card is added to the smart home application , It is convenient for users to realize the sharing of the first card.
  • the smart home application can not only obtain the card name of the first card, but also the card module number of card module 2 and the card module number of card module 5 in the first card . This allows the user to share the card module sharing 2 and the card module 5 in the first card to the second application or the second device.
  • At least one card can be embedded in any application of the electronic device, thereby displaying service content to the user in the form of a card, so that the card has a rich UI display channel and can meet different user needs.
  • a card is an embedded service form that can be embedded in an application process or operating system to intuitively show users key content (such as pictures, texts, videos, links, etc. on the same subject). To meet user needs.
  • a card corresponds to a service in an application, such as order logistics service in shopping application, ticket information service in travel application, and sound playing service in smart speaker application.
  • Each card can be split into multiple corresponding card modules (complication), that is, the card can be split.
  • the card module is the smallest unit of card reassembly, or in other words, the card module is the smallest unit of card sharing. It can be understood that each card module in the card is recombinable, so as to realize the recombination of at least one card module in the card. Or, part of the card modules in the card are recombinable, and the remaining card modules are not recombinable, so as to realize the recombination of at least one of the remaining card modules and the partial card modules.
  • a card module can be combined with multiple components.
  • a component can include, but is not limited to, information, pictures, text, operation buttons, audio and video, links, etc. If the combined components are different, the corresponding card modules display different UIs, so that different cards include different card modules to achieve different UI displays. Therefore, it is not only convenient for each card to be stored and managed by multiple card modules, but also can support the UI display of part or all of the card modules in each card, which is beneficial to quickly realize and update the UI display of each card.
  • the card module included in each card can be a card application process that the service provider of the application splits each service into corresponding card modules and sends them to the electronic device, or it can be the service provider of the application.
  • the merchant sends the service content to the card service application process, and the card service application process splits each service into corresponding card modules based on the service content, and sends them to the card application process of the electronic device.
  • the card service application process and the card application process please refer to the following description, which will not be repeated here.
  • each card has a unique identifier, that is, a card identity document (ID), such as a card name or a card number and other representations.
  • ID a card identity document
  • the card modules included in each card are associated with the card name of the card, so that the electronic device stores the card modules included in each card based on the card name.
  • each card module has a unique identification, such as a card module number, and the identification can be expressed in the form of binary numbers, character strings, etc., for example.
  • the identification of the card module is the card module number as an example for illustration.
  • the card name is also issued to the electronic device at the same time, so as to quickly determine the card corresponding to the card name and all the card modules in the card, or the card name and card module number are also issued at the same time To the electronic device to quickly determine the card corresponding to the card name and the card module in the card.
  • the visual style mentioned here also known as "style” refers to the visual experience of things presented to people, including the shape, structure, size, color, movement, etc. of things.
  • the visual style of the card may include the shape (such as rectangle), color (such as white, black, color, etc.), size, position and layout of the card module, and the shape of the card module.
  • the first card includes: card module 1, card module 2, card module 3, card module 4, card module 5 and card module 6 (in Figure 7 the 6 card modules are illustrated with corresponding numbers). in:
  • Card module 1 corresponding to the code for the smart speaker icon and the text "HUAWEI Sound X" shown in Figure 8.
  • the card module 2 corresponds to the code of the operation button with the text "online” and the Bluetooth icon shown in FIG. 8.
  • the card module 4 corresponds to the code for the operation button of the text "music with sound” and the earphone icon shown in FIG. 8.
  • the card module 5 corresponds to the code of the operation button for the text "voice skill” and the learning icon shown in FIG. 8.
  • any card may only include recombinable card modules.
  • the first card includes a first card module and a second card module, and the first card module and the second card module can be recombined card modules.
  • any card may include recombinable card modules and non-recombinable card modules.
  • the first card includes a first card module, a second card module, and a third card module.
  • the first card module and the second card module can both be recombinable card modules
  • the third card module can be a non-recombinable card. Module.
  • the recombination mentioned in this application can be understood as the user can select and share.
  • each card can be associated with one or more UIs corresponding to the card, so that the user can realize the function of jumping to the page of the application corresponding to the card by performing operations on the card.
  • the operation button can also be linked to a page of the application corresponding to the operation button.
  • the display of the mobile phone can jump to the lyrics page of the song name "Baoao Tie He", and the song is displayed on the lyrics page.
  • the lyrics of the name "Baoaotiehe” the operation button of the previous icon, the operation button of the play/pause icon, and the operation button of the next icon, the text "volume” and "68%” indicating the volume, use Sliding operation buttons to adjust the volume, etc.
  • the card itself can also be linked to a page such as the card application.
  • the user clicks on an option on the first card, which is used to indicate that the display of the first card is turned off, and the screen of the mobile phone displays the interface shown in Figure 10b, which is shown in Figure 3c. interface.
  • the interface includes: an application page 101 of a smart home application, a UI of 6 cards (102-107), and an option 108, which is used to add a card.
  • the content of the 6 cards can be referred to the previous description, and will not be repeated here.
  • the 6 cards (102-107) are illustrated with the first card and the second card as an example. in:
  • the application page 101 of the smart home application corresponds to the code of the application page as shown in FIG. 11.
  • the smart home application realizes the UI display of the application page.
  • the UI of the first card corresponds to the code of the first card as shown in Figure 11.
  • the code is embedded with the card label "card src" of the first card, and the card label carries the card name of the first card "fa.soundx” .soundXcard".
  • the smart home application realizes the UI display of the first card.
  • the UI of the second card corresponds to the code of the second card as shown in Figure 11.
  • the code is embedded with the card label "card src" of the second card, and the card label carries the card name of the second card "fa.aircondition” .airconditioncard”.
  • the smart home application realizes the UI display of the second card.
  • the UI of one option 108 corresponds to the code of the card slot as shown in FIG. 11, in which the card label "card" of the second card is embedded in the code.
  • the smart home application realizes UI display of newly added cards (such as cards after recombination of card modules).
  • FIG. 12a is a schematic diagram of a scenario software architecture according to an embodiment of the application.
  • the first card service module in the first device may include: a first application process, a first card service application process, and a resource package set. Among them, the first card service module is located at the application layer in Figure 2a.
  • the process is the basic unit of the operating system for resource allocation and scheduling, and is the foundation of the operating system's structure. That is, when the operating system runs any application, it creates a process and allocates a space.
  • the first application process corresponds to the first application in the first device
  • the first card service application process corresponds to the first card service application in the first device.
  • this application does not limit the specific implementation type of the application in the first device.
  • the application programs mentioned in this application can also be referred to as applications.
  • the first application process is used to provide cards.
  • the first application process includes: resource pack 1, card label 1, and card container 1. in:
  • Resource pack 1 is used to provide UI display and logic execution code of the application page of the first application, that is, interface resources.
  • Resource bundle 1 includes JS Bundle and Resource corresponding to the application page of the first application.
  • JS Bundle is used to implement the logic execution and UI display of application page 1 of the first application, and Resource is used to provide the application of the first application to JS Bundle Data sources such as videos and pictures in the UI display of page 1.
  • the application page 1 of the first application here refers to UI other than the UI displayed by the card, that is, the UI displayed through the JS Bundle in the resource bundle 1.
  • Card label 1 used to embed different cards or card modules.
  • the card label 1 carries the card name of the card, so that the first application process parses and loads the card corresponding to the card name based on the card label 1, and the card includes at least one card module.
  • the first application can simultaneously implement the display UI of the application page 1 and at least one card. If the first application can realize the display UI of the first card and the display UI of the second card, as shown in Figure 11, the code of the first card will be embedded in the UI display and logic execution code of the application page 1 of the first application.
  • Card label 1 and card label 1 of the second card wherein the card label 1 of the first card carries the card name "fa.soundx.soundXcard" of the first card, and the card label 1 of the second card carries the second The card name of the card is "fa.aircondition.airconditioncard".
  • the first application process may also include a card label 2 that does not carry a card name, so that the first application process uses the card label 2 as a placeholder for loading and displaying the card after the recombination of the card module.
  • the card after the recombination of the card modules mentioned in this article can be understood as a card that includes part of the card modules, or a card that includes all the card modules after the recombination.
  • the code in the first application process is: ⁇ card"> ⁇ /card>, card represents card label 2, and there is no card name src, then the first application process can load and display the card after recombining the card module.
  • the card container 1 is used to store the drawing result (shown as a card in FIG. 12a).
  • the drawing result can be understood as a frame by frame image, which is used to form the display UI of the card.
  • the interface resources of each card are stored in different storage spaces in the card container 1.
  • each card corresponds to an address 1, so that the first card service application process transmits the drawing result to the corresponding storage space in the card container 1 according to the address 1, so that the first application can realize the UI display of the card.
  • address 1 may be the starting address of the storage space for the card.
  • the first application in addition to implementing the display UI of the application page 1 and at least one card, can also reserve at least one card slot for the card after the recombination of the card module, so as to realize the recombination of the card after the card module is recombined.
  • Display the UI If the first application can display the card after the recombination of the card module in addition to the display UI of the first card and the display UI of the second card, as shown in Figure 11, the UI of the application page 1 of the first application is displayed And the logic execution code will embed the card label 2, the card label 1 of the first card, and the card label 1 of the second card.
  • the card label 2 is used to reserve a card slot to display the card after recombining the card module.
  • the card label 1 of one card carries the card name "fa.soundx.soundXcard" of the first card
  • the card label 1 of the second card carries the card name "fa.aircondition.airconditioncard” of the second card.
  • the card application process that is, the corresponding process when resources are loaded from the resource pack set is called the card application process.
  • the resource pack collection is used to pre-store the UI display and logic execution code of each card, usually based on the card name of each card to store the UI display and logic execution code of all card modules of the card.
  • the first card service application process can load the card UI display and logic execution code from the card application process, so as to realize the card UI display of the first application process and the second application process, and also make the card application available from the card application process. Load the code for the UI display and logic execution of the card so that the card application can realize the UI display of the card.
  • the card application mentioned in this article is an application about cards. Taking the card corresponding to the music playing service pushed by the smart home application as an example, the card application may be a smart home application or a smart speaker application.
  • the resource pack set includes: at least one resource pack 2 (in Figure 12a, the resource pack 2 of the first card and the resource pack 2 of the second card are shown), and each resource pack 2 corresponds to the UI display of a card And the code executed by logic.
  • the resource pack 2 of the first card can realize the UI display of 6 card modules in the first card.
  • resource bundle 2 includes JS Bundle and Resource corresponding to each card module in the card. JS Bundle is used to realize the UI display and logic execution of each card module in the card, and Resource is used to provide cards to JS Bundle Data sources such as videos and pictures displayed on the UI.
  • the resource pack collection is also used to store the UI display and logic execution code of the application page of the card application, so that the card application can load the UI display and logic execution code of the application page from the card application process to realize the addition of the card application UI other than the card UI display.
  • the application page of the card application here refers to the UI other than the UI displayed by the card, that is, the UI displayed through the JS Bundle in the resource bundle 3.
  • the resource package set may also include: at least one resource package 3 (a resource package 3 is illustrated in FIG. 12a), each resource package 3 corresponds to the UI display and logic of the application page of the card application corresponding to a card The code executed.
  • resource bundle 3 includes the JS Bundle and Resource corresponding to the application page of the card application corresponding to the card.
  • the JS Bundle is used to implement the UI display and logic execution of the application page of the card application corresponding to the card.
  • Resource is used to provide JS Bundle with data sources such as videos and pictures displayed on the application page UI of the card application corresponding to the card.
  • the first card service application process is used to provide services for driving the UI display and logic execution of the card. That is, the first card service application process loads the JS Bundle from the card application process, and draws and renders the drawing result 1 based on the JS Bundle. Thus, the first card service application process transmits the drawing result 1 to the first application process or the second application process to realize the UI display of the card, that is, the first card service application process and the first application process or the first card service application process With the second application process, the UI display of the card is realized by sharing the address. Wherein, the first card service application process corresponds to the card service application in the first device.
  • an inter-process communication (IPC) connection can be established between the first application process and the first card service application process, so as to realize the mutual communication between the first card service application process and the first application process.
  • IPC inter-process communication
  • Figure 12b is a signaling interaction diagram of a card sharing method provided by an embodiment of the application. As shown in Figure 12b, the card sharing method of the present application may include: steps S101-S117.
  • the user can perform a first operation such as click, long press, and slide on the page of the first application.
  • the first card is any card in the first application.
  • the long-press operation mentioned in this article can be understood as the operation that the user performs the operation for a duration that meets the preset duration.
  • the first application process queries whether there is a resource pack set in the card service module of the first device according to the card name in the card tag 1 of the first card. Wherein, the first card corresponding to the card name is stored in the resource pack set.
  • the first application process can determine whether the card application process is installed by determining whether the broadcast information can be found. If the broadcast information is not found, the first application process determines that the first device does not have a resource package set corresponding to the card application process, and executes step S102. If the broadcast information is found, the first application process determines that the first device has a resource package set corresponding to the card application process, and executes steps S103-S108.
  • the first application process does not perform processing and cannot display the first card. It can be understood that the first application cannot be embedded in the first card.
  • the first application process parses the card label 1 of the first card to obtain the card name of the first card, and establishes an IPC connection between the first application process and the first card service application process.
  • the first card service application process is in an inactive state by default when no card is displayed, and the first application program in S103 can start the first card service application process, thereby reducing resource overhead.
  • a binding relationship can be established between the first application and the first card service application process in advance, so that the first application process can start the first card service application process based on the binding relationship, that is, the first application process can start the first card service application process.
  • the first card service application process is in the activated state by default when no card is displayed, and the first application process does not need to start the first card service application process in S103.
  • the IPC connection between the first application process and the first card service application process may also be established by the operating system of the first device, which is not limited in this application.
  • Step 103 is optional, that is, the IPC connection between the first application process and the first card service application process can be established in advance.
  • the first application process sends the card name and address 1 of the first card to the first card service application process through the IPC connection between the first application process and the first card service application process.
  • the first card service application process determines at least one card module associated with the card name of the first card, and loads the JS Bundle corresponding to the at least one card module from the resource bundle set through the card application process.
  • the JS Bundle involved in this article may be one JS Bundle or multiple JS Bundles, which is not limited in this application.
  • the first card service application process draws and renders to obtain the first drawing result based on the JS Bundle corresponding to the at least one card module.
  • the first drawing result can be understood as a frame by frame image, which is used to form the UI of the first card.
  • the first card service application process sends the first drawing result to the card container 1 of the first application process according to the address 1 through the IPC connection between the first card service application process and the first application process.
  • the first application process displays the first card based on the first drawing result in the address 1 of the card container 1.
  • the first device is made to present the service content pushed by the application service provider to the user in the form of a card, so as to push different cards to the user according to different service scenarios.
  • the display UI of the card in each application can be the same or different, which is not limited in this application.
  • step 11 in scenario one and step 21 in scenario two can use the above description to realize the UI display of the first card.
  • the user can share the card module in the first card to the second application in the first device.
  • the specific implementation of the card sharing method between different applications of the same device of the present application will be described.
  • FIGS. 13a to 13c taking the card sharing from the first application of the first device to the second application of the first device as an example.
  • Figures 13a and 13b are schematic diagrams of a scenario software architecture provided by an embodiment of the application.
  • the first card service module in the first device may include: a first application process, a first card service application process, a second application process, and a resource pack set.
  • the first application process, the first card service application process, and the resource package set can be referred to the description in FIG. 12a, which will not be repeated here.
  • the second application process is used to receive and display shared cards.
  • the second application process includes: resource pack 4, card label 2 and card container 2. in:
  • the resource pack 4 is used to provide the UI display and logic execution code of the application page 2 of the second application.
  • Resource bundle 4 includes JS Bundle and Resource corresponding to application page 2 of the second application.
  • JS Bundle is used to implement the logic execution and UI display of application page 2 of the second application, and Resource is used to provide JS Bundle with information for the second application.
  • Data sources such as videos and pictures in the UI display of application page 2.
  • the application page 2 of the second application here refers to UI other than the UI displayed by the card, that is, the UI displayed through the JS Bundle in the resource bundle 4.
  • Card label 2 used to embed different cards or card modules.
  • the card label 2 does not carry the card name, so that the second application process uses the card label 2 as a placeholder for loading and displaying the card after the recombination of the card module.
  • the code in the second application process is: ⁇ card"> ⁇ /card>, and card represents card label 2, then the second application process can load and display the card after the recombination of the card module.
  • the second application realizes the UI display of the application page 2, it can reserve at least one card slot for the card after the recombination of the card module, so as to realize the display UI of the card after the recombination of the card module.
  • the specific implementation process Refer to the description of the display UI and the card label 2 of the application page 1 in the embodiment of FIG. 12a, which will not be repeated here.
  • the second application process may also include a card tag 1 carrying a card name, so that the second application process parses and loads a card corresponding to the card name based on the card tag 1, and the card includes at least one card module.
  • the card container 2 is used to store the drawing result (shown as a card in FIG. 13b).
  • the drawing result can be understood as a frame by frame image, which is used to form the display UI of the card.
  • the interface resources of each card are stored in different storage spaces in the card container 2.
  • each card corresponds to an address 2, so that the first card service application process transmits the drawing result to the corresponding storage space in the card container 2 according to the address 2, so that the second application can realize the UI display of the card.
  • address 2 may be the starting address of the storage space of the card.
  • the second application in addition to simultaneously implementing the display UI of the application page 2 and reserving at least one card slot for the card after recombining the card module, the second application can also implement the display UI of at least one card.
  • the display UI of the application page 2 in addition to simultaneously implementing the display UI of the application page 2 and reserving at least one card slot for the card after recombining the card module, the second application can also implement the display UI of at least one card.
  • the specific implementation process please refer to The description in the embodiment of FIG. 12a will not be repeated here.
  • an IPC connection can be established between the first application process and the second application process, so as to realize the mutual communication between the first application process and the second application process.
  • An IPC connection can be established between the first card service application process and the second application process, so as to realize the mutual communication between the first card service application process and the second application process.
  • Fig. 13c is a signaling interaction diagram of a card sharing method provided by an embodiment of the application. As shown in Fig. 13c, the card sharing method of the present application may include: steps S201-S209.
  • the user can perform a second operation on the UI of the first card.
  • the second operation is used to determine the card module selected by the user to share from the first card and the second application selected by the user, and share the card module selected by the user to share from the first card from the first application to The second application. It should be noted that the user can select part of the card modules from the first card to share, or select all card modules from the first card to share, and this application does not limit it.
  • the first application process determines the first card module selected by the user to share from the first card and the second application process selected by the user.
  • the first card module may be at least one card module in the first card.
  • the second operation can be associated with the first card module in the first card, or can be associated with the first card module in the first card and the third card module in the first card.
  • the third card module is not recombinable At least one card module, which is not limited in this application.
  • the second operation can also be used to instruct the first device to share the first card module in the first card with the second application, or the second operation can also be used to instruct the first device to share the first card module in the first card.
  • the card module and the third card module are shared to the second application.
  • the first application process establishes an IPC connection between the first application process and the second application process, and sends the card of the first card to the second application process through the IPC connection between the second application process and the second application process.
  • Name and card module number of the first card module are the first card module.
  • the second application process judges whether the card tag 2 of the first card associated with the card name of the first card exists, so as to determine whether the second application process can load and display the card. If the card label 2 of the first card exists, the second application process determines that the second application process can load and display the card; if the card label 2 of the first card does not exist, the second application process determines that the second application process cannot load and display the card card.
  • the second application process sends the card name of the first card, the card module number and address of the first card module to the first card service application process through the IPC connection between the second application process and the first card service application process 2 .
  • the first card service application process determines the first card module associated with the card name of the first card and the card module number of the first card module, and loads the first card module from the resource pack set through the card application process The corresponding JS Bundle.
  • the first card service application process draws and renders to obtain a drawing result 2 based on the JS Bundle corresponding to the first card module.
  • the drawing result 2 can be understood as a frame by frame image, which is used to form the display UI of the first card module.
  • the first card service application process can adapt the shape, size, position, layout, and content of each card module in the drawing result 2
  • the setting enables the first card module to realize beautiful and clear UI display in the second application.
  • the display UI of the card module in each application program may be the same or different, which is not limited in this application.
  • drawing result 2 can also be used to form the display UI of the first card module and the third card module.
  • the first card service application process sends the drawing result 2 to the card container 2 of the second application process according to the address 2 through the IPC connection between the first card service application process and the second application process.
  • the second application process displays the first card module based on the drawing result 2 in the card container 2.
  • the first device uses the form of a card to display the service content pushed by the application service provider based on the user's wishes, especially the key information such as frequent use or cumbersome operation of the user in the service content, to the user through the UI display, so that according to different service scenarios Push different cards to users.
  • the card after the recombination of the card module can be shared between different applications of the same device, and based on the user's wishes, the card can be displayed through the UI of the card.
  • the user provides the service content that the user wants, especially the key information such as frequent use or cumbersome operation in the service content, which is conducive to enhancing the user experience.
  • the first application process connects to the first application process through the IPC connection between the first application process and the second application process.
  • the second application process sends the card name of the first card without sending the card module numbers corresponding to all the card modules of the first card to the second application process, which reduces the amount of data transmission.
  • the second application process sends the card name and address 2 of the first card to the first card service application process through the IPC connection between the second application process and the first card service application process, and there is no need to transfer the first card
  • the card module numbers corresponding to all the card modules in the card module are sent to the first card service application process, which reduces the amount of data transmission.
  • the user's electronic device is made to push all the service content of the application service provider based on the user's wishes in the form of a card, and present it to the user through the UI display, so as to push different cards to the user according to different service scenarios.
  • the user can drag the first card embedded in the first application in the first device to the second application in the first device.
  • the display UI of the card displayed by the first application and the second application may be the same or different, which is not limited in this application.
  • the user drags the first card displayed in the smart home application of the mobile phone to the negative screen of the mobile phone, so that the negative screen can display the UI of the first card.
  • the card has a rich display channel.
  • the user can drag and drop the card after the recombination of the card module in the second application in the first device to the third application in the first device.
  • the display UI of the card displayed by the second application and the third application may be the same or different, which is not limited in this application.
  • the user drags the card displayed on the negative screen shared to the mobile phone to the home screen of the mobile phone, so that the home screen can display the UI of the card.
  • the user can stop sharing the card by ending the second application.
  • the first application process can also send the card sharing duration to the first card service application process while sharing the card with the second application, so that the first card service application process is within the card sharing duration through address sharing, Supporting the second application to display the card also enables the first card service application process to stop address sharing in addition to the card sharing duration, and no longer supports the second application to display the card.
  • This application is not limited to the foregoing two implementation methods to stop card sharing. Therefore, the first application can realize service recovery by stopping card sharing.
  • the first card service application process can also update the drawing result 2 through address sharing.
  • the first device can adopt multiple implementation methods to share the card with the second device.
  • the specific implementation of the card sharing method between cross-devices of the present application will be described in combination with the feasible implementations of the two.
  • FIGS. 14a to 14c are schematic diagrams of a scenario software architecture provided by an embodiment of this application.
  • the first card service module in the first device may include: a first application process and a first card service application process. Among them, the first card service module is located at the application layer in Figure 2a.
  • the second card service module in the second device may include: a third application process and a second card service application process. Among them, the second card service module is located at the application layer in Figure 2a.
  • the specific implementation content of the first application process and the first card service application process can refer to the description in the embodiment of FIG. 12a, which is not repeated here.
  • the third application process is used to receive and display shared cards.
  • the third application process includes: resource pack 5, card label 2 and card container 3. in:
  • the resource pack 5 is used to provide the UI display and logic execution code of the application page 3 of the third application, that is, interface resources.
  • Resource bundle 5 includes JS Bundle and Resource corresponding to application page 3 of the third application.
  • JS Bundle is used to implement the logic execution and UI display of application page 3 of the third application, and Resource is used to provide JS Bundle with the third application.
  • Data sources such as videos and pictures in the UI display of application page 3.
  • the application page 3 of the third application here refers to UI other than the UI displayed by the card, that is, the UI displayed through the JS Bundle in the resource bundle 5.
  • Card label 2 used to embed different cards or card modules.
  • the card label 2 does not carry the card name, so that the third application process uses the card label 2 as a placeholder for loading and displaying the card after the recombination of the card module.
  • the code in the third application process is: ⁇ card"> ⁇ /card>, and card represents card tag 2, then the third application process can load and display the card after the recombination of the card module.
  • the third application realizes the UI display of the application page 3, it can reserve at least one card slot for the card after the recombination of the card module, so as to realize the display UI of the card after the recombination of the card module.
  • the specific implementation process Refer to the description of the display UI and the card label 2 of the application page 1 in the embodiment of FIG. 12a, which will not be repeated here.
  • the third application process may also include a card tag 1 carrying a card name, so that the third application process parses and loads a card corresponding to the card name based on the card tag 1, and the card includes at least one card module.
  • the card container 3 is used to store the drawing result (shown as a card in FIG. 14b), the drawing result can be understood as a frame by frame image, which is used to form the display UI of the card.
  • the interface resources of each card are stored in different storage spaces in the card container 3.
  • each card corresponds to an address 3, so that the first card service application process transmits the drawing result to the corresponding storage space in the card container 3 according to the address 3, so that the third application can realize the UI display of the card.
  • address 3 can be the starting address of the storage space of the card.
  • the third application in addition to implementing the display UI of the application page 3 and reserving at least one card slot for the card after recombining the card module, the third application can also implement the display UI of at least one card at the same time.
  • the specific implementation process can be seen in the figure. The description in the 12a embodiment will not be repeated here.
  • the second card service application process is used to provide services that drive the UI display and logic execution of the card, that is, the second card service application process loads the JS Bundle from the card application process, and draws and renders the JS Bundle to obtain the drawing result 2 based on the JS Bundle.
  • the second card service application process transmits the drawing result 2 to the third application process to realize the UI display of the card, that is, the second card service application process and the first application process or the second card service application process and the second application process , Realize the UI display of the card by sharing the address.
  • the second card service application process corresponds to the second card service application in the second device.
  • a remote procedure call (RPC) connection may be established between the first application process and the third application process, so as to implement mutual communication between the first application process and the third application process.
  • An IPC connection can be established between the first card service application process and the first application process, so as to realize the mutual communication between the first card service application process and the first application process.
  • An IPC connection can be established between the second card service application process and the third application process, so as to realize the mutual communication between the second card service application process and the third application process.
  • both the first device and the second device can install the resource package set corresponding to the card application process from, for example, a cloud application server.
  • the specific implementation content of the card application process and the resource package set can be referred to the description in the embodiment of FIG. 12a, which will not be repeated here.
  • the resource pack sets in the first device and the second device may be the same or different, which is not limited in this application.
  • FIG. 14a and FIG. 14b take the same resource pack set in the first device and the second device as an example for illustration.
  • the first application process, the first card service application process, the third application process, the second card service application process, and the card application process in Figures 14a and 14b are taken as execution
  • the main body provides a detailed description of the specific implementation process of the card sharing method of this application.
  • Figure 14c is a signaling interaction diagram of a card sharing method provided by an embodiment of the application. As shown in Fig. 14c, the card sharing method of the present application may include: steps S301-S310.
  • the user can perform the second operation on the display UI of the first card, The second operation is used to determine the card module selected by the user to share from the first card, and the second device and third application process selected by the user, and through steps S301-S310, the card module selected by the user to share from the card is selected from the first card module.
  • One application process is shared with the third application process in the second device. It should be noted that the user can select part of the card modules from the first card to share, or select all the card modules from the first card to share, and this application does not limit it.
  • the first application process determines the first card module selected by the user to share from the first card and the second device selected by the user (for example, the unique identifier such as the device number of the second device is determined) ) And the third application process (for example, the unique identification such as the name and number of the third application process is determined).
  • the first card module may be at least one card module in the first card.
  • the second operation can be associated with the first card module in the first card, or can be associated with the first card module in the first card and the third card module in the first card.
  • the third card module is not recombinable At least one card module, which is not limited in this application.
  • the second operation can also be used to instruct the first device to share the first card module in the first card with the third application in the second device, or the second operation can also be used to instruct the first device to share the first card module in the second device.
  • the first card module and the third card module in the card are shared with the third application in the second device.
  • the first application process establishes an RPC connection between the first application process and the third application process, and sends the card of the first card to the third application process through the RPC connection between the first application process and the third application process.
  • Name and card module number of the first card module are the first card module.
  • the third application process queries whether there is a resource pack set in the card service module of the second device according to the card name of the first card. Wherein, the first card corresponding to the card name is stored in the resource pack set.
  • step S304 is executed. If there is a card application process, steps S305-S310 are executed.
  • step S303 is similar to the implementation of S101 in the embodiment of FIG. 12b, which is not limited in this application.
  • the third application process does not perform processing and cannot display the card.
  • the third application process establishes an IPC connection between the third application process and the second card service application process.
  • the second card service application process is in an inactive state by default when no card is displayed, and the third application can start the second card service application process in S305, thereby reducing resource overhead.
  • the second card service application process is in the activated state by default when no card is displayed, and the third application process does not need to start the second card service application process in S305.
  • the third application process sends the card name of the first card, the card module number and address of the first card module to the second card service application process through the IPC connection between the third application process and the second card service application process 3 .
  • the second card service application process determines the first card module associated with the card name of the first card and the card module number of the first card module, and loads the JS corresponding to the first card module from the card application process Bundle.
  • the second card service application process draws and renders to obtain a drawing result 2 based on the JS Bundle corresponding to the first card module.
  • the drawing result 2 can be understood as a frame by frame image, which is used to form the display UI of the first card module.
  • the second card service application process sends the drawing result 2 to the card container 3 of the third application process according to the address 3 through the IPC connection between the second card service application process and the third application process.
  • the third application process displays the first card module based on the drawing result 2 in the card container 3.
  • the second device uses the form of a card to display the service content pushed by the application service provider based on the user's wishes, especially key information such as frequent user use or cumbersome operation in the service content, to the user through the UI display, so that the card can be quickly downloaded
  • the first device is shared with the second device to push cards to different users according to different service scenarios.
  • the card after the recombination of the card module can be shared between different devices, and based on the user's wishes, the service content that the user wants to share can be converted to the card's
  • the form is quickly shared with other users, so that other users also have control requirements for the device, such as family members have control rights to the device or guests have temporary control requirements for the device at home, etc., which is conducive to enhancing the user experience.
  • the first application process connects to the first application process through the RPC connection between the first application process and the third application process.
  • the third application process sends the card name of the first card without sending the card module numbers corresponding to all the card modules of the first card to the second application process, which reduces the amount of data transmission.
  • the third application process sends the card name and address 3 of the first card to the second card service application process through the IPC connection between the third application process and the second card service application process, and there is no need to transfer the first card
  • the card module numbers corresponding to all the card modules in the card module are sent to the second card service application process, which reduces the amount of data transmission.
  • the user's electronic device is made to push all the service content of the application service provider based on the user's wishes in the form of a card, and present it to the user through the UI display, so as to push different cards to the user according to different service scenarios.
  • the card in addition to sharing the card to the in-vehicle device, the card can also be shared to other devices.
  • the second device can also share the card with other devices.
  • the user can drag and drop the card after the recombination of the card module in the second device to other applications or other devices in the second device.
  • the specific implementation process please refer to the foregoing content.
  • the user can stop sharing the card by ending the third application.
  • the first application process can also send the card sharing duration to the third application process while sharing the card with the third application process, so that the second card service application process can support the second card service application process within the card sharing duration through address sharing.
  • the third application displays the card, so that the second card service application process stops sharing the address in addition to the card sharing duration, and no longer supports the third application to display the card.
  • This application is not limited to the foregoing two implementation methods to stop card sharing. Therefore, the first application can realize service recovery by stopping card sharing.
  • the second card service application process can also update the drawing result 2 through address sharing.
  • FIGS. 15a to 15c are schematic diagrams of a scenario software architecture provided by an embodiment of this application.
  • the first card service module in the first device may include: a first application process, a card application process, and a first card service application process. Among them, the first card service module is located at the application layer in Figure 2a.
  • the second card service module in the second device may include: a third application process. Among them, the second card service module is located at the application layer in Figure 2a.
  • the specific implementation manners of the first application process, the card application process, and the first card service application process can be referred to the description in the embodiment of FIG. 12a, which will not be repeated here.
  • the specific implementation manner of the third application process refer to the description in the embodiment of FIG. 14a and FIG. 14b, which will not be repeated here.
  • an RPC connection can be established between the first application process and the third application process, so as to realize the mutual communication between the first application process and the third application process.
  • An IPC connection can be established between the first card service application process and the first application process, so as to realize the mutual communication between the card service application process and the first application process.
  • An RPC connection can be established between the first card service application process and the third application process, so as to realize the mutual communication between the first card service application process and the third application process.
  • Figure 15c is a signaling interaction diagram of a card sharing method provided by an embodiment of the application. As shown in FIG. 15c, the card sharing method of the present application may include: steps S401-S409.
  • the user can perform the second operation on the display UI of the first card, The second operation is used to determine the card module selected by the user to share from the first card, and the second device and third application process selected by the user, and through steps S401-S409, the user selects the card module to share from the first card Share from the first application process to the third application process in the second device. It should be noted that the user can select part of the card modules from the first card to share, or select all card modules from the first card to share, and this application does not limit it.
  • the first application process determines the first card module selected by the user to share from the first card and the second device and third application process selected by the user.
  • the first card module may be at least one card module in the first card.
  • the second operation can be associated with the first card module in the first card, or can be associated with the first card module in the first card and the third card module in the first card.
  • the third card module is not recombinable At least one card module, which is not limited in this application.
  • the second operation can also be used to instruct the first device to share the first card module in the first card with the third application in the second device, or the second operation can also be used to instruct the first device to share the first card module in the second device.
  • the first card module and the third card module in the card are shared with the third application in the second device.
  • the first application process establishes an RPC connection between the first application process and the third application process, and sends the card of the first card to the third application process through the RPC connection between the first application process and the third application process.
  • Name and card module number of the first card module are the first card module.
  • the third application process judges whether the card tag 2 of the first card associated with the card name of the first card exists, so as to determine whether the third application process can load and display the card. If the card label 2 of the first card exists, the third application process determines that the third application process can load the display card; if the card label 2 of the first card does not exist, the third application process determines that the third application process cannot load the display card .
  • the third application process sends the card name of the first card, the card module number and address of the first card module to the first card service application process through the RPC connection between the third application process and the first card service application process 3 .
  • the first card service application process determines the card module associated with the card name of the first card and the card module number of the first card module, and calls the JS Bundle corresponding to the first card module from the card application process.
  • the first card service application process draws and renders to obtain a drawing result 2 based on the JS Bundle corresponding to the first card module.
  • the first card service application process sends the drawing result 2 to the card container 3 of the third application process according to the address 3 through the RPC connection between the first card service application process and the third application process.
  • the third application process displays the first card module based on the drawing result 2 in the card container 3.
  • the second device uses the form of a card to display the service content pushed by the application service provider based on the user's wishes, especially key information such as frequent user use or cumbersome operation in the service content, to the user through the UI display, so that the card can be quickly downloaded
  • the first device is shared with the second device to push cards to different users according to different service scenarios.
  • the card after the recombination of the card module can be shared between different devices, and based on the user's wishes, the service content that the user wants to share can be converted to the card's
  • the form is quickly shared with other users, so that other users also have control requirements for the device, such as family members have control rights to the device or guests have temporary control requirements for the device at home, etc., which is conducive to enhancing the user experience.
  • the first application process communicates to the third application process through the RPC connection between the first application process and the third application process.
  • the process sends the card name of the first card without sending the card module numbers corresponding to all the card modules of the first card to the second application process, which reduces the amount of data transmission.
  • the third application process sends the card name and address 3 of the first card to the first card service application process through the RPC connection between the third application process and the first card service application process, and there is no need to transfer the first card
  • the card module numbers corresponding to all the card modules in the card module are sent to the second card service application process, which reduces the amount of data transmission.
  • cards including all card modules can be shared between different devices, so that the cards have rich UI display channels, so that cards can be pushed to different users according to different service scenarios.
  • the card in addition to sharing the card to the in-vehicle device, the card can also be shared to other devices. For details, please refer to the foregoing content, which will not be repeated here.
  • the second device can also share the card with other devices. For the specific implementation process, please refer to the foregoing content.
  • the user can stop sharing the card by ending the third application.
  • the first application process can also send the card sharing duration to the first card service application process while sharing the card with the third application, so that the first card service application process is within the card sharing duration through address sharing, Supporting the third application to display the card also enables the first card service application process to stop address sharing in addition to the card sharing duration, and no longer supports the third application to display the card.
  • This application is not limited to the foregoing two implementation methods to stop card sharing. Therefore, the first application can realize service recovery by stopping card sharing.
  • the first card service application process can also update the drawing result 2 through address sharing.
  • this application provides a card sharing method.
  • the card sharing method of this application may include: Step 21-Step 23.
  • Step 21 In response to the user's first operation, the interface of the first application is displayed.
  • the interface of the first application displays the first card, the first card includes the first card module and the second card module, and the interface resources of the first card It is provided by the second application.
  • Step 22 In response to the second operation of the user, a second message is sent to the third application.
  • the second operation is associated with the first card module, and the second message includes the identifier of the first card module.
  • Step 23 Display the interface of the third application.
  • the interface of the third application displays the first card module, and the interface resources of the first card module are provided by the fourth application.
  • steps 21 to 23 can be applied to the scenario of card sharing between different applications in the same device, and can also be applied to the scenario of card sharing between different devices.
  • the first application, the second application, and the third application are different applications in the first device.
  • the first application process corresponds to the first application
  • the second application The process corresponds to the second application
  • the third application process corresponds to the third application
  • the fourth application process corresponds to the fourth application
  • the second application and the fourth application are the same application
  • the second application process and the fourth application process are the same application Program progress.
  • the execution subject of step 21 to step 23 is the first device.
  • the execution subject of step 21 is the first application process
  • the execution subject of step 22 is the first application process
  • the execution subject of step 23 is the third application process.
  • the first operation may include, but is not limited to, at least one operation of the user such as clicking, long pressing, and sliding.
  • This application does not limit the type and number of operations of the first operation and other parameters, as long as the first application can respond to the user The first operation is sufficient to realize the display of the first card.
  • the interface resources of the first card can be understood as displaying the respective logic execution of the first card module and the second card module and resources such as code, video, data, etc. required for UI display, that is, the first card module and the second card module correspond to each other
  • the specific content of the JS Bundle and Resource can be found in the previous description, so I won’t repeat them here.
  • the second application corresponds to the first card service application in the foregoing embodiment.
  • the second operation may include, but is not limited to, at least one operation such as a user's click, long press, and swipe. This application does not limit the type and number of the second operation and other parameters. And the second operation is associated with the first card module, so that the first application can determine the first card module selected to be shared in the first card and the sharing object (ie, the second application) in response to the user's second operation.
  • the second message may also include the identification of the second application and/or the identification of the first card.
  • the interface resources of the first card module can be understood as displaying the logic execution of the first card module and the resources such as code, video, data and other resources required for UI display, that is, the JS Bundle and Resource corresponding to the first card module.
  • the resources such as code, video, data and other resources required for UI display, that is, the JS Bundle and Resource corresponding to the first card module.
  • the fourth application corresponds to the first card service application in the foregoing embodiment.
  • the first application and the second application are different applications in the first device
  • the third application and the fourth application are different applications in the second device.
  • the device is different from the second device.
  • the first application process corresponds to the first application
  • the second application process corresponds to the second application
  • the third application process corresponds to the third application
  • the fourth application process corresponds to the fourth application.
  • the execution subject of step 21 to step 23 is the first device. Specifically, the execution subject of step 21 is the first application process, the execution subject of step 22 is the first application process, and the execution subject of step 23 is the third application process.
  • the implementation process refer to the descriptions in Figures 3a-31, Figure 12a- Figure 12b, and Figure 13a- Figure 13c, or refer to the first card displayed in the first application and a feasible implementation of the second scenario The description content of the first card shared from the first application to the second application is not repeated here.
  • the first operation may include, but is not limited to, at least one operation of the user such as clicking, long pressing, and sliding.
  • This application does not limit the type and number of operations of the first operation and other parameters, as long as the first application can respond to the user The first operation is sufficient to realize the display of the first card.
  • the interface resources of the first card can be understood as displaying the respective logic execution of the first card module and the second card module and resources such as code, video, data, etc. required for UI display, that is, the first card module and the second card module correspond to each other
  • the specific content of the JS Bundle and Resource can be found in the previous description, so I won’t repeat them here.
  • the second application corresponds to the first card service application in the foregoing embodiment.
  • the second operation may include, but is not limited to, at least one operation such as a user's click, long press, and swipe. This application does not limit the type and number of the second operation and other parameters. And the second operation is associated with the first card module, so that the first application can determine the first card module selected to be shared in the first card and the sharing object (ie, the second application) in response to the user's second operation.
  • the second message may also include at least one of the device identification of the second device, the identification of the second application, or the identification of the first card.
  • the interface resources of the first card module can be understood as displaying the logic execution of the first card module and the resources such as code, video, data and other resources required for UI display, that is, the JS Bundle and Resource corresponding to the first card module.
  • the resources such as code, video, data and other resources required for UI display, that is, the JS Bundle and Resource corresponding to the first card module.
  • the fourth application corresponds to the second card service application in the foregoing embodiment.
  • the first application and the second application are different applications in the first device, and the third application is a different application in the second device.
  • the device is different, the first application process corresponds to the first application, the second application process corresponds to the second application, the third application process corresponds to the third application, the fourth application process corresponds to the fourth application, and the second application and the fourth application are the same application Program, the second application process and the fourth application process are the same application process.
  • the execution subject of step 21 to step 23 is the first device. Specifically, the execution subject of step 21 is the first application process, the execution subject of step 22 is the first application process, and the execution subject of step 23 is the third application process.
  • the implementation process refer to the descriptions in Figures 3a-31, Figure 12a- Figure 12b, and Figure 13a- Figure 13c, or refer to the first card displayed in the first application and a feasible implementation of the second scenario The description content of the first card shared from the first application to the second application is not repeated here.
  • the first operation may include, but is not limited to, at least one operation of the user such as clicking, long pressing, and sliding.
  • This application does not limit the type and number of operations of the first operation and other parameters, as long as the first application can respond to the user The first operation is sufficient to realize the display of the first card.
  • the interface resources of the first card can be understood as displaying the respective logic execution of the first card module and the second card module and resources such as code, video, data, etc. required for UI display, that is, the first card module and the second card module correspond to each other
  • the specific content of the JS Bundle and Resource can be found in the previous description, so I won’t repeat them here.
  • the second application corresponds to the first card service application in the foregoing embodiment.
  • the second operation may include, but is not limited to, at least one operation such as a user's click, long press, and swipe. This application does not limit the type and number of the second operation and other parameters. And the second operation is associated with the first card module, so that the first application can determine the first card module selected to be shared in the first card and the sharing object (ie, the second application) in response to the user's second operation.
  • the second message may also include at least one of the device identification of the second device, the identification of the second application, or the identification of the first card.
  • the interface resources of the first card module can be understood as displaying the logic execution of the first card module and the resources such as code, video, data and other resources required for UI display, that is, the JS Bundle and Resource corresponding to the first card module.
  • the resources such as code, video, data and other resources required for UI display, that is, the JS Bundle and Resource corresponding to the first card module.
  • the fourth application corresponds to the first card service application in the foregoing embodiment.
  • the first card further includes: a third card module, the third card module is also displayed in the interface of the third application, and the interface resources of the third card module are provided by the fourth application.
  • the first card module and the second card module can be configured as recombinable card modules, such as the aforementioned card module 2-card module 6 in the first card.
  • the third card module can be set as a non-recombinable card module, such as the card module 1 in the first card mentioned above.
  • the third card module is a non-recombinable card module, and the first application can determine the first card module.
  • the second card module and the third card module enable the first application to send a second message to the third application.
  • the second message includes the identification of the first card module and the identification of the third card module. Therefore, in step 23, the first card module and the third card module are displayed on the interface of the third application.
  • the first application can determine the second card module so that the first application can send a second message to the third application.
  • the second message includes the information of the first card module.
  • logo based on the third card module and the second card module belong to the first card, the third card module is a non-recombinable card module, and the first card module and the third card are displayed on the interface of the third application. Module.
  • this application can set the attributes of the card to be recombinable, or the attributes of the card can be set to be non-recombinable, for example, the card module used to indicate the service content of the card or the key information of the card is set to be non-recombinable Therefore, in response to the second operation of the user, the first application process can determine that the second card module and the third card module need to be displayed on the interface of the third application, or the third application is based on the information in the second message The identification of the first card module can determine that the second card module and the third card module need to be displayed on the interface of the third application.
  • the specific implementation process please refer to Figure 3a-3d and the description in the card explanation. Do repeats. Thus, convenience is provided for realizing card sharing.
  • step 21 in response to the user's first operation, the specific implementation process of displaying the interface of the first application may include: step 31 to step 33.
  • Step 31 Send the first message to the second application process.
  • Step 32 Receive the first drawing result from the second application process.
  • the first drawing result is obtained by rendering and drawing by the second application process based on the interface resource of the first card, and the interface resource of the first card is the second application process based on the first message.
  • the resource pack collection includes the interface resources of the first card module, the second card module, and the third card module in the first card, and the fourth card module and the fifth card module in the second card Interface resources.
  • Step 33 Display the first card in the interface of the first application based on the first drawing result.
  • the execution subject of step 31-step 33 is the first device, specifically, the execution subject of step 31-step 33 is the first application process.
  • the specific implementation process please refer to Figure 3a- Figure 3d and Figure 12a- Figure 12b.
  • this application does not limit the specific content of the first message.
  • the first message may include: the identification of the first card. For example, the card name of the first card.
  • the second application process determines the first card and the first card module and the second card module in the first card, the amount of data transmission between the first application process and the second application process is reduced.
  • the first message may include: the identification of the first card, the identification of the first card module, and the identification of the second card module.
  • the card name of the first card, the card module number of the first card module, and the card module number of the second card module For example, the card name of the first card, the card module number of the first card module, and the card module number of the second card module.
  • the first message may further include: the first address. Therefore, the first application process receives the first drawing result sent to the first address from the second application process, which facilitates the use of address sharing, which not only enables the second application process to provide the first drawing result, but also allows the first application process to Use the first drawing result to display the interface of the first application.
  • this application does not limit the specific content of the first address, for example, see address 1 mentioned above. It should be noted that, in addition to the first address from the first application process to the second application process, the first address can also be notified by the second application process to the first application process, or the first address is from the first device The operating system determines and informs the first application process and the second application process, which is not limited in this application.
  • the method further includes: when the first device has a resource bundle set, sending a first message to the second application process.
  • the first device does not have a resource pack set
  • the second application process cannot call the interface resources of the first card from the resource pack set, which helps reduce unnecessary operations performed by the first device and saves the first device Power consumption, and enables the first device to download the resource package collection in time, so as to quickly realize card sharing.
  • step 22 in response to the second operation of the user, the specific implementation process of sending the second message to the third application may include: step 41 to step 43.
  • Step 41 Send a third message to the fourth application process.
  • Step 42 Receive the second drawing result from the fourth application process.
  • the second drawing result is obtained by rendering and drawing by the fourth application process based on the interface resources of the first card module.
  • the interface resources of the first card module are based on the fourth application process.
  • the three messages are called from the resource pack set.
  • the resource pack set includes the interface resources of the first card module, the second card module and the third card module in the first card, and the fourth card module and the fifth card module in the second card. Interface resources of the card module.
  • Step 43 Display the first card module in the interface of the third application based on the second drawing result.
  • the execution subject of step 31-step 33 is the first device. Specifically, the execution subject of step 31-step 33 is the first application process.
  • the specific implementation process please refer to Figure 3a- Figure 31 and Figure 13a- Figure 13c. Steps S201-S209 in Figure 14a-14c, steps S301-S310, and Figure 15a-15c in the description of steps S401-S409, or refer to sharing the first card from the first application to the third application The content of the description is not repeated here.
  • this application does not limit the specific content of the third message.
  • the third message may include: the identification of the first card and the identification of the first card module. For example, the card name of the first card and the card module number of the first card module.
  • the fourth application process quickly determines the first card module in the first card.
  • the third message may further include: a second address. Therefore, the third application process receives the second drawing result sent to the second address from the fourth application process, so as to adopt the address sharing method, which not only allows the fourth application process to provide the second drawing result, but also allows the third application process to Use the second drawing result to display the interface of the third application.
  • this application does not limit the specific content of the second address, such as address 2 or address 3 mentioned above. It should be noted that, in addition to the second address from the third application process to the fourth application process, the second address can also be notified by the fourth application process to the third application process, or the second address is from the second device or the third application process. The operating system in a device is determined, and the third application process and the fourth application process are notified, which is not limited in this application.
  • the method may further include: in the case where it is determined that the third application process can display the card, sending a third message to the fourth application process.
  • a third message For specific implementation content, see step 201 in FIG. 13c and step 201 in FIG. 14c. The descriptions of step 301 and step 401 in FIG. 15c are not repeated here. Therefore, since the third application process cannot send the third message to the fourth application process when the third application process cannot display the card, it is beneficial to reduce unnecessary operations performed by the device where the third application process is located. The power consumption of the device where the third application process is located is saved, and the device where the third application process is located can notify the user in time that the first application cannot share the card with the third application.
  • the resource pack set further includes interface resources of the fifth application.
  • the fifth application can refer to the card application mentioned above, which will not be repeated here.
  • resource support is provided for the fifth application to realize interface display.
  • the interface of the first application includes: a first area and a second area.
  • the first card is located in the first area
  • the first application page is located in the second area
  • the interface resources of the first application page are provided by the first application.
  • the first application includes any one of a home screen, a negative screen, a control center, a notification center, or a smart home application.
  • the third application includes any one of a home screen, a negative screen, a control center, a notification center, or a smart home application.
  • the electronic device may include: at least one memory and at least one processor; the memory is used to store program instructions; the processor is used to call the program instructions in the memory to make the first device execute the card sharing method of the foregoing embodiment.
  • the present application also provides a computer program product, including: an execution instruction, the execution instruction is stored in a readable storage medium, and at least one processor of an electronic device can read the execution instruction from the readable storage medium.
  • the instruction is executed, and at least one processor executes the execution instruction to enable the electronic device to implement the card sharing method of the foregoing embodiment.
  • this application also provides a computer-readable storage medium on which a computer program is stored, and the computer program is executed by a processor to implement the card sharing method of the foregoing embodiment when the computer program is executed by an electronic device.
  • this application also provides a communication system.
  • the communication system of the present application may include: a first device and a second device; the first device is installed with a first application, and the second device is installed with a third application; the first application is used to display The interface of the first application, the interface of the first application displays the first card, the first card includes the first card module and the second card module, the interface resources of the first card are provided by the second application; the first application, It is also used to send a second message to the third application in response to the second operation of the user, the second operation is associated with the first card module, the second message is used to indicate the first card module; the third application is used to display the third The interface of the application, the interface of the third application displays the first card module, and the interface resources of the first card module are provided by the fourth application.
  • all or part of the functions can be implemented by software, hardware, or a combination of software and hardware.
  • software When implemented by software, it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions can be stored in a computer-readable storage medium.
  • 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 data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the process can be completed by a computer program instructing relevant hardware.
  • the program can be stored in a computer readable storage medium. , May include the processes of the foregoing method embodiments.
  • the aforementioned storage media include: ROM or random storage RAM, magnetic disks or optical discs and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)

Abstract

本申请提供一种卡片分享方法、电子设备及通信***。该方法包括：响应于用户的第一操作，显示第一应用的界面，第一应用的界面中显示有第一卡片，第一卡片包括第一卡片模块和第二卡片模块，第一卡片的界面资源是由第二应用提供的；响应于用户的第二操作，向第三应用发送第二消息，第二操作与第一卡片模块关联，第二消息包括第一卡片模块的标识；显示第三应用的界面，第三应用的界面中显示有第一卡片模块，第一卡片模块的界面资源是由第四应用提供的。从而，使得卡片可以在同设备中的不同应用程序之间或者在跨设备之间实现分享。

Description

卡片分享方法、电子设备及通信***
本申请要求于2020年06月08日提交中国专利局、申请号为202010512011.3、申请名称为“卡片分享方法、电子设备及通信***”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种卡片分享方法、电子设备及通信***。
背景技术
卡片是一种新的服务展示技术，广泛应用于电子设备，方便用户快速查看各类应用的服务信息。然而，现有卡片只支持应用中有限的控件组合，尤其是并不支持使用频繁或者控制入口较深的控件，且常常出现在电子设备的固定位置，展示方式单一固定，很难做到二次组合和分享。因此，如何灵活实现卡片分享是现亟需解决的问题。
发明内容
本申请提供一种卡片分享方法、电子设备及通信***，以在同设备的应用程序之间实现卡片中的部分卡片模块或者整张卡片的分享，还在跨设备之间实现卡片中的部分卡片模块或者整张卡片的分享。
第一方面，本申请提供一种卡片分享方法，包括：响应于用户的第一操作，显示第一应用的界面，第一应用的界面中显示有第一卡片，第一卡片包括第一卡片模块和第二卡片模块，第一卡片的界面资源是由第二应用提供的；响应于用户的第二操作，向第三应用发送第二消息，第二操作与第一卡片模块关联，第二消息包括第一卡片模块的标识；显示第三应用的界面，第三应用的界面中显示有第一卡片模块，第一卡片模块的界面资源是由第四应用提供的。
通过第一方面提供的卡片分享方法，基于卡片可拆分为多个卡片模块以及卡片模块可重新组合，不仅在同设备的应用程序之间实现了卡片中的部分卡片模块或者整张卡片的分享，还在跨设备之间实现了卡片中的部分卡片模块或者整张卡片的分享，从而，基于用户意愿能够通过卡片中的卡片模块或者整张卡片，方便快捷地向用户提供用户想要得到的服务内容，尤其是服务内容中频繁使用或者操作繁琐等关键信息，满足了不同场景的分享需求，有利于提升用户体验感。
在一种可能的设计中，第一卡片还包括：第三卡片模块，第三应用的界面中还显示有第三卡片模块，第三卡片模块的界面资源是由第四应用提供的。由此，本申请可将卡片的属性设置为可重新组合，也可将卡片的属性设置为不可重新组合，如用于表明卡片的服务内容或者卡片的关键信息等的卡片模块设置为不可重新组合的卡片模块，从而，第一应用进程响应于用户的第二操作，可以确定出第三应用的界面上需要显示第二卡片模块和第三卡片模块，或者，第三应用基于第二消息中的第一卡片模块的标识，可以确定出第三应用 的界面上需要显示第二卡片模块和第三卡片模块。由此，为实现卡片的分享提供给了便利性。
在一种可能的设计中，第一应用、第二应用、第三应用为第一设备中的不同的应用程序，第一应用进程对应第一应用，第二应用进程对应第二应用，第三应用进程对应第三应用，第四应用进程对应第四应用，第二应用与第四应用为同一个应用程序，第二应用进程与第四应用进程为同一个应用程序进程。从而，本申请的卡片分享方法适用于在同设备中的不同应用程序之间的使用场景中，有利于向用户提供卡片的多种显示渠道，且每种显示渠道的卡片可以相同或者不同，方便用户能够及时获取到想要获取到的服务内容。
在一种可能的设计中，第一应用和第二应用为第一设备中的不同的应用程序，第三应用和第四应用为第二设备中的不同的应用程序，第一设备与第二设备不同，第一应用进程对应第一应用，第二应用进程对应第二应用，第三应用进程对应第三应用，第四应用进程对应第四应用。从而，本申请的卡片分享方法适用于在跨设备之间的卡片分享场景，有利于向不同用户提供卡片的显示渠道，且不同设备提供各自的卡片的资源支持，降低了不同设备之间的依赖性，实现了不同设备间的解耦。
在一种可能的设计中，第一应用和第二应用为第一设备中的不同的应用程序，第三应用为第二设备中的不同的应用程序，第一设备与第二设备不同，第一应用进程对应第一应用，第二应用进程对应第二应用，第三应用进程对应第三应用，第四应用进程对应第四应用，第二应用与第四应用为同一个应用程序，第二应用进程与第四应用进程为同一个应用程序进程。从而，本申请的卡片分享方法适用于在跨设备之间的卡片分享场景，有利于向不同用户提供卡片的显示渠道，且不同设备中的卡片的UI显示由一个设备提供资源支持，确保了卡片能够在不同设备中连续显示。
在一种可能的设计中，向第二应用进程发送第一消息；从第二应用进程接收第一绘制结果，第一绘制结果是第二应用进程基于第一卡片的界面资源渲染绘制得到的，第一卡片的界面资源是第二应用进程基于第一消息从资源包集合中调用得到的，资源包集合包括第一卡片中的第一卡片模块、第二卡片模块和第三卡片模块的界面资源以及第二卡片中的第四卡片模块和第五卡片模块的界面资源；基于第一绘制结果在第一应用的界面中显示第一卡片。由此，至少一个卡片可以嵌入到电子设备的任意一个应用程序中，从而以卡片的方式向用户显示服务内容，使得卡片具备丰富的UI显示渠道，能够满足不同的用户需求。
在一种可能的设计中，第一消息包括：第一卡片的标识。从而，在第二应用进程确定出第一卡片以及第一卡片中的第一卡片模块和第二卡片模块的基础上，减少了第一应用进程与第二应用进程之间的数据传输量。
在一种可能的设计中，第一消息包括：第一卡片的标识、第一卡片模块的标识和第二卡片模块的标识。从而，使得第二应用进程可以准确地确定出第一卡片中的第一卡片模块和第二卡片模块，并及时调用第一卡片中的第一卡片模块和第二卡片模块的界面资源，实现第一卡片的渲染绘制，使得第一应用能够快速显示第一卡片。
在一种可能的设计中，第一消息还包括：第一地址；从第二应用进程接收发送到第一地址中的第一绘制结果，为提供第一绘制结果提供一种可能的实现方式。另外，通过地址分享的方式，不仅可以实现第一绘制结果的更新，还可以停止卡片的分享以回收服务。
在一种可能的设计中，该方法还包括：在第一设备有资源包集合的情况下，向第二应 用进程发送第一消息。从而，由于在第一设备没有资源包集合的情况下，第二应用进程便无法从资源包集合中调用第一卡片的界面资源，因此，有利于降低第一设备执行不必要的操作，节省第一设备的功耗，还使得第一设备可以及时下载资源包集合，以便快速实现卡片分享。
在一种可能的设计中，向第四应用进程发送第三消息；从第四应用进程接收第二绘制结果，第二绘制结果是第四应用进程基于第一卡片模块的界面资源渲染绘制得到的，第一卡片模块的界面资源是第四应用进程基于第三消息从资源包集合中调用得到的，资源包集合包括第一卡片中的第一卡片模块、第二卡片模块和第三卡片模块的界面资源以及第二卡片中的第四卡片模块和第五卡片模块的界面资源；基于第二绘制结果在第三应用的界面中显示第一卡片模块。由此，卡片可以分享到同一设备中的不同应用程序中或者不同设备中，满足了不同场景的分享需求。
在一种可能的设计中，第三消息包括：第一卡片的标识和第一卡片模块的标识。从而，使得第四应用进程能够准确地确定出第一卡片和第一卡片模块，并及时调用第一卡片中第一卡片模块的界面资源，实现第一卡片模块的渲染绘制，使得第三应用能够快速显示第一卡片模块。
在一种可能的设计中，第三消息还包括：第二地址；从第四应用进程接收发送到第二地址中的第二绘制结果，为提供第二绘制结果提供一种可能的实现方式。另外，通过地址分享的方式，不仅可以实现第二绘制结果的更新，还可以停止卡片的分享以回收服务。
在一种可能的设计中，该方法还包括：在确定第三应用进程能够显示卡片的情况下，向第四应用进程发送第三消息。从而，由于在第三应用进程不能够显示卡片的情况下，第三应用进程便无法向第四应用进程发送第三消息，因此，有利于降低第三应用进程所在的设备执行不必要的操作，节省第三应用进程所在的设备的功耗，且使得第三应用进程所在的设备可以及时向用户通知第一应用无法向第三应用分享卡片。
在一种可能的设计中，资源包集合还包括第五应用的界面资源。从而，为第五应用实现界面显示提供了资源支持。
在一种可能的设计中，第一应用的界面包括：第一区域和第二区域；第一卡片位于第一区域，第一应用页面位于第二区域，第一应用页面的界面资源是由第一应用提供的。从而，丰富了第一应用的界面，使得第一应用不仅可以显示一个或者多个卡片，还可以显示第一应用页面。对应的，第三应用等其他应用也可同时支持卡片和应用页面的显示。
在一种可能的设计中，第一应用包括：主屏幕、负一屏、控制中心、通知中心或者智能家居应用中的任意一个。其中，第一应用可为第一设备中各种类型的应用程序，有利于丰富卡片显示和卡片分享的渠道。
在一种可能的设计中，第三应用包括：主屏幕、负一屏、控制中心、通知中心或者智能家居应用中的任意一个。其中，第三应用可为第一设备或者第二设备中各种类型的应用程序，有利于丰富卡片显示和卡片分享的渠道。
第二方面，本申请提供一种电子设备，包括：至少一个存储器和至少一个处理器；存储器用于存储程序指令；处理器用于调用存储器中的程序指令使得电子设备执行第一方面及第一方面任一种可能的设计中的卡片分享方法。
第三方面，本申请提供一种计算机可读存储介质，其上存储有计算机程序，计算机程 序被处理器使得电子设备执行时实现第一方面及第一方面任一种可能的设计中的卡片分享方法。
第四方面，本申请提供一种计算机程序产品，包括：执行指令，执行指令存储在可读存储介质中，电子设备的至少一个处理器可以从可读存储介质读取执行指令，至少一个处理器执行执行指令使得电子设备实现第一方面及第一方面任一种可能的设计中的卡片分享方法。
第五方面，本申请提供一种通信***，包括：第一设备和第二设备；第一设备中安装有第一应用，第二设备安装有第三应用；第一应用，用于响应于用户的第一操作，显示第一应用的界面，第一应用的界面中显示有第一卡片，第一卡片包括第一卡片模块和第二卡片模块，第一卡片的界面资源是由第二应用提供的；第一应用，还用于响应于用户的第二操作，向第三应用发送第二消息，第二操作与第一卡片模块关联，第二消息用于指示第一卡片模块；第三应用，用于显示第三应用的界面，第三应用的界面中显示有第一卡片模块，第一卡片模块的界面资源是由第四应用提供的。
上述第五面以及上述第五面的各可能的设计中所提供的网络设备，其有益效果可以参见上述第一方面和第一方面的各可能的实施方式所带来的有益效果，在此不再赘述。
附图说明
图1为本申请一实施例提供的一种电子设备的结构示意图；
图2a为本申请一实施例提供的一种电子设备的软件结构框图；
图2b为本申请一实施例提供的一种卡片服务引擎的软件结构框图；
图3a-图3l为本申请一实施例提供的人机交互界面示意图；
图4a-图4b为本申请一实施例提供的人机交互界面示意图；
图5a-图5d为本申请一实施例提供的人机交互界面示意图；
图6a-图6d为本申请一实施例提供的人机交互界面示意图；
图7为本申请一实施例提供的一种卡片的界面示意图；
图8为本申请一实施例提供的一种卡片模块的代码示意图；
图9a-图9b为本申请一实施例提供的人机交互界面示意图；
图10a-图10b为本申请一实施例提供的人机交互界面示意图；
图11为本申请一实施例示意的一种应用程序的代码示意图；
图12a为本申请一实施例示意的一种场景软件架构示意图；
图12b为本申请一实施例提供的一种卡片分享方法的信令交互图；
图13a-图13b为本申请一实施例示意的一种场景软件架构示意图；
图13c为本申请一实施例提供的一种卡片分享方法的信令交互图；
图14a-图14b为本申请一实施例示意的一种场景软件架构示意图；
图14c为本申请一实施例提供的一种卡片分享方法的信令交互图；
图15a-图15b为本申请一实施例示意的一种场景软件架构示意图；
图15c为本申请一实施例提供的一种卡片分享方法的信令交互图。
具体实施方式
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，单独a，单独b或单独c中的至少一项(个)，可以表示：单独a，单独b，单独c，组合a和b，组合a和c，组合b和c，或组合a、b和c，其中a，b，c可以是单个，也可以是多个。此外，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性。
本申请提供一种卡片分享方法，基于卡片可拆分为多个卡片模块以及卡片模块可重新组合，不仅在同设备的应用程序之间实现了卡片中的部分卡片模块或者整张卡片的分享，还在跨设备之间实现了卡片中的部分卡片模块或者整张卡片的分享，从而，基于用户意愿能够通过卡片中的卡片模块或者整张卡片，方便快捷地向用户提供用户想要得到的服务内容，尤其是服务内容中频繁使用或者操作繁琐等关键信息，满足了不同场景的分享需求，有利于提升用户体验感。
例如，该电子设备可以是手机、平板电脑、可穿戴设备、车载设备、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、笔记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本、个人数字助理(personaldigital assistant，PDA)、智能电视、智慧屏、高清电视、4K电视、智能音箱、智能投影仪等物联网(the internet of things，IOT)设备，本申请对电子设备的具体类型不作任何限制。
下面以电子设备为手机为例，结合图1，介绍本申请涉及的电子设备。
图1为本申请一实施例提供的一种电子设备的结构示意图。如图1所示，电子设备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为电子设备供电。
电源管理模块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静止时可检测出重力的大小及方向。还可以用于识别电子设备姿态，应用于横竖屏切换，计步器等应用。
距离传感器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分离。
电子设备100的软件***可以采用分层架构，事件驱动架构，微核架构，微服务架构，或云架构。本申请以分层架构的Android***为例，示例性说明电子设备100的软件结构。其中，本申请对电子设备的操作***的类型不做限定。例如，Android***、鸿蒙操作***(Harmony Operating System，鸿蒙OS)等。
图2a为本申请一实施例提供的一种电子设备的软件结构框图。如图2a所示，分层架构将软件分成若干个层，每一层都有清晰的角色和分工。层与层之间通过软件接口通信。在一些实施例中，将Android***分为四层，从上至下分别为应用程序层，应用程序框架层，安卓运行时(Android runtime)和***库，以及内核层。
应用程序层可以包括一系列应用程序包。
如图2a所示，应用程序包可以包括相机，图库，日历，通话，地图，导航，WLAN，蓝牙，音乐，视频，游戏，购物，出行，即时通信(如短信息)，智能家居，设备控制等应用程序。
其中，智能家居应用可用于对具有联网功能的家居设备进行控制或管理。例如，家居设备可以包括电灯、电视和空调。又如，家居设备还可以包括防盗门锁、音箱、扫地机器人、插座、体脂秤、台灯、空气净化器、电冰箱、洗衣机、热水器、微波炉、电饭锅、窗帘、风扇、电视、机顶盒、门窗等。
另外，应用程序包还可以包括：主屏幕(即桌面)，负一屏，控制中心，通知中心，卡片应用，卡片服务应用等应用程序。
其中，负一屏，又可称为“-1屏”，是指在电子设备的主屏幕向右滑动屏幕，直至滑动至最左侧分屏的用户界面(user interface，UI)。例如，负一屏可以用于放置一些快捷服务功能和通知消息，比如全局搜索、应用程序某个页面的快捷入口(付款码、微信等)、即时信息及提醒(快递信息、支出信息、通勤路况、打车出行信息、日程信息等)及关注动态(足球看台、篮球看台、股票信息等)等。控制中心为电子设备的下拉消息通知栏，即当用户在电子设备上进行向下操作时电子设备所显示出的用户界面。通知中心为电子设备的上拉消息通知栏，即当用户在电子设备上进行向上操作时电子设备所显示出的用户界面。卡片应用可参见下文提及的内容，此处不做赘述。卡片服务应用，用于提供卡片服务，以支持卡片的UI显示、卡片在同设备中各个应用程序之间的分享以及卡片在跨设备之间的分享等。
应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。应用程序框架层包括一些预先定义的函数。
如图2a所示，应用程序框架层可以包括窗口管理器，内容提供器，视图***，电话管理器，资源管理器，通知管理器，卡片服务(Service)引擎等。
窗口管理器用于管理窗口程序。窗口管理器可以获取显示屏大小，判断是否有状态栏，锁定屏幕，截取屏幕等。
内容提供器用于存放和获取数据，并使这些数据可以被应用程序访问。所述数据可以包括视频，图像，音频，拨打和接听的电话，浏览历史和书签，电话簿等。
视图***包括可视控件，例如显示文字的控件，显示图片的控件等。视图***可用于 构建应用程序。显示界面可以由一个或多个视图组成的。例如，包括短信通知图标的显示界面，可以包括显示文字的视图以及显示图片的视图。
电话管理器用于提供电子设备100的通信功能。例如通话状态的管理(包括接通，挂断等)。
资源管理器为应用程序提供各种资源，比如本地化字符串，图标，图片，布局文件，视频文件等等。
通知管理器使应用程序可以在状态栏中显示通知信息，可以用于传达告知类型的消息，可以短暂停留后自动消失，无需用户交互。比如通知管理器被用于告知下载完成，消息提醒等。通知管理器还可以是以图表或者滚动条文本形式出现在***顶部状态栏的通知，例如后台运行的应用程序的通知，还可以是以对话窗口形式出现在屏幕上的通知。例如在状态栏提示文本信息，发出提示音，电子设备振动，指示灯闪烁等。
卡片服务引擎用于支撑卡片服务应用实现卡片的渲染展示，还用于负责事件、API等调用处理。
图2b为本申请一实施例提供的一种卡片服务引擎的软件结构框图。如图2b所示，卡片服务引擎可以包括：前端框架、后端引擎和适配层(porting layout)。其中：
前端框架包括：服务前端和Javascript Engine。
后端引擎包括：component、API、component tree、element tree、render tree、eventmanager、focus、theme、channel、animation、layout、image provider和cardview。
适配层用于对接如surface、event、vsync、life cycle等***，以适配不同类型的操作***的***库。
安卓运行时包括核心库和虚拟机。安卓运行时负责Android***的调度和管理。
核心库包含两部分：一部分是java语言需要调用的功能函数，另一部分是Android***的核心库。
应用程序层和应用程序框架层运行在虚拟机中。虚拟机将应用程序层和应用程序框架层的java文件执行为二进制文件。虚拟机用于执行对象生命周期的管理，堆栈管理，线程管理，安全和异常的管理，以及垃圾回收等功能。
***库可以包括多个功能模块。例如：表面管理器(surface manager)，媒体库(Media Libraries)，三维图形处理库(例如：OpenGLES)，2D图形引擎(例如：SGL)等。
表面管理器用于对显示子***进行管理，并且为多个应用程序提供了2D和3D图层的融合。
媒体库支持多种常用的音频，视频格式回放和录制，以及静态图像文件等。媒体库可以支持多种音视频编码格式，例如：MPEG4，H.264，MP3，AAC，AMR，JPG，PNG等。
三维图形处理库用于实现三维图形绘图，图像渲染，合成，和图层处理等。
2D图形引擎是2D绘图的绘图引擎。
内核层是硬件和软件之间的层。内核层至少包含显示驱动，摄像头驱动，音频驱动，传感器驱动。
下面结合利用智能音箱播放声音的场景，示例性说明电子设备100的软件和硬件的工作流程。
当触摸传感器180K接收到触摸操作，相应的硬件中断被发给内核层。内核层将触摸 操作加工成原始输入事件(包括触摸坐标，触摸操作的时间戳等信息)。原始输入事件被存储在内核层。应用程序框架层从内核层获取原始输入事件，识别该输入事件所对应的控件。以该触摸操作是触摸单击操作，该单击操作所对应的控件为智能音箱图标的控件为例，智能音箱应用调用应用框架层的接口，启动智能音箱应用，进而通过调用内核层启动音频驱动，通过扬声器170A将音频电信号转换成声音信号。
可以理解的是，本申请示意的结构并不构成对电子设备100的具体限定。在另一些实施例中，电子设备100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
基于前述描述，电子设备可以将卡片或者卡片中的卡片模块，分享给电子设备的其他应用程序，实现同设备的不同应用程序之间的卡片分享，或者分享给其他电子设备，实现在跨设备之间的卡片分享。
下面，结合场景一和场景二，对任意一张卡片分享的实现过程进行详细说明。
场景一
场景一中，本申请将第一设备中的第一应用所显示的第一卡片分享到第一设备中的第二应用。图3a-图3l为本申请一实施例提供的人机交互界面示意图。以第一设备为手机，第一应用为手机中的智能家居应用，第一卡片对应于智能家居应用推送的播放音乐服务，第二应用为手机的负一屏为例。
其中，第一卡片包括：卡片模块1、卡片模块2、卡片模块3、卡片模块4、卡片模块5和卡片模块6。其中，卡片模块1为不可重新组合的。卡片模块2、卡片模块3、卡片模块4、卡片模块5和卡片模块6均为可重新组合的。
卡片模块1，用于表示卡片对应的服务为智能音箱应用推送的播放音乐服务，如采用智能音箱图标和文字“HUAWEI Sound X”表示。
卡片模块2，用于表示智能音箱的蓝牙连接功能，如采用文字“在线”和蓝牙图标的操作按钮表示。
卡片模块3，用于表示智能音箱的当前播放歌曲名称、切换歌曲和调节音量大小的功能，如采用歌曲名称“半岛铁盒”、上一首图标的操作按钮、播放/暂停图标的操作按钮和下一首图标的操作按钮、文字“音量”、音量图标、用于调节音量的滑动操作按钮以及文字“68％”表示。
卡片模块4，用于表示智能音箱的音乐有声功能，如采用文字“音乐有声”和耳机图标的操作按钮表示。
卡片模块5，用于表示智能音箱的语音技能功能，如采用文字“语音技能”和学习图标的操作按钮表示。
卡片模块6，用于表示智能音箱的立体声功能，如采用文字“立体声”和立体声图标的操作按钮表示。
请参考图3a-图3l，本申请的卡片分享方法可以包括：步骤11-步骤15。
步骤11：如果用户想要启动智能家居应用中的第一卡片，用户可以在如图3b所示的第一设备的显示屏上点击智能家居应用的图标，手机的显示屏显示如图3c所示的界面，用户点击界面上第一卡片的图标，其中，将“HUAWEI Sound X”和智能音箱图标共同设置 在一个圆角矩形框来表示第一卡片的图标，手机的显示屏显示如图3d所示的第一卡片的UI，以便向用户提供第一卡片的服务内容。
步骤12：如果用户想要查看第一卡片，用户可在如图3d所示的第一卡片的空白处进行长按操作，则手机的显示屏显示如图3e所示的界面，该界面上的卡片模块2、卡片模块3、卡片模块4、卡片模块5和卡片模块6的右下方均显示一个选项，该选项用于指示对应的卡片模块是否被选中进行分享，如方框图标的操作按钮。本文提及的长按操作可以理解为用户执行操作的时长满足预设时长所对应的操作。
步骤13：用户可以在如图3e所示的界面上勾选在线和语音技能的服务功能，用户可以分别点击卡片模块2显示的方框图标和卡片模块5显示的方框图标，则卡片模块2对应的方框图标和卡片模块5对应的方框图标中均会出现如图3f所示的对勾图标。其中，该对勾图标用于表示卡片模块被选择且待分享。用户可继续点击文字“分享”的操作按钮，则手机的显示屏跳转至如图3g所示的页面。
步骤14：如图3g所示，该页面显示有预览区域、跨设备分享选项以及本设备分享选项。
其中，预览区域中显示有卡片模块1、卡片模块2和卡片模块5。卡片模块1采用智能音箱图标和文字“HUAWEI Sound X”进行表示，卡片模块2采用和蓝牙图标的操作按钮进行表示，卡片模块5采用学习图标的操作按钮进行表示。
其中，跨设备分享选项中包括：车载图标、电视图标、手机图标、平板电脑图标、手表图标和笔记本图标。车载图标对应于唯一的车载设备，电视图标对应电视机，手机图标对应手机，平板电脑图标对应平板电脑，手表图标对应手表，笔记本图标对应笔记本。
其中，本设备分享选项中包括：文字“添加到桌面”的操作按钮、文字“添加到负一屏”的操作按钮、“添加到控制中心”的操作按钮和文字“添加到通知中心”的操作按钮。
其中，本申请对该页面中预览区域、跨设备分享选项和本设备分享选项各自的形状大小、位置布局、表示内容、设备数量和设备类型等参数不做限定。需要说明的是，该页面不限于图3g所示的表示方式。
步骤15：如果用户想要将第一卡片分享到负一屏，用户在本设备分享选项中的文字“添加到负一屏”的操作按钮上进行点击操作，则手机的负一屏便显示如图3h所示的包括有卡片模块1、卡片模块2和卡片模块5的卡片。
由此，负一屏从如图3a所示的界面变为如图3h所示的界面，该界面上增加了包括有卡片模块1、卡片模块2和卡片模块5的卡片，该卡片的UI与预览区域显示的内容的布局相同。另外，该卡片的UI也可以与预览区域显示的内容的布局不同。
其中，用户在如图3b所示的显示屏上向右滑动操作，手机的显示屏便显示如图3a所示的界面，即手机的负一屏在卡片未分享之前的界面。需要说明的是，负一屏上显示的客厅的电视的卡片，可以按照与步骤11-步骤15的相似描述，从智能家居应用分享到负一屏，此处不做赘述。
在一些实施例中，手机的负一屏可能未开启。此时，用户在如图3g所示的界面上点击文字“添加到负一屏”的操作按钮，手机的显示屏可显示出图3i所示的界面，该界面上可以弹出一个圆角矩形框，该圆角矩形框中显示有文字“未打开负一屏”以及“设置”的操作按钮，使得用户及时获知由于负一屏未打开而无法将第一卡片分享到负一屏。
用户可以点击“设置”的操作按钮，手机的显示屏便显示“更多设置”的界面，该界面上显示有“桌面布局”的设置操作按钮、“摇一摇”的开关操作按钮、“图标角标”的开关操作按钮、“循环滑动”的开关操作按钮和“HiBoard(负一屏)”的开关操作按钮，用户可以点击“HiBoard(负一屏)”的开关操作按钮，将HiBoard(负一屏)打开，如图3k所示。用户点击如图3k所示的界面上的返回按钮，该返回按钮采用如位于左上角的向左箭头进行表示。手机的显示屏返回到如图3l所示的界面，即图3g所示的界面。
用户在如图3l所示的界面上点击文字“添加到负一屏”的操作按钮，手机的显示屏可显示出图3h所示的界面，使得包括有卡片模块1、卡片模块2和卡片模块5的卡片可以分享到手机的负一屏。
综上，卡片或者卡片中的卡片模块能够在同一设备的不同应用程序之间实现分享，有利于通过同一设备的不同显示渠道向用户提供卡片，方便用户快速查找卡片，避免了由于服务内容的控制入口比较深而导致用户操作繁琐且复杂的问题，使得用户方便快捷地查找到卡片对应的服务内容，简化了用户的复杂操作，满足了用户高频操作的诉求，提升了用户的操作体验感。
场景二
场景二中，本申请将第一设备中的第一应用所显示的第一卡片分享到第二设备中的第三应用。图4a-图4b为本申请一实施例提供的人机交互界面示意图。以第一设备为手机，第一应用为手机中的智能家居应用，第一卡片对应于智能家居应用推送的播放音乐服务，第二设备为车载设备，第三应用为车载设备的主屏幕为例。其中，第一卡片的具体内容可参见图3a-图3l所示描述，此处不做赘述。
请参考图4a-图4b，本申请的卡片分享方法可以包括：步骤21-步骤25。其中，步骤21-步骤24分别与图3a-图3l中的步骤11-步骤14所描述的内容，此处不做赘述。
步骤25：如果用户想要将第一卡片分享到车载设备，如图4a所示，用户点击跨设备分享选项中的车载图标的操作按钮，则车载设备的主屏幕便显示如图4b所示的包括有卡片模块1、卡片模块2和卡片模块5的卡片。
由此，车载设备的主屏幕新增了包括有卡片模块1、卡片模块2和卡片模块5的卡片，该卡片的UI与预览区域显示的内容的布局不同。另外，该卡片的UI也可以与预览区域显示的内容的布局相同。
综上，卡片或者卡片中的卡片模块能够在不同设备之间实现分享，有利于通过不同设备的显示渠道向用户提供服务内容，使得多个用户通过卡片的形式同时具备控制诉求，如家庭成员或者客人对家中设备具备临时的控制诉求等，满足了不同场景的分享需求，提升了用户的操作体验感。
需要说明的是，场景一和场景二中，本申请包括但不限于上述内容提及的用户操作、界面布局、界面大小、显示内容等参数。另外，不同类型的设备，第一卡片的UI可以相同，也可以不同，本申请对此不做限定。
基于场景一和场景二的描述，如果用户在第一应用中未找到第一卡片，用户可以从如云端下载市场等服务器中下载安装第一卡片，或者从第一设备的本地存储中下载安装第一 卡片，本申请对此不做限定。
下面以智能家居应用为例，示例性说明智能家居应用下载第一卡片的实现过程。
图5a-图5d为本申请一实施例提供的人机交互界面示意图。以第一设备为手机，第一应用为手机中的智能家居应用，第一卡片对应于智能家居应用推送的播放音乐服务为例。
请参见图5a-图5d，如果用户执行步骤11或步骤21，手机的显示屏显示如图5a所示的界面，而不是如图3c所示的界面，用户需要从智能家居应用中下载第一卡片。用户可以点击添加操作按钮，手机的显示屏显示如图5b所示的界面。其中，该界面上包括已添加卡片选项和所有卡片选项。已添加卡片选项中包括：主卧的台灯的卡片、客厅的空调的卡片、插头的卡片、客厅的电视的卡片和空气净化器的卡片。所有卡片中包括：第一卡片和体脂秤的卡片。需要说明的是，已添加卡片选项中的卡片也可以参见图5a-图5d所示的描述添加到智能家居应用中，此处不做赘述。
如图5b所示，用户可点击第一卡片上的添加操作按钮，手机的显示屏显示出如图5c所示的界面，该界面中已添加卡片选项中新增了第一卡片。用户可点击一个选项，该选项用于表示已完成添加卡片，如图5c所示的对勾图标，手机的显示屏显示出如图5d所示的界面，即图3c所示的界面，使得第一卡片添加到智能家居应用中，方便用户实现第一卡片的分享。
在第一卡片添加到智能家居应用的过程中，智能家居应用不仅可以获取到第一卡片的卡片名称，还可以获取到第一卡片中全部卡片模块的卡片模块编号，即卡片模块1的卡片模块编号、卡片模块2的卡片模块编号、卡片模块3的卡片模块编号、卡片模块4的卡片模块编号、卡片模块5的卡片模块编号和卡片模块6的卡片模块编号。从而使得用户将第一卡片中的全部卡片模块分享给第二应用或者第二设备。
在一些实施例中，用户还可以选择将第一卡片中的卡片模块添加到智能家居应用中，以便灵活显示单一卡片的UI，满足不同的显示需求。另外，用户还可以选择将第一卡片中的卡片模块与第二卡片中的卡片模块组合添加到智能家居应用中，有利于灵活显示不同卡片的UI，满足不同的显示需求。
下面继续以智能家居应用为例，示例性说明智能家居应用下载第一卡片的实现过程。
图6a-图6d为本申请一实施例提供的人机交互界面示意图。以第一设备为手机，第一应用为手机中的智能家居应用，第一卡片对应于智能家居应用推送的播放音乐服务为例。
请参见图6a-图6d，用户在手机的显示屏所显示的如图5a所示的界面上点击添加操作按钮，手机的显示屏显示如图6a所示的界面。用户点击第一卡片上的一个选项，该选项用于展示第一卡片中的卡片模块，如图6a所示上的展开操作按钮，手机的显示屏显示如图6b所示的界面，该界面上包括卡片模块2、卡片模块4、卡片模块5和卡片模块6，且该界面上的卡片模块2、卡片模块4、卡片模块5和卡片模块6的右下方均显示一个选项，该选项用于指示对应的卡片模块是否被选中，如方框图标的操作按钮。
用户可以在如图6b所示的界面上分别点击卡片模块2显示的方框图标和卡片模块5显示的方框图标，则卡片模块2显示的方框图标和卡片模块5显示的方框图标中均会出现如图6b所示的对勾图标。其中，该对勾图标用于表示卡片模块被选择。
如图6c所示，用户可点击第一卡片上的添加操作按钮，手机的显示屏显示出如图6c所示的界面，该界面中已添加卡片选项中新增了第一卡片，且该界面上还显示有第一卡片 中的卡片模块2对应的图标和卡片模块5对应的图标。用户可点击一个选项，该选项用于表示已完成添加卡片，如图6c所示的对勾图标，手机的显示屏显示出如图6d所示的界面，使得第一卡片添加到智能家居应用中，方便用户实现第一卡片的分享。
在第一卡片添加到智能家居应用的过程中，智能家居应用不仅可以获取到第一卡片的卡片名称，还可以获取到第一卡片中卡片模块2的卡片模块编号和卡片模块5的卡片模块编号。从而使得用户将第一卡片中的卡片模块分享2和卡片模块5分享给第二应用或者第二设备。
综上，至少一个卡片可以嵌入到电子设备的任意一个应用程序中，从而以卡片的方式向用户显示服务内容，使得卡片具备丰富的UI显示渠道，能够满足不同的用户需求。
本申请中，卡片(card)是一种嵌入式服务形态，可嵌入在应用进程或者操作***中，直观地向用户展示关键的内容(如关于同一主题的图片、文本、视频、链接等)，以满足用户需求。
一般情况下，一张卡片对应于应用程序中的一个服务，如购物应用中订单物流服务，出行应用中票务信息服务，智能音箱应用中播放声音服务等。每张卡片可拆分为对应的多个卡片模块(complication)，即卡片可拆分。
其中，卡片模块是卡片重新组合的最小单元，或者说，卡片模块是卡片分享的最小单元。可以理解为，卡片中的每个卡片模块均为可重新组合的，以便实现卡片中至少一个卡片模块的重新组合。或者，卡片中的部分卡片模块为可重新组合的，且剩余卡片模块为不可重新组合的，以便实现剩余卡片模块和部分卡片模块中的至少一个卡片模块的重新组合。
一个卡片模块可由多个组件组合。一个组件可以包括但不限于为信息、图片、文本、操作按钮、音视频、链接等。组合的组件不同，则对应的卡片模块显示不同的UI，使得不同卡片通过包括不同的卡片模块以实现不同的UI显示。从而，不仅方便每张卡片由多个卡片模块实现存储和管理，且可支持每张卡片中部分或者全部卡片模块的UI显示，有利于快速实现和更新每张卡片的UI显示。
其中，每张卡片所包括的卡片模块可以是应用程序的服务提供商通过将每个服务拆分为对应的卡片模块，并下发给电子设备的卡片应用进程，也可以是应用程序的服务提供商向卡片服务应用进程发送服务内容，由卡片服务应用进程基于服务内容将每个服务拆分为对应的卡片模块，并下发给电子设备的卡片应用进程。卡片服务应用进程和卡片应用进程的具体内容可参见下文描述内容，此处不做赘述。
其中，每张卡片具有唯一的标识，即卡片身份标识(identity document，ID)，如卡片名称或者卡片编号等表示形式。为了便于说明，本申请中以卡片的标识为卡片名称为例进行示意。每张卡片中所包括的卡片模块均与该卡片的卡片名称相关联，以便电子设备基于卡片名称来存储每张卡片所包括的卡片模块。且每个卡片模块具有唯一的标识，如卡片模块编号，且该标识可以如采用二进制数、字符串等表示形式。为了便于说明，本申请中以卡片模块的标识为卡片模块编号为例进行示意。
在卡片模块下发给电子设备时，卡片名称也同时下发给电子设备，以便快速确定与卡片名称对应的卡片以及该卡片中的全部卡片模块，或者，卡片名称和卡片模块编号也同时下发给电子设备，以便快速确定与卡片名称对应的卡片以及该卡片中的卡片模块。
其中，本申请对卡片的视觉样式不做限定。此处提及的视觉样式，又称“样式”，是指事物呈现给人视觉上的感受，包括事物的形状、结构、大小、色彩、动静等。例如，电子设备显示卡片时，卡片的视觉样式可以包括卡片的形状(如矩形)、颜色(如白色、黑色、彩色等)、尺寸、卡片模块的位置布局、卡片模块的形状等。
在一个具体实施例中，以如图3d所示的第一卡片为例，如图7所示，该第一卡片包括：卡片模块1、卡片模块2、卡片模块3、卡片模块4、卡片模块5和卡片模块6(图7中以对应的数字分别对6个卡片模块进行示意)。其中：
卡片模块1，对应于图8所示的关于智能音箱图标和文字“HUAWEI Sound X”的代码。
卡片模块2，对应于图8所示的关于文字“在线”和蓝牙图标的操作按钮的代码。
卡片模块4，对应于图8所示的关于文字“音乐有声”和耳机图标的操作按钮的代码。
卡片模块5，对应于图8所示的关于文字“语音技能”和学习图标的操作按钮的代码。
需要说明的是，任意一张卡片可以仅包括可重新组合的卡片模块。例如，第一卡片包括第一卡片模块和第二卡片模块，第一卡片模块和第二卡片模块可以均可重新组合的卡片模块。另外，任意一张卡片可以包括可重新组合的卡片模块和不可重新组合的卡片模块。例如，第一卡片包括第一卡片模块、第二卡片模块和第三卡片模块，第一卡片模块和第二卡片模块可以均可重新组合的卡片模块，第三卡片模块可以为不可重新组合的卡片模块。本申请提及的重新组合可以理解为用户可进行选择及分享。
另外，每张卡片可以关联该卡片对应的一个或者多个UI，方便用户通过在该卡片上执行操作可以实现跳转至该卡片对应的应用程序的页面的功能。
一方面，操作按钮还可以链接到操作按钮对应的应用程序的某个页面。例如，用户点击图9a所示的第一卡片中歌曲名称“半岛铁盒”操作按钮，则手机的显示屏可以跳转至歌曲名称“半岛铁盒”的歌词页面，该歌词页面中显示有歌曲名称“半岛铁盒”的歌词的部分内容、上一首图标的操作按钮、播放/暂停图标的操作按钮和下一首图标的操作按钮、文字“音量”和表示音量的“68％”、用于调节音量的滑动操作按钮等。
另一方面，卡片自身也可以链接到如卡片应用的页面。例如，如图10a所示，用户通过点击第一卡片上一选项，该选项用于表示关闭第一卡片的显示，则手机的显示屏显示如图10b所示的界面，即图3c所示的界面。
请参见图10b，如图10b所示，该界面中包括：智能家居应用的应用页面101、6个卡片(102-107)的UI以及1个选项108，该选项108用于添加卡片。其中，6个卡片的内容可参见前文描述，此处不做赘述。为了便于说明，6个卡片(102-107)以第一卡片和第二卡片为例进行示意。其中：
智能家居应用的应用页面101对应于如图11所示的应用页面的代码。从而，使得智能家居应用实现应用页面的UI显示。
第一卡片的UI对应于如图11所示的第一卡片的代码，该代码中嵌入第一卡片的卡片标签“card src”，该卡片标签中携带有第一卡片的卡片名称“fa.soundx.soundXcard”。从而，使得智能家居应用实现第一卡片的UI显示。
第二卡片的UI对应于如图11所示的第二卡片的代码，该代码中嵌入第二卡片的卡片标签“card src”，该卡片标签中携带有第二卡片的卡片名称“fa.aircondition.airconditioncard”。 从而，使得智能家居应用实现第二卡片的UI显示。
1个选项108的UI对应于如图11所示的卡槽的代码，该代码中嵌入第二卡片的卡片标签“card”。从而，使得智能家居应用实现对新增卡片(如重新组合卡片模块后的卡片)的UI显示。
请参见图12a，以将第一卡片嵌入到第一设备的第一应用中并实现第一卡片的显示为例。图12a为本申请一实施例示意的一种场景软件架构示意图。如图12a所示，第一设备中的第一卡片服务模块可以包括：第一应用进程、第一卡片服务应用进程以及资源包集合。其中，第一卡片服务模块位于图2a中的应用程序层。
需要说明的是，进程(Process)是操作***进行资源分配和调度的基本单位，是操作***结构的基础。即，操作***在运行任意一个应用程序时，就会创建一个进程，分配一个空间。对应的，第一应用进程对应于第一设备中的第一应用，第一卡片服务应用进程对应于第一设备中的第一卡片服务应用。且本申请对第一设备中的应用的具体实现类型不做限定。另外，本申请提及的应用程序又可称为应用。
第一应用进程，用于提供卡片。
第一应用进程包括：资源包1、卡片标签1和卡片容器1。其中：
资源包1，用于提供第一应用的应用页面的UI显示和逻辑执行的代码，即界面资源。资源包1中包括与第一应用的应用页面对应的JS Bundle和Resource，JS Bundle用于实现第一应用的应用页面1的逻辑执行和UI显示，Resource用于向JS Bundle提供第一应用的应用页面1的UI显示中的视频、图片等数据来源。此处的第一应用的应用页面1指的是除了卡片显示的UI之外的其他UI，即通过资源包1中的JS Bundle所显示的UI。
卡片标签1，用于嵌入不同的卡片或者卡片模块。卡片标签1中携带有卡片的卡片名称，以便第一应用进程基于卡片标签1解析加载与卡片名称对应的卡片，且该卡片包括至少一个卡片模块。例如，第一应用进程中的代码有：<card src＝＂src_to_card＂></card>，card表示卡片标签1，src表示卡片名称，则第一应用进程可以加载并显示包括全部卡片模块的卡片。
基于前述描述，第一应用可以同时实现应用页面1和至少一个卡片的显示UI。如果第一应用可实现第一卡片的显示UI和第二卡片的显示UI，则如图11所示，在第一应用的应用页面1的UI显示和逻辑执行的代码中会嵌入第一卡片的卡片标签1和第二卡片的卡片标签1，其中，第一卡片的卡片标签1中携带有第一卡片的卡片名称“fa.soundx.soundXcard”，第二卡片的卡片标签1中携带有第二卡片的卡片名称“fa.aircondition.airconditioncard”。
另外，第一应用进程还可以包括未携带有卡片名称的卡片标签2，以便第一应用进程将卡片标签2作为占位符，用于加载显示重新组合卡片模块后的卡片。本文提及的重新组合卡片模块后的卡片可以理解为包括部分卡片模块的卡片，或者通过将重新组合后包括全部卡片模块的卡片。例如，第一应用进程中的代码有：<card＂></card>，card表示卡片标签2，且无卡片名称src，则第一应用进程可以加载并显示者重新组合卡片模块后的卡片。
卡片容器1，用于存放绘制结果(图12a中以一个卡片进行示意)，绘制结果可以理解为一帧一帧的图像，用来形成卡片的显示UI。一般情况下，每张卡片的界面资源存储在卡片容器1中的不同存储空间。在一些实施例中，每张卡片对应一个地址1，以便第一卡片 服务应用进程按照地址1，将绘制结果传输给卡片容器1中对应的存储空间，使得第一应用能够实现卡片的UI显示，不仅可以实现静态图片形式的卡片的显示，还可以实现较为复杂的动态形式的卡片的显示。其中，本申请对地址1的具体实现形式不做限定。例如，地址1可以为用于卡片的存储空间的起始地址。
基于前述描述，第一应用除了实现应用页面1和至少一个卡片的显示UI之外，还可以同时为重新组合卡片模块后的卡片预留至少一个卡槽，以便实现重新组合卡片模块后的卡片的显示UI。如果第一应用除了实现第一卡片的显示UI和第二卡片的显示UI之外还可显示重新组合卡片模块后的卡片，则如图11所示，在第一应用的应用页面1的UI显示和逻辑执行的代码中会嵌入卡片标签2、第一卡片的卡片标签1和第二卡片的卡片标签1，其中，卡片标签2用于预留卡槽来显示重新组合卡片模块后的卡片，第一卡片的卡片标签1中携带有第一卡片的卡片名称“fa.soundx.soundXcard”，第二卡片的卡片标签1中携带有第二卡片的卡片名称“fa.aircondition.airconditioncard”。
卡片应用进程，即从资源包集合中加载资源时对应的进程称之为卡片应用进程。资源包集合，用于预先存储各张卡片的UI显示和逻辑执行的代码，通常基于每张卡片的卡片名称来存储该卡片的全部卡片模块的UI显示和逻辑执行的代码。
从而，第一卡片服务应用进程可从卡片应用进程中加载卡片的UI显示和逻辑执行的代码，以实现第一应用进程和第二应用进程的卡片UI显示，还使得卡片应用可从卡片应用进程中加载卡片的UI显示和逻辑执行的代码，以便卡片应用实现卡片的UI显示。其中，本文提及的卡片应用为关于卡片的应用程序。以卡片对应于智能家居应用推送的播放音乐服务为例，则卡片应用可以为智能家居应用或者智能音箱应用。
对应的，资源包集合中包括：至少一个资源包2(图12a中以第一卡片的资源包2和第二卡片的资源包2进行示意)，每个资源包2对应一张卡片的UI显示和逻辑执行的代码。例如，第一卡片的资源包2可以实现第一卡片中的6个卡片模块的UI显示。针对任意一张卡片，资源包2中包括与该卡片中各个卡片模块对应的JS Bundle和Resource，JS Bundle用于实现卡片中各个卡片模块的UI显示和逻辑执行，Resource用于向JS Bundle提供卡片UI显示的视频、图片等数据来源。
另外，资源包集合还用于存储卡片应用的应用页面的UI显示和逻辑执行的代码，使得卡片应用可从卡片应用进程中加载应用页面的UI显示和逻辑执行的代码，以实现卡片应用中除了卡片UI显示之外的其他UI。此处的卡片应用的应用页面指的是除了卡片显示的UI之外的其他UI，即通过资源包3中的JS Bundle所显示的UI。
对应的，资源包集合中还可以包括：至少一个资源包3(图12a中以一个资源包3进行示意)，每个资源包3对应一张卡片对应的卡片应用的应用页面的UI显示和逻辑执行的代码。针对任意一张卡片，资源包3中包括与该卡片对应的卡片应用的应用页面对应的JS Bundle和Resource，JS Bundle用于实现与该卡片对应的卡片应用的应用页面的UI显示和逻辑执行，Resource用于向JS Bundle提供与该卡片对应的卡片应用的应用页面UI显示的视频、图片等数据源。
第一卡片服务应用进程，用于提供驱动卡片的UI显示和逻辑执行的服务，即第一卡片服务应用进程从卡片应用进程中加载JS Bundle，并基于JS Bundle绘制渲染得到绘制结果1。从而，第一卡片服务应用进程将绘制结果1传输给第一应用进程或者第二应用进程， 以实现卡片的UI显示，即第一卡片服务应用进程与第一应用进程或者第一卡片服务应用进程与第二应用进程，通过共享地址来实现卡片的UI显示。其中，第一卡片服务应用进程对应于第一设备中卡片服务应用。
本申请中，在第一应用进程与第一卡片服务应用进程之间可以建立进程间通信(inter-process communication，IPC)连接，以便实现第一卡片服务应用进程与第一应用进程之间的相互通信。
下面，基于图12a实施例的描述，以图12a中的第一应用进程、卡片应用进程和第一卡片服务应用进程为执行主体，对本申请的第一卡片显示的实现过程进行详细说明。
图12b为本申请一实施例提供的一种卡片分享方法的信令交互图。如图12b所示，本申请的卡片分享方法可以包括：步骤S101-S117。
如果用户想要启动第一应用中的第一卡片，用户可以在第一应用的页面上执行如点击、长按、滑动等第一操作。其中，第一卡片为第一应用中的任意一个卡片。本文提及的长按操作可以理解为用户执行操作的时长满足预设时长所对应的操作。
S101、第一应用进程响应于用户的第一操作，根据第一卡片的卡片标签1中的卡片名称查询第一设备的卡片服务模块中是否有资源包集合。其中，该资源包集合中存储有与卡片名称对应的第一卡片。
本领域技术人员可以理解，在电子设备中的任意一个进程安装后，该进程会在电子设备的操作***中存储广播信息，该广播信息用于表示该进程已安装。因此，第一应用进程可以通过确定是否能够查找到该广播信息，来判断卡片应用进程是否安装。若未查找到该广播信息，则第一应用进程确定第一设备没有卡片应用进程对应的资源包集合，并执行步骤S102。若查找到该广播信息，则第一应用进程确定第一设备有卡片应用进程对应的资源包集合，并执行步骤S103-S108。
S102、第一应用进程不作处理，且无法显示第一卡片。可以理解为，第一应用无法嵌入第一卡片。
S103、第一应用进程解析第一卡片的卡片标签1得到第一卡片的卡片名称，并在第一应用进程与第一卡片服务应用进程之间建立IPC连接。
在一些实施例中，第一卡片服务应用进程在无卡片显示时默认处于不启动状态，则S103中第一应用程序可以启动第一卡片服务应用进程，从而可以降低资源开销。其中，第一应用程序与第一卡片服务应用进程之间可以预先建立绑定关系，以便第一应用进程基于该绑定关系，启动第一卡片服务应用进程，即第一应用进程可以拉起第一卡片服务应用进程。
在另一些实施例中，第一卡片服务应用进程在无卡片显示时默认处于启动状态，则S103中第一应用进程无需启动第一卡片服务应用进程。
需要说明的是，在第一应用进程与第一卡片服务应用进程之间的IPC连接也可以由第一设备的操作***建立，本申请对此不做限定。步骤103为可选地，即在第一应用进程与第一卡片服务应用进程之间的IPC连接可以预先建立好的。
S104、第一应用进程通过第一应用进程与第一卡片服务应用进程之间的IPC连接，向第一卡片服务应用进程发送第一卡片的卡片名称和地址1。
S105、第一卡片服务应用进程确定出与第一卡片的卡片名称相关联的至少一个卡片模 块，并通过卡片应用进程从资源包集合中加载与至少一个卡片模块对应的JS Bundle。其中，本文涉及的JS Bundle可以为一个JS Bundle，也可以为多个JS Bundle，本申请对此不做限定。
S106、第一卡片服务应用进程基于与至少一个卡片模块对应的JS Bundle，绘制渲染得到第一绘制结果。其中，第一绘制结果可以理解为一帧一帧的图像，用来形成第一卡片的UI。
S107、第一卡片服务应用进程通过第一卡片服务应用进程与第一应用进程之间的IPC连接，按照地址1，向第一应用进程的卡片容器1中发送第一绘制结果。
S108、第一应用进程基于卡片容器1的地址1中的第一绘制结果显示出第一卡片。从而，使得第一设备以卡片的形式将应用服务提供商推送的服务内容呈现给用户，以便根据不同服务场景向用户推送不同的卡片。另外，卡片在每个应用程序中的显示UI可以相同，也可以不同，本申请对此不做限定。
由此，场景一中的步骤11和场景二中的步骤21均可采用上述描述内容，实现第一卡片的UI显示。
本申请中，用户可以将第一卡片中的卡片模块分享到第一设备中的第二应用中。下面，对本申请的在同设备的不同应用之间的卡片分享方法的具体实现方式进行描述。
请参见图13a-图13c，以卡片从第一设备的第一应用分享到第一设备的第二应用为例。图13a和图13b为本申请一实施例提供的一种场景软件架构示意图。如图13a和图13b所示，第一设备中的第一卡片服务模块可以包括：第一应用进程、第一卡片服务应用进程、第二应用进程以及资源包集合。其中，第一应用进程、第一卡片服务应用进程以及资源包集合可参见图12a中的描述，此处不做赘述。
第二应用进程，用于接收并显示分享的卡片。
第二应用进程包括：资源包4、卡片标签2和卡片容器2。其中：
资源包4，用于提供第二应用的应用页面2的UI显示和逻辑执行的代码。资源包4中包括与第二应用的应用页面2对应的JS Bundle和Resource，JS Bundle用于实现第二应用的应用页面2的逻辑执行和UI显示，Resource用于向JS Bundle提供第二应用的应用页面2的UI显示中的视频、图片等数据来源。此处的第二应用的应用页面2指的是除了卡片显示的UI之外的其他UI，即通过资源包4中的JS Bundle所显示的UI。
卡片标签2，用于嵌入不同的卡片或者卡片模块。卡片标签2中未携带有卡片名称，以便第二应用进程将卡片标签2作为占位符，用于加载显示重新组合卡片模块后的卡片。例如，第二应用进程中的代码有：<card＂></card>，card表示卡片标签2，则第二应用进程可以加载并显示重新组合卡片模块后的卡片。
基于前述描述，第二应用在实现应用页面2的UI显示的同时，可以为重新组合卡片模块后的卡片预留至少一个卡槽，以便实现重新组合卡片模块后的卡片的显示UI，具体实现过程可参见图12a实施例中应用页面1的显示UI和卡片标签2的描述，此处不做赘述。
另外，第二应用进程还可以包括携带有卡片名称的卡片标签1，以便第二应用进程基于卡片标签1解析加载与卡片名称对应的卡片，且该卡片包括至少一个卡片模块。例如，第二应用进程中的代码有：<card src＝＂src_to_card＂></card>，card表示卡片标签1，src 表示卡片名称，则第二应用进程可以加载并显示包括全部卡片模块的卡片。
卡片容器2，用于存放绘制结果(图13b中以一个卡片进行示意)，绘制结果可以理解为一帧一帧的图像，用来形成卡片的显示UI。一般情况下，每张卡片的界面资源存储在卡片容器2中的不同存储空间。在一些实施例中，每张卡片对应一个地址2，以便第一卡片服务应用进程按照地址2，将绘制结果传输给卡片容器2中对应的存储空间，使得第二应用能够实现卡片的UI显示，不仅可以实现静态图片形式的卡片的显示，还可以实现较为复杂的动态形式的卡片的显示。其中，本申请对地址2的具体实现形式不做限定。例如，地址2可以为卡片的存储空间的起始地址。
基于前述描述，第二应用除了可以同时实现应用页面2的显示UI以及为重新组合卡片模块后的卡片预留至少一个卡槽之外，还可以实现至少一个卡片的显示UI，具体实现过程可参见图12a实施例中的描述，此处不做赘述。
本申请中，在第一应用进程与第二应用进程之间可以建立IPC连接，以便实现第一应用进程与第二应用进程之间的相互通信。在第一卡片服务应用进程与第二应用进程之间可以建立IPC连接，以便实现第一卡片服务应用进程与第二应用进程之间的相互通信。
下面，基于图13a和图13b实施例的描述，以图13a和图13b中的第一应用进程、第二应用进程、卡片应用进程和第一卡片服务应用进程为执行主体，对本申请的卡片分享方法的具体实现过程进行详细说明。
图13c为本申请一实施例提供的一种卡片分享方法的信令交互图。如图13c所示，本申请的卡片分享方法可以包括：步骤S201-S209。
如果用户想要将嵌入到第一应用中的第一卡片或者第一卡片中的卡片模块分享到第一设备中的第二应用，则用户可以在第一卡片的UI上执行第二操作，该第二操作用于确定用户从第一卡片中选择分享的卡片模块以及用户所选择的第二应用，并通过步骤S201-S217将用户从第一卡片中选择分享的卡片模块从第一应用分享到第二应用。需要说明的是，用户可以从第一卡片中选择部分卡片模块进行分享，也可以从第一卡片中选择全部卡片模块进行分享，本申请对不做限定。
S201、第一应用进程响应于用户的第二操作，确定出用户从第一卡片中选择分享的第一卡片模块和用户所选择的第二应用进程。其中，第一卡片模块可以为第一卡片中的至少一个卡片模块。该第二操作可以与第一卡片中的第一卡片模块关联，也可以与第一卡片中的第一卡片模块以及第一卡片中的第三卡片模块关联，第三卡片模块为不可重新组合的至少一个卡片模块，本申请对此不做限定。并且，第二操作还可以用于指示第一设备将第一卡片中的第一卡片模块分享到第二应用，或者，第二操作还可以用于指示第一设备将第一卡片中的第一卡片模块和第三卡片模块分享到第二应用。
S202、第一应用进程在第一应用进程与第二应用进程之间建立IPC连接，并通过第二应用进程与第二应用进程之间的IPC连接，向第二应用进程发送第一卡片的卡片名称和第一卡片模块的卡片模块编号。
S203、第二应用进程判断与第一卡片的卡片名称相关联的第一卡片的卡片标签2是否存在，以确定第二应用进程是否能够加载并显示卡片。若第一卡片的卡片标签2存在，则第二应用进程确定第二应用进程能够加载并显示卡片；若第一卡片的卡片标签2不存在，则第二应用进程确定第二应用进程无法加载显示卡片。
S204、第二应用进程在确定第二应用进程能够加载显示卡片时，在第二应用进程与第一卡片服务应用进程之间建立IPC连接。
S205、第二应用进程通过第二应用进程与第一卡片服务应用进程之间的IPC连接，向第一卡片服务应用进程发送第一卡片的卡片名称、第一卡片模块的卡片模块编号和地址2。
S206、第一卡片服务应用进程确定出与第一卡片的卡片名称和第一卡片模块的卡片模块编号相关联的第一卡片模块，并通过卡片应用进程从资源包集合中加载与第一卡片模块对应的JS Bundle。
S207、第一卡片服务应用进程基于与第一卡片模块对应的JS Bundle，绘制渲染得到绘制结果2。其中，绘制结果2可以理解为一帧一帧的图像，用来形成第一卡片模块的显示UI。
其中，基于第二应用的页面尺寸和第一设备的显示屏的尺寸，第一卡片服务应用进程可以对绘制结果2中的每个卡片模块的形状大小、位置布局和表示内容等参数进行适应性设置，使得第一卡片模块能够在第二应用中实现美观且清晰的UI显示。另外，卡片模块在每个应用程序中的显示UI可以相同，也可以不同，本申请对此不做限定。
需要说明的是，绘制结果2也可以用来形成第一卡片模块和第三卡片模块的显示UI。
S208、第一卡片服务应用进程通过第一卡片服务应用进程与第二应用进程之间的IPC连接，按照地址2，向第二应用进程的卡片容器2发送绘制结果2。
S209、第二应用进程基于卡片容器2中的绘制结果2显示出第一卡片模块。从而，使得第一设备以卡片的形式，基于用户意愿将应用服务提供商推送的服务内容，尤其服务内容中用户频繁使用或者操作繁琐等关键信息，通过UI显示呈现给用户，以便根据不同服务场景向用户推送不同的卡片。
综上，基于卡片的可拆分以及卡片模块的可重新组合，使得重新组合卡片模块后的卡片可以在同一设备的不同应用程序之间进行分享，且基于用户意愿，可通过卡片的显示UI向用户提供用户想要得到的服务内容，尤其是服务内容中频繁使用或者操作繁琐等关键信息，有利于提升用户体验感。
另外，由于第一卡片中的全部卡片模块可以基于第一卡片的卡片名称进行确定，因此，在步骤S202中，第一应用进程通过第一应用进程与第二应用进程之间的IPC连接，向第二应用进程发送第一卡片的卡片名称，而无需将第一卡片的全部卡片模块各自对应的卡片模块编号发送给第二应用进程，降低了数据传输量。在步骤S205中，第二应用进程通过第二应用进程与第一卡片服务应用进程之间的IPC连接，向第一卡片服务应用进程发送第一卡片的卡片名称和地址2，无需将第一卡片的全部卡片模块各自对应的卡片模块编号发送给第一卡片服务应用进程，降低了数据传输量。
从而，使得用户的电子设备以卡片的形式，基于用户意愿将应用服务提供商推送全部的服务内容，通过UI显示呈现给用户，以便根据不同服务场景向用户推送不同的卡片。
需要说明的是，第一卡片除了分享到负一屏之外，还可以分享到第一设备的其他进程中。
在另一些实施例中，用户可以将第一设备中的第一应用嵌入的第一卡片拖拽到第一设备中的第二应用中。其中，第一应用和第二应用所显示的卡片的显示UI可以相同，也可以不同，本申请对此不做限定。例如，用户将显示在手机的智能家居应用中的第一卡片拖 拽到手机的负一屏中，使得负一屏能够显示第一卡片的UI。从而，使得卡片具备丰富的显示渠道。
在另一些实施例中，用户可以将第一设备中的第二应用中重新组合卡片模块后的卡片拖拽到第一设备中的第三应用中，其具体实现过程可参见前述内容。其中，第二应用和第三应用所显示的卡片的显示UI可以相同，也可以不同，本申请对此不做限定。例如，用户将显示在分享到手机的负一屏中的卡片拖拽到手机的主屏幕中，使得主屏幕能够显示卡片的UI。
在一些实施例中，用户可通过结束第二应用，停止卡片的分享。第一应用进程也可以在向第二应用分享卡片的同时，向第一卡片服务应用进程发送卡片的分享时长，使得第一卡片服务应用进程在卡片的分享时长之内，通过地址分享的方式，支持第二应用显示该卡片，也使得第一卡片服务应用进程在卡片的分享时长之外，通过停止地址分享的方式，不再支持第二应用显示该卡片。本申请不限于前述两种实现方式停止卡片的分享。从而，第一应用可通过停止卡片的分享实现服务的回收。另外，第一卡片服务应用进程还可以通过地址分享的方式，实现绘制结果2的更新。
本申请中，第一设备可以采用多种实现方式，向第二设备分享卡片。下面，结合两者可行的实现方式，对本申请的在跨设备之间的卡片分享方法的具体实现方式进行描述。
一种可行的实现方式中，请参见图14a-图14c，以卡片从第一设备的第一应用分享到第二设备的第三应用为例。图14a和图14b为本申请一实施例提供的一种场景软件架构示意图。如图14a和图14b所示，第一设备中的第一卡片服务模块可以包括：第一应用进程和第一卡片服务应用进程。其中，第一卡片服务模块位于图2a中的应用程序层。第二设备中的第二卡片服务模块可以包括：第三应用进程和第二卡片服务应用进程。其中，第二卡片服务模块位于图2a中的应用程序层。
其中，第一应用进程和第一卡片服务应用进程的具体实现内容可参见图12a实施例中的描述，此处不做赘述。
第三应用进程，用于接收并显示分享的卡片。
第三应用进程包括：资源包5、卡片标签2和卡片容器3。其中：
资源包5，用于提供第三应用的应用页面3的UI显示和逻辑执行的代码，即界面资源。资源包5中包括与第三应用的应用页面3对应的JS Bundle和Resource，JS Bundle用于实现第三应用的应用页面3的逻辑执行和UI显示，Resource用于向JS Bundle提供第三应用的应用页面3的UI显示中的视频、图片等数据来源。此处的第三应用的应用页面3指的是除了卡片显示的UI之外的其他UI，即通过资源包5中的JS Bundle所显示的UI。
卡片标签2，用于嵌入不同的卡片或者卡片模块。卡片标签2中未携带有卡片名称，以便第三应用进程将卡片标签2作为占位符，用于加载显示重新组合卡片模块后的卡片。例如，第三应用进程中的代码有：<card＂></card>，card表示卡片标签2，则第三应用进程可以加载并显示重新组合卡片模块后的卡片。
基于前述描述，第三应用在实现应用页面3的UI显示的同时，可以为重新组合卡片模块后的卡片预留至少一个卡槽，以便实现重新组合卡片模块后的卡片的显示UI，具体实现过程可参见图12a实施例中应用页面1的显示UI和卡片标签2的描述，此处不做赘述。
另外，第三应用进程还可以包括携带有卡片名称的卡片标签1，以便第三应用进程基于卡片标签1解析加载与卡片名称对应的卡片，且该卡片包括至少一个卡片模块。例如，第三应用进程中的代码有：<card src＝＂src_to_card＂></card>，card表示卡片标签1，src表示卡片名称，则第三应用进程可以加载并显示包括全部卡片模块的卡片。
卡片容器3，用于存放绘制结果(图14b中以一个卡片进行示意)，绘制结果可以理解为一帧一帧的图像，用来形成卡片的显示UI。一般情况下，每张卡片的界面资源存储在卡片容器3中的不同存储空间。在一些实施例中，每张卡片对应一个地址3，以便第一卡片服务应用进程按照地址3，将绘制结果传输给卡片容器3中对应的存储空间，使得第三应用能够实现卡片的UI显示，不仅可以实现静态图片形式的卡片的显示，还可以实现较为复杂的动态形式的卡片的显示。其中，本申请对地址3的具体实现形式不做限定。例如，地址3可以为卡片的存储空间的起始地址。
基于前述描述，第三应用除了实现应用页面3的显示UI以及为重新组合卡片模块后的卡片预留至少一个卡槽之外，还可以同时实现至少一个卡片的显示UI，具体实现过程可参见图12a实施例中的描述，此处不做赘述。
第二卡片服务应用进程，用于提供驱动卡片的UI显示和逻辑执行的服务，即第二卡片服务应用进程从卡片应用进程中加载JS Bundle，并基于JS Bundle绘制渲染得到绘制结果2。从而，第二卡片服务应用进程将绘制结果2传输给第三应用进程，以实现卡片的UI显示，即第二卡片服务应用进程与第一应用进程或者第二卡片服务应用进程与第二应用进程，通过共享地址来实现卡片的UI显示。其中，第二卡片服务应用进程对应于第二设备中第二卡片服务应用。
本申请中，在第一应用进程与第三应用进程之间可以建立远程过程调用(remote procedure call，RPC)连接，以便实现第一应用进程与第三应用进程之间的相互通信。在第一卡片服务应用进程与第一应用进程之间可以建立IPC连接，以便实现第一卡片服务应用进程与第一应用进程之间的相互通信。在第二卡片服务应用进程与第三应用进程之间可以建立IPC连接，以便实现第二卡片服务应用进程与第三应用进程之间的相互通信。
另外，第一设备和第二设备均可从如云端应用服务器中安装卡片应用进程对应的资源包集合。其中，卡片应用进程和资源包集合的具体实现内容可参见图12a实施例中的描述，此处不做赘述。需要说明的是，第一设备和第二设备中的资源包集合可以相同，也可以不同，本申请对此不做限定。为了便于说明，图14a和图14b中以第一设备和第二设备中的资源包集合相同为例进行示意。
下面，基于图14a和图14b实施例的描述，以图14a和图14b中的第一应用进程、第一卡片服务应用进程、第三应用进程、第二卡片服务应用进程和卡片应用进程为执行主体，对本申请的卡片分享方法的具体实现过程进行详细说明。
图14c为本申请一实施例提供的一种卡片分享方法的信令交互图。如图14c所示，本申请的卡片分享方法可以包括：步骤S301-S310。
如果用户想要将嵌入到第一应用中的第一卡片或者第一卡片中的卡片模块分享到第二设备中的第三应用，则用户可以在第一卡片的显示UI上执行第二操作，该第二操作用于确定用户从第一卡片中选择分享的卡片模块以及用户所选择的第二设备和第三应用进程，并通过步骤S301-S310将用户从卡片中选择分享的卡片模块从第一应用进程分享到第 二设备中的第三应用进程。需要说明的是，用户可以从第一卡片中选择部分卡片模块进行分享，也可以从卡第一片中选择全部卡片模块进行分享，本申请对不做限定。
S301、第一应用进程响应于用户的第二操作，确定出用户从第一卡片中选择分享的第一卡片模块和用户所选择的第二设备(如确定出第二设备的设备编号等唯一标识)和第三应用进程(如确定出第三应用进程的名称、编号等唯一的标识)。其中，第一卡片模块可以为第一卡片中的至少一个卡片模块。该第二操作可以与第一卡片中的第一卡片模块关联，也可以与第一卡片中的第一卡片模块以及第一卡片中的第三卡片模块关联，第三卡片模块为不可重新组合的至少一个卡片模块，本申请对此不做限定。并且，第二操作还可以用于指示第一设备将第一卡片中的第一卡片模块分享到第二设备中的第三应用，或者，第二操作还可以用于指示第一设备将第一卡片中的第一卡片模块和第三卡片模块分享到第二设备中的第三应用。
S302、第一应用进程在第一应用进程与第三应用进程之间建立RPC连接，并通过第一应用进程与第三应用进程之间的RPC连接，向第三应用进程发送第一卡片的卡片名称和第一卡片模块的卡片模块编号。
S303、第三应用进程根据第一卡片的卡片名称查询第二设备的卡片服务模块中是否有资源包集合。其中，该资源包集合中存储有与卡片名称对应的第一卡片。
若没有资源包集合，则执行步骤S304。若有卡片应用进程，则执行步骤S305-S310。
其中，步骤S303与图12b实施例中的S101的实现方式类似，本申请对此不做限定。
S304、第三应用进程不作处理，且无法显示该卡片。
S305、第三应用进程在第三应用进程与第二卡片服务应用进程之间建立IPC连接。
在一些实施例中，第二卡片服务应用进程在无卡片显示时默认处于不启动状态，则S305中第三应用可以启动第二卡片服务应用进程，从而可以降低资源开销。
在另一些实施例中，第二卡片服务应用进程在无卡片显示时默认处于启动状态，则S305中第三应用进程无需启动第二卡片服务应用进程。
S306、第三应用进程通过第三应用进程与第二卡片服务应用进程之间的IPC连接，向第二卡片服务应用进程发送第一卡片的卡片名称、第一卡片模块的卡片模块编号和地址3。
S307、第二卡片服务应用进程确定出与第一卡片的卡片名称关联和第一卡片模块的卡片模块编号相关联的第一卡片模块，并从卡片应用进程中加载与第一卡片模块对应的JS Bundle。
S308、第二卡片服务应用进程基于与第一卡片模块对应的JS Bundle，绘制渲染得到绘制结果2。其中，绘制结果2可以理解为一帧一帧的图像，用来形成第一卡片模块的显示UI。
S309、第二卡片服务应用进程通过第二卡片服务应用进程与第三应用进程之间的IPC连接，按照地址3，向第三应用进程的卡片容器3发送绘制结果2。
S310、第三应用进程基于卡片容器3中的绘制结果2显示出第一卡片模块。从而，使得第二设备以卡片的形式，基于用户意愿将应用服务提供商推送的服务内容，尤其服务内容中用户频繁使用或者操作繁琐等关键信息，通过UI显示呈现给用户，使得卡片能够快速从第一设备分享到第二设备，以便根据不同服务场景向不同的用户推送卡片。
综上，基于卡片的可拆分以及卡片模块的可重新组合，使得重新组合卡片模块后的卡 片可以在不同设备之间实现分享，且基于用户意愿能够将用户想要分享的服务内容以卡片的形式快速分享给其他用户，使得其他用户也具备对设备的控制诉求，如家庭成员均具备设备的控制权限或者客人对家里的设备具备临时控制诉求等，有利于提升用户体验感。
另外，由于第一卡片中的全部卡片模块可以基于该卡片的卡片名称进行确定，因此，在步骤S302中，第一应用进程通过第一应用进程与第三应用进程之间的RPC连接，向第三应用进程发送第一卡片的卡片名称，而无需将第一卡片的全部卡片模块各自对应的卡片模块编号发送给第二应用进程，降低了数据传输量。在步骤S306中，第三应用进程通过第三应用进程与第二卡片服务应用进程之间的IPC连接，向第二卡片服务应用进程发送第一卡片的卡片名称和地址3，无需将第一卡片的全部卡片模块各自对应的卡片模块编号发送给第二卡片服务应用进程，降低了数据传输量。
从而，使得用户的电子设备以卡片的形式，基于用户意愿将应用服务提供商推送全部的服务内容，通过UI显示呈现给用户，以便根据不同服务场景向用户推送不同的卡片。
需要说明的是，卡片除了分享到车载设备之外，还可以分享到其他设备中，具体可参考前述内容，此处不做赘述。且第二设备还可以将卡片分享到其他设备中，其具体实现过程可参考前述内容。另外，用户可以将第二设备中的重新组合卡片模块后的卡片拖拽到第二设备中的其他应用或者其他设备中，其具体实现过程可参见前述内容。
在一些实施例中，用户可通过结束第三应用，停止卡片的分享。第一应用进程也可以在向第三应用分享卡片的同时，向第三应用进程发送卡片的分享时长，使得第二卡片服务应用进程在卡片的分享时长之内，通过地址分享的方式，支持第三应用显示该卡片，也使得第二卡片服务应用进程在卡片的分享时长之外，通过停止地址分享的方式，不再支持第三应用显示该卡片。本申请不限于前述两种实现方式停止卡片的分享。从而，第一应用可通过停止卡片的分享实现服务的回收。另外，第二卡片服务应用进程还可以通过地址分享的方式，实现绘制结果2的更新。
另一种可行的实现方式中，请参见图15a-图15c，以卡片从第一设备的第一应用分享到第二设备的第三应用为例。图15a和图15b为本申请一实施例提供的一种场景软件架构示意图。如图15a和图15b所示，第一设备中的第一卡片服务模块可以包括：第一应用进程、卡片应用进程以及第一卡片服务应用进程。其中，第一卡片服务模块位于图2a中的应用程序层。第二设备中的第二卡片服务模块可以包括：第三应用进程。其中，第二卡片服务模块位于图2a中的应用程序层。
其中，第一应用进程、卡片应用进程以及第一卡片服务应用进程的具体实现方式可参见图12a实施例中的描述，此处不做赘述。第三应用进程的具体实现方式可参见图14a和图14b实施例中的描述，此处不做赘述。
本申请中，在第一应用进程与第三应用进程之间可以建立RPC连接，以便实现第一应用进程与第三应用进程之间的相互通信。在第一卡片服务应用进程与第一应用进程之间可以建立IPC连接，以便实现卡片服务应用进程与第一应用进程之间的相互通信。在第一卡片服务应用进程与第三应用进程之间可以建立RPC连接，以便实现第一卡片服务应用进程与第三应用进程之间的相互通信。
下面，基于图15a和图15b实施例中的描述，以图15a和图15b中的第一应用进程、 第三应用进程、卡片应用进程和第一卡片服务应用进程为执行主体，对本申请的卡片分享方法的具体实现过程进行详细说明。
图15c为本申请一实施例提供的一种卡片分享方法的信令交互图。如图15c所示，本申请的卡片分享方法可以包括：步骤S401-S409。
如果用户想要将嵌入到第一应用中的第一卡片或者第一卡片中的卡片模块分享到第二设备中的第三应用，则用户可以在第一卡片的显示UI上执行第二操作，该第二操作用于确定用户从第一卡片中选择分享的卡片模块以及用户所选择的第二设备和第三应用进程，并通过步骤S401-S409将用户从第一卡片中选择分享的卡片模块从第一应用进程分享到第二设备中的第三应用进程。需要说明的是，用户可以从第一卡片中选择部分卡片模块进行分享，也可以从第一卡片中选择全部卡片模块进行分享，本申请对不做限定。
S401、第一应用进程响应于用户的第二操作，确定出用户从第一卡片中选择分享的第一卡片模块和用户所选择的第二设备和第三应用进程。其中，第一卡片模块可以为第一卡片中的至少一个卡片模块。该第二操作可以与第一卡片中的第一卡片模块关联，也可以与第一卡片中的第一卡片模块以及第一卡片中的第三卡片模块关联，第三卡片模块为不可重新组合的至少一个卡片模块，本申请对此不做限定。并且，第二操作还可以用于指示第一设备将第一卡片中的第一卡片模块分享到第二设备中的第三应用，或者，第二操作还可以用于指示第一设备将第一卡片中的第一卡片模块和第三卡片模块分享到第二设备中的第三应用。
S402、第一应用进程在第一应用进程与第三应用进程之间建立RPC连接，并通过第一应用进程与第三应用进程之间的RPC连接，向第三应用进程发送第一卡片的卡片名称和第一卡片模块的卡片模块编号。
S403、第三应用进程判断与第一卡片的卡片名称相关联的第一卡片的卡片标签2是否存在，以确定第三应用进程是否能够加载显示卡片。若第一卡片的卡片标签2存在，则第三应用进程确定第三应用进程能够加载显示卡片；若第一卡片的卡片标签2不存在，则第三应用进程确定第三应用进程无法加载显示卡片。
S404、第三应用进程在确定第三应用进程能够加载显示卡片时，在第三应用进程与第一卡片服务应用进程之间建立RPC连接。
S405、第三应用进程通过第三应用进程与第一卡片服务应用进程之间的RPC连接，向第一卡片服务应用进程发送第一卡片的卡片名称、第一卡片模块的卡片模块编号和地址3。
S406、第一卡片服务应用进程确定出与第一卡片的卡片名称和第一卡片模块的卡片模块编号相关联的卡片模块，并从卡片应用进程中调用与第一卡片模块对应的JS Bundle。
S407、第一卡片服务应用进程基于与第一卡片模块对应的JS Bundle，绘制渲染得到绘制结果2。
S408、第一卡片服务应用进程通过第一卡片服务应用进程与第三应用进程之间的RPC连接，按照地址3，向第三应用进程的卡片容器3中发送绘制结果2。
S409、第三应用进程基于卡片容器3中的绘制结果2显示出第一卡片模块。从而，使得第二设备以卡片的形式，基于用户意愿将应用服务提供商推送的服务内容，尤其服务内容中用户频繁使用或者操作繁琐等关键信息，通过UI显示呈现给用户，使得卡片能够快速从第一设备分享到第二设备，以便根据不同服务场景向不同的用户推送卡片。
综上，基于卡片的可拆分以及卡片模块的可重新组合，使得重新组合卡片模块后的卡片可以在不同设备之间实现分享，且基于用户意愿能够将用户想要分享的服务内容以卡片的形式快速分享给其他用户，使得其他用户也具备对设备的控制诉求，如家庭成员均具备设备的控制权限或者客人对家里的设备具备临时控制诉求等，有利于提升用户体验感。
另外，由于卡片中的全部卡片模块可以基于该卡片的卡片名称进行确定，因此，在步骤S402中，第一应用进程通过第一应用进程与第三应用进程之间的RPC连接，向第三应用进程发送第一卡片的卡片名称，而无需将第一卡片的全部卡片模块各自对应的卡片模块编号发送给第二应用进程，降低了数据传输量。在步骤S405中，第三应用进程通过第三应用进程与第一卡片服务应用进程之间的RPC连接，向第一卡片服务应用进程发送第一卡片的卡片名称和地址3，无需将第一卡片的全部卡片模块各自对应的卡片模块编号发送给第二卡片服务应用进程，降低了数据传输量。
综上，包括全部卡片模块的卡片可以在不同设备之间进行分享，使得卡片具有丰富的UI显示渠道，以便根据不同服务场景向不同的用户推送卡片。
需要说明的是，卡片除了分享到车载设备之外，还可以分享到其他设备中，具体可参考前述内容，此处不做赘述。且第二设备还可以将卡片分享到其他设备中，其具体实现过程可参考前述内容。
在一些实施例中，用户可通过结束第三应用，停止卡片的分享。第一应用进程也可以在向第三应用分享卡片的同时，向第一卡片服务应用进程发送卡片的分享时长，使得第一卡片服务应用进程在卡片的分享时长之内，通过地址分享的方式，支持第三应用显示该卡片，也使得第一卡片服务应用进程在卡片的分享时长之外，通过停止地址分享的方式，不再支持第三应用显示该卡片。本申请不限于前述两种实现方式停止卡片的分享。从而，第一应用可通过停止卡片的分享实现服务的回收。另外，第一卡片服务应用进程还可以通过地址分享的方式，实现绘制结果2的更新。
基于前述的一些实施例，下面介绍本申请提供的卡片分享方法。
示例性地，本申请提供一种卡片分享方法。
本申请的卡片分享方法可以包括：步骤21-步骤23。
步骤21、响应于用户的第一操作，显示第一应用的界面，第一应用的界面中显示有第一卡片，第一卡片包括第一卡片模块和第二卡片模块，第一卡片的界面资源是由第二应用提供的。
步骤22、响应于用户的第二操作，向第三应用发送第二消息，第二操作与第一卡片模块关联，第二消息包括第一卡片模块的标识。
步骤23、显示第三应用的界面，第三应用的界面中显示有第一卡片模块，第一卡片模块的界面资源是第四应用提供的。
本申请中，步骤21-步骤23可适用于同设备中不同应用程序之间的卡片分享的场景，也可以适用于跨设备之间的卡片分享的场景。
在同设备中不同应用程序之间的卡片分享的场景下，第一应用、第二应用、第三应用为第一设备中的不同的应用程序，第一应用进程对应第一应用，第二应用进程对应第二应用，第三应用进程对应第三应用，第四应用进程对应第四应用，第二应用与第四应用为同 一个应用程序，第二应用进程与第四应用进程为同一个应用程序进程。
步骤21-步骤23的执行主体为第一设备，具体地，步骤21的执行主体为第一应用进程，步骤22的执行主体为第一应用进程，步骤23的执行主体为第三应用进程，具体实现过程可参见图3a-图3l、图12a-图12b以及图13a-图13c中的描述内容，或者说参见第一卡片显示在第一应用中以及场景一中第一卡片从第一应用分享到第二应用的描述内容，此处不做赘述。
其中，第一操作可以包括但不限于用户的点击、长按、滑动等至少一个操作，本申请对第一操作的类型和操作数量等参数不做限定，只需满足第一应用可以响应于用户第一操作实现第一卡片的显示即可。
第一卡片的界面资源可以理解为显示第一卡片模块和第二卡片模块各自的逻辑执行和UI显示所需的如代码、视频、数据等资源，即第一卡片模块和第二卡片模块各自对应的JS Bundle和Resource，具体内容可参见前文描述，此处不做赘述。
第二应用对应于前文实施例中的第一卡片服务应用。
第二操作可以包括但不限于用户的点击、长按、滑动等至少一个操作，本申请对第二操作的类型和操作数量等参数不做限定。且第二操作与第一卡片模块关联，使得第一应用可以响应于用户的第二操作，确定出第一卡片中选择分享的第一卡片模块和分享的对象(即第二应用)。
本申请对第二消息的具体表示方式不做限定。例如，第二消息除了包括第一卡片模块的标识之外，还可以包括第二应用的标识和/或第一卡片的标识等。
第一卡片模块的界面资源可以理解为显示第一卡片模块的逻辑执行和UI显示所需的如代码、视频、数据等资源，即第一卡片模块对应的JS Bundle和Resource，具体内容可参见前文描述，此处不做赘述。
第四应用对应于前文实施例中的第一卡片服务应用。
在跨设备之间的卡片分享的情况下，第一应用和第二应用为第一设备中的不同的应用程序，第三应用和第四应用为第二设备中的不同的应用程序，第一设备与第二设备不同，第一应用进程对应第一应用，第二应用进程对应第二应用，第三应用进程对应第三应用，第四应用进程对应第四应用。
步骤21-步骤23的执行主体为第一设备，具体地，步骤21的执行主体为第一应用进程，步骤22的执行主体为第一应用进程，步骤23的执行主体为第三应用进程，具体实现过程可参见图3a-图3l、图12a-图12b以及图13a-图13c中的描述内容，或者说参见第一卡片显示在第一应用中以及场景二的一种可行的实现方式中的第一卡片从第一应用分享到第二应用的描述内容，此处不做赘述。
其中，第一操作可以包括但不限于用户的点击、长按、滑动等至少一个操作，本申请对第一操作的类型和操作数量等参数不做限定，只需满足第一应用可以响应于用户第一操作实现第一卡片的显示即可。
第一卡片的界面资源可以理解为显示第一卡片模块和第二卡片模块各自的逻辑执行和UI显示所需的如代码、视频、数据等资源，即第一卡片模块和第二卡片模块各自对应的JS Bundle和Resource，具体内容可参见前文描述，此处不做赘述。
第二应用对应于前文实施例中的第一卡片服务应用。
第二操作可以包括但不限于用户的点击、长按、滑动等至少一个操作，本申请对第二操作的类型和操作数量等参数不做限定。且第二操作与第一卡片模块关联，使得第一应用可以响应于用户的第二操作，确定出第一卡片中选择分享的第一卡片模块和分享的对象(即第二应用)。
本申请对第二消息的具体表示方式不做限定。例如，第二消息除了包括第一卡片模块的标识之外，还可以包括第二设备的设备标识、第二应用的标识或者第一卡片的标识等中的至少一个。
第一卡片模块的界面资源可以理解为显示第一卡片模块的逻辑执行和UI显示所需的如代码、视频、数据等资源，即第一卡片模块对应的JS Bundle和Resource，具体内容可参见前文描述，此处不做赘述。
第四应用对应于前文实施例中的第二卡片服务应用。
在跨设备之间的卡片分享的情况下，第一应用和第二应用为第一设备中的不同的应用程序，第三应用为第二设备中的不同的应用程序，第一设备与第二设备不同，第一应用进程对应第一应用，第二应用进程对应第二应用，第三应用进程对应第三应用，第四应用进程对应第四应用，第二应用与第四应用为同一个应用程序，第二应用进程与第四应用进程为同一个应用程序进程。
步骤21-步骤23的执行主体为第一设备，具体地，步骤21的执行主体为第一应用进程，步骤22的执行主体为第一应用进程，步骤23的执行主体为第三应用进程，具体实现过程可参见图3a-图3l、图12a-图12b以及图13a-图13c中的描述内容，或者说参见第一卡片显示在第一应用中以及场景二的一种可行的实现方式中的第一卡片从第一应用分享到第二应用的描述内容，此处不做赘述。
其中，第一操作可以包括但不限于用户的点击、长按、滑动等至少一个操作，本申请对第一操作的类型和操作数量等参数不做限定，只需满足第一应用可以响应于用户第一操作实现第一卡片的显示即可。
第一卡片的界面资源可以理解为显示第一卡片模块和第二卡片模块各自的逻辑执行和UI显示所需的如代码、视频、数据等资源，即第一卡片模块和第二卡片模块各自对应的JS Bundle和Resource，具体内容可参见前文描述，此处不做赘述。
第二应用对应于前文实施例中的第一卡片服务应用。
第二操作可以包括但不限于用户的点击、长按、滑动等至少一个操作，本申请对第二操作的类型和操作数量等参数不做限定。且第二操作与第一卡片模块关联，使得第一应用可以响应于用户的第二操作，确定出第一卡片中选择分享的第一卡片模块和分享的对象(即第二应用)。
本申请对第二消息的具体表示方式不做限定。例如，第二消息除了包括第一卡片模块的标识之外，还可以包括第二设备的设备标识、第二应用的标识或者第一卡片的标识等中的至少一个。
第一卡片模块的界面资源可以理解为显示第一卡片模块的逻辑执行和UI显示所需的如代码、视频、数据等资源，即第一卡片模块对应的JS Bundle和Resource，具体内容可参见前文描述，此处不做赘述。
第四应用对应于前文实施例中的第一卡片服务应用。
在一些实施例中，第一卡片还包括：第三卡片模块，第三应用的界面中还显示有第三卡片模块，第三卡片模块的界面资源是由第四应用提供的。
其中，第一卡片模块和第二卡片模块可以设置为可重新组合的卡片模块，如前文提及的第一卡片中的卡片模块2-卡片模块6。第三卡片模块可以设置为不可重新组合的卡片模块，如前文提及的第一卡片中的卡片模块1。
步骤22中，基于第二操作与第一卡片模块关联，且第三卡片模块和第二卡片模块同属于第一卡片，第三卡片模块为不可重新组合的卡片模块，第一应用可以确定出第二卡片模块和第三卡片模块，使得第一应用可以向第三应用发送第二消息，该第二消息包括第一卡片模块的标识和第三卡片模块的标识。从而，步骤23中，第三应用的界面上显示有第一卡片模块和第三卡片模块。
步骤22中，基于第二操作与第一卡片模块关联，第一应用可以确定出第二卡片模块，使得第一应用可以向第三应用发送第二消息，该第二消息包括第一卡片模块的标识。从而，步骤23中，基于第三卡片模块和第二卡片模块同属于第一卡片，第三卡片模块为不可重新组合的卡片模块，第三应用的界面上显示有第一卡片模块和第三卡片模块。
综上，本申请可将卡片的属性设置为可重新组合，也可将卡片的属性设置为不可重新组合，如用于表明卡片的服务内容或者卡片的关键信息等的卡片模块设置为不可重新组合的卡片模块，从而，第一应用进程响应于用户的第二操作，可以确定出第三应用的界面上需要显示第二卡片模块和第三卡片模块，或者，第三应用基于第二消息中的第一卡片模块的标识，可以确定出第三应用的界面上需要显示第二卡片模块和第三卡片模块，具体实现过程可参见图3a-图3d以及卡片的解释中的描述内容，此处不做赘述。从而，为实现卡片的分享提供给了便利性。
步骤21的一种可行的实现方式中，响应于用户的第一操作，显示第一应用的界面的具体实现过程可以包括：步骤31-步骤33。
步骤31、向第二应用进程发送第一消息。
步骤32、从第二应用进程接收第一绘制结果，第一绘制结果是第二应用进程基于第一卡片的界面资源渲染绘制得到的，第一卡片的界面资源是第二应用进程基于第一消息从资源包集合中调用得到的，资源包集合包括第一卡片中的第一卡片模块、第二卡片模块和第三卡片模块的界面资源以及第二卡片中的第四卡片模块和第五卡片模块的界面资源。
步骤33、基于第一绘制结果在第一应用的界面中显示第一卡片。
本申请中，步骤31-步骤33的执行主体为第一设备，具体地，步骤31-步骤33的执行主体为第一应用进程，具体实现过程可参见图3a-图3d以及图12a-图12b中的步骤S101-S108的描述内容，或者说参见第一卡片显示在第一应用中的描述内容，此处不做赘述。
其中，本申请对第一消息的具体内容不做限定。
在一些实施例中，第一消息可以包括：第一卡片的标识。例如，第一卡片的卡片名称。从而，在第二应用进程确定出第一卡片以及第一卡片中的第一卡片模块和第二卡片模块的基础上，减少了第一应用进程与第二应用进程之间的数据传输量。
在一些实施例中，第一消息可以包括：第一卡片的标识、第一卡片模块的标识和第二卡片模块的标识。例如，第一卡片的卡片名称、第一卡片模块的卡片模块编号和第二卡片 模块的卡片模块编号。从而，使得第二应用进程快速确定第一卡片中的第一卡片模块和第二卡片模块。
在一些实施例中，第一消息还可以包括：第一地址。从而，第一应用进程从第二应用进程接收发送到第一地址中的第一绘制结果，方便采用地址共享的方式，不仅使得第二应用进程提供第一绘制结果，还使得第一应用进程可以利用第一绘制结果显示第一应用的界面。
其中，本申请对第一地址的具体表示内容不做限定，如参见前文提及的地址1。需要说明的是，除了第一地址由第一应用进程向第二应用进程之外，第一地址也可以由第二应用进程向第一应用进程通知，或者，第一地址由第一设备中的操作***确定，并向第一应用进程和第二应用进程通知，本申请对此不做限定。
在一些实施例中，方法还包括：在第一设备有资源包集合的情况下，向第二应用进程发送第一消息，具体实现内容可参见图12b中的步骤101中的描述内容，此处不做赘述。从而，在第一设备没有资源包集合的情况下，第二应用进程便无法从资源包集合中调用第一卡片的界面资源，有利于降低第一设备执行不必要的操作，节省第一设备的功耗，以及使得第一设备可以及时下载资源包集合，以便快速实现卡片分享。
步骤22的一种可行的实现方式中，响应于用户的第二操作，向第三应用发送第二消息的具体实现过程可以包括：步骤41-步骤43。
步骤41、向第四应用进程发送第三消息。
步骤42、从第四应用进程接收第二绘制结果，第二绘制结果是第四应用进程基于第一卡片模块的界面资源渲染绘制得到的，第一卡片模块的界面资源是第四应用进程基于第三消息从资源包集合中调用得到的，资源包集合包括第一卡片中的第一卡片模块、第二卡片模块和第三卡片模块的界面资源以及第二卡片中的第四卡片模块和第五卡片模块的界面资源。
步骤43、基于第二绘制结果在第三应用的界面中显示第一卡片模块。
本申请中，步骤31-步骤33的执行主体为第一设备，具体地，步骤31-步骤33的执行主体为第一应用进程，具体实现过程可参见图3a-图3l、图13a-图13c中的步骤S201-S209、图14a-图14c中的步骤S301-S310以及图15a-图15c中的步骤S401-S409的描述内容，或者说参见将第一卡片从第一应用分享到第三应用的描述内容，此处不做赘述。
其中，本申请对第三消息的具体内容不做限定。
在一些实施例中，第三消息可以包括：第一卡片的标识和第一卡片模块的标识。例如，第一卡片的卡片名称和第一卡片模块的卡片模块编号。从而，使得第四应用进程快速确定第一卡片中的第一卡片模块。
在一些实施例中，第三消息还可以包括：第二地址。从而，第三应用进程从第四应用进程接收发送到第二地址中的第二绘制结果，以便采用地址共享的方式，不仅使得第四应用进程提供第二绘制结果，还使得第三应用进程可以利用第二绘制结果显示第三应用的界面。
其中，本申请对第二地址的具体表示内容不做限定，如参见前文提及的地址2或者地址3。需要说明的是，除了第二地址由第三应用进程向第四应用进程之外，第二地址也可以由第四应用进程向第三应用进程通知，或者，第二地址由第二设备或者第一设备中的操 作***确定，并向第三应用进程和第四应用进程通知，本申请对此不做限定。
在一些实施例中，方法还可以包括：在确定第三应用进程能够显示卡片的情况下，向第四应用进程发送第三消息，具体实现内容可参见图13c中的步骤201、图14c中的步骤301以及图15c中的步骤401中的描述内容，此处不做赘述。从而，由于在第三应用进程不能够显示卡片的情况下，第三应用进程便无法向第四应用进程发送第三消息，因此，有利于降低第三应用进程所在的设备执行不必要的操作，节省第三应用进程所在的设备的功耗，且使得第三应用进程所在的设备可以及时向用户通知第一应用无法向第三应用分享卡片。
在一些实施例中，资源包集合还包括第五应用的界面资源。其中，第五应用可参见前文提及的卡片应用，此处不做赘述。从而，为第五应用实现界面显示提供了资源支持。
在一些实施例中，第一应用的界面包括：第一区域和第二区域。第一卡片位于第一区域，第一应用页面位于第二区域，第一应用页面的界面资源是由第一应用提供的，具体实现内容可参见图10b以及图11中的描述内容，此处不做赘述。
在一些实施例中，第一应用包括：主屏幕、负一屏、控制中心、通知中心或者智能家居应用中的任意一个。
在一些实施例中，第三应用包括：主屏幕、负一屏、控制中心、通知中心或者智能家居应用中的任意一个。
示例性地，本申请还提供一种电子设备。该电子设备可以包括：至少一个存储器和至少一个处理器；存储器用于存储程序指令；处理器用于调用存储器中的程序指令使得第一设备执行前文实施例的卡片分享方法。
示例性地，本申请还提供一种计算机程序产品，包括：执行指令，所述执行指令存储在可读存储介质中，电子设备的至少一个处理器可以从所述可读存储介质读取所述执行指令，至少一个处理器执行所述执行指令使得所述电子设备实现前文实施例的卡片分享方法。
示例性地，本申请还提供一种计算机可读存储介质，其上存储有计算机程序，计算机程序被处理器使得电子设备执行时实现前文实施例的卡片分享方法。
示例性地，本申请还提供一种通信***。本申请的通信***可以包括：第一设备和第二设备；第一设备中安装有第一应用，第二设备安装有第三应用；第一应用，用于响应于用户的第一操作，显示第一应用的界面，第一应用的界面中显示有第一卡片，第一卡片包括第一卡片模块和第二卡片模块，第一卡片的界面资源是由第二应用提供的；第一应用，还用于响应于用户的第二操作，向第三应用发送第二消息，第二操作与第一卡片模块关联，第二消息用于指示第一卡片模块；第三应用，用于显示第三应用的界面，第三应用的界面中显示有第一卡片模块，第一卡片模块的界面资源是由第四应用提供的。
关于上述通信***中的第一设备和第二设备可参见前文描述示例，此处不做赘述。
在上述实施例中，全部或部分功能可以通过软件、硬件、或者软件加硬件的组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网 络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。

Claims (21)

  1. 一种卡片分享方法，其特征在于，包括：
    响应于用户的第一操作，显示第一应用的界面，所述第一应用的界面中显示有第一卡片，所述第一卡片包括第一卡片模块和第二卡片模块，所述第一卡片的界面资源是由第二应用提供的；
    响应于所述用户的第二操作，向第三应用发送第二消息，所述第二操作与所述第一卡片模块关联，所述第二消息包括所述第一卡片模块的标识；
    显示所述第三应用的界面，所述第三应用的界面中显示有所述第一卡片模块，所述第一卡片模块的界面资源是由第四应用提供的。
  2. 根据权利要求1所述的方法，其特征在于，所述第一卡片还包括：第三卡片模块，所述第三应用的界面中还显示有所述第三卡片模块，所述第三卡片模块的界面资源是由所述第四应用提供的。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一应用、所述第二应用、第三应用为第一设备中的不同的应用程序，第一应用进程对应所述第一应用，第二应用进程对应所述第二应用，第三应用进程对应所述第三应用，第四应用进程对应所述第四应用，所述第二应用与所述第四应用为同一个应用程序，所述第二应用进程与所述第四应用进程为同一个应用程序进程。
  4. 根据权利要求1或2所述的方法，其特征在于，所述第一应用和所述第二应用为第一设备中的不同的应用程序，第三应用和第四应用为第二设备中的不同的应用程序，所述第一设备与所述第二设备不同，第一应用进程对应所述第一应用，第二应用进程对应所述第二应用，第三应用进程对应所述第三应用，第四应用进程对应所述第四应用。
  5. 根据权利要求1或2所述的方法，其特征在于，所述第一应用和所述第二应用为第一设备中的不同的应用程序，第三应用为第二设备中的不同的应用程序，所述第一设备与所述第二设备不同，第一应用进程对应所述第一应用，第二应用进程对应所述第二应用，第三应用进程对应所述第三应用，第四应用进程对应所述第四应用，所述第二应用与所述第四应用为同一个应用程序，所述第二应用进程与所述第四应用进程为同一个应用程序进程。
  6. 根据权利要求2-5任一项所述的方法，其特征在于，
    向所述第二应用进程发送第一消息；
    从所述第二应用进程接收第一绘制结果，所述第一绘制结果是所述第二应用进程基于所述第一卡片的界面资源渲染绘制得到的，所述第一卡片的界面资源是所述第二应用进程基于所述第一消息从资源包集合中调用得到的，所述资源包集合包括所述第一卡片中的第一卡片模块、第二卡片模块和第三卡片模块的界面资源以及第二卡片中的第四卡片模块和第五卡片模块的界面资源；
    基于所述第一绘制结果在所述第一应用的界面中显示所述第一卡片。
  7. 根据权利要求6所述的方法，其特征在于，所述第一消息包括：所述第一卡片的标识。
  8. 根据权利要求6所述的方法，其特征在于，所述第一消息包括：所述第一卡片的标识、所述第一卡片模块的标识和所述第二卡片模块的标识。
  9. 根据权利要求7或8所述的方法，其特征在于，所述第一消息还包括：第一地址；
    从所述第二应用进程接收发送到所述第一地址中的所述第一绘制结果。
  10. 根据权利要求6-9任一项所述的方法，其特征在于，所述方法还包括：
    在所述第一设备有所述资源包集合的情况下，向所述第二应用进程发送所述第一消息。
  11. 根据权利要求2-10任一项所述的方法，其特征在于，
    向所述第四应用进程发送第三消息；
    从所述第四应用进程接收第二绘制结果，所述第二绘制结果是所述第四应用进程基于所述第一卡片模块的界面资源渲染绘制得到的，所述第一卡片模块的界面资源是所述第四应用进程基于所述第三消息从资源包集合中调用得到的，所述资源包集合包括所述第一卡片中的第一卡片模块、第二卡片模块和第三卡片模块的界面资源以及第二卡片中的第四卡片模块和第五卡片模块的界面资源；
    基于所述第二绘制结果在所述第三应用的界面中显示所述第一卡片模块。
  12. 根据权利要求11所述的方法，其特征在于，所述第三消息包括：所述第一卡片的标识和所述第一卡片模块的标识。
  13. 根据权利要求12所述的方法，其特征在于，所述第三消息还包括：第二地址；
    从所述第四应用进程接收发送到所述第二地址中的所述第二绘制结果。
  14. 根据权利要求11-13任一项所述的方法，其特征在于，所述方法还包括：
    在确定所述第三应用进程能够显示卡片的情况下，向所述第四应用进程发送所述第三消息。
  15. 根据权利要求6-14任一项所述的方法，其特征在于，所述资源包集合还包括第五应用的界面资源。
  16. 根据权利要求1-15任一项所述的方法，其特征在于，所述第一应用的界面包括：第一区域和第二区域；
    所述第一卡片位于所述第一区域，第一应用页面位于所述第二区域，所述第一应用页面的界面资源是由所述第一应用提供的。
  17. 根据权利要求1-16任一项所述的方法，其特征在于，所述第一应用包括：主屏幕、负一屏、控制中心或者通知中心中的任意一个。
  18. 一种电子设备，其特征在于，包括：至少一个存储器和至少一个处理器；
    所述存储器用于存储程序指令；
    所述处理器用于调用所述存储器中的程序指令使得所述电子设备执行权利要求1-17任一项所述的卡片分享方法。
  19. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器使得电子设备执行时实现权利要求1-17任一项所述的卡片分享方法。
  20. 一种通信***，其特征在于，包括：第一设备和第二设备；所述第一设备中安装有第一应用，所述第二设备安装有第三应用；
    所述第一应用，用于响应于用户的第一操作，显示所述第一应用的界面，所述第一应用的界面中显示有第一卡片，所述第一卡片包括第一卡片模块和第二卡片模块，所述第一卡片的界面资源是由第二应用提供的；
    所述第一应用，还用于响应于所述用户的第二操作，向第三应用发送第二消息，所述 第二操作与所述第一卡片模块关联，所述第二消息用于指示所述第一卡片模块；
    所述第三应用，用于显示所述第三应用的界面，所述第三应用的界面中显示有所述第一卡片模块，所述第一卡片模块的界面资源是由第四应用提供的。
  21. 一种程序产品，其特征在于，所述程序产品包括计算机程序，所述计算机程序存储在可读存储介质中，通信装置的至少一个处理器可以从所述可读存储介质读取所述计算机程序，所述至少一个处理器执行所述计算机程序使得通信装置实施如权利要求1-17任意一项所述的方法。
PCT/CN2021/092985 2020-06-08 2021-05-11 卡片分享方法、电子设备及通信*** WO2021249087A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/794,165 US20230004259A1 (en) 2020-06-08 2021-05-11 Card sharing method, electronic device, and communications system
EP21822929.2A EP4024210A4 (en) 2020-06-08 2021-05-11 CARD SHARING METHOD, ELECTRONIC DEVICE AND COMMUNICATION SYSTEM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010512011.3 2020-06-08
CN202010512011.3A CN113778574B (zh) 2020-06-08 2020-06-08 卡片分享方法、电子设备及通信***

Publications (1)

Publication Number Publication Date
WO2021249087A1 true WO2021249087A1 (zh) 2021-12-16

Family

ID=78834266

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/092985 WO2021249087A1 (zh) 2020-06-08 2021-05-11 卡片分享方法、电子设备及通信***

Country Status (4)

Country Link
US (1) US20230004259A1 (zh)
EP (1) EP4024210A4 (zh)
CN (2) CN116009999A (zh)
WO (1) WO2021249087A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116414277A (zh) * 2021-12-31 2023-07-11 华为技术有限公司 一种显示方法、终端、划船机和通信***
WO2023142940A1 (zh) * 2022-01-28 2023-08-03 华为技术有限公司 应用组件分享方法及相关设备
CN116088724B (zh) * 2022-05-19 2024-06-11 荣耀终端有限公司 卡片显示方法和电子设备
US20230385526A1 (en) * 2022-05-25 2023-11-30 Kyocera Document Solutions, Inc. Fine-grained control of visual display and scaling attributes
CN117170535A (zh) * 2022-05-27 2023-12-05 华为技术有限公司 卡片管理方法、电子设备及计算机可读存储介质
CN117676518A (zh) * 2022-08-31 2024-03-08 华为技术有限公司 一种卡片跨设备交互方法及电子设备
CN115309299B (zh) * 2022-09-14 2024-02-23 Oppo广东移动通信有限公司 桌面卡片的显示方法、装置、终端、存储介质及程序产品

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109032479A (zh) * 2018-06-07 2018-12-18 珠海格力电器股份有限公司 一种打开应用中功能界面的方法和装置
CN110572431A (zh) * 2019-07-31 2019-12-13 华为技术有限公司 一种卡片分享方法、装置及***
CN110837398A (zh) * 2019-10-15 2020-02-25 青岛海信移动通信技术股份有限公司 一种显示快应用的卡片的方法及终端
US20200097871A1 (en) * 2018-09-25 2020-03-26 Smartsheet Inc. Card view interface with automatically generated calculated value
CN111061522A (zh) * 2019-12-16 2020-04-24 深圳市随金科技有限公司 基于后端生成前端卡片组件的方法、装置、设备及存储介质

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040030719A1 (en) * 2002-02-13 2004-02-12 Jie Wei Web page based dynamic book for document presentation and operation
US8042110B1 (en) * 2005-06-24 2011-10-18 Oracle America, Inc. Dynamic grouping of application components
US7933632B2 (en) * 2005-09-16 2011-04-26 Microsoft Corporation Tile space user interface for mobile devices
US9171076B2 (en) * 2009-05-18 2015-10-27 International Business Machines Corporation Help information for links in a mashup page
US8621387B2 (en) * 2009-06-08 2013-12-31 Apple Inc. User interface for multiple display regions
US9058401B2 (en) * 2011-08-16 2015-06-16 Fabebook, Inc. Aggregating plug-in requests for improved client performance
US20130091513A1 (en) * 2011-10-10 2013-04-11 Mitchell International, Inc. Seamless external process integration
AU2013262488A1 (en) * 2012-05-18 2014-12-18 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs
US9747003B2 (en) * 2012-08-01 2017-08-29 Blackberry Limited Multiple-stage interface control of a mobile electronic device
US9665178B2 (en) * 2012-08-01 2017-05-30 Blackberry Limited Selective inbox access in homescreen mode on a mobile electronic device
US9458017B2 (en) * 2012-11-14 2016-10-04 Pontificia Universidad Catolica Madre Y Maestra Carbon nanotubes conformally coated with diamond nanocrystals or silicon carbide, methods of making the same and methods of their use
US10761673B2 (en) * 2013-03-12 2020-09-01 Oracle International Corporation Managing display of detachable windows in a GUI computing environment
WO2014157908A1 (en) * 2013-03-27 2014-10-02 Samsung Electronics Co., Ltd. Device and method for displaying execution result of application
KR101832394B1 (ko) * 2013-04-10 2018-02-26 삼성전자주식회사 단말 장치, 서버 및 그 제어 방법
KR20150081073A (ko) * 2014-01-03 2015-07-13 삼성전자주식회사 글랜스 정보를 제공하는 방법, 저장 매체 및 전자 장치
WO2017058956A1 (en) * 2015-09-29 2017-04-06 Weebly, Inc. Application dashboard
WO2017117455A1 (en) * 2015-12-29 2017-07-06 Quixey, Inc. Message based application state and card sharing methods for user devices
JP7076451B2 (ja) * 2016-12-21 2022-05-27 ウィックス．コム リミテッド． アクション可能なウィジェットカード
US10955994B2 (en) * 2017-06-02 2021-03-23 Apple Inc. User interfaces for downloading applications on an electronic device
US10404636B2 (en) * 2017-06-15 2019-09-03 Google Llc Embedded programs and interfaces for chat conversations
US10366136B2 (en) * 2017-09-20 2019-07-30 Wolters Kluwer Elm Solutions, Inc. Method for interacting with a web browser embedded in another software application
CN109923507B (zh) * 2017-10-31 2022-04-22 华为技术有限公司 在通知栏下拉菜单中管理多个自由窗口
CN108958867B (zh) * 2018-06-29 2021-01-15 维沃移动通信有限公司 一种应用的任务操作方法及装置
US10461710B1 (en) * 2018-08-28 2019-10-29 Sonos, Inc. Media playback system with maximum volume setting
WO2020048495A1 (zh) * 2018-09-06 2020-03-12 上海伴我科技有限公司 资源的配置方法、用户界面的导航方法及电子设备、存储介质
US20200183545A1 (en) * 2018-12-06 2020-06-11 Sonos, Inc. Selection of Playback Devices
US10860208B2 (en) * 2019-01-04 2020-12-08 Byton Limited Multi-window display controller

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109032479A (zh) * 2018-06-07 2018-12-18 珠海格力电器股份有限公司 一种打开应用中功能界面的方法和装置
US20200097871A1 (en) * 2018-09-25 2020-03-26 Smartsheet Inc. Card view interface with automatically generated calculated value
CN110572431A (zh) * 2019-07-31 2019-12-13 华为技术有限公司 一种卡片分享方法、装置及***
CN110837398A (zh) * 2019-10-15 2020-02-25 青岛海信移动通信技术股份有限公司 一种显示快应用的卡片的方法及终端
CN111061522A (zh) * 2019-12-16 2020-04-24 深圳市随金科技有限公司 基于后端生成前端卡片组件的方法、装置、设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4024210A4 *

Also Published As

Publication number Publication date
EP4024210A4 (en) 2022-12-14
CN116009999A (zh) 2023-04-25
CN113778574B (zh) 2022-11-29
US20230004259A1 (en) 2023-01-05
EP4024210A1 (en) 2022-07-06
CN113778574A (zh) 2021-12-10

Similar Documents

Publication Publication Date Title
WO2021013158A1 (zh) 显示方法及相关装置
WO2021249087A1 (zh) 卡片分享方法、电子设备及通信***
CN109814766B (zh) 一种应用显示方法及电子设备
WO2021036735A1 (zh) 显示用户界面的方法及电子设备
WO2021103981A1 (zh) 分屏显示的处理方法、装置及电子设备
WO2020177622A1 (zh) Ui组件显示的方法及电子设备
WO2021139768A1 (zh) 跨设备任务处理的交互方法、电子设备及存储介质
WO2021000804A1 (zh) 锁定状态下的显示方法及装置
WO2021213164A1 (zh) 应用界面交互方法、电子设备和计算机可读存储介质
WO2021036770A1 (zh) 一种分屏处理方法及终端设备
CN114327666B (zh) 应用启动方法、装置和电子设备
WO2021078032A1 (zh) 用户界面的显示方法及电子设备
WO2021253975A1 (zh) 应用程序的权限管理方法、装置和电子设备
WO2022017393A1 (zh) 显示交互***、显示方法及设备
WO2020155875A1 (zh) 电子设备的显示方法、图形用户界面及电子设备
WO2023130921A1 (zh) 一种适配多设备的页面布局的方法及电子设备
WO2021175272A1 (zh) 一种应用信息的显示方法及相关设备
WO2021218429A1 (zh) 应用窗口的管理方法、终端设备及计算机可读存储介质
WO2023138305A9 (zh) 卡片显示方法、电子设备及计算机可读存储介质
US20230259346A1 (en) Application Module Startup Method and Electronic Device
WO2021196980A1 (zh) 多屏交互方法、电子设备及计算机可读存储介质
WO2023207799A1 (zh) 消息处理方法和电子设备
WO2024109573A1 (zh) 悬浮窗显示的方法和电子设备
WO2024060968A1 (zh) 管理服务卡片的方法和电子设备
EP4372579A1 (en) Application recommendation method and electronic device

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: 21822929

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021822929

Country of ref document: EP

Effective date: 20220328

NENP Non-entry into the national phase

Ref country code: DE