Architecture and communication protocol for haptic output devices

The embodiments are directed toward an architecture and communication protocol for controlling haptic output devices. According to the embodiments, a composite drive signal is generated that includes a first drive signal to be rendered by a first haptic output device, a second drive signal to be rendered by a second haptic output device, and a packet identifier. A controller includes the first haptic output device that is associated with a first user input element and the second haptic output device associated with a second user input element. The composite drive signal is transmitted to controller, and the execution order of the first and second drive signals is determined based on the packet identifier.

FIELD OF INVENTION

The embodiments are generally directed to electronic devices, and more particularly, to electronic devices that produce haptic effects.

BACKGROUND

Video games and video game systems have become extremely popular. Video game devices or controllers typically use visual and auditory cues to provide feedback to a user. In some interface devices, kinesthetic feedback (e.g., active and resistive force feedback) and/or tactile feedback (e.g., vibration, texture, temperature variation, and the like) may be provided to the user. In general, such feedback is collectively known as “haptic feedback” or “haptic effects.” Haptic feedback provides cues that enhance and simplify a user's interaction with a video game controller, or other electronic device. For example, haptic effects may provide cues to users of video game controllers or other electronic devices to alert the user to specific events, or provide realistic feedback to create greater sensory immersion within a simulated or virtual environment.

Other devices in which a user interacts with a user input element to cause an action also may benefit from haptic feedback or haptic effects. For example, such devices may include medical devices, automotive controls, remote controls, and other similar devices.

SUMMARY OF THE INVENTION

Embodiments of the present invention are directed toward electronic devices configured to produce haptic effects that substantially improve upon the related art.

Features and advantages of the embodiments are set forth in the description which follows, or will be apparent from the description, or may be learned by practice of the invention.

In one example embodiment, functionality for controlling haptic output devices according to an architecture and communication protocol is provided. A composite drive signal is generated that includes a first drive signal to be rendered by a first haptic output device, a second drive signal to be rendered by a second haptic output device, and a packet identifier. A controller includes the first haptic output device that is associated with a first user input element and the second haptic output device associated with a second user input element. The composite drive signal is transmitted to the controller, and the execution order of the first and second drive signals is determined based on the packet identifier.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not intended to limit the invention to the described examples.

Example embodiments are directed toward functionality for controlling haptic output devices according to an architecture and communication protocol. A composite drive signal is generated that includes a first drive signal to be rendered by a first haptic output device, a second drive signal to be rendered by a second haptic output device, and a packet identifier. A controller includes the first haptic output device that is associated with a first user input element and the second haptic output device associated with a second user input element. The composite drive signal is transmitted to the controller, and the execution order of the first and second drive signals is determined based on the packet identifier.

In the various embodiments, a variety of user interfaces and methods for using a device are described. In some embodiments, the device is a portable electronic device (e.g., a game controller, console, mobile phone, smartphone, tablet, etc.). It should be understood, however, that the user interfaces and associated methods may be applied to numerous other devices, such as personal computers, medical devices, laptops, and the like that may include one or more other physical user-interface devices, such as a keyboard, mouse, trackball and the like.

FIG. 1illustrates a block diagram of a system100according to an example embodiment of the present invention.

System100may include a communication device110configured to transmit and/or receive data from remote sources. Communication device110may enable connectivity between a processor120and other devices by encoding data to be sent from processor120to another device over a network (not shown) and decoding data received from another system over the network for processor120.

For example, communication device110may include a network interface card that is configured to provide wireless network communications. A variety of wireless communication techniques may be used including infrared, radio, Bluetooth, Wi-Fi, and/or cellular communications. Alternatively, communication device110may be configured to provide wired network connection(s), such as an Ethernet connection.

Processor120may comprise one or more general or specific purpose processors to perform computation and control functions of system100. Processor120may include a single integrated circuit, such as a micro-processing device, or may include multiple integrated circuit devices and/or circuit boards working in cooperation to accomplish the functions of processor120. In addition, processor120may execute computer programs, such as an operating system141, a communication module142, and other applications143, stored within memory140.

