Cross-device application calling method, electronic device and system

Abstract

The invention discloses a cross-device application calling method, electronic equipment and a system, and relates to the technical field of terminals. And when the first equipment needs to call the application of the second equipment to execute the corresponding action, converting a first calling intention which can be identified by the first equipment into a second calling intention which can be identified by the second equipment through the class adapter. After the second device receives the second calling intention, the second calling intention can be recognized, and then the application is called to execute the corresponding action. And finishing a cross-device application calling task.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a cross-device application calling method, electronic device and system. Background Art

[0002] With the development of science and technology, there are more and more types of electronic devices (such as mobile phones, tablet computers, laptops, etc.). Different types of electronic devices have different hardware configurations and are applicable to different scenarios. For example, compared with tablet computers, mobile phones have more powerful camera functions and are small and easy to carry; compared with mobile phones, tablet computers have larger screens and can be connected to physical keyboards, making them easier to edit text or pictures.

[0003] In daily applications, users can associate different electronic devices and use multiple electronic devices to complete work at the same time. For example, when a user is using a tablet to edit a document, he needs to insert a picture of the surrounding scenery. However, the camera function of the tablet is poor, and the quality of the pictures taken is not high; and the tablet is large in size, which is not convenient for taking pictures. In this case, the tablet can call the camera application of the mobile phone associated with the tablet to take pictures of the surrounding scenery, and then the mobile phone transfers the pictures to the tablet, and the tablet inserts the pictures into the text.

[0004] However, different electronic devices may use different system versions. When two electronic devices with different system versions call applications across devices, problems may occur such as the inability to recognize the calling intent or the inability to recognize the data due to different system versions, which further leads to the inability to use multiple electronic devices to work collaboratively. Summary of the invention

[0005] In view of this, the embodiments of the present application provide a cross-device application calling method, electronic device and system, which can provide users with a cross-device application calling experience.

[0006] In the first aspect, the embodiment of the present application provides a method for calling a cross-device application, the method comprising: when a user triggers an operation on a first device, the first device generates and obtains a first calling intent through a first type adapter, and uses the first type adapter to convert the first calling intent into a second calling intent that can be recognized by a second device. The first device is a device of the first system version; the second device is a device of the second system version.

[0007] Through this method, after receiving the second call intent, the second device can identify the second call intent, and then execute the corresponding call action according to the second call intent, thereby realizing cross-device application calls. In addition, when the system version of the first device is different from the system version of the second device, the call intent is converted through a class adapter, and the call intent recognizable by the first device is converted into a call intent recognizable by the second device, so that the second device can recognize the second call intent, thereby completing the cross-device application call between two devices with different system versions.

[0008] In some embodiments, before using the first type of adapter to convert the first call intent into the second call intent, the first type of adapter can also be used to filter the parameters of the first call intent, retaining the target parameters for implementing the application call that are editable and controllable by the device system. Then, the first type of adapter is used to convert the target parameters to obtain the second call intent.

[0009] In addition to the above-mentioned target parameters, the first call intent also includes some parameters that are not controlled by the device editor and parameters that are irrelevant to the application call. Even if such parameters are sent to the second device, the second device cannot recognize them. Therefore, by filtering the parameters in the first call intent through the first-class adapter, the parameters other than the target parameters are discarded, and the amount of parameters that need to be transmitted across devices and converted by the first-class adapter is reduced. On the one hand, transmission resources can be saved, and on the other hand, the conversion speed can be improved.

[0010] In some embodiments, the first device further includes a second type of adapter. Before using the first type of adapter to convert the first call intent into the second call intent, the first type of adapter is first used to filter the parameters of the first call intent, and the target parameters editable and controllable by the device system for implementing the application call are retained. The first type of adapter is then used to filter the data in the additional parameters in the target parameters, and the target data editable and controllable by the device system for implementing the application call are retained.

[0011] It is understandable that, in addition to the above-mentioned target data, the additional parameters also include some parameter data that is not controlled by the device editor, and data that is not related to the application call. Similarly, the second device cannot recognize this type of data. Therefore, after using the first type of adapter to filter the parameters in the first call intent, the second type of adapter is also used to filter the data in the additional parameters. Finally, the filtered parameters and data are converted by the first type of adapter and the second type of adapter to obtain the second call intent. Further reduce the amount of parameters that need to be transmitted across devices and the amount of parameters that need to be converted by the first type of adapter.

[0012] In some embodiments, the first type adapter stores conversion methods between the intent of the first system version and the intent of multiple system versions. After the first device searches the first type adapter for the conversion method from the intent of the first system version to the intent of the second system version, it can use the first type adapter to convert the first call intent into the second call intent.

[0013] By storing the conversion method of the intent of the first system version and the intent of multiple system versions in the first type of adapter. When the first device needs to call an application in other devices, it can find the conversion method from the intent of the first system version to the intent of the system version of other devices from the first type of adapter, and then convert the calling intent through the first type of adapter. Other devices can accept and identify the calling intent, and call the corresponding application to complete the cross-device application call.

[0014] In some embodiments, the first device converts the first call intent into a general call intent recognizable by both the first device and the second device through a first type adapter, and instructs the second device to convert the general call intent into a third call intent through the general call intent, thereby recognizing the third call intent.

[0015] By converting the first call intent into a universal call intent, the second device can convert the universal call intent into a second call intent after receiving the universal call intent. In addition, through this method, only the conversion method between the system version intent of the device and the universal system version intent needs to be stored in the class adapter of the device, thereby reducing the stored conversion methods and the occupied storage space.

[0016] In some embodiments, after completing the application call, the second device generates a first call completion intent, and uses a class adapter to convert the first call completion intent into a second call completion intent that can be recognized by the first device. The second call completion intent is returned to the first device. After receiving the second call completion intent, the first device can identify the second call completion intent, and then determine that the second device has called the target application to perform the target action.

[0017] By receiving the second call completion intention that can be recognized by the first device through the first device, the first device can be informed whether the second device has completed the application call, so as to facilitate the next operation.

[0018] In some embodiments, the method can be applied to a scenario where a camera application is called across devices to take photos. The first device includes a notebook application, a first distributed application framework, and a first type of adapter, and the second device includes a camera application and a second distributed application framework. In this application scenario, the first call intent is a first photo intent, which is used to instruct the second device to call a camera application to take photos; the second call intent is a second photo intent. When the user chooses to use the camera application in the second device to take photos in the notebook application, the notebook application will first generate a first photo intent and send the first photo intent to the first distributed application framework. Then, the first device uses the first type of adapter to convert the first photo intent. When the first distributed application framework receives the second photo intent sent by the first type of adapter application, the first distributed application framework sends the second photo intent to the second distributed application framework in the second device. Finally, the second distributed application framework identifies the second photo intent and then calls the camera application to take photos.

[0019] In this way, it is possible to call the camera application in the second device through the first device to take pictures, thereby completing the cross-device application call.

[0020] In some embodiments, the first device may convert the first photographing intent into a general photographing intent. After the second device receives the general photographing intent, it uses a third type of adapter to convert the general photographing intent into a third photographing intent recognizable by the second device, and then recognizes the third photographing intent to call a camera application to complete the photographing.

[0021] By using this method, the first type adapter of the first device only needs to store the conversion method between the intent of the first system version and the intent of the second system version. The third type adapter of the second device only needs to store the conversion method between the intent of the second system version and the intent of the second system version. This can reduce the conversion methods stored in the class adapters and reduce the storage space occupied.

[0022] In one embodiment, the method can be applied to a scenario where a camera application is called across devices to take photos. The first device includes a notebook application, a first distributed application framework, and a first type of adapter, and the second device includes a camera application, a second distributed application framework, and a third type of adapter. In this application scenario, the first call completion intent is a first photo completion intent, and the second call completion intent is a second photo completion intent, and both the first device and the second device can recognize the second photo completion intent. When the second device calls the camera application to complete the photo, the first photo completion intent is generated first, and the first photo completion intent is converted into the second photo completion intent through the third type of adapter. Then, the second distributed application framework sends the second photo completion intent to the first distributed application framework. After receiving the second photo intent, the first distributed application framework uses the first type of adapter to convert the second photo intent into the third photo completion intent. Finally, the first distributed application framework identifies the third photo completion intent and notifies the notebook application that the camera application of the second device has been called to take photos. The notebook application can perform subsequent operations.

[0023] In this way, the first device receives the second photographing completion intent and converts the second photographing completion intent into the third photographing completion intent, thereby identifying the third photographing completion intent, so that the camera application in the first device can know whether the second device has called the camera application to take a photo, so that the user can perform the next operation according to the calling result.

[0024] In the second aspect, an embodiment of the present application provides a method for calling a cross-device application, the method comprising: when a user triggers an operation on a first device, the first device generates a first calling intent and sends the first calling application to a second device. After the second device receives the first calling application, it uses a third-class adapter to convert the first calling intent into a second calling intent that can be recognized by the second device. The first device is a device of the first system version; the second device is a device of the second system version.

[0025] Through this method, after receiving the first call intent, the second device can convert the first call intent so that the second device can recognize the second call intent, and then execute the corresponding call action according to the second call intent to realize cross-device application calling. In addition, when the system version of the first device is different from the system version of the second device, the call intent is converted through the class adapter, and the call intent recognizable by the first device is converted into a call intent recognizable by the second device, so that the second device can recognize the second call intent, and then complete the cross-device application calling between two devices with different system versions.

