CN112422614A

CN112422614A - Method, apparatus, and medium for device interaction

Info

Publication number: CN112422614A
Application number: CN202010977039.4A
Authority: CN
Inventors: 胡慧锋; 李加润; 朱建华
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-06-30
Filing date: 2020-06-30
Publication date: 2021-02-26
Anticipated expiration: 2040-06-30
Also published as: WO2022002088A1; CN112422614B; CN113965581A

Abstract

Embodiments of the present disclosure provide methods, apparatuses, and media for device interaction. According to the scheme of the disclosure, the first device establishes a communication connection with the second device and acquires device information of the second device. Based on the device information, the first device determines whether it is appropriate to share application data between the first device and the second device. The first device automatically initiates transmission of the application data between the first device and the second device if it is determined to be appropriate to share the application data between the first device and the second device. In this way, device interaction of service migration from one device to another may be achieved with as little user intervention as possible through sharing of application data. In a distributed environment comprising multiple devices, the user can be provided with services using the appropriate devices, thereby enhancing the user experience. This also helps to improve the efficiency of utilization of the devices in a distributed environment.

Description

Method, apparatus, and medium for device interaction

Technical Field

Embodiments of the present disclosure relate generally to the field of device interaction, and more particularly, to a method, apparatus, and medium for device interaction.

Background

In a distributed environment comprising multiple devices, distributed co-operation between the multiple devices is an important function. With distributed collaboration, users expect to obtain information on other devices without changing locations. Meanwhile, various devices such as a mobile phone, a tablet computer, a television, a vehicle-mounted terminal (also referred to as a car machine) and the like have advantages, and a user also expects that the same function can be realized on other more convenient devices when operating a certain device. That is, a user desires to migrate a service provided by a certain device to another device, to provide the service by another device instead of the device or to provide the service by both devices at the same time. For example, after entering a vehicle, a user may desire to migrate a navigation service on a mobile phone to a vehicle machine, and continue navigation by the vehicle machine. For another example, after the user goes home, the user may desire to migrate the music being played on the mobile phone to a smart speaker at home, and the smart speaker continues to play the music.

However, current techniques for migrating between devices require user pre-configuration or triggering. In addition, after the user triggers, there is a case that the devices are not matched and cannot be migrated, which reduces the user experience and the efficiency of mutual cooperation. Therefore, how to automatically identify services that are migratable is important to perfect distributed collaboration.

Disclosure of Invention

Embodiments of the present disclosure provide a scheme for device interaction.

In a first aspect of the disclosure, a method of device interaction is provided. The method comprises the following steps: the method comprises the steps that a first device and a second device are in communication connection; the first equipment acquires the equipment information of the second equipment; based on the device information, the first device determining whether it is appropriate to share application data between the first device and the second device, the application data being used by the first device or the second device to provide a service; and if it is determined that it is appropriate to share the application data between the first device and the second device, the first device automatically initiates transmission of the application data between the first device and the second device. The "application data" described herein refers to data that an application generates and uses in order to provide a service or implement a preset function. For example, application data of a navigation application may include planned navigation routes, such as start points, end points, waypoints, and the like. As another example, application data for an audio playback application can include a playlist indicating one or more audios to play.

In this way, migration of services from one device to another may be automatically achieved with as little user intervention as possible through sharing of application data. In a distributed environment comprising multiple devices, the user can be provided with services using the appropriate devices, thereby enhancing the user experience. This also helps to improve the efficiency of utilization of the devices in a distributed environment.

In some embodiments, automatically initiating transmission of the application data comprises: the first device determining a likelihood that the application data will be shared; and if the likelihood exceeds a threshold, the first device automatically initiates transmission of the application data. In such an embodiment, the likelihood of sharing is predicted, and the transmission of application data is triggered only if the likelihood exceeds a threshold. In this way, more accurate service migration is facilitated.

In some embodiments, determining the likelihood that the application data is to be shared comprises: the first device acquiring use information about an application using the application data and state information of the first device; the first device obtaining a predictive model associated with the application; and said first device determining said likelihood from said predictive model using at least said usage information and said status information as inputs. In some embodiments, obtaining the predictive model comprises: the first device obtaining historical usage information related to the application, historical state information of the first device, and historical user selections as to whether to migrate the service; and the first device training the predictive model by taking as input the historical usage information, the historical state information, and as output the historical user selection. In such embodiments, the likelihood of sharing may be more accurately predicted using a trained predictive model. Further, because historical user selections are used in model training, the determined likelihood may reflect user intent with respect to service migration. In this way, accurate service migration may be provided for a particular user.

In some embodiments, automatically initiating transmission of the application data comprises: the first device automatically providing a prompt regarding whether to share the application data between the first device and the second device; the first device receiving user input for the prompt; and if the user input indicates that the application data is shared between the first device and the second device, the first device automatically initiates transmission of the application data. In such an embodiment, the user is only provided with relevant prompts if it is appropriate to share application data. In this way, situations where the user selects the migration service but the migration is unsuccessful due to the unsuitability for sharing application data between the two devices can be avoided, thereby avoiding bringing about a poor user experience.

In some embodiments, determining whether it is appropriate to share the application data between the first device and the second device comprises: in response to a first application running at the first device providing the service using the application data, the first device determining whether a device type of the second device is of a preset device type corresponding to the service; if the device type of the second device is determined to belong to the preset device type, the first device determines whether the second device has a second application of the same type as the first application; and if it is determined that the second device has the second application, the first device determines to be adapted to share the application data to the second device. In this way, in a scenario in which application data of the local device is shared with the peer device, it may be automatically determined whether the application data is suitable for sharing to the peer device.

In some embodiments, determining whether it is appropriate to share the application data between the first device and the second device comprises: in response to a third application for providing the service being enabled at the first device, the first device determining whether a device type of the second device is of a preset device type corresponding to the service; if it is determined that the device type of the second device belongs to the preset device type, the first device determines whether a fourth application of the same type as the third application at the second device is providing the service using the application data; and if it is determined that the fourth application is providing the service using the application data, the first device determines to be adapted to share the application data from the second device to the first device. In this way, in a scenario in which application data of a peer device is shared to a local device, it may be automatically determined whether the application data is suitable for sharing to the local device.

In some embodiments, the application data is used by the first device to provide a service prior to the sharing, and automatically initiating transmission of the application data comprises: the first device automatically sends the application data to the second device to enable the second device to provide the service using the application data. In this way, migration of services from the local device may be achieved through sharing of application data.

In some embodiments, the method of the first aspect further comprises: the first device stops using the application data to provide the service if it is determined that the application data was successfully transmitted. In this way, after sharing of application data is completed, the first device may be used to provide other services or be in a lock screen state to conserve power. This further helps to improve the efficiency of utilization of the devices in a distributed environment.

In some embodiments, the application data is used by the second device to provide a service prior to the sharing, and automatically initiating transmission of the application data comprises: the first device automatically sending a request for the application data to the second device; the first device receiving the application data from the second device; and the first device automatically using the application data to provide the service. In this way, migration of services to local devices may be achieved through sharing of application data.

In some embodiments, the service comprises at least one of: a navigation service, an audio playing service, a video playing service, a text editing service, a document browsing service, an audio call service, or a video call service. The scheme according to the present disclosure migrates services through sharing of application data, and thus may be applicable to migration of various services without being limited to a specific type of service.

In a second aspect of the disclosure, an apparatus for device migration is provided. The device includes: a connection establishing unit configured to establish a communication connection with a second device at a first device; an information acquisition unit configured to acquire device information of the second device; a sharing judgment unit configured to determine whether it is appropriate to share application data between the first device and the second device, the application data being used by the first device or the second device to provide a service, based on the device information; and a transmission initiating unit configured to automatically initiate transmission of the application data between the first device and the second device if it is determined that it is appropriate to share the application data between the first device and the second device.

In some embodiments, the transmission initiation unit comprises: a likelihood determination unit configured to determine a likelihood that the application data is to be shared; and a likelihood determination unit configured to automatically initiate transmission of the application data if the likelihood exceeds a threshold.

In some embodiments, the likelihood determination unit comprises: an input information acquisition unit configured to acquire use information about an application using the application data and state information of the first device; a model acquisition unit configured to acquire a prediction model associated with the application; and a model utilizing unit configured to determine the likelihood from the prediction model with at least the usage information and the state information as inputs.

