Synchronized Invocation of an Action on Multiple Devices

A variety of applications are available that facilitate group activities for users of multiple mobile devices. For example, gaming, entertainment, networking, education, and content generation applications allow multiple users to launch the applications on their respective mobile devices and play a game together or work on a shared task. However, synchronizing usage of the application using the mobile devices results in challenges, as the application may not be downloaded on each of the mobile devices, or some users may not understand which application to launch on their mobile device. Once using the application, some users may not understand how to navigate to a particular functionality used by the group, and users may not use the application at the same pace, leading to unsynchronized activities and user frustration.

Implementations of the techniques for synchronized invocation of an action on multiple devices may be implemented as described herein. A mobile device and an additional mobile device, such as any type of mobile phone or computing device, may be configured to perform the techniques for synchronized invocation of an action on multiple devices. In one or more implementations, a synchronization manager, housed in the mobile device, the additional mobile device, a central computing device, or a network-based cloud accessible to the mobile device and the additional mobile device, can be used to implement aspects of the techniques described herein.

Mobile devices may launch applications and access webpages related to group activities. For example, gaming applications allow users of multiple mobile devices to play games together, while entertainment, networking, education, and content generation applications allow multiple users to consume entertainment together or collaborate on a task simultaneously. Additionally, a multitude of webpages are available for access using the mobile devices, which may further support group activities, either as a function of the webpage, or by viewing the webpage from the multiple devices.

However, while the applications and webpages may facilitate multiple group activities, some disadvantages are evident related to utilizing the applications and web pages on multiple devices. For example, an application may not be downloaded on each of the multiple devices, preventing simultaneous launch of the application on the multiple devices. Some users may not understand which application to launch, which webpage to access, or how to navigate the application or webpage using their mobile device, which causes frustration among users and delays in collaboration. Additionally, the users may not perform the group activity using the application or the webpage at the same pace, leading to unsynchronized activities and further user frustration.

Techniques and systems are described for synchronized invocation of an action on multiple devices that overcome these limitations. To begin, the synchronization manager detects that the mobile device and the additional mobile device are “co-located,” or physically located within a threshold distance of each other. To do this, the synchronization manager compares GPS data received from the mobile device and the additional mobile device to determine a physical distance between the mobile devices. Additionally, in some implementations the synchronization manager determines that the additional mobile device satisfies criteria for synchronization of actions with the mobile device, such as being identified as part of a group of related devices. For example, the mobile device and the additional mobile device belong to family members or members of a group.

The synchronization manager also monitors for a trigger indicating that the mobile device has invoked an action that involves a group activity. The action, for instance, involves launching an application or visiting a webpage intended for collaboration among multiple devices. In one example implementation, the synchronization manager may detect that an application has been initiated on the mobile device and determine that a type of the application indicates a group activity is intended, such as any type of gaming application, or other application involving input from multiple users. In another example implementation, the synchronization manager may detect that an application has been initiated on the mobile device and also detect that speech data received from the microphone of the mobile device indicates a verbal cue that the application involves a group activity, such as “Let's play a game on this app.” To do this, the synchronization manager may leverage a machine learning model trained to perform voice recognition for users with known associations to the mobile device and the additional mobile device.

After identifying the trigger to invoke the action on the mobile device, the synchronization manager identifies consent from a user of the additional mobile device to invoke the action on the additional mobile device. In one example implementation, the synchronization manager identifies the consent based on received speech data from the microphone of the additional mobile device, such as a vocal reply indicating agreement to the earlier suggestion to play a game together using the application. In situations when the user of the additional mobile device remains silent, the synchronization manager may cause display of a prompt on a display of the additional mobile device, asking the user of the additional mobile device to confirm the consent to the invocation of the action to sync with the mobile device.

After receiving the consent from the user of the additional mobile device, the synchronization manager invokes the action on the additional mobile device, such as launching the application or navigating to the webpage. In some example implementations, the synchronization manager determines that the application is not downloaded on the additional mobile device. In response, the synchronization manager causes display of a prompt to download the application on the additional user device. Because both the mobile device and the additional mobile device now have access to the application or the webpage, collaboration may begin.

Many applications and webpages have different pages that offer different functionalities. To ensure the mobile device and the additional mobile device are accessing the same page, the synchronization manager may monitor further action on the mobile device and the additional mobile device to synchronize the accessed pages. For instance, the synchronization manager navigates the application launched on the additional mobile device to a specific page to match a page open on the mobile device. In other example implementations, the synchronization manager may fast forward or slow down display of video content related to the invocation of the action on the mobile device or the additional mobile device to establish synchronization of consumption of media across the mobile devices.

The described techniques for synchronized invocation of an action on multiple devices overcome the limitations of conventional systems. For example, detecting an additional mobile device within a threshold distance of the mobile device and receiving consent from the additional mobile device to invoke an action results in automatic invocation of the action on multiple devices without manually inviting mobile devices to invoke the action. Synchronized invocation of an action on multiple devices also alleviates user frustration by facilitating downloading and launching of applications and/or webpages to ensure resources are available to invoke the action on multiple devices. Additionally, synchronized invocation of an action on multiple devices promotes efficiency of user collaboration by monitoring the invocation of the action and managing which pages of the application or webpage are actively displayed on the mobile devices to synchronize continued usage of the application or webpage across the mobile devices.

While features and concepts of the described techniques for synchronized invocation of an action on multiple devices is implemented in any number of different devices, systems, environments, and/or configurations, implementations of the techniques for synchronized invocation of an action on multiple devices are described in the context of the following example devices, systems, and methods.

1 FIG. 100 100 102 104 106 102 104 illustrates an example systemfor synchronized invocation of an action on multiple devices. The systemincludes a mobile device, an additional mobile device, and a communication network. Examples of the mobile deviceand the additional mobile deviceinclude at least one of any type of a wireless device, mobile device, mobile phone, flip phone, client device, companion device, tablet, computing device, communication device, entertainment device, gaming device, media playback device, any other type of computing and/or electronic device.