[0026] In some embodiments, the first calling intent may be an intent that can only be recognized by the first device, or may be an intent that can be recognized by both the first device and the second device.

[0027] In this way, no matter the second device receives a recognizable calling intent or an unrecognizable calling intent, through the conversion of the class adapter, the second device can obtain a second calling intent that can be recognized by the second device, and then call the target application to perform the target action, thereby realizing the calling of cross-device applications.

[0028] In a third aspect, the present application also provides an electronic device, comprising a memory and one or more processors, wherein the memory is coupled to the processor; wherein computer program code is stored in the memory, and the computer program code comprises computer instructions, and when the computer instructions are executed by the processor, the electronic device executes the methods in the above-mentioned first aspect, second aspect and any possible design thereof.

[0029] In a fourth aspect, the present application also provides a communication system, comprising a first device and a second device, wherein the first device is used to execute the method executed by the first device in the above-mentioned first aspect, second aspect and any possible design thereof, and the second device is used to execute the method of interaction between the second device and the first device in the above-mentioned first aspect, second aspect and any possible design thereof.

[0030] In a fifth aspect, the present application also provides a computer-readable storage medium, comprising computer instructions, which, when executed on an electronic device, enable a server to execute the methods in the first aspect, the second aspect and any possible design thereof.

[0031] In a sixth aspect, the present application provides a chip system, which is applied to an electronic device including a processor and a memory. The chip system includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected through lines. The interface circuit is used to receive signals from the memory of the electronic device and send signals to the processor. The signals include computer instructions stored in the memory. When the processor executes the computer instructions, the electronic device implements the methods in the first aspect, the second aspect and any possible design thereof.

[0032] It can be understood that the beneficial effects that can be achieved by the above-mentioned server, electronic device, communication system, chip system, computer-readable storage medium, and computer program product can be referred to the beneficial effects in the first aspect, the second aspect and any possible design method thereof, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in this embodiment or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0034] Figure 1 A schematic diagram of a cross-device application call in the related art;

[0035] Figure 2 One of the schematic diagrams of cross-device application calls provided in an embodiment of the present application;

[0036] Figure 3 A hardware structure diagram of an electronic device provided in an embodiment of the present application;

[0037] Figure 4 A software architecture diagram of an electronic device (such as a first device / second device) provided in an embodiment of the present application;

[0038] Figure 5 One of the interactive signaling diagrams of the cross-device application calling method provided in the embodiment of the present application;

[0039] Figure 6 An interface diagram of a tablet computer provided in an embodiment of the present application;

[0040] Figure 7 A schematic diagram of intent conversion performed by an intent class adapter provided in an embodiment of the present application;

[0041] Figure 8 A schematic diagram of an additional parameter class adapter provided in an embodiment of the present application performing additional parameter conversion;

[0042] Fig. 9 The second interactive signaling diagram of the cross-device application calling method provided in the embodiment of the present application;

[0043] Fig.10 This is an interface diagram of a mobile phone provided in an embodiment of the present application;

[0044] Fig.11 A second schematic diagram of a cross-device application call provided in an embodiment of the present application;

[0045] Fig.12 The third schematic diagram of cross-device application calling provided in an embodiment of the present application;

[0046] Fig.13 A fourth schematic diagram of a cross-device application call provided in an embodiment of the present application;

[0047] Fig.14A fifth schematic diagram of a cross-device application call provided in an embodiment of the present application;

[0048] Fig.15 Schematic diagram six of cross-device application calling provided in an embodiment of the present application;

[0049] Fig.16 A structural diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] The technical solutions in the embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application. Reference to "one embodiment" or "some embodiments" described in this specification means that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in the different parts of this specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways. The term "connection" includes direct connection and indirect connection, unless otherwise specified. "First" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

[0051] In the embodiments of the present application, the words "exemplarily" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a specific way.

[0052] In order to make the description of the following embodiments clear and concise, a brief introduction to the related technology is first given:

[0053] Intent is an abstract description of an operation to be performed. It is the hub between the four major components of Android and a bridge of communication. Intent is responsible for describing the action, data involved in the action, and additional data of an operation in the application. Android is responsible for finding the corresponding component based on the description of the intent, passing the intent to the called component, and completing the call of the component. Intent specifically includes the following components: Action (intent type, a required part of the intent, expressed as a character), Data (URI parameter), Flags (Flage parameter), Package (specify the intent package name), Component (specify the intent component name), Category (intent matching category), ClipData (clipboard data) and Extras (extra parameters).

[0054] Bundle (executable file) is a type of Extras (extra parameters) in intent. In intent, Extras can be set to Bundle. Bundle is mainly used to transfer data in the form of key-value pairs.

[0055] A class adapter is a converter that converts the adapter interface into a target interface by inheriting or referencing the adapter's object, and then accesses the adapter in the format of the target interface.

[0056] At present, a more feasible way to call applications across devices is as follows: when the first device needs to call an application in the second device, the first device sends a call intent to the second device. After receiving the call intent, the second device identifies the call intent, determines the target application that the first device wants to call, and the operation that needs to be performed when calling the target application. The second device then calls the target application and completes the operation, and transmits the obtained data back to the first device.

[0057] To better understand the relevant technologies, Figure 1 The relevant technology is described. Figure 1 As shown in the figure, A is a tablet computer and B is a mobile phone. When a user edits a document through tablet computer A, if the user wants to insert a picture of the surrounding environment into the document, and the picture taken by tablet computer A is of poor quality, the user can take the picture through mobile phone B, which has a relatively stronger camera function. Tablet computer A will send a photo intent to mobile phone B, which is used to instruct mobile phone B to pull up the camera application as the target application and take a picture. Mobile phone B receives the photo intent and recognizes the photo intent, and then determines that the target application is the camera application. The required operation is to take a picture, pull up the camera application and perform the photo operation to obtain the required picture. Mobile phone B returns the picture to tablet computer A, so that tablet computer A inserts the picture into the document, completing the entire process of calling the camera application across devices.

[0058] However, there is an important prerequisite for the above-mentioned related technologies to be successfully implemented, that is, the system version of the device initiating the call is the same as the system version of the device receiving the call.

[0059] In different system versions, the intents used to express or describe the same content may have different expressions or parameter formats. Taking the call intent described above as an example, a device with system version S cannot recognize or cannot correctly recognize the call intent sent by a device with system version T. The result of the recognition of this call intent by the device with system version S may be that it cannot be recognized, the target application is incorrectly identified, or the operation to be performed is incorrectly identified. In the above situations, the user cannot achieve the purpose of calling the device application to perform the corresponding operation.

[0060] Likewise Figure 1 Taking the scenario shown as an example, it is assumed that the system version of tablet A is S and the system version of mobile phone B is T. After receiving the photo intent sent by tablet A, mobile phone B needs to identify the photo intent. Since the system versions of mobile phone B and tablet A are different, the recognition results may be as follows: 1. The photo intent cannot be recognized and the camera application cannot be launched to take photos; 2. The photo intent is recognized incorrectly, and other applications other than the camera application are launched; 3. The photo intent is recognized incorrectly, and the camera application is launched to record the video. When any of the above three situations occurs, the cross-device call to the camera application cannot be successfully completed. Even if mobile phone B can correctly recognize the photo intent and successfully launch the camera application to take photos and obtain pictures, in the process of mobile phone B sending the pictures back to tablet A, the tablet may not be able to receive the pictures or the received pictures may not be displayed correctly due to different system versions. It can be seen that the inconsistency of system versions will affect cross-device application calls and / or data transmission.

[0061] In response to the problems existing in the above-mentioned related technologies, an embodiment of the present application provides a method for calling a cross-device application, which can be applied to the above-mentioned scenario of calling an application across devices. By converting the intent of cross-device transmission, the intent that can be recognized by the sending device is converted into the intent that can be recognized by the receiving device, so that the receiving device can operate according to the converted intent to complete the cross-device application call. Similarly, the method provided by the embodiment of the present application is also applicable to cross-device data transmission. By converting the data transmitted across devices, the data that can be recognized by the sending device is converted into the data that can be recognized by the receiving device, so that the receiving device can accurately recognize the converted data and complete the cross-device data transmission.

[0062] Figure 2This is one of the schematic diagrams of cross-device application calls provided in an embodiment of the present application. The first device and the second device serve as the device that initiates the call and the device that receives the call, respectively. Figure 2 As shown, the first device is a tablet computer 200, the second device is a mobile phone 210, and the system versions of the tablet computer 200 and the mobile phone 210 are different. When the tablet computer 200 runs a document editing application, it can display Figure 2 The first interface 201 shown in the figure shows the interface of the notebook application, including the edited document content, such as "Daily Essays...", and also includes a picture insertion control 202. The tablet computer 200 can receive a trigger operation of the user on the picture insertion control 202 (such as: clicking the control), and in response to the user's click operation on the picture insertion control 202, the tablet computer 200 sends a photo-taking intention that can be recognized by the mobile phone 210 to the mobile phone 210, so that the mobile phone 210 completes the photo-taking operation according to the photo-taking intention after recognizing the photo-taking intention. When the tablet computer 200 receives the photo-taking completion intention that can be recognized by the tablet computer 200, the picture 203 obtained by the mobile phone 210 can be inserted into the corresponding "picture to be inserted" position in the document. Figure 2 The picture 203 in the second interface 204 is a picture taken by a mobile phone 210 . Figure 2 The second interface 204 also shows the insertion effect of the picture 203.