System100may include memory140for storing information and instructions for execution by processor120. Memory140may contain various components for retrieving, presenting, modifying, and storing data. For example, memory140may store software modules that provide functionality when executed by processor120. The modules may include operating system141that provides operating system functionality for system100. The modules may further include communication module142that is configured to control packet based communications between system100and controller150. In some instances, the packet based communications are relayed between system100and controller150over one or more USB (“Universal Serial Bus”) channels. Communication module142also interfaces with a variety of other applications143, and relays the haptic instructions originating from other applications143using one or more standard and/or proprietary communication protocols. Although USB channels are described herein as an example, the embodiments of the invention may be readily applied to other communication protocols, such as Bluetooth. Other applications143within system100may include additional functionality, such as peripheral firmware configured to provide control functionality for a peripheral device, such as controller150(e.g., a gamepad, wearable device, etc.).

Non-transitory memory140may include a variety of computer-readable media that may be accessed by processor120. In the various embodiments, memory140may include volatile and nonvolatile media, removable and non-removable media. For example, memory140may include any combination of random access memory (“RAM”), dynamic RAM (“DRAM”), static RAM (“SRAM”), read only memory (“ROM”), flash memory, cache memory, and/or any other type of non-transitory computer-readable media. Alternatively, or additionally, memory140may include one or more network or cloud accessible storage media.

Although shown as a single system, the functionality of system100may be implemented as a distributed system. For example, memory140and processor120may be distributed across multiple different computers that collectively comprise system100. In one embodiment, system100may be part of a device (e.g., personal computer, console, video game console, etc.), and system100provides haptic effect functionality for the device. In another embodiment, system100may be separate from the device, and may remotely provide the aforementioned functionality for the device.

System100may be operably connected to controller150. Controller150may be a peripheral device configured to provide input to the system100. Controller150may be operably connected to system100using either a wireless connection or a wired connection. Controller150also may include a local processor configured to communicate with system100using either a wireless connection or a wired connection. Alternatively, controller150may be configured to not include a local processor, and all input signals and/or output signals associated with controller150may be processed by the components of system100. In embodiments in which controller150has a local processor, additional functionality, such as communication modules and peripheral firmware configured to provide control functionality may reside within controller150. Here, the clock of the host device and the clock of the peripheral device may be synchronized.

Controller150may further include one or more digital buttons, one or more analog buttons, one or more bumpers, one or more directional pads, one or more analog or digital sticks, one or more driving wheels, and/or one or more user input elements that can be interacted with by a user, and that can provide input to system100. Controller150may also include one or more analog or digital trigger buttons (or “triggers”) that can further be interacted with by the user, and that can further provide input to system100. As is described below in greater detail, controller150can further include a motor, or another type of actuator or haptic output device, configured to exert a bi-directional push/pull force on at least one trigger of controller150.

Controller150can also include one or more actuators, or other types of haptic output devices. The local processor of controller150, or processor120in embodiments where controller150does not include a local processor, may transmit a haptic signal associated with a haptic effect to at least one actuator of controller150. The actuator, in turn, outputs haptic effects such as vibrotactile haptic effects, kinesthetic haptic effects, or deformation haptic effects, in response to the haptic signal. The haptic effects can be experienced at a user input element (e.g., a digital button, analog button, bumper, directional pad, analog or digital stick, driving wheel, or trigger) of controller150. Alternatively, the haptic effects can be experienced at an outer surface of controller150.

An actuator is an example of a haptic output device, where a haptic output device is a device configured to output haptic effects, such as vibrotactile haptic effects, electrostatic friction haptic effects, temperature variation, and/or deformation haptic effects, in response to a drive signal. In alternate embodiments, the one or more actuators within controller150can be replaced by some other type of haptic output device. The haptic output device may be, for example, an electric motor, an electro-magnetic actuator, a voice coil, a shape memory alloy, an electro-active polymer, a solenoid, an eccentric rotating mass motor (“ERM”), a harmonic ERM motor (“HERM”), a linear resonant actuator (“LRA”), a piezoelectric actuator, a high bandwidth actuator, an electroactive polymer (“EAP”) actuator, an electrostatic friction display, or an ultrasonic vibration generator. In some instances, the haptic output device may include haptic output drive circuit. In some embodiments, the haptic output device may be unidirectional or bidirectional.

