Providing remote keyboard services

By providing remote keyboard services on computing devices, the cumbersome text input process of streaming media devices is solved, and the function of using a virtual keyboard to enter text without the need for applications or unlocking devices is realized, improving the user experience.

CN120066374APending Publication Date: 2025-05-30APPLE INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202510228631.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2016-09-21
Filing Date
2017-05-22
Publication Date
2025-05-30

AI Technical Summary

Technical Problem

The text input process of streaming media devices is cumbersome, and users need to select characters one by one through remote control devices, resulting in a slow and cumbersome input process.

Method used

Provides a system that allows individual computing devices (such as smartphones, tablets, etc.) to provide remote keyboard services for media devices, and users can use virtual keyboards to enter text without calling applications or unlocking devices.

Benefits of technology

It implements the remote virtual keyboard service for streaming media devices without calling applications or unlocking devices, simplifying the text input process and improving user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120066374A_ABST
    Figure CN120066374A_ABST
Patent Text Reader

Abstract

The invention relates to providing remote keyboard services. The systems described herein provide remote keyboard services for media devices on a computing device without having to invoke an application or unlock the computing device. The computing device may receive a message indicating that a text input field on the other device is selected, and present a notification to the user that prompts the user to invoke the virtual keyboard on the computing device to provide text input to the selected text input field. The computing device may receive user input selecting the notification and present a virtual keyboard for providing text input to the other devices. The computing device may receive a keyboard input from the user selecting a character and send the character to the other device. The other device may then use the character as a text input to the selected text input field.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application No. 201780035030.8, titled "Providing Remote Keyboard Service", with an application date of May 22, 2017. Technical Field

[0002] This disclosure generally relates to coordinating services between different devices. Background Art

[0003] Streaming media devices are becoming increasingly popular. Streaming media devices allow users to browse, search for, and view media content on demand. However, the input mechanisms of these streaming media devices are often simple remote controls without a keyboard, and when entering a search query into a text input control (e.g., a text input box), the keyboard requires the user to search for and select individual text characters. Therefore, the process of providing text input to these streaming media devices can be cumbersome for users.

[0004] Some streaming media devices have corresponding applications through which users can use the virtual keyboard on the user's handheld device (e.g., a smart phone, a tablet, etc.) to provide text input. However, the user must first install and invoke the application before being able to use the virtual keyboard to provide text input to the streaming media device. Summary of the Invention

[0005] The systems described herein provide a remote keyboard service for media devices on a separate computing device without having to invoke an application or unlock the computing device. The computing device can receive a message indicating that a text input field on another device has been selected and present a notification prompting the user to invoke the virtual keyboard on the computing device to provide text input to the selected text input field. The computing device can receive user input selecting the notification and present the virtual keyboard for providing text input to the other device. The computing device can receive keyboard input from the user selecting characters and send those characters to the other device. Then, the other device can use those characters as text input to the selected text input field.

[0006] Certain specific embodiments provide at least the following advantages. The user device can provide a remote virtual keyboard without having to invoke a specific application. The remote virtual keyboard can be provided even when the user's device is locked. Since there is a need to advertise the keyboard to all user devices, the user can select the user device that is most convenient for the user.

[0007] The details of one or more specific embodiments are set forth in the following drawings and detailed description. Other features, aspects, and potential advantages will be apparent from the detailed description, the drawings, and the claims. Brief Description of the Drawings

[0008] Figure 1 It is a block diagram of an example system 100 for providing a remote keyboard service on a user device.

[0009] Figure 2 An example graphical user interface for presenting a remote keyboard notification on a user device is shown.

[0010] Figure 3 An example graphical user interface for presenting a virtual keyboard on a user device is shown.

[0011] Figure 4 An example graphical user interface for presenting a virtual keyboard on a user device is shown.

[0012] Figure 5 It is a flowchart of an example process for providing a remote keyboard service on a user device.

[0013] Figure 6 It is a flowchart of an example process for requesting a remote keyboard service from a user device.

[0014] Figure 7 It can be implemented Figures 1 to 6 A block diagram of an example computing device that can implement the features and processes described above.

[0015] Similar reference numerals in the various figures indicate similar elements. Detailed Description

[0016] Overview

[0017] Examples of methods, apparatuses, and computer programs for providing a remote keyboard service on a user device are disclosed below. In the following description, for the purpose of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present invention. However, it will be apparent to those skilled in the art that the embodiments of the present invention can be practiced without these specific details or with equivalent arrangements. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments of the present invention.

[0018] Figure 1 It is a block diagram of an example system 100 for providing a remote keyboard service on a user device. In some specific implementations, system 100 may include a user device 102 (e.g., 102a, 102b... 102n). For example, user device 102a may be a computing device such as a smartphone, tablet, television, desktop computer, laptop computer, home device, e - book device, gaming device, smartwatch, smart glasses, and / or other mobile or wearable devices, accessories and peripherals of these devices, or any combination thereof.

[0019] In some specific implementations, the user device 102 (e.g., user device 102a, user device 102b... user device 102n) may be configured with a corresponding operating system 104 that provides various services and features. For example, the operating system 104 may be configured to receive and decode status advertisement messages (e.g., Bluetooth packets, Bluetooth LE packets, etc.) from different devices within a very close range of the user device 102. The status advertisement messages may include information describing the current status of other devices, including the availability of different services, data required to coordinate processing between different devices, and / or information and / or requests for services from other devices. For example, the user device 102a may receive status advertisement messages from the user devices 102b and / or 102n that describe the current status of these devices.

