WO2017097128A1 - 设备间任务接管的方法及装置 - Google Patents

设备间任务接管的方法及装置 Download PDF

Info

Publication number
WO2017097128A1
WO2017097128A1 PCT/CN2016/107420 CN2016107420W WO2017097128A1 WO 2017097128 A1 WO2017097128 A1 WO 2017097128A1 CN 2016107420 W CN2016107420 W CN 2016107420W WO 2017097128 A1 WO2017097128 A1 WO 2017097128A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
task
data
song
service
Prior art date
Application number
PCT/CN2016/107420
Other languages
English (en)
French (fr)
Inventor
谭雄
施少峰
吴鑫
周琼
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2017097128A1 publication Critical patent/WO2017097128A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Definitions

  • the present application relates to a task takeover technology, and in particular, to a method and apparatus for task takeover between devices.
  • the present application provides a method and apparatus for taking over tasks between devices, which can switch tasks on one device to another device.
  • a method for task takeover between devices comprising the steps of:
  • the task data of the local service is sent to the service application of the peer; the task data carries the local service.
  • the service application processing of the local end that matches the type identifier of the service application of the peer end is sent.
  • an apparatus for taking over an inter-device task includes:
  • the connection management module is configured to monitor the connection status of the devices at both ends, and notify the service application where the device is located after the devices at both ends establish a connection;
  • the transmission management module is configured to send the task data of the local service application to the service application of the peer end when the corresponding service application on the two ends of the device has the task takeover capability; the task data carries the service application of the local end The type identifier; and/or when the task data of the service application of the peer end is received, the service application processing of the local end matching the type identifier of the service application of the peer end is sent.
  • the application uses the service application of different devices to transmit task data, and the number of tasks of the business application on one device It is sent to another device and processed by a service application with processing capability on another device, thereby implementing task takeover between different devices; this application enables information on different devices to flow between different devices, according to the current user The environment is the most reasonable way to present information.
  • FIG. 1 is a network diagram of an application according to an embodiment of the present application
  • FIG. 2 is a flowchart of a method for indirectly managing a task of a device in an embodiment of the present application
  • FIG. 3a is a schematic diagram of a service scenario in an application example of the present application.
  • FIG. 3b is an interaction timing diagram of a navigation application in an application example of the present application.
  • FIG. 3c is an effect diagram of a notification message in an application example of the present application.
  • FIG. 3d is an interaction timing diagram of an audio playing application in an application example of the present application.
  • 3e is an effect diagram of a notification message in an application example of the present application.
  • FIG. 3f is a signal interaction diagram of a system message monitoring application in an application example of the present application.
  • FIG. 4 is a hardware architecture diagram of an apparatus for indirect pipe tasks of a device in an embodiment of the present application
  • FIG. 5 is a logical structural diagram of an apparatus for indirect pipe tasks of a device in an embodiment of the present application.
  • first, second, third, etc. may be used to describe various information in this application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present application.
  • second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • FIG. 1 is a network diagram of a service scenario to which the present application applies.
  • the network 10 includes a plurality of devices (device 101, device 102, device 103, ...); each device can be loaded with a plurality of service application App software (App1, App2, App3, ).
  • Devices can be of various types, such as mobile phones, tablets, computers, smart headphones, smart TVs, smart watches, car machines in automobiles, and the like.
  • the business application App software may be software that provides a certain service, such as an application that provides an audio playback service, an application that provides a navigation service, or the like, or may monitor a service provided by an operating system (such as a phone or a text message).
  • the app of the system message (such as the service) is called the system message monitoring app for convenience of description.
  • a wireless or wired connection can be established between the devices.
  • the application can implement the tasks performed by the App on the device through the App on other devices.
  • the implementation scheme can be referred to FIG. 2.
  • the task takeover in this application refers to the smooth switching of tasks on different devices.
  • the task on the device 101 is switched to the device 102.
  • the device 102 can have a small amount of control on the device 101, and the device 101 also It can be no longer controlled by the device 102.
  • the device 101 accepts the remote control of the device 102 in the prior art VNC (Virtual Network Computer) technology
  • the device 102 essentially transmits the control command to the device 101.
  • the task is still performed on device 101.
  • the entity performing the method may alternatively perform steps S201 and S202, or may perform both steps. That is to say, the service application in which the entity is located may only serve as the receiver of the task or only as the receiver of the task, or may have the functions of the receiver and the receiver of the task at the same time.
  • a connection can be established between two devices through a local area network mobile communication network.
  • one of the devices can be used as a server to provide short-range wireless connection services (such as WIFI, Bluetooth, infrared, etc.); It is not excluded that two devices establish connections by other means, such as establishing a connection through a 3G, 4G mobile network, or establishing a connection by wire.
  • the SDK Software Development Kit
  • the SDK may be embedded in the business application that does not have the task takeover capability in the prior art. Packets, steps S201 and S202 are performed by the SDK; of course, new service applications can also be specifically designed to perform steps S201 and S202.
  • the SDK may include a connection management service and a transmission management service.
  • the connection management service is responsible for monitoring the connection status of the devices at both ends.
  • the transmission management service is responsible for interacting with the peer device.
  • connection management service After a connection is established between two devices, the current connection status can be notified to the service applications at both ends through the connection management service.
  • the service application at both ends After the service application at both ends knows that the two devices have established a connection, you need to confirm whether the peer and the peer have the ability to take over the task. You can use the task takeover capability indicator to distinguish whether the service application has the ability to take over the task. For example, you can use 1 to indicate that the service application has the task takeover capability, and 0 means that the service application does not have the task takeover capability.
  • the service application of the two ends can mutually negotiate the message of the task takeover capability; the message carrying the task takeover capability identifier is carried in the message of the negotiation task takeover capability, and the sender of the message indicating the negotiation task takeover capability is determined by the task takeover capability identifier; After the task takeover capability negotiation is successful, step S201 is performed, and if the negotiation fails, the process of the task takeover is ended.
  • the receiver can be not fixed for tasks of the same business application.
  • the device 101 in FIG. 1 is a vehicle
  • the device 102 is a mobile phone of the driver
  • the device 103 is a mobile phone of the passenger in the vehicle
  • the App1 on the device 101 can be allowed to take over the task of the App1 on the device 102, and the solution is solved.
  • the problem that the driver is inconvenient to operate the device 102 during driving may also allow the App1 on the device 101 to take over the task of App1 on the device 103.
  • the App of the peer device may perform the task takeover of the first received task data after having negotiated the successful task takeover capability with the service application of the plurality of taken over devices; or may also be based on the service of the taken over device.
  • the account information of the application ranks the task data consistent with the information of the App account at the highest priority; or the prompt information may be popped up for manual selection of which task data to take over the task.
  • the service type of the service application of the local device can be carried, so that the peer device can send the task data to the matching service application. deal with.
  • the service type of the transmitted task data may also be carried, so that the service application of the peer end can identify the task data when processing the task data. The type is processed accordingly.
  • the user may be prompted to set the permission of the task to take over.
  • the service application of the receiver device After receiving the task data sent by the service application of the receiver device, check whether the task takeover permission set by the user allows the service application to take over the task. If permitted, the task data received from other devices shall be sent to the service of the sender. The type used identifies the matching local business application.
  • the local service application may determine whether to process the task data of the service application of the peer end according to the current usage state of the local service application or the user instruction. For example, if the local business application is currently in an idle state, the task data can be directly run; if the business application is accepting the user's operation instruction, or the task data is running, or is using other business applications to run the same kind of task data (for example)
  • the business application that receives the task data is the QQ music playing app, but the device is playing the music data using the shrimp music playing app on the device, and the user may be prompted to take over the received task data, and perform further according to the user's instruction. operating. For the task data under which the business application is executed, and how to execute the task data, there may be different processes according to different design requirements.
  • the process disclosed in Figure 2 can be applied to services provided by a variety of business applications.
  • the type of the service application may be a navigation application, an audio playback application, a video playback application, a system monitoring message application, an instant messaging application, etc.
  • the system monitoring message application is used to monitor the system message received by the operating system of the local device through the notification center (for example, SMS notifications, phone notifications, etc.).
  • the system monitoring message application can integrate the functions of the required system services, for example, the functions of the short message service and the telephone service can be integrated into the system monitoring message application.
  • the service data transmitted by the local service application is different for different service processes involved in different services, and the process of processing the task data by the opposite end service application may also be different.
  • the task data transmitted by the navigation application may include at least one of the following navigation information: destination data currently being navigated, current planned path destination data, and a predetermined number of recently searched
  • the destination data, the navigation preference data, and the like may of course include other navigation-related information that is not listed.
  • the transmitted task data may include at least one of the following audio playback information: a current song cover image, a current song ID, an artist to which the current song belongs, and an album to which the current song belongs;
  • the audio data of the current song, the play control data of the current song, the song list, the song list includes the song ID and the song arrangement order, and of course, may also include other unrelated audio play related information.
  • the transmitted task data includes at least one of the following short message information: the sender name, the sender's phone number, the short message content, and the short message.
  • the reception time and the like may of course include other information related to the short message not listed.
  • alternate application takeovers can occur between applications at both ends of the device.
  • the navigation application on the local end may send the task data to the navigation application on the peer end.
  • the process of updating the navigation information by the peer-to-peer navigation application for example, updating one or more of the following navigation information: destination data currently being navigated, current planned route destination data, recently searched predetermined number of destination data
  • the navigation application of the peer end requests the navigation application of the peer to take over the task data of the navigation application of the opposite end
  • the navigation application of the local end may first obtain the task data of the navigation application of the opposite end.
  • the previously stored navigation information is updated according to the received task data of the navigation application of the opposite end, and then navigated according to the updated navigation information.
  • the current song cover picture, the current song ID, the artist of the current song, and the album of the current song are encapsulated into task data of a predetermined format, and sent to the audio play application of the receiver through WIFI;
  • the audio play application of the takeover party receives After the task data, if it agrees to take over the received task data, and does not store the audio data of the current song or the playback control data of the current song on the device, the audio playback application of the receiver is notified, and the audio of the receiver is played.
  • the application sends the audio data of the current song or the play control data of the current song to the audio play application of the receiver via Bluetooth.
  • Another way may be to send the current song cover picture of the receiver, the current song ID, the artist of the current song, the album of the current song, and the audio data of the current song or the play control data of the current song to the receiver through WIFI. Audio playback app.
  • the audio playback application of the device plays through the mobile communication network and the audio.
  • the cloud server of the application is connected, the audio data of the current song or the playback control data of the current song can be downloaded from the cloud server.
  • the task data received by the takeover's audio playback application may be a song list or song ID, such as device 102 in FIG. 1 wishing to share a list of songs on the device with device 101.
  • the takeover's audio playback application can generate a temporary entry; in the temporary entry, a predetermined rule saves or deletes the song list.
  • the predetermined rules may exist in various forms.
  • the song list may be saved in the order of the received song list, and when the audio data is played, the play may be performed according to the order in the song list.
  • the relevant parts above refer to the relevant parts above, and I will not repeat them.
  • the number of song lists stored in the temporary entry can be set in advance, when the saved song After the list reaches the predetermined number, if another song list is received, the received song list is deleted; or when the saved song list reaches the predetermined number, the played song is deleted from the earliest saved song ID, for example
  • the song list is retained for a maximum of 100 songs. When the 101st song is newly added and the first music is played, the ID of the first song is deleted.
  • the temporary entry may be deleted only when the local device is powered off, and remain when the audio playback application is closed, or when the current task data is completed. It is easy to understand that the management strategy for temporary entrances can be tailored to the design needs.
  • the system may be equipped with a system message monitoring application, and the system message monitoring application monitors the notification center of the operating system in real time to obtain system messages received by the notification center, such as short message notification, telephone notification, and update reminder.
  • the system message monitoring application can be pre-agreed with the peer to support the task takeover type, for example, the short message service can be agreed upon.
  • the system message monitoring application of the local end determines whether to support the service corresponding to the system message according to the supported task takeover type. If supported, the system message is encapsulated into task data and sent to the peer end.
  • the system message monitoring application the task data carries the type identifier of the system message monitoring service and the type identifier of the service corresponding to the system message.
  • the peer system message monitoring application sends the task data to the notification center of the device if the user approves the takeover, and the notification center prompts the user whether to view the system message, if the user instruction is to view the system message, and the system message is monitored.
  • the application has integrated the function of the short message service, and the notification center informs the system message monitoring application to display the content of the system message; if the system message monitoring application does not integrate the function of the short message service, the notification center informs the short message service to display the content of the system message.
  • FIG. 3a is a network environment diagram of the application instance.
  • the device a is a vehicle mounted on a car
  • the device b is a driver's mobile phone
  • the devices c and d are mobile phones of a passenger on the vehicle.
  • a navigation app, a music play app, a system message monitoring app for monitoring system messages (such as short message notification, phone notification, etc.) are installed on the devices a, b, c, and d, respectively, and the system message monitoring app has integrated short message service and telephone.
  • the function of the service An SDK (SDK1 ⁇ SDK2 ⁇ SDK3) is embedded in each app, and each SDK contains a connection management service and a transfer management service.
  • Each device supports WIFI function and Bluetooth function.
  • the car machine can be used as the server of WIFI function, and broadcast SSID (Service Set Identifier) to establish WIFI connection between the mobile phone and the car in the car.
  • SSID Service Set Identifier
  • other mobile phones in the car select the SSID of the car and establish a WIFI connection with the car.
  • the process of establishing a WIFI connection can refer to related schemes disclosed in the prior art. In this case, you can allow multiple devices to be built with the car. Establish a WIFI connection.
  • the driver needs to navigate the driving route through the device a, but the driver is driving the vehicle, and the device b is inconvenient to operate, so the owner of the device c opens the navigation app on the device.
  • the connection management service in the SDK1 on the device c detects that the device c has established a WIFI connection with the device a, and then notifies the navigation app.
  • the navigation app on the device c sends a message for negotiating the task takeover capability to the navigation app of the device a through the transport management service, so as to negotiate the task takeover capability with the navigation app on the device a, and the message for negotiating the task takeover capability carries its own task.
  • the takeover capability identifier the value of the task takeover capability identifier is 1, indicating that it has the task takeover capability.
  • the navigation app on the device a and the navigation app on the device c exchange the message of the task takeover capability through the transmission management service provided by the SDK1, and notify the device a and the navigation app on the device c after the interaction succeeds.
  • the navigation app on the device c encapsulates the navigation-related information input by the owner into task data according to a predetermined format, and sends the information to the device a.
  • the predetermined format includes a type identifier of the navigation app and a type identifier of the navigation data.
  • the navigation related information includes destination data currently being navigated, path destination data currently being planned, 5 destination data recently searched, navigation preference data.
  • the navigation application of the device a determines, according to the type identifier of the service application, the task data that the navigation application needs to process, and further determines whether the permission set by the user is allowed. Take over the navigation task, if yes, send the task data to the navigation app of device a; if not, prompt the user whether to reset the permissions.
  • the navigation app of the device a determines whether to start the task takeover: if the navigation app of the device a is currently in use, or is receiving an instruction of the user's operation map, prompting the user to switch to the device
  • the navigation state of the task data of c (the format of the prompt refers to FIG. 3c, the task data can be stored when the user refuses to take over the task data); if the navigation app of the device a is currently in an idle state, the task data of the device c is started to be processed.
  • the driver finds that the navigation destination or the navigation preference needs to be changed, and the updated navigation information may be encapsulated by the navigation app of the device c into the navigation application of the task data to the device a, or may be navigated in the device a.
  • the navigation app of the device a restarts navigation according to the newly input navigation information.
  • the device data of the device a may be requested after the device A inputs new navigation information.
  • the navigation app on the device a encapsulates the navigation information into task data according to a predetermined format, and the predetermined format includes the type of the navigation app.
  • the identification and the type identification of the navigation data are transmitted to the transmission management service of the navigation app on the device c through the transmission management service (S307b).
  • the transmission management service sends the received task data to the navigation app of the device c.
  • the navigation app on the device c determines whether the received task data matches the initially saved navigation information, if not, if not , the saved navigation information is updated.
  • the navigation app of the device a ends the navigation or the device a is disconnected from the device c, etc., the navigation app on the device a and the device c is notified to end the task takeover process.
  • the owner of device c opens the music play app on the device, and wishes to send the audio data currently being played by the music play app on the device to the music play App of device a.
  • Device c and device a have established a WIFI connection and a Bluetooth connection.
  • the music playback app has been loaded with SDK2.
  • the cover, the song name, the artist, the album, and the like of the currently playing music are encapsulated into task data, and sent to the device a, and the task data carries the type identifier of the music play App.
  • the music play App of the device a determines the task data that the music play application needs to process according to the type identifier of the service application, and further determines the permission set by the user. Whether to allow the music play task to be taken over, if yes, the task data is sent to the music play App of the device a; if not, the user is prompted whether to reset the permission.
  • the music play App of the device a determines whether to start the task takeover:
  • the music play App of the device c sends the audio data of the currently playing music, the play control data (for example, control data such as forward, backward, stop, etc.) to the device a via Bluetooth.
  • the play control data for example, control data such as forward, backward, stop, etc.
  • the device a can be implemented by the following processes S307d to S310d.
  • the takeover of the music play task of device d The user may be prompted to take over the music play task by guiding the page as shown in FIG. 3e: when the user opens the music play app, if the SDK 2 recognizes that the current WIFI hotspot device is the device a, the boot page is popped up (the boot page in this example) It can appear only once, and will not appear when the user opens the music play app next time).
  • the searched song ID or song list is encapsulated into the task data according to the predetermined format and sent to the device a, and all the song IDs and the songs may be included in the song list, and the task data includes the type identifier of the music play App. It may also include a type identifier of the task data indicating whether the song ID or the song list is sent.
  • the music play App of the device a after receiving the task data, the music play App of the device a generates a temporary entrance of the "friend sharing song", and saves the received task data in a temporary portal, which can be only when the device a is powered off. Delete, the entry disappears and the song list is cleared, and the entry is no longer displayed the next time the car is started.
  • the method for saving the task data for the temporary entry is: adding the task data received multiple times to the temporary entry in the order of receiving, for example, receiving the first, second, third, fourth, and fifth songs for the first time. The second time you receive 6, 7, 8, 9, or 10 songs, the list of songs saved in the temporary entrance is refreshed to 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, if saved.
  • the song list has exceeded the predetermined value, and the task data received after the predetermined value is deleted.
  • a loop list is generated according to the information in the "friend sharing song”
  • the audio data is downloaded from the Internet according to the order of the loop list, and the downloaded audio data is played.
  • the cached audio data in the "friend sharing song” is played; if there is no cached audio data, the system is disconnected from the network to stop the task takeover. .
  • the device a When the device a prompts the user, if the owner of the device a confirms switching to the music playing state of the task data of the device d, if the device d sends the song form again, the notification is not notified, and the received song form is directly received. Save in the list of "Friends sharing songs" and start playing the song (or the first song of the song list); if device a The owner of the machine does not confirm the switch to the music playing state of the task data of the device d, and if the device d sends the song form again, the owner of the device a is still notified.
  • the music play App of the device a is in the process of taking over the task, if another media audio play app receives the user instruction and needs to play the audio data, the “friend sharing music” play pauses, records the current play progress, and then switches back to the music again. When the app is played, playback starts based on the recorded playback progress.
  • the owner of device b opens the system message monitoring app on the device, and wishes to hand over the task data of the short message service on the device to device a to take over.
  • the System Message Monitoring App on both devices has the SDK3 loaded.
  • the task type that supports the takeover is preset.
  • the task type that supports the takeover is the short message service.
  • phase 1 the system message monitoring device of the device b monitors the notification center of the operating system of the device b in real time, and when the notification center generates a new system message, acquires the newly generated system message.
  • phase 2 according to the pre-set task type of the support takeover, it is determined that the received system message is a short message notification, and the content of the system message is encapsulated into task data of a predetermined format, including the sender name and the sender's phone number. And the content of the short message; the task data carries the type identifier of the system message monitoring App and the type identifier of the task data (indicating that the service corresponding to the system message is a short message service).
  • the system message monitoring App of the device a receives the task data sent by the device a through the transmission management service, and determines the task data that the system message monitoring application needs to process according to the type identifier of the service application therein, and then determines Whether the permission set by the user allows the task to take over, and if so, the task data is sent to the system message monitoring App of the device a; if not, the user is prompted to reset the permission.
  • the system monitoring message App of the device a sends the task data to the notification center of the device a.
  • the notification center prompts the user whether to view the short message
  • stage 5 the user instructs the notification center to feed back an instruction to view the short message
  • the notification center sends an instruction to view the short message to the system monitoring message App;
  • the system monitoring message App may prompt the user to perform the next operation when displaying the short message content, for example, whether to play the short message, or to prompt whether to make a call after opening the short message.
  • the present application also provides an embodiment of an apparatus for task takeover between devices.
  • Embodiments of the device for taking over tasks between devices of the present application can be applied to smart devices.
  • the device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software.
  • the corresponding computer in the non-volatile memory is passed through the processor of the smart device in which it is located.
  • Program instructions are read into memory to form a run.
  • FIG. 4 a hardware structure diagram of the smart device where the device that takes over the task between the devices of the present application is located, except for the processor, memory, network interface, and non-volatile shown in FIG.
  • the smart device in which the device is located in the embodiment may also include other hardware according to the actual function of the smart device, and details are not described herein.
  • the device 500 for taking over the tasks between devices includes:
  • the connection management module 501 is configured to monitor the connection status of the devices at both ends, and notify the service application after the two devices establish a connection.
  • the transmission management module 502 is configured to send the task data of the local service application to the service application of the peer end when the corresponding service application on the two ends of the device has the task takeover capability; the task data carries the service application of the local end The type identification of the service application; and/or when the task data of the service application of the peer end is received, the service application processing of the local end matching the type identifier of the service application of the peer end is sent.
  • the device 500 may be a software development kit SDK; the SDKs are respectively embedded in the service applications 503 of the devices at both ends.
  • the transmission management module 502 is further configured to: negotiate a message of the task takeover capability with the service application of the peer end, and determine, according to the message of the negotiation task takeover capability, whether the service application at both ends has the task takeover capability; and the message of the negotiation task takeover capability is The task takeover capability identifier is carried, and the sender of the message indicating the negotiation task takeover capability has the task takeover capability.
  • the transmission management module 502 is further configured to: when receiving the task data of the service application of the peer end, determine, according to the task takeover authority set by the user, whether to send the service application processing of the local end that matches the type identifier of the service application of the peer end.
  • the local service application 503 can also be used to determine whether to process task data of the peer service application according to the current usage state or user instruction.
  • the type of business application 503 can include one of the following:
  • the navigation application, the audio playback application, the video playback application, the system monitoring message application, and the instant messaging application, the system monitoring message application is used to monitor the system message received by the operating system of the local device through the notification center.
  • the task data transmitted by the navigation application may include at least one of navigation information: destination data currently being navigated, current planned route destination data, a recently searched predetermined number of destination data, navigation preference data;
  • the task data transmitted by the audio playing application may include at least one of the following: a current song cover picture, a current song name, an artist to which the current song belongs, an album to which the current song belongs, audio data of the current song, playback control data of the current song, a song ID, a song list including a song ID and a song arrangement order;
  • the task data transmitted by the system message monitoring service may include at least one of the following short message information: the sender's name, the sender's phone number, the short message content, and the short message receiving time.
  • the following at least one navigation information may be updated according to the task data of the navigation application of the opposite end: the destination data currently being navigated, the currently planned path destination data, and the most recently searched A predetermined number of destination data, navigation preference data; navigation based on the updated navigation information.
  • the audio playback application of the local end can encapsulate the current song cover image, the current song ID, the artist of the current song, and the album of the current song into a task data of a predetermined format, and send the data to the peer audio playing application through WIFI; when receiving the audio playback of the opposite end After the application request, the audio data of the current song or the play control data of the current song is sent to the peer audio playing application via Bluetooth.
  • the audio playback application of the local end can process the task data of the audio playback application of the opposite end, if the task data of the audio playback application of the opposite end does not include the audio data of the current song or the playback control data of the current song, and the audio of the current song is not stored at the local end, The data or the play control data of the current song is requested to download to the peer audio play application or to the cloud server to download the audio data of the current song or the play control data of the current song.
  • the local audio playing application may generate a temporary entry when receiving the song list; save or delete the song list according to a predetermined rule in the temporary portal;
  • the local system message monitoring application can obtain the system message received by the notification center, and determine whether to support the service corresponding to the system message according to the supported task takeover type. If supported, the system message is encapsulated into task data and sent to the pair.
  • the system message monitoring application of the terminal; the task data carries a type identifier of the system message monitoring application and a type identifier of a service corresponding to the system message.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present application. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Abstract