Controller150may further include one or more speakers. The local processor of controller150, or processor120in embodiments where controller150does not include a local processor, may transmit an audio signal to at least one speaker of controller150, which in turn outputs audio effects. The speaker may be, for example, a dynamic loudspeaker, an electrodynamic loudspeaker, a piezoelectric loudspeaker, a magnetostrictive loudspeaker, an electrostatic loudspeaker, a ribbon and planar magnetic loudspeaker, a bending wave loudspeaker, a flat panel loudspeaker, a heil air motion transducer, a plasma arc speaker, and a digital loudspeaker.

Controller150can further include one or more sensors. A sensor may be configured to detect a form of energy, or other physical property, such as, but not limited to, sound, movement, acceleration, bio signals, distance, flow, force/pressure/strain/bend, humidity, linear position, orientation/inclination, radio frequency, rotary position, rotary velocity, manipulation of a switch, temperature, vibration, or visible light intensity. The sensor may further be configured to convert the detected energy, or other physical property, into an electrical signal, or any signal that represents virtual sensor information, and controller150can send the converted signal to the local processor of controller150, or processor120in embodiments where controller150does not include a local processor.

FIG. 2is a simplified block diagram illustrating a system200for providing a haptic effect according to an example embodiment of the present invention.

As shown inFIG. 2, system200includes one or more applications210. Each of applications210may generate a variety of instructions215. Instructions215are supplied to a communication driver220. Upon receiving instructions215, communication driver220may generate one or more haptic drive signals225based on instructions215. In some configurations, haptic drive signals225may be configured according to one or more report formats. Haptic drive signals225are then transmitted to a controller230.

At controller230, haptic drive signals225may be executed by one or more haptic output devices232. By executing haptic drive signals225, haptic output devices232render the haptic effects to an end user.

FIG. 3illustrates a block diagram of a haptic effect software stack300according to an example embodiment of the present invention. As shown inFIG. 3, software stack300includes device modules310, peripheral firmware modules320, controller modules330, drive modules340, and rumble drive modules350. Haptic effect software stack300is implemented on a system, such as system100ofFIG. 1.

Device modules310may include a variety of modules such as input management code311, peripheral input application programming interface (“API”)312, rumble API313, haptic effect API314, direct playback/crossover315, trigger engine316, spatialization engine317, and encoder318.

Input management code311may include a set of computer-readable instructions that manage input provided by controller330in the context of a game application, or other type of application, executed within a device.

Peripheral input API312may include a set of computer-readable functions or routines that enable game input management code311to interact with peripheral firmware320in order to receive and manage input provided by controller330.

Rumble API313may include a set of computer-readable functions or routines that enable input management code311to interact with peripheral firmware320in order to transmit rumble instructions to one or more rumble motors or rumble actuators of controller330(e.g., rumble motors L and R ofFIG. 3). In addition, a rumble instruction may cause a rumble motor or rumble actuator of controller330to produce a general or rumble haptic effect.

Haptic effect API314(identified inFIG. 3as “API”) may include a set of computer-readable functions or routines that are accessible to input management code311, and that enable input management code311to interact with peripheral firmware320in order to transmit haptic instructions to controller330. In addition, a haptic instruction may cause one or more targeted motors or targeted actuators of controller330to produce a haptic effect at one or more user input elements of controller330.

Haptic effect API314also may store one or more haptic effect definitions. A haptic effect definition is a data structure that includes haptic data, such as a haptic signal, that is pre-defined and that can be stored within a storage, such as a haptic file or haptic stream, and that can be sent to one or more rumble motors, rumble actuators, targeted motors, or targeted actuators, to produce a haptic effect at a component, or user input element, of controller330. The haptic data can include one or more attributes of the corresponding haptic effect, where the attributes can be stored as parameters. Example parameters of a haptic effect definition may include an amplitude parameter, a frequency parameter, a waveform parameter, an envelope parameter, a magnitude (or strength) parameter, and a duration parameter.