In some embodiments, the model obtaining unit includes: a history information acquisition unit configured to acquire history usage information on the application, history status information of the first device, and history user selection as to whether to share the application data; and a model training unit configured to train the prediction model by taking the historical usage information, the historical state information as inputs and the historical user selection as an output.

In some embodiments, the transmission initiation unit comprises: a prompt providing unit configured to provide a prompt regarding whether to share the application data between the first device and the second device; an input receiving unit configured to receive a user input for the prompt; and an input determination unit configured to automatically initiate transmission of the application data if the user input indicates sharing of the application data between the first device and the second device.

In some embodiments, the sharing determination unit includes: a first determination unit configured to determine whether a device type of the second device belongs to a preset device type corresponding to the service in response to a first application running at the first device providing the service using the application data; a second determination unit configured to determine whether the second device has a second application of the same type as the first application if it is determined that the device type of the second device belongs to the preset device type; and a third judging unit configured to determine that it is appropriate to share the application data to the second device if it is determined that the second device has the second application.

In some embodiments, the sharing determination unit includes: a fourth determination unit configured to determine whether a device type of the second device belongs to a preset device type corresponding to the service in response to a third application for providing the service being enabled at the first device; a fifth judging unit configured to determine whether a fourth application of the same type as the third application at the second device is providing the service using the application data if it is determined that the device type of the second device belongs to the preset device type; and a sixth judging unit configured to determine that it is appropriate to share the application data from the second device to the first device if it is determined that the fourth application is using the application data.

In some embodiments, the application data is used by the first device to provide the service prior to the sharing, and the transmission initiating unit comprises: an application data transmitting unit configured to automatically transmit the application data to the second device to enable the second device to provide the service using the application data.

In some embodiments, the apparatus of the second aspect further comprises: a service stopping unit configured to stop providing the service using the application data if it is determined that the application data is successfully transmitted.

In some embodiments, the application data is used by the second device to provide the service before the sharing, and the transmission initiating unit comprises: a request transmitting unit configured to transmit a request for the application data to the second device; a data receiving unit configured to receive the application data from the second device; and a service providing unit configured to provide the service using the application data.

In some embodiments, the service comprises at least one of: a navigation service, an audio playing service, a video playing service, a text editing service, a document browsing service, an audio call service, or a video call service.

In a third aspect, an electronic device is provided. The electronic device includes: one or more processors; one or more memories; and one or more computer programs. The one or more computer programs are stored in the one or more memories, the one or more computer programs including instructions. The instructions, when executed by the electronic device, cause the electronic device to perform the method of the first aspect.

In a fourth aspect, a computer-readable storage medium is provided. The computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method of the first aspect.

It should be understood that the statements herein reciting aspects are not intended to limit the critical or essential features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. In the drawings, like or similar reference characters designate like or similar elements, and wherein:

FIG. 1 illustrates a schematic diagram of an example environment in which embodiments of the present disclosure can be implemented;

FIG. 2 shows a schematic block diagram of an example system in accordance with an embodiment of the present disclosure;

FIG. 3 illustrates a schematic architecture diagram of an example system in accordance with some embodiments of the present disclosure;

FIG. 4 shows a schematic block diagram of an emigration process in accordance with some embodiments of the present disclosure;

FIG. 5 illustrates a flow diagram of a decision process according to some embodiments of the present disclosure;

FIG. 6 illustrates a schematic block diagram of predicting user intent in accordance with some embodiments of the present disclosure;

FIG. 7 shows a schematic block diagram of an emigration process in accordance with further embodiments of the present disclosure;

fig. 8 shows a schematic block diagram of an immigration process in accordance with some embodiments of the present disclosure;

FIG. 9 illustrates a flow diagram of a decision process according to some embodiments of the present disclosure;

FIG. 10 shows a schematic block diagram of an immigration process in accordance with further embodiments of the present disclosure;

FIG. 11 shows a flowchart of an example method of device interaction, in accordance with an embodiment of the present disclosure;

FIG. 12 shows a block diagram of an example apparatus according to an embodiment of the disclosure; and

FIG. 13 illustrates a block diagram of an example device suitable for implementing embodiments of the present disclosure.

Detailed Description

The principles of the present disclosure will now be described with reference to a few exemplary embodiments. It is understood that these examples are described for illustrative purposes only and to aid those skilled in the art in understanding and enabling the present disclosure, and do not imply any limitation on the scope of the present disclosure. The disclosure described herein may be implemented in various ways other than those described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "comprising" and its variants should be read as open-ended terms, meaning "including but not limited to". The term "based on" should be read as "based at least in part on. The terms "one embodiment" and "an embodiment" should be read as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". The terms "first," "second," and the like may refer to different or the same object. Other definitions (explicit and implicit) may be included below.

As used herein, the term "service" refers to a function that a mobile device implements using visual output means, auditory output means, a combination thereof, or other suitable means. "services" may include, but are not limited to, navigation services, audio playback services, video playback services, text editing services, video call services, document browsing services, web browsing services, social media browsing and publishing services, audio call services, and so forth. The "service" may be provided by an application at the mobile device.

As used herein, the term "application data" refers to data generated and used by an application in order to provide a service or implement a preset function. For example, application data of a navigation application may include planned navigation routes, such as start points, end points, waypoints, and the like. As another example, application data for an audio playback application can include a playlist indicating one or more audios to play.

As briefly described above, current schemes for migrating services between devices require user pre-configuration or triggering, and after user triggering, there are situations where devices do not match and cannot be migrated. One common distributed migration technique is a Digital Living Network Alliance (DLNA) protocol-based scheme, hereinafter referred to as DLNA scheme. In this scheme, a series of operations such as parsing, presentation and the like of multimedia content are performed between different mobile devices through a network connection such as wireless fidelity (Wi-Fi), so that a multimedia content service can be migrated between different mobile devices. In the DLNA scheme, a local device transmits a Uniform Resource Locator (URL) of multimedia content to a target device, and the target device continues presentation of the multimedia content through the URL.

It can be seen that the DLNA scheme is based on an interconnected system, which is essentially the transmission of URLs. This limits the usage scenarios of the DLNA scheme. Generally, the DLNA scheme can support only migration of multimedia contents services providing video, audio, etc., and cannot migrate services such as memo, document editing, browser, etc., because migration of these services is not simply achieved through a URL.

Furthermore, in the DLNA scheme, after a plurality of mobile devices are networked, a user needs to click a customized option (e.g., a virtual button) in an application at a local mobile device to start migration. In addition, if the opposite-side mobile device does not support the format of the migrated multimedia content, the multimedia content service cannot be successfully migrated.

Another common distributed migration technique is the projection of a cell phone screen. For example, connecting a cell phone and a target device (e.g., a television) with a high-definition multimedia interface (HDMI) line may project the screen of the cell phone onto the target device in a completely consistent manner.

In this scheme, the triggering condition for the migration is that the two devices are connected together through an HDMI line. This requires the user to initiate proactively and does not enable automatic service migration. Furthermore, what this solution achieves is just to have the target device display the same content as the cell phone screen. Therefore, after the migration is successful, the mobile phone also needs to continue to display the related content, but cannot stand by or be used for other purposes.

To address, at least in part, the above problems, as well as other potential problems, the present application provides a solution for device interaction. In general, according to various embodiments described herein, after a first device establishes a communication connection with a second device, the first device determines whether it is appropriate to share application data between the first device and the second device based on device information of the second device. The application data is used by the first device or the second device to provide the service prior to sharing. The first device automatically initiates a transmission of the application data between the first device and the second device if it is adapted to share the application data between the first device and the second device.

The scheme according to the embodiment of the disclosure can automatically realize the device interaction of service migration from one device to another device through the sharing of application data under the condition of as little user intervention as possible. In this way, in a distributed environment including a plurality of devices, a user can be provided with a service using an appropriate device. This helps to improve the user experience and the efficiency of utilization of the devices in the distributed environment. In addition, since the migration of services is realized by the sharing of application data, the scheme is applicable to migrating various types of services, such as a navigation service, a video playing service, an audio playing service, a text editing service, a video call service, a document browsing service, and the like.

