Patent Description:
According to at least one aspect of the disclosure, a system to authenticate computing devices can include a data processing system. The data processing system can execute a natural language processor component, a content selection component, and an authorization component. The data processing system can receive an input audio signal detected by a sensor at a first client device. The natural language processor component can parse the input audio signal to identify a first digital component request in the input audio signal. The content selection component can transmit a first portion of the first digital component to the first client device. The authorization component can transmit an authorization request to a second client device to authorize transmission of a second portion of the digital component to the first client device. The authorization request can be transmitted to the second client device based at least on transmitting the first portion of the first digital component to the first client device. The authorization component can receive, from the second client device, a confirmation message in response to the authorization request. The content selection component can transmit the second portion of the digital component to the first client device based at least on receiving the confirmation message from the second client device.

According to at least one aspect of the disclosure, a method to authenticate computing devices can include receiving, by a natural language processor component executed by a data processing system and via an interface of the data processing system, an input audio signal detected by a sensor at a first client device. The method can include parsing, by the natural language processor component, the input audio signal to identify a first digital component request in the input audio signal. The method can include transmitting, by a content selection component, a first portion of the first digital component to the first client device. The method can include transmitting, by an authorization component, an authorization request to a second client device to authorize transmission of a second portion of the digital component to the first client device. The authorization request can be transmitted to the second client device based at least on transmitting the first portion of the first digital component to the first client device. The method can include receiving, by the authorization component from the second client device, a confirmation message in response to the authorization request. The method can include transmitting, by the content selection component, the second portion of the digital component to the first client device based at least on receiving the confirmation message from the second client device.

According to at least one aspect of the disclosure, a system to authenticate computing devices in a networked environment a data processing system that can include one or more processors and memory. The one or more processors can execute a natural language processor component, a content selection component, and an authorization component. The system can receive, by the natural language processor component, an input audio signal detected by a sensor at a first client device. The system can parse, by the natural language processor component, the input audio signal to identify a first digital component request in the input audio signal. The system can select, by the content selection component, a first digital component and a second digital component based at least on the first digital component request. The system can transmit, by the content selection component and to the first client device, a first portion of the first digital component. The system can transmit, by the authorization component and to a second client device to authorize transmission of a second portion of the digital component to the first client device, an authorization request transmitted to the second client device based at least on transmitting the first portion of the first digital component to the first client device. The system can transmit, by the content selection component and to the second client device, the second digital component. The system can transmit, by the content selection component, the second portion of the digital component to the first client device based at least on receiving a confirmation message generated in response to the authorization request.

According to at least one aspect of the disclosure, a method to authenticate computing devices can include receiving, by a natural language processor component, an input audio signal detected by a sensor at a first client device. The method can include parsing, by the natural language processor component, the input audio signal to identify a first digital component request in the input audio signal. The method can include selecting, by a content selection component, a first digital component and a second digital component based at least on the first digital component request. The method can include transmitting, by the content selection component and to the first client device, a first portion of the first digital component. The method can include transmitting, by an authorization component and to a second client device to authorize transmission of a second portion of the digital component to the first client device, an authorization request transmitted to the second client device based at least on transmitting the first portion of the first digital component to the first client device. The method can include transmitting, by the content selection component and to the second client device, the second digital component. The method can include transmitting, by the content selection component, the second portion of the digital component to the first client device based at least on receiving a confirmation message generated in response to the authorization request.

Following below are more detailed descriptions of various concepts related to, and implementations of, methods, apparatuses, and systems of transferring data in a secure processing environment. The various concepts introduced above and discussed in greater detail below may be implemented in any of numerous ways. The present disclosure is generally directed to authentication of audio-based interaction devices in an interconnected network. For example, a digital assistant component can receive audio input that can include speech. The speech can include a request for content. The digital assistant component can request the content from a third-party responsive to the audio input. Delivery of the content to the digital assistant component can require authorization. It can be challenging to authenticate devices that the use a voice-based interface. For example, some input can be difficult or insecure to provide through a voice-based interface, such as credit card numbers or passwords that the end user may not want to speak aloud for privacy and security concerns. Additionally, it can be challenging or inefficient to authorize devices with voice-based interfaces because generating a conversational interface to authorize the content delivery can result in consuming excessive computing resources, such as processor and memory resources, network bandwidth, or remote procedure calls. Additionally, requiring immediate authorization through the non-voice-based interface of a second device can result in wasted network resources as the end user often abandons the request rather than switching to interface through a second device.

Systems and methods of the present technical solution enable for a delayed, two-factor authentication to occur in networked devices that improves the delivery of requested digital components while reducing computing resource utilization, network bandwidth, or remote procedure calls. For example, the systems and methods of the present technical solution enable the immediate delivery of digital components, which results in fewer abandoned requests, while the digital component delivery is authorized through a delay two-factor authentication process.

In an illustrative example, voice-driven (and hands free) digital assistant devices can be used to request digital components. The digital components can be provided through a subscription-based service (e.g., a streaming music service) or may require payment authorization (e.g., purchasing a song). Delivery of the digital component to the digital assistant can require authorization at a second, non-voice-driven client device. This system of the present technical solution can include a state machine. The state machine can track both the enabled state of the services providing the digital component (for the digital assistant) and the authentication state of the digital assistant.

Responsive to the request for the content, the system can provide the requested content to the digital assistant even if the state of the state machine is in a non-authenticated state. The system can transmit an authorization request to a second client device that is associated with the digital assistant. The system can provide the second client device with a predetermined amount of time to respond to the authorization request. During this predetermined amount of time, the digital assistant can render or present the requested digital component. Once the authorization request is received, the second device can show a notification with a confirm option and a reject option, or the notification might open a dialog with those options. The second client device can automatically approve the authorization request based on local device state, such as if the second client device is within a predetermined distance of the digital assistant. When the end user confirms the dialog (or otherwise positively engages with the authorization request), the second client device can send the system an authentication token and a unique action identifier. The system can use the authentication token and the unique action identifier to change the digital assistant's state machine to an authorized state.

A primary engagement action will enable a disabled service ephemerally and syndicate a notification to a second device. This change of state will also include a timestamp denoting when the ephemeral state is no longer valid. This notification will include a payload with an action that has two sets of parameters, the first parameter is an instruction to authenticate the user and a dialog component (or reference to dialog component) which informs the user about which specific action is being authenticated, and the second parameter is a specific action or event identifier for the action to be authenticated.

<FIG> illustrates an example system <NUM> to authenticate devices in a networked environment. The system <NUM> can include a digital component selection infrastructure. The system <NUM> can include a data processing system <NUM>. The data processing system <NUM> can communicate with one or more of a digital component provider device <NUM> (e.g., content provider device) or client computing devices <NUM> via a network <NUM>. The network <NUM> can include computer networks such as the Internet, local, wide, metro, or other area networks, intranets, satellite networks, and other communication networks such as voice or data mobile telephone networks. The network <NUM> can be used to access information resources such as web pages, web sites, domain names, or uniform resource locators that can be presented, output, rendered, or displayed on at least one computing device <NUM>, such as a laptop, desktop, tablet, digital assistant, personal digital assistant, smartwatch, wearable device, smart phone, portable computers, or speaker. For example, via the network <NUM> a user of the client computing device <NUM> can access information or data provided by a digital component provider device <NUM>. The client computing device <NUM> may or may not include a display. For example, the client computing device <NUM> may include limited types of user interfaces, such as a microphone and speaker (e.g., the client computing device <NUM> can include a voice-drive or audio-based interface). The primary user interface of the computing device <NUM> can include a microphone and speaker.