102 104 102 104 108 102 104 102 104 13 FIG. The mobile deviceand the additional mobile devicecan be implemented with various components, such as a processor system and memory, as well as any number and combination of different components as further described with reference to the example device shown in. In implementations, the mobile deviceand the additional mobile deviceare equipped with a microphoneto receive audio data at the mobile deviceand the additional mobile device. The audio data, for instance, may be spoken dialog in the environment of the mobile deviceor the additional mobile device.

106 102 104 110 110 106 In some implementations, the devices, applications, modules, servers, and/or services described herein communicate via the communication network, such as for data communication with the mobile deviceand the additional mobile device. The interface moduleincludes a wired and/or a wireless network. The interface moduleis implemented using any type of network topology and/or communication protocol and is represented or otherwise implemented as a combination of two or more networks, to include IP based networks, cellular networks, and/or the Internet. The communication networkincludes mobile operator networks that are managed by a mobile network operator and/or other network operators, such as a communication service provider, mobile phone provider, and/or Internet service provider.

102 104 110 102 104 106 110 102 104 The mobile deviceand the additional mobile deviceinclude various functionalities that enable the devices to implement different aspects of synchronized invocation of an action on multiple devices, as described herein. In one or more examples, an interface modulerepresents functionality (e.g., logic and/or hardware) enabling the mobile deviceand the additional mobile deviceto interconnect and interface with other devices and/or networks, such as the communication network. For example, the interface moduleenables wireless and/or wired connectivity of the mobile deviceand the additional mobile device.

102 104 112 102 104 102 104 112 102 104 130 106 The mobile deviceand the additional mobile devicecan include and implement an application, such as any type of messaging application, email application, video communication application, cellular communication application, music/audio application, gaming application, media application, social platform applications, and/or any other of the many possible types of various device applications. Many of the device applications have an associated application user interface that is generated and displayed for user interaction and viewing, such as on a display screen of the mobile deviceor the additional mobile device. Generally, an application user interface, or any other type of video, image, graphic, and the like is digital image content that is displayable on the display screen of the mobile deviceand the additional mobile device. The applicationmay be accessible to the mobile deviceand the additional mobile devicefrom an application service providervia the communication network.

102 104 114 116 102 104 102 104 In implementations, the mobile deviceand the additional mobile devicemay include any type of location device, such as a GPS transceiver or other type of geo-location device, to determine a locationof the mobile deviceand the additional mobile device. Notably, any of the devices described herein, to include components, modules, services, computing devices, camera devices, and/or the tracking tags, can share the GPS data between any of the devices, whether they are GPS-hardware enabled or not. Additionally or alternatively, the mobile deviceand the additional mobile devicecan also include various radios for wireless communication in the environment, such as a UWB radio, Bluetooth radio, or a Wi-Fi radio implemented for wireless communications with the other devices in the environment.

100 102 104 118 118 120 102 104 106 118 102 104 106 118 118 102 104 118 In the example systemfor synchronized invocation of an action on multiple devices, the mobile deviceand/or the additional mobile deviceimplements a synchronization manager. For example, the synchronization managermay be implemented using a network service, such as a cloud-based service, in communication with the mobile deviceand the additional mobile devicevia the communication network. Additionally or alternatively, the synchronization manageris implemented in an external device in communication with the mobile deviceand the additional mobile devicevia the communication network. As shown in this example, the synchronization managerrepresents functionality (e.g., logic, software, and/or hardware) enabling aspects of the described techniques for synchronized invocation of an action on multiple devices. The synchronization managercan be implemented as computer instructions stored on computer-readable storage media and can be executed by a processor system of the mobile deviceand/or the additional mobile device. Alternatively, or in addition, the synchronization managercan be implemented at least partially in hardware of the device.

118 102 104 118 118 102 104 118 118 118 In one or more implementations, the synchronization managerincludes independent processing, memory, and/or logic components functioning as a computing and/or electronic device integrated with the mobile deviceand/or the additional mobile device. Alternatively, or in addition, the synchronization managercan be implemented in software, in hardware, or as a combination of software and hardware components. In this example, the synchronization manageris implemented as a software application or module, such as executable software instructions (e.g., computer-executable instructions) that are executable with a processor system of the mobile deviceand/or the additional mobile deviceto implement the techniques and features described herein. As a software application or module, the synchronization managercan be stored on computer-readable storage memory (e.g., memory of a device), or in any other suitable memory device or electronic data storage implemented with the controller. Alternatively or in addition, the synchronization manageris implemented in firmware and/or at least partially in computer hardware. For example, at least part of the synchronization manageris executable by a computer processor, and/or at least part of the content manager is implemented in logic circuitry.

100 118 126 102 104 118 126 102 112 104 126 In this example system, the synchronization managersynchronizes an invocation of an actionbetween the mobile deviceand the additional mobile device. For instance, the synchronization managerdetects invocation of the actionon the mobile device, such as launching an application, navigating to a webpage, or any other action, and automatically coordinates synchronization of the additional mobile deviceto invoke the action.

118 102 104 118 114 116 102 104 114 118 116 114 102 104 118 102 118 122 106 124 To do this, the synchronization managerdetermines that the mobile deviceand the additional mobile deviceare physically located within a threshold distance of each other (i.e., are co-located). To do this, the synchronization managerleverages the location deviceto determine the locationof the mobile deviceand the additional mobile device. For example, the location deviceis a GPS device, and the synchronization managerdetermines the locationbased on GPS data. Additionally or alternatively, the location deviceinvolves a UWB tag incorporated in the mobile deviceand the additional mobile device, and the synchronization managerdetermines the mobile deviceis within the threshold distance by comparing the signal path loss from received signals from the UWB tags. In some implementations, the synchronization manageraccesses a databasevia the communication networkthat includes mobile device identity information.

118 104 102 102 104 Additionally, in some implementations the synchronization managerdetermines that the additional mobile devicesatisfies criteria for synchronization of actions with the mobile device, such as being part of a pre-assigned group of devices. For example, the mobile deviceand the additional mobile devicebelong to family members or members of a group.