[0020] In some specific implementations, the user device 102 may receive status advertisement messages from the media device 106. For example, the media device 106 may be a computing device, such as a streaming media player, a set-top box, a smart TV, a laptop computer, or other computing devices. The user of the user device 102 may interact with the media device 106 to browse and search for media items to play and / or other content to view. For example, the media device 106 may present a graphical user interface on a display (e.g., a TV, a computer monitor, etc.) connected to the media device 106 to allow the user to browse, search, and select media items (e.g., movies, websites, images, photos, etc.) of the media device 106 to be presented on the display of the media device 106.

[0021] In some specific implementations, the media device 106 may require text input from the user. For example, the media device 106 may require text input from the user when searching for media items. The media device 106 may require text input from the user when logging in to a subscription service that requires the user's login credentials. Sometimes, the operating system 108 of the media device 106 will require some text input. For example, the media device 106 may present prompts and text input controls on the display of the media device 106 for receiving network configuration input, login credentials, etc. Sometimes, the application 110 (e.g., media content provider software application, video application, music application, game application, weather application, etc.) will present prompts and text input controls for receiving text input from the user. For example, the application 110 may provide a media item search feature that allows the user to input text defining a search query.

[0022] In some specific implementations, a user may use a remote control device 120 to provide text input. For example, the media device 106 may have been sold with or work with the remote control device 120, which has several directional buttons and selection buttons to move a cursor on the media device 106 and select items on the display. Sometimes the remote control device 120 may have a touch interface and the remote control device 120 can receive touch input gestures (e.g., swipe up, swipe down, swipe left, swipe right, tap, etc.) to move the cursor on the media device 106 and select items on the display. When using the remote control device 120 to provide text input to the media device 106, the user typically has to use the remote control device 120 to move the cursor to a character array presented on the graphical user interface and select one character at a time until an appropriate string is constructed. If the user has to repeatedly perform the key input process to find the media item that the user wishes the media device 106 to play, the process may be slow and cumbersome for the user and usually results in the user feeling frustrated.

[0023] To address the above problems by using the remote control device 120 to input text, the user device 102 may be configured with a remote control application 104 (e.g., 104a, 104b) for remote interaction with the media device 106. For example, the remote control application may control the media device 106 via the network 112. The network 112 may be, for example, a local area network, a wide area network, a local Wi-Fi network, an ad hoc peer-to-peer network, etc. The network 112 may be implemented using the Internet protocol, Bluetooth, Bluetooth Low Energy, or any other network protocol.

[0024] In some specific implementations, the remote control application 104 may be configured to provide functions similar to those of the remote control device 120. For example, the remote control application 104 may present on the display of the user device 102 directional controls for moving the cursor and selection controls for selecting items presented by the media device 106. However, the remote control application 104 may also provide the user with a virtual keyboard that can be used to provide text input to the media device 106. For example, the virtual keyboard may be presented by the remote control application 104a on the touch-sensitive display of the user device 102a, and the user can type on the virtual keyboard to select characters and create a string corresponding to the desired text input. Then, the user device 102a may send the text input to the media device 106 via the network 112. Then, the media device 105 may use the text input to perform a search, configure the operating system 108, configure the application 110, or for any other purpose.

[0025] While providing text input to the virtual keyboard provided by the remote control application 104 is an improvement over entering text using the remote control device 120, users are still concerned about unlocking the user device 102a and invoking the remote control application 104a before being able to access and use the virtual keyboard to provide text input to the media device 106. Thus, in some embodiments, the operating system 104a of the user device 102a may provide a virtual keyboard service for providing text input to the media device 106. For example, the user device 102a may provide the virtual keyboard service without unlocking the user device 102a. The user device 102a may provide the virtual keyboard service without invoking the remote control application 104a.

[0026] In some embodiments, the media device 106 may broadcast a remote keyboard service request to connect to the remote keyboard service provided by the user device 102. For example, the remote keyboard service request may be (e.g., in part) a device status advertisement message that indicates that a text input control has been selected on the media device 106. For example, when a user interacts with the media device 106 (e.g., using the remote control device 120) and selects a text input field, the media device 106 may generate a status advertisement message indicating that the text input field has been selected. For example, if the application 110 presents a media item search graphical user interface, the user may select a text input control on the graphical user interface so that the user can provide a search query. In response to selecting the text input control, the application 110 may call an application programming interface (API) of the operating system 108 to request keyboard support to provide input to the selected text input control.

[0027] If the operating system 108 presents a configuration graphical user interface that requires text input, the user may select a text input control on the graphical user interface so that the user can provide an appropriate configuration string (e.g., network identifier, account credentials, etc.). In response to selecting the text input control, the operating system 108 may call an API of the operating system 108 to request keyboard support to provide input to the selected text input control. When the keyboard support API is called, the operating system 108 may generate a status advertisement message that includes data indicating that a text input control has been selected on the media device 106. For example, the status advertisement message may include an identifier of the media device 106, an identifier of the application 110, data indicating that the text input control has been selected (e.g., true / false), data describing the text input control, or text input provided by the user and / or text input that the user has provided to the media device 106. The status advertisement message data may be encoded into and decoded from the status advertisement message using a status advertisement message scheme as described in U.S. Patent Application Serial No. 15 / 179,676, the entire disclosure of which is incorporated herein by reference.