本申请公开了设备间任务接管的方法和装置，该方法包括步骤：在两端设备建立连接后，如果两端设备上的所对应的业务应用具有任务接管能力，则将本端的业务应用的任务数据发给对端的业务应用处理；所述任务数据中携带本端的业务应用的类型标识；和/或当接收到对端的业务应用的任务数据时，发给与对端的业务应用的类型标识相匹配的本端的业务应用处理。本申请能够将一个设备上的任务切换到另一个设备上运行。

Description

设备间任务接管的方法及装置
本申请要求2015年12月08日递交的申请号为201510898148.6、发明名称为“设备间任务接管的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及任务接管技术，尤其涉及设备间任务接管的方法及装置。
背景技术
在某些场合下，用户不方便对设备上的任务进行操作，例如，当司机正在开车时，经常会需要使用设备上的导航功能，并且也会需要在导航过程中改变之前设置的某些参数。
但是目前较常见的情况下，一台设备上开启的任务通常只能在本设备上运行。
发明内容
本申请提供一种设备间任务接管的方法及装置，能够将一个设备上的任务切换到另一个设备上运行。
根据本申请实施例的第一方面，提供一种设备间任务接管的方法，该方法包括步骤：
在两端设备建立连接后，如果两端设备上的所对应的业务应用具有任务接管能力，则将本端的业务应用的任务数据发给对端的业务应用处理；所述任务数据中携带本端的业务应用的类型标识；和/或
当接收到对端的业务应用的任务数据时，发给与对端的业务应用的类型标识相匹配的本端的业务应用处理。
根据本申请实施例的第二方面，提供一种设备间任务接管的装置，包括：
连接管理模块，用于监控两端设备的连接状态，并在两端设备建立连接后，通知所述装置所在的业务应用；
传输管理模块，用于当两端设备上的所对应的业务应用具有任务接管能力时，将本端的业务应用的任务数据发给对端的业务应用处理；所述任务数据中携带本端的业务应用的类型标识；和/或当接收到对端的业务应用的任务数据时，发给与对端的业务应用的类型标识相匹配的本端的业务应用处理。
本申请利用不同设备的业务应用传输任务数据，将一个设备上的业务应用的任务数 据发给另一个设备，并由另一个设备上具有处理能力的业务应用处理，从而实现了不同设备间的任务接管；本申请使得不同设备上的信息可以在不同设备之间流动，根据用户当前环境选择最合理的信息呈现方式。
附图说明
图1为本申请实施例中一种适用本申请的网络图；
图2为本申请实施例中设备间接管任务的方法的流程图；
图3a为本申请应用实例中业务场景示意图；
图3b为本申请应用实例中导航应用的交互时序图；
图3c为本申请应用实例中一通知消息的效果图；
图3d为本申请应用实例中音频播放应用的交互时序图；
图3e为本申请应用实例中一通知消息的效果图；
图3f为本申请应用实例中系统消息监控应用的信号交互图；
图4为本申请实施例中设备间接管任务的装置的硬件架构图；
图5为本申请实施例中设备间接管任务的装置的逻辑架构图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
图1是本申请所适用的一个业务场景下的网络图。网络10内包括多个设备(设备101、设备102、设备103…)；每个设备上可以装有多种业务应用App软件(App1、App2、App3…)。
设备可以是多种类型，例如，手机、平板电脑、电脑、智能耳机、智能电视、智能手表、汽车中的车机等。
业务应用App软件(以下称为App)可以是提供某种服务的软件，诸如提供音频播放服务的App，提供导航服务的App等等，也可以是监控操作系统所提供的服务(例如电话、短信等服务)的系统消息的App(为方便描述，称为系统消息监控App)。各设备之间可以建立无线或有线连接。
当两个设备上均装有同一种App时(例如均装有图1中的App1)，本申请可实现通过其他的设备上的App接管本设备上的该App所执行的任务。实现方案可参考图2所示。
本申请中的任务接管是指任务在不同设备上的平滑切换，例如，将设备101上的任务切换到设备102上执行，切换后，设备102对设备101可以具有少量的控制力，设备101也可以不再受设备102的控制，不同于现有技术VNC(Virtual Network Computer，虚拟网络计算机)技术中当设备101接受设备102的远程控制时，其实质是设备102通过传输控制指令，将设备101的任务仍然在设备101上执行。
S201，在两端设备建立连接后，如果两端设备上所对应的业务应用具有任务接管能力，则将本端的业务应用的任务数据发给对端的业务应用处理；所发送的任务数据中携带有本端的业务应用的类型标识；和/或
S202，当接收到对端的业务应用的任务数据时，发给与对端的业务应用的类型标识相匹配的本端的业务应用处理。
本申请中，执行本方法的实体可以择一的执行步骤S201和S202，也可以两个步骤均执行。也就是说，该实体所在的业务应用可以只作为任务的被接管方或者只作为任务的接管方，也可以同时具有任务的接管方和被接管方的功能。
本申请中，两个设备之间可以通过局域网络移动通信网建立连接，例如可以将其中一个设备作为服务端，提供短距离无线连接服务(例如WIFI、蓝牙、红外等无线连接服务)；当然，并不排除两个设备通过其他的方式建立连接，例如通过3G、4G移动网络建立连接，或通过有线方式建立连接等。
作为一个实施例，为了使两端的业务应用具备任务接管的能力，可以在现有技术中并不具备任务接管能力的业务应用中嵌入SDK(Software Development Kit，软件开发 包)，通过SDK来执行步骤S201和S202；当然，也可以专门设计出新的业务应用来执行步骤S201和S202。作为一个实施例，SDK可以包含连接管理服务和传输管理服务。连接管理服务负责监控两端设备的连接状态，传输管理服务负责与对端设备交互。
当两个设备之间建立连接后，可以通过连接管理服务将当前的连接状态通知两端的业务应用。
两端的业务应用获知两端设备已建立连接后，需要确认自身和对端是否具有任务接管的能力。可以通过任务接管能力标识来区分业务应用是否具备任务接管的能力，例如，可以用1表示本业务应用具有任务接管能力，0表示本业务应用不具有任务接管能力。
两端的业务应用之间可以交互协商任务接管能力的消息；在协商任务接管能力的消息中携带任务接管能力标识，通过任务接管能力标识表示协商任务接管能力的消息的发送者是否具有任务接管能力；任务接管能力协商成功后，执行步骤S201，如果协商失败，则结束任务接管的流程。
在某些场景下，对于同一种业务应用的任务，被接管方可以并不固定。例如，图1中设备101为车机时，设备102为驾驶员的手机，设备103为车内乘客的手机，可以允许设备101上的App1对设备102上的App1的任务进行接管，而为了解决驾驶员在驾驶过程中对设备102操作不便的问题，也可以允许设备101上的App1对设备103上的App1的任务进行接管。当有不止一个设备的业务应用请求被同一个对端的业务应用接管任务时，对端的业务应用选择对哪个设备的业务应用进行任务接管的策略可以存在多种方式。例如，对端设备的App可以在已经与多个被接管的设备的业务应用协商成功任务接管能力后，对第一个接收到的任务数据进行任务接管；或者还可以根据被接管的设备的业务应用的账户信息，将与自身的App账户信息一致的任务数据排在最高优先级；或者也可以弹出提示信息，供人工选择对哪一个任务数据进行任务接管等等。
由于设备上可能发生任务接管的业务应用不止一种，在传输本端的业务应用的任务数据时，可以携带本端的业务应用的类型标识，以便对端设备能够将任务数据发给相匹配的业务应用处理。除此之外，由于所传输的任务数据也可能不止一种，在一个实施例中，还可以携带所传输的任务数据的业务类型，以便对端的业务应用在处理任务数据时可以识别任务数据的类型进行相应的处理。
在一个例子中，还可以提示用户对任务接管的权限进行设置，在接收到被接管方设备的业务应用所发送的任务数据后，先查看用户设置的任务接管权限是否允许本业务应用进行任务接管，如果允许，则将从其他设备接收到的任务数据发给与发送方的业务应 用的类型标识相匹配的本端的业务应用。
同样作为一个例子，本端的业务应用在收到其他设备的任务数据后，可根据本端的业务应用的当前的使用状态或用户指令确定是否处理对端的业务应用的任务数据。例如，如果本端的业务应用当前处于空闲状态，则可直接运行任务数据；如果本业务应用正在接受用户的操作指令，或者正在运行任务数据，或正在使用其他的业务应用运行同类的任务数据(例如，接收到任务数据的业务应用是QQ音乐播放App，但本设备上正在使用虾米音乐播放App播放音乐数据)，则可提示用户是否接管所收到的任务数据，根据用户的指令来执行进一步的操作。对于业务应用在何种条件下执行任务数据，以及如何执行任务数据，可根据不同的设计需求有不同的流程。
图2所揭示的流程可以适用于多种业务应用所提供的服务。例如业务应用的类型可以是导航应用、音频播放应用、视频播放应用、系统监控消息应用、即时通讯应用等，系统监控消息应用用于监控本端设备的操作系统通过通知中心收到的系统消息(例如短信通知、电话通知等)。需要说明，系统监控消息应用可以集成所需要的系统服务的功能，例如可以将短信服务、电话服务的功能集成到系统监控消息应用中实现。针对不同的服务所涉及的业务流程不同，本端的业务应用所传输的任务数据不同，对端的业务应用处理任务数据的过程也可以不同。
作为一个例子，当业务应用是导航应用时，导航应用所传输的任务数据可以包括以下至少一项导航信息：当前正在导航的目的地数据、当前规划的路径目的地数据、最近搜索的预定数量的目的地数据、导航偏好数据等，当然也可以包括其他未列举出的导航相关的信息。
而在另一个例子中，当业务应用是音频播放应用时，所传输的任务数据可以包括以下至少一项音频播放信息：当前歌曲封面图片、当前歌曲ID、当前歌曲所属艺人、当前歌曲所属专辑；当前歌曲的音频数据、当前歌曲的播放控制数据；歌曲列表，所述歌曲列表中包括歌曲ID及歌曲排列顺序等，当然也可以包括其他未列举出的音频播放相关的信息。
另外，当业务数据是系统消息监控应用，且所监控到的系统消息为短信时，所传输的任务数据包括以下至少一项短信信息：发件人名称、发件人电话号码、短信内容、短信接收时间等，当然也可以包括其他未列举出的短信相关的信息。
在某些场景下，两端设备的应用之间可以发生交替进行任务接管的情况。对于提供导航服务的业务应用，在本端的导航应用将任务数据发给对端的导航应用后，可能会发 生对端的导航应用对导航信息进行更新的过程(例如更新以下导航信息中的一项多多项：当前正在导航的目的地数据、当前规划的路径目的地数据、最近搜索的预定数量的目的地数据、导航偏好数据等)，如果对端的导航应用在更新导航信息后要求本端的导航应用接管对端的导航应用的任务数据，则本端的导航应用在收到对端的导航应用的任务数据后，可以先根据所收到的对端的导航应用的任务数据更新之前所存储的导航信息，之后根据更新后的导航信息进行导航。
对于提供音乐服务的业务应用，将被接管方的音频播放应用的任务数据发送给接管方的音频播放应用、以及接管方的音频播放应用处理任务数据的过程可以有多种方式。
例如，可以将当前歌曲封面图片、当前歌曲ID、当前歌曲所属艺人、当前歌曲所属专辑封装成预定格式的任务数据，通过WIFI发给接管方的音频播放应用；接管方的音频播放应用在收到任务数据后，如果同意接管所收到的任务数据，且在本设备上未存储当前歌曲的音频数据或当前歌曲的播放控制数据，则通知被接管方的音频播放应用，被接管方的音频播放应用接收到该请求后，将当前歌曲的音频数据或当前歌曲的播放控制数据通过蓝牙发给接管方的音频播放应用。
另一种方式可以是将被接管方的当前歌曲封面图片、当前歌曲ID、当前歌曲所属艺人、当前歌曲所属专辑以及当前歌曲的音频数据或当前歌曲的播放控制数据均通过WIFI发给接管方的音频播放应用。
还可以是将被接管方的当前歌曲封面图片、当前歌曲ID、当前歌曲所属艺人、当前歌曲所属专辑封装成预定格式的任务数据，通过WIFI发给接管方的音频播放应用；接管方的音频播放应用在收到任务数据后，如果同意接管所收到的任务数据，且本设备未存储当前歌曲的音频数据或当前歌曲的播放控制数据，当本设备的音频播放应用通过移动通信网络与音频播放应用的云端服务器连接时，则可以从云端服务器下载当前歌曲的音频数据或当前歌曲的播放控制数据。
在某些场景下，接管方的音频播放应用收到的任务数据可以是歌曲列表或歌曲ID，例如图1中的设备102希望向设备101分享本机上的歌曲列表。此时，接管方的音频播放应用可以生成临时入口；在临时入口中预定规则保存或删除歌曲列表。预定规则可以存在多种形式，举例来说，可以按照所收到的歌曲列表的先后顺序保存歌曲列表，在播放音频数据时，可以根据歌曲列表中的顺序来进行播放。获取音频数据和控制数据的方式可参考上文相关部分，不再赘述。
作为一个例子，可以预先设置临时入口所存储的歌曲列表的数量，当所保存的歌曲 列表到达预定数量后，如果再接收到其他歌曲列表，则将所收到的歌曲列表删除；或者当所保存的歌曲列表到达预定数量后，从最早保存的歌曲ID开始，删除已播放的歌曲，例如该歌曲列表最多保留100首，当新加入第101首并播放该首音乐时，删除第1首歌曲的ID。
作为一个例子，临时入口可以仅在本端设备关机时被删除，而当音频播放应用被关闭时，或当前任务数据执行完毕时均继续保留。容易理解，对临时入口的管理策略可以随设计需求而定。
在一个例子中，设备上可以装有系统消息监控应用，系统消息监控应用实时监控操作系统的通知中心，获取通知中心收到的系统消息，例如短信通知、电话通知、更新提醒等。可以与对端的系统消息监控应用事先约定支持任务接管类型，例如可约定支持短信服务等。
本端的系统消息监控应用获取到通知中心收到的新系统消息后，根据所支持的任务接管类型判断是否支持系统消息所对应的服务，如果支持，则将系统消息封装成任务数据发给对端的系统消息监控应用；任务数据中携带所述系统消息监控服务的类型标识和系统消息所对应的服务的类型标识。对端的系统消息监控应用在收到任务数据后，如果同意接管，则将任务数据发给本设备的通知中心，通知中心提示用户是否查看系统消息，如果用户指令为查看系统消息，且系统消息监控应用已集成有短信服务的功能，则通知中心告知系统消息监控应用显示系统消息的内容；如果系统消息监控应用未集成有短信服务的功能，则通知中心告知短信服务显示系统消息的内容。
以下是本申请的一个应用实例，图3a为应用实例所在的网络环境图。图中设备a为装载于汽车上的车机，设备b为驾驶员的手机，设备c、d为车上乘客的手机。在设备a、b、c、d上分别装有导航App、音乐播放App、用于监控系统消息(例如短信通知、电话通知等)的系统消息监控App，系统消息监控App已集成短信服务、电话服务的功能。每个App上嵌入有SDK(SDK1\SDK2\SDK3)，每个SDK包含连接管理服务和传输管理服务。
各个设备支持WIFI功能和蓝牙功能，车机可以作为WIFI功能的服务端，广播SSID(Service Set Identifier，服务集标识)，供车内的手机与车机建立WIFI连接。车机开启后，车机上的WIFI功能自动打开，将自身的SSID广播给车内的其他设备。车内的其他手机在开启WIFI功能后，选择车机的SSID，与车机建立WIFI连接。建立WIFI连接的过程可参考已有技术中所揭示的相关方案。本例中，可以允许多台设备与车机建 立WIFI连接。
1、对于导航App的任务接管流程，参见图3b：
驾驶员需要通过设备a来对行驶路线进行导航，但驾驶员正在驾驶车辆，对持有的设备b操作不便，因此设备c的机主打开本设备上的导航App。
S301b，设备c上的SDK1中的连接管理服务检测到设备c已与设备a建立WIFI连接，于是通知导航App。
S302b，设备c上导航App通过传输管理服务将协商任务接管能力的消息发给设备a的导航App，以便与设备a上的导航App协商任务接管能力，协商任务接管能力的消息中携带自身的任务接管能力标识，任务接管能力标识的值为1，表示具有任务接管能力。
S303b，设备a上的导航App与设备c上的导航App通过自身的SDK1所提供的传输管理服务交互协商任务接管能力的消息，交互成功后通知设备a和设备c上的导航App。
S304b，设备c上的导航App将机主输入的导航相关的信息按照预定格式封装成任务数据，并发给设备a。预定格式中包括导航App的类型标识以及导航数据的类型标识。导航相关的信息包括当前正在导航的目的地数据、当前正在规划的路径目的地数据、最近搜索的5个目的地数据、导航偏好数据。
S305b，设备a的导航App通过传输管理服务收到设备c发来的任务数据后，根据其中的业务应用的类型标识判断出是导航App所需要处理的任务数据，进而判断用户设置的权限是否允许接管导航任务，如果是，则将任务数据发给设备a的导航App；如果不允许，则提示用户是否重新设置权限。
S306b，设备a的导航App在收到任务数据后，判断是否开始任务接管：如果设备a的导航App目前正处于使用状态，或正在接收用户的操作地图的指令，则提示用户是否切换到对设备c的任务数据的导航状态(提示的格式参考图3c，可以在用户拒绝接管任务数据时将任务数据存储)；如果设备a的导航App目前正处于空闲状态，则开始处理设备c的任务数据。
在车辆行驶过程中，驾驶员发现导航目的地或导航偏好需要变更，可以由设备c的导航App将更新后的导航信息封装成任务数据发给设备a的导航App，也可以在设备a的导航App上输入变更后的导航信息，设备a的导航App根据新输入的导航信息重新开始导航；还可以是在设备a上输入新的导航信息后请求设备c接管设备a的任务数据。
如果此时需要切换到设备c的导航App接管设备a的导航App的任务，则设备a上的导航App将导航信息按照预定格式封装成任务数据，预定格式中包括导航App的类型 标识以及导航数据的类型标识，通过传输管理服务发给设备c上的导航App的传输管理服务(S307b)。
S308b，传输管理服务将收到的任务数据发给设备c的导航App，设备c上的导航App收到任务数据后，判断所收到的任务数据与最初保存的导航信息是否相符，如果不相符，则将所保存的导航信息更新。
S309b，更新后，如果目前设备c上的导航App没有处于导航状态，则自动输入最新保存的设备a的导航目的地和偏好设置并开始导航。
当设备a的导航App结束导航或设备a与设备c断开连接等情况时，通知设备a和设备c上的导航App结束任务接管流程。
2、对于音乐播放App的任务接管流程：
设备c的机主打开本机上的音乐播放App，希望将本设备上的音乐播放App目前正在播放的音频数据发给设备a的音乐播放App播放。设备c与设备a已建立WIFI连接和蓝牙连接。音乐播放App已装载SDK2。
设备c的音乐播放App与设备a上的音乐播放App协商成功任务接管能力(协商过程不再赘述)后，两设备接管任务的流程参见图3d：
S301d，将当前正在播放的音乐的封面、歌曲名、艺人、专辑等信息封装成任务数据，发到设备a，任务数据中携带音乐播放App的类型标识。
S302d，设备a的音乐播放App通过传输管理服务收到设备c发来的任务数据后，根据其中的业务应用的类型标识判断出是音乐播放App所需要处理的任务数据，进而判断用户设置的权限是否允许接管音乐播放任务，如果是，则将任务数据发给设备a的音乐播放App；如果不允许，则提示用户是否重新设置权限。
S303d，设备a的音乐播放App在收到任务数据后，判断是否开始任务接管：
S304d，如果设备a的音乐播放App目前正处于使用状态，或有其他同类的音乐播放App在处于使用状态，则提示用户是否切换到对设备c的任务数据的播放状态；
当用户指令为切换到对设备c的任务数据的播放状态时，或设备a的导航App目前正处于空闲状态，则通知设备c的音乐播放App；
S305d，设备c的音乐播放App将当前正在播放的音乐的音频数据、播放控制数据(例如前进、后退、停止等控制数据)通过蓝牙发送给设备a。
S306d，在设备a的音乐播放App通过蓝牙收到音频数据和播放控制数据后开始播放，并在显示界面上显示之前通过WIFI接收到的音乐的封面、歌曲名、艺人、专辑等 信息。
如果设备d的机主希望通过本机的音乐播放App将搜索到的歌曲名称、歌曲列表发给设备a，由设备a的音乐播放App播放，则可通过以下S307d～S310d的流程实现设备a对设备d的音乐播放任务的接管。可以通过如图3e所示引导页来提示用户是否希望音乐播放任务被接管：当用户打开音乐播放App后，如果SDK2识别当前的WIFI热点设备为设备a，则弹出引导页(引导页本例中可以只出现一次，当用户下次打开音乐播放App时不再出现)。
S307d，将所搜索到的歌曲ID或歌曲列表按照预定格式封装成任务数据发给设备a，歌曲列表中可以包含的所有歌曲ID及歌曲的排列顺序，任务数据中除了包括音乐播放App的类型标识，还可以包括任务数据的类型标识，表示发送的是歌曲ID还是歌曲列表。
S308d，设备a的音乐播放App在收到任务数据后，生成“好友分享歌曲”的临时入口，并将所收到的任务数据保存在临时入口中，该临时入口可以仅在设备a关机时被删除，入口消失同时歌曲列表清空，下次再启动车机时不再显示该入口。在本例中，对于临时入口保存任务数据的方式为：将多次收到的任务数据按照接收顺序依次添加到临时入口，例如第一次收到1、2、3、4、5首歌曲，第二次收到6、7、8、9、10首歌曲，则临时入口中保存的歌曲列表刷新为1、2、3、4、5、6、7、8、9、10，如果所保存的歌曲列表已经超过预定值，将预定值之后接收到的任务数据删除。
S309d，在将任务数据保存到临时入口后，判断是否开始任务接管：
S310d，如果设备a的音乐播放App目前正处于使用状态，则提示用户是否切换到对设备d的任务数据的音乐播放状态(当设备d的音乐播放App多次向设备a发送任务数据，或有多个设备的音乐播放App向设备a发送任务数据时，可仅在第一次提示用户)；如果设备a的音乐播放App目前正处于空闲状态，或用户指令为允许接管设备d的任务数据时，开始处理设备d的任务数据：
如果设备a与互联网处于连接状态，则根据“好友分享歌曲”中的信息生成循环列表，根据循环列表的顺序从互联网上下载音频数据，将所下载的音频数据进行播放。除图3d所示的流程外，如果设备a与互联网未连接，则播放“好友分享歌曲”中的已缓存的音频数据；若没有已缓存的音频数据，则弹出系统断网提示，停止任务接管。
设备a对用户进行提示时，如果设备a的机主确认切换到对设备d的任务数据的音乐播放状态后，如果设备d再次发送歌曲表单，则不再通知，直接将所收到的歌曲表单保存在“好友分享歌曲”的列表中，并开始播放该歌曲(或歌单的第一首)；若设备a 的机主未确认切换到对设备d的任务数据的音乐播放状态，则如果设备d再次发送歌曲表单，仍然通知提示设备a的机主。
如果设备a的音乐播放App在任务接管过程中，有其他的媒体音频播放App收到用户指令，需要播放音频数据，则“好友分享音乐”播放暂停，记录当前播放进度，再重新切换回此音乐播放App时，根据所记录的播放进度开始播放。
3)对于短信App的任务接管流程可参见图3f：
设备b的机主打开本机上的系统消息监控App，希望将本设备上的短信服务的任务数据交给设备a接管。两个设备上的系统消息监控App已装载SDK3。在系统消息监控App预先设置支持接管的任务类型，本例中支持接管的任务类型为短信服务。
在阶段1，设备b的系统消息监控App实时监控设备b的操作系统的通知中心，当通知中心产生新的系统消息时，获取新产生的系统消息。
在阶段2，根据预先设置的支持接管的任务类型判断所收到的系统消息为短信通知，则将系统消息的内容封装成预定格式的任务数据，内容包括发件人名称、发件人电话号码、短信内容；任务数据中携带有系统消息监控App的类型标识以及任务数据的类型标识(表示系统消息所对应的服务为短信服务)。
在阶段3，设备a的系统消息监控App通过传输管理服务收到设备a发来的任务数据后，根据其中的业务应用的类型标识判断出是系统消息监控App所需要处理的任务数据，进而判断用户设置的权限是否允许任务接管，如果是，则将任务数据发给设备a的系统消息监控App；如果不允许，则提示用户是否重新设置权限。设备a的系统监控消息App在收到任务数据后，将任务数据发给设备a的通知中心。
在阶段4，通知中心提示用户是否查看短信；
在阶段5，用户指令向通知中心反馈查看短信的指令；
在阶段6，通知中心将查看短信的指令发给系统监控消息App；
在阶段7，系统监控消息App在显示短信内容时可提示用户进行下一步的操作，例如，是否播放此短信，或在打开短信后提示是否拨打电话。
与前述设备间任务接管的方法的实施例相对应，本申请还提供了设备间任务接管的装置的实施例。
本申请设备间任务接管的装置的实施例可以应用在智能设备上。装置实施例可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为一个逻辑意义上的装置，是通过其所在智能设备的处理器将非易失性存储器中对应的计算机 程序指令读取到内存中运行形成的。从硬件层面而言，如图4所示，为本申请设备间任务接管的装置所在智能设备的一种硬件结构图，除了图4所示的处理器、内存、网络接口、以及非易失性存储器之外，实施例中装置所在的智能设备通常根据该智能设备的实际功能，还可以包括其他硬件，对此不再赘述。
请参考图5，设备间任务接管的装置500包括：
连接管理模块501，用于监控两端设备的连接状态，并在两端设备建立连接后，通知所在的业务应用；
传输管理模块502，用于当两端设备上的所对应的业务应用具有任务接管能力时，将本端的业务应用的任务数据发给对端的业务应用处理；所述任务数据中携带本端的业务应用的类型标识；和/或当接收到对端的业务应用的任务数据时，发给与对端的业务应用的类型标识相匹配的本端的业务应用处理。
装置500可以是软件开发包SDK；所述SDK分别嵌入于两端设备的业务应用503中。
传输管理模块502还可以用于与对端的业务应用交互协商任务接管能力的消息，根据所述协商任务接管能力的消息确定两端的业务应用是否具有任务接管能力；所述协商任务接管能力的消息中携带有任务接管能力标识，用于表示所述协商任务接管能力的消息的发送者是否具有任务接管能力。
传输管理模块502还可以用于当接收到对端的业务应用的任务数据时，根据用户设置的任务接管权限判断是否发给与对端的业务应用的类型标识相匹配的本端的业务应用处理。
本端的业务应用503还可以用于根据当前的使用状态或用户指令确定是否处理对端的业务应用的任务数据。
业务应用503的类型可以包括以下其中之一：
导航应用、音频播放应用、视频播放应用、系统监控消息应用、即时通讯应用，所述系统监控消息应用用于监控本端设备的操作系统通过通知中心收到的系统消息。
导航应用所传输的任务数据可以包括以下至少一项导航信息：当前正在导航的目的地数据、当前规划的路径目的地数据、最近搜索的预定数量的目的地数据、导航偏好数据；
音频播放应用所传输的任务数据可以包括以下至少一项：当前歌曲封面图片、当前歌曲名称、当前歌曲所属艺人、当前歌曲所属专辑；当前歌曲的音频数据、当前歌曲的播放控制数据；歌曲ID、歌曲列表，所述歌曲列表中包括歌曲ID及歌曲排列顺序；
系统消息监控应用所监控到的系统消息为短信时，所述系统消息监控服务所传输的任务数据可以包括以下至少一项短信信息：发件人名称、发件人电话号码、短信内容、短信接收时间。
本端的导航应用处理对端的导航应用的任务数据时还可以根据对端的导航应用的任务数据更新以下至少一项导航信息：当前正在导航的目的地数据、当前规划的路径目的地数据、最近搜索的预定数量的目的地数据、导航偏好数据；根据更新后的导航信息进行导航。
本端的音频播放应用可以将当前歌曲封面图片、当前歌曲ID、当前歌曲所属艺人、当前歌曲所属专辑封装成预定格式的任务数据，通过WIFI发给对端的音频播放应用；当接收到对端的音频播放应用的请求后，将当前歌曲的音频数据或当前歌曲的播放控制数据通过蓝牙发给对端的音频播放应用。
本端的音频播放应用可以处理对端的音频播放应用的任务数据时，如果对端的音频播放应用的任务数据不包括当前歌曲的音频数据或当前歌曲的播放控制数据，且本端未存储当前歌曲的音频数据或当前歌曲的播放控制数据，则向对端的音频播放应用或向云端服务器请求下载当前歌曲的音频数据或当前歌曲的播放控制数据。
本端的音频播放应用可以当收到歌曲列表时，生成临时入口；在所述临时入口中按照预定规则保存或删除所述歌曲列表；
当本端设备关机时，将所述临时入口删除。
本端的系统消息监控应用可以获取通知中心收到的系统消息，并根据所支持的任务接管类型判断是否支持系统消息所对应的服务，如果支持，则将所述系统消息封装成任务数据发给对端的系统消息监控应用；所述任务数据中携带所述系统消息监控应用的类型标识和所述系统消息所对应的服务的类型标识。
上述装置中各个单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本申请方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
以上所述仅为本申请的较佳实施例而已，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。