Haptic effect API314may enable game input management code311to interact with direct playback/crossover315, trigger engine316, and spatialization engine317, and may further manage direct playback/crossover315, trigger engine316, and spatialization engine317according to requests invoked by game input management code311. Further, haptic effect API314may store data used for communication with peripheral firmware320, and used for generation of one or more haptic effects.

Direct playback/crossover315may receive haptic data as input, produce haptic data as output, and transmit haptic data to one or more targeted motors, or targeted actuators, of controller330(e.g., motors L and R ofFIG. 3). In some embodiments, direct playback/crossover315may output the input haptic data directly, without modifying a format of the input haptic data. This results in an “as-is” playback of the input haptic data. In other embodiments, direct playback/crossover315may convert the haptic data that is input from a first format to a second format, and can further output the converted haptic data. Depending on the type of playback, direct playback/crossover315may optionally use a programmable crossover to convert the haptic data. By converting the haptic data, device modules may deconstruct the haptic effect and playback the haptic effect at multiple actuators.

The format of the haptic data may be a haptic elementary stream (“HES”) format. A HES format is a file or data format for representing haptic data that may be streamed to a device. The haptic data can be represented in a manner that is identical or similar to how uncompressed sound is represented, although the haptic data can be encrypted within the HES format.

Trigger engine316may receive haptic data, such as a haptic effect definition, and may modify the haptic data based on user input data, such as trigger data323. Trigger data is data that includes one or more parameters that indicate a position and/or range of one or more triggers of controller330(e.g., triggers L and R ofFIG. 3). Trigger engine316may further transmit haptic instructions to controller330. For example, trigger engine316may transmit haptic instructions to a variety of user-input elements of controller330. As previously described, a haptic instruction may cause one or more targeted motors or targeted actuators of controller330to produce a haptic effect at one or more user-input elements of controller330.

Spatialization engine317may receive haptic data and may modify the haptic data based on spatialization data. Spatialization data may include data that indicates a desired direction and/or flow of a haptic effect, such as an ordering of haptic effects on respective user input elements. In certain embodiments, spatialization engine317may receive spatialization data that includes a direction and/or flow from input management code311.

Spatialization engine317may modify the haptic data so that a haptic effect, such as a trigger haptic effect, is scaled for one or more rumble motors, or rumble actuators, of controller330(e.g., rumble motors L and R ofFIG. 3), and that the haptic effect is also scaled for one or more targeted motors, or targeted actuators, of controller330(e.g., motors L and R, as illustrated inFIG. 3). In other words, spatialization engine317may modify the haptic data that is sent to each motor or actuator, and thus, modify the haptic effect that is experienced at each motor or actuator, in order to convey a sense of direction and flow of an overall haptic effect. For example, in order to emphasize a haptic effect experienced at a motor or actuator, spatialization engine317may scale one or more portions of the haptic effect. For example, spatialization engine317may scale haptic data that is sent to the motor or actuator that causes the haptic effect to be experienced, causing the haptic effect to be more pronounced (e.g., increased magnitude, duration, etc.). Additionally, spatialization engine317may scale haptic data that is sent to other motors or actuators, causing other haptic effects that are experienced at those motors or actuators to be less pronounced (e.g., decreased magnitude, duration, etc.). In some embodiments, spatialization engine317may modify the haptic data in real-time or substantially in real time. Further, in some embodiments, spatialization engine317may have non-linear relationships between inputs and motor, or actuator, outputs in order to exaggerate an overall haptic effect.

Encoder318encodes haptic data received from direct playback/crossover315, trigger engine316, and/or spatialization engine317into a format. In one embodiment, the format may be an HES format. Encoder318may transmit the encoded haptic data to peripheral firmware320.