118 128 102 126 118 112 102 112 118 112 102 108 112 112 102 104 130 106 102 104 132 106 The synchronization manageralso monitors for a triggerindicating that the mobile devicehas invoked an actionthat involves a group activity or group collaboration. In one example implementation, the synchronization managermay detect that an applicationhas been initiated on the mobile deviceand determine that the applicationinvolves a group activity, such as any type of gaming application, collaboration application, scheduling application, or other type of application involving input from multiple users. In another example implementation, the synchronization managermay detect that an applicationhas been initiated on the mobile deviceand also receive speech data from the microphoneindicating that the applicationinvolves a group activity, such as “Let's play this game.” The application, for instance, may be accessible to the mobile deviceand the additional mobile devicefrom an application service providervia the communication network. Similarly, the webpage may be accessible to the mobile deviceand the additional mobile devicefrom a web service providervia the communication network.

128 126 102 118 134 104 126 104 118 134 108 104 112 104 118 104 104 134 126 102 After identifying the triggerto invoke the actionon the mobile device, the synchronization manageridentifies consentfrom a user of the additional mobile deviceto invoke the actionon the additional mobile device. In one example implementation, the synchronization manageridentifies the consentbased on received speech data from the microphoneof the additional mobile device, such as a vocal reply indicating agreement to the earlier suggestion to play a game together using the application. In situations when the user of the additional mobile deviceremains silent, the synchronization managermay cause display of a prompt on a display of the additional mobile device, asking the user of the additional mobile deviceto confirm the consentto the invocation of the actionto sync with the mobile device.

134 104 118 126 104 112 102 118 104 118 102 104 112 102 104 118 112 104 102 After receiving the consentfrom the user of the additional mobile device, the synchronization managerinvokes the actionon the additional mobile device, such as launching the applicationor webpage already launched on the mobile device. The synchronization managermay do this by transmitting a deep link or broadcast ID to the additional mobile device. Additionally, in some implementations, the synchronization managermonitors further action on the mobile deviceand the additional mobile deviceto synchronize stages or other aspects related to the applicationor the webpage on the mobile deviceand the additional mobile device. For instance, the synchronization managernavigates the applicationlaunched on the additional mobile deviceto a specific page to match a page open on the mobile device.

2 FIG. 200 200 118 102 104 102 104 102 104 102 104 102 202 104 illustrates an exampleof synchronized invocation of an action on multiple devices, including detecting an additional mobile device within a threshold distance, as described herein. In the example, a synchronization managerconfigured for synchronized invocation of an action on multiple devices is implemented in a mobile device, an additional mobile device, or in another device or network-based cloud that is in communication with the mobile deviceand the additional mobile device. The mobile deviceand the additional mobile deviceare configured to display content accessed from the mobile deviceand the additional mobile device, such as application and webpage user interfaces. For instance, the mobile deviceincludes a display featuring a user interface, and the additional mobile deviceincludes an additional display featuring an additional user interface.

118 102 104 206 118 114 102 104 102 104 206 114 118 116 114 102 104 118 102 118 122 106 124 As illustrated in this example, the synchronization managerdetermines that the mobile deviceand the additional mobile deviceare physically within a threshold distanceof each other. To do this, the synchronization managerreceives location data from the location deviceof the mobile deviceand the additional mobile deviceand compares the location data to determine whether the mobile deviceand the additional mobile deviceare located within the threshold distance. For example, the location deviceis a GPS device, and the synchronization managerdetermines the locationbased on GPS data. Additionally or alternatively, the location deviceinvolves a UWB tag incorporated in the mobile deviceand the additional mobile device, and the synchronization managerdetermines the mobile deviceis within the threshold distance by comparing the signal path loss from received signals from the UWB tags. In some implementations, the synchronization manageraccesses a databasevia the communication networkthat includes mobile device identity information.

118 102 104 206 118 206 118 104 102 102 104 As illustrated in this example, the synchronization managerdetermines that the mobile deviceand the additional mobile deviceare located within the threshold distance. In some example implementations, the synchronization managercontinuously monitors for co-located devices based on the threshold distance. Additionally, in some implementations the synchronization managerdetermines that the additional mobile deviceis pre-associated for synchronization of actions with the mobile device. In this example, the mobile deviceand the additional mobile devicebelong to family members.

118 126 102 102 202 118 126 118 The synchronization manageralso detects an invocation of an actionusing the mobile device. As illustrated in this example, a trivia application called “QuizGame” is launched on the mobile deviceand is displayed on in the user interface. The synchronization managerdetermines that the invocation of the actioninvolves a group activity before initiating synchronization with another device. For example, the synchronization managerdetermines that the “QuizGame” app involves a group activity because it is a game played by multiple users with multiple devices.

118 126 102 102 208 118 126 118 102 104 206 126 Additionally or alternatively, the synchronization managerdetermines that the invocation of the actioninvolves a group activity based on received audio data from the mobile device. As illustrated in this example, the user of the mobile devicesays trigger dialog“Let's play QuizGame!” The synchronization managerdetermines that because this speech is directed at another user, then the invocation of the actioninvolving the launching of the application is intended to involve a group activity and therefore synchronized with other devices. Although this example involves the synchronization managerdetermining the mobile deviceand the additional mobile deviceare located within the threshold distancebefore determining that the invocation of the actioninvolves a group activity, it is noted that these steps may be performed in any order.

118 118 104 118 134 108 104 118 104 210 102 118 108 102 104 104 126 118 104 126 The synchronization manageralso determines whether the user of the synchronization managerconsents to invoke the action using the additional mobile device. For example, the synchronization managermay identify the consentbased on received speech data from the microphoneof the additional mobile device, such as a vocal reply. As illustrated in this example, the synchronization managerdetects that the user of the additional mobile devicesays consent dialog“Sounds good to me!” in response to the suggestion of from the user of the mobile deviceto play “QuizGame.” For instance, the synchronization managermonitors audio data collected from a microphoneof the mobile deviceand/or the additional mobile deviceto determine whether the user of the additional mobile deviceconsents to the invocation of the action. Further, in some example implementations, the synchronization managerleverages a voice recognition model, which may involve an algorithm trained to identify user's voices captured in the audio data, to determine whether the user of the additional mobile deviceconsents to the invocation of the action.

3 FIG. 2 FIG. 300 300 200 illustrates an exampleof synchronized invocation of an action on multiple devices, including prompting a user of the additional mobile device for consent to invoke an action, as described herein. The exampleis an alternative implementation of the exampledescribed with respect to.

