Controller equipped with adjustable functional units

Abstract

A controller capable of adjusting various functional parts of the controller is disclosed. The controller may include one or more speakers for outputting sound or audio content. A user may touch one or more of the speakers with a finger(s) to adjust the characteristics of the audio content and / or adjust audio settings. For example, a user may touch the speakers with a finger to change the volume (e.g., increase or decrease) or to mute the sound. In some examples, the speakers may be located on the controller body of the portable controller for convenient and quick access by the user.

Description

Technology Field

[0001] Cross-reference of related applications

[0002] The present application is a PCT application claiming priority to U.S. Provisional Patent Application No. 62 / 977,046, filed on February 14, 2020, with the title of invention "CONTROLLER WITH ADJUSTABLE FEATURES", and claiming priority to U.S. Patent Application No. 17 / 174,216, filed on February 11, 2021, with the title of invention "CONTROLLER WITH ADJUSTABLE FEATURES", the full contents of each of which are incorporated herein by reference. Background Technology

[0003] Portable controllers are used in many architectures to provide input, for example, to local or remote computing devices. For instance, in the gaming industry, portable controllers are utilized to enable players to interact with personal computing devices running game applications, game consoles, game servers, or the controller itself. While current portable controllers offer a wide range of functions, further technological improvements can enhance the user experience provided by these controllers. Brief explanation of the drawing

[0004] Detailed descriptions are provided with reference to the attached drawings. In the drawings, the leftmost digit(s) of a reference number identify the drawing in which the reference number first appears. Identical or identical reference numbers in different drawings indicate similar or identical items. FIG. 1 illustrates a front perspective view of an exemplary portable controller that partially includes one or more speakers. A user operating the portable controller can adjust the characteristics of audio content being output by the speakers(s) by touching the speakers(s) with their fingers. FIG. 2 illustrates an exemplary technique for detecting finger contact on the speaker of a portable controller. FIG. 3 illustrates other exemplary techniques for detecting finger contact on a speaker of a portable controller, and / or for detecting a finger gesture and the directionality of the gesture on the speaker. FIG. 4 illustrates another exemplary technique for detecting finger contact on the speaker of a portable controller. FIG. 5 illustrates another exemplary technique for detecting finger contact on the speaker of a portable controller. FIG. 6 illustrates an exemplary process for adjusting the audio characteristics of audio content being output from speaker(s) based at least partially on sensor data. FIG. 7 illustrates an exemplary process for adjusting the volume of audio content being output from speaker(s) based at least partially on sensor data. FIG. 8 illustrates an exemplary process for adjusting the audio characteristics of audio content being output from speaker(s) using a high-frequency audio (HFA) tone. FIG. 9 illustrates a front perspective view of an exemplary portable controller comprising, in part, one or more front surface control devices and a display screen having touch sensors for detecting the presence and location of a user operating the portable controller. The controller may also include a mechanism for adjusting the sensitivity of one or more front surface control devices. The adjustment feature may provide a more general-purpose and / or multi-purpose portable controller. FIG. 10 illustrates a rear view of an exemplary portable controller, such as the portable controller of FIG. 9, which partially includes one or more rear surface control devices. FIG. 11 illustrates a rear view of an exemplary portable controller, such as the portable controller of FIG. 9, which includes, in part, one or more receptacles for accommodating additional components. The additional components may improve the ergonomics of the portable controller and / or provide other functions. FIG. 12 illustrates a rear view of an exemplary portable controller, such as the portable controller of FIG. 9, which includes, in part, one or more receptacles for accommodating one or more additional components. FIG. 13 illustrates a rear view of an exemplary portable controller, such as the portable controller of FIG. 9, which partially comprises one or more rear surface control devices operable at least partially by a first rear cover. The first rear cover may be interchangeable with other rear covers to provide other functions to the portable controller. FIG. 14 illustrates a rear view of the portable controller of FIG. 13, including, in part, a second rear cover. The second rear cover may be interchangeable with the first rear cover of FIG. 13 to defeature certain control devices and / or functions of the portable controller. FIG. 15 illustrates a rear view of a portable controller of FIG. 13 that partially includes a third rear cover for providing an enhanced functional unit to the controller. The third rear cover is interchangeable with the first rear cover of FIG. 13 and / or the second rear cover of FIG. 14 to provide different functions to the portable controller. FIG. 16a illustrates a front perspective view of a portable controller of FIG. 9, which partially includes a knob for adjusting the sensitivity of one or more front surface control devices. In FIG. 16a, a knob at a first position corresponding to a first sensitivity of one or more front surface control devices is shown. FIG. 16b illustrates a front perspective view of a portable controller of FIG. 9 that partially includes a knob for adjusting the sensitivity of one or more front surface control devices. In FIG. 16b, a knob at a second position corresponding to a second sensitivity of one or more front surface control devices is shown. FIG. 17a illustrates a first perspective view of a dial mechanism for adjusting the sensitivity of one or more front surface control devices. FIG. 17b illustrates a second perspective view of the dial mechanism of FIG. 17a for adjusting the sensitivity of one or more front surface control devices. FIG. 18 illustrates selected functional components of an exemplary portable controller. Specific details for implementing the invention

[0005] As mentioned above, portable controllers are used in various environments and include a variety of functions. However, some existing portable controllers include static configurations, despite the fact that various users may have diverse configuration requirements, understandings, and / or preferences.

[0006] What is described herein is, among many other things, a portable controller that enables various control devices to participate in video game play through a running video game application and / or to control other types of applications and / or programs. In some examples, the portable controller may include a control device for controlling a game or application running on the portable controller itself (e.g., a standalone portable game system substantially self-contained in the controller). In some examples, the portable controller may include a control device for controlling a remote device (e.g., a television, an audio system, a personal computing device, a game console, etc.). The portable controller may include one or more control devices, including one or more front surface control devices on the front surface of the portable controller housing. Such front surface control devices may include one or more joysticks, directional pads (D-pads), trackpads, trackballs, buttons, or other control devices controllable, for example, by the thumb of the user of the portable controller.

[0007] Additionally or alternatively, the handheld controller may include one or more upper surface control devices located on the upper surface of the housing of the handheld controller. These upper surface control devices may be referred to as "triggers" or "bumpers," and may be controlled by one or more fingers of the user, such as the stop finger or index finger. In some examples, the handheld controller includes one or more upper surface control devices operable by one or more fingers of the user's left hand and / or one or more fingers of the user's right hand. Additionally, the handheld controller may include one or more rear surface control devices. In some examples, the rear surface control device may include one or more control devices operable by the user's left hand and / or the user's right hand.

[0008] The portable controller described herein allows for various configurations depending on the needs of various applications (e.g., game titles), users, etc. Accordingly, the technology described herein enables a dynamically configurable portable controller that corrects some of the current shortcomings of traditional portable controllers as discussed above.

[0009] In some examples, the portable controller may include one or more speakers for outputting sound or audio content. The audio content may be associated with a running game or application. The speaker(s) may be located on the front, side, top, bottom, and / or rear of the portable controller. A user may touch one or more of the speakers with their finger(s) to adjust the characteristics of the audio content and / or adjust audio settings. For example, a user may touch the speakers with their finger to change the volume (e.g., increase or decrease) or to mute the sound. In some examples, the speakers may be located on the controller body of the portable controller for convenient and quick access by the user. For example, a first speaker may be located on the front surface of the controller body on or inside the left side, left half, or left handle of the portable controller, while a second speaker may be located on the front surface of the controller body on or inside the right side, right half, or right handle of the portable controller. In some examples, the user's left thumb can easily access the first speaker, and while the left hand holds the controller, the left thumb can touch the speaker to increase, decrease, and / or mute the volume. Additionally, or alternatively, the user's right thumb can touch the speaker while the right hand holds the controller to increase, decrease, or mute the volume. In some examples, touching the first speaker may decrease the volume, while touching the second speaker may increase the volume, or vice versa. In another embodiment, touching the first speaker and the second speaker simultaneously (or substantially the same amount of time) may mute or unmute the volume.As another example, the user can swipe in a specific direction (e.g., up, down, left, or right) on the speaker(s) to adjust the characteristics of the audio content being output by the speaker(s).

[0010] In some embodiments, one or more sensors may be used to detect or sense finger contact on the speaker, possibly pressure on the speaker and / or gestures on the speaker (e.g., swipe gestures). Accordingly, characteristics of audio content being output by the speaker(s) (e.g., volume) may be adjusted at least partially based on sensor data received from the sensor(s). Various exemplary types of sensors for detecting or sense finger contact on the speaker(s) are described herein, including, but not limited to, inductive sensors, capacitive sensors, impedance sensors, and / or microphones.

[0011] An exemplary controller system may include processor(s) and a controller, wherein the controller may include a controller body, a speaker placed on the controller body, and a sensor associated with the speaker and configured to detect finger contact on the speaker. The controller system may further include logic configured to receive data from the sensor indicating that a finger is in contact with the speaker, and to adjust the characteristics of the audio content being output by the speaker based at least partially on the data. Allowing control of audio characteristics through user interaction with the speaker placed on the controller can provide the user with an intuitive and convenient way to adjust audio characteristics while operating the controller. For example, the user can focus attention on the video game being played while adjusting the volume or muting or unmuting the sound by conveniently touching the speaker placed near another controller being used to play a video game.

[0012] The present disclosure provides an overall understanding of the structure, function, manufacture and use, and principles of the method of the system disclosed herein. One or more embodiments of the present disclosure are illustrated in the accompanying drawings. Those skilled in the art will understand that the system and method described herein and illustrated in the accompanying drawings are non-limiting embodiments. Features illustrated or described in connection with one embodiment may be combined with features of other embodiments, such as between the system and the method. Such modifications and variations are intended to be included within the scope of the appended claims.

[0013] FIG. 1 illustrates a front view of an exemplary controller (100) according to one embodiment of the present disclosure. The controller (100) may be considered portable when the controller is operated by the user's hand, regardless of whether the entire controller (100) is supported by the user's hand or within the hand. However, according to various embodiments described herein, the terms “device,” “portable device,” “portable game device,” “portable console,” “portable game console,” “controller,” and “portable controller” may be used interchangeably herein to describe any device such as the controller (100).

[0014] The controller (100) may include a controller body (102) having a front surface (104). The controller body (102) may further include a rear surface (or rear portion), an upper surface (or upper edge, or upper), a lower surface (or lower edge, or lower), a left surface (or left edge, or left), and a right surface (or right edge, or right). Thus, the controller body (102) may be a rectangular prism. The front surface (104) and the rear surface may be surfaces that are relatively larger than the upper surface, the lower surface, the left surface, and the right surface.