Various example embodiments of the present disclosure will be described below with reference to the accompanying drawings.

FIG. 1 illustrates a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. As shown, the example environment 100 includes a mobile device 110 (which may also be referred to herein as a first device). While the mobile device 110 is shown as a mobile telephone, it will be understood that this is merely exemplary and is not intended to limit the scope of the present disclosure. The mobile device 110 described herein may be any suitable type of device.

The example environment 100 also includes devices 120-1, 120-2, 120-3, and 120-4, which are also collectively referred to hereinafter as devices 120 (which may also be referred to herein as second devices). Device 120-1 is shown as a vehicle-mounted terminal (e.g., a car machine) mounted on vehicle 130, device 120-2 is shown as a portable computer, device 120-3 is shown as a display device (e.g., a television), and device 120-4 is shown as a speaker. It should be understood that the device 120 shown in fig. 1 is exemplary only and is not intended to limit the scope of the present disclosure. Device 120 may also include any suitable type of device, such as a set-top box, a projector, an entertainment unit, a navigation device, a communications device, a mobile phone, a tablet, a computer, a portable computer, a desktop computer, a Personal Digital Assistant (PDA), a monitor, a radio, a satellite radio, a music player, a digital music player, a portable music player, a digital video player, a Digital Video Disc (DVD) player, a portable digital video player, and so forth.

Mobile device 110 may establish a communication connection with one or more devices 120. The process of establishing a communication connection between mobile device 110 and device 120 may also be referred to as a networking process. The communication connection may be based on any suitable form, including but not limited to a wide area network (e.g., the Internet), a local area network, a private network, a public network, a packet network, a wired or wireless network (e.g., an established connection via Bluetooth, NFC, Wi-Fi, infrared, or 2G/3G/4G/5G), and so forth.

In one scenario, an application at mobile device 110 may be providing a service (e.g., a map or navigation application playing music or an audio playback application, etc.). After the mobile device 110 establishes a connection with the device 120, the user of the mobile device 110 may desire to migrate the service to the device 120, with the device 120 continuing to provide the service. Accordingly, application data at the mobile device 110 for providing the service needs to be shared to the device 120. Such a scenario may be referred to herein as an emigration scenario. For example, the mobile device 110 is carried around by the user, and a map or navigation application running in the mobile device 110 navigates according to the planned navigation route. The user may desire to continue navigating along the navigation route by device 120-1 after entering vehicle 130.

In another scenario, an application at device 120 may be providing a service. After mobile device 110 establishes a connection with device 120, the user of mobile device 110 may desire to migrate the service provided by device 120 to mobile device 110, with mobile device 110 continuing to provide the service. Accordingly, application data at device 120 for providing the service needs to be shared to mobile device 110. Such a scenario may be referred to herein as an immigration scenario. For example, device 120-4, which is placed at home, plays music in a playlist. The user may desire to continue playing the music in the list by the mobile device 110 carried around while away from home.

The migration of services from mobile device 110 to device 120 and the migration of services from device 120 to mobile device 110 may be collectively referred to as migrating services between mobile device 110 and device 120. Migration of services between mobile device 110 and device 120 may be accomplished by sharing application data between mobile device 110 and device 120. After mobile device 110 establishes a connection with device 120, mobile device 110 needs to automatically identify whether application data can be shared between mobile device 110 and device 120.

Fig. 2 shows a schematic block diagram of an example system 200 in accordance with an embodiment of the present disclosure. As shown, the example system 200 includes a mobile device 110 and a device 120. Mobile device 110 includes an identification module 210 configured to determine whether application data can be shared between mobile device 110 and device 120. In some embodiments, the identification module 210 may determine whether application data at the mobile device 110 is sharable to the device 120. In some embodiments, the identification module 210 may determine whether application data at the device 120 is sharable to the mobile device 110.

Mobile device 110 also includes a shared interface 220 that supports the transfer of application data. If the application data is used by mobile device 110 to provide a service prior to sharing, sharing interface 220 may send the application data to device 120 to enable device 120 to continue to provide the service. If the application data is used by device 120 to provide a service prior to sharing, sharing interface 220 may receive the application data from device 120 to continue providing the service at mobile device 110.

As shown, device 120 includes a shared interface 260 for interfacing with shared interface 220 to support the transfer of application data. The shared interface 260 is similar to the shared interface 220, and thus the description of the shared interface 260 is not repeated.

In some embodiments, in addition to sending and receiving application data, the shared interfaces 220 and 260 may also, in response to receiving the application data, launch an application at the respective device that may use the application data. For example, shared interfaces 220 and 260 may be Application Programming Interfaces (APIs) with the ability to launch applications. Any known or future developed technique may be used to implement shared interfaces 220 and 260, and the scope of the present disclosure is not limited in this respect.

In some embodiments, device 120 may include an identification module 250 similar to identification module 210. In such embodiments, device 120 may also implement a process of determining whether application data is shareable as described below.

Herein, sharing of application data is described from the perspective of the mobile device 110. Thus, mobile device 110 may also be referred to as a local device and device 120 may also be referred to as a peer device. Sharing application data at mobile device 110 to device 120 may be considered an emigration of application data, while sharing application data at device 120 to mobile device 110 may be considered an emigration of application data.

Fig. 3 illustrates a schematic architecture diagram of an example system 200, according to some embodiments of the present disclosure. Mobile device 110 includes an application layer 320, a system layer 310, and a kernel layer (not shown). The application layer 320 includes

applications

301, 302, and 303. These applications may provide various services to the user of mobile device 110. By way of example, the application 301 may be a map or navigation application that may display road conditions, navigation routes, and the like; the application 302 may be an audio application that may play audio content such as music, recordings, etc.; the application 303 may be a document application that may present a document for reading or editing by a user. The number of applications shown in fig. 3 is merely exemplary, and the application layer 320 may include more or fewer applications. In addition to the types of applications illustrated above, the application layer 320 may include any suitable type of application, such as a video application, a shopping application, an e-book reading application, a social application, a browser application, a video call application, a fitness application, and so forth. As shown in FIG. 3, the application layer 320 also includes an API 330 for interfacing with the system layer 310.

The system layer 310 includes the identification module 210. The recognition module 210 includes a shared recognition interface 311, an information acquisition sub-module 312, and a decision sub-module 313. The shared identification interface 311 is used to interface with the application layer 320. For example, one or more of the

applications

301, 302, 303 may register with the shared identification interface 311. The registered application may call the shared identification interface 311, thereby triggering the identification module 210 to determine whether application data for the application is shareable to the device 120, or whether the device 120 has application data shareable to the mobile device 110. Additionally, in some embodiments, the identification module 210 may also send notifications to the

applications

301, 302, 303 in the application layer 320 via the shared identification interface 311 to trigger the sharing of application data.

The information obtaining sub-module 312 may obtain the device information of the peer device (i.e., the device 120) through the established communication connection. The information acquisition sub-module 312 may also acquire and/or store device information for local devices (i.e., mobile devices 110). The device information may include various configuration information of the mobile device 110 or the device 120, including but not limited to hardware information, Operating System (OS) information, capability information, state information, or application information, etc.

Fig. 3 shows example device information 3120. Example device information 3120 includes hardware information 3121, OS information 3122, capability information 3123, status information 3124, and application information 3125. It should be understood that device information 3120 is merely exemplary. Hardware information 3121 may include device type, such as a mobile phone, a vehicle terminal, a speaker, a television, a projector, and so forth. Hardware information 3121 may additionally include information for components of the device, such as a processor, memory, and the like. The OS information 3122 may include the type of operating system installed in the device (e.g., android, iOS, Windows), its version, and so forth. The capability information 3123 may indicate whether the device has one or more capabilities, such as whether an application data sharing capability (hereinafter referred to as "sharing capability"), whether positioning is supported, whether playback of audio is supported, whether a display capability is present, and the like. Status information 3124 may indicate the current status of various hardware, capabilities of the device, such as whether connected to a network, whether location functions are enabled, etc. The application information 3125 may indicate an application installed in the device, a version of the application, whether the application is currently running, and the like.