102 208 118 126 As illustrated in this example, the user of the mobile devicesays trigger dialog“Let's play QuizGame!” The synchronization managerdetermines that because this speech is directed at another user and that the invocation of the actioninvolving the launching of the application is intended to involve a group activity to be synchronized with other devices.

118 104 210 102 118 108 102 104 104 126 118 134 104 118 302 204 104 302 118 134 104 210 However, in this example the synchronization managerdetects that the user of the additional mobile deviceis silent regarding the consent dialogin response to the suggestion of from the user of the mobile deviceto play “QuizGame.” For instance, the synchronization managermonitors audio data collected from a microphoneof the mobile deviceand/or the additional mobile deviceto determine whether the user of the additional mobile deviceconsents to the invocation of the action. Because the synchronization manageris unable to receive the consentfrom the user of the additional mobile device, the synchronization managergenerates a consent promptfor display on the user interfaceof the additional mobile device. For example, the consent promptreads “Would you like to play QuizGame with Joe?” and offers buttons to respond “Yes” or “No.” In this way, the synchronization managermay receive the consentfrom the user of the additional mobile deviceeven though the consent dialogis silent.

302 118 104 104 134 In other example implementations, the consent promptmay be a verbal or audio prompt. For example, the synchronization managercauses output of audio from a speaker device of the additional mobile devicethat says “Would you like to place QuizGame with Joe?” and monitors to detect a response from the user of the additional mobile deviceto confirm consent.

4 FIG. 2 FIG. 3 FIG. 400 400 200 300 illustrates an exampleof synchronized invocation of an action on multiple devices, including prompting the additional mobile device to download an application to invoke the action, as described herein. The exampleis a continuation of the exampledescribed with respect toor the exampledescribed with respect to.

400 118 134 104 126 104 112 126 102 104 118 112 104 402 104 112 In the example, the synchronization managerhas received the consentfrom the user of the additional mobile deviceto invoke the actionusing the additional mobile device. However, the applicationinvolved in the invocation of the actionusing the mobile deviceis not installed on the additional mobile device. The synchronization managerdetects that the applicationis not installed on the additional mobile deviceand generates a download promptrequesting the user of the additional mobile deviceto download or to allow download of the application.

402 104 112 104 112 118 112 104 104 In this example, the download promptsays “Looks like QuizGame is not downloaded on your device. Would you like to download it?” and offers buttons to respond “Yes” or “No.” If the user of the additional mobile deviceresponds with “Yes,” an automatic download of the applicationmay commence. In other example implementations, the user of the additional mobile deviceis instructed to manually download the application. Further, in other example implementations, the synchronization managerautomatically causes download of the applicationon the additional mobile devicewithout receiving download consent from the user of the additional mobile device.

5 FIG. 4 FIG. 500 500 400 illustrates an exampleof synchronized invocation of an action on multiple devices, including sending a trigger to invoke the action using the additional mobile device, as described herein. The exampleis a continuation of the exampledescribed with respect to.

500 118 134 104 126 104 126 112 126 102 104 118 112 104 104 104 102 In the example, the synchronization managerhas received consentfrom the user of the additional mobile deviceto invoke the actionusing the additional mobile device. In this example, the invocation of the actioninvolves launching the applicationcalled “QuizGime.” Therefore, to synchronize the invocation of the actionon the mobile devicewith the additional mobile device, the synchronization managerlaunches the applicationon the additional mobile device, which is now downloaded. As illustrated in this example, the “QuizGame” application is launched on the additional mobile deviceso that the user of the additional mobile deviceand user of the mobile devicemay simultaneously use the application.

126 102 126 102 104 118 104 104 102 In other example implementations, the invocation of the actioninvolves navigating to a webpage using the mobile device. In this situation, to synchronize the invocation of the actionon the mobile devicewith the additional mobile device, the synchronization managernavigates to the webpage using the additional mobile deviceso that the user of the additional mobile deviceand user of the mobile devicemay simultaneously interact with content on the webpage.

6 FIG. 5 FIG. 600 600 500 illustrates an exampleof synchronized invocation of an action on multiple devices, including monitoring the additional mobile device, as described herein. The exampleis a continuation of the exampledescribed with respect to.

600 126 104 118 102 104 126 102 104 102 104 202 102 204 104 104 104 In the example, after invoking the actionusing the additional mobile device, the synchronization managermonitors the mobile deviceand the additional mobile deviceto synchronize the actionon the mobile deviceand the additional mobile device. As shown in this example, the application “QuizGame” has been launched on both the mobile deviceand the additional mobile device. This initiates a series of trivia questions displayed on the user interfaceof the mobile deviceand the user interfaceof the additional mobile device, beginning at a first question on a starting page. However, the user of the additional mobile devicehas already navigated past the starting page by answering the first question, while the user of the additional mobile devicehas not yet answered the first question.

126 102 104 118 602 112 102 102 104 118 102 104 104 118 102 104 102 104 To synchronize the actionon the mobile devicewith the additional mobile device, the synchronization managercauses a pauseto navigation or interaction with the applicationon the mobile deviceso that the mobile deviceremains on at a stopping page until the additional mobile devicenavigates to the stopping page. As illustrated, the synchronization managercauses the “QuizGame” application to pause at Question 2 on the mobile deviceuntil the additional mobile devicenavigates to Question 2 by the user of the additional mobile deviceanswering the first question. The synchronization managerthen continues to further monitor the stages of the mobile deviceand the additional mobile deviceso that the mobile deviceand the additional mobile deviceremain synchronized.

118 104 112 112 102 102 118 104 In some example implementations, the synchronization managercauses the additional mobile deviceto skip pages of the applicationor webpage to catch up to a page of the applicationor webpage being viewed on the mobile device. For example, the user of the mobile deviceskips an account setup page, prompting the synchronization managerto skip display of the account setup page on the additional mobile device.

7 FIG. 2 FIG. 700 700 200 700 illustrates an exampleof synchronized invocation of an action on multiple devices, including monitoring the additional mobile device, as described herein. The exampleis an alternative implementation of the exampledescribed with respect to. The example, for instance, involves an invocation of an action involving accessing a webpage using a Quick Response (QR) code, rather than launching an application.