The network <NUM> can include or constitute a display network, e.g., a subset of information resources available on the internet that are associated with a content placement or search engine results system, or that are eligible to include third party digital components. The network <NUM> can be used by the data processing system <NUM> to access information resources such as web pages, web sites, domain names, or uniform resource locators that can be presented, output, rendered, or displayed by the client computing device <NUM>. For example, via the network <NUM> a user of the client computing device <NUM> can access information or data provided by the digital component provider device <NUM>.

The network <NUM> may be any type or form of network and may include any of the following: a point-to-point network, a broadcast network, a wide area network, a local area network, a telecommunications network, a data communication network, a computer network, an ATM (Asynchronous Transfer Mode) network, a SONET (Synchronous Optical Network) network, a SDH (Synchronous Digital Hierarchy) network, a wireless network and a wireline network. The network <NUM> may include a wireless link, such as an infrared channel or satellite band. The topology of the network <NUM> may include a bus, star, or ring network topology. The network may include mobile telephone networks using any protocol or protocols used to communicate among mobile devices, including advanced mobile phone protocol ("AMPS"), time division multiple access ("TDMA"), code-division multiple access ("CDMA"), global system for mobile communication ("GSM"), general packet radio services ("GPRS") or universal mobile telecommunications system ("UMTS"). Different types of data may be transmitted via different protocols, or the same types of data may be transmitted via different protocols.

The system <NUM> can include at least one data processing system <NUM>. The data processing system <NUM> can include at least one logic device such as a computing device having a processor to communicate via the network <NUM>, for example, with the computing device <NUM> or the digital component provider device <NUM>. The data processing system <NUM> can include at least one computation resource, server, processor or memory. For example, the data processing system <NUM> can include a plurality of computation resources or servers located in at least one data center. The data processing system <NUM> can include multiple, logically-grouped servers and facilitate distributed computing techniques. The logical group of servers may be referred to as a data center, server farm or a machine farm. The servers can also be geographically dispersed. A data center or machine farm may be administered as a single entity, or the machine farm can include a plurality of machine farms. The servers within each machine farm can be heterogeneous - one or more of the servers or machines can operate according to one or more type of operating system platform.

Servers in the machine farm can be stored in high-density rack systems, along with associated storage systems, and located in an enterprise data center. For example, consolidating the servers in this way may improve system manageability, data security, the physical security of the system, and system performance by locating servers and high performance storage systems on localized high performance networks. Centralization of all or some of the data processing system <NUM> components, including servers and storage systems, and coupling them with advanced system management tools allows more efficient use of server resources, which saves power and processing requirements and reduces bandwidth usage.

The client computing device <NUM> can include, execute, interface, or otherwise communicate with one or more of at least one local digital assistant <NUM>, at least one sensor <NUM>, at least one transducer <NUM>, at least one audio driver <NUM>, or at least one display <NUM>. The sensor <NUM> can include, for example, a camera, an ambient light sensor, proximity sensor, temperature sensor, accelerometer, gyroscope, motion detector, GPS sensor, location sensor, microphone, video, image detection, or touch sensor. The transducer <NUM> can include or be part of a speaker or a microphone. The audio driver <NUM> can provide a software interface to the hardware transducer <NUM>. The audio driver <NUM> can execute the audio file or other instructions provided by the data processing system <NUM> to control the transducer <NUM> to generate a corresponding acoustic wave or sound wave. The display <NUM> can include one or more hardware or software component configured to provide a visual indication or optical output, such as a light emitting diode, organic light emitting diode, liquid crystal display, laser, or display.

The local digital assistant <NUM> can include or be executed by one or more processors, logic array, or memory. The local digital assistant <NUM> can detect a keyword and perform an action based on the keyword. The local digital assistance <NUM> can be an instance of the remote digital assistance component <NUM> executed at the data processing system <NUM> or can perform any of the functions of the remote digital assistance component <NUM>. The local digital assistant <NUM> can filter out one or more terms or modify the terms prior to transmitting the terms as data to the data processing system <NUM> (e.g., remote digital assistant component <NUM>) for further processing. The local digital assistant <NUM> can convert the analog audio signals detected by the transducer <NUM> into a digital audio signal and transmit one or more data packets carrying the digital audio signal to the data processing system <NUM> via the network <NUM>. The local digital assistant <NUM> can transmit data packets carrying some or all of the input audio signal responsive to detecting an instruction to perform such transmission. The instruction can include, for example, a trigger keyword or other keyword or approval to transmit data packets comprising the input audio signal to the data processing system <NUM>.

The local digital assistant <NUM> can perform a pre-filtering or pre-processing on the input audio signal to remove certain frequencies of audio. The pre-filtering can include filters such as a low-pass filter, high-pass filter or a bandpass filter. The filters can be applied in the frequency domain. The filters can be applied using a digital signal processing techniques. The filter can be configured to keep frequencies that correspond to a human voice or human speech, while eliminating frequencies that fall outside the typical frequencies of human speech. For example, a bandpass filter can be configured to remove frequencies below a first threshold (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM>) and above a second threshold (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM>). Applying a bandpass filter can reduce computing resource utilization in downstream processing. The local digital assistant <NUM> on the computing device <NUM> can apply the bandpass filter prior to transmitting the input audio signal to the data processing system <NUM>, thereby reducing network bandwidth utilization. However, based on the computing resources available to the computing device <NUM> and the available network bandwidth, it may be more efficient to provide the input audio signal to the data processing system <NUM> to allow the data processing system <NUM> to perform the filtering.

The local digital assistant <NUM> can apply additional pre-processing or pre-filtering techniques such as noise reduction techniques to reduce ambient noise levels that can interfere with natural language processor. Noise reduction techniques can improve accuracy and speed of natural language processor, thereby improving the performance of the data processing system <NUM> and manage rendering of a graphical user interface provided via the display <NUM>.

The client computing device <NUM> can be associated with an end user that enters voice queries as audio input into the client computing device <NUM> (via the sensor <NUM> or transducer <NUM>) and receives audio (or other) output from the data processing system <NUM> or digital component provider device <NUM> to present, display, or render to the end user of the client computing device <NUM>. The digital component can include a computer-generated voice that can be provided from the data processing system <NUM> or digital component provider device <NUM> to the client computing device <NUM>. The client computing device <NUM> can render the computer-generated voice to the end user via the transducer <NUM> (e.g., a speaker). The computer-generated voice can include recordings from a real person or computer generated language. The client computing device <NUM> can provide visual output via a display device <NUM> communicatively coupled to the computing device <NUM>.

The end user that enters the voice queries to the client computing device <NUM> can be associated with multiple client computing devices <NUM>. For example, the end user can be associated with a first client computing device <NUM> that can be a speaker-based digital assistant device, a second client computing device <NUM> that can be a mobile device (e.g., a smartphone), and a third client computing device <NUM> that can be a desktop computer. The data processing system <NUM> can associate each of the client computing devices <NUM> through a common login, location, network, or other linking data. For example, the end user may log into each of the client computing devices <NUM> with the same account user name and password.

