Reversible connector for accessory devices.

(54) Title: REVERSIBLE CONNECTOR FOR ACCESSORY DEVICES.

(54) Title: REVERSIBLE CONNECTOR FOR ACCESSORY DEVICES.

(57) Summary

Reversible connectors for accessory devices are described. In one or more implementations, a connector cable for an accessory of a host computing device is configured so that a head of the connector cable can be connected to a corresponding port on the housing in any orientation (forward or backward). The host computing device is configured to test signals associated with assigned connector terminals to detect connection of the connector to an accessory port and to check an orientation of the connector. A combination of high and low values ​​of the signals carried through these assigned terminals at the connector insert can be used by a housing controller to distinguish between different types of devices and to resolve the orientation of the connector wire. A trigger mechanism of the host computing device can then be configured to automatically route the signals accordingly.

(57) Abstract

Reversible connectors for accessory devices are described. In one or more implementations, a connector cable for an accessory of a host computing device is configured such that a head of the connector cable may be plugged into a corresponding port of the host in either orientation (straight or reverse). The host computing device is configured to sample signs associated with allocated pins of the connector to detect connection of the connector to an accessory port and to ascertain an orientation of the connector. A combination of high and low values ​​of signals conveyed via these allocated pins upon insertion of the connector may be used by a controller of the host to distinguish between different types of devices and to resolve the orientation of the connector cable. A switching mechanism of the host computing device may then be configured to automatically route sign accordingly.

REVERSIBLE CONNECTOR FOR ACCESSORY DEVICES

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanying figures. In figures, the digit (s) on the left side of a reference number identifies the figure in which the reference number appears first. The use of the same reference numbers in different instances in the description of the figures may indicate similar or identical items. The entities depicted in the figures may be indicative of one or more entities and thus interchangeably refers to individual or plural forms of the entities in the discussion.

Figure 1 is an illustration of an environment in an illustrative implementation that is operable to employ the techniques described herein.

Figure 2 depicts an illustrative computing device and accessory device of Figure 1 in greater detail.

Figure 3 describes an illustrative scenario for reversible connection of an accessory to an accessory port according to one or more implementations.

Figure 4 depicts an illustrative representation of a terminal arrangement for a connector in accordance with one or more implementations.

Figure 5 describes an illustrative procedure in accordance with one or more implementations.

Figure 6 depicts another illustrative procedure according to one or more implementations.

Figure 7 illustrates an illustrative system that includes various components of an illustrative device that can be implemented with any type of computing device to implement the modalities or techniques described herein.

DETAILED DESCRIPTION

General view

Today, mobile computing devices such as laptops and tablets can be configured to support and connect a variety of types of accessory devices by way of common universal serial (USB) conductors or other communication techniques. However, traditional accessory connectors, ports, and connecting cables are designed to connect in a single orientation. Consequently, users can often attempt to make connections in the wrong way, which not only frustrates the user, but can also result in wear and / or damage to connectors, ports, and connecting cables.

Reversible connector techniques for accessory devices are described. In one or more implementations, a connector cable for an accessory of a host computing device is configured such that a head of the connector cable can be plugged into a corresponding port on the housing in any orientation (forward or backward). The host computing device is configured to sample signals associated with the assigned connector terminals to detect the connection of the connector to an accessory port and to check a connector orientation. A trigger mechanism of the host computing device can then be configured to automatically route signals according to orientation. In one aspect, a pair of connector "sense" terminals is dedicated for hot plug detection. A combination of logic high and low states that are carried across these two sense terminals at connector insertion can be used by an enclosure controller to distinguish between different types of devices (for example, two-wire and one-wire devices). cable) and to resolve the orientation of the connecting cable. The lines associated with the two sense terminals can be tested together (for example, in parallel or in sequence) and the values ​​for the two lines obtained can be combined together to derive a combined logic state indicative of the device type and / or orientation of the device. connector. The controller can then operate to configure the signal routing according to the device type and orientation. In order to do this, the controller can be configured to direct positions for the switches and multiplexers of the housing and / or the connected accessory to effect the signal paths forward or backward as appropriate.

In the following discussion, an illustrative environment and devices 25 are first described as they may employ the techniques described herein.

Illustrative details and procedures are then described where they can be performed in the illustrative environment and by devices in addition to other environments and by other devices. Accordingly, the implementation of the illustrative details and procedures is not limited to the illustrative environment / devices and the illustrative environment / devices are not limited to the illustrative details and procedures.

Illustrative Operating Environment

Figure 1 is an illustration of an environment 100 in an illustrative implementation that is operable to employ the techniques described herein. The illustrated environment 100 includes an example of a host computing device 102 that is physically and communicatively coupled to an accessory device 104 through an interface 106. The host computing device 102 can be configured in a variety of ways. For example, computing device 102 can be configured for mobile use, such as a mobile phone, a tablet computer as illustrated, and so on. In that way, the host computing device 102 can vary from full resource devices with substantial memory and processor resources to a low resource device with limited memory and / or processing resources. Host computing device 102 may also refer to software that causes host computing device 102 to perform one or more operations.