700 118 102 104 102 104 102 104 102 104 102 202 104 In the examplea synchronization managerconfigured for synchronized invocation of an action on multiple devices is implemented in a mobile device, an additional mobile device, or in another device or cloud that is in communication with the mobile deviceand the additional mobile device. The mobile deviceand the additional mobile deviceare configured to display content accessed from the mobile deviceand the additional mobile device, such as a webpage. For instance, the mobile deviceincludes a display featuring a user interface, and the additional mobile deviceincludes an additional display featuring an additional user interface.

118 102 104 206 118 114 116 102 104 114 118 116 114 102 104 118 102 118 122 106 124 As illustrated in this example, the synchronization managerdetermines that the mobile deviceand the additional mobile deviceare within a threshold distance. To do this, the synchronization managerleverages the location deviceto determine the locationof the mobile deviceand the additional mobile device. For example, the location deviceis a GPS device, and the synchronization managerdetermines the locationbased on GPS data. Additionally or alternatively, the location deviceinvolves a UWB tag incorporated in the mobile deviceand the additional mobile device, and the synchronization managerdetermines the mobile deviceis within the threshold distance by comparing the signal path loss from received signals from the UWB tags. In some implementations, the synchronization manageraccesses a databasevia the communication networkthat includes mobile device identity information.

102 104 114 116 102 104 For example, the mobile deviceand the additional mobile devicemay include any type of location device, such as a GPS transceiver or other type of geo-location device, to determine a locationof the mobile deviceand the additional mobile device.

118 102 104 206 118 206 As illustrated in this example, the synchronization managerdetermines that the mobile deviceand the additional mobile deviceare located within the threshold distance. In some example implementations, the synchronization managercontinuously monitors for co-located devices based on the threshold distance.

118 126 102 102 702 102 202 118 126 118 102 104 118 102 104 The synchronization manageralso detects an invocation of an actionusing the mobile device. As illustrated in this example, a menu at a restaurant is accessed on the mobile deviceby navigating to a webpage featuring the menu by scanning a QR codewith a camera device of the mobile device, and the menu is displayed on in the user interface. The synchronization managerdetermines that the invocation of the actioninvolves a group activity before initiating synchronization with another device. For example, the synchronization managerdetermines that a shared calendar event includes the user of the mobile deviceand the user of the additional mobile devicedining at the restaurant together. In other example implementations, the synchronization managerdetermines the mobile deviceand the user of the additional mobile deviceare already linked and/or using a group application.

118 126 102 102 704 118 126 118 102 104 206 126 Additionally or alternatively, the synchronization managerdetermines that the invocation of the actioninvolves a group activity based on received audio data from the mobile device. As illustrated in this example, the user of the mobile devicesays trigger dialog“Want to look at the menu?” The synchronization managerdetermines that because this speech is directed at another user, then the invocation of the actioninvolving navigating to the webpage featuring the menu is intended to involve a group activity and therefore synchronized with other devices. Although this example involves the synchronization managerdetermining the mobile deviceand the additional mobile deviceare located within the threshold distancebefore determining that the invocation of the actioninvolves a group activity, it is noted that these steps may be performed in any order.

118 118 104 118 134 108 104 118 104 706 102 118 108 102 104 104 126 118 104 126 The synchronization manageralso determines whether the user of the synchronization managerconsents to invoke the action using the additional mobile device. For example, the synchronization managermay identify the consentbased on received speech data from the microphoneof the additional mobile device, such as a vocal reply. As illustrated in this example, the synchronization managerdetects that the user of the additional mobile devicesays consent dialog“Sure!” in response to the suggestion of from the user of the mobile deviceto view the menu For instance, the synchronization managermonitors audio data collected from a microphoneof the mobile deviceand/or the additional mobile deviceto determine whether the user of the additional mobile deviceconsents to the invocation of the action. Further, in some example implementations, the synchronization managerleverages a voice recognition model, which may involve an algorithm trained to identify user's voices captured in the audio data, to determine whether the user of the additional mobile deviceconsents to the invocation of the action.

134 126 104 118 126 104 118 104 104 In response to receiving the consentto invoke the actionusing the additional mobile device, the synchronization managercauses invocation of the actionusing the additional mobile device. In this example, the synchronization managercauses the additional mobile deviceto navigate to the webpage featuring the menu, so that the user of the additional mobile devicemay avoid manually scanning the QR code.

8 FIG. 7 FIG. 800 800 700 illustrates an exampleof synchronized invocation of an action on multiple devices, including prompting a user of the additional mobile device for consent to invoke an action to visit a webpage related to the scannable code, as described herein. The exampleis an alternative implementation of the exampledescribed with respect to.

800 102 704 118 126 In the example, the user of the mobile devicesays trigger dialog“Want to look at the menu?” The synchronization managerdetermines that because this speech is directed at another user, then the invocation of the actioninvolving the navigation to the webpage is intended involve a group activity and therefore synchronized with other devices.

118 104 706 102 118 108 102 104 104 126 118 134 104 118 802 204 104 302 118 134 104 210 However, in this example the synchronization managerdetects that the user of the additional mobile deviceis silent regarding the consent dialogin response to the suggestion of from the user of the mobile deviceto look at the menu. For instance, the synchronization managermonitors audio data collected from a microphoneof the mobile deviceand/or the additional mobile deviceto determine whether the user of the additional mobile deviceconsents to the invocation of the action. Because the synchronization manageris unable to receive the consentfrom the user of the additional mobile device, the synchronization managergenerates a consent promptfor display on the user interfaceof the additional mobile device. For example, the consent promptreads “Do you want to look at the page Joe is viewing?” and offers buttons to respond “Yes” or “No.” In this way, the synchronization managermay receive the consentfrom the user of the additional mobile deviceeven though the consent dialogis silent.

302 118 104 104 134 In other example implementations, the consent promptmay be a verbal or audio prompt. For example, the synchronization managercauses output of audio from a speaker device of the additional mobile devicethat says “Do you want to look at the page Joe is viewing?” and monitors to detect a response from the user of the additional mobile deviceto confirm consent.

9 FIG. 900 is a flowchartillustrating an example of synchronized invocation of an action on multiple devices in accordance with one or more implementations, as described herein.

