Handheld controller with interchangeable controls

Abstract

To provide a handheld controller having an exchangeable control unit.SOLUTION: A handheld controller includes a housing having one or more receiver parts for being detachably coupled to one or more control units. For instance, the housing of such one controller can include a receiver configured to detachably connect to one or more joysticks, one or more D pads, one or more track pads, and / or one or more buttons on a front surface of the housing. In some case, a user can exchange a first control unit for a second control unit on the basis of a current application (e.g., a game title) being played by the user, comfort of the user, and / or for some other reason.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. patent application Ser. No. 16 / 134,612, filed Sep. 18, 2018, entitled "Handheld Controllers With Swappable Controls," the entire contents of which are incorporated herein by reference. [Background technology]

[0002] Handheld controllers are used in a range of architectures, for example, to provide input to local or remote computing devices. For example, handheld controllers are utilized in the gaming industry to enable players to interact with personal computing devices running game applications, game consoles, game servers, etc. While current handheld controllers offer a variety of functionality, further technological improvements may enhance the user experience these controllers provide. [Brief explanation of the drawings]

[0003] The detailed description will now be described with reference to the accompanying drawings, in which the leftmost digit(s) of a reference number refers to the figure in which the reference number first appears. Use of the same reference number in different figures indicates similar or identical components or functions.

[0004] [Figure 1] FIG. 1 is a front view of an exemplary handheld controller that includes, in part, a receiver configured to removably couple to different controls, such as a joystick and a directional pad (D-pad). [Figure 2] 2A and 2B show cross-sectional and perspective views of the receiver of the handheld controller of FIG. 1 when coupled to a detachable joystick. As shown, the controller, in this example, includes a Hall Effect sensor for determining that the controller is currently coupled to a joystick. [Figure 3] 1A-1C show perspective and cross-sectional views of two different detachable joysticks, as well as a cross-sectional view of a receiver of a handheld controller that can be configured to accept each of the different joysticks. [Figure 4] 1A-1C show perspective, cross-sectional side, and cross-sectional top views of two different detachable D-pads, as well as a cross-sectional view of a receiver of a handheld controller that can be configured to accept each of the different D-pads. [Figure 5] 1 shows an example where the receiver includes RFID functionality to identify which control, such as a detachable joystick, is currently coupled to the receiver. In this example, a flat joystick is shown as the coupling to the receiver. [Figure 6] 1 shows another example in which the receiver includes RFID functionality to identify which control is currently coupled to the receiver, such as a detachable D-pad. In this example, a four-way D-pad is shown as a coupling to the receiver. [Figure 7] 1A-1C show perspective and cross-sectional views of a detachable joystick and a detachable D-pad, as well as a cross-sectional view of a receiver of a handheld controller configured to accept each of the detachable controls. [Figure 8] FIG. 2 is a top view of the example handheld controller of FIG. 1. [Figure 9] FIG. 2 is a side view of the example handheld controller of FIG. 1. [Figure 10] FIG. 2 is a rear view of the example handheld controller of FIG. 1. In this example, the controller includes a back cover with two buttons, although this view also shows a back cover with four buttons that can optionally be interchanged with the two-button back cover. [Figure 11] 1 shows a perspective view of an exemplary two-button back cover, where the back cover includes a magnet that can be used by a handheld controller to identify the two-button back cover when the cover is coupled to the controller. [Figure 12]1 shows a perspective view of an exemplary four-button back cover, where the back cover includes an RFID chip that can be used by a handheld controller to identify the four-button back cover when the cover is mated to the controller. [Figure 13] FIG. 1 is a flow diagram of an exemplary process for enabling replacement of controls on a handheld controller using the techniques described herein. [Figure 14] 2 illustrates exemplary components of a handheld controller such as the controller of FIG. 1. DETAILED DESCRIPTION OF THE INVENTION

[0005] As described above, handheld controllers are used in a variety of environments and include a variety of functions. However, some conventional handheld controllers include a static configuration with respect to the controls that a user can manipulate. That is, many conventional handheld controllers typically include the same controls that are used across different applications, such as different game titles. Furthermore, these same controls are used by each user of the handheld controller, despite the fact that different users may have different configuration needs and / or preferences.

[0006] Described herein are, among other things, handheld controllers configured to removably couple to different controls, as well as methods for use and / or assembling handheld controllers. Accordingly, the handheld controllers described herein enable dynamic swapping of controls to change the configuration of the controller to meet the needs of different applications (e.g., game titles), users, and the like. For example, a first game application may best be played using a first control, such as a joystick coupled to the controller, while a second game application may best be played by a user of a second control, such as a directional pad (D-pad). Thus, a user may swap a first control for a second control, or vice versa, depending on the currently running game application. Additionally or alternatively, a first user may prefer a first control, such as a relatively long joystick with a convex-shaped cap, while a second user may prefer a second control, such as a shorter joystick with a concave-shaped cap. Again, the handheld controller may be dynamically configured depending on which user is currently operating the controller. Furthermore, in each of these cases, the handheld controller or the remote system may determine, in near real time, which controls are currently coupled to the controller and provide this information to the system running the current application, which may then make changes based on the configuration of the handheld controller. Thus, the techniques described herein enable dynamically configurable handheld controllers that ameliorate some of the current deficiencies of conventional handheld controllers, as discussed above.

[0007] In some cases, the handheld controllers described herein can be used to control remote devices (e.g., televisions, audio systems, personal computing devices, game consoles, etc.) and / or engage in video gameplay, etc. The handheld controller may include one or more controls, including one or more front side controls on the front of the handheld controller's housing. These front controls may include one or more joysticks, directional pads (D-pads), trackpads, trackballs, buttons, or other controls controllable by, for example, the thumbs of a user of the handheld controller. Additionally or alternatively, the handheld controller may include one or more top side controls on the top side of the handheld controller's housing. For example, these top side controls may be referred to as "triggers," "bumpers," etc., and may be controllable by one or more fingers of the user, such as the middle finger or index finger. In some cases, the handheld controller includes one or more top left side controls operable by one or more fingers of the user's left hand and one or more top right side controls operable by one or more fingers of the user's right hand. Additionally, the handheld controller may include one or more rear controls, such as one or more buttons on the back cover of the controller that are also used to provide access to the controller's battery. In some cases, the rear controls may include one or more controls operable by a user's left hand and one or more controls operable by a user's right hand.

[0008] In some cases, a handheld controller may include a housing having one or more receiver portions for removably coupling to one or more controls. For example, the housing may include a receiver on the front of the housing configured to removably couple to one or more joysticks, one or more D-pads, one or more trackpads, one or more buttons, and / or one or more accessibility controls, etc. In some cases, a user may swap a first control for a second control based on the current application (e.g., game title) the user is playing, based on the user's comfort, and / or for any other reason. Furthermore, while the above examples describe detachable front controls, in other examples, the controller may additionally or alternatively include one or more detachable top controls, rear controls, etc.