[0015] As illustrated in FIG. 1, the front surface (104) of the controller body (102) may include a plurality of control devices configured to receive user input. Touch data generated by the control devices may be used to detect the presence, location, and / or gesture of a user's finger operating the controller (100). In some examples, the front surface (104) of the controller body (102) may include one or more front surface control devices controllable by one or more thumbs of a user operating the controller (100). Although not illustrated in FIG. 1, the portable controller (100) may further include one or more upper surface control devices located on the upper surface (or upper edge) of the controller body (102). Such upper surface control devices may include, without limitation, triggers, bumpers, etc., and the upper surface control devices may be controlled by one or more fingers of a user, such as a middle finger, index finger, etc. Additionally or alternatively, the portable controller (100) may include one or more rear surface control devices located on the rear surface of the controller body (102) and operable by the fingers of the user's left hand and / or right hand. Additionally or alternatively, the portable controller (100) may include one or more left surface control devices and / or right surface control devices located on the left surface and right surface, respectively, of the controller body (102).

[0016] The front surface control device may include one or more trackpads, trackballs, joysticks, buttons, directional pads (D-pads), etc., as described in more detail below. For example, the front surface (104) may include a left joystick (106), a left trackpad (108), and / or a left D-pad (110) controllable by the user's left thumb. In some embodiments, the front surface (104) may include additional left buttons controllable by the left thumb, such as buttons (112) and buttons (114). The front surface (104) may also include a right joystick (116), a right trackpad (118), and / or one or more right buttons (120(1)-(4)) (e.g., X, Y, A, and B buttons) controllable by the user's right thumb. In some embodiments, the front surface (104) may include additional right buttons controllable by the right thumb, such as buttons (122) and buttons (124). However, the front surface (104) may include other control devices such as tilting button(s), trigger(s), knob(s), wheel(s), and / or trackball(s), and a plurality of control devices may be configured to receive input from any combination of the user's thumb and / or fingers. In some examples, the trigger(s) may be multi-directional triggers configured to be pressed away from the controller (100) and pulled toward the handheld controller (100).

[0017] In some embodiments, the trackpads (108 and 118) are rectangular trackpads. For example, the trackpads (108 and 118) may generally be square trackpads. Furthermore, the rectangular trackpads (108 and 118) may have rounded corners. Additionally, as shown in FIG. 1, the straight side edges of each trackpad (108, 118) are aligned (e.g., parallel) with the side edges (e.g., left and right) of the display (126) located in the center of the controller body (102) on the front surface (104) of the controller body (102). Compared to a circular trackpad, the rectangular trackpads (108 and 118) provide additional space at the corners that can be accessed by the user's fingers (e.g., thumbs). Accordingly, square-shaped trackpads (108 and 118) may be more ergonomic than circular trackpads due to the additional area provided by the trackpads (108 and 118). For example, the square shape of the trackpads (108 and 118) may provide the user with the ability to reorient their hand relative to the controller (100) and still access the trackpads (108 and 118) with their thumb. Additionally, or alternatively, the user may choose to hold the controller body (102) in a slightly different way so that the corners of the trackpads (e.g., trackpads (108 and 118)) are used as the north, south, east, and west parts of the trackpad (e.g., diamond-shaped trackpad).

[0018] Additionally, the controller (100) may include one or more speakers configured to be placed on the controller body (102) and to output audio content or sound. For example, a video game or other application running on the controller (100) may include audio content that is output during the execution of the application (e.g., during gameplay). The speakers may also output other sounds, such as audible notifications.

[0019] FIG. 1 illustrates a pair of speakers positioned on the front surface (104) of a controller body, the pair of speakers comprising a first (left) speaker (128) and a second (right) speaker (130). The left speaker (128) is illustrated as being positioned on the front surface (104) and within the left half (132) (or left side) of the front surface (104), while the right speaker (130) is illustrated as being positioned on the front surface (104) and within the right half (134) (or right side) of the front surface (104). In some examples, the left speaker (128) and the right speaker (130) may be positioned on or near the handle of the controller (100). For example, the left speaker (128) may be positioned on or adjacent to the left handle (136) of the controller (100) configured to be held and / or maintained by the user's left hand, while the right speaker (130) may be positioned on or adjacent to the right handle (138) of the controller (100) configured to be held and / or maintained by the user's right hand. In some examples, the left speaker (128) may be positioned in a location accessible to the user's left thumb while the left hand is holding the controller (100) by the left handle (136), and the right speaker (130) may be positioned in a location accessible to the user's right thumb while the right hand is holding the controller (100) by the right handle (138). In some embodiments, the speaker (128, 130) is positioned on the front surface (104) closer to the lower edge (140) of the controller body (102) than to the upper edge (142) of the controller body (102).

[0020] Although FIG. 1 illustrates a specific shape and location of the speaker (128, 130), the speaker (128, 130) may be located at other places on the controller body (102) (e.g., other surfaces such as other parts of the front surface (104), the rear, the top, the bottom, etc.). The speaker (128, 130) may further include different shapes (e.g., spherical, rectangular, elliptical, etc.). Additionally, the control device (100) may include a single speaker or more than two speakers.

[0021] A user may touch the speaker(s) (e.g., the first speaker (128) and / or the second speaker (130)) to control or adjust the audio characteristics or audio features of the audio content being output by the speaker(s) (128, 130). For example, the user's left thumb may touch the first speaker (128) to disable, enable, and / or adjust specific audio features, while the user's right thumb may touch the second speaker (130) to disable, enable, and / or adjust specific audio features. In some examples, the user may touch either or both of the first speaker (128) or the second speaker (130) to mute or unmute the audio. In some examples, the user may touch the first speaker (128) and the second speaker (130) substantially simultaneously to mute or unmute the audio (e.g., touch the second speaker (130) within a threshold time period, such as within one second or several milliseconds, after touching the first speaker (128), or vice versa). In some examples, the user may touch the second speaker (130) to increase and / or decrease the volume, or touch the first speaker (128) to decrease the volume, and vice versa. In some embodiments, the user may swipe up or right and / or down and left on the speaker (128 or 130) to increase the volume, or swipe down and left on the speaker (128 or 130) to decrease the volume. This is an example of an intuitive interaction (e.g., gesture) for the user.

[0022] In some embodiments, sensor(s) associated with the speaker(s) (128, 130) may be configured to detect finger contact on the speaker(s) (128, 130) to determine whether audio characteristics need to be adjusted. Additionally or alternatively, one or more of the speaker(s) (128, 130) may be pressed to cause the operation of a switch (e.g., a switch(s) placed below the speaker(s) (128, 130)), thereby causing the speaker(s) (128, 130) to be pressed like a button. The sensor(s) configured to detect finger contact on the speaker(s) (128, 130) may be any suitable type of sensor, examples of which are described in more detail below. Generally, the sensor(s) may be configured to detect the proximity of a finger to the speaker(s) (128, 130). Accordingly, the sensor(s) may be proximity sensor(s) (e.g., touch sensor(s)). Additionally or alternatively, the sensor(s) may be pressure sensor(s) configured to detect pressure applied to the speaker(s) (128, 130) and / or the amount of pressure applied.

[0023] FIG. 2 illustrates an exemplary technique for detecting finger contact on a speaker (200) of a portable controller. The speaker (200) illustrated in FIG. 2 may be a schematic diagram of any one of the speakers of the portable controller (100) described herein, such as a first speaker (128) or a second speaker (130), or both. The speaker (200) may include a speaker coil (202) (sometimes referred to herein as "voice coil (202)"). During operation of the speaker (200), current may flow through the speaker coil (202) to move a diaphragm, frame, or suspension, etc., that generates sound. A sensor (204) may be coupled to the speaker coil (202) and may be configured to detect or sense a change in electrical parameters associated with the speaker coil (202) based at least partially on a finger (206) moving in close proximity to the speaker coil (202). For example, the sensor (204) may represent an inductive sensor configured to provide inductance data to the processor(s) of the controller system disclosed herein, and the inductance data indicates a change in inductance associated with the speaker coil (202) based on a finger (206) moving close to the speaker coil (202). In some embodiments, the sensor (204) may be part of or represent an amplifier (e.g., a smart amplifier) ​​of the speaker (200). The smart amplifier may be configured to generate a powerful and rich sound while mitigating damage to the speaker (200) by utilizing modeling and / or algorithms. Such a smart amplifier may include or otherwise utilize the sensor (204) to determine a change in inductance caused by a finger (206) moving closer to or further away from the speaker coil (202) of the speaker (200), which may be determined as an audio waveform is driven out of the speaker (200).In this way, the change in inductance can be utilized to determine whether the finger (206) is in contact with the speaker (200) (for example, by determining whether the inductance value meets the threshold inductance).

[0024] Alternatively, the sensor (204) may be omitted from the system, and the speaker coil (202) may be configured to function as an inductive sensor (or "pickup") without using a separate sensor to detect changes in inductance. In this configuration, the speaker coil (202) itself may be configured to detect or sense changes in inductance based at least partially on a finger (206) moving in close proximity to the speaker coil (202). The processor(s) of the controller system disclosed herein may be coupled to the speaker coil (202) to receive indications of such changes in inductance detected by the speaker coil (202) based on the finger (206) moving in close proximity to the speaker coil (202), and to adjust audio characteristics (e.g., volume) according to the changes in inductance.

[0025] In another embodiment, the sensor (204) may represent a capacitive sensor configured to provide capacitance data to the processor(s) of the controller system disclosed herein, the capacitance data indicating a change in capacitance associated with the speaker coil (202) based on a finger (206) moving in close proximity to the speaker coil (202). That is, the sensor (204) may be configured to determine a change in capacitance caused by a finger (206) moving closer to or further away from the speaker coil (202) of the speaker (200), which may be determined as an audio waveform is driven out of the speaker (200). In this way, the change in capacitance may be utilized to determine whether the finger (206) is in contact with the speaker (200) (e.g., by determining whether the capacitance value meets a threshold capacitance).