902 126 102 118 904 102 104 118 102 104 102 104 104 102 118 102 104 At, an actionis invoked using a mobile device. A synchronization managerdetermines, at, whether the mobile deviceis co-located with an additional mobile device. For example, the synchronization managerdetermines whether the mobile deviceand the additional mobile deviceare located within a threshold distance based on location data, calendar data, or other location-specifying data from the mobile deviceand the additional mobile deviceor associated with the users of the devices. If the additional mobile deviceis not co-located with the mobile device, the synchronization managercontinues to monitor whether the mobile deviceis co-located with an additional mobile device.

906 118 126 104 118 104 908 118 126 104 910 118 104 104 At, the synchronization managermonitors for verbal consent to invoke the actionusing the additional mobile device. For example, the synchronization managermonitors audio data captured using one or more microphones associated with the additional mobile deviceto detect the verbal consent. If verbal consent is received, at, the synchronization managerinvokes the actionusing the additional mobile device. If verbal consent is not received, at, the synchronization managercauses generation of a prompt for display on the additional mobile deviceto prompt the user of the additional mobile devicefor consent.

126 104 912 118 914 102 104 102 104 916 118 102 104 118 102 104 102 104 118 918 102 104 After invoking the actionusing the additional mobile deviceat, the synchronization manager, at, determines whether the mobile deviceand the additional mobile deviceare in sync. If the mobile deviceand the additional mobile deviceare not in sync, at, the synchronization managerperforms an action to sync the mobile deviceand the additional mobile device. For example, the synchronization managermay pause display of content on the mobile deviceand/or skip display of content on the additional mobile device. If the mobile deviceand the additional mobile deviceare in sync, the synchronization managercontinues to monitor, at, whether the mobile deviceand the additional mobile deviceare in sync.

1000 1100 1200 10 11 12 FIGS.,, and Example methods,, andare described with reference to respectivein accordance with one or more implementations of synchronized invocation of an action on multiple devices, as described herein. Generally, any services, components, modules, managers, controllers, methods, and/or operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods may be described in the general context of executable instructions stored on computer-readable storage memory that is local and/or remote to a computer processing system, and implementations can include software applications, programs, functions, and the like. Alternatively or in addition, any of the functionality described herein can be performed, at least in part, by one or more hardware logic components, such as, and without limitation, Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SoCs), Complex Programmable Logic Devices (CPLDs), and the like.

10 FIG. 1000 illustrates example method(s)for synchronized invocation of an action on multiple devices. The order in which the method is described is not intended to be construed as a limitation, and any number or combination of the described method operations may be performed in any order to perform a method, or an alternate method.

1002 118 104 206 102 102 206 102 104 118 104 112 102 At, an additional mobile device is detected that is located within a threshold distance of the mobile device and that satisfies one or more criteria for synchronization of one or more actions with the mobile device. For example, the synchronization managerdetects an additional mobile devicethat is located within a threshold distanceof the mobile deviceand that satisfies one or more criteria for synchronization of one or more actions with the mobile device. In this example, the threshold distanceis determined based on a determined location for the mobile deviceand a received indication of a location from the additional mobile device. In some examples, the synchronization managerdetects the additional mobile devicein response to a trigger involving an applicationbeing launched on the mobile device.

1004 118 126 134 104 126 134 104 104 118 104 126 At, an action is invoked, and consent is received from the additional mobile device to invoke the action. For example, the synchronization managerinvokes an actionand receives consentfrom the additional mobile deviceto invoke the action. In this example, the consentfrom the additional mobile deviceis indicated by verbal consent detected from a user of the additional mobile deviceusing voice recognition. In some examples, the synchronization managerprompts a user of the additional mobile deviceto indicate the consent to invoke the action.

1006 118 126 104 134 126 104 104 102 112 104 102 118 104 112 104 118 104 104 112 104 104 112 104 118 104 102 104 At, a trigger is sent to invoke the action using the additional mobile device based at least in part on receiving the consent. For example, the synchronization managersends a trigger to invoke the actionusing the additional mobile devicebased at least in part on receiving the consent. In this example, the actioninvolves transmitting instruction to the additional mobile deviceto automatically open a webpage using the additional mobile devicethat is open on the mobile device. In some examples, the trigger involves automatically launching an applicationusing the additional mobile devicethat is launched on the mobile device, and the synchronization managerrequests information from the additional mobile deviceindicating whether the applicationis downloaded on the additional mobile device. For example, the synchronization managertransmits a prompt to the additional mobile deviceto prompt a user of the additional mobile deviceto download the applicationon the additional mobile devicebased on the information from the additional mobile deviceindicating whether the applicationis downloaded on the additional mobile device. In some examples, the synchronization managermonitors the additional mobile devicebased on received usage information to determine that content displayed on the mobile deviceis synchronized with content displayed on the additional mobile device.

11 FIG. 1100 illustrates example method(s)for synchronized invocation of an action on multiple devices. The order in which the method is described is not intended to be construed as a limitation, and any number or combination of the described method operations may be performed in any order to perform a method, or an alternate method.

1102 118 126 102 At, an invocation of an action is detected using a mobile device. For example, the synchronization managerdetects an invocation of an actionusing a mobile device.

1104 118 104 134 126 104 118 102 104 206 102 104 134 104 104 At, whether a user of an additional mobile device expresses consent to invoke the action using the additional mobile device is determined. For example, the synchronization managerdetermines whether a user of an additional mobile deviceexpresses consentto invoke the actionusing the additional mobile device. In some examples, the synchronization managerdetermines that the mobile deviceand the additional mobile deviceare located within a threshold distancebased on a determined location for the mobile deviceand a determined location for the additional mobile device. For example, the consentfrom the additional mobile deviceis indicated by verbal consent detected from a user of the additional mobile deviceusing voice recognition.