The client computing device <NUM> can receive an input audio signal detected by a sensor <NUM> (e.g., microphone) of the computing device <NUM>. The input audio signal can include, for example, a query, question, command, instructions, or other statement provided in a language. The input audio signal can include an identifier or name of a third-party (e.g., a digital component provider device <NUM>) to which the question or request is directed. For example, the query can include the name of the subscription-based music service (an example digital component provider device <NUM>) in the input audio signal in order to instruct the data processing system <NUM> to provide the request to the specified subscription-based music service. For example, the input audio signal can include "Play my music playlist on XYZ Music Service. " The music service can provide the songs associated with the playlist to the client computing device <NUM> through the network <NUM> or to the data processing system <NUM>, which can provide the songs associated with the playlist to the client computing device <NUM> through the network <NUM>.

The client computing device <NUM> can include, execute, or be referred to as a digital assistant device. The digital assistant device can include one or more components of the computing device <NUM>. The digital assistant device can include a graphics driver that can receive display output from the data processing system <NUM>, and render the display output on display <NUM>. The graphics driver can include hardware or software components that control or enhance or how graphics or visual output is displayed on the display <NUM>. The graphics driver can include, for example, a program that controls how the graphic components work with the rest of the computing device <NUM> (or digital assistant). The local digital assistant <NUM> can filter the input audio signal to create a filtered input audio signal, convert the filtered input audio signal to data packets, and transmit the data packets to a data processing system comprising one or more processors and memory.

The digital assistant device can include an audio driver <NUM> and a speaker component (e.g., transducer <NUM>). The pre-processor component <NUM> to receive an indication of the display output and instruct the audio driver <NUM> to generate an output audio signal to cause the speaker component (e.g., transducer <NUM>) to transmit an audio output corresponding to the indication of the display output.

The system <NUM> can include, access, or otherwise interact with at least digital component provider device <NUM>. The digital component provider device <NUM> can include one or more servers that can provide digital components to the client computing device <NUM> or data processing system <NUM>. The digital component provider device <NUM> or components thereof can be integrated with the data processing system <NUM>, or executed at least partially by the data processing system <NUM>. The digital component provider device <NUM> can include at least one logic device such as a computing device having a processor to communicate via the network <NUM>, for example with the computing device <NUM>, the data processing system <NUM>, or the digital component provider device <NUM>. The digital component provider device <NUM> can include at least one computation resource, server, processor or memory. For example, the digital component provider device <NUM> can include a plurality of computation resources or servers located in at least one data center.

A digital component provider device <NUM> can provide audio, visual, or multimedia based digital components for presentation by the client computing device <NUM> as an audio output digital component or visual output digital components. The digital component can be or include a digital content. The digital component can be or include a digital object. The digital component can include subscription-based content or pay-for content. A digital component can include a plurality of digital content items. For example, a digital component can be a data stream from a streaming music service (e.g., the digital component provider device <NUM>). The streamed digital component can include multiple songs as different digital content items. The digital components can include or can be digital movies, websites, songs, applications (e.g., smartphone or other client device applications), or other text-based, audio-based, image-based, or video-based content.

The digital component provider device <NUM> can provide the digital components to the client computing device <NUM> via the network <NUM> and bypass the data processing system <NUM>. The digital component provider device <NUM> can provide the digital component to the client computing device <NUM> via the network <NUM> and data processing system <NUM>. For example, the digital component provider device <NUM> can provide the digital components to the data processing system <NUM>, which can store the digital components and provide the digital components to the client computing device <NUM> when requested by the client computing device <NUM>.

The data processing system <NUM> can include at least one computation resource or server. The data processing system <NUM> can include, interface, or otherwise communicate with at least one interface <NUM>. The data processing system <NUM> can include, interface, or otherwise communicate with at least one remote digital assistant component <NUM>. The remote digital assistant component <NUM> can include, interface, or otherwise communicate with at least one natural language processor component <NUM>. The data processing system <NUM> can include, interface, or otherwise communicate with at least one digital component selector <NUM>. The data processing system <NUM> can include, interface, or otherwise communicate with at least one authorization component <NUM>. The data processing system <NUM> can include, interface, or otherwise communicate with at least one data repository <NUM>. The at least one data repository <NUM> can include or store, in one or more data structures or databases, deep links <NUM>, payload policies <NUM>, event identifiers <NUM>, or content data <NUM>. The data repository <NUM> can include one or more local or distributed databases, and can include a database management.

The interface <NUM>, remote digital assistant component <NUM>, the natural language processor component <NUM>, the digital component selector <NUM>, and the authorization component <NUM> can each include at least one processing unit or other logic device such as programmable logic array engine, or module configured to communicate with the database repository or database <NUM>. The interface <NUM>, the remote digital assistant component <NUM>, the natural language processor component <NUM>, the digital component selector <NUM>, the authorization component <NUM>, and the data repository <NUM> can be separate components, a single component, or part of multiple data processing systems <NUM>. The system <NUM> and its components, such as a data processing system <NUM>, can include hardware elements, such as one or more processors, logic devices, or circuits.

The data processing system <NUM> can include an interface <NUM>. The interface <NUM> can be configured, constructed, or operational to receive and transmit information using, for example, data packets. The interface <NUM> can receive and transmit information using one or more protocols, such as a network protocol. The interface <NUM> can include a hardware interface, software interface, wired interface, or wireless interface. The interface <NUM> can facilitate translating or formatting data from one format to another format. For example, the interface <NUM> can include an application programming interface that includes definitions for communicating between various components, such as software components.

The data processing system <NUM> can include an application, script or program installed at the client computing device <NUM>, such as a local digital assistant <NUM> to communicate input audio signals to the interface <NUM> of the data processing system <NUM> and to drive components of the client computing device to render output audio signals or visual output. The data processing system <NUM> can receive data packets, a digital file, or other signals that include or identify an input audio signal (or input audio signals). The computing device <NUM> can detect the audio signal via the transducer <NUM>, and convert the analog audio signal to a digital file via an analog-to-digital converter. For example, the audio driver <NUM> can include an analog-to-digital converter component. The pre-processor component <NUM> can convert the audio signals to a digital file that can be transmitted via data packets over network <NUM>.

The remote digital assistant component <NUM> of the data processing system <NUM> can execute or run an NLP component <NUM> to receive or obtain the data packets including the input audio signal detected by the sensor <NUM> of the computing device <NUM>. The data packets can provide a digital file. The NLP component <NUM> can receive or obtain the digital file or data packets comprising the audio signal and parse the audio signal. For example, the NLP component <NUM> can provide for interactions between a human and a computer. The NLP component <NUM> can be configured with techniques for understanding natural language and enabling the data processing system <NUM> to derive meaning from human or natural language input. The NLP component <NUM> can include or be configured with techniques based on machine learning, such as statistical machine learning. The NLP component <NUM> can utilize decision trees, statistical models, or probabilistic models to parse the input audio signal. The NLP component <NUM> can perform, for example, functions such as named entity recognition (e.g., given a stream of text, determine which items in the text map to proper names, such as people or places, and what the type of each such name is, such as person, location, or organization), natural language generation (e.g., convert information from computer databases or semantic intents into understandable human language), natural language understanding (e.g., convert text into more formal representations such as first-order logic structures that a computer module can manipulate), machine translation (e.g., automatically translate text from one human language to another), morphological segmentation (e.g., separating words into individual morphemes and identify the class of the morphemes, which can be challenging based on the complexity of the morphology or structure of the words of the language being considered), question answering (e.g., determining an answer to a human-language question, which can be specific or open-ended), semantic processing (e.g., processing that can occur after identifying a word and encoding its meaning in order to relate the identified word to other words with similar meanings).