Peripheral firmware320is firmware for one or more peripheral devices (e.g., controllers). Peripheral firmware320may include a variety of modules such as decoder and crossover321, trigger control322, trigger data323, other functions324, and rumble control325.

Decoder and crossover321may receive the encoded haptic data from encoder318and decodes the encoded haptic data. In some embodiments, decoder and crossover321computes a programmable crossover in order to decode the encoded haptic data. Decoder and crossover321may compute the programmable crossover in real-time.

Trigger control322is a low-level control API for one or more targeted motors or targeted actuators of controller330(e.g., motors L and R ofFIG. 3). Trigger control322may receive a trigger instruction and may convert the trigger instruction into a low-level trigger instruction for a specified targeted motor or targeted actuator of controller330, and may transmit the low-level trigger instruction to the specified targeted motor or targeted actuator of controller330. The low-level trigger instruction may cause the specified targeted motor or targeted actuator to produce a trigger haptic effect at a specified trigger of controller330.

Trigger data323, as previously described, is data that includes one or more parameters that indicate a position and/or range of one or more triggers of controller330(e.g., triggers L and R ofFIG. 3). Trigger data323may be received from controller330by peripheral firmware320. Peripheral firmware320may further store trigger data323, and may further transmit trigger data323to device modules310.

Other gamepad functions324may be functions of controller330managed by peripheral firmware320. Such functions may include such functions as wired/wireless communications, input reporting, protocol implementation, power management, etc.

Rumble control325is a low-level control API for one or more rumble motors or rumble actuators of controller330(e.g., rumble motors L and R ofFIG. 3). Rumble control325may receive a rumble instruction, may convert the rumble instruction into a low-level rumble instruction for a specified rumble motor or rumble actuator of controller330, and may transmit the low-level trigger instruction to the specified rumble motor or rumble actuator of controller330.

Communication driver module326is a firmware module that is configured to control packet based communications between device modules310and controller330. For example, the packet based communications may be relayed between device modules310and controller330over one or more USB channels. Upon receiving instructions from device modules310, communication driver module326may generate one or more haptic drive signals. In some configurations, the haptic drive signals are generated according to one or more report formats.

Communication driver module326may include multiple sections of firmware that may be hardware dependent or independent. In some instances, sections of firmware that are hardware independent may be separated from the sections that are hardware dependent. Here, hardware independent firmware may interact with the hardware dependent firmware by using functional pointers.

Controller330may include triggers L and R. Controller330may further include gear boxes L and R and motors L and R. Motor L and gearbox L are operably coupled to trigger L within controller330. Likewise, motor R and gearbox R are operably coupled to trigger R within controller330. When motor L receives a trigger instruction, motor L and gearbox L may collectively cause a trigger haptic effect to be experienced at trigger L. Likewise, when motor R receives a trigger instruction, motor R and gearbox R may collectively cause a trigger haptic effect to be experienced at trigger R. Peripheral firmware320may send trigger instructions to motors L and R of controller330using drive electronics340.

Controller330may further include potentiometers L and R. Potentiometer L may detect a position and/or range of trigger L, and may further send the detected position and/or range of trigger L to peripheral firmware320as trigger data. Likewise, potentiometer R may detect a position and/or range of trigger R, and may further send the detected position and/or range of trigger R to peripheral firmware320as trigger data.

Controller330may further include rumble motors L and R. When rumble motor L receives a rumble instruction, rumble motor L causes a haptic effect to be experienced along a left component of controller330. Likewise, when rumble motor R receives a rumble instruction, rumble motor R causes a haptic effect to be experienced along a right component of controller330. Peripheral firmware320may send rumble instructions to rumble motors L and R using rumble drive electronics350.

FIG. 4is a simplified block diagram illustrating a system400for controlling haptic communications according to an example embodiment of the present invention.

As an input to system400, one or more applications410may generate a variety of haptic instructions. In some instances, the haptic instructions may be retrieved from a haptic effect library415. The haptic instructions may be parsed, mixed, and converted to packetized haptic drive signals suitable for transmission on a USB compliant channel by the various components of system400.