1106 118 126 104 104 102 112 104 102 112 104 118 104 112 104 104 118 102 104 102 104 At, a trigger is initiated to invoke the action using the additional mobile device. For example, the synchronization managerinitiates a trigger to invoke the actionusing the additional mobile device. In some examples, the trigger involves automatically opening a webpage using the additional mobile devicethat is open on the mobile device. In other examples, the trigger involves automatically launching an applicationusing the additional mobile devicethat is launched on the mobile device, and further comprising determining whether the applicationis downloaded on the additional mobile device. In some examples, the synchronization managerprompts a user of the additional mobile deviceto download the applicationon the additional mobile devicebased on the determination on whether the application is downloaded on the additional mobile device. In some examples, the synchronization managermonitors the mobile deviceand the additional mobile deviceto determine that content displayed on the mobile deviceis synchronized with content displayed on the additional mobile device.

12 FIG. 1200 illustrates example method(s)for synchronized invocation of an action on multiple devices. The order in which the method is described is not intended to be construed as a limitation, and any number or combination of the described method operations may be performed in any order to perform a method, or an alternate method.

1202 118 126 102 At, an indication of an invocation of an action by a mobile device is received. For example, the synchronization managerreceives an indication of an invocation of an actionby a mobile device.

1204 118 104 206 102 102 118 104 206 102 102 104 At, an additional mobile device is detected within a threshold distance of the mobile device and identified in the memory as being pre-associated for synchronization of one or more actions with the mobile device. For example, the synchronization managerdetects an additional mobile devicewithin a threshold distanceof the mobile deviceand identified in the memory as being pre-associated for synchronization of one or more actions with the mobile device. In this example, the synchronization managerdetermines the additional mobile deviceis within the threshold distanceof the mobile devicebased on received calendar data indicating a user of the mobile deviceand a user of the additional mobile deviceattending an event.

1206 118 134 104 126 At, consent is received from the additional mobile device to invoke an action. For example, the synchronization managerreceives consentfrom the additional mobile deviceto invoke an action.

1208 118 126 104 104 102 112 104 102 118 104 112 104 At, a trigger is sent to invoke the action using the additional mobile device. For example, the synchronization managersends a trigger to invoke the actionusing the additional mobile device. In this example, the trigger involves automatically opening a webpage using the additional mobile devicethat is open on the mobile device. In other examples, the trigger involves automatically launching an applicationusing the additional mobile devicethat is launched on the mobile device, and the synchronization managerprompts a user of the additional mobile devicebased on received data indicating whether the applicationis downloaded on the additional mobile device.

13 FIG. 1 9 FIGS.- 1 12 FIGS.- 1300 1300 108 1300 illustrates various components of an example device, which can implement aspects of the techniques and features for synchronized invocation of an action on multiple devices, as described herein. The example devicemay be implemented as any of the devices described with reference to the previous, such as any type of a wireless device, mobile device, mobile phone, flip phone, client device, companion device, display device, tablet, computing, communication, entertainment, gaming, media playback, and/or any other type of computing, consumer, and/or electronic device. For example, the microphonedescribed with reference tomay be implemented as the example device.

1300 1302 1304 1304 1304 1302 The example devicecan include various, different communication devicesthat enable wired and/or wireless communication of device datawith other devices. The device datacan include any of the various devices data and content that is generated, processed, determined, received, stored, and/or communicated from one computing device to another. Generally, the device datacan include any form of audio, video, image, graphics, and/or electronic data that is generated by applications executing on a device. The communication devicescan also include transceivers for cellular phone communication and/or for any type of network data communication.

1300 1306 1306 1300 1306 The example devicecan also include various, different types of data input/output (I/O) interfaces, such as data network interfaces that provide connection and/or communication links between the devices, data networks, and other devices. The data I/O interfacesmay be used to couple the device to any type of components, peripherals, and/or accessory devices, such as a computer input device that may be integrated with the example device. The I/O interfacesmay also include data input ports via which any type of data, information, media content, communications, messages, and/or inputs may be received, such as user inputs to the device, as well as any type of audio, video, image, graphics, and/or electronic data received from any content and/or data source.

1300 1308 1308 1310 1300 The example deviceincludes a processor systemof one or more processors (e.g., any of microprocessors, controllers, and the like) and/or a processor and memory system implemented as a system-on-chip (SoC) that processes computer-executable instructions. The processor systemmay be implemented at least partially in computer hardware, which can include components of an integrated circuit or on-chip system, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), and other implementations in silicon and/or other hardware. Alternatively, or in addition, the device may be implemented with any one or combination of software, hardware, firmware, or fixed logic circuitry that may be implemented in connection with processing and control circuits, which are generally identified at. The example devicemay also include any type of a system bus or other data and command transfer system that couples the various components within the device. A system bus can include any one or combination of different bus structures and architectures, as well as control and data lines.

1300 1312 1312 1312 1300 The example devicealso includes memory and/or memory devices(e.g., computer-readable storage memory) that enable data storage, such as data storage devices implemented in hardware which may be accessed by a computing device, and that provide persistent storage of data and executable instructions (e.g., software applications, programs, functions, and the like). Examples of the memory devicesinclude volatile memory and non-volatile memory, fixed and removable media devices, and any suitable memory device or electronic data storage that maintains data for computing device access. The memory devicescan include various implementations of random-access memory (RAM), read-only memory (ROM), flash memory, and other types of storage media in various memory device configurations. The example devicemay also include a mass storage media device.

1312 1304 1314 1316 1312 1308 1314 The memory devices(e.g., as computer-readable storage memory) provide data storage mechanisms, such as to store the device data, other types of information and/or electronic data, and various device applications(e.g., software applications and/or modules). For example, an operating systemmay be maintained as software instructions with a memory deviceand executed by the processor systemas a software application. The device applicationsmay also include a device manager, such as any form of a control application, software application, signal-processing and control module, code that is specific to a particular device, a hardware abstraction layer for a particular device, and so on.

1300 1318 1318 1314 1300 108 1318 106 108 1318 1300 1 12 FIGS.- In this example, the deviceincludes a synchronization managerthat implements various aspects of the described features and techniques described herein. The synchronization managermay be implemented with hardware components and/or in software as one of the device applications, such as when the example deviceis implemented as the microphonedescribed with reference to. An example of the synchronization manageris the Communication networkimplemented by the microphone, such as a software application and/or as hardware components in the mobile device. In implementations, the synchronization managermay include independent processing, memory, and logic components as a computing and/or electronic device integrated with the example device.