The NLP component <NUM> can convert the input audio signal into recognized text by comparing the input signal against a stored, representative set of audio waveforms (e.g., in the data repository <NUM>) and choosing the closest matches. The set of audio waveforms can be stored in data repository <NUM> or other database accessible to the data processing system <NUM>. The representative waveforms are generated across a large set of users, and then may be augmented with speech samples from the user. After the audio signal is converted into recognized text, the NLP component <NUM> matches the text to words that are associated, for example via training across users or through manual specification, with actions that the data processing system <NUM> can serve. The NLP component <NUM> can convert image or video input to text or digital files. The NLP component <NUM> can process, analyze or interpret image or video input to perform actions, generate requests, or select or identify data structures.

The data processing system <NUM> can receive image or video input signals, in addition to, or instead of, input audio signals. The data processing system <NUM> can process the image or video input signals using, for example, image interpretation techniques, computer vision, a machine learning engine, or other techniques to recognize or interpret the image or video to convert the image or video to a digital file. The one or more image interpretation techniques, computer vision techniques, machine learning techniques can be collectively referred to as imaging techniques. The data processing system <NUM> (e.g., the NLP component <NUM>) can be configured with the imaging techniques, in addition to, or instead of, audio processing techniques.

The NLP component <NUM> can obtain the input audio signal. From the input audio signal, the NLP component <NUM> can identify at least one request or at least one trigger keyword corresponding to the request. The request can indicate intent, digital components, or subject matter of the input audio signal. The trigger keyword can indicate a type of action likely to be taken. For example, the NLP component <NUM> can parse the input audio signal to identify at least one request to leave home for the evening to attend dinner and a movie. The trigger keyword can include at least one word, phrase, root or partial word, or derivative indicating an action to be taken. For example, the trigger keyword "go" or "to go to" from the input audio signal can indicate a need for transport. In this example, the input audio signal (or the identified request) does not directly express an intent for transport, however the trigger keyword indicates that transport is an ancillary action to at least one other action that is indicated by the request.

The NLP component <NUM> can parse the input audio signal to identify, determine, retrieve, or otherwise obtain the request and the trigger keyword. For instance, the NLP component <NUM> can apply a semantic processing technique to the input audio signal to identify the trigger keyword or the request. The NLP component <NUM> can apply the semantic processing technique to the input audio signal to identify a trigger phrase that includes one or more trigger keywords, such as a first trigger keyword and a second trigger keyword. For example, the input audio signal can include the sentence "Play my favorite song. " The NLP component <NUM> can determine that the input audio signal includes a trigger keyword "play. " The NLP component <NUM> can determine that the request is for the end user's favorite song (a digital component). The NLP component <NUM> can identify an application identifier or a digital component provider device <NUM> identifier in the input audio signal. The application identifier or digital component provider device <NUM> identifier can indicate which application or digital component provider device <NUM> the end user would like to fill the request.

The data processing system <NUM> can execute or run an instance of the authorization component <NUM>. The authorization component <NUM> can enable the data processing system <NUM> to perform delayed, two-factor authentication. The digital component identified by the NLP component <NUM> in the input audio signal can be provided to the client computing device <NUM> from a digital component provider device <NUM>. To provide the digital component to the client computing device <NUM>, the digital component provider device <NUM> or the data processing system <NUM> can require authorization. The authorization component <NUM> can enable a portion of the digital component to be transmitted or streamed to the client computing device <NUM> responsive to the request for the digital component and before the transmission of the full digital component is authorized. For example, the portion of the digital component can be transmitted to the client computing device <NUM> before authorization of the client computing device has started or has been completed.

The authorization component <NUM> can include a state machine that can determine whether the client computing device <NUM> is authorized to receive digital components from the digital component provider device <NUM> and whether the digital component provider device <NUM> is enabled for the client computing device <NUM>. Once the digital component provider device <NUM> is enabled for the client computing device <NUM>, the default state for the client computing device <NUM> can be a non-authorized state. When in the non-authorized state, the authorization component <NUM> may only provide portions of requested digital components to the client computing device <NUM>.

Based on receiving the request for a digital component, the digital component selector <NUM> can select a portion of the digital component to transmit to the first client computing device <NUM> that transmitted the input audio signal to the data processing system <NUM>. Based at least on transmitting the portion of the first digital component to the first client device, the authorization component <NUM> can transmit an authorization request to a second client device. The authorization request can include a request to authorize transmission of a second portion (or the remainder) of the requested digital component to the first client computing device <NUM>. The authorization request can include a digital message or other engagement signal that can be transmitted or pushed to the client computing device <NUM>. For example, the authorization request can include a notification, SMS, email, or other electronic message that is transmitted from the data processing system <NUM> to the second client computing device <NUM>.

The authorization component <NUM> can select a dialog component, action identifier or event identifier, or other parameters to include in the authorization request. The dialog component can include deep links selected from the deep links <NUM> stored in the data repository <NUM>. Execution of the deep link at the client computing device <NUM> can cause the client computing device <NUM> to open a predetermined application executed on the client computing device <NUM>. The deep link can include information that is populated into one or more fields of the open application's window. Rendering the authorization request at the second client computing device <NUM> can cause the second client computing device <NUM> to present dialog including a confirm option or a reject option.

The authorization component <NUM> can receive via the interface <NUM> and network <NUM> a confirmation message. The client computing device <NUM> can generate the confirmation message in response the activation of the confirm option. For example, the authorization request can cause the client computing device <NUM> to display a notification window asking the end user of the client computing device <NUM> whether the user would like to authenticate the transmission of a digital component to a different client computing device <NUM> associated with the end user (e.g., the client computing device <NUM> that transmitted the input audio signal to the data processing system <NUM>). The notification window can render the confirm option as an accept button and the rejection option as a decline button. Selection of the confirm option can cause the client computing device <NUM> to generate and transmit the confirmation message to the data processing system <NUM>. Selection of the reject option can cause the client computing device <NUM> to generate and transmit a declining message to the data processing system <NUM>.

The authorization request can include a request to transmit a predetermined or requested digital component to the client computing device <NUM>. The authorization request can include a request to begin a subscription (e.g., a streaming music subscription) with the digital component provider device <NUM> that is required for the digital component to be transmitted to the client computing device <NUM>.

The confirmation message can include an authorization token and the action or event identifier of the authorization request. The authorization component <NUM> can update the state machine based on receiving the authorization token to indicate that the client computing device <NUM> that transmitted the input audio signal to the data processing system <NUM> is authorized to receive the second portion of the digital component or additional digital components from the digital component provider device <NUM>.

The authorization component <NUM> can reference the event identifiers <NUM> to determine whether the client computing device <NUM> previously established a connection with the digital component provider device <NUM> or requested digital components from the digital component provider device <NUM>. The authorization component <NUM> can store an indication of the request in association with an identifier of the client computing device <NUM> as an event identifier <NUM>. The authorization component <NUM> may only store the indication of the request if the authorization component <NUM> does not receive a confirmation message in response to the authorization request to provide the digital component. For example, the data processing system <NUM> can receive an input audio signal requesting that a song be streamed to a first client computing device <NUM>. In response to the request, the authorization component <NUM> can transmit an authorization request to a second client computing device <NUM> that is associated with the first client computing device <NUM>. The data processing system <NUM> can transmit a first portion of the requested song to the first client computing device <NUM>. If the authorization component <NUM> does not receive a confirmation message within a predetermined length of time, the authorization component <NUM> can store as an event identifier <NUM> an indication that at least portion of the requested song was transmitted to the first client computing device <NUM>.