[0026] FIG. 3 illustrates other exemplary techniques for detecting finger contact on the speaker (300) of a portable controller and / or for detecting a finger gesture and the directionality of the gesture on the speaker (300). The speaker (300) illustrated in FIG. 3 may be a schematic diagram of any one of the speakers of the portable controller (100) described herein, such as the first speaker (128) or the second speaker (130), or both. The speaker (300) may include a touch sensor (302) placed inside or on top of the speaker (300). For example, the touch sensor (302) may represent a capacitive array very similar to a trackpad touch sensor attached to the cover of the speaker (300). The touch sensor (302) may be configured to detect or determine the presence, location, and / or gesture of a finger (304) in contact with the speaker (300). For example, the touch sensor (302) may detect or sense whether a finger (304) is in contact with the surface of the speaker (300) based on a capacitance value that satisfies (e.g., satisfies or exceeds, strictly exceeds) a threshold value. Although a capacitive sensor is described, the touch sensor (302) may include, without limitation, a resistive sensor, an infrared sensor, a touch sensor that detects the proximity of the finger (304) using acoustic sound waves, and / or other sensors for detecting the presence, location, and / or posture of an object, e.g., the finger (304), in proximity to the speaker (300). In an embodiment utilizing capacitive-based sensing, the touch sensor (302) may include electrodes (e.g., a transmitter electrode and a receiver electrode of a transcapacitive sensor), and a voltage may be applied to the electrodes so that the electrodes are configured to measure a change in capacitance at the electrodes, and this change may be transformed into sensor data in the form of a capacitance value indicating the proximity of an object to the sensor (302). For example, changes in capacitance at the electrodes of a capacitive-based touch sensor(s) can be affected by an object (e.g., a finger) close to the electrodes.Additionally, the logic of the controller system may be configured to analyze touch data generated by the touch sensor (302) to identify the direction of the gesture (e.g., relative up, down, left, or right within a fixed reference plane, such as the XY plane shown in FIG. 1), as well as the gesture (e.g., swipe gesture) of the finger (304) on the speaker (300), such as the finger (304) moving in a specific direction and at a specific speed. Next, the processor(s) may adjust the audio characteristics (e.g., volume) of the audio content based on the gesture (e.g., based on the direction of the swipe gesture).

[0027] FIG. 4 illustrates an exemplary technique for detecting finger contact on a speaker (400) of a portable controller. The speaker (400) illustrated in FIG. 4 may be a schematic diagram of any one of the speakers of the portable controller (100) described herein, such as a first speaker (128) or a second speaker (130), or both. The speaker (400) may include leads (402), such as leads of a speaker coil (or voice coil) of the speaker (400). A sensor (404) may be coupled to the leads (402) and configured to detect or sense a change in electrical impedance between the speaker leads (402) based at least partially on a finger (406) moving in close proximity to the speaker. For example, the sensor (404) may represent an impedance sensor configured to provide impedance data to the processor(s) of the controller system disclosed herein, and the impedance data represents a change in impedance between a pair of leads (402) of the speaker (400) based on a finger (406) moving close to the speaker (400). That is, when the finger (406) contacts the speaker (400) and covers the speaker (400), thereby weakening the sound (408) being output from the speaker (400), the acoustic impedance of the speaker (400) may change, which subsequently may cause a change in electrical impedance between the speaker leads (402). In some embodiments, the impedance sensor (404) may be part of or represent an amplifier (e.g., a smart amplifier) ​​of the speaker (400), and may be configured to determine the change in impedance between the speaker leads (402) caused by the finger (406) moving closer to or further away from the speaker (400) to reduce or stop the sound (408) being output from the speaker (400), which may be determined as the audio waveform is driven out of the speaker (400).In this way, the change in electrical impedance can be utilized to determine whether the finger (406) is in contact with the speaker (400) (e.g., by determining whether the impedance value meets the threshold impedance).

[0028] FIG. 5 illustrates an exemplary technique for detecting finger contact on the speaker (500) of a portable controller. The speaker (500) illustrated in FIG. 5 may be a schematic diagram of any one of the speakers of the portable controller (100) described herein, such as the first speaker (128) or the second speaker (130), or both. The speaker (500) may be configured to output one or more tones (502) at frequencies inaudible to the human ear. Thus, these tone(s) (502) are sometimes referred to as "high frequency audio (HFA) (502)," "high frequency sound (502)," or "ultrasonic communication (502)." The frequency at which the tone(s) (502) are output using HFA may be greater than a threshold frequency (e.g., greater than about 20 kHz). In this way, a human being near the speaker (500) (or the controller (100) including the speaker (500)) that is outputting the tone (502) cannot hear the tone. The controller (100) may further include microphone(s) (504) configured to detect the broadcast tone (502) by generating audio data representing, for example, the HFA tone(s) (502). A series of tones (502) may be output periodically (e.g., every few milliseconds, seconds, etc.) so that the tone (502) is periodically broadcast from the speaker (500) for use in detecting finger contact. If a finger (506) contacts the speaker (500) and covers the speaker (500), thereby weakening the tone(s) (502) being output from the speaker (500), the tone(s) (502) may not appear in the audio data generated by the microphone(s) (504).In other words, the microphone(s) (504) may not be able to detect (or “hear”) the tone(s) (502) when the finger (506) weakens the tone(s) (502) being output by the speaker (500), and in this scenario, the audio data generated by the microphone(s) (504) can be used to determine whether the finger (506) is in contact with the speaker (500) (e.g., by determining whether the amplitude of the tone appearing in the audio data exceeding a threshold frequency does not meet the threshold amplitude).

[0029] The method described herein is exemplified as a set of blocks in a logical flowchart representing a sequence of operations, some or all of which may be implemented in hardware, software, or a combination thereof (sometimes referred to herein as “logic”). In the context of software, a block may represent computer-executable instructions stored on one or more computer-readable media that program a processor to perform the said operation when executed by one or more processors. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc., that perform a specific function or implement a specific abstract data type. The order in which blocks are described shall not be interpreted as a limitation unless specifically stated otherwise. Any number of described blocks may be combined in any order and / or in parallel to implement the method or an alternative method, and not all blocks need to be executed.

[0030] FIG. 6 illustrates an exemplary process (600) for adjusting the audio characteristics of audio content being output from speaker(s) based at least partially on sensor data. In some examples, the process (600) may be performed by a controller (100) and / or a remote device communicateably coupled to the controller (100).

[0031] In block 602, as disclosed herein, the processor(s) of the controller system may receive data from sensor(s) associated with the speaker(s) placed on the controller body (102) of the controller (100), such as the speaker (128) or the speaker (130). The sensor(s) transmitting data in block 602 may be any one of the sensors described herein, such as a sensor configured to detect finger contact on the associated speaker(s). Examples of such sensor(s) are described above with reference to FIGS. 2 through 5, such as an inductive or capacitive sensor (204), a touch sensor (302), an impedance sensor (404), and / or a microphone (504). Data received from the sensor(s) in block 602 may indicate that the finger(s) are in contact with the speaker(s). If the remote device is a device that makes such a judgment, the controller (100) can transmit sensor data to the remote device, and the remote device can process the provided sensor data to detect that a finger is in contact with the speaker(s).

[0032] In 604, the processor(s) may allow the characteristics of the audio content or sound being output by the speaker(s) to be adjusted at least partially based on the data received in block 602. For example, if the sensor data received in block 602 indicates that a finger is in contact with the second (right) speaker (130) (which is placed on the front surface (104) of the controller body (102) within the right half (134) of the front surface (104)), the processor(s) may increase the volume of the audio content or sound being output by the first (left) speaker (128) and the second (right) speaker (130). As another example, if sensor data received in block 602 indicates that a finger is in contact with the first (left) speaker (128) (which is placed on the front surface (104) of the controller body (102) within the left half (132) of the front surface (104)), the processor(s) may reduce the volume of audio content or sound being output by the first (left) speaker (128) and the second (right) speaker (130). Thus, an intuitive interaction may be provided to increase and / or increase the volume by touching the right speaker (130) or to decrease the volume by touching the left speaker (128). As another example, if sensor data received in block 602 indicates that a swipe gesture of a finger has been made on the first (left) speaker (128) and / or the second (right) speaker (130), and if sensor data indicates that the direction of the swipe gesture is upward (e.g., the positive Y direction in FIG. 1) or to the right (e.g., the positive X direction in FIG. 1), the processor(s) may increase the volume of the audio content or sound being output by the first (left) speaker (128) and the second (right) speaker (130). A swipe gesture in the opposite direction (e.g., a downward or left swipe gesture) may cause the volume to decrease.Another embodiment involves touching the two speakers (128, 130) substantially simultaneously to mute or unmute audio content, sound, or its volume. These are merely examples, and any suitable algorithm may be used to adjust the characteristics of the audio content or sound output by the speaker(s) (128, 130) in block 604. As illustrated by the return arrow from block 604 to block 602, the process (600) may be repeated as additional sensor data indicating various types of finger contact with the speaker(s) is received. For example, the user may increase or decrease the volume as desired and mute or unmute the audio during gameplay of a video game.

[0033] FIG. 7 illustrates an exemplary process (700) for adjusting the volume of audio content being output from speaker(s) based at least partially on sensor data. In some examples, the process (700) may be performed by a controller (100) and / or a remote device communicably coupled to the controller (100).

[0034] In block 702, data may be received from a sensor associated with a speaker placed within a specific half of the front surface (104) of the controller body (102) of the controller (100) (e.g., the left half (132) or the right half (134)). For example, sensor data may be received from a sensor associated with the first (left) speaker (128) in block 702 or from a sensor associated with the second (right) speaker (130) shown in FIG. 1.

[0035] In 704, a determination of whether a finger is in contact with the associated speaker may be made at least partially based on sensor data received in block 702. As illustrated by block 706, this determination may be made by detecting a change in an electrical parameter configured to be detected by the sensor. For example, the sensor may be an inductive sensor configured to detect a change in inductance based on a finger moving in close proximity to the speaker coil (202) of the speaker, as described herein. As another example, the sensor may be a capacitive sensor configured to detect a change in capacitance based on a finger moving in close proximity to the speaker coil (202) of the speaker. As yet another example, the sensor may be an impedance sensor configured to detect a change in impedance between a pair of leads (402) of the speaker. If finger contact is not detected in block 704, the process (700) may follow the NO path from block 704 to block 702, additional sensor data may be received in block 702, and the decision in block 704 may be repeated. If finger contact is detected in block 704, the process (700) may follow the YES path from block 704 to block 708.

[0036] In 708, a decision to increase or decrease the volume of audio content or sound being output by the speaker(s) of the controller (100) may be made at least partially based on sensor data received in block 702. As illustrated by block 710, this decision may be made by determining that a specific gesture, such as a swipe gesture and / or the direction of the gesture, has been performed by a finger in contact with the speaker. For example, if the direction of the swipe gesture (e.g., detected by the touch sensor (302) associated with the speaker) is upward or right in the XY plane illustrated in FIG. 1, the processor(s) of the controller system may decide to increase the volume, and if the direction of the swipe gesture is in the opposite direction (e.g., downward or left), the processor(s) may decide to decrease the volume. As another example, in block 712, the processor(s) may determine that the received sensor data is associated with a specific half of the front surface (104) of the controller body (102) or a specific speaker. For example, if the sensor data indicates that a finger is in contact with the second (right) speaker (130), the processor(s) may decide to increase the volume, whereas if the sensor data indicates that a finger is in contact with the first (left) speaker (128), the processor(s) may decide to decrease the volume.