[0063] It should be noted that the applications (such as the first application and the second application) in the embodiments of the present application may be embedded applications (i.e., system applications of the electronic device) installed in the electronic device or downloadable applications. Among them, the embedded application is an application provided as part of the implementation of the electronic device (such as a mobile phone). A downloadable application is an application that can provide its own Internet Protocol Multimedia Subsystem (IMS) connection. The downloadable application may be an application pre-installed in the terminal or a third-party application that can be downloaded and installed in the terminal by the user.

[0064] For example, the above application may be an embedded application installed in the terminal (i.e., a system application of the terminal). For example, the application running in the above first device may be a picture editor, and the application to be called in the second device may be a camera. Taking the first device calling the camera application in the second device as an example, the first device may instruct the second device to open the camera application to take a picture through the camera application, and the second device may send the picture obtained by taking the picture to the first device, so that the first device may edit the picture through the picture editor after receiving the picture.

[0065] For another example, the application may also be a downloadable application. The application running in the first device may be a word processing system (WPS). In the method, still taking the first device calling the camera application in the second device as an example, the first device may instruct the second device to open the camera application to take a photo through the camera application, and the second device sends the photo to the first device, so that the first device inserts the photo into the document created by the WPS after receiving the photo.

[0066] The first device and the second device can be communicatively connected. The communication connection includes an Internet connection. Through the Internet connection, the first device (or the second device) can send an intent to the second device (or the first device) to facilitate cross-device communication. And, the communication connection also includes a near-field communication connection. Through the near-field communication connection, the first device can send a call intent to the second device point-to-point, and the second device can send a call completion intent to the first device point-to-point, and data can also be transmitted. Among them, near-field communication includes Bluetooth, Wireless Fidelity (Wireless Fidelity, WIFI), Near Field Communication (Near Field Communication, NFC), etc.

[0067] It should be noted that in the embodiments of the present application, compared with Internet connection: transmitting calling intentions and data through near-field communication, on the one hand, can transmit information in a point-to-point manner, which is more conducive to ensuring information security. On the other hand, if near-field communication technologies such as Bluetooth or NFC that do not rely on the network are used, the information transmission rate will not be affected by network factors, and information can be transmitted more stably and quickly. Moreover, even if the first device and / or the second device is not connected to the network, cross-device calling of applications and transmission of data can be achieved.

[0068] It should be noted that the first device and the second device may not establish an Internet connection and a near field communication connection at the same time. For example, when the first device calls the camera application of the second device, only a near field communication connection may be established without establishing an Internet connection.

[0069] In some examples, the first device and the second device may have the same system-level user account logged in, such as the same Account number, same Accounts, etc. It should be understood that devices with the same account (such as the first device and the second device) that log in to the same user account can be added to the same trusted environment through identity authentication. Therefore, information interaction can be performed only within the trusted environment, such as calling the capabilities of the camera application, transmitting the calling intent, transmitting images, etc., to ensure device security.

[0070] The first device and the second device are merely divided based on the different functional roles they play in the cross-device application call scenario. The first device is a sending device that sends the call intent, and the second device is a receiving device that receives the call intent. It should be understood that the same electronic device can be used as the first device in some scenarios and as the second device in other scenarios. Figure 2 In the example, if the user wishes to call the camera application of the tablet computer 200 to take a photo while editing a document on the mobile phone 210, the mobile phone 210 is the sending device that sends the photo intention, and can also be called the first device. If the tablet computer 200 calls the camera application and performs the photo operation after receiving and identifying the photo intention, the tablet computer 200 is the receiving device that receives the photo intention, and can also be called the second device.

[0071] Exemplarily, the first device / second device may be a handheld device, a vehicle-mounted device, etc., such as a mobile phone, a tablet, a laptop computer, a PDA, a mobile internet device (MID), a virtual reality (VR) device, an augmented reality (AR) device, a wireless device in industrial control, a wireless device in self-driving, a wireless device in remote medical surgery, a wireless device in a smart grid, a wireless device in transportation safety, a wireless device in a smart city, a wireless device in a smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with a wireless communication function, a personal computer (PC), a wireless communication device, ... Computer, PC), computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in a 5G network, or terminal device in a future evolved public land mobile communication network (public landmobile network, PLMN), etc., the embodiments of the present application are not limited to this.

[0072] The first device / second device may also be a wearable device, such as a smart watch or smart glasses, and may focus on a certain type of application function and be used in conjunction with other devices such as smart phones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0073] The first device / second device mentioned above may also be a terminal device in an Internet of Things (IoT) system.

[0074] See also Figure 3 , Figure 3 The hardware structure diagram of an electronic device (such as a first device / a second device) provided in an embodiment of the present application. Figure 3 As shown, taking the electronic device as a mobile phone as an example, it may include: a processor 310, an external memory interface 320, an internal memory 321, a universal serial bus (USB) interface 330, a charging management module 340, a power management module 341, a battery 342, an antenna 1, an antenna 2, a mobile communication module 350, a wireless communication module 360, an audio module 370, a speaker 370A, a receiver 370B, a microphone 370C, an earphone interface 370D, a sensor module 380, a button 390, a motor 391, an indicator 392, a camera 393, a display screen 394, and a subscriber identification module (SIM) card interface 395, etc.

[0075] It is to be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0076] The processor 310 may include one or more processing units, for example, the processor 310 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

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

[0078] The charging management module 340 is used to receive charging input from a charger. The charger can be a wireless charger or a wired charger. While the charging management module 340 charges the battery 342, it can also power the electronic device through the power management module 341.

[0079] The power management module 341 is used to connect the battery 342, the charging management module 340 and the processor 310. The power management module 341 receives input from the battery 342 and / or the charging management module 340, and supplies power to the processor 310, the internal memory 321, the external memory, the display screen 394, the camera 393, and the wireless communication module 360. The power management module 341 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc.

[0080] The wireless communication function of the electronic device can be implemented through antenna 1, antenna 2, mobile communication module 350, wireless communication module 360, modem processor and baseband processor.

[0081] In some embodiments, when the electronic device acts as a first device / second device, it can transmit intent and data based on antenna 1, antenna 2, mobile communication module 350 and wireless communication module 360.

[0082] The electronic device implements the display function through a GPU, a display screen 394, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 394 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 310 may include one or more GPUs that execute program instructions to generate or change display information.

[0083] The electronic device can realize the shooting function through ISP, camera 393, video codec, GPU, display screen 394 and application processor.

[0084] In some embodiments, when the electronic device acts as a second device, it can call the camera 393 to capture an image based on the photo-taking intention of the first device and return the image to the first device.

[0085] The external memory interface 320 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor 310 through the external memory interface 320 to implement a data storage function. For example, files such as music and videos can be stored in the external memory card.

[0086] The internal memory 321 can be used to store computer executable program codes, which include instructions. The processor 310 executes various functional applications and data processing of the electronic device by running the instructions stored in the internal memory 321. The internal memory 321 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device (such as audio data, a phone book, etc.), etc. In addition, the internal memory 321 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

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

[0088] In some embodiments, the user's voice can be acquired through the microphone 370C, and the voice can be recognized by the processor 310, converted into text, and then the document can be edited.

[0089] In some embodiments, when the user uses the first device to perform audio editing, it is necessary to call the recording application of the second device to obtain the audio. The first device can meet the user's audio pre-listening needs during the audio editing process through the speaker 370A and the receiving microphone 370B. The second device can collect audio through the microphone 370C, and when the headphone interface 370D is connected to other audio devices, it can also receive the audio collected by other audio devices through the headphone interface 370D.

[0090] The key 390 includes a power key, a volume key, etc. The key 390 can be a mechanical key or a touch key. The electronic device can receive key input and generate key signal input related to user settings and function control of the electronic device.

[0091] In some embodiments, when the electronic device acts as a second device and calls the camera 393 to take a photo based on the photo taking intention of the first device, the photo taking operation can be quickly completed by triggering the button 390 .

[0092] Motor 391 can generate vibration prompts. Motor 391 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 394, motor 391 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0093] Indicator 392 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0094] In some embodiments, the electronic device acts as a second device, and when receiving a photographing intention sent by the first device, the electronic device can receive the photographing intention through the indication of the indicator light 392.

[0095] The SIM card interface 395 is used to connect a SIM card. The SIM card can be connected to or disconnected from the electronic device by inserting the SIM card interface 395 or pulling the SIM card out of the SIM card interface 395. The electronic device can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 395 can support Nano SIM cards, Micro SIM cards, SIM cards, etc.

[0096] In the embodiment of the present application, the software system of the electronic device (such as the first device / the second device) can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. Taking the system as an example, the software structures of the first device and the second device are exemplified.

[0097] See also Figure 4 The software architecture diagram of the electronic device (such as the first device / the second device) provided in the embodiment of the present application. As shown in the figure, the layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Data is transmitted and communicated between the layers through software interfaces. In some embodiments, The system is divided into five layers, from top to bottom: application layer, application framework layer, Runtime and system libraries, hardware abstraction layer (HAL), and kernel layer.

[0098] The application layer may include a series of application packages, which may include notebook, memo, recording, camera, social software and other applications.

[0099] In an embodiment of the present application, the application layer of the electronic device (such as the first device / second device) also includes document editing applications such as WPS, office, and memo, video editing applications, image processing applications, social applications, etc.

[0100] When the electronic device is the first device, a photo taking intention is sent to the second device, and after receiving the photo taking completion intention, the photo taken by the second device is used in a document editing application, a video editing application, a picture processing application or a social application.