The authorization component <NUM> can decline the request for a digital component based on the at least a portion of the digital component being previously transmitted to the client computing device <NUM> or the client computing device <NUM> previously requesting digital components from the digital component provider device <NUM>. The authorization component <NUM> can use a unique identifier associated with the client computing device <NUM> to lookup in the event identifiers <NUM> whether the requested digital component (or a digital component from the same digital component provider device <NUM>) was previously transmitted to the client computing device <NUM>. For example, the data processing system <NUM> can receive an input audio signal requesting a music playlist be streamed to the client computing device <NUM> from the digital component provider device <NUM>. The authorization component <NUM> can determine if the client computing device <NUM> previously requested the streaming of a playlist or other digital components from the digital component provider device <NUM>. If the authorization component <NUM> determines digital components were previously streamed or transmitted to the client computing device <NUM> (without the authorization component <NUM> receiving a confirmation message), the authorization component <NUM> can prevent the data processing system <NUM> from streaming the requested playlist (or a portion thereof) to the client computing device <NUM>.

The authorization component <NUM> can shorten the length or duration of the portion of the digital component transmitted to the client computing device <NUM> transmitted prior to the receipt of an authorization message based on the number of times the client computing device <NUM> requested the digital component without the authorization component <NUM> receiving a confirmation message. For example, the first time the client computing device <NUM> requests a movie (e.g., a digital component) from the digital component provider device <NUM>, the authorization component <NUM> can select or authorize a <NUM>-minute portion of the movie be transmitted to the client computing device <NUM> without receiving a confirmation message. The second time the client computing device <NUM> requests a movie from the digital component provider device <NUM>, the authorization component <NUM> can select or authorize a <NUM>-minute portion of the movie to be transmitted to the client computing device <NUM> without receiving a confirmation message. For each subsequent request, the authorization component <NUM> can authorize or select smaller (or shorter) subportions of the portion of the digital component transmitted to the client computing device <NUM> based on the first request for a digital component.

The digital component selector <NUM> can select a digital component that includes text, strings, characters, video files, image files, or audio files that can be processed by the client computing device <NUM> and presented to the user via the display <NUM> or the transducer <NUM> (e.g., speaker). The digital component selector <NUM> can select a digital component that is in responsive to the request identified by the NLP component <NUM> in the input audio signal. The digital component selector <NUM> can select which digital component provider device <NUM> should or can fulfill the request and can forward the request to the digital component provider device <NUM>. For example, the data processing system <NUM> can initiate a session between the digital component provider device <NUM> and the client computing device <NUM> to enable the digital component provider device <NUM> to transmit the digital component to the client computing device <NUM>. The digital component selector <NUM> can request digital component from the digital component provider device <NUM>. The digital component provider device <NUM> can provide digital components to the data processing system <NUM>, which can store the digital components in the data repository <NUM>. Responsive to a request for a digital component, the digital component selector <NUM> can retrieve the digital component from the data repository <NUM>.

In response to a request for a digital component, for example, the digital component selector <NUM> can select a portion of the digital component to provide the client computing device <NUM> in response to the request. The digital component selector <NUM> can select a portion of the digital component that corresponds to a duration or length set by the authorization component <NUM>.

The digital component selector <NUM> can select multiple digital components via a real-time content selection process. The digital component selector <NUM> can score and rank the digital components, and provide multiple digital components to the output merger component <NUM> to allow the output merger component <NUM> to select the highest ranking digital component. The digital component selector <NUM> can select one or more additional digital components that are transmitted to a second client computing device <NUM> based on an input audio signal (or keywords and requests contained therein). The one or more additional digital components can be transmitted to the second client computing device <NUM> as part of or in addition to the authorization request. For example, if the input audio signal from the first client computing device <NUM> includes a request for a digital component from a first digital component provider device <NUM>, the digital component selector <NUM> can select one or more digital components that correspond to one or more related digital component provider devices <NUM>. In one illustrative example, the input audio signal can include a request to start a streaming music to a first client computing device <NUM>. The digital component selector <NUM> can select additional digital components (e.g., ads) are associated with a different digital component provider device <NUM>. The data processing system <NUM> can include the additional digital components in the authorization request to the second client computing device <NUM>. The additional digital components can inform an end user of additional or related digital component provider devices <NUM> that could fulfill the request from the first client computing device <NUM>.

The digital component selector <NUM> can provide the selected digital component selected in response to the request identified in the input audio signal to the computing device <NUM> or local digital assistant <NUM> or application executing on the computing device <NUM> for presentation. Thus, the digital component selector <NUM> can receive the content request from the client computing device <NUM>, select, responsive to the content request, a digital component, and transmit, to the client computing device <NUM>, the digital component for presentation. The digital component selector <NUM> can transmit, to the local digital assistant <NUM>, the selected digital component for presentation by the local digital assistant <NUM> itself or a third-party application executed by the client computing device <NUM>. For example, the local digital assistant <NUM> can play or output an audio signal corresponding to the selected digital component.

The data repository <NUM> can store deep links <NUM> that can be stored in one or more data structures or data files. The deep links <NUM> can be stored in a table or database. The deep links126 can include links, pointers, references, or other address or location information of an application that can be executed by the client computing device <NUM>. A deep link to an application can refer to a uniform resource locator or hyperlink that links to a specific resource, web content, application, or view within an application. The deep link can include the information used to point to a particular resource or application, launch an application, or populate predetermined fields within the application. Deep links can include uniform resource identifiers ("URI") that links to a specific location within a mobile application in addition to launching the application. For example, opening, selecting, or executing a deep link on the client computing device <NUM> can cause the client computing device <NUM> to open an application associated with the digital component provider device <NUM>. The deep link fully or partially pre-populate a registration or sign-up form within the opened application. In this example, to register for the subscription service offered by the digital component provider device <NUM>, the end user may need to only review the information entered into the form and then select a confirmation icon located on the loaded application page. The deep links <NUM> data structure can include a hash table that maps application names or views of an application to a deep link.

The data repository <NUM> can store payload policies <NUM> that can be stored in one or more data structures or data files. The payload policies <NUM> can indicate what data or information should be included in a deep link <NUM> when the deep link <NUM> is generated. The data processing system <NUM> can store a different payload policy <NUM> for each of the digital component provider devices <NUM> associated with the data processing system <NUM>. The payload policies <NUM> can indicate to the data processing system <NUM> what information a digital component provider device <NUM> may need to begin or continue a subscription service or purchase process. For example, a payload policy <NUM> can indicate if an account name or credit card number are needed when registering with the digital component provider device <NUM>. The payload policy <NUM> can also indicate to the data processing system <NUM> if the data processing system <NUM> can automatically include the information in a deep link <NUM>, is not allowed to include the information in a deep link <NUM>, or must receive end user approval before including the information in the deep link <NUM>.

The data repository <NUM> can store event identifiers <NUM> as one or data structures or data files. As described herein, the authorization component <NUM> can monitor or count the number of times that a client computing device <NUM> establishes a connection with a digital component provider device <NUM> or requests digital components from the digital component provider device <NUM> without registering or authenticating with the digital component provider device <NUM> or data processing system <NUM>. The event identifiers <NUM> can refer to aspects of current and past requests a client computing device <NUM> makes with a digital component provider device <NUM> or the data processing system <NUM>. The event identifiers <NUM> can include one or more data structures that can indicate when and the duration of connections between a client computing device <NUM> and a digital component provider device <NUM> that were not authorized by an end user. The event identifiers can include an indication of the input audio file (e.g., a unique identifier), an indication of to which digital component provider device <NUM> the request was directed, and an indication (e.g., hash) of the client computing device <NUM> that included the input audio file.