Claims (24)

  1. 一种设备间任务接管的方法，其特征在于，该方法包括步骤：
    在两端设备建立连接后，如果两端设备上的所对应的业务应用具有任务接管能力，则将本端的业务应用的任务数据发给对端的业务应用处理；所述任务数据中携带本端的业务应用的类型标识；和/或
    当接收到对端的业务应用的任务数据时，发给与对端的业务应用的类型标识相匹配的本端的业务应用处理。
  2. 根据权利要求1所述的方法，其特征在于，所述方法通过软件开发包SDK执行；所述SDK分别嵌入于两端设备的业务应用中。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括步骤：
    与对端的业务应用交互协商任务接管能力的消息，根据所述协商任务接管能力的消息确定两端的业务应用是否具有任务接管能力；所述协商任务接管能力的消息中携带有任务接管能力标识，用于表示所述协商任务接管能力的消息的发送者是否具有任务接管能力。
  4. 根据权利要求1所述的方法，其特征在于，当接收到对端的业务应用的任务数据时，所述方法还包括步骤：
    根据用户设置的任务接管权限判断是否发给与对端的业务应用的类型标识相匹配的本端的业务应用处理。
  5. 根据权利要求1所述的方法，其特征在于，所述方法还包括步骤：
    本端的业务应用接收到对端的业务应用的任务数据后，根据当前的使用状态或用户指令确定是否处理对端的业务应用的任务数据。
  6. 根据权利要求1所述的方法，其特征在于，所述业务应用的类型包括以下其中之一：
    导航应用、音频播放应用、视频播放应用、系统监控消息应用、即时通讯应用，所述系统监控消息应用用于监控本端设备的操作系统通过通知中心收到的系统消息。
  7. 根据权利要求6所述的方法，其特征在于，所述导航应用所传输的任务数据包括以下至少一项导航信息：当前正在导航的目的地数据、当前规划的路径目的地数据、最近搜索的预定数量的目的地数据、导航偏好数据；
    所述音频播放应用所传输的任务数据包括以下至少一项：当前歌曲封面图片、当前歌曲名称、当前歌曲所属艺人、当前歌曲所属专辑；当前歌曲的音频数据、当前歌曲的 播放控制数据；歌曲ID、歌曲列表，所述歌曲列表中包括歌曲ID及歌曲排列顺序；
    所述系统消息监控应用所监控到的系统消息为短信时，所述系统消息监控服务所传输的任务数据包括以下至少一项短信信息：发件人名称、发件人电话号码、短信内容、短信接收时间。
  8. 根据权利要求7所述的方法，其特征在于，本端的导航应用处理对端的导航应用的任务数据的步骤包括：
    根据对端的导航应用的任务数据更新以下至少一项导航信息：当前正在导航的目的地数据、当前规划的路径目的地数据、最近搜索的预定数量的目的地数据、导航偏好数据；
    根据更新后的导航信息进行导航。
  9. 根据权利要求7所述的方法，其特征在于，本端的音频播放应用将任务数据发送给对端的音频播放应用处理的过程包括：
    将当前歌曲封面图片、当前歌曲ID、当前歌曲所属艺人、当前歌曲所属专辑封装成预定格式的任务数据，通过WIFI发给对端的音频播放应用；
    当接收到对端的音频播放应用的请求后，将当前歌曲的音频数据或当前歌曲的播放控制数据通过蓝牙发给对端的音频播放应用。
  10. 根据权利要求7所述的方法，其特征在于，本端的音频播放应用处理对端的音频播放应用的任务数据的步骤包括：
    如果对端的音频播放应用的任务数据不包括当前歌曲的音频数据或当前歌曲的播放控制数据，且本端未存储当前歌曲的音频数据或当前歌曲的播放控制数据，则向对端的音频播放应用或向云端服务器请求下载当前歌曲的音频数据或当前歌曲的播放控制数据。
  11. 根据权利要求7所述的方法，其特征在于，本端的音频播放应用处理对端的音频播放应用的任务数据的步骤包括：
    当收到歌曲列表时，生成临时入口；在所述临时入口中按照预定规则保存或删除所述歌曲列表；
    当本端设备关机时，将所述临时入口删除。
  12. 根据权利要求6所述的方法，其特征在于，本端的系统消息监控应用的任务数据发给对端的系统消息监控应用处理的过程包括：
    系统消息监控应用获取通知中心收到的系统消息，并根据所支持的任务接管类型判 断是否支持系统消息所对应的服务，如果支持，则将所述系统消息封装成任务数据发给对端的系统消息监控应用；所述任务数据中携带所述系统消息监控应用的类型标识和所述系统消息所对应的服务的类型标识。
  13. 一种设备间任务接管的装置，其特征在于，包括：
    连接管理模块，用于监控两端设备的连接状态，并在两端设备建立连接后，通知所述装置所在的业务应用；
    传输管理模块，用于当两端设备上的所对应的业务应用具有任务接管能力时，将本端的业务应用的任务数据发给对端的业务应用处理；所述任务数据中携带本端的业务应用的类型标识；和/或当接收到对端的业务应用的任务数据时，发给与对端的业务应用的类型标识相匹配的本端的业务应用处理。
  14. 根据权利要求13所述的装置，其特征在于，所述装置为软件开发包SDK；所述SDK分别嵌入于两端设备的业务应用中。
  15. 根据权利要求13所述的装置，其特征在于，所述传输管理模块还用于与对端的业务应用交互协商任务接管能力的消息，根据所述协商任务接管能力的消息确定两端的业务应用是否具有任务接管能力；所述协商任务接管能力的消息中携带有任务接管能力标识，用于表示所述协商任务接管能力的消息的发送者是否具有任务接管能力。
  16. 根据权利要求13所述的装置，其特征在于，所述传输管理模块还用于当接收到对端的业务应用的任务数据时，根据用户设置的任务接管权限判断是否发给与对端的业务应用的类型标识相匹配的本端的业务应用处理。
  17. 根据权利要求13所述的装置，其特征在于，本端的业务应用用于接收到对端的业务应用的任务数据后，根据当前的使用状态或用户指令确定是否处理对端的业务应用的任务数据。
  18. 根据权利要求13所述的装置，其特征在于，所述业务应用的类型包括以下其中之一：
    导航应用、音频播放应用、视频播放应用、系统监控消息应用、即时通讯应用，所述系统监控消息应用用于监控本端设备的操作系统通过通知中心收到的系统消息。
  19. 根据权利要求18所述的装置，其特征在于，所述导航应用所传输的任务数据包括以下至少一项导航信息：当前正在导航的目的地数据、当前规划的路径目的地数据、最近搜索的预定数量的目的地数据、导航偏好数据；
    所述音频播放应用所传输的任务数据包括以下至少一项：当前歌曲封面图片、当前 歌曲名称、当前歌曲所属艺人、当前歌曲所属专辑；当前歌曲的音频数据、当前歌曲的播放控制数据；歌曲ID、歌曲列表，所述歌曲列表中包括歌曲ID及歌曲排列顺序；
    所述系统消息监控应用所监控到的系统消息为短信时，所述系统消息监控服务所传输的任务数据包括以下至少一项短信信息：发件人名称、发件人电话号码、短信内容、短信接收时间。
  20. 根据权利要求19所述的装置，其特征在于，本端的导航应用处理对端的导航应用的任务数据时还用于：
    根据对端的导航应用的任务数据更新以下至少一项导航信息：当前正在导航的目的地数据、当前规划的路径目的地数据、最近搜索的预定数量的目的地数据、导航偏好数据；根据更新后的导航信息进行导航。
  21. 根据权利要求19所述的装置，其特征在于，本端的音频播放应用用于：
    将当前歌曲封面图片、当前歌曲ID、当前歌曲所属艺人、当前歌曲所属专辑封装成预定格式的任务数据，通过WIFI发给对端的音频播放应用；
    当接收到对端的音频播放应用的请求后，将当前歌曲的音频数据或当前歌曲的播放控制数据通过蓝牙发给对端的音频播放应用。
  22. 根据权利要求19所述的装置，其特征在于，本端的音频播放应用用于处理对端的音频播放应用的任务数据时，如果对端的音频播放应用的任务数据不包括当前歌曲的音频数据或当前歌曲的播放控制数据，且本端未存储当前歌曲的音频数据或当前歌曲的播放控制数据，则向对端的音频播放应用或向云端服务器请求下载当前歌曲的音频数据或当前歌曲的播放控制数据。
  23. 根据权利要求19所述的装置，其特征在于，本端的音频播放应用用于：
    当收到歌曲列表时，生成临时入口；在所述临时入口中按照预定规则保存或删除所述歌曲列表；
    当本端设备关机时，将所述临时入口删除。
  24. 根据权利要求18所述的装置，其特征在于，本端的系统消息监控应用用于获取通知中心收到的系统消息，并根据所支持的任务接管类型判断是否支持系统消息所对应的服务，如果支持，则将所述系统消息封装成任务数据发给对端的系统消息监控应用；所述任务数据中携带所述系统消息监控应用的类型标识和所述系统消息所对应的服务的类型标识。