A haptic engine420is a higher level API (“Application Programming Interface”) that uses lower level API functions to manage the haptic effect instructions originating from applications410. For example, haptic engine420may be configured to load, start, stop, modify, and/or render the playback of the haptic effects.

Haptic engine420interfaces with haptic effect parser430. As its name implies, haptic effect parser430is configured to parse haptic effect instructions into segments defining their operational characteristics. In some instances, haptic effect parser430also may retrieve additional operational characteristics from memory (e.g., haptic effect library415). Alternatively, or additionally, haptic effect parser430includes an API to load the haptic effects in memory, verify haptic effect formats, and retrieve a variety of information relating to the haptic effects, such as packet size, effect duration, and other haptic effect data.

Haptic engine420also interfaces with a haptic mixer440. At haptic mixer440, haptic instructions intended for different haptic output devices may be combined into a single haptic instruction set. By implementing haptic mixer440, system400may simultaneously playback multiple haptic effects at different haptic output devices. Here, start and/or stop times for the various haptic effects may be adjusted and/or determined. In addition, haptic mixer440may manage the contents of a mixer buffer (not shown).

Haptic engine420further interfaces with a haptic device handler450. Haptic device handler450initiates and manages communication with the haptic output devices. For example, haptic device handler450is configured to retrieve individual haptic output device handlers (e.g., identifiers). Accordingly, haptic device handler450may render haptic effects at the various haptic output devices of system400. In some instances, haptic device handler450also initializes several state machine structures utilized to render the haptic effects.

Further, haptic device handler450interfaces with the USB communication layers, including haptic report handler460and USB HID (“Human Interface Device”) library470. Haptic report handler460packages the haptic instructions originating from applications410into packetized data suitable for transmission on a USB channel. And, USB HID library470stores a variety of functions used to facilitate USB communications. For example, USB HID library470stores functions to encode and decode the haptic instructions. In another example, USB HID library470stores USB descriptors and functions to handle the USB communication.

By utilizing the various components of system400, including components420-470, USB compliant communications between the controller (such as controller230ofFIG. 2) and application410may be achieved. Between the controller and application410, additional layers such as gamepad firmware480and controller input reader490may be used. For example, controller input reader490reports the state of the user input elements of the controller to applications410.

FIG. 5illustrates a flow diagram of functionality for driving a plurality of haptic output devices according to an example embodiment of the present invention. In some configurations, the functionality of the flow diagram ofFIG. 5(andFIG. 6below) may be implemented by software stored in memory or other computer readable or tangible media, and executed by a processor. In other embodiments, the functionality may be performed by hardware (e.g., through the use of an application specific integrated circuit (“ASIC”), a programmable gate array (“PGA”), a field programmable gate array (“FPGA”), etc.), or any combination of hardware and software.

At the outset, functionality500generates a composite drive signal that includes a first drive signal to be rendered by a first haptic output device, a second drive signal to be rendered by a second haptic output device, and a packet identifier, at510. Here, the first haptic output device may be associated with a first user input element and the second haptic output device may be associated with a second user input element. Next, at520, the composite drive signal is transmitted to a controller having the first and second haptic output devices. Lastly, the execution order of the first and second drive signals is determined based on the packet identifier,530.

FIG. 6illustrates a flow diagram of functionality600for mapping positions of a user input element with expected input signals according to an example embodiment of the present invention.

At the outset, the user input elements of the controller may be initialized, at610. Here, functionality600may initially set position and range information for the user input elements. In some instances, these values may be calculated based on the movement of the user input device from the maximum out position to the grounding position.

Next, functionality600determines and stores profiles for the user input elements, at620. The determined profiles may map each position of the user input device to an analog to digital conversion (“ADC”) value. For example, the determined profiles of620may map each position of the user input device to an ADC value between 0 and 255.