The decision sub-module 313 is configured to determine whether application data can be shared between the mobile device 110 and the device 120 based at least on the device information 3120 of the peer device. In the migration scenario, the decision sub-module 313 may determine whether application data at the mobile device 110 may be shared to the device 120. In the immigration scenario, decision sub-module 313 may determine whether application data at device 120 may be shared to mobile device 110.

The decision sub-module 313 may determine whether it is appropriate to share application data between the mobile device 110 and the device 120 based on the device information 3120 of the correspondent device. A sharing condition indicating that it is appropriate to share application data between the mobile device 110 and the device 120 may be set in advance. If the sharing condition is satisfied, the decision sub-module 313 may determine that it is appropriate to share application data between the mobile device 110 and the device 120. If the sharing condition is not met, the decision sub-module 313 may determine that it is not appropriate to share application data between the mobile device 110 and the device 120.

In some embodiments, sharing conditions for a common policy may be defined regardless of the type of application. For example, if the device type and the OS type of the device 120 are respectively preset types and the device 120 has sharing capability, the decision sub-module 313 may determine that the sharing condition is satisfied.

In some embodiments, different sharing conditions may be defined for different services. Preset device types, preset OS types, and the like corresponding to different services may be set in advance. As an example, the preset device types corresponding to the navigation service may include mobile device types such as a mobile phone, a vehicle terminal, and the like, and non-mobile device types such as a television, a desktop computer, and the like. As another example, the preset device types corresponding to the video play service may include a device type having a display function such as a mobile phone, a television, and the like, and not include a device type having no display function such as a smart speaker and the like. The OS type may be similarly preset.

In some embodiments, the mobile device 110 may maintain one or more condition templates 314, and the decision sub-module 313 may utilize the condition templates 314 to determine whether the sharing condition is satisfied. FIG. 3 illustrates a condition template 314-1, which may be considered a specific implementation of condition template 314. Item 3141 indicates the scenario in which the template applies, in this example a "navigation emigration" scenario, i.e. sharing navigation application data at mobile device 110 to device 120. Items 3142 through 3149 indicate conditions that need to be satisfied for sharing navigation application data. Item 3142 indicates that the local device type should be "mobile phone"; item 3143 indicates that the peer device type should be "vehicle mount terminal"; item 3144 indicates that the local device should have sharing capabilities; item 3145 indicates that the peer device should have sharing capabilities; item 3146 indicates that the OS of the local device should be an "android" system; item 3147 indicates that the OS of the peer device should be an "android" system; item 3148 indicates that the local device and the peer device should be in a "connected" state; item 3149 indicates that the peer device should have the navigation application installed.

It should be understood that the various items of the condition template 314-1 shown in FIG. 3 are exemplary only, and are not intended to limit the scope of the present disclosure. Templates corresponding to different services or different types of applications may be configured. One or more of the condition templates 314 may have multiple selectable values, for example, the peer device type may be "mobile device" or "mobile phone"; as another example, the peer OS type may be "android" or "iOS". Further, condition template 314 may not include an item about the local device, e.g., may not include item 3142, item 3144, item 3146.

Additionally, in some embodiments, if it is determined that it is appropriate to share application data, the decision sub-module 313 may further determine a likelihood that the application data is to be shared, which is also referred to as a sharing likelihood. The decision sub-module 313 may identify the application data as shareable if the likelihood of sharing exceeds a threshold. The decision sub-module 313 may identify the application data as not shareable if the likelihood of sharing does not exceed a threshold. For example, the decision sub-module 313 may obtain a predictive model associated with the application and determine the likelihood of sharing based on the predictive model. The predictive model may be determined based at least in part on user habits. Thus, the sharing likelihood may reflect the likelihood that the user of the mobile device 110 wishes to share application data to migrate a service, i.e., may reflect the user's intent. In such embodiments, by determining the sharing likelihood, it may be determined whether to share the application data based on the user intent. In this way, accurate service migration can be automatically achieved without increasing interaction with the user.

In the event that it is determined that application data is to be shared, mobile device 110 automatically initiates transmission of the shared application data between mobile device 110 and device 120. For example, the mobile device 110 may automatically invoke the sharing interface 220. In some embodiments, if the decision sub-module 313 determines that the application data is shareable, the mobile device 110 may directly invoke the sharing interface 220 to automatically initiate the transfer of the application data. For example, in a migration scenario, mobile device 110 may directly call sharing interface 220 to automatically send application data to device 120. In the immigration scenario, mobile device 110 may directly invoke shared interface 220 to automatically send a request for application data to device 120.

In some embodiments, if the decision sub-module 313 determines that the application data is sharable, the mobile device 110 may provide a prompt regarding whether to share the application data and receive user input for the prompt. For example, mobile device 110 may first invoke sharing identification interface 311 to send a notification that application data is shareable to a corresponding application (e.g., application 301). The application 301 may visually or audibly provide a prompt to the user of the mobile device 110 regarding whether to share application data. If the user selects to share application data to migrate the service, the application 301 may call the sharing interface 220, for example, via the API 330, to trigger the transfer of the application data.

Similar to the mobile device 110, the device 120 includes an application layer 370, a system layer 360, and a kernel layer (not shown). The application layer 370 includes

applications

351, 352, and 353. These applications may be the same type or different types of applications as the

applications

301, 302, 303. As shown in FIG. 3, the application layer 370 also includes an API 380 for interfacing with the system layer 360.

In some embodiments, system layer 360 may include an identification module 250 similar to identification module 210. The sharing interface 361, the information obtaining sub-module 362, the decision sub-module 363 and the condition template 364 included in the recognition module 250 may be the same as the corresponding components of the recognition template 210, and thus, the description will not be repeated.

The process of sharing application data between mobile device 110 and device 120 to migrate services according to some embodiments of the present disclosure will be described in detail below in conjunction with fig. 4-10. Fig. 4 shows a schematic block diagram of an emigration process 400 in accordance with some embodiments of the present disclosure. For ease of understanding, the migration process 400 will be described in conjunction with fig. 3. As shown, the application 301 at the mobile device 110 is enabled, and the application 301 generates application data (i.e., target application data in the present embodiment) to start providing a service (i.e., target service in the present embodiment). After being enabled, the application 301 may call the shared identification interface 311 in the identification template 210 through the API 330. In the example of fig. 4, the application 301 is a map application, and provides a navigation service by displaying a navigation route 401 and a map. Accordingly, the application data of the application 301 may include planning data of the navigation route 401, such as a start point, an end point, a waypoint, and the like.

Mobile device 110 establishes a communication connection 403 with device 120. For example, a user enters a vehicle in which the device 120 is installed with the mobile device 110, and the mobile device 110 and the device 120 establish a communication connection. If it is detected that the communication connection 403 has been established, the mobile device 110 may obtain device information of the device 120. The device information may include hardware information (e.g., device type), OS information (e.g., OS type), capability information (e.g., whether sharing capability is available), state information (e.g., whether connected) and application information (e.g., installed applications) of the device 120, and the like. For example, the information acquisition sub-module 312 in the identification module 210 may acquire the device information 3120 about the device 120 as shown in fig. 3.

It should be understood that the order in which the communication connection 403 is established and the mobile device 110 begins providing the target service may not be limited in embodiments of the present disclosure. In some embodiments, the communication connection 403 between the mobile device 110 and the device 120 may be established first, and then the mobile device 110 generates application data to begin providing the target service. For example, a user may enter a vehicle in which device 120 is installed with mobile device 110, and mobile device 110 and device 120 establish a communication connection. The user may then enable the application 301 at the mobile device 110, and the application 301 generates application data to begin providing a target service, such as a navigation service.

Next, the mobile device 110 performs a decision process 410. In some embodiments, the mobile device 110 may determine whether it is appropriate to share the target application data at the mobile device 110 to the device 120, i.e., whether it is appropriate to migrate the target application data, based on the device information 3120 of the device 120. For example, the mobile device 110 may determine whether a sharing condition is satisfied.

In some embodiments, if the mobile device 110 determines that it is appropriate to migrate the target application data, the mobile device 110 may further determine a sharing likelihood. FIG. 5 illustrates a flow diagram of a decision process 410-1 according to some embodiments of the present disclosure. Decision process 410-1 may be viewed as one specific implementation of decision process 410.