[0101] When the electronic device is the second device, it receives the photographing intention sent by the first device, identifies the photographing intention, launches the camera application and takes a photo, and after obtaining the photo, sends the photographing completion intention to the first device.

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

[0103] The application framework layer may include class adapters, notification managers, resource managers, and view systems, etc.

[0104] The class adapter can convert the interface of one class into the interface of another class, thereby making the classes with originally incompatible interfaces compatible. In the embodiment of the present application, when the system versions of the first device and the second device are different, the class adapter can be used to convert the intent and data based on the difference in the device system versions, so that the device as the receiving party can correctly identify the intent and data.

[0105] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, the terminal device vibrates, the indicator light flashes, etc.

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

[0107] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

[0108] In addition, the application framework layer may also include a distributed application framework, connection services, application authentication services, communication services, device management services (Profile) and meta-capability management services.

[0109] The distributed application framework can call the package management service based on the received intent to query whether the target application indicated by the intent has been installed on the device, and when the target application is not installed, it can request the capability management service (Ability Manager Service, AMS) to start the process of downloading and installing the target application based on the download information obtained by the package management service.

[0110] The continuation service provides the application with near-field device discovery awareness and the ability to send data and files. For example, the continuation service can be responsible for the access of the application. And, after the application accesses the continuation service, the continuation service can also be responsible for querying other devices that can be called by the application (i.e., available devices below), and transmitting the call intent and data across devices.

[0111] The application authentication service can be responsible for the legitimacy verification of the application, such as verifying the identity and permissions of the application. For example, the application authentication module can be responsible for verifying the legitimacy of the application requesting access to the continuation service. Only when the application is confirmed to be legitimate, the application is allowed to access the continuation service. This avoids providing illegal applications with services that call other devices and improves the security of application use.

[0112] Communication services such as The smart interconnection service (Magic Link) can be used to realize data transmission across devices, security authentication and account authentication of devices with the same account, self-discovery and self-organizing network of devices, etc. For example, through the communication service, the first device can discover the second device in the near field and verify the identity of the second device, and after verifying that the second device is a trusted device (i.e., a device logged in with the same user account), transmit intentions and data between the first device and the second device.

[0113] The device management service can be regarded as a database for synchronizing data between devices. The database can record the capabilities of devices with the same account, the situation in which the capabilities are occupied, information about near-field devices, etc. For example, the device management service of the first device can record information such as the camera function of the second device, the situation in which the camera function is occupied, and the devices within the near-field communication range.

[0114] The meta-capability management service is used to manage the meta-capability information of applications installed on electronic devices. It can start applications based on intent information and perform operations corresponding to the intent information.

[0115] The runtime includes the core library and the virtual machine. The runtime is responsible for Scheduling and management of the system.

[0116] The core library consists of two parts: one is the function called by Java language, and the other is the core library of Android.

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

[0118] The system library may include multiple functional modules, such as media libraries, function libraries, graphics processing libraries (such as OpenGL ES), etc.

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

[0120] The function library provides developers with API interfaces for multiple services, making it easy for developers to quickly integrate and implement various functions.

[0121] The graphics processing library is used to implement graphics drawing, image rendering, synthesis and layer processing.

[0122] The hardware abstraction layer is an abstracted structure between the kernel layer and the Android runtime. The hardware abstraction layer can be a package of the hardware driver, providing a unified interface for the call of the upper layer application. The hardware abstraction layer can include a Bluetooth module, a WIFI module, etc. Exemplarily, the Bluetooth module and the WIFI module can shield the specific hardware implementation details of the Bluetooth driver and the WIFI driver in the kernel layer, and the upper layer application can implement the Bluetooth function and the WIFI function by calling the interface without having to know the specific implementation method of the kernel layer hardware driver.

[0123] The kernel layer is the layer between hardware and software. The kernel layer may include display drivers, camera drivers, audio drivers, Bluetooth drivers, WiFi drivers, Universal Serial Bus (USB) drivers, CPU drivers, etc.

[0124] In some embodiments, communication services (such as Magic Link) can connect across devices through relevant near-field communication modules such as Bluetooth drivers and WiFi drivers, thereby achieving self-discovery and self-organizing networking of devices.

[0125] The present application embodiment will be combined with Figure 4 The software architecture of Figure 2 An implementation process of the scenario shown is described below:

[0126] After the notebook application on the tablet computer 200 is connected to the connection service, if the user needs to insert images of surrounding objects into the document while using the notebook application to edit the document. The notebook application can query the available devices through the connection service and the device management service, and the available devices include the mobile phone 210. Then, the notebook application can determine the mobile phone 210 among the available devices through the class adapter, connection service and communication service of the tablet computer 200, and send the photo-taking intention converted by the class adapter to the mobile phone 210 to call the camera application of the mobile phone 210. After the communication service, connection service and class adapter of the mobile phone 210, the class adapter of the mobile phone 210 receives the photo-taking intention sent by the tablet computer 200 and converted by the class adapter of the tablet computer 200, and converts the photo-taking intention again into a photo-taking intention that can be recognized by the mobile phone 210 of the current system version. The connection service of the mobile phone 210 starts the camera application of the mobile phone 210 to call the camera application of the mobile phone 210 to take a photo. After the camera application of the mobile phone 210 is used to take pictures, the mobile phone 210 feeds back the intention of completing the picture taking to the tablet computer 200, and finally notifies the notebook application of the tablet computer 200 that the picture taking is completed through the camera of the mobile phone 210, the class adapter, the connection service and the communication service of the tablet computer 200, the connection service and the class adapter of the tablet computer 200. In this way, the notebook application of the tablet computer 200 can call the camera application in the mobile phone 210 and obtain the pictures taken by the mobile phone 210, thus realizing the application call between two devices with different system versions.

[0127] At this point, it should be noted that the above Figure 4 Android TM The system is used as an example to illustrate the software architecture of the first device and the second device in the embodiment of the present application. In practice, the operating system of the first device and / or the second device may also be Windows TM System. In WindowsTM In the operating system, the application layer (such as the PC manager application) can also integrate the connection service, application authentication service, communication service, device management service in the application framework layer, and the functions of the Bluetooth module and WIFI module in the hardware abstraction layer. The application layer completes near-field communication with the other end by calling the Bluetooth driver or WIFI driver to realize data transmission between devices.

[0128] The cross-device application calling method provided in the embodiment of the present application can be implemented in a communication system composed of a first device and a second device having the above-mentioned hardware and software structure. The following takes the first device as a tablet computer 200, the second device as a mobile phone 210, and the calling intention as a photo taking intention as an example, and further describes the cross-device application calling method provided in the embodiment of the present application in detail in combination with the accompanying drawings.

[0129] See also Figure 5 , Figure 5 An interactive signaling diagram of a cross-device application calling method provided in an embodiment of the present application.

[0130] In the embodiment of the present application, it is assumed that the system version of the tablet computer 200 is S and the system version of the mobile phone 210 is T.

[0131] S501: In response to the user triggering the selection of the mobile phone 210 to take a photo in the notebook application, the notebook application sends a first photo-taking intention to the distributed application framework.

[0132] When the user uses the notebook application to perform text editing operations in the tablet computer 200, the display of the tablet computer 200 may display the following Figure 2 The interface shown in the figure. The interface may include the text edited by the user and various controls, such as: "File", "Start", "Insert", "Design", "Page Layout", "Quote", "Mail", "Review", "View", and "Cover", "Blank Page", "Pagination", "Table" and "Picture" under "Insert". If the user wants to insert a picture during the text editing process, he can directly click the "Picture" 201 control to display the following. Figure 6 The interface shown.

[0133] If there are multiple electronic devices connected to the tablet computer at the same time, when the user triggers the application interaction instruction, the tablet computer displays a device selection interface including multiple electronic devices connected to it, and responds to the user's operation of selecting a picture source in the device selection interface, such as selecting mobile phone 210, and taking mobile phone 210 as the electronic device receiving the intent, the tablet computer 200 sends the intent to mobile phone 210. For example, the tablet computer 200 displays as follows Figure 6The device selection interface shown in the figure displays the image source, including the local gallery and the electronic devices connected to the tablet computer, such as the mobile phone 210 and the smart watch. The user can select an electronic device as the electronic device receiving the intent on the device selection interface. When the user chooses to obtain the image through the mobile phone 210, the notebook application will send a first photo taking intent to the distributed application framework, and the first photo taking intent is used to instruct the mobile phone 210 to call the camera application to take a photo.

[0134] It is understandable that the tablet computer 200 and the mobile phone 210 should be able to establish a connection through a wireless local area network, a Bluetooth network or a peer-to-peer (P2P) network to transfer data to each other. The tablet computer 200 and the mobile phone 210 can establish a connection and transfer data through a wireless local area network or a mobile communication network. In addition, the tablet computer 200 and the mobile phone 210 are connected in advance through authorization or verification, or they are different electronic devices belonging to the same user, for example, the user accounts logged in to the tablet computer 200 and the mobile phone 210 are both Account a, belongs to the same account device.

[0135] S502: After receiving the first photographing intention sent by the notebook application, the distributed application framework sends the first photographing intention to the class adapter.

[0136] Since the system version of the tablet computer 200 is S, the first photographing intention is an intention under the S system version, while the system version of the mobile phone 210 is T. In other words, even if the first photographing intention is directly transmitted to the mobile phone 210, the mobile phone 210 cannot correctly recognize the first photographing intention. Therefore, after receiving the first photographing intention, the distributed application framework will not directly transmit the first photographing intention to the mobile phone 210, but will first send it to the class adapter, which will convert the first photographing intention.