The data repository <NUM> store content data <NUM> that can include, for example, digital components provided by a digital component provider device <NUM> or obtained or determined by the data processing system <NUM> to facilitate content selection. The content data <NUM> can include, for example, digital components (or digital component object) that can include, for example, a content item, an online document, audio, images, video, multimedia content, or third-party content. The digital component provider device <NUM> can provide full-length digital components to the data processing system <NUM> to store as content data <NUM>. The digital component provider device <NUM> can provide subportions of the digital components to the data processing system <NUM>. The data processing system <NUM> can provide the subportions of the digital components to the client computing device <NUM> until the account or subscription through which the client computing device <NUM> accesses the digital components is authorized. The subportions of the digital components can include the first predetermined minutes or seconds of a digital component (e.g., a song, TV show, movie, or other video) or sample associated with the requested digital component. For example, if the digital component is a movie, the sample that is transmitted to the data processing system <NUM> as a subportion can be the trailer for the movie.

<FIG> illustrates a block diagram of an example method <NUM> to authenticate computing devices. The method <NUM> can include receiving an input signal (ACT <NUM>). The method <NUM> can include parsing the input signal (ACT <NUM>). The method <NUM> can include transmitting a first portion of a digital component to a client computing device (ACT <NUM>). The method <NUM> can include transmitting an authorization request (ACT <NUM>). The method <NUM> can include receiving a confirmation message (ACT <NUM>). The method <NUM> can include transmitting a second portion of the digital component to the client computing device (ACT <NUM>).

The method <NUM> can be performed by one or more component or system illustrated in <FIG>, <FIG>, or <FIG>. As set forth above, the method <NUM> can include receiving an input signal (ACT <NUM>). The method can include receiving, by a natural language processor component executed by a data processing system, the input signal. The input signal can be an input audio signal that is detected by a sensor at a first client device. The sensor can be a microphone of the first client device. For example, a digital assistant component executed at least partially by a data processing system that includes one or more processors and memory can receive the input audio signal. The input audio signal can include a conversation facilitated by a digital assistant. The conversation can include one or more inputs and outputs. The conversation can be audio based, text based, or a combination of audio and text. The input audio signal can include text input, or other types of input that can provide conversational information. The data processing system can receive the audio input for a session corresponding to the conversation. The data processing system can receive the audio input in one or more portions or as a bulk or batch upload (e.g., multiple portions of the conversations uploaded in a single transmission to reduce the number of transmissions).

The method <NUM> can include parsing the input signal (ACT <NUM>). The NLP component of the data processing system can parse the input signal to identify a digital component request. The NLP component can identify a trigger keyword in the input signal. For example, the input audio signal can include "OK, play today's top hits from my music service. " The NLP component can parse the input signal to determine the requested digital component is a music playlist of "top hits. " The NLP component can determine that the trigger keyword is to play, which can indicate that the end user wants to start streaming the songs on the music playlist to the client computing device. The data processing system can determine that my music service is the digital component provider device that the end user is requesting provide digital components (e.g., songs).

The method <NUM> can include transmitting a first portion of a digital component (ACT <NUM>). The digital component selector can select a digital component based on the request identified in the input audio signal. The digital component can include a song, stream or plurality of songs, video, application, image, or other digital content. The portion of the digital component can be or include a segment of the digital component (e.g., a video segment of the first few minutes of a video file) or a digital component related to the requested digital component. For example, the portion of the digital component can include trailer, teaser, or other content related to the requested digital component. The data processing system can transmit the request to the digital component provider device, which can provide the portion of the digital component to the client computing device. The data processing system can store digital components and portions thereof provided by the digital component provider device in the data repository, and the data processing system can provide the digital components and portions thereof to the client computing device. The data processing system can establish a connection between the digital component provider device and the client computing device to enable the digital component provider device to provide the digital components and portions thereof to the client computing device. The data processing system can transmit or initiation the transmission of the portion of the digital component to the client computing device without completing an authorization of the client computing device. For example, if the digital component is part of a subscription service or a pay-for content item, the data processing system can transmit the portion of the digital component to the client computing device without requiring payment or the end user of the client computing device to sign up for the required subscription.

The method <NUM> can include transmitting an authorization request (ACT <NUM>). The client computing device can receive and begin to render, play, or present the portion of the digital component to the end user of the client computing device prior to requiring payment, login, or authorization to render, play, or present the digital component to the user via the client computing device. The authorization component can transmit the authorization request to a second client computing device. The second client computing device can be associated with the first client computing device. For example, both the first and the second client computing device can be registered to the same end user. The authorization request can include a request to transmit a second portion of the digital component to the first client computing device. For example, the request identified at ACT <NUM> can be to stream music to the client computing device to a speaker-based assistant device. The first portion of the digital component can be a stream of the music limited to five minutes in duration. In this example, as the first client computing device plays the five-minute stream of the music, the authorization component can transmit the authentication request to a second client computing device. The second client computing device can be the end user's mobile device. The authorization request can include deep links that cause a registration page associated with the digital component provider device providing the streaming music to open. The deep link can include information that is populated into the registration page.

The method <NUM> can include receiving a confirmation message (ACT <NUM>). The data processing system can receive the confirmation message from the client computing device to which the authorization request was transmitted. The data processing system can transmit the authorization request to and receive the confirmation message from a second client computing device that is different from the client computing device to which the first portion of the digital component was transmitted. The data processing system can receive the confirmation message from the digital component provider device. For example, the authorization request can include a deep-link that populates a registration page to register with a service provided by the digital component provider device. Accepting the authorization request at the second client computing device can cause the second client computing device to transmit the registration information to the digital component provider device to, for example, create an account with the digital component provider device. Once the end user's account is established at the digital component provider device (based on receiving the registration information), the digital component provider device can transmit a message to the data processing system with confirmation message indicating the end user is registered with the digital component provider device.

The method <NUM> can include transmitting a second portion of the digital component (ACT <NUM>). The data processing system can transmit a second portion of the digital component to the digital component that received the first portion of the digital component. The second portion of the digital component can be the remaining portion of the digital component that was not included in the first portion. The second portion of the digital component can be additional digital components. For example, the first portion can be a first song in a playlist and the second portion can the subsequent songs in the playlist.

<FIG> illustrates a block diagram of the system <NUM> and the network transmissions between the components of the system <NUM> during, for example, the acts of method <NUM>.

The client computing device <NUM>(<NUM>) can receive an audio signal from an end user. The client computing device <NUM>(<NUM>) can detect the audio signal with a sensor, such a microphone. The client computing device <NUM>(<NUM>) can convert the audio signal into an input audio signal and transmit the input audio signal to the data processing system <NUM> in transmission <NUM>. The transmission <NUM> (and the other transmission illustrated in <FIG>) can be established over a network similar to the network <NUM> illustrated in <FIG>. The input audio signal can include a request for a digital component that is provided to the client computing device <NUM>(<NUM>) by the digital component provider device <NUM>. The digital component provider device <NUM> can provide the digital component directly over the network <NUM> to the client computing device <NUM>(<NUM>) or through the data processing system <NUM>. The digital components provided by the digital component provider device <NUM> can be provided as part of a subscription (e.g., streaming music service) or are pay-for content (e.g., a streaming movie).