At block 510, the mobile device 110 determines whether the target application data at the mobile device 110 is suitable for sharing to a peer device, i.e., device 120, based on the device information of the device 120. In some embodiments, mobile device 110 may determine whether the device type of device 120 is of a preset device type corresponding to the target service. If the device type of the device 120 does not belong to the preset device type, the mobile device 110 identifies the target application data as not suitable for sharing. If the device type of the device 120 is of the preset device type, the mobile device 110 may continue with the determination of the remaining conditions. Mobile device 110 may determine whether device 120 has the same type of application as application 301. If the devices 120 do not have the same type of application, the mobile device 110 identifies the target application data as not suitable for sharing. If the device 120 has the same type of application (e.g., application 351 is the same type as application 301), the mobile device 110 determines that it is appropriate to share the target application data to the device 120. Additionally, other conditions may also be set. For example, the mobile device 110 may also determine whether the device 120 supports sharing of target application data, a status of a function related to providing the target service (such as a status of a location function), and so on.

For the example in fig. 4 in which the target service is a navigation service, the mobile device 110 may determine whether the device type of the device 120 is a preset device type corresponding to the navigation service, for example, a mobile device type such as a vehicle-mounted terminal, a mobile phone, or the like, based on the hardware information 3121. If the device type of the device 120 is of the preset device type, the determination of other conditions may be continued. Mobile device 110 may determine whether device 120 has a mapping application or other navigation-enabled application installed based on application information 3115. If the device 120 is installed with a mapping application or other navigation-enabled application, the mobile device 110 may determine that it is appropriate to share navigation application data to the device 120. Additionally, in some embodiments, the mobile device 110 may also determine whether remaining conditions are met, such as the status of a positioning function module (such as a GPS module) used to support navigation. If the location function module is in a failed state, the mobile device 110 may identify the navigation application data as not suitable for sharing. If the location function template is in a normal state, the mobile device 110 may determine that the navigation application data is suitable for sharing to the device 120.

In some embodiments, mobile device 110 may utilize condition template 314 to determine whether it is appropriate to share the target application data. For example, the mobile device 110 may retrieve the corresponding condition template 314 and then determine, item by item, whether an item in the condition template 314 is satisfied based on the device information 3120. If the respective items are satisfied, the mobile device 110 may determine that it is appropriate to share the target application data.

If the mobile device 110 determines that it is appropriate to share the target application data, the process 410-1 proceeds to block 520. At block 520, the mobile device 110 determines a likelihood that the target application data will be shared, i.e., a sharing likelihood. The sharing likelihood described herein represents the probability that the target application data is shared to the peer device. Since migration of the target service may be achieved through sharing of the target application data, in such an embodiment, the sharing likelihood may reflect a probability that the user of mobile device 110 wishes to have the target service provided by the peer device. In some embodiments, mobile device 110 may determine the sharing likelihood based on the frequency, number of times, etc. that application data of application 301 was shared to device 102 within a past period of time (e.g., the last week, the last month, the last three months, the last half year). In some embodiments, the mobile device 110 may determine the sharing likelihood based on a predictive model. Such an embodiment will be described in detail below with reference to fig. 6.

At block 530, the mobile device 110 determines whether the sharing likelihood is greater than a threshold. If the likelihood of sharing is not greater than the threshold, mobile device 110 may determine that the target application data is not sharable and process 410-1 ends. If the sharing likelihood is greater than the threshold, the process 410-1 proceeds to block 540. At block 540, mobile device 110 determines that the target application data can be shared to the peer device, i.e., device 120.

Optionally, continuing with fig. 4. If it is determined in decision process 410 that the target application data is shareable, mobile device 110 may provide a prompt to the user regarding whether to share the application data and receive user input for the prompt. It will be appreciated that since the user of the mobile device 110 may not be aware of the sharing of application data, in embodiments of the present disclosure, a prompt may be made as to whether to share application data from the perspective of the application or the service provided by the application. Such a prompt may therefore be presented as a prompt as to whether or not the services are provided by the peer device. For example, if the decision sub-module 313 determines that the target application data is shareable, the share identification interface 311 may be invoked to notify the application 301 that the target application data is shareable. As shown, the application 301 may display a dialog box 402. Alternatively or additionally, mobile device 110 may audibly prompt the user whether the targeted service is provided by device 120 and recognize the user's voice to determine the user's selection.

If the user input indicates that the target service is provided by the peer device (i.e., device 120), e.g., the user clicks "yes" in dialog box 402, then mobile device 110 initiates sharing process 420. For example, application 301 may call sharing interface 220 to send target application data to device 120. In the navigation service example shown in fig. 4, the navigation planning data of the application 301 may be sent to the device 120.

Device 120 utilizes the received application data to provide the target service, as indicated by arrow 430. For example, sharing interface 260 of device 120 receives application data from sharing interface 220. An application 351 of the same type as the application 301 is launched and provides a target service using the application data. In the example of fig. 4, the device 120 may continue to provide navigation services using the received navigation planning data. As shown, the device 120 displays a navigation route 401 and a corresponding map on its screen.

In some embodiments, mobile device 110 may stop providing the target service if it is determined that the application data was successfully shared, as illustrated with arrow 440. For example, if it is determined that the application data was successfully transmitted, the mobile device 110 may stop using the target application data to provide the target service. For example, mobile device 110 may close application 301. Additionally, mobile device 110 may also place itself in a lock screen state. In such embodiments, mobile device 110 may be released from providing the target service after sharing of the target application data is completed. The mobile device 110 may provide other services or be in a lock screen state to conserve power. This helps to further increase the efficiency of utilization of the devices in the distributed environment.

The scheme according to the embodiment of the disclosure can automatically realize the device interaction of service migration from one device to another device through the sharing of application data under the condition of as little user intervention as possible. In this way, in a distributed environment including a plurality of devices, a user can be provided with a service using an appropriate device. For example, when a user enters a vehicle, navigation originally performed on a mobile phone may be migrated to the in-vehicle terminal, so that the in-vehicle terminal provides a navigation service. This helps to improve the user experience and the efficiency of utilization of the devices in the distributed environment.

As briefly described above with reference to fig. 5, the mobile device 110 may determine a sharing likelihood based on a predictive model. Fig. 6 illustrates a schematic block diagram 600 of determining sharing possibilities in accordance with some embodiments of the present disclosure. The mobile device 110 may first obtain information 610 for determining the sharing likelihood. Information 610 may include usage information 611 related to application 301 and status information 612 of mobile device 110. Alternatively or additionally, in some embodiments, information 610 may also include capability information 613 related to mobile device 110 and/or device 120.

Usage information 611 may include a time at which application 301 is enabled at mobile device 110, a time at which mobile device 110 establishes a communication connection with device 120, a current system time, an expected duration of time that application 301 is running (e.g., an expected total duration of navigation), a user habit associated with application 301. The user habit may be the number of times or frequency the user selects the application data of the shared application 301 over a past period of time (e.g., within one month), or the like. Status information 612 may include a power status of mobile device 110 (e.g., remaining power, whether charging is in progress, etc.), an audio status (e.g., whether audio is being output, volume level), whether functionality related to application 301 is enabled (e.g., whether GPS is on), etc. Capability information 613 may include whether mobile device 110 and/or device 120 support migration of application data, etc. In some embodiments, information 610 may additionally include status information of device 120, and the like.

The sharing likelihood may be determined from predictive model 630 using usage information 611, state information 612, and optionally capability information 613 as inputs. In particular, to apply this information to the predictive model 630, feature extraction may be performed on the collected data to obtain the feature representation X. For example, one or more of the information 610 may each be represented by a corresponding vector. The matrix of these vectors is normalized to obtain the eigenrepresentation X. The feature representation X may be input to the predictive model 630 to determine the likelihood of sharing 631. In some embodiments, the predictive model 630 may be implemented using a logistic regression algorithm. For example, the prediction model 630 may be represented by equation (1):

where e is the base of the natural logarithm, which is an infinite acyclic decimal and can take the value of 2.71828; t represents matrix transposition; θ is a parameter of logistic regression and can be obtained by training of the model; y is a dependent variable, and p represents a sharing possibility at a constant time of x and θ. As previously described, when the sharing likelihood is greater than a threshold, it may be determined that the target application data is sharable; when the likelihood of sharing is less than a threshold, the target application data may be determined to be not sharable.