[0037] If it is determined to increase the volume at block 708, the process (700) may follow an up path from block 708 to block 714, and the volume of the audio content or sound is increased at block 714. In some embodiments, this may include increasing the volume setting to the next maximum increment. In some embodiments, the user may touch and maintain contact with the speaker to continue increasing the volume at block 714. If it is determined to decrease the volume at block 708, the process (700) may follow a down path from block 708 to block 716, and the volume of the audio content or sound is decreased at block 716. Additionally, in some embodiments, the user may touch and maintain contact with the speaker to continue decreasing the volume at block 716.

[0038] FIG. 8 illustrates an exemplary process (800) for adjusting the audio characteristics of audio content being output from speaker(s) using high-frequency audio (HFA) tones. In some examples, the process (800) may be performed by a controller (100) and / or a remote device communicably coupled to the controller (100).

[0039] In 802, the speaker(s) of the controller (100) may output one or more tones (e.g., HFA tones) at frequencies inaudible to the human ear as described in this specification. The tone(s) may be output from one speaker or multiple speakers. If tones are output from multiple speakers, each speaker may be configured to output tones at different frequencies. For example, the first (left) speaker (128) may be configured to output first tones at a first frequency greater than about 20 kHz, and the second (right) speaker (130) may be configured to output second tones at a second frequency greater than about 20 kHz.

[0040] In 804, the processor(s) of the controller system disclosed herein may receive audio generated by the microphone(s) (504) of the controller (100). For example, the microphone(s) (504) may capture sound near the controller (100) and generate audio data, and if an HFA tone is emitted by the speaker(s) of the controller (100), the audio data may represent such high frequencies. In some embodiments, the microphone (504) is associated with a specific speaker (e.g., a first microphone associated with a first speaker (128), a second microphone associated with a second speaker (130), etc.) and is configured to detect a tone of a specific frequency emitted by the associated speaker. In another embodiment, a single microphone or microphone array may be configured to capture any sound in the environment of the controller (100), including ambient noise, audio content emitted by the speaker(s) of the controller (100), and HFA tones emitted by one or more speakers of the controller (100). In some embodiments, a filter may remove background / ambient noise and / or audio content associated with video games from the audio data to separate the HFA tones.

[0041] In 806, a determination of whether a finger is in contact with the speaker(s) may be made at least partially based on audio data generated by the microphone(s) (504). For example, if the finger weakens the HFA tone (502) being output by the first (left) speaker (128), audio content in the high-frequency range may be absent from the audio data generated by the microphone(s) (504) or at least below a threshold amplitude, which may indicate that the finger is in contact with the first (left) speaker (128). A similar technique may be employed to detect finger contact with the second (right) speaker (130) or any other speaker of the controller (100). If finger contact is not detected in block 806, the process (800) may continue to output the HFA tone along the NO path from block 806 to block 802 and use the tone to determine finger contact.

[0042] When finger contact is detected in block 806, the process (800) may follow the ‘yes’ path from block 806 to block 808, and in block 808, the processor(s) may cause the characteristics of the audio content or sound being output by the speaker(s) to be adjusted at least partially based on the audio data generated by the microphone(s) (504). For example, if the microphone-generated audio data indicates that a finger is in contact with the second (right) speaker (130) (thus weakening the sound being output), the processor(s) may increase the volume of the audio content or sound being output by the first (left) speaker (128) and the second (right) speaker (130). As another example, if microphone-generated audio data indicates that a finger is in contact with the first (left) speaker (128) (thus weakening the sound being output), the processor(s) may increase the volume of the audio content or sound being output by the first (left) speaker (128) and the second (right) speaker (130). Another embodiment includes touching the two speakers (128, 130) substantially simultaneously (thus weakening the sound being output) to mute or unmute the audio content, sound, or its volume. These are merely examples, and any suitable algorithm may be used to adjust the characteristics of the audio content or sound output by the speaker(s) (128, 130) in block 808.

[0043] FIG. 9 illustrates an exemplary controller (900) having a controller body (902) having a front surface (904). As illustrated, the front surface (904) of the controller body (902) may include a plurality of control devices, including a front surface control device configured to receive input through a user's thumb. For example, the controller (900) may include a left joystick (906), a left trackpad (908), a left D-pad (910) in the form of four individual buttons, a right joystick (912), a right trackpad (914), and a right button (916) (e.g., X, Y, A, B). The controller (100) may also include additional control devices or functional parts similar to the controller (100). Additionally, the controller (900) may include a left handle (918) and a right handle (920) configured to be held in the user's hand.

[0044] In some examples, depending on the game or application, the user may desire a different sensation to increase comfort or desire a specific gameplay experience. Additionally, the user may desire specific components or functions of the portable controller. For example, a first game application may be best played using a first controller, while a second game application may be best played using a second controller. Here, the user can select which controller is available depending on the currently running game application. In this sense, the controller components or specific components of the portable controller may be interchangeable based on user preferences and / or the application. In some examples, the portable controller may be dynamically configured based on the user currently operating the portable controller. Furthermore, in each of these cases, the portable controller or remote system may determine the configuration of the portable controller and the controller currently in operation. This information may be provided to the system running the current application, which can then be modified based on the configuration of the portable controller.

[0045] In some examples, one or more front surface control devices may be pressed. For example, a trackpad (e.g., left trackpad (908) and / or right trackpad (914)) may be pressed to detect pressure and / or enable button-like operation of the trackpad. However, in some examples, the user may prefer to adjust the sensitivity associated with pressing the trackpad or the amount of force required to press the trackpad to enable button-like operation. In some examples, the controller (900) may include a protrusion, lever, or knob (922) for adjusting the sensitivity of one or more of the front surface control devices, such as the right trackpad (914). As illustrated in FIG. 9, the knob (922) may protrude through the front cover of the controller (900) or from the front portion (904). The knob (922) may be operated or otherwise manipulated by the user to adjust the sensitivity of the right trackpad (914). For example, the knob (922) may slide or be repositioned within a slot or channel (924) of the front section (904). The knob (922) may slide within the channel (924) or between the ends of the channel (924) to adjust the sensitivity of the right trackpad (914).

[0046] As discussed herein and illustrated in the drawings thereafter, the knob (922) may be operably coupled to a rotary dial mechanism positioned together with the controller body (902). This rotary dial mechanism can adjust the amount of force required to press the right trackpad (914) and engage one or more switches positioned below the right trackpad (914). The knob (922) may also be positioned adjacent to the right trackpad (914). However, the knob (922) may be positioned in a different location or may protrude through another surface of the controller (900) for user operation. Additionally or alternatively, instead of sliding the knob (922) back and forth to change sensitivity, the user may press a button that changes the sensitivity of the trackpad by operating a motor. Additionally, FIG. 9 illustrates a specific front surface control device including a knob (922) or illustrates that the knob (922) can be operated to change the sensitivity of the specific front surface control device, but other front surface control devices may include a corresponding knob (or other functional part) for adjusting the associated sensitivity.

[0047] FIG. 10 illustrates a rear portion (1000) of a controller body (1002) of a controller (1004) that may represent a rear portion of a controller (100) or a controller (900). FIG. 10 further illustrates an upper portion (1006) of a controller (1004) that may represent an upper portion of a controller (100 or 900).

[0048] The upper part (1006) may include one or more left trigger(s) and / or one or more right trigger(s). In some examples, each of the one or more left trigger(s) and / or one or more right trigger(s) may be located along the upper edge of the controller body (1002). The one or more left trigger(s) and / or one or more right trigger(s) may be controlled by the user's index finger during normal operation while the controller (1004) is held by the user. The upper part (1006) may additionally or alternatively include a pushable button (or other additional input control device) that may be controllable by the user's finger. In some examples, the upper part (1006) may include a touch sensor for detecting the presence, position, and / or gesture of the finger(s) on the control device(s). Additionally, the upper part (1006) may include receiver(s), such as a wired communication interface (e.g., port, plug, jack, etc.), for communicatingly connecting the controller (1004) to an external device (e.g., charger, game console, display, computing device, etc.).

[0049] The rear portion (1000) of the controller body (1002) may also include one or more left control devices (1008) and / or one or more right control devices (1010), which can be conveniently operated by the user's detection or suspension during normal operation while the controller (1004) is held in the user's hand. One or more left control devices (1008) and / or one or more right control devices (1010) may be touch-sensitive to identify the presence, position, and / or gesture of one or more fingers on the control device(s).

[0050] In addition to providing various control devices, the portable controller may support various interchangeable accessories. For example, parts of the portable controller held or held in the user's hand may be interchangeable or swapped with one another to provide different tactile and / or comfort levels. These grips may vary in size, shape, and / or contour to fit the hand and allow the user to grip them. For example, a small grip may be used by users with small hands, while a larger grip may be used by users with large hands. In some examples, the grip (or handle) may be attached to or inside a receiver located on the rear and / or side(s) of the portable controller. Various grips may be detachably attached to or inside the receiver(s). The grip may also provide the user with an additional surface to clutch or hold when operating the portable controller. For example, the grip may include varying degrees of contours and protrusions, and the user may select the corresponding grip depending on the application or user preference.

[0051] In some examples, the portable controller may include a cavity or compartment located at the rear of the portable controller. The compartment may include a control device (e.g., a button) operable via a cover placed over the compartment. The cover may conceal the compartment when attached. The button may be placed within the compartment, and the button (or other sensor / switch) may be operable by applying pressure to parts of the cover. For example, applying pressure to the cover may engage one or more buttons.

[0052] FIG. 11 illustrates a rear portion (1100) of a controller body (1102) of a controller (1104) that may represent a rear portion of a controller (100) or a rear portion of a controller (900). The rear portion (1100) of the controller body (1102) may include a receptacle (1106) for receiving one or more accessories, which attach the accessories to the rear portion of the controller body (1102). As illustrated, the receptacle (1106) may include a recess, pocket, or compartment disposed on the controller body (1102) and / or within. In some examples, the receptacle (1106) may include a side wall disposed below the surface of the rear portion (1100) to secure or attach the accessories to the controller body (1102). In other words, the receptacle (1106) may include a concave side wall below the surface of the rear portion (1100) of the controller body (1102). Reducing the receptacle (1106) in this way allows the accessory to be secured to or within the controller body (1102) and prevents the accessory from being translated or shifted in other ways during use.