Based on receiving the request in the input audio signal, the data processing system <NUM> and the digital component provider device <NUM> can provide a first portion of the digital component to the client computing device <NUM>. The data processing system <NUM>, through a transmission <NUM>, can instruct the digital component provider device <NUM> to transmit the first portion of the digital component to the digital component provider device <NUM>. The data processing system <NUM> can also establish a session between the digital component provider device <NUM> and the client computing device <NUM>. Through the transmission <NUM>, the data processing system <NUM> can interact with the digital component provider device <NUM> through an API call to the services or digital components provided by the digital component provider device <NUM>. The digital component provider device <NUM> can transmit the first portion to the client computing device <NUM> via a transmission <NUM> to the client computing device <NUM>(<NUM>). The first portion can be transmitted in bulk or batch transmissions or the first portion of the digital component can be streamed to the client computing device <NUM>.

The data processing system <NUM> can determine whether the client computing device <NUM>(<NUM>) previously requested digital components from the digital component provider device <NUM>. If the client computing device <NUM>(<NUM>) previously requested digital components from the digital component provider device <NUM>, the data processing system <NUM> can decline to transmit the first portion of the digital component to the client computing device <NUM>(<NUM>). The data processing system <NUM> can decline to transmit the first portion of the digital component to the client computing device <NUM>(<NUM>) but can transmit the authorization request to the client computing device <NUM>(<NUM>). If the data processing system <NUM> receives a confirmation message from the client computing device <NUM>(<NUM>), the data processing system <NUM> may then transmit the requested digital component to the client computing device <NUM>(<NUM>).

In response to or before the transmission of the first portion of the digital component to the client computing device <NUM>(<NUM>), the data processing system <NUM> can transmit an authorization request to the client computing device <NUM>(<NUM>) through a transmission <NUM>. The client computing device <NUM>(<NUM>) and the client computing device <NUM>(<NUM>) can be associated with the same end user. If the service or digital components provided by the digital component provider device <NUM> require a subscription, the authorization request can include information for starting a subscription with the digital component provider device <NUM> or can include a deep link that at least partially fills in fields of a registration form. The authorization request can be or include a message asking the user of the client computing device <NUM>(<NUM>) if the user would like to authorize the transmission of the digital component requested in the input audio signal to the client computing device <NUM>(<NUM>).

In response to receiving the authorization request, the client computing device <NUM>(<NUM>) can transmit a confirmation message to the data processing system <NUM> indicating that the end user of the client computing device <NUM>(<NUM>) authorizes transmission of the requested digital component to the client computing device <NUM>(<NUM>). If the end user does not wish to authorize the transmission of the digital component to the client computing device <NUM>(<NUM>), the end user can decline the authorization request causing the client computing device <NUM>(<NUM>) to transmit a declining message to the data processing system <NUM> in the transmission <NUM>. If the data processing system <NUM> does not receive a confirmation message from the client computing device <NUM>(<NUM>) within a predetermined time of transmitting the authorization request to the client computing device <NUM>(<NUM>), the data processing system <NUM> can register the non-response as if the data processing system <NUM> received a declining message. The client computing device <NUM>(<NUM>) can automatically transmit a declining message (or the data processing system <NUM> can register a non-response) based on a time delay between since an action or context occurred at the client computing device <NUM>(<NUM>). Once the time delay crosses a predetermined threshold, the client computing device <NUM>(<NUM>) can transmit the declining message to the data processing system <NUM>. The action can be the opening of the confirmation message, the receipt of the confirmation message, or the opening of an application, among others. For example, if the client computing device <NUM>(<NUM>) receives the confirmation message and the end user of the client computing device <NUM>(<NUM>) opens the confirmation message but does not enter a response, the confirmation message can time out once the predetermined time delay threshold is reached and automatically send the declining message to the data processing system <NUM>. The context can be a location context or an application context, among others. For example, the client computing device <NUM>(<NUM>) can automatically generate and transmit a declining message to the data processing system <NUM> if the end user does not respond to the confirmation message a predetermined amount of time after the context is initiated. The predetermined amount of time can be based on the action or the context. For example, if the context is a first location, such as the user's house, the predetermined time delay can be a first length of time, and if the context is a second location, such as in the user's car, the predetermined time delay may be longer or shorter.

The data processing system <NUM> can determine the client computing device <NUM>(<NUM>) is within a predetermined distance <NUM> of the client computing device <NUM>(<NUM>) and automatically generate a confirmation message to the authorization request. The predetermined distance <NUM> can be defined by a physical distance. For example, the predetermined distance can be defined by a radius of <NUM> ft, <NUM> ft, <NUM> ft, <NUM> ft, <NUM> ft, or more from the location of the client computing device <NUM>(<NUM>). The predetermined distance <NUM> can be defined by a geographical designation. For example, the predetermined distance <NUM> can include two locations within the same home, building, city, county, country, zip code, or other geographic region. The predetermined distance can be defined by a proximity between the client computing device <NUM>(<NUM>) and the client computing device <NUM>(<NUM>). The proximity can be defined by the distance over which the client computing device <NUM>(<NUM>) and the client computing device <NUM>(<NUM>) can establish a connection <NUM> with one another. For example, the predetermined distance <NUM> can be defined by a wireless or wired network, a Bluetooth link, or a sub-audible signal generated by one client computing device <NUM> and detected by the other client computing device <NUM>.

When the client computing device <NUM>(<NUM>) and the client computing device <NUM>(<NUM>) are within the predetermined distance <NUM> of one another, the client computing device <NUM>(<NUM>) can indicate that the client computing device <NUM>(<NUM>) is within the predetermined distance of the client computing device <NUM>(<NUM>) as metadata in the input audio signal. The client computing device <NUM>(<NUM>) can determine it is within the predetermined distance <NUM> of the client computing device <NUM>(<NUM>) and automatically respond to the authorization request. The authorization request can request different levels of authorization or information based on whether the client computing device <NUM>(<NUM>) is within the predetermined distance <NUM> of the client computing device <NUM>(<NUM>). For example, the client computing device <NUM>(<NUM>) may be able to respond to the authorization request without entering a password at the client computing device <NUM>(<NUM>) when the client computing device <NUM>(<NUM>) is within the predetermined distance, but the password may be required when the client computing device <NUM>(<NUM>) is not within the predetermined distance <NUM>.

In response to receiving the confirmation message, the data processing system <NUM> can establish send transmission <NUM> to the digital component provider device <NUM>. Via the transmission <NUM>, the data processing system <NUM> can instruct the digital component provider device <NUM> to transmit the second portion of the requested digital component to the client computing device <NUM>(<NUM>) or indicate to the digital component provider device <NUM> that an authorization message was received. Through a transmission <NUM>, the digital component provider device <NUM> can provide the second portion of the digital component to the client computing device <NUM>(<NUM>).

According to at least one aspect of the disclosure, the method may further include selecting, by the content selection component, a first digital component and a second digital component based at least on the first digital component request and transmitting, by the content selection component and to the second client device, the second digital component. The first client device and the second client device may both be associated with a same user. The method may further include receiving, by the natural language processor component, a second input audio signal detected by the sensor at the first client device. The second input audio signal may be parsed by the natural language processor component to identify a second digital component request in the second input audio signal. The authorization component may determine that a first portion of the second digital component was previously transmitted to the first client device and the authorization component may decline to transmit the first portion of the second digital component to the first client device. The method may further include transmitting, by the authorization component, a second authorization request to the second client device to authorize transmission of the digital component to the first client device.