[0009] In some cases, the handheld controller or a system communicatively coupled to the controller may determine the current control(s) coupled to the controller, such as a joystick or D-pad. In one example, the handheld controller may include a Hall Effect sensor for use in identifying which control is currently coupled to the controller. In these cases, each control may include a different magnet configuration, and when each control couples to a receiver in the controller's housing, the Hall Effect sensor may change its voltage in response to the magnetic field caused by the magnet configuration of the respective control. The controller, or a system coupled to the controller, may then map this voltage to a known control, such as a joystick or D-pad. That is, because each magnet configuration of a control may be unique relative to other controls, the resulting magnetic field, and therefore the voltage generated by the Hall Effect sensor, may likewise be unique. The controller or a system communicating with the controller may store a table or other data structure that associates each voltage with specific identification data that identifies a particular control.

[0010] As used herein, a magnet configuration may include the strength of the magnet, the position or location of the magnet, the orientation of the magnet, the number of magnets used, and / or any combination thereof. For example, a first control may include a magnet of a first strength oriented in a first direction. A second control may also include a magnet having the first strength but oriented in a second direction (e.g., opposite the first direction). A third control may include a magnet of a second strength, a fourth control may include two magnets in a specific location, a fifth control may include a specific number of magnets of a specific strength and in a predetermined position and orientation, etc. In each of these examples, the generated magnetic field, and therefore the voltage generated by the Hall Effect sensor, may be unique to each other control, such that each control may be unambiguous with respect to the other controls. Furthermore, in some cases, one control may not include a magnet, such that the absence of a magnetic field detected by a Hall Effect sensor uniquely identifies that specific control.

[0011] After identifying the control currently coupled to the handheld controller's housing, the handheld controller and / or system may relay the control's identification to an application being executed by the system. The system may then take this information into account to determine one or more parameters of the application. For example, calibration factors and scaling factors associated with control movement translated into movement on the display may be updated to reflect the current control. In another example, an application (e.g., a game) may allow different movement / control selections based on which control is currently coupled to the receiver. In yet another example, the controller's configuration may be used to determine content to recommend or otherwise display to a user. For example, if the controller is currently coupled to a back cover having four buttons instead of two, a game application or platform may recommend games that are compatible with (e.g., include features utilized by) a four-button back cover. Of course, while several examples have been described, it should be understood that the system and / or controller may use this information in one or more other ways.

[0012] In some cases, for example, in response to determining that a first D-pad that can move in eight directions (e.g., up, down, left, right, up / left, down / left, up / right, down / left) is coupled to the handheld controller, the controller and / or remote system may digitize signals for these eight directions based on analog inputs provided via user manipulation. For example, when a user manipulates the controller with an eight-way D-pad coupled to it, analog signals corresponding to each of these directions may be compared to a threshold. If a particular analog signal is greater than the threshold, the signal may be digitized and an indication of the signal may be passed to the remote system. For example, suppose a user presses down on the left portion of the eight-way D-pad and the controller is configured to generate an analog signal between 0 volts and 1 volt for each direction. Further, suppose an exemplary threshold is set at 0.3 volts, and analog signals above that threshold are digitized to 1 volt, while the remaining signals are not digitized. In this case, it is possible that the analog signal corresponding to the left direction of the D-pad is greater than the 0.3 volt threshold (if the user is pressing in that direction), but the analog signals corresponding to the other seven directions may not be greater than the 0.3 volt threshold (if the user is not pressing in those directions). Thus, the signal corresponding to the left direction may be digitized to a value of 1 V, and other values may be assigned a value of 0 V. Additionally, when the controller determines that a second D-pad that can move in four directions (e.g., left, right, up, and down) is coupled to the controller, the controller and / or remote system may attempt to digitize analog signals corresponding to these four directions. Stated differently, the controller and / or remote system may apply a threshold to each signal associated with each direction such that each of four, eight, or other number of directions corresponds to either an "on" or "off" reading (commonly known as a "digital signal" or "digital input").Furthermore, although the above description discusses example voltages and example thresholds, it should be understood that the controllers described herein may be configured to output any other suitable range of voltage values and may utilize any other thresholds.

[0013] In yet another example, the analog signal may be amplified based on the controller coupling to a particular control, such as a joystick or D-pad. For example, the controller may be configured to identify when a joystick with a relatively limited range of motion is coupled to the controller and, in response, amplify the resulting analog signal by a particular multiplier. For example, the controller may apply a multiplier of 2 so that an analog signal corresponding to 0.4V is read by the gaming system as 0.8V. In yet another example, the signal may be amplified and then digitized.

[0014] Additionally, other techniques can be used to determine which controls are currently coupled to the handheld controller. For example, radio frequency identification (RFID) technology may be used to uniquely identify each control that removably couples to the controller. In these examples, the housing (e.g., in proximity to the receiver) may include an RFID reader configured to transmit RFID signals, while each control may include an RFID tag configured to receive the RFID signals and, in response, provide identification data that uniquely identifies the control relative to other controls configured to removably couple to the controller. In some cases, the RFID tag may comprise an active tag, a passive tag, or the like. Furthermore, while the above examples describe the handheld controller housing including an RFID reader, in some cases, each control may include a respective reader and the housing may include an RFID tag.

[0015] In yet other examples, the handheld controller may utilize optical sensors, capacitance sensors, built-in resistors, and / or any other type of hardware to identify which particular control is currently coupled to the controller's housing.

[0016] In yet another example, removable controls may be identified using one or more software-based detection methods. For example, given that each control may have a different physical form factor, each control may be operable by the user in a different manner. That is, a joystick coupled to a receiver on the housing may be movable in all directions (i.e., 360 degrees), but a first D-pad may only be movable in eight directions (e.g., up, down, left, right, up / left, down / left, up / right, down / right), while a second D-pad may only be movable in four directions (e.g., left, right, up, down), and a third D-pad may only be movable in two directions (e.g., left / right or up / down). An application running on the handheld controller, or a system communicatively coupled to the handheld controller, may receive movements made via the coupled controls over time to identify the specific control currently coupled to the controller. For example, if an application receives data over time of a user manipulating a control in only four directions (e.g., left, right, up, and down), the application may determine that the controller is currently coupled to the second D-pad described above. However, if the application receives data over time of a user manipulating a control in all directions, the application may determine that the controller is currently coupled to a joystick. Of course, while several examples have been described, it should be understood that these techniques can identify which control is currently coupled to a controller in multiple other ways.