The determined profiles may utilize either an increasing or a decreasing profile. For example, an increasing profile will produce a value [0,255] when the position of the user input value is read from an 8 bit ADC data. Similarly, a decreasing profile will produce a value [255,0] when read from the 8 bit ADC data.

Subsequently, at630, functionality600determines and stores an expected input signal for each position of the user input device. In some instances, ranges of user input values may be associated with expected input signals.

In some instances, the resting position of the user input elements may vary at different times. For example, after use of the various user input devices, some of the user input devices may not return to the same resting position when the user interaction is removed. In such instances, functionality600may adjust the determined profile and expected user input values for such user input elements, at640. Accordingly, the changed resting position(s) may be accounted for while monitoring the position of the user input elements.

FIG. 7illustrates an example haptic stream report700sent from a host device to a controller according to an example embodiment to the present invention. Within haptic stream report700, a report identifier710may be associated with a timer identifier720, and haptic drive packets730. Haptic drive packets may include a predetermined number of bytes (e.g., 25 bytes) allocated to each of the haptic output devices (e.g., left rumble, right rumble, left trigger, right trigger, etc.). The overall length of haptic stream report700may be indicated by number of bytes identifier740.

Within haptic drive packets730, a force value may be modified and/or applied to each haptic output device when the haptic stream report is updated (e.g., periodically every 5ms). For example, if the host device receives a request to play a new haptic effect, it may retrieve haptic effect data from memory, and populate haptic stream report700with force values to be applied on multiple haptic output devices for an upcoming 70ms (e.g., 14 force values per actuator yields 14*5ms). Here, timer identifier720such as start tick value, at byte offset 2, may be used to synchronize haptic instructions by ensuring their storage at the correct locations within the drive buffers of the haptic output devices.

In the various configurations, the semantics and the range of force values may depend on the haptic output device and its directionality. For example, two types of haptic output devices include trigger and rumble actuators. Trigger actuators are typically bidirectional and are configured to respond to push and pull motions. By contrast, rumble actuators may be bidirectional or unidirectional. The range of force values for both rumble and trigger actuators may be the same (e.g., 0x00 and 0xFF). However, the haptic output devices may utilize range of force values differently based on their respective characteristics.

For the trigger actuators example, the force values in the range [0,127] may move the trigger actuators in a pull direction. Here, the strength of the pull may decrease as the force value increases. The force value of 128 may not push or pull the trigger actuators. And, the force values in the range [129,255] may move the trigger actuators in a push direction. Here, the strength of the push increases as the force value increases.

In another example, for unidirectional rumble actuators, the force values in the range [0,127] may be ignored. The force value of 128 may not move the unidirectional rumble actuator, and the force value in the range [129,255] may move the unidirectional rumble actuator in the clockwise direction with speed increasing as the force value increases.

In yet another example, for bidirectional rumble actuators, the force values in the range [0,127] may move the actuators in the counter-clockwise direction. The force value of 128 may not move the actuator. The force values in the range [129,255] may move the actuators in the clockwise direction with speed increasing as the force value increases.

Thus, haptic stream report700provides an example composite drive signal. In this example configuration, drive signals for a plurality of haptic output devices may be simultaneously supplied to the controller within one reporting structure (e.g.,700). In turn, the controller may determine the execution (or execution order) for the plurality of haptic output devices based on the various fields within haptic stream report700, such report identifier710, timer identifier720, and haptic drive packets730.

FIG. 8illustrates an example haptic stream report800sent from a controller to a host device according to an example embodiment to the present invention. Haptic stream report800may communicate information about the positions of the user input elements associated with the haptic output devices. For example, haptic stream report800may store data for six potentiometer values, of 1 byte each, to convey the trigger and joystick positions. Example haptic stream report800can store and report up to sixteen buttons allocating 1 bit for every button state.

FIG. 9illustrates an example capability report900sent from a controller to a host device according to an example embodiment to the present invention. Capability report900may communicate controller capabilities, such as the number of haptic output devices, the haptic device update rates, and the buffer identifiers allocated to each haptic output device. In addition, capability report900may further identify communication protocols and/or firmware supported by the controller.