In some embodiments, the predictive model 630 may be trained at the mobile device 110 using historical information about the application 301. For example, mobile device 110 may collect historical information about application 301. The historical information may include information corresponding to one or more items of information 610, such as historical usage information, historical status information, and historical capability information, respectively. The historical information also includes historical user selections as to whether to share application data to migrate the service. Such historical information may cover a past period of time, such as a half year, a year, etc.; the time since the mobile device 110 was enabled may also be covered.

In some embodiments, mobile device 110 may also update predictive model 630 with user selection 632. For example, a user's selection of "yes" or "no" in dialog box 402 may be fed back to predictive model 630 to further train predictive model 630.

In such an embodiment, by predicting the probability that the user wishes to share the application data, the user intention can be considered in the service migration, and the service migration based on the user intention can be realized. This helps to achieve more accurate service migration. In a distributed device scenario, user experience can be improved. Furthermore, in such embodiments, the predictive models used are trained on the user's habits. This may enable customized service migration for the user.

Take a navigation application as an example. Since the road is easy to jam during the early peak period, the user of the mobile device 110 needs to select a fast route, and therefore the user is used to navigate by the vehicle-mounted terminal on the way to work in the morning, so as to drive according to the fast route. Suppose that the user gets on the car at home at 8:45 am and is ready to go out to work. The mobile device 110 inputs the information 610 gathered in this case to the predictive model 630 to determine the likelihood of sharing. In this case, the resulting sharing probability will be greater than the threshold. Thus, the mobile device 110 can initiate sharing of navigation application data.

As another example, the user of mobile device 110 may be late to the next shift. Due to the fact that road conditions are good at night, the user returns home according to a fixed route every day, and therefore navigation is not needed to be conducted by the vehicle-mounted terminal on the way of returning home. Suppose that the user is ready to go home from the company at 10:45 pm. The mobile device 110 inputs the information 610 gathered in this case to the predictive model 630 to determine the likelihood of sharing. In this case, the resulting sharing probability will be less than the threshold. Thus, the mobile device 110 will not trigger the sharing of navigation application data.

In some embodiments, the predictive model 630 may be obtained by the mobile device 110 from the cloud platform 640. Such a predictive model 630 may be a big data based model, such as a model trained based on data from a large number of mobile devices 110. In the event that the usage time of the mobile device 110 is short and not enough data can be accumulated to train the predictive model, the mobile device 110 may obtain the big-data based predictive model 630 from the cloud platform 640. In such embodiments, the user selection 632 and related information at the mobile device 110 may be sent to the cloud platform 640 to enable the cloud platform 640 to optimize the big-data based model.

It should be understood that different types of applications may be associated with different prediction models, and that the same type of application may have a prediction model corresponding to an emigration scenario and a prediction model corresponding to an emigration scenario. As an example, for a navigation application, mobile device 110 and/or cloud platform 640 may maintain a predictive model corresponding to the migration out of navigation application data and a predictive model corresponding to the migration in of navigation application data.

Fig. 7 shows a schematic block diagram of an emigration process 700 according to further embodiments of the present disclosure. Only the differences between the migration process 700 and the migration process 400 are described below. As shown in fig. 7, if it is determined in decision process 410 that the target application data is shareable, mobile device 110 may automatically initiate sharing process 420 without providing a prompt regarding whether to share the application data. For example, the identification module 210 may call the sharing interface 220 to send the application data to the device 120.

In such an embodiment, interaction with the user is further reduced and automatic service migration may be achieved. Such embodiments may be implemented where the trained predictive model is capable of accurately predicting user intent (e.g., the number of times user intent is accurately predicted over a period of time exceeds a threshold). In this manner, accurate service migration may still be achieved with minimal interaction with the user.

In the embodiments described with reference to fig. 4 and 7, application data is shared from the local device to the peer device, i.e. the migration scenario. The device interaction scheme according to the embodiments of the present disclosure is also applicable to immigration scenarios. Fig. 8 illustrates a schematic block diagram of an immigration process 800 in accordance with some embodiments of the present disclosure. As shown, mobile device 110 establishes a communication connection 803 with device 120. For example, a user enters a vehicle in which device 120 is installed with mobile device 110, and mobile device 110 and device 120 establish communication connection 803. The application 351 at the device 120 is enabled, and the application 351 generates application data (i.e., target application data in the present embodiment) to start providing a service (i.e., target service in the present embodiment). In the example of fig. 8, the application 351 is a map application, and provides a navigation service by displaying a navigation route 801 and a map.

At some point, application 301 at mobile device 110 is enabled. For example, the user opens the application 301 at the mobile device 110 when intending to get off the vehicle. After being enabled, the application 301 may call the shared identification interface 311 in the identification template 210 through the API 330.

Mobile device 110 may obtain device information for device 120. The device information may include hardware information (e.g., device type), OS information (e.g., OS type), capability information (e.g., whether sharing capability is available), state information (e.g., whether connected) and application information (e.g., installed applications) of the device 120, and the like. For example, the information acquisition sub-module 312 in the identification module 210 may acquire the device information 3120 about the device 120 as shown in fig. 3.

It should be understood that in embodiments of the present disclosure, the order in which communication connection 803 is established and device 120 begins providing the target service may not be limited. In some embodiments, the communication connection 803 between the mobile device 110 and the device 120 may be established after the device 120 generates application data to begin providing the target service.

Next, mobile device 110 performs decision process 810. In some embodiments, the mobile device 110 may determine whether it is appropriate to share the target application data at the device 120 to the mobile device 110, i.e., whether it is appropriate to migrate the target application data, based on the device information 3120 of the device 120. For example, the mobile device 110 may determine whether a sharing condition is satisfied.

In some embodiments, if it is determined to be appropriate to share the target application data, the mobile device 110 may further determine a likelihood that the target application data will be shared, i.e., a sharing likelihood. FIG. 9 illustrates a flow diagram of a decision process 810-1 according to some embodiments of the present disclosure. Decision process 810-1 may be considered a specific implementation of decision process 810.

At block 910, the mobile device 110 determines whether the target application data at the device 120 is suitable for sharing to the local device, i.e., the mobile device 110, based on the device information of the device 120. In some embodiments, mobile device 110 may determine whether the device of device 120 is of a preset device type corresponding to the target service. The target application data may be identified as not suitable for sharing if the device type of the device 120 does not belong to the preset device type. If the device type of the device 120 is of the preset device type, the mobile device 110 may continue with the determination of the remaining conditions. Mobile device 110 determines whether application 351, which is of the same type as application 301 at device 120, is using the target application data to provide the target service. If the application 351 at the device 120 is not using the target application data (e.g., is not running), it may be determined that there is no sharable target application data. If the application 351 at the device 120 is providing the target service using the target application data, the mobile device 110 determines that the target application data is suitable for sharing to the mobile device 110. Additionally, other conditions may also be set. For example, mobile device 110 may also determine whether device 120 supports sharing of target application data, and so on.

For the example in fig. 8 in which the target service is a navigation service, the mobile device 110 may determine whether the device type of the device 120 is a preset device type corresponding to the navigation service, for example, a mobile device type such as a vehicle-mounted terminal, a mobile phone, or the like, based on the hardware information 3121. If the device type of the device 120 is of the preset device type, the determination of other conditions may be continued. Mobile device 110 may determine, based on application information 3215, whether a mapping application or other navigation-enabled application at device 120 is using navigation application data to provide navigation services. If a mapping application or other navigation-enabled application of device 120 is using navigation application data to provide navigation services, mobile device 110 may determine that the navigation application data at device 120 is suitable for sharing to mobile device 110. Additionally, in some embodiments, mobile device 110 may also determine whether the remaining conditions are met. For example, the mobile device 110 may determine the status of a positioning function module (such as a GPS module) that is itself used to support navigation. If the location function module is in a failed state, the mobile device 110 may identify the navigation application data as not suitable for sharing. If the location function template is in a normal state, the mobile device 110 may determine that the navigation application data is suitable for sharing to the mobile device 110.