[0017] While some conventional handheld controllers include a fixed number and type of controls, the controllers described herein allow for a variety of configurations that can be tailored to individual users and / or applications being run via the controller. This configurability enhances the use of these controllers and therefore improves the experience of users operating the controller.

[0018] FIG. 1 is a front view of an exemplary handheld controller 100 that may include a receiver configured to removably couple to different controls, such as a joystick and a directional pad (D-pad).

[0019] As shown, the handheld controller 100 includes a housing 102 potentially having a front surface 104(1) and a top surface 104(2), along with a back surface opposite the front surface 104(1) and a bottom surface opposite the top surface 104(2). The front surface 104(1) may include one or more front controls, in some cases controllable by one hand or thumb of a user operating the handheld controller 100. These front controls may include one or more trackpads, trackballs, joysticks, buttons, etc., as described in more detail below. In this example, the front surface 104(1) includes a left trackpad 106(1) controllable by the thumb of a user's left hand and a right trackpad 106(2) controllable by the user's right thumb. Additionally, the exemplary controller 100 includes a receiver 108 configured to removably couple to one or more controls 110, such as a joystick 110(1), a first D-pad 110(2), and a second D-pad 110(3). When coupled to the controller, each of these controls 110 may be controllable, for example, by the thumb of a user's left hand. Of course, while Figure 1 illustrates the handheld controller 100 as including a receiver 108 on the top surface 104(1) of the housing 102, in other examples, the controller 100 may additionally or alternatively include one or more receivers on other surface(s) of the housing 102.

[0020] For example, and as described below, the handheld controller 100 may include a receiver on the back of the housing configured to accept different removable back covers. These back covers can function as controls in addition to functioning as a cover over the battery cavity of the controller 100. For example, a first removable back cover may include two buttons (e.g., one on the left side of the back cover and one on the right side of the back cover), while a second removable back cover may include four buttons (e.g., two on each of the right and left sides). Again, the handheld controller 100 may be configured to identify the back cover to which the controller 100 is currently coupled using the identification techniques described herein. Additionally, while several exemplary cover and receiver locations are described, it should be understood that the handheld controller 100 may include receivers in a variety of locations configured to removably couple to an array of different types of covers.