[0028] In some specific implementations, the media device 106 may broadcast the generated status advertisement message. For example, the media device 106 may use wireless (e.g., peer-to-peer) technology to broadcast the generated status advertisement message, such as Bluetooth, Bluetooth Low Energy, peer-to-peer Wi-Fi, or some other wireless technology. For example, the status advertisement message may be broadcast without selecting a specific receiving device. For example, any user device (e.g., user device 102) within the wireless signal range transmitted by the media device 106 may receive and / or process the advertisement message generated by the media device 106. Alternatively, only the user device associated with the same user account (e.g., subscriber account, cloud service account, etc.) as the sending device can receive and decode the message from the sending device. Alternatively, the sending and / or receiving devices do not have to be associated with the same user and / or the same user account. For example, both the user device 102 and the media device 106 may be associated with different user accounts or no user account. The user device 102 and the media device 106 may be different types of computing devices from different manufacturers, with different configurations and / or different operating systems.

[0029] In some specific implementations, the user device 102 may receive the broadcast status advertisement message. For example, the user device 102 (e.g., user device 102a, user device 102b, … user device 102n) within the broadcast range of the media device 106 may receive the status advertisement message. In response to receiving the status advertisement message, the user device 102 may determine that the text input control on the media device 106 is the currently selected control based on the status data in the status advertisement message. When the user device 102 determines that the text input control on the media device 106 is selected, the operating system 104 on the user device 102 will present a graphical notification on the corresponding device that prompts the user to invoke the virtual keyboard. For example, if the user has user devices 102a (e.g., smartphone), 102b (e.g., laptop), and 102n (e.g., tablet) all within the broadcast range of the media device 106, then all of these devices may determine that the text input control on the media device 106 is the currently selected control based on the status advertisement message, and all of these user devices may present graphical notifications that prompt the user to invoke the virtual keyboard on each of these user devices.

[0030] In some specific implementations, the user device 102 (e.g., user device 102a, user device 102b, … user device 102n) may present a keyboard notification on the screen of the user device even when the screen of the user device is locked. For example, the user device 102 may present a remote keyboard notification when receiving the status advertisement message broadcast from the media device 106.

[0031] Continuing with the above example, assume that the user device 102a is within the broadcast range of the media device 106. Then, the user device 102a can present a remote keyboard notification on the display of the user device 102a. After the user selects the notification on the user device 102a (e.g., by touching, swiping, etc.), the user device 102a can establish a two-way communication session with the media device 106 via the communication network 112. For example, the communication network 112 can include various networks, such as a data network, a wireless network, a telephone network, or any combination thereof. After the user device 102a responds to a remote keyboard service request (e.g., embodied in a status advertisement message), the media device 106 can broadcast another status advertisement message indicating that the media device 106 has been connected to the remote keyboard. Thus, in response to receiving the status advertisement message indicating that the media device 106 has been connected to the remote keyboard, other user devices (e.g., user device 102b, user device 102n, etc.) can cancel (e.g., hide, remove from the display) their respective keyboard notifications.

[0032] In some specific implementations, the media device 106 can send information describing the required text input to the user device 102a. For example, after establishing a two-way communication session via the network 112, the operating system 108 of the media device 106 can send information describing the text input provided by the user via the remote keyboard to the operating system 104a of the user device 102a. For example, the information can include prompts for text input fields (e.g., "Enter username", "Enter password", "Enter search query", etc.). The information can include an identification or representation of the application 110 or the operating system 108. For example, the information can include an image, icon, or graphic representing the manufacturer of the application 110 or the operating system 108. Then, the operating system 104a can use this information to present text input controls and / or a virtual keyboard on the display of the user device 102a, as further described below. Alternatively, the information can be obtained from the status advertisement message received by the user device 102a, as described above.

[0033] In some specific implementations, the operating system 104a may send virtual keyboard inputs to the media device 106. For example, the operating system 104a may detect when the user provides an input that selects a character or other graphical element presented on the virtual keyboard. After each input is detected, the operating system 104a may send a message identifying the selected character or graphical element to the operating system 108. For example, the operating system 104a may send each character or graphical element individually when it is selected, such that the operating system 108 and / or the application 110 can respond appropriately to each keyboard input (e.g., by presenting search results, moving between text input controls, etc.). For example, the operating system 108 may send the keyboard input to the application 110, such that the application 110 can respond to the keyboard input according to the programming of the application 110. In some specific implementations, after the user provides an input indicating that the user has finished providing text input to the selected control, the keyboard service provided by the user device 102a may be terminated. For example, when the user selects a graphical element (e.g., an "enter" key, a "done" element, etc.) on the virtual keyboard, the keyboard service may be terminated and the virtual keyboard may be cancelled or hidden.

[0034] In some specific implementations, the operating system 104a may wait for a period of time before terminating the remote virtual keyboard service. For example, even if the user may have finished providing input to the text control presented on the media device 106, the operating system 104a may continue to present the virtual keyboard for a period of time (e.g., 5 seconds, 7 seconds, etc.) after the last input, to allow the user to provide input to additional text controls presented on the media device 106. Thus, if the media device 106 requires additional text input, the user does not have to be responsible for invoking the virtual keyboard again.