[0053] In some examples, the receptacle (1106) may be positioned on the left and right handle portions of the controller body (1102) and configured to be grasped or held by the user's hand, respectively. Here, for example, the receptacle (1106) may accommodate an accessory that is to be grasped or held by the user. In other examples, the receptacle (1106) may accommodate an accessory to be controlled by the user's left and right fingers. For example, FIG. 11 illustrates that the receptacle (1106) may be positioned on the left handle portion of the controller (1104). As discussed herein, the accessory may be attached to the controller body (1102), and the user's left hand may hold the accessory or otherwise utilize the accessory. However, in some cases, the controller (1104) may be operable without an accessory attached to the controller body (1102). In this sense, the accessory may increase functionality and provide specific functional parts to the controller (1104).

[0054] In some examples, one or more accessories may be removablely coupled to the rear portion (1100) of the controller body (1102) within the receptacle (1106) and may be interchangeable. For example, different accessories may be coupled to the controller body (1102) depending on the user, the user's preference and / or application. In some examples, the accessories may provide various grips or provide surfaces and / or areas of the controller (1104) that the user holds or maintains while operating the controller (1104). In some examples, the user may exchange accessories based on the current application the user is playing (e.g., game title), based on the user's comfort, and / or for any other reason.

[0055] FIG. 11 illustrates a plurality of accessories (1108) that can be coupled to a controller body (1102). In some examples, a user of the controller (1104) may exchange the accessories (1108) coupled to the controller body (1102) to change the function, look, or feel of the controller (1104). For example, various accessories may include various sizes, textures, shapes, heights, etc. In one embodiment, various accessories have various heights and shapes (e.g., convex, concave, flat, etc.). For example, a first accessory (1108(1)) may represent a first grip configured to be coupled to the controller body (1102). A second accessory (1108(2)) may represent a second grip configured to be coupled to the controller body (1102). By comparison, the first accessory (1108(1)) and the second accessory (1108(2)) may represent grips formed differently in size or shape, having various contours and shapes. For example, the first accessory (1108(1)) may be usable by a user with large hands, while the second accessory (1108(2)) may be usable by a user with small hands. In either case, both the first accessory (1108(1)) and the second accessory (1108(2)) may provide or serve as a part of the controller (1104) held by the user (e.g., a left grip held by the user).

[0056] The accessory (1108) may also include a third accessory (1108(3)) and / or a fourth accessory (1108(4)). The third accessory (1108(3)) exemplifies a grip (or handle) having a button (1110) operable by a user. The user may operate the button (1110) to perform a corresponding action within a game and / or application. The fourth accessory (1108(4)) may represent an extended battery pack to provide extended battery life to the controller (1104). Additionally, the accessory (1108) may include a touch-sensing control device for identifying the presence, position, and / or gesture of one or more fingers on the control device(s).

[0057] In some examples, grips or other accessories may be magnetically coupled to the rear and / or side of the handheld controller. In this way, grips can be easily interchanged. However, other attachment mechanisms (e.g., snap-fits, slots, hooks, etc.) may be used. Additionally, the grip may also include one or more control devices (e.g., buttons). In these examples, the receiver and the grip may include corresponding connectors for transmitting touch data, input data, and / or selection data to the handheld controller. For example, the grip may include buttons for controlling aspects of a game or application. In addition to coupling the grip to the handheld controller via an attachment mechanism, for example, a connector on the grip may be communicably coupled to a connector on the handheld controller to provide data (e.g., indicating the press of a button) to the handheld controller.

[0058] Regardless of the type of accessory or the associated functional part of the accessory (1108), the accessory (1108) may be removablely coupled to the controller body (1102) to add a grip, function, and / or functional part to the controller (1104). In some examples, the accessory (1108) may be coupled to the controller body (1102) through an engagement between an attachment mechanism on the controller body (1102) and an attachment mechanism on the accessory (1108). For example, the lower surface or other surface of the receptacle (1106) may include a first magnetic element (e.g., a first magnet) complementary to a second magnetic element (e.g., a second magnet) on the accessory (1108). For example, the lower part of the receptacle (1106) may include a magnetic element that engages with a magnetic element located on the lower surface of the accessory (1108). The interlocking or attractive force between the first magnetic element and the second magnetic element can secure or hold the accessory (1108) within the receptacle (1106) and / or the controller body (1102). However, the interlocking force between the first magnetic element and the second magnetic element can be overcome by the user applying a greater amount of force. In this way, the user can replace or exchange the accessory (1108) attached to the controller body (1102).

[0059] However, the accessory (1108) and the controller body (1102) may be joined to each other using a mechanism other than magnetic elements. For example, the accessory (1108) may include a tab that engages with a hook of the controller body (1102). Additional attachment mechanisms may include snap-fits, hooks and loops, press-fits and / or mechanical fasteners. Additionally, in some examples, the accessory (1108) may include a flange or lip that engages with or contacts the side wall of the receptacle (1106) to further join or secure the accessory (1108) within the receptacle (1106) or to the controller body (1102).

[0060] Additionally, the controller body (1102) may include a connector for commutatively coupling the function of the accessory (1108) to the controller (1104), and vice versa. In some examples, the connector may be located within a receptacle (1106) and may receive or be coupled to a corresponding connector of the accessory (1108). For example, if the controller (1104) includes a third accessory (1108(3)) or a fourth accessory (1108(4)), power from the battery may be transmitted to the controller through the connector, and data indicating the pressing of the button may be transmitted to the controller (1104) through the connector. In some examples, the connector may represent a prong connector that is complementary to interlock with each other and couples the function of the sensor, button, and / or accessory to the controller (1104). In some embodiments, the accessory (1108) can wirelessly transmit / receive data to / from the corresponding transceiver of the controller (1104).

[0061] Although FIG. 11 illustrates a specific location, size, or shape of the receptacle (1106), the receptacle (1106) may be located elsewhere on the controller body (1102). In some examples, more than two receptacles (1106) and more than two accessories (1108) may be coupled to the controller body (1102). Additionally, while the above discussion illustrates a single accessory accommodated by the receptacle (1106), the receptacle (1106) may be configured to accommodate multiple accessories. For example, a first accessory may be coupled within the receptacle (1106) and engage with a first magnetic element of the magnetic element, while a second accessory may be coupled within the receptacle (1106) and engage with a second magnetic element of the magnetic element. Due to the compatibility of the accessory (1108), the user can customize the controller (1104) to suit their preferences according to the user's desired function (or feel). In some examples, the controller (1104) and / or the system telecommunicationally coupled to it may determine which accessory (1108) is coupled to the controller body (1102) to use in determining the function of the controller (1104) and / or the functional part of the controller (1104) (e.g., tag, RFID, magnet, etc.). For example, after identifying the accessory currently coupled to the controller (1104), the controller (1104) and / or the system telecommunicationally coupled to the controller (1104) may relay the identification of the control of the application being executed by the system. Next, the system may consider this information to determine one or more parameters of the application (e.g., correction and scaling factors associated with the movement of the control device). In other embodiments, the application (e.g., a game) may enable different movement / control options based on which control is currently connected to the receiver.

[0062] FIG. 12 illustrates a rear view of a controller (1104) showing a first accessory (1108(1)) coupled to the controller body (1102) and inside the receptacle (1106). Once coupled, the accessory (1108(1)) can be fixed to the controller (1104) and operated by a user. Additionally, once coupled, the rear portion (1100) of the controller (1104) can have a smooth and continuous surface for the user. As illustrated, the user can grasp the accessory (1108(1)) to hold the controller (1104) in their hand or otherwise grip it.

[0063] In some examples, the cover may be interchangeable with other covers depending on the game, application, and / or user preference. Different covers may provide additional functionality to the portable controller or de-functionalize specific functional parts of the portable controller. For example, a user may attach a cover that de-functionalizes the controller within the compartment. In some examples, this cover may include a part that is not pressable and does not operate or engage with a button located within the cover. Additionally, the interchangeable cover may include electronic devices such as a battery, a haptic feedback mechanism, etc. Here, for example, if the user wishes to extend battery life, the user may attach a cover containing a battery for the portable controller. For example, if the user wishes to receive haptic feedback during a racing game, the user may attach a cover containing a haptic actuator. In such cases, the cover may include an electronic device and a connector for connecting the electronic device of the cover to the portable controller. For example, the connector of the cover may be connected to the connector of the compartment.

[0064] FIGS. 13 through 15 illustrate a rear portion (1300) of a controller body (1304) comprising various rear covers attached to the controller body (1302). In some examples, the rear portion (1300) may represent the rear portion of a controller (100) or the rear portion of a controller (900). The rear portion (1300) of the controller body (1302) includes a receiver for accommodating different types of rear covers. Thus, different covers may be configured to be mounted, coupled, or attached to the rear portion (1300). In some examples, the rear covers may be coupled to the rear portion (1300) via a latch mechanism, a magnet, a fastener, and / or any combination thereof. Additionally, the controller (1304) may be configured to acquire data indicating which rear cover is currently coupled to the controller (1304). Next, the controller (1304) or other system can use this data to make these decisions, which can then be used by an application operating through the controller (1304).

[0065] Referring to FIG. 13, a first cover (1306) is shown attached to a controller body (1302). The first cover (1306) may include four buttons, two of which are located on the left side, such as with the first control device (1308) and the second control device (1310), and two of which are located on the right side, such as with the first control device (1312) and the second control device (1314). In some examples, when the controller (1304) is held by a user, the buttons located on the left side may be operated or controlled by the user's left fingers (e.g., ring finger, middle finger, index finger), and the buttons located on the right side may be operated or controlled by the user's right fingers (e.g., ring finger, middle finger, index finger). A dividing line on the first cover (1306) may separate the control device so that the control device can be addressed separately. For example, the user can hold the controller (1304) through the left handle (1316) and the right handle (1318). In this position, the user can press the button.

[0066] Buttons on the left and right sides of the controller body (1302) may be individually pressed to engage or activate switches placed within the compartments of the controller (1304). Each individual button, or each part of the first cover (1306), may engage with each switch (1320) within the compartment. For example, the switch (1320), illustrated by a dashed line, may be placed within the compartment, and the compartment may be placed under the first cover (1306) when the first cover (1306) is attached to the controller body (1302). In some examples, the switch (1320) may include a tactile or mechanical switch configured to detect or sense pressure, and / or may include a force sensing resistor (FSR) having a transducer having an electrical resistance that changes based on the applied force being experienced.

[0067] Removing the first cover (1306) may allow access to a compartment, which, in some examples, may include a battery and a switch (1320). Thus, by pressing the control device, the control device itself or a part of the control device, such as a protrusion, may engage with the switch to perform a specific action. Additionally, although FIG. 13 illustrates the first cover (1306) as including four buttons or two buttons placed on each side, the first cover may include any number of buttons and / or the buttons may be located in other positions. In such cases, the controller (1304) may include a corresponding number of switches placed and positioned below the buttons.