[0021] The controller may further include a depressible button 112 (e.g., controllable by the thumb of a user's right hand) and additional input controls. In this example, the handheld controller 100 also includes a left handle 114(1) and a right handle 114(2) that allow a user to hold the controller 100 via the user's right and left hands, respectively.

[0022] Meanwhile, top surface 104(2) may include one or more top surface controls. In the illustrated example, controller 100 includes a left top surface control 116(1) and a right top surface control 116(2). The left top surface control 116(1) may be operable by a user's left finger (e.g., middle finger or index finger), while the right top surface control may be operable by a user's right finger (e.g., middle finger or index finger). Top surface controls 116(1) and 116(2) may, in some cases, be referred to as "triggers" or "bumpers." Additionally, in some cases, one or more of top surface controls 116(1) and 116(2) may include one or more touch sensors for detecting the presence, position, and / or gesture of one or more of a user's fingers on the respective top surface control.

[0023] In some cases, a user of the handheld controller 100 can swap which controls 110 are coupled to the receiver 108 to change the functionality, appearance, or feel of the controller 100. For example, a user may select to couple a joystick 110(1) to the receiver 108 when operating a first application, a first D-pad 110(2) when operating a second application, a second D-pad 110(3) when operating a third application, and so on. In some cases, each of these controls may provide a different function (e.g., movement in different directions). In yet other examples, a user may select a control based on the appearance or feel of the control. For example, different controls may include different sizes, textures, shapes, heights, etc. In one example, different joysticks may have different heights and different shapes (e.g., convex, concave, flat, etc.).

[0024] In each case, the handheld controller can generate data used to identify which of the controls 110 are currently coupled to the receiver. In some cases, the handheld controller 100 may use this data to make this determination; in other examples, the handheld controller 100 may provide this data to a remote system (e.g., a game console in the controller's local environment, a remote server running an application controlled by the controller 100, etc.). In each of these cases, the controller 100 may generate this data in a variety of ways. For example, the handheld controller 100 may include analog Hall effect sensors, digital switch Hall effect sensors, optical sensors, RFID functionality, or other functionality for generating data used to determine which controls are currently coupled to the receiver 108. In some cases, the handheld controller may track control usage data over time that indicates how the controls are manipulated by the user to determine which controls are currently coupled to the receiver 108. For example, software running on the control, the game console, and / or a remote server, etc., can use this control usage data to identify a specific usage signature associated with a particular control. For example, if the control usage data indicates that the control is being manipulated in a 360° manner, the software (or firmware) can identify a usage signature associated with a joystick and therefore determine that the joystick is coupled to receiver 108. Conversely, if the control usage data indicates that the control is being used in only four directions (e.g., up, down, left, and right), the software can identify a usage signature associated with a four-way D-pad and therefore determine that a four-way D-pad is currently coupled to receiver 108. The following figures and accompanying descriptions discuss these concepts in more detail below.

[0025] FIG. 2 illustrates cross-sectional and perspective views of an exemplary assembly 200 including a detachable joystick 202 coupled to a receiver 204 of a handheld controller, such as the handheld controller 100 of FIG. 1. As shown, in this example, the receiver portion is coupled to or otherwise adjacent to a Hall Effect sensor 206 configured to generate data for use in determining which detachable control is currently coupled to the receiver 204, as described below. While FIG. 2 illustrates a single Hall Effect sensor, in other examples, the controller may include multiple such sensors. In these cases, each Hall Effect sensor may generate a different voltage reading, and a combination of these readings may be used to uniquely identify a particular control coupled to the controller. In these cases, a control, such as the exemplary joystick 202, may include multiple Hall Effect sensor magnets, a single Hall Effect sensor magnet, or, as described above, may not include a Hall Effect sensor magnet.

[0026] FIG. 2 further shows that receiver 204 also includes magnet 208(1) and joystick 202 includes magnet 208(2). In some cases, magnets 208(1) and 208(2) are oriented to attract each other to removably couple joystick 202 to receiver 204. For example, the south pole of magnet 208(1) may be oriented with the north pole of magnet 208(2) pointing downward (or vice versa) so that the receiver and joystick are magnetically coupled, thus allowing a user of the controller to operate the controller using the joystick. In other examples, however, one of magnets 208(1) or 208(2) may comprise a magnetic metal rather than a magnet, providing a similar attractive force for coupling joystick 202 (or other control) to receiver 204. For example, controller 100 may include magnet 208(1) in the location of magnet 208(2) shown, coupled to a magnetic material present in place of magnet 208(2). In another example, joystick 202 may include magnet 208(2) in the location of magnet 208(1) shown, coupled to magnetic material present in place of magnet 208(1). Additionally, although this example describes removably coupling joystick 202 or other control to receiver 204 via magnetic attraction, in other examples, these components may additionally or alternatively couple via a force-fit connection or any other type of connection.

[0027] Alternatively, the Hall Effect sensor 206 may comprise a transducer that changes its output voltage in response to a magnetic field. To accomplish this, the Hall Effect sensor 206 may include a thin strip of metal through which a current is applied, so that when a magnetic field is applied to the thin strip of metal, the electrons in the thin strip are deflected toward one edge. This deflection creates a voltage gradient across the strip that is perpendicular to the flow of the applied current.

[0028] Thus, different controllers of controller 110 may include different magnetic configurations that generate different magnetic fields, and thus create different voltage gradients in Hall Effect sensor 206. These different gradients, or voltage measurements, may then be used to determine which controller is coupled to receiver 204. That is, the handheld controller or a system remote from the controller (e.g., a game console, server, etc.) may store an association between each voltage measurement and each controller identifier (ID). For example, a first voltage measurement may be associated with a first controller, a second measurement may be associated with a second controller, and so on.

[0029] In this example, the joystick 202 includes a Hall Effect sensor magnet 210. Thus, when the joystick 202 couples to a controller, the Hall Effect sensor 206 may measure a particular voltage measurement, and the controller or another device may be used to determine the identity of the currently coupled joystick 202. That is, the controller or another device (e.g., a game console, a server, etc.) may determine a device ID associated with the particular voltage measurement determined by the Hall Effect sensor 206.

[0030] Additionally, and as noted above, in some cases, the absence of a voltage gradient may be associated with a particular control. For example, a joystick may not include a Hall Effect sensor magnet in proximity to the sensor 206. Thus, the sensor may refrain from generating a gradient that may be used as a signal in this example to indicate that the receiver 204 is currently coupled to a particular joystick.

[0031] FIG. 3 shows perspective and cross-sectional views of two different detachable joysticks, as well as a cross-sectional view of a handheld controller receiver that can be configured to accept each of the different joysticks. The right joystick can include joystick 202 shown with reference to FIG. 2. That is, this joystick 202 can include a relatively flat top compared to joystick 302, which has a convex top surface. As shown, each of joysticks 202 and 302 can include magnets 208(2) and 208(3), respectively, for magnetically coupling the respective joystick to receiver 204 via magnet 208(1). In some cases, magnets 208(2) and 208(3) can have the same or substantially similar magnetic fields oriented in the same direction. Additionally, in this example, joystick 202 includes a Hall Effect sensor magnet 210 for use in identifying joystick 202. Meanwhile, joystick 302 may include a Hall Effect sensor magnet 212, such that Hall Effect sensor 206 generates a unique voltage gradient when joystick 302 couples to receiver 204. While in this example, the joysticks may include different Hall Effect sensor magnets, in other examples, joysticks 202 and 302 may be treated identically for purposes of operation of the handheld controller and / or any application in which the system(s) to which the controller couples are controlled by the controller. Thus, a user may select a preferred joystick (e.g., convex, concave, flat, etc.) without changing the functionality of the controls compared to the other joystick. In some cases, the two joysticks may include the same magnet oriented in opposite directions. For example, joystick 202 may include magnet 210 oriented so that the south pole faces the controller when the joystick couples to the controller, while joystick 302 may include the same magnet 210 but oriented in the opposite direction. Thus, the Hall Effect sensors 206 can distinguish joysticks from one another based on the different voltage readings caused by different magnetic orientations.

[0032] 4 shows a perspective view, a cross-sectional side view, and a cross-sectional top view of two different detachable D-pads, as well as a cross-sectional view of a receiver of a handheld controller that may be configured to accept each of the different D-pads. As shown, FIG. 4 shows D-pad 402, which may be configured to move in four directions (e.g., four azimuths) when coupled to receiver 204, and D-pad 404, which may be configured to move in eight directions (e.g., four azimuths and four azimuths) when coupled to receiver 204. Of course, while two exemplary D-pads are described, it should be understood that other D-pads having any other range of motion may also be used.

[0033] To distinguish these two controls from one another and from other controls configured to removably couple to the receiver, the D-pads may include different Hall-effect sensor magnets. As shown, D-pad 402 includes a Hall-effect sensor magnet 406(1) located near the edge of the D-pad, while D-pad 404 includes a Hall-effect sensor magnet 406(2) also located near the edge of the D-pad. In some cases, these magnets may be located on the side of the control closest to the Hall-effect sensor 206 (e.g., molded into it) to enable the Hall-effect sensor 206 to generate voltage data used to identify the control currently coupled to the handheld controller.

[0034] Additionally, in some cases, the magnetic configuration of Hall-effect sensor magnet 406(1) may be different from the magnetic configuration of Hall-effect sensor magnet 406(2). For example, the poles may be oriented in opposite directions, the magnetic strengths may be different, and the locations on the respective controls may be different and / or similar. Furthermore, in some cases, the controls may use different numbers of Hall-effect sensor magnets relative to each other. In any case, these magnets may be used to identify whether D-pad 402, D-pad 404, or another control is currently coupled to the controller. Furthermore, D-pads 402 and 404 may each include removable magnets 208(4) and 208(5) (which may be the same or different) for securing the respective control to receiver 204 via magnet 208(1).

[0035] FIG. 5 illustrates an example assembly 500 including an example control, in this case a joystick 502, coupled to a receiver 504. Additionally, the controller 100 to which the receiver 504 is coupled may include RFID functionality for identifying which control, such as a detachable joystick 502, is currently coupled to the receiver 504. To identify a control via RFID, in some cases, the controller's housing, e.g., a portion of the housing adjacent the receiver 504, may include an RFID reader otherwise configured to transmit an interrogation signal to an RFID tag and, in response, receive identification data in the form of a modulated signal. Thus, each control (or class of controls) configured to removably couple to a receiver may include a unique RFID tag configured to receive an interrogation signal from the RFID reader and transmit its identification information back. Additionally, while the above example describes an RFID reader transmitting an interrogation signal to a passive tag, it should be understood that any other form of RFID (e.g., a passive reader, an active tag, etc.) may be utilized.

[0036] As shown, the exemplary joystick 502 includes an RFID tag 506 (e.g., including an RF coil and an IC) configured to receive an interrogation signal from an RFID reader 508 (e.g., an RF coil, an antenna, and an integrated circuit (IC)) and, in response, transmit a signal encoding its identification data. This identification data received by the RFID reader 508 may then be used by a handheld controller or another system to identify which control is currently coupled to the controller. In some cases, the RFID reader 508 forms part of, or is otherwise adjacent to, the receiver 504. Here, the RFID reader 508 includes a coil housed in an RFID bobbin 510. Further, in some cases, the RFID tag 506 may form part of an integrated component that includes a magnet for coupling the control to the receiver. That is, the RFID tag 506 may form part of a component configured to perform the RFID tag functionality and the functionality of the magnet 208(2) described above. Alternatively, in other implementations, RFID tag 506 may be present at or near the location of magnet 208(2) shown without functioning as magnet 208(2).

[0037] FIG. 6 illustrates an example assembly 600 including an example control, in this case, a D-pad 602, coupled to a receiver 504 that includes RFID functionality for identifying which control, such as a detachable D-pad 602, is currently coupled to the receiver 504. Again, to identify the control via RFID, the D-pad 602 includes an RFID tag 606, while the receiver 504 or another portion of the housing includes an RFID reader 508 configured to transmit an interrogator signal to the tag 606. In response, the RFID tag may transmit its identification data in the form of a modulated signal back to the reader 508. This identification data received by the RFID reader 508 may then be used by the handheld controller or another system to identify which control is currently coupled to the controller. Again, the RFID reader 508 may form part of or otherwise be adjacent to the receiver 504. Here, the RFID reader 508 includes a coil housed in an RFID bobbin 510. Additionally, in some cases, RFID tag 606 may form part of an integrated component that includes a magnet for coupling a control unit to a receiver, i.e., and as noted above, RFID tag 606 may form part of a component configured to perform the RFID tag functions described above and the functions of magnet 208(4).

[0038] 7 shows perspective and cross-sectional views of an exemplary detachable joystick 502 and an exemplary detachable D-pad 602, as well as a cross-sectional view of a handheld controller receiver 504 configured to accept each of the detachable controls. This diagram helps explain that a user can exchange the joystick 502 for the D-pad 602 and / or any other control with an associated RFID tag, and in response, the RFID reader 508 can receive RFID identification data from the tag to identify the associated control. For example, when the joystick 502 is coupled to the receiver 504, the RFID tag 506 of the joystick 502 may receive an interrogation signal from the RFID reader 508 and, in response, modulate a signal that encodes its identification data. Similarly, when the D-pad 602 is coupled to the receiver 504, the RFID tag 606 of the D-pad 602 may receive an interrogation signal from the RFID reader 508 and, in response, modulate a signal that encodes its identification data.

[0039] 8 is a top view of an exemplary handheld controller 100 configured to implement the techniques described herein. As shown, top surface 104(2) may include an additional top-left surface control 802(1) operable by a user's left fingers and an additional top-right surface control 802(2) operable by a user's right fingers. In some cases, both the additional top-left surface control 802(1) and the additional top-right surface control 802(2) may include touch sensors for detecting the presence, position, and / or gesture of a finger on the control, in addition to or instead of touch sensors present on top surface controls 116(1) and / or 116(2).

[0040] 9 is a side view of exemplary handheld controller 100. As shown, the side view shows right-side handle 114(2) and right-side top controls 116(2) and 802(2). One or more of controls 116(2) and 802(2) may be touch-sensitive to identify the presence, position, and / or gesture of one or more fingers on the control.

[0041] FIG. 10 is a rear view of the exemplary handheld controller 100 of FIG. 1. In this example, the controller includes a rear surface 104(3) that includes a receiver portion for accepting different types of back covers. For example, this rear receiver can accept a back cover 1002 having two buttons, a back cover 1004 having four buttons, and so on. In each case, a back cover, such as the two-button back cover 1002, can be interchanged with another back cover, such as the back cover 1004. Of course, while FIG. 10 shows two examples of back covers, in other examples, interchangeable back covers may include any other number of selectable buttons. Furthermore, similar to the techniques described above with reference to the illustrated control unit 110, the handheld controller 100 may be configured to obtain data indicating which back cover is currently coupled to the controller. The handheld controller or another system can then use this data to make this determination, which may be used by an application operated via the controller 100.

[0042] In some cases, the controller 100 may determine which back cover is coupled to the controller 100 using techniques similar or the same as those described above with reference to the illustrated controller 100. For example, the rear surface 104(3) of the housing of the controller 100 may include or be adjacent to a Hall Effect sensor, an RFID reader, an optical sensor, or the like. Each of these components may be configured to generate data for use in identifying which back cover is currently coupled to the controller 100. To accomplish this, each back cover may include a specific magnetic configuration, a unique RFID tag, and / or other information used to identify the particular cover.

[0043] For example, FIG. 11 shows a perspective view of an exemplary two-button back cover 1002. In this case, the back cover 1002 includes a Hall Effect sensor magnet 1102 that can be used by the handheld controller to identify the two-button cover 1002 when the cover is coupled to the controller 100. That is, a Hall Effect sensor, similar to the Hall Effect sensor 206 but located near the back surface 104(3) of the controller, may generate a voltage gradient based on the magnetic configuration of the magnet 1102. This voltage gradient may be used to uniquely identify the back cover 1002. The back cover 1004 may similarly include a unique Hall Effect sensor magnet (or magnetic configuration) for use in identifying the back cover 1004, etc.

[0044] 12, on the other hand, shows a perspective view of an exemplary four-button back cover 1004. In this case, the back cover 1004 includes an RFID tag 1202 that can be used by the handheld controller to identify the four-button cover 1004 when the cover is coupled to the controller 100. That is, an RFID reader similar to the reader described above, but positioned near the back surface 104(3) of the controller, can transmit an interrogation signal that is received and modulated back by the RFID tag 1202. This modulated signal may be used to uniquely identify the back cover 1004. The back cover 1002 may similarly include a unique RFID tag for use in identifying the back cover 1002, etc.

[0045] 13 is a flow diagram of an example process 1300. The process 1300 described herein is illustrated as a collection of blocks in a logic flow graph, which represent a sequence of operations that may be implemented in hardware, software, or a combination thereof. In the software context, the blocks represent computer-executable instructions that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order and / or in parallel to implement a process.

[0046] Operation 1302 represents determining that a first control is coupled to a receiver on the housing of the handheld controller. This operation may be implemented in a variety of ways. For example, a component of the handheld controller may generate data that uniquely identifies the first control and use that data to determine an association between the data and the unique control ID, or may transmit this data to another system to make this determination. This data may include voltage data measured by a Hall Effect sensor, RFID data received by an RFID reader, optical data, resistive data, control usage data indicating how the control is being used, and / or any other type of data that may be used to uniquely identify the currently bound control.

[0047] Meanwhile, operation 1304 represents notifying a software application that the controller may currently be running that the handheld controller is currently coupled to the first control. For example, the controller may provide this notification, or another system, such as a game console or a remote server, may provide this notification. Meanwhile, the software application may use this information in various ways. For example, the software application may utilize certain scaling parameters based on this information to ensure that movements within a particular game are performed correctly. In another example, the software application may recommend content, etc. to a user based on the current configuration of the controller. For example, the software application may determine which applications (e.g., games) are compatible with or recommended for the current configuration of the controller and recommend these applications to the user of the controller. Of course, while several examples have been described, it should be understood that the software application may use this information in any other manner.

[0048] Operation 1306 represents determining that a second control is coupled to a receiver on the housing of the handheld controller. Again, this operation may be implemented in a variety of ways. For example, a component of the handheld controller may generate data that uniquely identifies the second control and use that data to determine the association between the data and the unique control ID, or may transmit this data to another system to make this determination. This data may include voltage data measured by a Hall effect sensor, RFID data received by an RFID reader, optical data, resistive data, control usage data indicating how the control is being used, and / or any other type of data that may be used to uniquely identify the currently bound control.

[0049] Finally, operation 1308 represents notifying a software application that the handheld controller is now coupled to a second control. For example, the controller may provide this notification, or another system, such as a game console or a remote server, may provide this notification. Again, the software application can use this information in a variety of ways. For example, the software application can update certain scaling parameters based on this information so that movements within a particular game continue to function correctly. In another example, the software application can recommend content, etc. to a user based on the new configuration of the controller. For example, the software application can determine which applications (e.g., games) are compatible with or recommended for the current configuration of the controller and recommend these applications to the user of the controller. Again, while several examples have been described, it should be understood that the software application can use this information in any other manner.

[0050] FIG. 14 illustrates exemplary components of a handheld controller, such as controller 100. As shown, the handheld controller includes one or more input / output (I / O) devices 1402, such as the controls described above (e.g., joystick, trackpad, trigger, detachable controls, fixed controls, etc.), and potentially any other type of input or output device. For example, I / O device 1402 may include one or more microphones for receiving audio input, such as user voice input. In some implementations, one or more cameras or other types of sensors (e.g., inertial measurement units (IMUs)) can function as input devices for receiving gestural input, such as movement of handheld controller 100. In some embodiments, additional input devices may be provided in the form of a keyboard, keypad, mouse, touchscreen, joystick, control buttons, etc. The input devices may further include controls such as basic volume control buttons for increasing and decreasing the volume, as well as power and reset buttons.

[0051] On the other hand, output devices may include displays, light elements (e.g., LEDs), vibrators for creating tactile sensations, speakers (e.g., headphones), etc. For example, there may also be simple light elements (e.g., LEDs) to indicate a state such as when the power is on. Although some examples are provided, the handheld controller may additionally or alternatively include any other type of output device.

[0052] In some cases, output by one or more output devices can be based on input received by one or more of the input devices. For example, selection of a top surface control can result in output of a haptic response by a vibrator positioned adjacent to (e.g., below) the top surface control or any other location. In some cases, the output may vary based at least in part on characteristics of a touch input of a touch sensor, such as a touch sensor associated with the top surface control. For example, touch input at a first location on the touch sensor may result in a first haptic output, while touch input at a second location on the touch sensor may result in a second haptic output. Furthermore, particular gestures on the touch sensor may result in particular haptic outputs (or other types of outputs). For example, a swipe gesture on the top surface control may result in a first type of haptic output, a tap on the top surface control (detected by the touch sensor) may result in a second type of haptic output, and a firm press on the top surface control may result in a third type of haptic output.

[0053] Additionally, handheld controller 100 may include one or more communication interfaces 1404 to facilitate wireless connection to a network and / or one or more remote systems (e.g., a host computing device executing an application, a game console, etc.). Communication interface 1404 may implement one or more of a variety of wireless technologies, such as Wi-Fi, Bluetooth, radio frequency (RF), etc. It should be understood that handheld controller 100 may further include physical ports to facilitate wired connection to a network, connected peripherals, or plug-in network devices that communicate with other wireless networks.

[0054] In the illustrated embodiment, the handheld controller further includes one or more processors 1406 and computer-readable media 1408. In some implementations, the processor(s) 1406 may include a central processing unit (CPU), a graphics processing unit (GPU), both a CPU and a GPU, a microprocessor, a digital signal processor, or other processing units or components known in the art. Alternatively or additionally, functions described functionally herein may be implemented, at least in part, by one or more hardware logic components and / or other circuits. For example, without limitation, exemplary types of hardware logic components and / or other circuits that may be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems-on-chips (SOCs), complex programmable logic devices (CPLDs), etc. Additionally, each of the processor(s) 1406 may have its own local memory that may also store program modules, program data, and / or one or more operating systems.

[0055] The computer-readable medium 1408 can include volatile and nonvolatile memory, removable and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data. Such memory includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVDs) or other optical memory, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other medium that can be used to store the desired information and that can be accessed by a computing device. The computer-readable medium 1408 can be implemented as a computer-readable storage medium (“CRSM”), which can be any available physical medium that can be accessed by the processor(s) 1406 to execute instructions stored on the computer-readable medium 1408. In one basic implementation, the CRSM can include random access memory (“RAM”) and flash memory. In other implementations, the CRSM may include read-only memory (“ROM”), electrically erasable programmable read-only memory (“EEPROM”), or any other tangible medium that can be used to store desired information and that can be accessed by the processor(s) 1406.

[0056] Some modules, such as instructions, data stores, etc., may be stored in computer-readable medium 1408 and configured to execute on processor(s) 1406. While some example functional modules are shown as being stored in computer-readable medium 1408 and executing on processor(s) 1406, the same functionality may alternatively be implemented as hardware, firmware, or a system-on-chip (SOC).

[0057] The operating system module 1410 may be configured to manage hardware within and coupled to the handheld controller 100 for the benefit of other modules. Additionally, the computer-readable medium 1408 may store a network communication module 1412 that enables the handheld controller 100 to communicate with one or more other devices, such as a personal computing device, game console, or remote server running an application (e.g., a game application), via the communication interface 1404. The computer-readable medium 1408 may further include a game session database 1414 for storing data associated with a game (or other application) running on the handheld controller or a computing device to which the handheld controller 100 is coupled. The computer-readable medium 1408 may also include a device record database 1416 that stores data associated with a device to which the handheld controller 100 is coupled, such as a personal computing device, game console, or remote server. The computer-readable medium 1408 may further store game control instructions 1418 that configure the handheld controller 100 to function as a game controller, and universal control instructions 1420 that configure the handheld controller 100 to function as a controller for other non-gaming devices.

[0058] Although the present subject matter has been described in language specific to structural features, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the particular features described. Rather, the particular features are disclosed as example forms of implementing the claims. The inventions described in the original claims of this application are set forth below. [1] A handheld controller, a housing having a receiver for removably coupling to at least a first control and a second control; a Hall effect sensor adjacent to the receiver; one or more processors; One or more computer-readable media storing computer-executable instructions that, when executed, cause the one or more processors to: receiving a first voltage measured by the Hall effect sensor; determining from the first voltage that the receiver is coupled to the first controller; receiving a second voltage measured by the Hall effect sensor; and and one or more computer-readable media configured to perform operations including determining from the second voltage that the receiver is coupled to the second control unit. [2] The handheld controller of [1], wherein the first control unit comprises a joystick and the second control unit comprises a directional pad. [3] the receiver is located on a rear surface of the housing; the first control comprises a first back cover having a first set of one or more selectable buttons; The handheld controller of [1], wherein the second control section includes a second back cover having a second set of one or more selectable buttons. [4] The handheld controller of [1], wherein the first control unit includes a first directional pad associated with directional control in a first number of directions, and the second control unit includes a second directional pad associated with directional control in a second number of directions different from the first number of directions. [5] and one or more communication interfaces, and wherein said operation comprises: transmitting, to a software application executing on a remote system, a signal indicating that the handheld controller is coupled to the first control unit, at least in part in response to determining that the receiver is coupled to the first control unit; [1] The handheld controller of [1], further comprising: transmitting a signal indicating that the handheld controller is coupled to the second control unit to the software application and at least in part in response to determining that the receiver is coupled to the second control unit. [6] the first control unit includes a first magnet; the second control portion includes a second magnet; the first voltage measured by the Hall effect sensor is based at least in part on a magnetic field generated by the first magnet; 10. The handheld controller of claim 1, wherein the second voltage measured by the Hall effect sensor is based at least in part on a magnetic field generated between the Hall effect sensor and the second magnet. [7] A handheld controller, a housing including a receiver for removably coupling to at least a first control and a second control; one or more processors; One or more computer-readable media storing computer-executable instructions that, when executed, cause the one or more processors to: receiving first data; determining, based at least in part on the first data, that the first controller is coupled to the receiver; receiving second data; and and one or more computer-readable media configured to perform operations including determining, based at least in part on the second data, that the second control unit is coupled to the receiver. [8] The one or more computer-readable media further store computer-executable instructions that, when executed, cause the one or more processors to: transmitting a signal indicating that the first control unit is coupled to the receiver to a remote system operating a software application controlled by the handheld controller and based at least in part on determining that the first control unit is coupled to the receiver; [7] The handheld controller of [7], which causes the remote system to perform operations including transmitting a signal indicating that the second control unit is coupled to the receiver based at least in part on determining that the second control unit is coupled to the receiver. [9] the first control unit including a first magnet; the second control unit including a second magnet; The handheld controller of [7], wherein the first data is based at least in part on a first magnetic field generated at least in part by the first magnet, and the second data is based at least in part on a second magnetic field generated at least in part by the second magnet.

[10] a radio frequency identification (RFID) reader coupled to the housing; the first control unit including a first RFID tag; the second control unit including a second RFID tag; and the first data is based at least in part on a first radio signal including first identification information transmitted by the first RFID tag; [7] The handheld controller of [7], wherein the second data is based at least in part on a second radio signal including second identification information transmitted by the second RFID tag.

[11] [7] The handheld controller of [7], further comprising a Hall effect sensor, wherein the first data includes a first voltage measured by the Hall effect sensor, and the second data includes a second voltage measured by the Hall effect sensor.

[12] the first data includes first control unit usage data; the second data includes second control unit usage data; determining that the first control unit is coupled to the receiver includes identifying a first usage signature associated with the first control unit based at least in part on the first control unit usage data; [7] A handheld controller as described in [7], wherein determining that the second control unit is coupled to the receiver includes identifying a second usage signature associated with the second control unit based at least in part on the second control unit usage data.

[13] [7] The handheld controller of [7], wherein the first control unit comprises a joystick and the second control unit comprises a directional pad.

[14] The handheld controller of [7], wherein the first control unit comprises a first joystick and the second control unit comprises a second joystick.

[15] The handheld controller of [7], wherein the first control unit includes a first directional pad associated with directional control in a first number of directions, and the second control unit includes a second directional pad associated with directional control in a second number of directions different from the first number of directions.

[16] [7] A handheld controller as described in [7], wherein the first control unit includes a first back cover having a first number of selectable buttons, and the second control unit includes a second back cover having a second number of selectable buttons.

[17] 1. A method comprising: determining that a first control is coupled to a receiver on a housing of a handheld controller, the handheld controller operating a software application executing on a system communicatively coupled to the handheld controller; notifying the software application that the first controller is coupled to the receiver based at least in part on determining that the first controller is coupled to the receiver; and determining that a second controller is coupled to the receiver; and notifying the software application that the second control unit is coupled to the receiver based at least in part on determining that the second control unit is coupled to the receiver.

[18] determining that the first control unit is coupled to the receiver includes determining, at the handheld controller, that the first control unit is coupled to the receiver; determining that the second control unit is coupled to the receiver includes determining, at the handheld controller, that the second control unit is coupled to the receiver; wherein notifying the software application that the first control unit is coupled to the receiver includes transmitting, by the handheld controller and to at least one of a game console or a server executing the software application, an indication that the first control unit is coupled to the receiver;

[17] The method of claim 17, wherein notifying the software application that the second control unit is coupled to the receiver includes sending, by the handheld controller and to at least one of the game console or the server running the software application, an indication that the second control unit is coupled to the receiver.

[19] determining that the first controller is coupled to the receiver; receiving, in the system, first data from the handheld controller; determining, by the system and based at least in part on the first data, that the first controller is coupled to the receiver; determining that the second controller is coupled to the receiver; receiving second data from the handheld controller in the system; and determining, by the system and based at least in part on the second data, that the second control unit is coupled to the receiver.

[20] determining that the first controller is coupled to the receiver includes determining that the first controller is coupled to the receiver based at least in part on a first voltage measured at the handheld controller;

[17] The method of

[17] , wherein determining that the second control unit is coupled to the receiver includes determining that the second control unit is coupled to the receiver based at least in part on a second voltage measured at the handheld controller.

[21] determining that the first control unit is coupled to the receiver includes determining that the first control unit is coupled to the receiver based at least in part on a first magnetic field measured at the handheld controller;

[17] The method of

[17] , wherein determining that the second control unit is coupled to the receiver includes determining that the second control unit is coupled to the receiver based at least in part on a second magnetic field measured at the handheld controller.

[22] determining that the first control unit is coupled to the receiver includes determining that the first control unit is coupled to the receiver based at least in part on at least one of a transmitted first radio frequency identification (RFID) signal or a received first radio frequency identification (RFID) signal at the handheld controller;

[17] The method of

[17] , wherein determining that the second control unit is coupled to the receiver includes determining that the second control unit is coupled to the receiver based at least in part on at least one of a transmitted second RFID signal or a received second RFID signal at the handheld controller.

[23] determining that a third controller is coupled to the receiver;

[17] The method of

[17] , further comprising: notifying the software application that the third control unit is coupled to the receiver based at least in part on determining that the third control unit is coupled to the receiver.

Claims

1. 1. A handheld controller system, comprising: a housing including a receiver, the receiver having a receptacle configured to receive and interchangeably couple with at least a first control of the handheld controller system and a second control of the handheld controller system; one or more processors; One or more computer-readable media storing computer-executable instructions that, when executed, cause the one or more processors to: receiving first control usage data indicating a first movement of the first control manipulated over a first time period; identifying a first usage signature for the first control unit based at least in part on the first control unit usage data; determining, based at least in part on the first usage signature, that the first controller is coupled to the receiver; receiving second control usage data indicating a second movement of the second control manipulated over a second time period; identifying a second usage signature for the second control unit based at least in part on the second control unit usage data; and and one or more computer-readable media configured to perform operations including determining that the second control unit is coupled to the receiver based at least in part on the second usage signature.

2. The housing is a housing for a handheld controller, and the operation is transmitting, based at least in part on the handheld controller and determining that the first control unit is coupled to the receiver, a signal to a remote system running a software application being controlled, indicating that the first control unit is coupled to the receiver; 10. The handheld controller system of claim 1, further comprising: transmitting a signal to the remote system indicating that the second control is coupled to the receiver based at least in part on determining that the second control is coupled to the receiver.

3. the first control unit including a first magnet; the second control unit including a second magnet; The operation is receiving first voltage data based at least in part on a first magnetic field generated at least in part by the first magnet, wherein determining that the first controller is coupled to the receiver is further based on the first voltage data; 10. The handheld controller system of claim 1, further comprising: receiving second voltage data based at least in part on a second magnetic field generated at least in part by the second magnet, and determining that the second control unit is coupled to the receiver is further based on the second voltage data.

4. a radio frequency identification (RFID) reader coupled to the housing; the first control unit including a first RFID tag; the second control unit including a second RFID tag; and The operation is receiving first identification data based at least in part on a first wireless signal including first identification information transmitted by the first RFID tag, wherein determining that the first controller is coupled to the receiver is further based on the first identification data; 10. The handheld controller system of claim 1, further comprising: receiving second identification data based at least in part on a second radio signal including second identification information transmitted by the second RFID tag, wherein determining that the second control unit is coupled to the receiver is further based on the second identification data.

5. further comprising a Hall effect sensor; The operation is measuring a first voltage by the Hall effect sensor, wherein determining that the first controller is coupled to the receiver is further based on the first voltage; 10. The handheld controller system of claim 1, further comprising: measuring a second voltage by the Hall effect sensor, wherein determining that the second control unit is coupled to the receiver is further based on the second voltage.

6. The handheld controller system of claim 1 , wherein the first control comprises a joystick and the second control comprises a directional pad.

7. The handheld controller system of claim 1 , wherein the first control comprises a first joystick and the second control comprises a second joystick.

8. 2. The handheld controller system of claim 1, wherein the first control comprises a first directional pad associated with directional control in a first number of directions, and the second control comprises a second directional pad associated with directional control in a second number of directions different from the first number of directions.

9. 10. The handheld controller system of claim 1, wherein the first control comprises a first back cover having a first number of selectable buttons, and the second control comprises a second back cover having a second number of selectable buttons.

10. Receiving first control unit usage data indicating a first operation of a first control unit at an operated first control unit over a first time period; identifying a first usage signature associated with the first control unit based at least in part on the first control unit usage data; determining, based at least in part on the first usage signature, that the first control unit is coupled to a receiver in a housing of a handheld controller, the handheld controller operating a software application executing on a system communicatively coupled to the handheld controller; notifying the software application that the first controller is coupled to the receiver based at least in part on determining that the first controller is coupled to the receiver; and receiving second control usage data indicative of a first operation of the second control for the operated second control over a second time period; identifying a second usage signature associated with the second control unit based at least in part on the second control unit usage data; determining, based at least in part on the second usage signature, that the second controller is coupled to the receiver; and and notifying the software application that the second control unit is coupled to the receiver based at least in part on determining that the second control unit is coupled to the receiver.

11. determining that the first control unit is coupled to the receiver includes determining, at the handheld controller, that the first control unit is coupled to the receiver; determining that the second control unit is coupled to the receiver includes determining, at the handheld controller, that the second control unit is coupled to the receiver; wherein notifying the software application that the first control is coupled to the receiver includes transmitting, by the handheld controller and to at least one of a game console or a server executing the software application, a first indication that the first control is coupled to the receiver; 11. The method of claim 10, wherein notifying the software application that the second control is coupled to the receiver includes transmitting, by the handheld controller and to the at least one of the game console or the server running the software application, a second indication that the second control is coupled to the receiver.

12. determining that the first control unit is coupled to the receiver is based at least in part further on a first voltage measured at the handheld controller; The method of claim 10 , wherein the determining that the second control unit is coupled to the receiver is further based at least in part on a second voltage measured at the handheld controller.

13. determining that the first control unit is coupled to the receiver is based at least in part further on a first magnetic field measured at the handheld controller; The method of claim 10 , wherein the determining that the second control is coupled to the receiver is further based at least in part on a second magnetic field measured at the handheld controller.

14. determining that the first control unit is coupled to the receiver is further based at least in part on at least one of a transmitted first radio frequency identification (RFID) signal or a received first radio frequency identification (RFID) signal at the handheld controller; 11. The method of claim 10, wherein the determining that the second control unit is coupled to the receiver is further based at least in part on at least one of a transmitted second RFID signal or a received second RFID signal at the handheld controller.

15. determining that a third controller is coupled to the receiver; 11. The method of claim 10, further comprising: notifying the software application that the third control unit is coupled to the receiver based at least in part on the determining that the third control unit is coupled to the receiver.

16. A handheld controller system as described in claim 1, wherein the receiver includes a sensor configured to generate data indicative of a control unit coupled to the handheld controller system.

17. A handheld controller system as described in claim 1, wherein the first movement of the first control unit includes at least one of movement in an up, down, left, or right direction, and the second movement of the second control unit includes at least one of movement in the up, down, left, or right direction.

Images