[0035] Figure 2 An example graphical user interface 200 for presenting a remote keyboard notification 202 on the user device 102a is shown. For example, the notification 202 may be a graphical element presented by the operating system 104a on the display of the user device 102a in response to receiving a status advertisement message indicating the selection of a text input control on the media device 106, as described above. The notification 202 may be presented on each user device 102 that receives the status advertisement message. The notification 202 may include, for example, a description 204 and / or an image 206 representing the media device 106 and / or the application 110. The notification 202 may include a prompt 208 describing how to invoke the virtual keyboard on the user device 102a. For example, the user may invoke the virtual keyboard by selecting (e.g., long-touching, pressure-touching, tapping, swiping, etc.) the notification 202.

[0036] In some specific implementations, when the user device 102a is locked, the user device 102 (e.g., user device 102a, user device 102b, … user device 102n) can present a keyboard notification 202 on the GUI 200 of the user device 102a. For example, the GUI 200 can be the lock screen of the user device 102a. When the user device 102a is unlocked (e.g., the user has been authenticated as a user of the user device 102a), the GUI 200 can be the home screen of the user device 102a.

[0037] Figure 3 An example graphical user interface 300 for presenting a virtual keyboard on the user device 102a is shown. For example, in response to the user selecting the notification 202, the operating system 104a can present the GUI 300 on the display of the user device 102a, as described above with reference to Figure 2 the GUI 200. In some specific implementations, the user device 102a can present graphical elements 302 representing the application 110 and / or the media device 106. For example, the graphical elements 302 can include a description 204 and / or an image 206 representing the media device 106. When the selected text input control is associated with the application 110, the graphical elements 302 can include a graphical representation 304 of the application 110 (e.g., an image, an icon, a graphic, etc.).

[0038] In some specific implementations, the graphical elements 302 can include a prompt 306 describing the text input that the user should provide. For example, the prompt 306 can include instructions such as “Enter your password” or “Enter a search term”. In some specific implementations, the graphical elements 302 can include a prompt instruction 308 describing how to invoke the virtual keyboard on the user device 102a. For example, the prompt 308 can include instructions to provide a tap, a swipe, a long touch, or a pressure touch gesture to the graphical elements 302 to invoke the virtual keyboard.

[0039] In some specific implementations, the GUI 300 can include a virtual keyboard 310. For example, in response to the user selecting the graphical elements 302 to invoke the virtual keyboard 310, the virtual keyboard 310 can be presented on the GUI 300. For example, in response to the user device 102a receiving the input specified by the prompt 208, the virtual keyboard 310 can be presented. For example, the virtual keyboard can include a typical virtual keyboard layout for selecting characters. In some specific implementations, the GUI300 can be presented without the graphical elements 302. For example, the virtual keyboard 310 can be presented as in Figure 3 the GUI 300, but without the graphical elements 302.

[0040] In some specific implementations, user device 102a may present virtual keyboard 310 in response to detecting movement. For example, user device 102a may present notification 202 on Figure 2 GUI 200. When the user picks up user device 102a to view notification 202, user device 102a may detect the movement of user device 102a (e.g., using a built-in motion sensor, accelerometer, etc.), and operating system 104a automatically presents virtual keyboard 310 on the display of user device 102a. For example, in response to detecting the movement of user device 102a, operating system 104a may present Figure 3 GUI 300. Thus, the user of user device 102a can simply call virtual keyboard 310 by picking up user device 102a.

[0041] In some specific implementations, virtual keyboard 310 may include text control 308. For example, when the user selects a character presented on virtual keyboard 310, the selected character may be represented on text control 308. As described above, when a character is selected on virtual keyboard 310, these characters are also sent to media device 106, so both user device 102a and media device 106 can present similar strings based on the characters selected by the user. Thus, the user does not have to shift the user's attention from the display of user device 102a when entering text, but can compare the text entered on user device 102a with the text received by media device 106 when needed.

[0042] In some specific implementations, virtual keyboard 310 may include graphical elements 312 and / or 314 for navigating between text controls (e.g., text input boxes, text input fields, etc.) presented on the display of media device 106. For example, operating system 108 or application 110 on media device 106 may need to input text into multiple text input controls. For example, operating system 108 or application 110 may require the user's username and password. The user may select graphical element 312 to select the next text input control. The user may select graphical element 314 to select the previous text input control.

[0043] In some embodiments, the virtual keyboard 310 may include a graphical element 316 for indicating that the user has completed providing text input. For example, the user may select the graphical element 316 to indicate that the user has completed providing input to the current text control. When the user selects the graphical element 316, the user device 102a may send a message to the media device 106 to cause another (e.g., next) text input control to be selected on the media device 106. When the user selects the graphical element 316, the user device 102a may send a message to the media device 106 to terminate the remote virtual keyboard service. Alternatively, the user may select the graphical element 318 to terminate the remote virtual keyboard service and cancel the graphical element 302 and the virtual keyboard 310. However, in some embodiments, termination of the service may be delayed to allow selection of additional text input controls and provision of additional text input on the media device 106, as described above.

[0044] Figure 4 An example graphical user interface 400 for presenting a virtual keyboard on a user device is shown. For example, in response to a user selection Figure 2 of the notification 202, the GUI 400 may be presented by the operating system 104a on the display of the user device 102a. For example, the GUI 400 may be presented as an alternative to the GUI 300 based on features (or lack of features) provided by various user devices 102. For example, if the user device 102a is configured with a force touch input feature, the user device 102a may present the GUI 300. If the user device 102a is not configured with a force touch input feature, the user device 102a may present the GUI 400.

