Abstract:
A graphical user interface (“GUI”) can be presented on a remote control accessory device that has user input and display devices. The GUI can be defined and managed by a portable media device that is controlled using the GUI. The portable media device can provide the accessory with a GUI image to be displayed. The accessory can send information to the portable media device indicative of a user operation of an input device in response to the displayed image. The portable media device can process this input to identify the action requested by the user and take the appropriate action, which can include updating the GUI image provided to the accessory.
Abstract:
An application can be launched in response to a launch request from an accessory. For example, the mobile computing device can determine whether it is in a state that allows launching of an application and/or can determine whether the application or application type requested in the launch command is available for launching. In response to the request, and if the mobile computing device is capable, the mobile computing device can launch the application. The mobile computing device can also send a positive acknowledgment message to the accessory indicating that the application may be launched. An open communication session message may also be sent to the accessory. In response thereto the accessory can open a communication session and interoperate with the application.
Abstract:
An authentication process for an endpoint device uses a pair of tokens. Tokens are generated at an authentication server that maintains a data store of token states, where the states are defined to include a “normal” state sequence along which a token is expected to advance. The endpoint device can store a token pair in non-volatile local storage. To authenticate, the endpoint device can provide its stored token pair to the authentication server, which can determine whether authentication succeeds based on the states of the tokens in the token pair. After successful authentication, the authentication server can provide a new token pair to the endpoint device and advance the token states along the normal sequence. When the endpoint device confirms receipt of the new token pair, which replaces the previous token pair, the authentication server can advance the state of the tokens again.
Abstract:
An authentication process for an endpoint device uses a pair of tokens. Tokens are generated at an authentication server that maintains a data store of token states, where the states are defined to include a “normal” state sequence along which a token is expected to advance. The endpoint device can store a token pair in non-volatile local storage. To authenticate, the endpoint device can provide its stored token pair to the authentication server, which can determine whether authentication succeeds based on the states of the tokens in the token pair. After successful authentication, the authentication server can provide a new token pair to the endpoint device and advance the token states along the normal sequence. When the endpoint device confirms receipt of the new token pair, which replaces the previous token pair, the authentication server can advance the state of the tokens again.
Abstract:
Techniques are disclosed relating to securing an accessory interface on a computing device. In various embodiments, a computing device detects a connection of an accessory device to an accessory interface port and, in response to the detected connection, evaluates a policy defining one or more criteria for restricting unauthorized access to the accessory interface port. Based on the evaluating, the computing device determines whether to disable the accessory interface port to prevent communication with the connected accessory device. In some embodiments, the computing device includes an interconnect coupled between the processor and the accessory interface port, and the interconnect includes a hub circuit configured to facilitate communication between a plurality of devices via the interconnect. In some embodiments, the computing device, in response to determining to disable the accessory interface port, instructs the hub circuit to prevent traffic from being conveyed from the accessory interface port.
Abstract:
Embodiments disclosed herein provide for identification processes and/or procedures for accessories coupled with a mobile computing device. During identification an accessory can communicate lingo information that includes only those lingoes the accessory can use while coupled with the mobile computing device. The accessory can also communicate accessory protocol information to the mobile computing device during identification. The accessory can be limited to using only those lingoes and/or those protocols identified during identification. Various other accessory information, capabilities, preferences, etc. can also be communicated to the mobile computing device during identification.
Abstract:
Shareable code objects (including a data object and/or executable program code) can be shared between accessories and mobile devices to facilitate interoperation of accessories and mobile devices. For instance, a shareable code object that contains configuration data for a particular accessory can be obtained by a mobile device from one accessory and subsequently shared with other accessories of similar type when they connect to the mobile device. As another example, a shareable code object that includes executable program code can facilitate interoperation of the accessory and the mobile device without the user having to download and install an app.
Abstract:
An adapter can be used to connect a portable electronic device to an accessory in instances where the portable electronic device and the accessory have incompatible connectors. The adapter provides two connectors, one compatible with the portable electronic device and the other compatible with the accessory. The adapter has several modes of operation. The portable electronic device selects the appropriate mode of operation for the adapter once it receives information about the accessory connected to the adapter. The portable electronic device instructs the adapter to switch to the selected mode and in response the adapter configures its internal circuitry to enable the selected mode. The portable electronic device can then communicate with the accessory via the adapter. The presence of the adapter can be transparent to the accessory.
Abstract:
A graphical user interface (“GUI”) can be presented on a remote control accessory device that has user input and display devices. The GUI can be defined and managed by a portable media device that is controlled using the GUI. The portable media device can provide the accessory with a GUI image to be displayed. The accessory can send information to the portable media device indicative of a user operation of an input device in response to the displayed image. The portable media device can process this input to identify the action requested by the user and take the appropriate action, which can include updating the GUI image provided to the accessory.
Abstract:
Techniques are disclosed relating to securing an accessory interface on a computing device. In various embodiments, a computing device detects a connection of an accessory device to an accessory interface port and, in response to the detected connection, evaluates a policy defining one or more criteria for restricting unauthorized access to the accessory interface port. Based on the evaluating, the computing device determines whether to disable the accessory interface port to prevent communication with the connected accessory device. In some embodiments, the computing device includes an interconnect coupled between the processor and the accessory interface port, and the interconnect includes a hub circuit configured to facilitate communication between a plurality of devices via the interconnect. In some embodiments, the computing device, in response to determining to disable the accessory interface port, instructs the hub circuit to prevent traffic from being conveyed from the accessory interface port.