The computing device 102, for example, is illustrated as including an input / output module 108. The input / output module 108 is representative of functionality that relates to the processing of the inputs and the representation of outputs of the computing device. host 102. A variety of different inputs can be processed by an input / output module 108, such as inputs that refer to the functions that correspond to the keys of the input device, keys of a virtual keyboard presented by the display device 110 to identify gestures and cause operations performed corresponding to the gestures that can be recognized through the accessory device and / or touch screen functionality of the display device 110, and so on. In that way, the input / output module 108 can support a variety of different input techniques by recognizing and leading to a division between types of inputs that include keystrokes, gestures, and so on.

Various configurations for an accessory device 104 are also contemplated, such as a keyboard, game controller, configuration to mimic a musical instrument, a power adapter, a docking station, a USB hub, an external battery, combinations of these. configurations, and so on. In that way, accessory device 104 can take on a variety of different configurations to support a variety of different functionality. Different accessory devices can be removably connected to the computing device at different times.

As previously described, accessory device 104 is physically and communicatively coupled to host computing device 102 in the example through an interface 106. Various types of interfaces 106 and connectors are also contemplated such as the use of a flexible hinge, magnetic coupling devices, integrated communication ports and communication contacts, mechanical coupling protrusions, grooves, and / or indentations, individually or in combination to form different types of interfaces 106. In one example, interface 5 106 may represent an accessory port (eg, communication port) configured to allow connection to accessory devices through a corresponding connector and / or connector cable. In accordance with the techniques discussed above and below, the accessory port and corresponding connector are designed to allow reversible connection of the connector to the port. In at least some implementations, interface 106 is configured to allow communications for authentication and control of accessory device 104 as described herein. For example, computing device 102 may receive credentials (eg, data indicative of an accessory's identity), signals, and other data regarding the capabilities of the accessory device through the interface response to detect the presence / attachment of accessory device 104. The interface may also provide a power coupling for exchanging power and message communication by implementing and updating the power management and control functions as described above and below.

As further illustrated in Figure 1, the computing device 102 may include an energy controller 112 configured to implement aspects of the energy management contact techniques 25 described herein. In particular, the power controller 112 represents functionality to perform various power management operations including managing configurations for power management based on accessory identities, facilitating the exchange of control messages between the enclosure and accessories, management of different power sources and activation between sources, implementing a defined and / or selected power management scheme, managing battery life, and so on. The power controller 112 can further facilitate connections and communications with a power adapter 114 (also referred to herein as a power supply unit (PSU) j configured to supply power to the device through an external power source. suitable 116, such as a wall outlet, external battery, power supply unit, or other power source. Power controller 112 may also be operable to supply power to accessory devices under suitable circumstances. In other words, the power controller 112 can jointly handle power operations for a host computing device and authorized accessory devices including power exchange between the host computing device and an accessory device.

Power controller 112 can be implemented in hardware, software, firmware, and / or combinations thereof. By way of example and not limitation, computing device 102 may include a microcontroller or other suitable hardware logic device configured to implement various functionalities described herein in relation to power controller 112. Power controller

112 it can therefore represent firmware or logic associated with a suitable hardware logical device. Additionally or alternatively, the power controller 112 may be implemented as a device processing system and one or more program modules that are executable / operable through the processing system.

Power adapter 114 can be configured to selectively operate in multiple modes and supply multiple levels of power to the computing device. The power level delivered at a particular time may be based on inputs, notifications, or other suitable configured feedback and is sent to power adapter 114 by power controller 112 to cause adapter 114 to deliver a corresponding level of power. Depending on a power exchange state, the power adapter 114, when connected to the computing device, can charge a battery associated with one or both of the housing and accessory, supply the power to support the operations of one or both of the housing and accessory, and otherwise supplying power from external power sources 116 to link the load and operation of the housing and accessory in various combinations. An implemented power scheme 20 through the power controller 112 can be configured to control the flow of power between system components (eg, housing, accessory, and adapter) based on accessory identity, power exchange conditions , availability of power source, and so on. Additional details regarding the operation of power controller 112 and power adapter 114 to implement power management contracts for accessory devices can be found in the following discussion.

Figure 2 generally depicts at 200 an illustrative host computing device 102 and an accessory device 104 in greater detail. In Figure 2, the host computing device 102 is described as having a power controller 112 which is illustrated as being provided by one or more microcontroller (s) 202, which also refers to the micro-controller unit (s). processing (μΡ). The computing device 104 further includes an associated power supply 204, such as one or more internal batteries. Accessory device 104 may also include one or more microcontroller (s) 206 and a respective power supply 208. The power supply 208 can be configured as one or more batteries that are internal to the accessory device 104 (eg, an accessory battery) and therefore can be considered as external batteries with respect to the host computing device 102.

Illustrative microcontrollers (μΡδ) represent hardware devices / systems that are designed to perform a predefined group of designated tasks. Microcontrollers can represent on-chip systems / circuits that have self-contained resources such as processing components, I / O devices / peripherals, various types of memory (ROM, RAM, flash, EEPROM, programmable logic, and so on. Different microcontrollers can be configured to implement applications / built-in functionality that are at least partially implemented in hardware and perform corresponding tasks. In particular, illustrative microcontrollers 202, 206 enable the performance of tasks for device authentication and off-line power management of a general purpose processing system and other applications / components of the computing device or accessory device. Generally, the power consumption of microcontrollers is low compared to operating a general-purpose processing system for one device.

Consequently, components implemented through microcontrollers can be operated using relatively low power, 10 regardless of operating a "primary" processing system of a host computing device, and / or without restarting / running an operating system or using other components. of device and applications. In other words, microcontrollers can operate by performing some power management tasks in a low power mode without having to operate or supply power to the processing system and other device components (e.g. device memory, network interface , display device, etc.) and / or without fully starting or waking up the computing device.

Host computing device 202 can be connected to 20 different accessory devices through accessory port 210. Accessory port 210 is representative of functionality to achieve a physical and communicative coupling between the host computing device and various advisors. For example, a connector 211 that corresponds to accessory port 210 can be used to connect accessories to the host computer and allow exchange of power, data, and control signals. In the example described, connector 211 is illustrated as a connector cable that can be removably inserted into a corresponding port associated with accessory interface 210, although other types of connections are also contemplated, such as the flexible hinge discussed in connection with Figure 1, connections to a docking station discussed in relation to the following figure, and / or other suitable interfaces and connector combinations. In accordance with the techniques described herein, the connector 211 and corresponding ports can be configured to support reversible connection / insertion of the connector / port combination.

As depicted in Figure 2, power exchange can occur between the housing power supply 204 and the accessory power supply 208 in accordance with the techniques described above and below. In some implementations, the power exchange can also occur with an external power source 116 configured as an external battery via a power adapter 114 as depicted in Figure 1. In other words, the exchange of three power paths can occur between the battery / power supplies that correspond to the housing, an accessory connected through the accessory interface, and an external power source. Generally, the exchange of power between the enclosure and one or more connected devices (adapters / accessories / peripherals) can occur again and after (for example, bi-directionally) the enclosure for one or more of the devices, one or more devices to the enclosure, and directly between connected devices (for example, device-to-device) through the enclosure.

Thus, power exchange can occur through accessory port 210 in some scenarios. Power supplied from the host computing device may be used to operate the enclosure (eg, systems load service) and / or to maintain a charge level of the power supply 204 (eg, internal battery). Additionally, power supplied to the housing may be supplied directly or indirectly to accessory device 104 to support operations and / or charge power supply 208 (eg, external battery). In addition, power can be distributed from host computing device 102 and / or accessory device 104 to one or more peripherals 212 that can be directly connected to the host computing device and / or connected to the system through accessory device 104 as shown. represented in Figure 2. For example, in one or more implementations an accessory device may be configured to provide the functionality of a peripheral device hub, such as a hub that provides multiple Universal Serial Common Conductor (USB) ports and / or other types of USB ports. connection where a variety of peripherals 212 can be connected. Peripherals 212 can include various devices, such as a peripheral display device, a printer, a scanner, audio devices, a camera, a storage device, or a network adapter, to name a few.

It will be appreciated that host computing device 102 and accessory device 104 can both be configured to employ external power sources 116, such as through the use of respective power adapters 114 connected to the wall outlet or other source. Power supplied directly to accessory device 104 through 5 through a respective power adapter 114 can be used, shared, and / or exchanged between the housing and accessory in a manner comparable to power that is supplied directly to the host computing device. 102.

The host computing device can further be configured to implement a power scheme 214 and a security module 216 in various ways. In the illustrated example, the power scheme 214 is described as being implemented through the power controller 112. In this example, the power scheme 214 is configured as firmware associated with the host computing device 102. For example, power schematic 214 may represent firmware associated with a microcontroller 202, power controller 112, or other suitable hardware logic device. Alternatively, the power scheme 214 can be implemented as a stand-alone module using any suitable combination of hardware, software, firmware, and / or logic devices.

Power scheme 214 represents functionality to implement power management contraction techniques described above and below in addition to other power management functions. In particular, the power scheme 214 can be configured to jointly handle power flow between a power adapter.

114, host computing device 102, and accessory device 104. By way of example and not limitation, this may include controlling power flow by selectively charging batteries associated with components; exchange power between batteries, processing systems, and components; supply power to service the system load for the housing and accessory; and so on. To do this, the power scheme 214 can provide functionality to establish, enforce, and update power management contracts 218 between various components of the system. This functionality may include support for sending and receiving messages regarding power management between system components that can be configured in a variety of ways. For example, the messages can be configured as pulsed signal patterns that are recognizable by the respective controllers of the enclosure and accessory. Various suitable messaging protocols and corresponding message formats are also contemplated, such as when using internal-integrated circuit protocol (l²C), Serial Peripheral Interface (SPI), Universal Asynchronous Receiver / Transmitter Messaging (UART), Communications-Based Packet, and Message-Based Object, to name a few. Furthermore, wireless messaging protocols such as near field communication, Bluetooth, Wi-Fi, RF protocols used in RFID, or cellular telecommunication protocols can be used.

Energy management contracts 218 are configured to define operational restrictions for energy management that include but are not limited to specific energy exchange direction and current limits for different devices and scenarios. Furthermore, the settings for the power management contracts 218 can be modified in real time based on the conditions observed by the enclosure or accessory. In that way, the initial or default settings for the energy management contracts 218 can be associated with different accessories and suitable contracts can be activated on the initial connection and authorization of the different accessories. Initially activated power management contracts 218 may later be modified based on conditions that include but are not limited to Related State of Charge (RSOC) for system component batteries, power loads being serviced, a number of 212 peripherals connected to the enclosure and / or accessory, availability of power source for system components, power supply characteristics, processing loads, and so on 15. Thus, although operating restrictions are set for energy exchange at the time accessories and / or peripherals are connected to the system, the energy management contracts discussed here are designed to allow dynamic adjustments to such contracts in response to changing conditions. conditions at any time during the connection of an accessory to a housing. Such initial configuration modifications for a power management contract 218 based on "real time" conditions can be initiated by the accessory devices and / or by the host computing device.

Security module 216 represents functionality operable to identify and / or authenticate accessory devices when devices are attached / connected to computing devices. Security module 216 can be configured to implement a variety of different authentication techniques. Generally speaking, security module 216 performs an authentication sequence in which credentials 220 (eg, device password ID, alphanumeric code, an identification resistor value, etc.) associated with an accessory device 104 are obtain and verify. In one aspect, security module 216 is configured to provide functionality to support techniques for reversible connections from connector 211 to the accessory port. For example, the security module 216 may represent functionality of the one or more microcontrollers 202 to detect insertion of the connector into the accessory port, connector sample detection terminals 211 to check an orientation of the connector as being forward or facing back according to the values ​​for the detection terminals, and / or distinguish between different types of communication devices and / or protocols based on the sample. Distinguishing between different types of devices can include distinguishing between two-wire devices that use separate RX and TX lines and one-wire devices where RX / TX are combined into a single line or channel. Additionally, the security module 216 may represent functionality to configure signal routing accordingly based on the tested orientation and / or device type.

In addition, the accessory device 104 of Figure 2 is illustrated as including illustrative credentials 220, which may be provided to the security module 216 for authentication on request. If the credentials are valid (for example, the device is a recognized device that has associated privileges), then the authentication is considered successful and the accessory device 104 can be authorized for power exchange through the power controller 112 and other interaction. with host computing device 102. In addition, the credentials 220 can be associated with the power management contract settings held for the authorized device and thus can be used to observe and activate such settings (eg, initial or default settings) for different devices on successful authentication. On the other hand, if the credentials are not valid, the interaction of the accessory device 104 with the computing device 102 can be restricted in various ways and / or prevented. In that way, the security module 216 can prevent unauthorized and / or unsupported devices from supplying / using power in ways that may be inefficient and / or unsafe.

Having considered the preceding discussion of illustrative operating environment, systems, and devices, now consider a discussion of illustrative devices, procedures, and scenarios that includes additional details regarding techniques for implementing reversible connectors for accessory devices.

Reversible Connector Details

Figure 3 generally depicts an illustrative scenario 300 for reversible connection of a connector to an accessory port in accordance with one or more implementations. In this example, representative views of a connector 211 are described in the forward and rearward orientation. As mentioned, the techniques for reversible connectors discussed here can rely on the dedicated sense terminals of connector 211 and correspond to the circuits / signals formed across the sense terminals. In one aspect, a pair of sense terminals is employed for an interface 106 to support hot plug detection and connections for device authentication, power exchange, signal routing control, and so on. Interface 106 is configurable based on device type and / or connector orientation to switch between different signal routing options (eg, forward / backward) and communication techniques (one-wire / two-wire).

Here, a pair of sensing terminals including an A terminal 302 (also referred to herein as an "HDP1A") and a B terminal 304 (which is also referred to herein as "HPD1B") is described. Although a pair of sense terminals is shown, generally speaking two or more sense terminals can be assigned by accessory hot sense connection detection and sampled to facilitate resolution of connector orientation and device type based on carrier signals. / read through the sense terminals. In the illustrated example, terminal A 302 and terminal B 304 are shown as being located generally on opposite edges and / or sides of a head of connector 211. A variety of other terminals 306 to support different communication protocols, common conductors, and high speed signals is also incorporated into connector 211. By way of example, in addition to providing the terminals for authentication / power exchange / control, the connector 211 may provide terminals to support USB signals, audio / video, a presentation port, network communications, and so on. Generally, the terminals are arranged as high-speed pairs of terminals. Terminals 302, 304, 306 are configured to mate with a group of add-on terminals 308 included with an accessory port 210 of the host computing device.

In the illustrated layout terminal A 302 and terminal B 304 they are configured to respectively mate with the RX and TX terminals associated with the accessory port 210 of the host computing device 102 in the "forward" orientation. In this arrangement, RX signals can be carried through terminal A 302 and TX signals can be carried through terminal B 304. When the connector is flipped or reversed to assume the "rearward" orientation also described in Figure 3, terminal B 304 now matches terminal RX and terminal A 302 now matches terminal TX. In other words, these terminal connections have physically changed positions. In the absence of correct reversal, the RX / TX may end up crossing over.

The host computing device, however, may include or otherwise make use of a trigger mechanism 310 to "straighten out" the signal routing. The trigger mechanism provides operable functionality to control signal routing so that signals are effectively communicated between the same end points with respect to connector orientation. Trigger mechanism 310 is used to selectively change signal paths for the system by configuring the accessory port and / or the corresponding interface based on the orientation of the connector and / or for the particular type of device. That way, for example, even when the connector is in the "rearward" orientation described in Figure 3, the trigger mechanism 310 can operate to change the signal routing so that the RX signals are still carried through the Terminal A 302 and TX signals are carried through terminal B 304. By way of example, trigger mechanism 310 may include one or more multiplexers 312 and / or switches 314 to allow control over the signal paths. Although the trigger mechanism 310, multiplexers 312, and switches 314 are shown as components of the housing device, multiplexers 312 and switches 314 used for selective inversion for some signal paths may be associated with an accessory device 104 as well. or alternatively to trigger mechanism 310, multiplexers 312, and housing switches 314. In this case, the host computing device 102 may operate to send commands to the accessory to cause the configuration of the signal routing through the accessory signal that activates the components under the direction of the housing.

Figure 4 generally depicts at 400 a representative example showing the details of, but an example of terminal arrangement for a connector head 402 of a connector 211. In this example, the connector includes forty terminals. Terminal A 302 and terminal B 304 are shown as being at opposite ends of connector head 402 and opposite sides of connector 211. Terminal A 302 and terminal B 304 are labeled "HDP1A" and "HPD1B" in the example, respectively. The labels "HDP1A" and "HPD1B" are used interchangeably with the terms terminal A and terminal B in this document. Several other terminals 310 for the transport of different types of signals and data are also arranged within the connector head 402, including for example terminals for USB2, USB2, power exchange, and so on. Illustrative terminal arrangements are shown and described in Figures 3 and 4 which are referred to as illustrative examples only and are not intended to limit the terminal arrangements and connector configurations that may be employed in accordance with the disclosed techniques. Additional details regarding the techniques associated with reversible connectors 20 for accessory devices are discussed in connection with the following illustrative procedures.

Illustrative Procedures

The following discussion describes techniques that can be implemented using the systems and devices previously described. Aspects of each of the procedures can be implemented in hardware, firmware, software, or a combination thereof. The procedures are shown as a group of blocks that specify operations performed by one or more devices and are not necessarily limited to the 5 commands shown to perform operations by the respective blocks. In portions of the following discussion, reference may be made to the illustrative operating environment 100 of Figure 1 and the illustrative devices and scenarios of Figures 2-4. Aspects of the procedures may be performed by a suitably configured computing device 10, such as the illustrative host computing device 102 of Figure 2 which includes or otherwise makes use of one or more microprocessors 202 to support reversible connectors 211. Additionally or alternatively, aspects of the procedures may be performed through an accessory device, such as the illustrative accessory device 104 of Figure 2 that includes or otherwise makes use of one or more microprocessors 206.

Figure 5 depicts an illustrative procedure 500 in which the signal routing is configured according to the orientation of the reversible connector. The connection is detected from a connector for an accessory device to an accessory port of a host computing device, the connector and accessory port configured to support reversible connection of the connector to the accessory port (block 502). For example, one or more microcontrollers 202 associated with a host computing device 102 can be configured to recognize the connection of the various devices for an accessory port 210. Detection can occur in a number of ways. In one aspect, the one or more microcontrollers 202 are capable of detecting the signals sent by an accessory device when a connector 211 is successfully attached to accessory interface 210. The signals can comprise logic states, a voltage input signal, a pulsation pattern, static resistor values, and so on. Alternatively, host computing device 102 can be configured to query accessory port 210 to determine when devices are fixed or separated from it, such as by monitoring the sense lines and reading the resistor values ​​that correspond to the accessory. The fixture can initiate further processing to determine the identity and / or type of device associated with an accessory in addition to the orientation of the connector. The signal routing lines and / or communication interface (s) between the housing and the accessory can then be configured to match the type of accessory and orientation of the connector.

In particular, after attaching the accessory device, an orientation of the connector connection to the accessory port is checked (block 504). Orientation can be solved in several ways. Generally, the orientation is determined based on the signals sampled at the detection terminals described herein. The particular values ​​and / or patterns that are conveyed in the connection of a connector are indicative of the type of device in addition to the orientation of the connector. Then, a host computing device trigger mechanism is configured to automatically route the signals according to orientation (block 506). For example, one or more microcontrollers 202 of a host computing device may operate by configuring a trigger mechanism 310 in the manner previously described to configure signal paths based on a proven orientation of a connector 211. This may involve the positioning of multiplexers 312 and switches 314 associated with trigger mechanism 310. Additionally or alternatively, microcontrollers 202 may communicate with microcontrollers 206 of an accessory device 104 to notify the accessory device regarding the orientation of the connector and / or direct the accessory device 104 to reconfigure a trigger mechanism in the accessory side in accordance with the appropriate signal routing settings. In this way, the end points for the signal paths can remain the same with respect to the orientation of the connector. In this way, consumers can connect in the 15 accessories to a housing device through a reversible cable either in orientation (forward or backward) and the system automatically describes the orientation and secures those signals so that they are not combine.

In one or more implementations, dedicated sense terminals 20 can be used for hot plug detection and orientation resolution as described herein. The detection can be based on a voltage (for example 5V) that is applied to the detection lines and corresponds to the logic states for the terminals, for example high = 1, or low = 0, which are obtained / read in response to the applied voltage. Possible different combinations of logic states for the detection lines can be associated with a group of detection cases each of which corresponds to a type of device and / or an orientation of a connector 211. The lines associated with the sense terminals can be sampled together (for example, in parallel or in sequence) and the values ​​to obtain the different lines can be combined together to derive a combined logic state that is indicative of the device type and / or orientation of the device. connector. Accordingly, a table, file, database, or other data structure can be established as it reflects the mapping of logical state combinations (or other credential / accessory identifiers) with corresponding discovery cases. In operation, the one or more microcontrollers 202 can verify the sense terminals and obtain the values ​​on each sense line. The microcontrollers 202 may make use of an assignment of the possible logical state combinations with the corresponding detection cases to resolve the device type and connector orientation.

With respect to device type, logical state combinations provide a mechanism to allow the enclosure to distinguish between different types of devices. In particular, a logic detectable state combination indicates whether a device is a one-wire device that can communicate over a single line with the combined RX and TX or a two-wire device that uses two different lines for RX and TX. . One-wire devices can be relatively simple and inexpensive devices that do not use complex communication schemes, such as a basic power adapter or external battery. Two-wire devices can be devices that provide functionality involving advanced interfaces, high-speed communications, and / or multiple types of data / protocols, such as a docking station, multi-media accessory, and so on.

In the case of a pair of sense terminals assigned for housing connector detection, such as HDP1A and HPD1B (for example, terminal A 302 and terminal B 304), there are four possible combinations of logic state, for example, high- high, high-low, low10 high, and low-low. Logic states are indicative of device type (for example, one wire or two wires) and can also be used to directly or indirectly resolve the orientation of the connector. In particular, both the HDP1A and HPD1B terminals are not checked (eg in a low state) in the absence of a connected accessory. When an accessory device is connected to the housing, the particular combination of the states for HDP1A and HPD1B determines the type of accessory. For one-wire devices, the line on which a high state is checked can be determined. Accordingly, the logic state combination for a one-wire device also reflects the connector orientation and can be used directly to check the orientation. For two-wire devices, both lines have high states and thus the logic state combination may be insufficient to resolve orientation. Therefore, further processing can be performed as described below to check the orientation of a two-wire device.

Thus, for the HDP1A and HPD1B sense terminals, the following shows an illustrative table showing an illustrative mapping of possible logical state combinations for the detection scenarios:

TABLE 1: Detection Pin Logical State Assignment

<td></td><td>HPD1A Height = 1</td><td>HPD1A Low = 0</td>

<td>HPD1B Height = 1</td><td>Two-wire accessory</td><td>One cable accessory (backwards)</td>

<td>HPD1B Low = 0</td><td>One cable accessory (forward)</td><td>Without fixed accessory</td>

In the table above, the values ​​1, 1 (high-high) indicate a two-wire accessory, 1, 0 (high-low) indicate a one-wire accessory in a forward orientation, 0, 1 (low-high) indicate a one-wire accessory in a rearward orientation, and 0, 0 (low-low) indicate that no accessory is fixed. After determining the device type using a mapping such as the example in Table 1, further processing can occur to perform device authentication / orientation, determine a particular identity and / or device capabilities (as opposed to just determining one cable versus two cables), and configure the housing and / or accessory trigger mechanisms to properly route signals.

For example, for a one-wire device, the sample can occur through the tested terminal (either HDP1A or HPD1B) to identify and authorize the device. This can involve several different authentication techniques as described previously. Authentication allows the enclosure / microcontroller to recognize unsupported accessories and determine specific configuration information for the supported accessories based on the identity of the particular accessory to configure the interface and signal routing accordingly. For example, accessory devices can be configured to supply credentials 220 to the enclosure in various ways as previously mentioned. In one aspect, the access devices are configured to display a respective resistor value indicative of identity for reading by the host computing device.

Different resistor values ​​can be associated with different accessories. That way, when an accessory is connected, the host computing device can read a corresponding resistor value and distinguish between different accessories on this base. Alternatively, other credentials 220 may be communicated to the enclosure by an accessory by indicating its identity, such as by sending a particular numeric code, an ID field value, a device name, and so on.

As noted, when the fixture is a two-wire device, the logic state combination is not sufficient to allow an orientation determination. In this case, the orientation is resolved through the authentication sequence. In order to do this, the supported two-wire devices can be configured to supply the credentials 220 to the enclosure over either or both of the signal lines. In this case, the sample occurs on both for HDP1A or HPD1B to identify and authorize the two-wire device. In one aspect, the two-wire device may have ID resistors associated with one or both lines and may display resistor value (s) indicative of identity. Again, other credentials 220 may also be communicated to the accommodation by an accessory to indicate their identity. The orientation can then be determined based on the assignment of the validated ID states for each line, eg, valid or invalid, for possible orientation cases. Thus, for the HDP1A and HPD1B detection terminals, the following shows an illustrative table showing an illustrative assignment of cases of ID validated status 10 orientation:

TABLE 2: Two-Wire Sense Terminal ID Validity Status Assignment

<td></td><td>HPD1A: Valid ID</td><td>HPD1A: Invalid id</td>

<td>HPD1B: Valid ID</td><td>Both orientations supported. Configure based on application</td><td>2-wire accessory (rearward)</td>

<td>HPD1B: Invalid id</td><td>2-wire accessory (forward)</td><td>accessory not supported</td>

Figure 6 depicts an illustrative procedure 600 illustrating illustrative logic for processing that may occur to detect both device type and orientation according to one or more implementations. In particular, procedure 600 is represented by an illustrative technique that can be employed to resolve device type and connector orientation in connecting an accessory to a housing. Procedure 600 additionally represents one possible implementation of the assignments for the detection terminals HDP1A and HPD1B reflected in Table 1 and Table 2 described above.

An accessory port is monitored (block 602) to detect the connection of an accessory through a corresponding connector cable. Monitoring can be implemented by a microcontroller 202 and / or security module 216 as described herein. Accessory port 218 and connector 211 can be configured to have a pair of terminals assigned for detection, eg, detection terminals HDP1A and HPD1B. A determination is made as to whether any of the HDP1A and HPD1B terminals are checked (eg, high signal value = 1) (block 604). If not, the port check continues through block 602. If at least one of the terminals is checked, a check is made to determine if both terminals are checked (block 606). If both terminals are not tested, procedure 600 proceeds to the operations associated with a one-wire configuration and otherwise both terminals are tested and procedure 600 proceeds to the operations associated with a two-wire configuration.

For a cable configuration, a determination is made as to whether HDP1A is checked (block 608) and if so, HDP1A is sampled (block 610) to obtain the credentials for identification. Based on the credentials, an ID of the attached accessory becomes valid (block 612) and when the ID is valid, the system is configured for a forward facing cable (block 614). On the other hand, if the accessory ID is invalid, which is an unsupported accessory (block 616), the interaction can be restricted. If HDP1A is not checked by block 608, the other terminal HPD1B is the checked terminal and 5 is sampled (block 618). ID validation occurs again (block 620) and either the ID is valid and the system is configured for a cable in the rearward orientation (block 622) or the ID is invalid the accessory that is a non-accessory. supported (block 616) and can be restricted.

For the two-wire configuration, both HDP1A and HPD1B 10 are sampled (block 624). ID validation occurs for HDP1A (block 626) and then for HPD1B (block 628) if the ID sampled in HDP1A is valid. If the IDs for both HDP1A and HPD1B are valid, then both forward and backward orientations are supported and configuration occurs based on the application (block 15,630). Otherwise, if only the ID for the HDP1A is valid, then the system is configured for two cables in forward orientation (block 632). If HDP1A is invalid by block 626, ID validation occurs for HPD1B (block 634). If HPD1B is valid for block 634, then the system is configured for two cables in rearward orientation (block 636). Otherwise, the sampled IDs for both HDP1A and HPD1B are invalid and the accessory is an unsupported accessory (block 638) and can be restricted. Following the proper configuration of the system based on the logic described, the signals are routed using the configuration that is applied (block 640).

Illustrative procedure 600 can be implemented in software, firmware, hardware, or a combination of each or some thereof. A software or firmware implementation can be flexible and advantageously reconfigured with a software or firmware update. Alternatively, illustrative method 600 can be implemented using discrete and analog logic gates and combined signal circuits, including analog to digital circuits. This alternative can be advantageously faster and can also comprise programmable thresholds, for example, to determine resistor values. Due to the binary nature of decisions, digital logic can be used extensively.

Having considered the above illustrative procedures, now consider a discussion of illustrative systems and devices that can be employed to implement aspects of reversible connector techniques in one or more embodiments.

Illustrative System and Device

Figure 7 illustrates an illustrative system generally at 700 that includes an illustrative computing device 702 that is representative of one or more computing systems and / or devices that can implement the various techniques described herein. The computing device 702 can, for example, be configured to assume a mobile configuration through the use of shaped and sized storage that is held and carried by one or more hands of a user, illustrated examples of which include a mobile phone, mobile music and gaming device, and tablet computer, although other examples are also contemplated.

The illustrative computing device 702 as illustrated includes a processing system 704, one or more computer-readable media 706, and one or more I / O interfaces 708 that are communicatively coupled to each other. Although not shown, the computing device 702 may further include a common system or other data conductor and the command transfer system that couples the various components together. A system common conductor may include any one or combination of different common conductor structures, such as a memory common conductor or memory controller, a peripheral common conductor, a universal series common conductor, and / or a common serial conductor. local processor using any of a variety of common driver architectures. A variety of other examples are also contemplated, such as control and data lines.

System 704 is representative of functionality to perform 15 or more operations using hardware. Accordingly, the processing system 704 is illustrated as including the hardware element 710 that can be configured as processors, functional blocks, and so on. This can include implementation in hardware such as an application specific integrated circuit or other logic device formed using one or more semiconductors. The hardware elements 702 are not limited by the materials of which they are formed or the processing mechanisms employed herein. For example, the processors can be composed of semiconductor (s) and / or transistors (eg, electronic integrated circuits (IC)). In such a context, the processor executable instructions may be electronically executable instructions.

Computer-readable storage medium 706 is illustrated as including memory / storage 712. Memory / storage 712 represents memory / storage capacity associated with one or more computer-readable media. Memory / storage component 712 can include volatile media (such as random access memory (RAM)) and / or non-volatile media (such as read-only memory (ROM), flash memory, optical discs, magnetic discs, and so on. successively). The memory / storage component 712 may include fixed media (eg, RAM, ROM, a fixed hard drive, and so on) in addition to removable media (eg, flash memory, a removable hard drive, an optical disk, and so on. successively). Computer-readable media 706 can be configured in a variety of other ways as further described below.

The input / output interface (ces) 708 is representative of functionality to allow a user to enter commands and information to the computing device 702, and also to allow the information to be presented to the user and / or other components or devices using various input devices. /departure. Examples of input devices include a keyboard, a cursor control device (for example, a mouse), a microphone, a scanner, touch functionality (for example, capacitive or other sensors that are configured to detect physical touch), a camera (for example, that they can use visible or non-visible wavelengths such as infrared frequencies to recognize movement as gestures that do not involve touch), and so on. Examples of output devices include a display device (eg, a monitor or projector), speakers, a printer, a network card, a touch response device, and so on. In that way, the computing device 702 can be configured in a variety of ways to support user interaction.

The .702 computing device is further illustrated as being communicatively and physically coupled to an accessory device 714 that is physically and communicatively removable from the 702 computing device. In this way, a variety of different input devices can be attached to the device. 702 computers that have a wide variety of configurations to support a wide variety of functionalities. In this example, accessory device 714 includes one or more controls 716, which can be configured as pressure sensitive keys, mechanically actuated keys 15, buttons, and so on.

Accessory device 714 is further illustrated as including one or more modules 718 that can be configured to support a variety of functionalities. The one or more modules 718 for example, can be configured to process analog and / or digital signals 20 received from controls 716 to determine if an input was expected, determine if an input is indicative of quiescent pressure, support accessory device authentication 714 for operation with computing device 702, and so on.

Various techniques can be described here in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, and so on that perform particular tasks or implement particular abstract data types. The terms "module", "functionality", and "component" as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform independent, referring to techniques that can be implemented on a variety of commercial computing platforms that have a variety of processors.

An implementation of the described modules and techniques may be stored on or transmitted through some form of computer-readable media. Computer-readable media may include a variety of media that can be accessed by computing device 702. By way of example, and not limitation, computer-readable media may include "computer-readable storage media" and "computer-readable media. computer readable signal ”.

"Computer-readable storage media" refers to media and / or devices that allow the storage of information in contrast to the mere transmission of signal, carrier waves, or signals per se. Thus, the computer-readable storage medium does not include signals per se or signal transport means. Computer-readable storage medium includes hardware such as volatile and non-volatile, removable and non-removable media and / or storage devices implemented in a suitable method or technology for storing information such as computer-readable instructions, data structures, modules. program, logic elements / circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile discs (DVD) or other optical storage, hard drives, cassettes magnetic, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage device, tangible medium, or article of manufacture suitable for storing the desired information and which can be accessed by a computer.

"Computer-readable signal media" may refer to a signal transport medium that is configured to transmit instructions to the hardware of the computing device 702, such as over a network. The signal media typically can incorporate computer-readable instructions, data structures, program modules, or other data into a modulated data signal, such as carrier waves, data signals, or other transport mechanism. The signal means also include any means of supplying information. The term "modulated data signal" refers to a signal that has one or more of its characteristics set or changed in such a way that it encodes the information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.

As previously described, hardware elements 710 and computer-readable media 706 are representative of modules, programmable device logic and / or fixed device logic implemented in a form of hardware that can be employed in some embodiments to implement at least some aspects of the techniques described here, such as performing one or more instructions. Hardware can include components of an integrated circuit or system on chip, microcontroller devices, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a complex programmable logic device (CPLD), and others. implementations in silica or other hardware. In this context, the hardware can operate as a processing device that performs program tasks defined by the instructions and / or logic incorporated by the hardware in addition to a hardware used to store the instructions for execution, for example, the readable storage medium. by computer previously described.

Combinations of the above can also be used to implement various techniques described herein. Accordingly, software, hardware, or executable modules may be implemented as one or more instructions and / or logic embedded in some form of computer-readable storage media and / or by one or more elements of hardware 710. The computing device 702 can be configured to implement particular instructions and / or functions that correspond to the software and / or hardware modules. Accordingly, the implementation of a module that is executable by computing device 702 as software can be achieved at least partially in hardware, for example, through the use of computer-readable storage media and / or hardware elements 710 of the system. processing 704. The instructions and / or functions may be executable / operable by one or more articles of manufacture (eg, one or more computing devices 702 and / or processing systems 704) to implement techniques, modules, and examples described herein.

conclusion

Although the illustrative implementations have been described in language specific to structural features and / or methodological acts, it will be understood that the implementations defined in the appended claims are not necessarily limited to the specific features or acts described. Rather, the specific features and acts are described as illustrative ways of implementing the claimed features.