[0045] In some embodiments, the GUI 400 may include a graphical element 402 for presenting text input. For example, the graphical element 402 may be presented in response to a selection of the notification 202. The graphical element 402 may be presented adjacent to or contiguous with the notification 202. The graphical element 402 may include a prompt 406. For example, the prompt 406 may provide the user with instructions describing what type of information the user should provide to the selected text input control. The graphical element 402 may include a text input control 408. For example, the text input control 408 may present text input provided by the user using a virtual keyboard, as described above.

[0046] In some specific implementations, the GUI 400 may include a virtual keyboard 410. For example, in response to a user selecting the graphical element 202, the virtual keyboard 410 may be presented on the GUI 400. For example, the virtual keyboard 410 may be presented simultaneously or almost simultaneously with the graphical element 402. For example, in response to the user device 102a receiving the input specified by the prompt 208, the virtual keyboard 310 may be presented. The virtual keyboard 410 may include a typical virtual keyboard layout for selecting characters.

[0047] In some specific implementations, the virtual keyboard 410 may include graphical elements 412 and / or 414 for navigating between text controls (e.g., text input boxes, text input fields, etc.) presented on the display of the media device 106. For example, the operating system 108 or an application 110 on the media device 106 may need to input text into multiple text input controls. For example, the operating system 108 or the application 110 may require the user's username and password. The user may select the graphical element 412 to select the next text input control. The user may select the graphical element 414 to select the previous text input control.

[0048] In some specific implementations, the virtual keyboard 410 may include a graphical element 416 for indicating that the user has finished providing text input. For example, the user may select the graphical element 416 to indicate that the user has finished providing input to the current text control. When the user selects the graphical element 416, the user device 102a may send a message to the media device 106 to cause another (e.g., the next) text input control to be selected on the media device 106. When the user selects the graphical element 416, the user device 102a may send a message to the media device 106 to terminate the remote virtual keyboard service. Alternatively, the user may select the graphical element 418 to terminate the remote virtual keyboard service and cancel the graphical element 402 and the virtual keyboard 410. However, in some specific implementations, the termination of the service may be delayed to allow additional text input controls to be selected and additional text input to be provided on the media device 106, as described above.

[0049] Example Process

[0050] Figure 5It is a flowchart of an example process 500 for providing a remote keyboard service on a user device. More specifically, the process 500 described herein is a method for providing a remote keyboard service from a user device to a media device (or any other type of computing device). The user device implementing the process 500 can provide the remote keyboard service and present the remote keyboard without invoking a user application (e.g., the remote control application 104a) on the user device. The process 500 can be effectively handled by the operating system and make the remote keyboard service available regardless of the applications installed on the user device and independent of the locked or unlocked state of the user device.

[0051] At step 502, the user device 102a can receive a status advertisement message broadcast from the media device 106. For example, the status advertisement message can identify the media device and include data describing the current state of the media device. According to the specific implementation described herein, the status advertisement message can include data indicating that the text input control presented by the media device 106 is the currently selected control. Alternatively, the status advertisement message can include data indicating that the media device 106 is requesting a connection to a remote keyboard.

[0052] At step 504, the user device 102a can determine that the text input control on the media device is the currently selected control. For example, based on the status advertisement message received at step 502, the user device 102a can determine that the text input control on the media device 106 is the currently selected control.

[0053] At step 506, the user device 102a can present a remote keyboard notification. For example, in response to determining that the text input control on the media device 106 is the currently selected control, the user device 102a can present a graphical keyboard notification prompting the user to invoke the virtual keyboard on the user device 102a. For example, when the user has user devices 102a (e.g., a smart phone), 102b (e.g., a laptop), and 102n (e.g., a tablet) all within the broadcast range of the media device 106, each of these devices can determine that the text input control on the media device is the currently selected control based on the status advertisement message and can present a graphical notification prompting the user to invoke the virtual keyboard on each of these user devices.

[0054] At step 508, the user device 102a can receive the user's selection of the notification. For example, the user device 102a can receive user input (such as tapping, swiping, long-touching, pressure-touching, etc.) for the notification, thereby selecting the notification. In some specific implementations, the first device selected by the user (for example, the user may tap on a graphical notification to invoke the virtual keyboard on that device) will present a remote keyboard on the selected device for the user to enter text into the text field on the media device 106. The remaining devices will cancel the graphical notification from their screens but will still retain the notification in these devices.

[0055] At step 510, the user device 102a can establish a connection with the media device 106. As described above, after the user selects the notification on the user device 102a by tapping or clicking on the notification, the user device 102a can establish a two-way communication session with the media device 106 through the communication network 112. For example, the user device 102a can establish a session with the media device 106 through the network 112 because a communication session through the network 112 can allow the transmission of more data than status advertisement messages.

[0056] At step 512, the user device 102a can receive application data from the media device 106. For example, after establishing a communication session with the media device 106, the media device 106 can send the application data to the user device 102a. For example, the application data can include media device data, such as the description 204 and / or the image 206 representing the media device 106. The application data can include the graphical representation 304 of the application 110 and / or the prompt 306 from the application 110 (such as "Please enter your password"), as Figure 3 shown.

[0057] At step 514, the user device 102a can present the device data, the application data, and / or the keyboard on the display of the user device 102a. For example, after receiving the device data and / or the application data, the user device 102a can present the device data and / or the application data, as Figure 3 shown.