In some embodiments, mobile device 110 may utilize condition template 314 to determine whether it is appropriate to share the target application data. For example, the mobile device 110 may retrieve the corresponding condition template 314 and then determine, item by item, whether an item in the condition template is satisfied based on the device information 3120. If the respective items are satisfied, the mobile device 110 may determine that it is appropriate to share the target application data. The mobile device 110 may maintain respective condition templates for the immigration scenario and the immigration scenario. For example, the condition template 314-1 shown in FIG. 3 is suitable for navigation emigration. Mobile device 110 may also maintain a condition template similar to condition template 314-1 that is suitable for navigation immigration. Such a condition template may include an item as to whether the peer application is running, in addition to or instead of item 3149.

If the mobile device 110 determines that it is appropriate to share the target application data, the process 810-1 proceeds to block 920. At block 920, the mobile device 110 determines a likelihood that the target application data will be shared, i.e., a sharing likelihood. The sharing likelihood described herein represents the probability that the target application data is shared to the local device. Since migration of the target service may be achieved through sharing of the target application data, in such embodiments, the sharing likelihood may reflect a probability that the user of the mobile device 110 wishes to be served by the local device. In some embodiments, the mobile device 110 may determine the sharing likelihood based on the frequency, number of times, etc. that application data of the application 351 was shared to the mobile device 110 within a past period of time (e.g., the last week, the last month, the last three months, the last half year). In some embodiments, the mobile device 110 may determine the sharing likelihood based on a predictive model. Determining the sharing likelihood based on the predictive model is similar to the embodiment described above with reference to fig. 6, and thus, will not be described again here.

At block 930, the mobile device 110 determines whether the sharing likelihood is greater than a threshold. If the likelihood of sharing is not greater than the threshold, mobile device 110 may determine that the target application data is not sharable and process 810-1 ends. If the sharing likelihood is greater than the threshold, the process 810-1 proceeds to block 940. At block 940, mobile device 110 determines that the target application data can be shared to the local device, i.e., mobile device 110.

Optionally, continuing with fig. 8. If it is determined in decision process 810 that the target application data is shareable, mobile device 110 may provide a prompt regarding whether to share the application data and receive user input for the prompt. Similar to that described above with reference to fig. 4, since the user of the mobile device 110 may not be aware of the sharing of application data, in embodiments of the present disclosure, a prompt may be made regarding whether to share application data from the perspective of the application or the service provided by the application. Such a prompt may therefore be presented as a prompt as to whether or not the service is provided by the local device. For example, if the decision sub-module 313 determines that the target application data is shareable, the share identification interface 311 may be invoked to notify the application 301 that the target application data is shareable. As shown, application 301 may display dialog box 802. Alternatively or additionally, mobile device 110 may provide a prompt by voice whether the target service is provided by mobile device 110 and recognize the voice input to determine the user's selection.

If the user input indicates that the target service is provided by the local device (i.e., mobile device 110), e.g., the user clicks "yes" in dialog box 802, then mobile device 110 initiates a sharing process 820. For example, mobile device 110 may send a request for target application data to device 120 via shared interface 220 and receive the target application data from device 120. In the example of fig. 8, mobile device 110 may receive navigation planning data generated by application 351 from device 120.

The mobile device 110 utilizes the received application data to provide the target service, as indicated by arrow 830. In the example of fig. 8, the application 301 at the mobile device 110 may continue to provide navigation services using the received navigation planning data. As shown, the mobile device 110 displays a navigation route 801 and a corresponding map on its screen.

Fig. 10 shows a schematic block diagram of an immigration process 1000 in accordance with further embodiments of the present disclosure. Only the differences between migration process 1000 and migration process 800 are described below. As shown in fig. 10, if it is determined in decision process 810 that the target application data is shareable, mobile device 110 may automatically initiate a sharing process 820 without providing a prompt to the user regarding whether to share the application data. For example, the identification module 210 may call the sharing interface 220 to send a request for target application data to the device 120.

In such an embodiment, interaction with the user is further reduced and automatic service migration may be achieved. Such embodiments may be implemented where the trained predictive model is capable of accurately predicting user intent (e.g., the number of times user intent is accurately predicted over a period of time exceeds a threshold). In this manner, automated and accurate service migration may still be achieved with minimal interaction with the user.

In the embodiment depicted in fig. 8 and 10, in response to application 301 being enabled at mobile device 110, mobile device 110 performs decision process 810 to determine whether the target application data is shareable. In still other embodiments, after mobile device 110 establishes a communication connection with device 120, mobile device 110 may perform decision process 810 without invocation of application 301 if mobile device 110 determines that an application at device 120 is running to provide a target service (e.g., a navigation service).

Fig. 11 shows a flowchart of an example method 1100 of device interaction, in accordance with an embodiment of the present disclosure. The method 1100 may be performed by a first device, such as the mobile device 110 shown in fig. 1, 2, and 3. The second device is, for example, the device 120 shown in fig. 1, 2, and 3. It is to be understood that method 1100 may also include additional acts not shown and/or may omit acts shown. The scope of the present disclosure is not limited in this respect.

At block 1105, the first device establishes a communication connection with a second device. At block 1110, a first device obtains device information for a second device. At block 1120, based on the device information, the first device determines whether it is appropriate to share application data between the first device and the second device.

In some embodiments, in response to a first application running at a first device providing a service using the application data, the first device may determine whether a device type of a second device is of a preset device type corresponding to the service. If it is determined that the device type of the second device belongs to the preset device type, the first device may determine whether the second device has a second application of the same type as the first application. The first device may determine that it is suitable to share application data from the first device to the second device if it is determined that the second device has the second application.

In some embodiments, in response to the third application for providing the service being enabled at the first device, the first device may determine whether the device type of the second device is of a preset device type corresponding to the service. If it is determined that the device type of the second device belongs to the preset device type, the first device may determine whether a fourth application of the same type as the third application at the second device is providing a service using the application data. The first device may determine that it is suitable to share the application data from the second device to the first device if it is determined that the fourth application is providing a service using the application data.

If it is determined at block 1120 that it is appropriate to share application data between the first device and the second device, the method 1100 proceeds to block 1130. At block 1130, the first device automatically initiates transmission of application data between the first device and the second device.

In some embodiments, the first device may determine a likelihood that the application data will be shared. The first device may automatically initiate transmission of the application data if the likelihood exceeds a threshold. In some embodiments, the first device may utilize a predictive model to determine a likelihood that the application data will be shared. For example, the first device may acquire use information about an application using the application data and state information of the first device. The first device may retrieve a predictive model associated with the application. The first device may determine the likelihood from the predictive model with at least the usage information and the status information as inputs. In some embodiments, the predictive model may be trained at the first device. For example, the first device may obtain historical usage information related to the application, historical state information of the first device, and historical user selections as to whether to share application data. The first device may train the predictive model by taking as input historical usage information, historical state information, and historical user selections as output.

In some embodiments, the first device may provide a prompt regarding whether to share application data between the first device and the second device. The first device may receive a user input for the prompt. The first device may automatically initiate transmission of the application data if the user input indicates that the application data is shared between the first device and the second device.

In some embodiments, the application data is used by the first device to provide the service prior to sharing. The first device may send the application data to the second device, which uses the application data to provide the service. In some embodiments, the first device may stop providing the service using the application data if it is determined that the application data was successfully transmitted.

In some embodiments, the application data is used by the second device to provide a service prior to sharing. The first device may send a request for application data to the second device. The first device may receive application data from the second device and provide a service using the application data.

In some embodiments, the service may include at least one of: a navigation service, an audio playing service, a video playing service, a text editing service, a document browsing service, an audio call service, or a video call service.

Fig. 12 shows a block diagram of an example apparatus 1200 in accordance with an embodiment of the disclosure. For example, apparatus 1200 may be used to implement mobile device 110 or a portion of mobile device 110 as shown in fig. 1, 2, and 3.

As shown in fig. 12, the apparatus 1200 includes: a connection establishing unit 1205 configured to establish a communication connection with the second device at the first device; an information acquisition unit 1210 configured to acquire device information of a second device; a sharing judgment unit 1220 configured to determine whether it is appropriate to share the application data between the first device and the second device based on the device information; and a transmission initiating unit 1230 configured to automatically initiate transmission of the application data between the first device and the second device if it is determined that it is appropriate to share the application data between the first device and the second device. For example, the information obtaining unit 1210 may be implemented as the information obtaining sub-module 312 shown in fig. 3, the sharing judging unit 1220 may be implemented as the decision sub-module 313 shown in fig. 3, and the transmission initiating unit 1230 may be implemented as the sharing interface 220 shown in fig. 2.