[0068] FIG. 14 illustrates a second cover (1400) attached to a controller body (1302). Compared to the first cover (1306), the second cover (1400) may not include any button configured to be pressed or capable of pressing the switch (1320). For example, the switch (1320) is still depicted in FIG. 14 and within the controller body (1302) to indicate its presence beneath the second cover (1400). However, the second cover (1400) may not include a button, or a portion of the second cover (1400) may not be able to be pressed to engage with the switch (1320). In some examples, the user may replace the first cover (1306) with the second cover (1400) based on the user's comfort, based on the current application (e.g., game title) the user is playing, and / or for any other reason.

[0069] Considering that the second cover (1400) does not include a feature that engages with the switch (1320), it can be said that the second cover (1400) deactivates, de-features, or disables the switch (1320) within the compartment. That is, the controller (1304) may still include the switch (1320) within the compartment, but attaching the second cover (1400) to the controller body (1302) may prevent the switch (1320) from being activated. In some examples, the user may replace the second cover (1400) with the first cover (1306) if the game or application does not require input from the button on the rear cover, and / or if the user does not wish to utilize the button on the rear cover.

[0070] Additionally, in some cases, since the switch (1320) cannot be operated when the second cover (1400) is coupled to the controller, the switch (1320) may be disabled to save power (e.g., by suppressing the supply of power to an electronic device associated with the switch (1320)). In other words, based on the rear cover coupled to the controller body (1302), the controller may be configured to detect a specific input and / or disable a specific function accordingly.

[0071] FIG. 15 illustrates a third cover (1500) attached to a controller body (1302). In some examples, the third cover (1500) may include buttons operable by the user's left and right hands. In some examples, the user may replace the first cover (1306) or the second cover (1400) with the third cover (1500) based on the user's comfort, based on the current application (e.g., game title) being played, and / or for any other reason. Additionally, the third cover (1500) may include additional electronic devices to provide additional features and / or functions to the controller. For example, the third cover (1500) may include a haptic actuator to provide vibration feedback to the user. Additionally, or alternatively, the third cover (1500) may include a battery to charge the controller (1304) or extend its battery life. However, the third cover (1500) may include additional electronic components that can be operated by the user and / or increase the functionality of the controller (1304).

[0072] In this case, the third cover (1500) may include a connector for communically connecting with the controller (1304). For example, the connector of the third cover (1500) may be connected to a connector placed within a section of the controller (1304) to provide data, transmit power, and activate the functions of the third cover (1500), and vice versa.

[0073] In some examples, the control device of the portable controller may be adjusted to increase and / or decrease sensitivity. In some examples, the control device may be completely disabled so that its sensitivity becomes zero (or substantially zero). For example, the portable controller may include a front surface control device such as a trackpad. The trackpad may include touch sensors to detect or determine presence, location, and / or gestures provided by the user. The trackpad may also be pressed (e.g., clickable). In some examples, the user may adjust the sensitivity of the trackpad to detect pressure. In other words, the user may adjust the amount of force the user must apply to the control device to press the trackpad. In this way, the sensitivity required to press the trackpad or the switch underneath the trackpad may be adjusted according to the game, application, and / or user preference.

[0074] In some examples, a mechanical function may control, or be used to control, the sensitivity of the trackpad for detecting pressure. A knob on the handheld controller may be slidable, twistable, rotatable, or actuated in other ways to adjust the sensitivity. In some examples, the knob may be coupled with a rotary dial mechanism located beneath the trackpad (or inside the controller's housing). The rotary dial mechanism may change the amount of force required for the user to press the trackpad. For example, rotating the dial may change the position of a support arm on a circular frame, which in turn adjusts how easy or difficult it is to press the trackpad. For example, in a first position, the knob may allow the trackpad to be pressed easily with a small force. In a second position, the knob may disable or effectively disable the pressability of the trackpad. In the second position, or when it is more difficult to press the trackpad, the user may be required to apply a greater amount of force to press the trackpad compared to when the trackpad can be pressed easily (e.g., in the first position). In some examples, the first and second positions may be considered as extremes or ends of the sensitivity range. However, the knob may be adjusted to one or more intermediate positions between the first and second positions to modify the sensitivity required to press the trackpad.

[0075] Existing portable controllers include selectable control units, but combining a control unit with a switch to identify the selection of the control unit using touch sensing capabilities (and associated sensitivity) can increase the quantity and richness of gestures that can be interpreted by the portable controller. Additionally, these gestures can enrich the operation of games or other applications controlled by the portable controller. Adjusting the sensitivity of the control unit and swapping specific control units with one another can further increase this richness.

[0076] FIGS. 16a and FIGS. 16b illustrate a knob (922) of a controller (900) located at different positions for adjusting the sensitivity of a control device, such as a right trackpad (914). As introduced and discussed above in relation to FIG. 9, the knob (922) can be slid within a channel (924) to adjust or change the sensitivity of the right trackpad (914). For example, the right trackpad (914) can be pressed, and by moving the knob (922) within the channel (924), the amount of force required to press the right trackpad (914) to engage one or more switches can be adjusted. As discussed in detail herein, the knob (922) can interact with one or more functional parts, such as a radial dial mechanism placed below the right trackpad (914), to adjust the sensitivity.

[0077] In FIG. 16a, the knob (922) is positioned at a first position (1600) within the channel (924). The first position (1600) may correspond to a first sensitivity (e.g., how hard the user must press) at which the right trackpad (914) can be pressed. For example, the first position (1600) is depicted as being at the leftmost position within the channel (924) (i.e., the knob (922) cannot be moved further to the left). In some examples, the first position (1600) may represent a first extreme of sensitivity. For example, when the knob (922) is at the first position (1600), the sensitivity may be at its maximum, and the right trackpad (914) may be easily pressed with a small amount of force. As such, the right trackpad (914) may be sensitive to being pressed by the user.

[0078] In FIG. 16b, the knob (922) is positioned at a second position (1602) within the channel (924). The second position (1602) may correspond to a second sensitivity of the right trackpad (914) that can be pressed. For example, the second position (1602) is depicted as being at the far right position within the channel (924) (i.e., the knob cannot be moved further to the right). In some examples, the second position (1602) may represent a second extreme of sensitivity. For example, when the knob (922) is at the second position (1602), the sensitivity may be at its lowest, and the right trackpad (914) may require a greater amount of force to be pressed. In such cases, the user may be required to apply a greater amount of force to the right trackpad (914) than when the knob (922) is in the first position (1600) in order to press the right trackpad (914). The far right position may also represent a scenario where the right trackpad (914) cannot be pressed, and thus, the pressable characteristics of the right trackpad (914) may be de-functionalized or disabled. Regardless of the sensitivity or the position of the knob (922), the right trackpad (914) can still detect touch input. In some examples, the sensitivity of the pressable right trackpad (914) may not affect the sensitivity of the right trackpad (914) to detect touch input.

[0079] In some examples, the front portion (904) of the controller (900) may include a visual indicator indicating the sensitivity of the right trackpad (914). For example, a visual indicator such as a less symbol ("-") may be positioned adjacent to the left side of the channel (924), while a visual indicator such as a plus symbol ("+") may be positioned adjacent to the right side of the channel (924). These indicators may indicate to the user how to decrease or increase the sensitivity of the right trackpad (914).

[0080] Although FIGS. 16a and 16b illustrate adjusting the sensitivity of the right trackpad (914), other control devices of the controller (900) (or controller (100)) may be adjusted in a similar manner. For example, the sensitivity of the left trackpad (908) being pressed may be adjusted. Additionally, instead of the controller (900) including a knob (922) for adjusting sensitivity, other mechanisms such as buttons, screws, pins, motors, or levers may be used to adjust the sensitivity of the control device. Also, instead of the knob (922) sliding within the channel (924) to adjust sensitivity, the knob (922) may be located elsewhere on the controller body (902) and / or implemented as another slide, channel, or track for adjusting sensitivity.

[0081] The knob (922) can also be adjusted to any position along the channel (924) to configure the right trackpad (914) to a specific sensitivity. That is, while FIGS. 16a and 16b illustrate a knob (922) positioned at the outer extreme of the channel (924), the knob (922) can be positioned at any intermediate position within the channel (924), and the right trackpad (914) can have a sensitivity corresponding to the intermediate position. Thus, the sensitivity of the right trackpad (914) (or other control device) can be gradually adjusted.

[0082] FIGS. 17a and FIGS. 17b illustrate a perspective view of a rotary dial mechanism (1700). The rotary dial mechanism (1700) may be operably coupled to a knob (922) to adjust the sensitivity of a control device such as a right trackpad (914). As illustrated, the rotary dial mechanism (1700) may include a frame (1702) having an upper surface (1704), a dial (1706), and a channel (1708) configured to allow the arm (1710) of the dial (1706) to be operated. The upper surface (1704) may be coupled to the lower part of the right trackpad (914) or to the lower part of the touch sensor of the right trackpad (914). Thus, the upper surface (1704) may be positioned vertically below the right trackpad (914). In some examples, the right trackpad (914) and / or rotary dial mechanism (1700) may be integrated or combined as a single component within the controller or controller body. Combining a controller having a switch to identify the selection of the controller with a touch sensing function can increase the quantity and richness of gestures that can be interpreted on the portable controller. Additionally, these gestures can enrich the operation of games or other applications controlled by the controller.

[0083] The dial (1706) is operably coupled to the knob (922) as discussed above in relation to FIGS. 16a and 16b. For example, one end of the knob (922) disposed within the controller body (902) may be attached to or fixed to the dial (1706), for example, to the arm (1710) of the dial (1706). The dial (1706) may be configured to rotate and control the knob (922) as discussed above in relation to FIGS. 16a and 16b, and may cause the dial (1706) to rotate within a rotary dial mechanism (1700). For example, the dial (1706) may rotate around a central axis or a hub. As the dial (1706) rotates, the arms (1710) may each move within the channels (1708). For example, the rotary dial (1706) may include three arms (1710), each of which is placed within a respective channel (1708).

[0084] Each arm (1710) may have a limited range of motion in the vertical direction within the channel (1708). For example, at both ends of the channel (1708), the arm (1710) may be prevented from rotating or moving further through the side wall or end wall. However, as the arm (1710) slides or rotates in the first direction within the channel (1708), the distance between the arm (1710) and the upper and lower surfaces of the channel (1708) may be reduced (for example, the channel (1708) may be reduced or contracted). Next, the arm (1710) may come into contact with the upper and lower surfaces of the channel (924) and be constrained between them. Constraint of the arm (1710) within the channel (1708) may reduce the amount configured to allow the right trackpad (914) to be pressed, and subsequently reduce the sensitivity of the right trackpad. In this case, the right trackpad (914) may be more difficult to press to engage one or more switches. A spring or other biasing member may provide mechanical action to the pressable characteristics of the right trackpad (914).

[0085] Conversely, moving the arm in a second opposite direction releases the arm from the upper and lower surfaces of the channel (1708), allowing the right trackpad (914) to be easily pressed. That is, because the arm (1710) of the dial (1706) may no longer be constrained between the upper and lower surfaces of the channel (1708), the arm (1710) may be pressed vertically, and subsequently the right trackpad (914) may be pressed. However, the arm (1710) may be positioned at a different location within the channel to modify or gradually adjust the sensitivity at which the right trackpad (914) can be pressed.

[0086] Collectively, each arm (1710) may be positioned within each channel (1708) to engage with each upper and lower surface of the channel (1708). In this way, the amount of force required to press the right trackpad may be uniform across the surface of the right trackpad (914) or at various locations on the upper side of the right trackpad (914). Additionally, while FIGS. 17a and 17b illustrate a dial (1706) having three arms, the dial (1706) may include fewer than three or more than three arms (1710) to engage with each channel. Furthermore, one or more mechanical movements within the controller may provide tactile or mechanical movement to the right trackpad (914) or the rotary dial mechanism (1700) to enable the right trackpad (914) to be pressed.

[0087] FIG. 18 illustrates an exemplary computing component of a controller (1800), such as a controller (100) or a controller (900). As illustrated, the portable controller (1800) includes one or more input / output (I / O) devices (1802), such as the aforementioned control devices (e.g., joystick, trackpad, trigger, etc.), and potentially any other type of input or output device. For example, the I / O device (1802) may include one or more microphones for receiving audio input, such as user voice input. In some embodiments, one or more cameras or other types of sensors (e.g., inertial measurement units (IMUs)) may function as input devices for receiving gesture input, such as motion of the controller (1800). In some embodiments, additional input devices may be provided in the form of a keyboard, keypad, mouse, touchscreen, joystick, control button, etc. The input device(s) may further include control mechanisms such as power and reset buttons, as well as basic volume control button(s) for increasing / decreasing volume.

[0088] Meanwhile, the output device may include a display, a light element (e.g., an LED), a vibrator for generating haptic sensations, speaker(s) (e.g., headphones), etc. For example, there may also be a simple light element (e.g., an LED) indicating a state such as when the power is on. Although a few examples have been provided, the portable controller may additionally or alternatively include any other type of output device.

[0089] In some cases, the output by one or more output devices may be based on the input received by one or more input devices. For example, a selection of the control device may produce an output of a tactile response by a vibrator located adjacent to (e.g., below) the control device or at any other location. In some cases, the output may vary based at least partially on the characteristics of a touch input on a touch sensor, such as a touch sensor associated with the control device. For example, a touch input at a first location on the touch sensor may produce a first tactile output, while a touch input at a second location on the touch sensor may produce a second tactile output. Furthermore, a specific gesture on the touch sensor may produce a specific tactile output (or other types of output). For example, a swipe gesture on the control device may produce a first type of tactile output, while a tap on the control device (detected by the touch sensor) may produce a second type of tactile output, while strong pressure on the control device may produce a third type of tactile output.

[0090] Additionally, the controller (1800) may include one or more communication interfaces (1804) to facilitate wireless connection to a network and / or one or more remote systems and / or devices (1805) (e.g., a host computing device running an application, a game console, etc.). The communication interfaces (1804) may implement one or more of various wireless technologies such as Wi-Fi, Bluetooth, radio frequency (RF), etc. It will be understood that the controller (1800) may further include physical ports to facilitate wired connection to a network, connected peripheral devices, or a plug-in network device communicating with another wireless network.

[0091] In the illustrated embodiment, the portable controller (1800) further comprises one or more processors (1806) and a computer-readable medium (1808). In some embodiments, the processor(s) (1806) 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, what is functionally described herein may be performed at least partially by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), an application-specific standard product (ASSP), a system-on-a-chip system (SOC), a complex programmable logic device (CPLD), etc. Additionally, each of the processor(s) (1806) may have its own local memory capable of storing program modules, program data, and / or one or more operating systems.