1300 1320 1322 1324 1324 1324 1300 1326 The example devicecan also include a microphone(e.g., to capture an audio recording) and/or camera devices, as well as device sensors, such as may be implemented as components of an inertial measurement unit (IMU). The device sensorsmay be implemented with various sensors, such as a gyroscope, an accelerometer, and/or other types of motion sensors to sense motion of the device. The device sensorscan generate sensor data vectors having three-dimensional parameters (e.g., rotational vectors in x, y, and z-axis coordinates) indicating location, position, acceleration, rotational speed, and/or orientation of the device. The example devicecan also include one or more power sources, such as when the device is implemented as a wireless device and/or a mobile device. The power sources may include a charging and/or power system, and may be implemented as a flexible strip battery, a rechargeable battery, a charged super-capacitor, and/or any other type of active or passive power source.

1300 1328 1330 1332 1300 The example devicecan also include an audio and/or video processing systemthat generates audio data for an audio systemand/or generates display data for a display system. The audio system and/or the display system may include any types of devices or modules that generate, process, display, and/or otherwise render audio, video, display, and/or image data. Display data and audio signals may be communicated to an audio component and/or to a display component via any type of audio and/or video connection or data link. In implementations, the audio system and/or the display system are integrated components of the example device. Alternatively, the audio system and/or the display system are external, peripheral components to the example device.

Although implementations for synchronized invocation of an action on multiple devices have been described in language specific to features and/or methods, the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations for synchronized invocation of an action on multiple devices, and other equivalent features and methods are intended to be within the scope of the appended claims. Further, various different examples are described, and it is to be appreciated that each described example may be implemented independently or in connection with one or more other described examples. Additional aspects of the techniques, features, and/or methods discussed herein relate to one or more of the following:

In some aspects, the techniques described herein relate to a mobile device, including: at least one memory, and at least one processor coupled with the at least one memory and configured to cause the mobile device to: detect an additional mobile device that is located within a threshold distance of the mobile device and that satisfies one or more criteria for synchronization of one or more actions with the mobile device, invoke an action and receive consent from the additional mobile device to invoke the action, and send a trigger to invoke the action using the additional mobile device based at least in part on receiving the consent.

In some aspects, the techniques described herein relate to a mobile device, wherein the consent from the additional mobile device is indicated by verbal consent detected from a user of the additional mobile device using voice recognition.

In some aspects, the techniques described herein relate to a mobile device, wherein the threshold distance is determined based on a determined location for the mobile device and a received indication of a location from the additional mobile device.

In some aspects, the techniques described herein relate to a mobile device, wherein the at least one processor is further configured to detect the additional mobile device in response to a trigger involving an application related to a group activity being launched on the mobile device.

In some aspects, the techniques described herein relate to a mobile device, wherein the trigger involves transmitting instruction to the additional mobile device to automatically open a webpage using the additional mobile device that is open on the mobile device.

In some aspects, the techniques described herein relate to a mobile device, wherein the trigger involves automatically launching an application using the additional mobile device that is launched on the mobile device, and the at least one processor is further configured to request information from the additional mobile device indicating whether the application is downloaded on the additional mobile device.

In some aspects, the techniques described herein relate to a mobile device, wherein the at least one processor is further configured to transmit a prompt to the additional mobile device to prompt a user of the additional mobile device to download the application on the additional mobile device based on the information from the additional mobile device indicating whether the application is downloaded on the additional mobile device.

In some aspects, the techniques described herein relate to a mobile device, wherein the at least one processor is further configured to monitor the additional mobile device based on received usage information to determine that content displayed on the mobile device is synchronized with content displayed on the additional mobile device.

In some aspects, the techniques described herein relate to a mobile device, wherein the at least one processor is further configured to transmit a prompt to the additional mobile device to request the consent to invoke the action.

In some aspects, the techniques described herein relate to a method performed by a mobile device, the method including: detecting an additional mobile device that is located within a threshold distance of the mobile device and that satisfies one or more criteria for synchronization of one or more actions with the mobile device, invoking an action and receive consent from the additional mobile device to invoke the action, and sending a trigger to invoke the action using the additional mobile device based at least in part on receiving the consent.

In some aspects, the techniques described herein relate to a method, further including determining that the mobile device and the additional mobile device are located within a threshold distance based on a determined location for the mobile device and a determined location for the additional mobile device.

In some aspects, the techniques described herein relate to a method, wherein the consent from the additional mobile device is indicated by verbal consent detected from a user of the additional mobile device using voice recognition.

In some aspects, the techniques described herein relate to a method, wherein the trigger involves automatically opening a webpage using the additional mobile device that is open on the mobile device.

In some aspects, the techniques described herein relate to a method, wherein the trigger involves automatically launching an application using the additional mobile device that is launched on the mobile device, and further including determining whether the application is downloaded on the additional mobile device.

In some aspects, the techniques described herein relate to a method, further including prompting a user of the additional mobile device to download the application on the additional mobile device based on the determination on whether the application is downloaded on the additional mobile device.

In some aspects, the techniques described herein relate to a method, further including monitoring the mobile device and the additional mobile device to determine that content displayed on the mobile device is synchronized with content displayed on the additional mobile device.

In some aspects, the techniques described herein relate to a system, including: a memory to maintain identities of at least one or more mobile devices for synchronization in an environment, and a synchronization manager configured to: receive an indication of an invocation of an action by a mobile device, detect that an additional mobile device is within a threshold distance of the mobile device and that the additional mobile device is identified in the memory as being pre-associated for synchronization of one or more actions with the mobile device, receive consent from the additional mobile device to invoke an action, and send a trigger to invoke the action using the additional mobile device.

In some aspects, the techniques described herein relate to a system, wherein the synchronization manager is further configured to determine the additional mobile device is within the threshold distance of the mobile device based on received calendar data indicating a user of the mobile device and a user of the additional mobile device attending an event.

In some aspects, the techniques described herein relate to a system, wherein the trigger involves automatically opening a webpage using the additional mobile device that is open on the mobile device.

In some aspects, the techniques described herein relate to a system, wherein the trigger involves automatically launching an application using the additional mobile device that is launched on the mobile device, and the synchronization manager is further configured to prompt a user of the additional mobile device based on received data indicating whether the application is downloaded on the additional mobile device.