PCT/CN2016/107420 2015-12-08 2016-11-28 设备间任务接管的方法及装置 WO2017097128A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510898148.6A CN106855823A (zh) 2015-12-08 2015-12-08 设备间任务接管的方法及装置
CN201510898148.6 2015-12-08

Publications (1)

Publication Number Publication Date
WO2017097128A1 true WO2017097128A1 (zh) 2017-06-15

Family

ID=59013728

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/107420 WO2017097128A1 (zh) 2015-12-08 2016-11-28 设备间任务接管的方法及装置

Country Status (2)

Country Link
CN (1) CN106855823A (zh)
WO (1) WO2017097128A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153600A (zh) * 2020-09-23 2020-12-29 博泰车联网(南京)有限公司 一种音频管理方法、装置、系统及计算机存储介质
CN112738776A (zh) * 2020-12-08 2021-04-30 上海博泰悦臻电子设备制造有限公司 获取音乐信息的方法、装置、系统及存储介质
CN115297353A (zh) * 2022-06-29 2022-11-04 青岛海尔科技有限公司 音频的播放方法、装置、存储介质及电子装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108762714A (zh) * 2018-06-01 2018-11-06 广东小天才科技有限公司 播放媒介切换方法、装置、可穿戴设备及播放设备
CN109597678B (zh) * 2018-10-09 2023-07-21 创新先进技术有限公司 任务处理方法及装置
CN109445925B (zh) * 2018-11-09 2022-02-18 郑州云海信息技术有限公司 一种应用程序接管方法、装置及系统
CN111756604B (zh) * 2019-03-29 2022-04-12 华为技术有限公司 一种设备配合方法、装置及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1386246A1 (en) * 2001-03-16 2004-02-04 Embrace Networks, Inc. System and method to manage network-enabled embedded devices operating under various protocols
CN101771707A (zh) * 2010-02-08 2010-07-07 中兴通讯股份有限公司 实现终端间资源共享的方法、资源处理系统及终端
CN104125282A (zh) * 2014-07-25 2014-10-29 大陆汽车投资（上海）有限公司 基于即时通讯/社交应用的位置分享及导航方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7937451B2 (en) * 2007-01-08 2011-05-03 Mspot, Inc. Method and apparatus for transferring digital content from a computer to a mobile handset
CN101232389B (zh) * 2007-01-22 2011-02-09 华为技术有限公司 一种提供组播业务的方法、设备及系统
CN101207538B (zh) * 2007-12-10 2010-07-28 宇龙计算机通信科技(深圳)有限公司 一种pc终端接管移动终端业务的方法、装置及系统
CN105100880B (zh) * 2015-06-01 2019-03-01 上海联彤网络通讯技术有限公司 智能终端及包括该终端的内容交互系统及方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1386246A1 (en) * 2001-03-16 2004-02-04 Embrace Networks, Inc. System and method to manage network-enabled embedded devices operating under various protocols
CN101771707A (zh) * 2010-02-08 2010-07-07 中兴通讯股份有限公司 实现终端间资源共享的方法、资源处理系统及终端
CN104125282A (zh) * 2014-07-25 2014-10-29 大陆汽车投资（上海）有限公司 基于即时通讯/社交应用的位置分享及导航方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153600A (zh) * 2020-09-23 2020-12-29 博泰车联网(南京)有限公司 一种音频管理方法、装置、系统及计算机存储介质
CN112738776A (zh) * 2020-12-08 2021-04-30 上海博泰悦臻电子设备制造有限公司 获取音乐信息的方法、装置、系统及存储介质
CN115297353A (zh) * 2022-06-29 2022-11-04 青岛海尔科技有限公司 音频的播放方法、装置、存储介质及电子装置
CN115297353B (zh) * 2022-06-29 2024-03-22 青岛海尔科技有限公司 音频的播放方法、装置、存储介质及电子装置