[0058] At step 516, the user device 102a can receive user input for the virtual keyboard presented on the user device. For example, the user input can be the selection of a single character or other objects (such as the graphical elements 312 and / or 314 for navigating between text controls) presented on the virtual keyboard.

[0059] At step 518, the user device 102a may send a user input to the media device 106. For example, the user device 102a may send the user input to the media device 106 via the communication network 112. For example, after step 518, the process 500 may return to step 516. Steps 516 and 518 may be repeated until the user has finished providing input to the virtual keyboard. Thus, the media device 106 may respond to each keyboard input as if the keyboard were directly connected to or part of the media device 106.

[0060] Figure 6 is a flowchart of an example process 600 for requesting a remote keyboard service from a user device. More specifically, the process 600 described herein is a method for advertising the need for a remote keyboard so that a user can select the most convenient device for invoking the remote keyboard, as described above.

[0061] At step 602, the media device 106 may present the application 110 on a display associated with the media device 106. In some embodiments, the media device 106 may be configured with various media applications for presenting media items to a user. The user may use a remote control device to invoke the application 110 on the media device 106. The application 110 may present a graphical user interface that allows the user to control the application 110. For example, the application 110 may present a graphical user interface that allows the user to browse, search, and view media items available via the application 110.

[0062] At step 604, the media device 106 may receive an indication of a selection of a text input control from the application 110. For example, in interacting with the application 110, the application 110 may require the user to provide text input. The application 110 may require a username and password. The application 110 may require search parameters for performing a search of media. In either case, the application 110 may present and the user may select (e.g., using the remote control device 120) a text input control presented by the application 110. When the text input control is selected, the application 110 may send a message (e.g., using the API described above) to the operating system 108 on the media device 106, thereby indicating that the text input control has been selected and / or providing a description of the information required by the text input control. In some embodiments, the message may include an identifier of the application 110 and / or other application metadata, such as the graphical representation 304.

[0063] At step 606, media device 106 may generate an advertisement message indicating that a text input control has been selected. In some embodiments, media device 106 may generate a status advertisement message that includes status information indicating that a text input control presented by application 110 has been selected. For example, in response to receiving a message from application 110 at step 604, operating system 108 may generate a status advertisement message that includes data indicating that a text input control is currently selected on media device 106.

[0064] At step 608, media device 106 may broadcast the status advertisement message. In some embodiments, after media device 106 generates a status advertisement message indicating that a text input control has been selected, media device 106 may broadcast the status advertisement message. For example, the advertisement message may be broadcast without identifying a specific recipient device. Thus, all user devices within the broadcast range of media device 106 may receive the status advertisement message.

[0065] At step 610, media device 106 may receive a message indicating that a user device will provide a remote keyboard for the media device. For example, after all user devices 102 within the broadcast range of media device 106 receive the media device status advertisement broadcast from media device 106, media device 106 may receive a message indicating that user device 102a will provide a remote keyboard for media device 106. For example, the message may be sent to media device 106 via network 112. The message may initiate a two-way communication session between media device 106 and user device 102a such that media device 106 and user device 102a can exchange data related to the text input control.

[0066] At step 612, media device 106 may send application data to user device 102a. For example, the application data may include device data such as description 204 and / or an image 206 representing the media device (e.g., media device 106). The application data may include a graphical representation 304 of application 110 and / or a prompt 306 from application 110 (e.g., Please enter your password), as Figure 3 shown. The application data may be received by operating system 108 from application 110 as described above in step 604.

[0067] At step 614, media device 106 may receive a user's keyboard input from user device 102a. For example, when user device 102a receives user input selecting a character and / or other object on a remote keyboard (e.g., keyboard 310, keyboard 410) presented on user device 102a, user device 102a may send the user input (e.g., the selected character or other object) to media device 106.

[0068] At step 616, media device 106 may send the user's keyboard input to application 110. For example, after receiving the user's keyboard input from user device 102a, operating system 108 may send the keyboard input to application 110. Application 110 may then perform an operation according to the selected text control use. For example, if the currently selected text control is configured to receive username and / or password input, application 110 may process the keyboard input to determine whether the entered username and / or password is correct for the user. If the currently selected text control is configured to receive search parameters, application 110 may process the keyboard input by performing a search after each character is entered by the user.

[0069] Since media device 106 receives and processes each keyboard input (e.g., character selection, object selection, etc.) as it is received, process 600 may return to step 614 to receive the next keyboard input and return to 616 to process the next keyboard input. Thus, process 600 may repeat steps 614 and 616 until the user has finished providing input to the selected text control.

[0070] In addition, although process 600 describes receiving text input for application 110, process 600 may also be implemented to receive text input for operating system 108. For example, application 110 may be replaced with operating system 108 in process 600 to obtain a remote keyboard service for operating system 108 and receive text input for a text input control presented by operating system 108.

[0071] Graphical User Interface

[0072] The present disclosure has described above various graphical user interfaces (GUIs) for implementing various features, processes, or workflows. These GUIs may be presented on various electronic devices, including but not limited to laptop computers, desktop computers, computer terminals, television systems, tablet computers, e-book readers, and smart phones. One or more of these electronic devices may include a touch-sensitive surface. The touch-sensitive surface may process multiple simultaneous input points, including processing data related to the pressure, degree, or position of each input point. Such processing may facilitate gestures performed with multiple fingers, including pinching and swiping.