[0137] S503: After receiving the first photographing intent, the class adapter converts the first photographing intent into a third photographing intent, and returns the third photographing intent to the distributed application framework.

[0138] In an embodiment of the present application, the class adapter in the device application framework layer can be subdivided into intent class adapters and additional parameter class adapters. Among them, the intent class adapter is used to convert intents, and the additional parameter class adapter is used to convert additional parameters. It should be noted that in the cross-device application calling method provided in the present application, the intent class adapter is crucial and is the key to converting intents. For the additional parameter class adapter, in some application scenarios, the additional parameters in the intent may be empty, so there is no need to use the additional parameter class adapter. Therefore, the presence or absence of the additional parameter class adapter does not affect the implementation of the cross-device calling method provided in the present application.

[0139] In the embodiment of the present application, two conversion methods are provided. The first method: only using the intent class adapter for conversion; the second method: using the intent class adapter and the additional parameter class adapter for conversion. The following mainly introduces the implementation process of the second conversion method. The implementation process of the first conversion method can refer to the relevant content of the intent class adapter in the second conversion method.

[0140] The class adapter can realize the mutual conversion of parameters under the electronic device system version and the general system version. For example, in the embodiment of the present application, the system version of the tablet computer 200 is S, and the class adapter of the tablet computer 200 can convert the intent of the S system version into the intent of the general system version, and can also convert the intent of the general system version into the intent of the S system version.

[0141] The following describes in detail the process of converting the first photographing intention by the class adapter in conjunction with the accompanying drawings. Figure 7 As shown, the first photographing intent includes Action, Data, Flags, Package, Component, Category, ClipData and Extras, wherein Extras is an additional parameter, and in this embodiment, the additional parameter is Bundle.

[0142] When the class adapter receives the intent, the intent class adapter selects stable and necessary parameters from the intent, that is, the parameters that the electronic device system can edit and control, and the parameters that are essential for completing cross-device application calls, such as Action, Data, Flags, Package, Component, and Extras. For unstable or unnecessary parameters such as Category and ClipData, even if these parameters are converted and transmitted to other devices, other devices cannot recognize them, and they will also occupy the resources of the class adapter and the transmission channel, so they can be discarded.

[0143] After the intent class adapter selects stable and necessary parameters, it converts and packages them. It is understandable that the parameter formats of the intents supported by devices with different system versions are different; in other words, the device can recognize the intent corresponding to the parameter format of its own system version. Therefore, it is necessary to convert the intent through the class adapter so that the receiving device can recognize the intent and perform the corresponding operation.

[0144] like Figure 7 As shown, the intent class adapter converts the parameters in the first photographing intent of the S system version into parameters of the general system version, and then packages the converted parameters to obtain the third photographing intent.

[0145] When converting the additional parameters in the first photographing intent, the conversion can be performed through the additional parameter class adapter. The principle is the same as that of the intent class adapter. The additional parameter class adapter selects stable and necessary parameters from the additional parameters and converts them. In the embodiment of the present application, the additional parameters are set to Bundle, such as Figure 8 As shown, the additional parameters in the first photo intent are the first additional parameters (Bundle), including STRING, INTEGER, MAP, SHORT, LONG, FLOAT, DOUBLE, BOOLEAN, LIST, SPARSEARRAY, BYTEARRAY, INTARRAY, LONGARRAY, DOUBLEARRAY, PARCELABLE, and SIZE. Among them, stable and required parameters include STRING, INTEGER, MAP, SHORT, LONG, FLOAT, DOUBLE, BOOLEAN, LIST, SPARSEARRAY, BYTEARRAY, INTARRAY, LONGARRAY, DOUBLEARRAY, and BOOLEAN. The data in PARCELABLE are all custom parameters, which are unstable and can be discarded; SIZE is dispensable for the process of implementing cross-device application calls, so it can be discarded.

[0146] After the additional parameter class adapter selects the stable and necessary parameters, it converts them to obtain the third additional parameters, that is, the additional parameters in the third photographing intent. Figure 8 As shown, the additional parameter class adapter converts the parameters in the first additional parameter of the S system version into the third additional parameter of the universal system version.

[0147] After the first photographing intent is converted into the third photographing intent through the class adapter, the third photographing intent is sent to the distributed application framework so that the tablet computer 200 transmits the second photographing intent to the mobile phone 210 .

[0148] It is understandable that the above-mentioned method of first using the intent class adapter and the additional parameter class adapter to screen and then convert is the preferred solution provided by the embodiment of the present application. Compared with the method of directly using the intent class adapter and the additional parameter class adapter for conversion, the conversion speed is faster and takes up less resources. However, without performing the screening step, directly using the intent class adapter and the additional parameter class adapter for conversion can also achieve the conversion of the intent.

[0149] S504: The tablet computer 200 transmits the third photographing intention to the mobile phone 210 through the distributed application framework.

[0150] For example, the tablet computer 200 and the mobile phone 210 may transmit the third photographing intention via RPC (Remote Procedure Call). The call between the two devices is implemented via a near-field or far-field link, and the RPC spans the transport layer and the application layer.

[0151] In some embodiments, the tablet computer 200 and the mobile phone 210 are in a two-way transmission process. After receiving the third photo taking intention and completing the photo taking intention, the mobile phone 210 transmits the photo taking completion intention to the tablet computer 200 in the same way to notify the tablet computer 200 that the photo taking is completed.

[0152] The embodiment of the present application does not limit the transmission method between the tablet computer 200 and the mobile phone 210, as long as the intended transmission can be achieved.

[0153] S505: The mobile phone 210 receives the third photographing intention through the distributed application framework, and sends the third photographing intention to the class adapter for conversion.

[0154] The system version of the mobile phone 210 is T, and the third photographing intent is in the format of the general system version. The intent in the format of the general system version does not necessarily mean that it can be directly and correctly recognized by the mobile phone 210 with the system version T. The class adapter of the mobile phone 210 can also realize the intent conversion: after the mobile phone 210 receives the third photographing intent transmitted by the tablet computer 200 through the transmission layer of the distributed application framework, the third photographing intent is sent to the class adapter for conversion, and converted into a photographing intent that can be recognized by the mobile phone 210 with the system version T.

[0155] S506: After receiving the third photographing intent, the class adapter converts the third photographing intent into a second photographing intent, and returns the second photographing intent to the distributed application framework.

[0156] The principle of the class adapter in the tablet computer 200 is the same as that of the class adapter in the mobile phone 210, which also includes an intent class adapter and an additional parameter class adapter. In addition, the mutual conversion of parameters under the electronic device system version and the general system version can also be realized. Exemplarily, if the system version of the mobile phone 210 is T, the class adapter can convert the intent of the T system version into the intent of the general system version, and can also convert the intent of the general system version into the intent of the T system version.

[0157] Combine the following Figure 7 and Figure 8 This section describes in detail the process of class adapter converting the third-party camera intent.

[0158] like Figure 7As shown, the third photo intent includes Action, Data, Flags, Package, Component and Extras (Bundle in the embodiment of the present application). These parameters can be converted through the intent class adapter to obtain parameters that can be recognized by the mobile phone 210 of the T system version. Figure 7 The second photographing intent shown also includes other parameters, such as Category, ClipData and OriginalIntent (original intent information). These three parameters are of the same nature as the parameters discarded in the first photographing intent, and are unstable or unnecessary parameters. Therefore, they are discarded when converting using the intent class adapter.

[0159] Similarly, the additional parameter class adapter of the mobile phone 210 converts the additional parameters. Figure 8 As shown, STRING, INTEGER, MAP, SHORT, LONG, FLOAT, DOUBLE, BOOLEAN, LIST, SPARSEARRAY, BYTEARRAY, INTARRAY, LONGARRAY, DOUBLEARRAY and BOOLEAN are converted into parameters that can be recognized by the mobile phone 210 of the T system version, that is, the third additional parameter is converted into the second additional parameter. Figure 8 The second additional parameter shown also includes PARCELABLE, SIZE and SIZEF. The reasons why PARCELABLE and SIZE are discarded are the same as those described above and will not be repeated here. SIZEF is a parameter specific to the T system version. Even if the parameter is converted, it cannot be recognized when it is transferred to the S system version tablet computer 200, so it is discarded.

[0160] After the third photographing intent is converted into the second photographing intent through the class adapter, the second photographing intent is sent to the distributed application framework.

[0161] It is understandable that the first photographing intention, the second photographing intention and the third photographing intention may all indicate calling the camera application of the mobile phone 210 to take a photo.

[0162] S507: The distributed application framework receives and identifies the second photographing intention, and then calls the camera application of the mobile phone 210 to complete the photographing operation.

[0163] After receiving the second photographing intention, the distributed application framework identifies the second photographing intention. By identifying the second photographing intention, it is possible to determine the application that the tablet computer 200 wants to call and the operation that it wants to perform. That is, the camera application in the mobile phone 210 is called and a photograph is taken. Further, the distributed application framework calls the camera application in the mobile phone 210 and takes a photograph to obtain a picture.

[0164] Through the above steps S501-S507, it is possible to implement application calls between two devices with different system versions. In some scenarios, the electronic device that issues the call intention cannot determine whether the electronic device that receives the call intention successfully completes the application call. For example: after the tablet 200 sends the third photo-taking intention to the mobile phone 210, it is not clear whether the mobile phone 210 calls the camera application to complete the photo-taking, and the call result cannot be obtained, and the user cannot proceed to the next step according to the call result.