Also Published As

Publication number Publication date
CN106855823A (zh) 2017-06-16

Similar Documents

Publication Publication Date Title
WO2017097128A1 (zh) 设备间任务接管的方法及装置
TWI470455B (zh) 媒體內容與用戶訂閱內容的無線同步
KR101951504B1 (ko) 플랫폼-인에이블형 근접 서비스
KR102124510B1 (ko) 앱을 다운로드하는 방법 및 앱을 실행시키는 방법
CN110087112B (zh) 远程媒体控制的方法、系统和存储介质
JP2011187058A (ja) アプリケーションのセッション継続性に対応するシステム及び方法
US9471296B2 (en) Method and device for application installation to multiple memory components
US20170311008A1 (en) Portable media server for providing offline playback of copyright protected media
TW201502787A (zh) 使用配件協定經由無線傳輸之主機與配件裝置間之通信
KR20150016751A (ko) 무선 연결 및 데이터 공유 간소화 장치 및 그 방법
KR101347804B1 (ko) 엔에프씨를 이용한 차량용 에이브이엔 제어 시스템 및 그 방법
US20240045639A1 (en) Distributed cross-device collaboration method, electronic device, and communication system
WO2022135553A1 (zh) 连续播放视频的投屏方法、装置及系统
KR20180100371A (ko) 데이터 전송 방법 및 디바이스
WO2022160612A1 (zh) 与车辆的车载系统交互方法、存储介质和移动终端
CN104468499A (zh) 在跨数据处理设备传送多媒体文件前确定格式兼容性
US20150072662A1 (en) Resumption of data connectivity between mobile devices via switching application
EP3748492A1 (en) Downloading and launching an app on a second device from a first device
JP2019507511A (ja) 複数のメディアタイトルを再生する方法、適合メディアソース装置、メディアプレーヤ装置、メディア委譲装置、及び構成可能且つ適合されたコンピュータプログラム
TW201828083A (zh) 設備間任務接管的方法及裝置
WO2018045722A1 (zh) 终端控制方法及装置
CN113300950A (zh) 数据处理方法、装置、电子设备及计算机可读介质
JP2012059055A (ja) 端末装置、サーバ、コンテンツ配信システム及びコンテンツ配信方法
US9788040B2 (en) File playback method and apparatus
KR20070050710A (ko) 웹 디스크와 연동하는 휴대단말기 및 그 방법

Legal Events

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

Ref document number: 16872320

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16872320

Country of ref document: EP

Kind code of ref document: A1