FIG. 10illustrates an example status request report1000sent from a host device to a controller according to an example embodiment to the present invention. For example, the host device may check the status of the most recent USB packet or command. In response to status request report1000, the controller may report that the command is valid, invalid, unsupported, and the like.

FIG. 11illustrates an example configuration change report1100sent from a host device to a controller according to an example embodiment to the present invention. Using configuration change report, the controller may request changes to the firmware settings of the host device. For example, configuration change report1100may be used to change the haptic output device update rate.

Each of the reports800-1100ofFIGS. 8-11illustrates an additional example composite signal. In each of these examples, the positions, capabilities, status, and configuration of multiple user input elements and haptic output devices may be simultaneously communicated between the host device and the controller. In each of reports800-1100, various identifiers, such as report, command, module, parameter, and other identifiers may be used.

FIG. 12illustrates a functional block diagram of a controller1200suitable for use with the embodiments of the present invention.

As illustrated inFIG. 12, controller1200may include one or more of a variety of user input elements. A user input element may refer to any interface device manipulated by the user to interact with host computer1204. Example user input elements include analog or digital joy stick1210, button1214, trigger1218, and the like. As understood by one of ordinary skill in the art, one or more of each user input element may be included on controller1200. For example, the present description of trigger1218does not limit controller1200to a single trigger. Similarly, those skilled in the art understand that multiple analog or digital sticks, buttons, and other user input elements may be used.

Controller1200may include local processor1208. Local processor1208may exchange commands and data with host computer1204via connection1205. Connection1205may be a wired or wireless connection using one or more communication protocols known to those skilled in the art. In some instances, controller1200may be alternatively configured to not include local processor1208. Here, input/output signals from controller1200may be handled and processed directly by host computer1204. Host computer1204may be a gaming device console and display device1206may be screen which is operably coupled to the gaming device console. In some instances, host computer1204and display device1206may be combined into a single device.

Controller1200may include targeted actuators1212,1216,1220(e.g., motors) to directly drive each of the user input elements thereof as well as one or more general or rumble actuators1222,1224operably coupled to housing1202in a location where a hand of the user is generally located. More particularly, analog or digital stick1210includes a targeted actuator or motor1212operably coupled thereto, button1214includes a targeted actuator or motor1216operably coupled thereto, and trigger1218includes a targeted actuator or motor1220operably coupled thereto. In addition to a plurality of targeted actuators, controller1200includes a position sensor operably coupled to each of the user input elements thereof. More particularly, analog or digital stick1210includes a position sensor1211operably coupled thereto, button1214includes a position sensor1215operably coupled thereto, and trigger1218includes a position sensor1219operably coupled thereto. Local processor1208is operably coupled to targeted actuators1212,1216,1220as well as position sensors1211,1215,1219of analog or digital stick1210, button1214, and trigger1218, respectively. In response to signals received from position sensors1211,1215,1219, local processor1208instructs targeted actuators1212,1216,1220to provide directed or targeted kinesthetic effects directly to analog or digital stick1210, button1214, and trigger1218, respectively. Such targeted kinesthetic effects are discernible or distinguishable from general or rumble haptic effects produced by general actuators1222,1224along the entire body of the controller. The collective haptic effects provide the user with a greater sense of immersion to the game as multiple modalities are being simultaneously engaged (e.g., video, audio, and haptics).

FIGS. 13A and 13Billustrate different views of a controller1300suitable for use with the embodiments of the present invention. As shown inFIGS. 13AandFIG. 13B, controller1300may include a variety of components such as housing1302, analog or digital joy stick1310, button(s)1314, trigger1318, and rumble actuators1322and1324.

Housing1302is shaped to easily accommodate user gripping of controller900. Controller1300is an example embodiment of a controller, and the embodiments of the invention may be readily applied to other controller shapes.

Accordingly, the embodiments of the present invention provide an improved architecture and communication protocol for the haptic output devices. By implementing the various embodiments, drive signals for multiple haptic output devices may be simultaneously communicated and executed.