[0073] When the present disclosure refers to a user interface element in a "select" GUI, these terms are understood to include clicking or "hovering" over the user interface element using a mouse or other input device, or touching, tapping, or gesturing on the user interface element using one or more fingers or a stylus. The user interface elements can be virtual buttons, menus, selectors, switches, sliders, brushes, knobs, thumbnails, links, icons, radio boxes, check boxes, and any other mechanism for receiving input from the user or providing feedback to the user.

[0074] Privacy

[0075] The present disclosure recognizes that the use of such personal information data in the technology of the present invention can be used to benefit the user. For example, the personal information data can be used to deliver target content that the user is more interested in. Thus, the use of such personal information data enables planned control over the delivered content. In addition, the present disclosure also anticipates other uses of personal information data that are beneficial to the user.

[0076] The present disclosure also contemplates that entities responsible for the collection, analysis, disclosure, transmission, storage, or other uses of such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of these legitimate uses. Additionally, such collection should only be carried out after the user's informed consent. Additionally, such entities should take any necessary steps to safeguard and protect access to such personal information data and ensure that others who have access to the personal information data comply with their privacy policies and procedures. Additionally, such an entity can subject itself to third-party assessments to demonstrate its compliance with widely accepted privacy policies and practices.

[0077] Notwithstanding the foregoing, the present disclosure also anticipates embodiments in which the user selectively blocks the use or access of personal information data. That is, the present disclosure anticipates that hardware elements and / or software elements can be provided to prevent or block access to such personal information data. For example, in the case of an advertising delivery service, the technology of the present invention can be configured to allow the user to select to "opt in" or "opt out" of participating in the collection of personal information data during the registration for the service. Also, for example, the user can choose not to provide location information for a target content delivery service. Additionally, for example, the user can choose not to provide precise location information but permit the transmission of location area information.

[0078] Example System Architecture

[0079] Figure 7 To be achievable Figures 1 to 6Block diagram of an example computing device 700 showing features and processes. Computing device 700 may include a memory interface 702, one or more data processors, image processors, and / or central processing units 704, and a peripheral device interface 706. Memory interface 702, one or more processors 704, and / or peripheral device interface 706 may be separate components or may be integrated into one or more integrated circuits. The various components in computing device 700 may be coupled by one or more communication buses or signal lines.

[0080] Sensors, devices, and subsystems may be coupled to peripheral device interface 706 to facilitate a variety of functions. For example, motion sensor 710, light sensor 712, and proximity sensor 714 may be coupled to peripheral device interface 706 to facilitate orientation, lighting, and proximity functions. Other sensors 716 may also be connected to peripheral device interface 706, such as a Global Navigation Satellite System (GNSS) (e.g., GPS receiver), temperature sensor, biometric sensor, magnetometer, or other sensing devices, to facilitate related functions.

[0081] Camera subsystem 720 and optical sensor 722 (e.g., a charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) optical sensor) may be used to facilitate camera functions, such as recording photographs and video clips. Camera subsystem 720 and optical sensor 722 may be used to collect images of a user to be used during user authentication, e.g., by performing face recognition analysis.

[0082] Communication functions may be facilitated through one or more wireless communication subsystems 724, which may include radio frequency receivers and transmitters and / or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of communication subsystem 724 may depend on the one or more communication networks through which computing device 700 is intended to operate. For example, computing device 700 may include a communication subsystem 724 designed to operate over a GSM network, GPRS network, EDGE network, Wi-Fi or WiMax network, and Bluetooth TM network. Specifically, wireless communication subsystem 724 may include a host protocol, thereby enabling device 100 to be configured as a base station for other wireless devices.

[0083] Audio subsystem 726 may be coupled to speaker 728 and microphone 730 to facilitate voice-enabled functions, such as speaker recognition, voice replication, digital recording, and telephone functions. Audio subsystem 726 may be configured to facilitate, for example, voice processing commands, voiceprint discrimination, and voice authentication.

[0084] The I / O subsystem 740 may include a touch surface controller 742 and / or one or more other input controllers 744. The touch surface controller 742 may be coupled to a touch surface 746. The touch surface 746 and the touch surface controller 742 may detect contact and movement or interruptions thereof, for example, using any of a variety of touch-sensitive technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch surface 746.

[0085] One or more other input controllers 744 may be coupled to other input / control devices 748, such as one or more buttons, rocker switches, thumb wheels, infrared ports, USB ports, and / or pointer devices (such as a stylus). One or more buttons (not shown) may include up / down buttons for volume control of the speaker 728 and / or the microphone 730.

[0086] In one particular implementation, pressing a button for a first duration can unlock the touch surface 746; and pressing a button for a second duration longer than the first duration can turn on or off the power of the computing device 700. Pressing a button for a third duration can activate a voice control or voice command module that enables the user to speak commands into the microphone 730 so that the device executes the spoken commands. The user can customize the functions of one or more of the buttons. For example, virtual or soft buttons and / or a keyboard can also be implemented using the touch surface 746.

[0087] In some particular implementations, the computing device 700 may present recorded audio and / or video files, such as MP3, AAC, and MPEG files. In some particular implementations, the computing device 700 may include the functionality of an MP3 player, such as an iPod TM . The computing device 700 may thus include a 36-pin connector compatible with an iPod. Other input / output and control devices may also be used.