[0092] A computer-readable medium (1808) may include volatile and non-volatile memory, removable and non-removable media implemented by any method or technique for storing information such as computer-readable instructions, data structures, program modules, or other data. Such memory may include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage device, magnetic cassette, magnetic tape, magnetic disk storage device, or other magnetic storage device, RAID storage system, or any other medium that can be used to store desired information and can be accessed by a computing device. The computer-readable medium (1808) may be implemented as a computer-readable storage medium ("CRSM"), which may be any available physical medium accessible by processor(s) (1806) to execute instructions stored in the computer-readable medium (1808). In one basic embodiment, the CRSM may include random access memory (RAM) and flash memory. In another embodiment, the CRSM may include read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), or any other type of tangible medium that can be used to store desired information and accessed by the processor(s) (1806), but is not limited thereto.

[0093] Various modules, such as instructions, data stores, etc., may be stored within a computer-readable medium (1808) and configured to be executed on a processor(s) (1806). Although several exemplary functional modules are shown as being stored in the computer-readable medium (1808) and executed on the processor(s) (1806), the same functions may alternatively be implemented in hardware, firmware, or a System-on-Chip (SOC).

[0094] An operating system module (1810) may be configured to manage hardware within the controller (1800) for the benefit of other modules and may be coupled to the controller. Additionally, the computer-readable medium (1808) may store a network communication module (1812) that enables the controller (1800) to communicate with one or more other devices (1805), such as a personal computing device, a game console, a remote server, etc., running an application (e.g., a game application) via a communication interface (1804). The computer-readable medium (1808) may further include a game-session database (1814) for storing data associated with a game (or other application) running on a portable controller or on a computing device to which the controller (1800) is coupled. The computer-readable medium (1808) may also include a device record database (1816) for storing data associated with a device to which the controller (1800) is coupled, such as a personal computing device, a game console, a remote server, etc. The computer-readable medium (1808) may further store game control commands (1818) that configure the controller (1800) to function as a game controller, and general-purpose control commands (1820) that configure the controller (1800) to function as a controller for other non-gaming devices.

[0095] In some examples, some or all of the components (software) illustrated in FIG. 18 may be implemented on other computing device(s) (1805) that are part of a controller system (1807) including a controller. In such cases, the processes and / or functions described herein may be implemented by other computing devices (1805) and / or controllers (1800). For example, the controller (1800) may combine the computing device(s) / server with a host PC or console in the same environment and may provide data to the device (1805) indicating accessories combined with the controller. For example, the controller (1800) may transmit data indicating or identifying accessories combined with the controller (1800). These data may be used by computing device(s) (1805) during a gameplay experience, or by computing device(s) when determining how to interpret data received from the controller (1800) (e.g., which button is pressed, what the button press means, etc.). Based on this data, the computing device (1805) may determine which accessory(s) are connected to the controller. In another embodiment, the computing device (1805) may receive data indicating the adjusted sensitivity of the controller device to be used to interpret data received from the controller (1800) and to cause one or more actions to be performed. However, although several scenarios are described, the controller (1800) and computing device(s) (1805) may be coupled to communicate with each other to transmit and receive data so that the controller (1800), the computing device (1805), and / or other devices of the controller system (1807) can perform the actions and processes described herein.

[0096] Exemplary provisions

[0097] 1. A controller comprising: a controller body including a rear portion; a first receptacle disposed in the rear portion of the controller body and configured to receive a first grip - the first receptacle includes a first attachment mechanism configured to engage with a second attachment mechanism of the first grip to connect the first grip to the controller body -; and a second receptacle disposed in the rear portion of the controller body and configured to receive a second grip - the second receptacle includes a third attachment mechanism configured to engage with a fourth attachment mechanism of the second grip to connect the second grip to the controller body -.

[0098] 2. In Clause 1, the controller body further comprises a left handle portion and a right handle portion, wherein a first receptacle is positioned in close proximity to the left handle portion; and a second receptacle is positioned in close proximity to the right handle portion.

[0099] 3. A controller according to Clause 1, wherein the first attachment mechanism comprises a first magnetic element; the second attachment mechanism comprises a second magnetic element capable of engaging with the first magnetic element; the third attachment mechanism comprises a third magnetic element; and the fourth attachment mechanism comprises a fourth magnetic element capable of combining with the third magnetic element.

[0100] 4. A controller according to Clause 1, wherein the first grip is one of a first plurality of grips that are each different in at least one of the contour, shape, or size, and each of the first plurality of grips is configured to be received within a first receptacle; and the second grip is one of a second plurality of grips that are each different in at least one of the contour, shape, or size, and each of the second plurality of grips is configured to be received within a second receptacle.

[0101] 5. A controller according to Clause 1, characterized in that the first grip comprises one or more first buttons; or the second grip comprises one or more second buttons.

[0102] 6. A controller according to Clause 1, wherein the first receptacle comprises a first connector that is communically coupled to a second connector of the first grip; and the second receptacle comprises a third connector that is communically coupled to a fourth connector of the second grip.

[0103] 7. A controller according to Clause 1, characterized in that the first receptacle is concave into the rear portion of the controller body; or the second receptacle is concave into the rear portion of the controller body.

[0104] 8. A controller comprising: a controller body including a rear portion; a compartment disposed in the rear portion of the controller body; one or more switches disposed within the compartment; and a cover configured to be coupled to the rear portion of the controller body and disposed over the compartment when coupled to the rear portion, wherein the cover is replaceable with one or more additional covers to change the function of the controller.

[0105] 9. In Clause 8, the cover comprises one or more operable areas that engage one or more switches when pressed.

[0106] 10. A controller according to Clause 8, wherein one or more switches comprise at least one of a tactile switch or a force-sensing resistor.

[0107] 11. A controller according to Clause 8, wherein the cover is configured to be coupled to the rear portion of the controller body between the left handle portion and the right handle portion of the controller body.

[0108] 12. A controller according to Clause 8, wherein the controller body comprises a first attachment mechanism and the cover comprises a second attachment mechanism, and the engagement between the first attachment mechanism and the second attachment mechanism connects the cover to the controller body.

[0109] 13. In Clause 8, one or more additional covers include: a first cover that prevents one or more switches from engaging when the cover is pressed; or at least one of a second cover comprising at least one of a battery or a haptic actuator, a controller.

[0110] 14. A controller system comprising: one or more processors; and a controller, wherein the controller comprises: a controller body; a trackpad configured to provide touch data indicating a touch input to one or more processors; a switch configured to provide selection data indicating pressure on the trackpad to one or more processors, at least a portion of which is located below the trackpad; and a rotary dial mechanism configured to adjust the amount of pressure required for the switch to detect pressure, at least a portion of which is disposed below the trackpad.