The method may further include receiving, by the natural language processor component, a second input audio signal detected by the sensor at the first client device. The natural language processor component may parse the second input audio signal to identify a second digital component request in the second input audio signal. The authorization component may determine that a first portion of the second digital component was previously transmitted to the first client device and the content selection component may transmit a subportion of first portion of the second digital component to the first client device.

The method may further include receiving, by the natural language processor component, a second input audio signal detected by the sensor at the first client device. The natural language processor component may parse the second input audio signal to identify a second digital component request in the second input audio signal. It may be determined, by the authorization component, that the second client device is within a predetermined distance from the first client device, and the content selection component may transmit the second digital component to the first client device based on determining the second client device is within the predetermined distance form the first client device. The authorization component may receive a message indicating that the second client device is within the predetermined distance of the first client device.

The method may further include generating, by the authorization component, a payload comprising at least one of an indication of a content provider configured to provide the first digital component, a uniform resource locator (URL) associated with the content provider, or registration information associated with the content provider.

The method may further include receiving, by the natural language processor component, a second input audio signal detected by the sensor at the first client device. The natural language processor component may parse the second input audio signal to identify a second digital component request in the second input audio signal. The content selection component may stream the second digital component to the first client device. The authorization component may transmit a second authorization request to the second client device to authorize streaming of the digital component to the first client device, and the authorization component may terminate the streaming of the second digital component to the first client device based on not receiving a response to the second authorization request within a predetermined time.

The method may further comprise receiving, by the natural language processor component, a second input audio signal detected by the sensor at the first client device. The natural language processor component may parse the second input audio signal to identify a second digital component request in the second input audio signal. The content selection component may stream the second digital component to the first client device. The authorization component may stream a second authorization request to the second client device to authorize streaming of the digital component to the first client device. The authorization component may receive a declining message in response to the second authorization request and the authorization component may terminate the streaming of the second digital component to the first client device based on receiving the declining message.

The computer system or computing device <NUM> can include or be used to implement the system <NUM>, or its components such as the data processing system <NUM>. The data processing system <NUM> can include an intelligent personal assistant or voice-based digital assistant. The computing system <NUM> includes a bus <NUM> or other communication component for communicating information and a processor <NUM> or processing circuit coupled to the bus <NUM> for processing information. The computing system <NUM> can also include one or more processors <NUM> or processing circuits coupled to the bus for processing information. The computing system <NUM> also includes main memory <NUM>, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus <NUM> for storing information, and instructions to be executed by the processor <NUM>. The main memory <NUM> can be or include the data repository <NUM>. The main memory <NUM> can also be used for storing position information, temporary variables, or other intermediate information during execution of instructions by the processor <NUM>. The computing system <NUM> may further include a read-only memory (ROM) <NUM> or other static storage device coupled to the bus <NUM> for storing static information and instructions for the processor <NUM>. A storage device <NUM>, such as a solid-state device, magnetic disk or optical disk, can be coupled to the bus <NUM> to persistently store information and instructions. The storage device <NUM> can include or be part of the data repository <NUM>.

The computing system <NUM> may be coupled via the bus <NUM> to a display <NUM>, such as a liquid crystal display, or active matrix display, for displaying information to a user. An input device <NUM>, such as a keyboard including alphanumeric and other keys, may be coupled to the bus <NUM> for communicating information and command selections to the processor <NUM>. The input device <NUM> can include a touch screen display <NUM>. The input device <NUM> can also include a cursor control, such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor <NUM> and for controlling cursor movement on the display <NUM>. The display <NUM> can be part of the data processing system <NUM>, the client computing device <NUM> or other component of <FIG>, for example.

For situations in which the systems discussed herein collect personal information about users, or may make use of personal information, the users may be provided with an opportunity to control whether programs or features that may collect personal information (e.g., information about a user's social network, social actions or activities, a user's preferences, or a user's location), or to control whether or how to receive content from a content server or other data processing system that may be more relevant to the user. In addition, certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed when generating parameters. For example, a user's identity may be anonymized so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, postal code, or state level), so that a particular location of a user cannot be determined. Thus, the user may have control over how information is collected about him or her and used by the content server.

The subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. The subject matter described in this specification can be implemented as one or more computer programs, e.g., one or more circuits of computer program instructions, encoded on one or more computer storage media for execution by, or to control the operation of, data processing apparatuses. Alternatively, or in addition, the program instructions can be encoded on an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. While a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially generated propagated signal. The computer storage medium can also be, or be included in, one or more separate components or media (e.g., multiple CDs, disks, or other storage devices).

The terms "data processing system" "computing device" "component" or "data processing apparatus" encompass various apparatuses, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations of the foregoing. For example, the interface <NUM>, digital component selector <NUM>, or NLP component <NUM> and other data processing system <NUM> components can include or share one or more data processing apparatuses, systems, computing devices, or processors.

A computer program (also known as a program, software, software application, app, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program can correspond to a file in a file system. A computer program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code).

The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs (e.g., components of the data processing system <NUM>) to perform actions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatuses can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks.

The subject matter described herein can be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described in this specification, or a combination of one or more such back end, middleware, or front end components.

The computing system such as system <NUM> or system <NUM> can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network (e.g., the network <NUM>). In some implementations, a server transmits data (e.g., data packets representing a digital component) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server (e.g., received by the data processing system <NUM> from the client computing device <NUM> or the digital component provider device <NUM>).

The separation of various system components does not require separation in all implementations, and the described program components can be included in a single hardware or software product. For example, the NLP component <NUM> or the digital component selector <NUM>, can be a single component, app, or program, or a logic device having one or more processing circuits, or part of one or more servers of the data processing system <NUM>.

Having now described some illustrative implementations, it is apparent that the foregoing is illustrative and not limiting, having been presented by way of example. In particular, although many of the examples presented herein involve specific combinations of method acts or system elements, those acts and those elements may be combined in other ways to accomplish the same objectives. Acts, elements and features discussed in connection with one implementation are not intended to be excluded from a similar role in other implementations or implementations.

Any implementation disclosed herein may be combined with any other implementation or embodiment, and references to "an implementation," "some implementations," "one implementation" or the like are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in connection with the implementation may be included in at least one implementation or embodiment. Such terms as used herein are not necessarily all referring to the same implementation. Any implementation may be combined with any other implementation, inclusively or exclusively, in any manner consistent with the aspects and implementations disclosed herein.

References to "or" may be construed as inclusive so that any terms described using "or" may indicate any of a single, more than one, and all the described terms. For example, a reference to "at least one of 'A' and 'B'" can include only 'A', only 'B', as well as both 'A' and 'B'. Such references used in conjunction with "comprising" or other open terminology can include additional items.

Claim 1:
A system to authenticate computing devices in a networked environment, comprising:
a data processing system comprising one or more processors and memory, the one or more processors configured to:
receive an input image or video and/or audio signal detected by a sensor at a first client device;
parse the input image or video and/or audio signal to identify a request for content in the input image or video and/or audio signal;
select a first digital component based at least on the request for content;
determine based on a context of a second client device, a time delay within which the first client device is to be authorized;
transmit to the first client device a first portion of the first digital component;
transmit an authorization request to the second client device to cause the second client device to render a prompt to authorize a transmission of a second portion of the first digital component to the first client device in response to detection of an action on the prompt at the second client device within the time delay; and
transmit the second portion of the first digital component to the first client device for presentation with the first portion of the first digital component, responsive to receipt of a confirmation message within the time delay.