[0088] The memory interface 702 may be coupled to a memory 750. The memory 750 may include high-speed random access memory and / or non-volatile memory, such as one or more disk storage devices, one or more optical storage devices, and / or flash memory (e.g., NAND, NOR). The memory 750 may store an operating system 752, such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system (such as VxWorks).

[0089] The operating system 752 may include instructions for handling basic system services and for performing hardware-related tasks. In some embodiments, the operating system 752 may be a kernel (e.g., a UNIX kernel). In some embodiments, the operating system 752 may include instructions for performing voice authentication. For example, the operating system 752 may implement a remote keyboard feature, as referenced Figures 1 to 6 as described.

[0090] The memory 750 may also store communication instructions 754 for facilitating communication with one or more additional devices, one or more computers, and / or one or more servers. The memory 750 may include: graphical user interface instructions 756 for facilitating graphical user interface processing; sensor processing instructions 758 for facilitating sensor-related processing and functions; telephone instructions 760 for facilitating telephone-related processes and functions; electronic instant messaging instructions 762 for facilitating electronic instant messaging-related processes and functions; web browsing instructions 764 for facilitating web browsing-related processes and functions; media processing instructions 766 for facilitating media processing-related processes and functions; GNSS / navigation instructions 768 for facilitating GNSS- and navigation-related processes and instructions; and / or camera instructions 770 for facilitating camera-related processes and functions.

[0091] The memory 750 may store other software instructions 772 for facilitating other processing and functions, such as the remote keyboard processing and functions as referenced Figures 1 to 6 as described.

[0092] The memory 750 may also store: other software instructions 774, such as web video instructions, for facilitating web video-related processes and functions; and / or web shopping instructions for facilitating web shopping-related processes and functions. In some embodiments, the media processing instructions 766 are divided into audio processing instructions and video processing instructions for facilitating audio processing-related processes and functions and video processing-related processes and functions, respectively.

[0093] Each of the instructions and applications identified above may correspond to an instruction set for performing one or more of the above functions. These instructions need not be implemented as separate software programs, processes, or modules. The memory 750 may include additional instructions or fewer instructions. Additionally, various functions of the computing device 700 may be implemented in hardware and / or software, including in one or more signal processing and / or application specific integrated circuits.

Claims

1. A method, comprising: receiving, by a user device, a status advertisement message broadcast from a media device; determining, by the user device based on the status advertisement message, that a text input control on the media device is currently selected; presenting, by the user device in response to determining that the text input control on the media device is currently selected, a first graphical notification associated with the text input control; detecting, by the user device, movement of the user device; and in response to detecting the movement of the user device: presenting, on a display of the user device, a virtual keyboard for providing input to the text input control selected on the media device.

2. The method according to claim 1, wherein the first graphical notification prompts the user to invoke the virtual keyboard on the user device.

3. The method according to claim 1, wherein the virtual keyboard is provided by a software system of the user device that is different from any user application on the user device.

4. The method according to claim 1, further comprising: establishing, by the user device, a connection with the media device; receiving, by the user device, a first user input selecting one or more characters for the virtual keyboard; and sending, by the user device, the first user input to the media device.

5. The method according to claim 1, wherein the first graphical notification includes application data from the media device and instructions for activating the virtual keyboard.

6. A system, comprising: one or more processors; and a non-transitory computer-readable medium including one or more sequences of instructions that, when executed by the one or more processors, cause: receiving, by a user device, a status advertisement message broadcast from a media device; determining, by the user device based on the status advertisement message, that a text input control on the media device is currently selected; presenting, by the user device in response to determining that the text input control on the media device is currently selected, a first graphical notification associated with the text input control; detecting, by the user device, movement of the user device; and in response to detecting the movement of the user device: presenting, on a display of the user device, a virtual keyboard for providing input to the text input control selected on the media device.

7. The system according to claim 6, wherein the first graphical notification prompts the user to invoke the virtual keyboard on the user device.

8. The system according to claim 6, wherein the virtual keyboard is provided by a software system of the user device that is different from any user application on the user device.

9. The system according to claim 6, wherein the one or more sequences of instructions, when executed by the one or more processors, further cause: establishing, by the user device, a connection with the media device; receiving, by the user device, a first user input selecting one or more characters for the virtual keyboard; and sending, by the user device, the first user input to the media device.

10. The system according to claim 6, wherein the first graphical notification includes application data from the media device and instructions for activating the virtual keyboard.

11. A non-transitory computer-readable medium comprising one or more sequences of instructions that, when executed by one or more processors, cause: a user device to receive a status advertisement message broadcast from a media device; based on the status advertisement message, the user device to determine that a text input control on the media device is currently selected; in response to determining that the text input control on the media device is currently selected, the user device to present a first graphical notification associated with the text input control; the user device to detect movement of the user device; and in response to detecting movement of the user device: present a virtual keyboard on a display of the user device for providing input to the text input control selected on the media device.

12. The non-transitory computer-readable medium according to claim 11, wherein the first graphical notification prompts the user to invoke the virtual keyboard on the user device.

13. The non-transitory computer-readable medium according to claim 11, wherein the virtual keyboard is provided by a software system of the user device that is different from any user application on the user device.

14. The non-transitory computer-readable medium according to claim 11, wherein the one or more sequences of instructions, when executed by one or more processors, further cause: the user device to establish a connection with the media device; the user device to receive a first user input selecting one or more characters for the virtual keyboard; and the user device to send the first user input to the media device.

Citation Information

Patent Citations

  • Adaptable schema based payloads

    US20170359676A1