[0111] 15. In Clause 14, the trackpad is positioned at the front of the controller body, in a controller system.

[0112] 16. In Clause 14, the rotary dial mechanism comprises a frame having one or more channels; a central dial; and one or more arms extending from the central dial and disposed within one or more channels, a controller system.

[0113] 17. A controller system in which, in accordance with Clause 16, individual channels of one or more channels comprise a first end and a second end; and individual arms of one or more arms are moved between the first end and the second end within corresponding channels among the individual channels to adjust the amount of force required for a switch to detect pressure.

[0114] 18. A controller system according to Clause 16, comprising a channel disposed through a front surface cover of a controller body; further comprising a knob disposed within the channel and operably coupled to a rotary dial mechanism, wherein the knob is movable within the channel to adjust the amount of force required for a switch to detect pressure.

[0115] 19. A controller system in which, in Clause 14, the amount of force is adjustable between a first amount of force required for the switch to detect pressure and a second amount of force required for the switch to detect pressure.

[0116] 20. A controller body having a front surface; and a controller comprising a speaker present on the front surface of the controller body and operable to change the audio characteristics of an application being executed.

[0117] 21. In Clause 20, the speaker is a first speaker, and the controller further comprises a second speaker present on the front surface of the controller body, wherein the second speaker is operable to change the audio characteristics of the application being executed or additional audio characteristics.

[0118] 22. A controller according to Clause 21, wherein the first speaker is located on the first side of the controller body; and the second speaker is located on the second side of the controller body.

[0119] 23. The controller of Clause 20 further comprises a control device existing on the front surface of the controller body, wherein the control device is configured to provide touch data representing a touch input to one or more processors, and the touch data is an additional audio characteristic of an application in execution.

[0120] 24. A controller further comprising a non-transient computer-readable medium storing instructions that, when executed by one or more processors in Clause 23, cause one or more processors to determine that touch data has been received within a threshold time after detecting the operation of the speaker; and, at least partially based on the determination, cause audio characteristics to be changed.

[0121] 25. In Clause 23, the speaker is operable by the user's first thumb; and the control device is a controller operable by the user's second thumb.

[0122] 26. In Clause 20, the audio characteristics include volume increase; volume decrease; volume mute; or volume unmute, a controller.

[0123] Unless otherwise indicated, all numbers representing quantities, characteristics, and conditions, etc. used in the specification and claims shall be understood in all cases to be modified by the term “about.” Accordingly, unless otherwise indicated, numerical parameters described in the specification and appended claims are approximations that may vary depending on the desired characteristics sought to be obtained by the present disclosure. At a minimum, each numerical parameter shall be interpreted in light of at least the number of reported significant figures and by applying ordinary rounding techniques, not in an attempt to limit the application of the principle of equivalence to the scope of the claims. Where further clarification is required, the term “about” has the meaning that a person skilled in the art would reasonably assign to it when used with a mentioned numerical value or range, namely, a somewhat greater or lesser than the mentioned value or range, ±20% of the mentioned value; ±19% of the mentioned value; ±18% of the mentioned value; ±17% of the mentioned value; ±16% of the mentioned value; ±15% of the mentioned value; ±14% of the mentioned value; ±13% of the mentioned value; Indicates within the range of ±12% of the mentioned value; ±11% of the mentioned value; ±10% of the mentioned value; ±9% of the mentioned value; ±8% of the mentioned value; ±7% of the mentioned value; ±6% of the mentioned value; ±5% of the mentioned value; ±4% of the mentioned value; ±3% of the mentioned value; ±2% of the mentioned value; or ±1% of the mentioned value.

[0124] Although various embodiments and practices are described individually herein, embodiments and practices may be combined, rearranged, and modified to arrive at other variations within the scope of this disclosure. Furthermore, it should be understood that while the subject matter has been described in expressions specific to structural features and / or methodological conduct, the subject matter defined in the appended claims is not necessarily limited to the specific features or conduct described. Rather, specific features and conduct are disclosed as exemplary forms embodying the claims.

Claims

Claim 1 A controller system comprising: one or more processors; a controller—the controller comprises: a controller body having a front surface; a first speaker disposed on the front surface and within the left half of the front surface; a first sensor associated with the first speaker and configured to detect finger contact on the first speaker—the first sensor comprises at least one of a first speaker coil of the first speaker; or a first inductive sensor coupled to the first speaker coil—; a second speaker disposed on the front surface and within the right half of the front surface; and a second sensor associated with the second speaker and configured to detect finger contact on the second speaker—the second sensor comprises at least one of a second speaker coil of the second speaker; or a second inductive sensor coupled to the second speaker coil—; A controller system comprising a non-transient computer-readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to receive inductance data representing a change in inductance based on a finger moving in proximity to at least one of the first speaker coil or the second speaker coil from at least one of the first sensor or the second sensor; and to perform acts including adjusting the volume of audio content being output by the first speaker and the second speaker based at least partially on the inductance data. Claim 2 A controller system according to claim 1, characterized in that the inductance data is received from the second sensor; and adjusting the volume includes increasing the volume; or the inductance data is received from the first sensor; and adjusting the volume includes decreasing the volume. Claim 3 A method comprising the steps of: receiving inductance data from a sensor associated with a speaker disposed on a controller body of a controller by a processor, wherein the sensor comprises at least one of a speaker coil of the speaker or an inductive sensor coupled to the speaker coil, and the inductance data represents a change in inductance based on a finger moving in close proximity to the speaker coil; and adjusting the characteristics of audio content being output by the speaker by the processor at least partially based on the inductance data. Claim 4 A method according to paragraph 3, wherein the step of adjusting the characteristics of the audio content comprises at least one of the steps of: increasing the volume of the audio content; lowering the volume; muting the volume; or unmuting the volume. Claim 5 In paragraph 3, the speaker is the first speaker of a pair of speakers disposed on the front surface of the controller body, and the first speaker is disposed within the right half of the front surface; the step of adjusting the characteristics of the audio content includes the step of increasing the volume of the audio content. Claim 6 A controller system comprising: one or more processors; a controller—the controller comprises: a controller body; a speaker disposed on the controller body; and a sensor associated with the speaker and configured to detect finger contact on the speaker, wherein the sensor comprises at least one of a speaker coil of the speaker; or an inductive sensor coupled to the speaker coil—; and a non-transient computer-readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to receive from the sensor inductance data representing a change in inductance based on the movement of a finger in proximity to the speaker coil; and cause the characteristics of audio content being output by the speaker to be adjusted at least partially based on the inductance data. Claim 7 In claim 6, the speaker comprises a first speaker disposed on the front surface of the controller body and within the left half of the front surface, the sensor comprises a first sensor, the controller further comprises a second speaker disposed on the front surface and within the right half of the front surface; and a second sensor associated with the second speaker and configured to detect finger contact on the second speaker, wherein adjusting the characteristics of the audio content includes reducing the volume of the audio content. Claim 8 A controller system according to claim 7, wherein the second sensor comprises at least one of a second speaker coil of the second speaker; or a second inductive sensor coupled to the second speaker coil. Claim 9 In claim 6, the speaker comprises a first speaker disposed on the front surface of the controller body and within the right half of the front surface; the sensor comprises a first sensor; the controller further comprises a second speaker disposed on the front surface and within the left half of the front surface; and a second sensor associated with the second speaker and configured to detect finger contact on the second speaker; and the controller system comprising increasing the volume of the audio content to adjust the characteristics of the audio content. Claim 10 In claim 9, the controller system comprises at least one of the second sensor, the second speaker coil of the second speaker; or a second inductive sensor coupled to the second speaker coil. Claim 11 A controller system according to claim 6, wherein adjusting the characteristics of the audio content comprises at least one of increasing the volume of the audio content; lowering the volume; muting the volume; or unmuting the volume. Claim 12 In paragraph 6, the inductive sensor is a controller system that is part of the amplifier of the speaker. Claim 13 In claim 6, the above operations further include determining that an inductance value detected by the sensor satisfies a threshold value based at least partially on the inductance data; a controller system in which the characteristics of the audio content are adjusted based on the inductance value satisfying the threshold value. Claim 14 In claim 6, the speaker comprises a first speaker, and the sensor comprises a first sensor; the inductance data is the first inductance data; the finger is the first finger; the controller further comprises a second speaker disposed on the controller body; and a second sensor associated with the second speaker and configured to detect finger contact on the second speaker—the second sensor comprises at least one of a second speaker coil of the second speaker; or a second inductive sensor coupled to the second speaker coil—and the acts are receiving second inductance data from the second sensor, which indicates a change in inductance based on the second finger moving in close proximity to the second speaker coil; and further comprising determining, based at least partially on the first inductance data and the second inductance data, that the first finger is in contact with the first speaker substantially simultaneously with the second finger being in contact with the second speaker; and a controller system wherein adjusting the characteristics of the audio content comprises at least one of muting the volume of the audio content or unmuting the volume. Claim 15 In paragraph 3, the speaker is the first speaker among a pair of speakers disposed on the front surface of the controller body, the first speaker is disposed within the left half of the front surface, and the method of adjusting the characteristics of the audio content includes reducing the volume of the audio content. Claim 16 In paragraph 3, the method wherein the inductive sensor is part of the amplifier of the speaker. Claim 17 In paragraph 3, the method further comprises the step of determining that an inductance value detected by the sensor satisfies a threshold value based at least partially on the inductance data; and the step of adjusting the characteristics of the audio content is based on the inductance value satisfying the threshold value. Claim 18 In claim 3, the speaker comprises a first speaker and the sensor comprises a first sensor; the inductance data is the first inductance data; the finger is the first finger; the method further comprises the step of receiving, by the processor, second inductance data from a second sensor associated with a second speaker disposed on the controller body, wherein the second sensor comprises at least one of a second speaker coil of the second speaker or a second inductive sensor coupled to the second speaker coil, and the second inductance data represents a change in inductance based on the second finger moving in close proximity to the second speaker coil; and the step of determining by the processor that the first finger is in contact with the first speaker substantially simultaneously with the second finger being in contact with the second speaker, at least partially based on the first inductance data and the second inductance data, and the step of adjusting the characteristics of the audio content comprises at least one of the step of muting the volume of the audio content or the step of unmuting the volume. Claim 19 A controller system according to claim 1, characterized in that the first inductive sensor is part of the first amplifier of the first speaker, or the second inductive sensor is part of the second amplifier of the second speaker. Claim 20 In claim 1, the operations further include determining that an inductance value detected by at least one of the first sensor or the second sensor satisfies a threshold value based at least partially on the inductance data; a controller system in which adjusting the volume is based on the inductance value satisfying the threshold value.

Images