[0165] Regarding the above Figure 2 The scenario described by Fig. 9 The process of feeding back the completion intention of taking a photo to the tablet computer 200 after the mobile phone 210 completes the camera call is further introduced. Fig. 9 For a signaling interaction diagram of a cross-device application calling method, see Fig. 9 In some embodiments, after the mobile phone 210 calls the camera to complete the photo shooting, it feeds back the intention of completing the photo shooting to the tablet computer 200, notifying the tablet computer 200 that the photo shooting has been completed. After the above steps S501-S507, the following may also be included:

[0166] S901: In response to completing a photo-taking action, the camera application sends a first photo-taking completion intent to the distributed application framework.

[0167] like Fig.10 In the display interface of the mobile phone 210 shown, the user can take a photo by triggering the photo control 1101 in the display interface, or by triggering the button 390. After the photo is taken, the camera application sends a first photo completion intent to the distributed application framework.

[0168] S902: After receiving the first photographing completion intent sent by the camera application, the distributed application framework sends the first photographing completion intent to the class adapter.

[0169] Similar to step S502, the system version corresponding to the first photographing completion intent is T. The first photographing completion intent is directly transmitted to the tablet computer 200, and the tablet computer 200 cannot correctly recognize the first photographing completion intent. Therefore, the first photographing completion intent needs to be converted by the class adapter of the mobile phone 210.

[0170] S903: After receiving the first photographing completion intent, the class adapter converts the first photographing completion intent into a third photographing completion intent, and returns the third photographing completion intent to the distributed application framework.

[0171] The process of step S903 is opposite to the process of step S503. Figure 7 and Figure 8 , step 503 describes Figure 7 and Figure 8 The process from left to right in the figure is the process from the tablet computer 200 to the mobile phone 210; the process described in step 1003 is Figure 7 and Figure 8 The process from right to left in the figure is the process of completing the intention of taking a photo from the mobile phone 210 to the tablet computer 200.

[0172] The principle of step S903 is the same as that of step S503 and will not be described in detail.

[0173] S904: The mobile phone 210 transmits the third photo-taking completion intention to the tablet computer 200 through the distributed application framework.

[0174] S905: The tablet computer 200 receives the third photographing completion intent through the distributed application framework, and sends the third photographing completion intent to the class adapter for conversion.

[0175] S906: After receiving the third photographing completion intent, the class adapter converts the third photographing completion intent into a second photographing completion intent, and returns the second photographing completion intent to the distributed application framework.

[0176] S907: The distributed application framework receives and identifies the second photo-taking completion intention, and then informs the notebook application that the photo-taking is completed.

[0177] The implementation process of steps S904-S907 refers to steps S504-S507.

[0178] It is understandable that in the above embodiment, the class adapters of the tablet computer 200 and the mobile phone 210 only need to store the conversion method between the parameters of the system version of the device and the parameters of the general system version. As for the conversion method between the parameters of the system version of other devices and the parameters of the general system version, and the conversion method between the parameters of the system version of the device and the parameters of the system version of other devices, in order to save the storage space of the device, it can be chosen not to store them, or to store them before they are needed.

[0179] In the above steps S501-S507 and steps S901-S907, the tablet computer 200 and the mobile phone 210 realize the interaction between the two devices across system versions by transmitting intents. No other data, such as pictures, is transmitted. The reason is that the amount of data of the picture is large, which requires higher transmission resources, and the transmission speed is slower than the transmission speed of the intent. If the picture and the intent are transmitted at the same time, the problem of untimely feedback may occur. For example, if only the intent is transmitted, the tablet computer 200 may receive the photo completion intent fed back by the mobile phone 210 within 1 millisecond; if the picture and the intent are packaged and transmitted, the tablet computer 200 may not receive the photo completion intent fed back by the mobile phone 210 until 50 milliseconds.

[0180] To address this problem, in some embodiments, the intent and the image can be transmitted separately, so that the tablet computer 200 can receive the intent first and then the image, without bundling the intent and the image, so that the tablet computer 200 can receive feedback from the mobile phone 210 in a timely manner. It is understandable that for images, there may also be a problem of being unable to recognize across system versions. In this case, it is still necessary to use a class adapter for conversion. The specific conversion process is the same as the conversion process for intents. Please refer to the introduction above, and it will not be repeated in the embodiments of this application.

[0181] In some embodiments, the tablet computer 200 can also obtain pictures by creating a virtual folder in the mobile phone 210 without transmitting the pictures. The specific implementation method includes: the tablet computer 200 selects a local folder and writes the path of the local folder into the first photo-taking intention; the mobile phone 210 can obtain this path by recognizing the second photo-taking intention, and then creates a virtual folder corresponding to the local folder in the tablet computer 200 in the mobile phone 210 according to this path. The data of the virtual folder and the local folder are updated synchronously. That is to say, when the camera application in the mobile phone 210 completes taking pictures, the picture is stored in the virtual folder, and correspondingly, the local folder in the tablet computer 200 will also be updated with this picture. The notebook application can directly obtain pictures from the local folder without transferring pictures between the tablet computer 200 and the mobile phone 210, which not only saves transmission resources, but also prevents the leakage of pictures during the transmission process, thereby improving the security of data.

[0182] It is understandable that the cross-device application calling method provided by the present application can be applied not only to the scenario where the system versions of the two electronic devices are inconsistent, but also to the scenario where the system versions of the two electronic devices are consistent. Exemplarily, it is assumed that the system versions of the tablet computer 200 and the mobile phone 210 are both S. The class adapter in the tablet computer 200 can convert the first photographing intention of the S system version into the third photographing intention of the universal system version, so that the tablet computer 200 transmits the third photographing intention to the mobile phone 210. After receiving the third photographing intention, the mobile phone 210 converts the third photographing intention of the universal system version into the second photographing intention of the S system version through the class adapter in the mobile phone 210, so that the mobile phone 210 recognizes the second photographing intention and then calls the camera application to complete the photographing. Among them, the first photographing intention and the second photographing intention are essentially the same, both of which are photographing intentions of the S system version, and the difference lies in the different acquisition methods or generation methods. The first photographing intention is generated by the notebook application in the tablet 200, and the second photographing intention is obtained by converting the third photographing intention by the class adapter in the mobile phone 210.

[0183] In the above, an implementation method is introduced, in which the class adapters in the tablet computer 200 and the mobile phone 210 perform conversion respectively, thereby realizing application calling and data transmission between the two devices with different system versions. The present application also provides several other embodiments, which can also realize application calling and data transmission between the two devices with different system versions. Figure 6 The scenario shown in the figure is taken as an example and described in detail with reference to the accompanying drawings.

[0184] It should be noted that the tablet computer 200 sends the intention to take a photo to the mobile phone 210, and the mobile phone 210 sends the intention to complete the photo taking to the tablet computer 200 in the same principle. To make the description more concise, only the first part, in which the tablet computer 200 sends the intention to take a photo to the mobile phone 210, is introduced as an example. For the second part of the process, the implementation process of the mobile phone 210 sending the intention to complete the photo taking to the tablet computer 200 can refer to the description of the first part.

[0185] In some embodiments, Figure 2 The scene shown, such as Fig.11 As shown, the class adapter in the tablet computer 200 can directly convert the first photographing intention into the second photographing intention, and the mobile phone 210 can directly receive and identify the second photographing intention.

[0186] It is understandable that the tablet computer 200 and the mobile phone 210 have been pre-established to achieve near field communication or far field communication. Through the pre-established connection relationship between the tablet computer 200 and the mobile phone 210, the tablet computer 200 can know in advance that the system version of the mobile phone 210 is T. The way in which the tablet computer 200 and the mobile phone 210 establish a connection has been described above and will not be repeated here.

[0187] S1101: The tablet computer 200 converts the first photographing intention into the second photographing intention according to the system version of the mobile phone 210.

[0188] In an embodiment of the present application, a class adapter can realize the mutual conversion of parameters under various system versions of electronic devices. Exemplarily, the system version of the tablet computer 200 is S, and the system version of the mobile phone 210 is T. The class adapter can convert the intent generated by the device of the S system version into an intent that can be directly recognized by the T system version. The tablet computer 200 has established a connection with the mobile phone 210 and has learned that the system version of the mobile phone 210 is T. Therefore, the conversion method from the intent of the S system version to the intent of the T system version can be directly determined through the class adapter in the tablet computer 200, and then the first photo intent can be directly converted into the second photo intent.

[0189] S1102: The tablet computer 200 transmits a second photo-taking intention to the mobile phone 210.

[0190] After converting the first photographing intention into the second photographing intention, the tablet computer 200 may transmit the second photographing intention to the mobile phone 210 through a pre-established connection, so that the mobile phone 210 calls the camera to take a photo according to the second photographing intention.

[0191] S1103: After receiving the second photographing intention, the mobile phone 210 identifies the second photographing intention through the distributed application framework and calls the camera application to complete the photographing.

[0192] The second photographing intent is an intent under the T system version. Therefore, after receiving the second photographing intent, the mobile phone 210 does not need to use a class adapter for conversion, but can directly identify the second photographing intent through the distributed application framework, determine that the called application is a camera application, and the operation performed is photographing. The distributed application framework calls the camera application and takes a photo.

[0193] It is understandable that the implementation process of the mobile phone 210 sending the photographing completion intent to the tablet computer 200 is the same as the principle of the above process. When the mobile phone 210 completes photographing, the class adapter in the mobile phone 210 converts the first photographing completion intent into the second photographing completion intent, and the tablet computer 200 does not need to perform the conversion process.