In some embodiments, the transmission initiation unit 1230 includes: a likelihood determination unit configured to determine a likelihood that the application data is to be shared; and a likelihood determination unit configured to automatically initiate transmission of the application data if the likelihood exceeds a threshold.

In some embodiments, the likelihood determination unit comprises: an input information acquisition unit configured to acquire use information about an application using the application data and state information of the first device; a model acquisition unit configured to acquire a prediction model associated with an application; and a model utilizing unit configured to determine the likelihood from the prediction model with at least the usage information and the state information as inputs.

In some embodiments, the model obtaining unit comprises: a history information acquisition unit configured to acquire history usage information related to an application, history status information of the first device, and history user selection as to whether to share application data; and a model training unit configured to train the prediction model by taking the historical usage information, the historical state information as inputs and the historical user selection as an output.

In some embodiments, the transmission initiation unit 1230 includes: a prompt providing unit configured to provide a prompt regarding whether to share application data between the first device and the second device; an input receiving unit configured to receive a user input for a prompt; and an input determination unit configured to automatically initiate transmission of the application data if the user input indicates sharing of the application data between the first device and the second device.

In some embodiments, the sharing determination unit 1220 includes: a first determination unit configured to determine whether a device type of a second device belongs to a preset device type corresponding to a service in response to a first application running at a first device providing the service using application data; a second determination unit configured to determine whether the second device has a second application of the same type as the first application if it is determined that the device type of the second device belongs to the preset device type; and a third judging unit configured to determine that it is appropriate to share the application data to the second device if it is determined that the second device has the second application.

In some embodiments, the sharing determination unit 1220 includes: a fourth determination unit configured to determine whether a device type of the second device belongs to a preset device type corresponding to the service in response to the third application for providing the service being enabled at the first device; a fifth judging unit configured to determine whether a fourth application of the same type as the third application at the second device is providing a service using the application data if it is determined that the device type of the second device belongs to the preset device type; and a sixth judging unit configured to determine that it is appropriate to share the application data from the second device to the first device if it is determined that the fourth application is using the application data.

In some embodiments, the application data is used by the first device to provide the service prior to sharing. The transmission initiation unit 1230 includes: an application data transmitting unit configured to automatically transmit application data to the second device to enable the second device to provide a service using the application data.

In some embodiments, the apparatus 1200 further comprises: a service stopping unit configured to stop providing a service using the application data if it is determined that the application data is successfully transmitted.

In some embodiments, the application data is used by the second device to provide the service prior to sharing. The transmission initiation unit 1230 includes: a request transmitting unit configured to transmit a request for application data to a second device; a data receiving unit configured to receive application data from a second device; and a service providing unit configured to provide a service using the application data.

It should be understood that the apparatus 1200 may correspond to the method performed by the first device in the previous embodiments. The first device is, for example, a mobile device 110 as shown in fig. 1, 2 and 3. The operations and features of the respective units in the apparatus 1200 are respectively for realizing the corresponding steps of the method performed by the first device in the foregoing embodiment, and have the same advantageous effects. For the sake of simplicity, detailed description is not repeated.

Fig. 13 illustrates a block diagram of an example device 1300 suitable for implementing embodiments of the present disclosure. For example, mobile device 110 as shown in fig. 1, 2, and 3 may be implemented by device 1300. As shown in fig. 13, device 1300 includes a Central Processing Unit (CPU)1301 that may perform various appropriate actions and processes according to computer program instructions stored in a Read Only Memory (ROM)1302 or computer program instructions loaded from a storage unit 1308 into a Random Access Memory (RAM) 1303. In the RAM 1303, various programs and data necessary for the operation of the device 1300 can also be stored. The CPU 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. An input/output (I/O) interface 1305 is also connected to bus 1304.

A number of components in the device 1300 connect to the I/O interface 1305, including: an input unit 1306 such as a keyboard, a mouse, or the like; an output unit 1307 such as various types of displays, speakers, and the like; storage unit 1308, such as a magnetic disk, optical disk, or the like; and a communication unit 1309 such as a network card, modem, wireless communication transceiver, etc. The communication unit 1309 allows the device 1300 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.

The various processes and processes described above, such as method 1100, may be performed by processing unit 1301. For example, in some embodiments, method 1100 may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 1308. In some embodiments, some or all of the computer program may be loaded onto and/or installed onto device 1300 via ROM 1302 and/or communications unit 1309. When the computer program is loaded into RAM 1303 and executed by CPU 1301, one or more acts of method 1100 described above may be performed.

The present disclosure may be methods, apparatus, systems, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for carrying out various aspects of the present disclosure.

The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.

The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.

The computer program instructions for carrying out operations of the present disclosure may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, the electronic circuitry that can execute the computer-readable program instructions implements aspects of the present disclosure by utilizing the state information of the computer-readable program instructions to personalize the electronic circuitry, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA).

Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method of device interaction, comprising:

the method comprises the steps that a first device and a second device are in communication connection;

the first equipment acquires the equipment information of the second equipment;

the first device determines, based on the device information, that application data is suitable for sharing between the first device and the second device, the application data being data generated and used by an application in order to provide a service or implement a preset function; and

the first device automatically initiates transmission of the application data between the first device and the second device.

2. The method of claim 1, wherein automatically initiating transmission of the application data comprises:

the first device determining a likelihood that the application data will be shared; and

the first device automatically initiates transmission of the application data if the likelihood exceeds a threshold.

3. The method of claim 2, wherein determining the likelihood that the application data will be shared comprises:

the first device acquiring use information about an application using the application data and state information of the first device;

the first device obtaining a predictive model associated with the application; and

the first device determines the likelihood from the predictive model with at least the usage information and the status information as inputs.

4. The method of claim 3, wherein obtaining the predictive model comprises:

the first device obtaining historical usage information related to the application, historical state information of the first device, and historical user selections as to whether to share the application data; and

the first device trains the predictive model by taking as input the historical usage information, the historical state information, and as output the historical user selection.

5. The method of any of claims 1 to 4, wherein determining whether it is appropriate to share the application data between the first device and the second device comprises:

in response to a first application running at the first device providing the service using the application data, the first device determining whether a device type of the second device is of a preset device type corresponding to the service;

if the device type of the second device is determined to belong to the preset device type, the first device determines whether the second device has a second application of the same type as the first application; and

the first device determines to be adapted to share the application data to the second device if it is determined that the second device has the second application.

6. The method of any of claims 1 to 4, wherein determining whether it is appropriate to share the application data between the first device and the second device comprises:

in response to a third application for providing the service being enabled at the first device, the first device determining whether a device type of the second device is of a preset device type corresponding to the service;

if it is determined that the device type of the second device belongs to the preset device type, the first device determines whether a fourth application of the same type as the third application at the second device is providing the service using the application data; and

the first device determines to be adapted to share the application data from the second device to the first device if it is determined that the fourth application is using the application data.

7. The method of any of claims 1 to 6, wherein the application data is used by the first device to provide the service prior to the sharing, the automatically initiating transmission of the application data comprising:

the first device automatically sends the application data to the second device to enable the second device to provide the service using the application data.

8. The method of claim 7, further comprising:

the first device stops using the application data to provide the service if it is determined that the application data was successfully transmitted.

9. The method of any of claims 1 to 6, wherein the application data is used by the second device to provide the service prior to the sharing, the automatically initiating transmission of the application data comprising:

the first device automatically sending a request for the application data to the second device;

the first device receiving the application data from the second device; and

the first device automatically uses the application data to provide the service.

10. The method according to any of claims 1 to 9, wherein the service comprises at least one of:

a navigation service that provides a navigation service to a user,

an audio play-back service is provided,

a video play-back service that provides a video play-back service,

a text editing service that is used to edit the text,

a document browsing service for browsing a document,

an audio call service, or

And (4) video call service.

11. An electronic device, comprising:

one or more processors;

one or more memories; and

one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, the one or more computer programs comprising instructions, which when executed by the electronic device, cause the electronic device to perform the method of any of claims 1-10.

12. A computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the operations of the method according to any one of claims 1 to 10.