[0194] Through the cross-device application calling method described in steps S1101-S1103, through the pre-established connection relationship, the first device (tablet computer 200) can know the system version of the second device (mobile phone 210) in advance, and only one conversion is required in the first device (tablet computer 200) to realize the application call between the two devices across system versions, thereby reducing the number of conversions using class adapters, reducing the time required for interaction between the two devices, and improving the response speed of the devices.

[0195] In an embodiment of the present application, the class adapter in the sending device converts the intent, and the receiving device is responsible for receiving and identifying the intent, calling the target application indicated by the intent according to the intent, and executing the operation indicated by the intent.

[0196] In the above embodiment, the first device (tablet computer 200) converts the first calling intention (first photographing intention) into the second calling intention (second photographing intention). Fig.12 As shown, the first calling intention (first photographing intention) can be converted into the second calling intention (second photographing intention) by the second device (mobile phone 210), and no conversion process is required on the first device (tablet computer 200).

[0197] It is understandable that the tablet computer 200 and the mobile phone 210 have been pre-established to achieve near field communication or far field communication. Through the pre-established connection relationship between the tablet computer 200 and the mobile phone 210, the mobile phone 210 can know that the system version of the tablet computer 200 is S. The way in which the tablet computer 200 and the mobile phone 210 establish a connection has been described above and will not be repeated here.

[0198] S1201: The tablet computer 200 transmits a first photographing intention to the mobile phone 210 .

[0199] S1202: The mobile phone 210 converts the first photographing intention into the second photographing intention according to the system version of the tablet computer 200.

[0200] S1203: The distributed application framework in the mobile phone 210 calls the camera application according to the second photographing intention to complete photographing.

[0201] In steps S1201-S1203, the class adapter in the mobile phone 210 performs the conversion process, and the tablet computer 200 only needs to send the first photo-taking intention to the mobile phone 210. Through the pre-established connection relationship between the mobile phone 210 and the tablet computer 200, the mobile phone 210 can know in advance that the system version of the tablet computer 200 is S. The class adapter in the mobile phone 210 determines the conversion method of converting the intent of the T system version to the intent of the S system version, and converts the first photo-taking intention into the second photo-taking intention. Then, the distributed application framework in the mobile phone 210 identifies the second photo-taking intention, and calls the camera application to complete the photo-taking.

[0202] It is understandable that the implementation process of the mobile phone 210 sending the photographing completion intent to the tablet computer 200 is the same as the principle of the above process. When the mobile phone 210 completes photographing, it sends the first photographing completion intent to the tablet computer 200, and the class adapter in the tablet computer 200 converts the first photographing completion intent into the second photographing completion intent, and the mobile phone 210 does not need to perform the conversion process.

[0203] In an embodiment of the present application, the class adapter in the receiving device converts the intent, and the sending device is responsible for sending the intent to the receiving device.

[0204] In some embodiments, Figure 2Take the scenario shown as an example. In the process of the tablet computer 200 calling the camera application of the mobile phone 210, the class adapter in the tablet computer 200 can convert the first photographing intention into the second photographing intention before the tablet computer 200 sends the photographing intention; or the class adapter in the mobile phone 210 can convert the first photographing intention into the second photographing intention after the mobile phone 210 receives the photographing intention. In the process of the mobile phone 210 feeding back the completion of photographing to the tablet computer 200, the class adapter in the tablet computer 200 can convert the first photographing completion intention into the second photographing completion intention after the tablet computer 200 receives the photographing completion intention; or the class adapter in the mobile phone 210 can convert the first photographing completion intention into the second photographing completion intention before the mobile phone 210 sends the photographing completion intention.

[0205] In the above-described embodiment, it is necessary to configure a class adapter in the first device (tablet computer 200) and / or the second device (mobile phone 210) to convert the intent. For electronic devices, storage space and computing power are very limited, and configuring a class adapter to convert the intent will occupy a certain amount of storage space and computing resources.

[0206] To address this problem, in some embodiments, Fig.13 As shown, the class adapter can be configured in other third-party devices (such as server 1300, router) except the first device (tablet computer 200) and the second device (mobile phone 210), and the third-party device (server 1300) converts and forwards the intent. In the following, the third-party device is server 1300, the first device is tablet computer 200, and the second device is mobile phone 210 for description.

[0207] It is understandable that the server 1300 has pre-established a connection with the tablet computer 200 and the mobile phone 210, and is in the same communication environment, and can achieve near field communication or far field communication. Through the pre-established connection relationship, the server 1300 can know that the system version of the tablet computer 200 is S and the system version of the mobile phone 210 is T. The way to establish a connection between electronic devices has been described in detail above. It will not be repeated here.

[0208] S1301: The tablet computer 200 transmits a first photographing intention to the server 1300 .

[0209] S1302: The server 1300 converts the first photographing intention into a second photographing intention.

[0210] S1303: The server 1300 transmits the second photo-taking intention to the mobile phone 210.

[0211] S1304: The mobile phone 210 receives and identifies the second photographing intention, and calls the camera application to complete the photographing.

[0212] In steps S1301-S1304, the class adapter in the server 1300 converts the intent, and the tablet computer 200 and the mobile phone 210 are responsible for sending and receiving the photographing intent. Through the pre-established connection relationship, the server 1300 can know the system versions of the tablet computer 200 and the mobile phone 210 in advance. The conversion method of converting the intent of the system version of the tablet computer 200 to the intent of the system version of the mobile phone 210 is determined by the class adapter in the server 1300, and the first photographing intent is converted into the second photographing intent in the server 1300. It can be understood that the class adapter in the server 1300 can realize the mutual conversion between parameters under various system versions of electronic devices. There is no need to configure the class adapter in the tablet computer 200, and the first photographing intent can be transmitted to the server 1300 through the distributed application framework; there is no need to configure the class adapter in the mobile phone 210, and it is only necessary to receive and identify the second photographing intent through the distributed application framework, and call the camera application to complete the photographing.

[0213] Configuring the class adapter in the server 1300 can save storage space and computing resources of the tablet computer 200 and the mobile phone 210. It can also utilize the stronger computing power of the server 1300 to convert the photo-taking intention more quickly through the class adapter, thereby increasing the speed of calling applications between the two devices across system versions.

[0214] It is understandable that the above steps S1301-S1304 introduce the process of the tablet computer 200 calling the camera application in the mobile phone 210. Correspondingly, the process of the mobile phone 210 feeding back the intention of completing the photo shooting to the tablet computer 200 after completing the photo shooting can refer to steps S1301-S1304. Specifically, after completing the photo shooting, the mobile phone 210 transmits the first photo shooting completion intention to the server 1300; the class adapter in the server 1300 converts the first photo shooting intention into the second photo shooting intention that the tablet computer 200 can recognize, and the server 1300 transmits the second photo shooting completion intention to the tablet computer 200; after receiving the second photo shooting intention, the tablet computer 200 learns that the mobile phone 210 has completed the photo shooting and can insert the picture in the notebook application.

[0215] In some embodiments, the photographing intention may be converted using a class adapter between the tablet computer 200 and the server 1300, or may be converted using a class adapter between the mobile phone 210 and the server 1300. Fig.14 and Fig.15 These two implementation methods are introduced.

[0216] See also Fig.14 , Fig.14 The fifth schematic diagram of cross-device application calling provided in an embodiment of the present application.

[0217] S1401: The tablet computer 200 converts the first photographing intent into a third photographing intent through a class adapter.

[0218] S1402: The tablet computer 200 transmits a third photographing intention to the server 1300 .

[0219] S1403: The server 1300 converts the third photographing intent into the second photographing intent through the class adapter.

[0220] S1404: The server 1300 transmits the second photo-taking intention to the mobile phone 210.

[0221] S1405: The mobile phone 210 receives and identifies the second photographing intention, and calls the camera application to complete the photographing.

[0222] In the embodiment of the present application, the tablet computer 200 and the server 1300 jointly realize the conversion of the photographing intention. The tablet computer 200 converts the first photographing intention that the tablet computer 200 can recognize into the third photographing intention of the general system version, and transmits the third photographing intention to the server 1300. Through the pre-established connection relationship, the server 1300 can know the system version of the mobile phone 210. When the server 1300 receives the third photographing intention, it queries the class adapter for the method of converting the intention from the general system version to the system version of the mobile phone 210, converts the third photographing intention into the second photographing intention that the mobile phone 210 can recognize, and transmits the second photographing intention to the mobile phone 210. After receiving the second photographing intention through the distributed application framework, the mobile phone 210 does not need to convert it through the class adapter, and can directly recognize the second photographing intention, determine that the target application indicated by the second photographing intention is the camera application, and the indicated operation is taking a photo. The mobile phone 210 calls the camera application to complete the photo taking.

[0223] See also Fig.15 , Fig.15 The sixth schematic diagram of cross-device application calling provided in an embodiment of the present application.

[0224] S1501: The tablet computer 200 transmits a first photographing intention to the server 1300 .

[0225] S1502: The server 1300 converts the first photographing intent into a third photographing intent through a class adapter.

[0226] S1503: The server 1300 transmits the third photo-taking intention to the mobile phone 210.

[0227] S1504: The mobile phone 210 converts the third photographing intent into a third photographing intent through the class adapter.

[0228] S1505: The mobile phone 210 identifies the second photographing intention and calls the camera application to complete the photographing.

[0229] In the embodiment of the present application, the conversion of the photographing intention is jointly realized by the mobile phone 210 and the server 1300. The tablet computer 200 does not convert the first photographing intention, but directly transmits the first photographing intention to the server 1300 through the pre-established connection relationship. Through the pre-established connection relationship, the server 1300 can not only transmit various data with the tablet computer 200 and the mobile phone 210, but also learn the system version of the tablet computer 200. After receiving the first photographing intention, the server 1300 converts the first photographing intention of the system version of the tablet computer 200 into the third photographing intention of the universal system version through the class adapter, and transmits the third photographing intention to the mobile phone 210. After the mobile phone 210 receives the third photographing intention through the distributed application framework, it is unable to recognize the third photographing intention, and needs to convert the third photographing intention into the second photographing intention that the mobile phone 210 can recognize through the class adapter. The distributed application framework obtains the second photographing intention converted by the class adapter, recognizes the second photographing intention, and calls the camera application to complete the photographing.

[0230] The present application also provides an electronic device, which may include: a memory and one or more processors. The memory and the processor are coupled. The memory is used to store computer program code, and the computer program code includes computer instructions. When the processor executes the computer instructions, the electronic device can execute the various functions or steps executed by the mobile phone in the above method embodiment.

[0231] The present application also provides a chip system, such as Fig.16 As shown, the chip system 1600 includes at least one processor 1601 and at least one interface circuit 1602. The processor 1601 and the interface circuit 1602 can be interconnected via a line. For example, the interface circuit 1602 can be used to receive signals from other devices (such as a memory of an electronic device). For another example, the interface circuit 1602 can be used to send signals to other devices (such as the processor 1601). Exemplarily, the interface circuit 1602 can read instructions stored in the memory and send the instructions to the processor 1601. When the instructions are executed by the processor 1601, the electronic device (such as Figure 2 The tablet computer 200 and the mobile phone 210 shown in the figure perform each step in the above embodiment. Of course, the chip system can also include other discrete devices, which are not specifically limited in the embodiment of the present application.

[0232] This embodiment further provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on an electronic device, the electronic device executes each function or step executed by the mobile phone in the above method embodiment.

[0233] This embodiment further provides a computer program product. When the computer program product is run on a computer, the computer executes each function or step executed by the mobile phone in the above method embodiment.

[0234] In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor can execute the computer-executable instructions stored in the memory so that the chip executes each function or step performed by the mobile phone in the above method embodiment.

[0235] Among them, the electronic device, communication system, computer-readable storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above and will not be repeated here.

[0236] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0237] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0238] The unit described as a separate component may or may not be physically separated, and the component shown as a unit may be one physical unit or multiple physical units, that is, it may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.

[0239] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0240] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

[0241] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present application and are not intended to limit it. Although the present application has been described in detail with reference to the preferred embodiments, a person of ordinary skill in the art should understand that the technical solution of the present application may be modified or replaced by equivalents without departing from the spirit and scope of the technical solution of the present application.

Claims

1. A cross-device application calling method, characterized in that: include: The first device obtains the first calling intention through the first type adapter; The first device is a device of a first system version, the first calling intent is an intent supported and recognized by the device of the first system version, and the first calling intent is an intent generated by the first device in response to a user triggering operation; The first calling intent is used to call a target application in a second device to perform a target action; the second device is a device of a second system version; The first device converts the first calling intention into a second calling intention by using the first type adapter; The second calling intent is an intent that the second device supports recognition.

2. The method according to claim 1, characterized in that The method further comprises: The first device filters the parameters in the first calling intent through the first type adapter and retains the target parameters; the target parameters are the parameters edited by the system in the first calling intent for calling the application; The first device converts the first calling intention into a second calling intention by using the first type adapter, including: The first device converts the target parameter through the first type adapter to obtain the second calling intention.

3. The method according to claim 1, characterized in that The first device also includes a second type of adapter; The method further comprises: The first device filters the parameters in the first calling intent through the first type adapter and retains the target parameters; the target parameters are the parameters edited by the system in the first calling intent for calling the application; the target parameters include additional parameters; The first device uses the second type adapter to filter the data in the additional parameters and retain the target additional parameters; the target additional data is the data in the additional parameters edited by the system for calling the application; The converting the first calling intention into a second calling intention by using the first type adapter includes: The first device converts the target parameters except the additional parameters according to the first type of adapter, and converts the target additional data according to the second type of adapter to obtain the second calling intent.

4. The method according to any one of claims 1 to 3, characterized in that: The converting the first calling intention into a second calling intention by using the first type adapter includes: The first device determines, in the first type adapter, a conversion method between an intent corresponding to the first system version and an intent corresponding to the second system version; the first type adapter is configured with a conversion method between an intent supported and recognized by a device of the first system version and an intent supported and recognized by devices of multiple system versions; The first device converts the first calling intent into the second calling intent according to the conversion method.

5. The method according to any one of claims 1 to 3, characterized in that: The converting the first calling intent into a second calling intent by using the class adapter includes: The first type of adapter is used to convert the first call intent into a general call intent; the general call intent is an intent that is supported and recognized by devices of the first system version and devices of the second system version; the general call intent is used to instruct the second device to convert the general call intent into a third call intent; the third call intent is an intent that is supported and recognized by the second device.

6. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: The first device obtains a second call completion intent, identifies the second call completion intent, and determines that the second device has called the target application to perform the target action; the second call intent is obtained by converting the first call completion intent through the first type of adapter; the second call completion intent is an intent supported and recognized by the device of the first system version; the first call completion intent is an intent generated by the second device of the second system version in response to completing the call to the target device to perform the target action.

7. The method according to claim 1, characterized in that The first device includes a notebook application, a first distributed application framework and a first type of adapter, the second device includes a camera application and a second distributed application framework, the first calling intent is a first photo taking intent; the first photo taking intent is used to instruct the second device to call the camera application to take a photo; The second calling intent is the second photo taking intent; Before the first device obtains the first calling intention through the first type adapter, the method further includes: In response to the user triggering an operation of calling a camera application in the second device to perform a photo-taking action, the notebook application generates a first photo-taking intention and transmits the first photo-taking intention to the first distributed application framework; The first distributed application framework receives and forwards the first photographing intention to the first type adapter; After the first device converts the first calling intention into a second calling intention by using the first type adapter, the method further includes: The first distributed application framework transmits the second photographing intention to the second distributed application framework, so that the second distributed application framework recognizes the second photographing intention and uses the second photographing intention to call the camera application to capture an image.

8. The method according to claim 7, characterized in that The second photographing intent is a general photographing intent; the general photographing intent is an intent that is supported and recognized by the device of the first system version and the device of the second system version; The second device also includes a third type adapter; The general photographing intent is obtained by the third type adapter from the second distributed application framework, converted into a third photographing intent, and returned to the second distributed application framework.

9. The method according to claim 6, characterized in that The first device includes a notebook application, a first distributed application framework, and a first type of adapter, the second device includes a camera application, a second distributed application framework, and a third type of adapter, and the first call completion intent is a first photo completion intent; The second calling completion intent is a second photographing completion intent, where the second photographing completion intent is an intent that is supported and recognized by the device of the first system version and the device of the second system version; The first device obtains the second call completion intent, including: The first distributed application framework receives a second photographing completion intent transmitted by the second distributed application framework, and forwards the second photographing completion intent to the first type adapter; The first type adapter converts the second photographing completion intent into the third photographing completion intent, and returns the third photographing completion intent to the first distributed application framework; the third photographing completion intent is used to notify the notebook application that the second device has called the camera application and completed the photographing action; the third photographing completion intent is an intent that the device of the first system version supports recognition; The first device identifies the second call completion intention, and determines that the second device has called the target application to perform the target action, including: The first distributed application framework identifies the third photographing completion intention, and notifies the notebook application that the second device has called the camera application and completed the photographing action.

10. A cross-device application calling method, characterized in that: include: The second device obtains the first calling intention through the third type adapter; The second device is a device of a second system version, and the first calling intent is used to call a target application in the second device to perform a target action; The second device converts the first calling intention into a second calling intention by using the third type adapter; The second calling intent is an intent that the second device supports recognition.

11. The cross-device application calling method according to claim 10, characterized in that: The first calling intent is an intent supported and recognized by a device of the first system version, and the first calling intent is an intent generated by the first device in response to a user triggering operation; Alternatively, the first calling intent is a general calling intent; The general call intent is an intent that is supported and recognized by devices of the first system version and devices of the second system version.

12. An electronic device, characterized in that: The electronic device includes a memory and one or more processors, the memory is coupled to the processor; wherein the memory stores computer program code, the computer program code includes computer instructions, and when the computer instructions are executed by the processor, the electronic device executes the method as described in any one of claims 1-9.

13. A communication system, characterized in that: The communication system includes a first device and a second device, wherein the first device is used to execute the cross-device application calling method described in any one of claims 1 to 9, and the second device is used to execute the cross-device application calling method described in claim 10 or 11.

14. A computer-readable storage medium, characterized in that: The method comprises computer instructions, which, when executed on an electronic device, cause the electronic device to execute the method as claimed in any one of claims 1 to 9.

15. A chip system, characterized in that: The chip system is applied to an electronic device including a processor and a memory. The chip system includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected through lines. The interface circuit is used to receive a signal from the memory of the electronic device and send the signal to the processor. The signal includes a computer instruction stored in the memory. When the processor executes the computer instruction, the electronic device executes the method as described in any one of claims 1 to 9.

Images