NOVELTY VEHICLE SIMULATION SYSTEMS

Abstract

Novelty vehicle simulation systems including computing devices, including processors configured to execute processor executable instructions and computer readable media encoded with processor executable instructions for executing novelty vehicle simulators on the computing devices, and supports defining vehicular appearances. In some examples, supports may be configured to seat computing devices and include vehicular appearance signifying mechanisms configured to communicate encoded representations of the vehicular appearances. In some examples, computing device include vehicular appearance sensing mechanisms operatively paired with the vehicular appearance signifying mechanisms to detect the encoded representations of the vehicular appearances of the supports. In some examples, the computer readable media include processor executable instructions for translating the encoded representation of the vehicular appearances of the support to produce vehicle parameter sets corresponding to the vehicles reflected by the vehicular appearances of the supports and modifying operating parameters of the novelty vehicle simulators according to the vehicle parameter sets.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application, Ser. No. 61542287, filed on Oct. 3, 2011, which is hereby incorporated by reference for all purposes.

BACKGROUND

The present disclosure relates generally to novelty vehicle simulation systems. In particular, novelty vehicle simulation systems including supports paired with computing devices are described.

Many known novelty vehicles are not entirely satisfactory for the range of applications in which they are employed. For example, many existing novelty vehicles lack sufficient interactive features, and further lack any meaningful simulation of the operation of the corresponding vehicle. This lack of interactivity hampers the lasting entertainment value of such toys, as users may quickly become bored after exhausting use of the skimp features available on many existing devices. In particular, many toys, including novelty vehicles, lack any type of electronic interface through which a graphical representation of a virtual interior such vehicles may be displayed.

Further, while many existing interactive toys may augment their functionality with some interactive features, tidy often lack any meaningful way to augment or adjust the interactive features after production. This limits their useful lives, as users may soon become bored with the initial, static set of features. Further, many of these interactive features lack the entertainment value provided by a graphical display.

Some known devices are configured to combine computing devices to augment three dimensional supports to provide interactive features. These devices, however, have not been adapted to visually or audibly simulate vehicles, including while being positioned within a vehicle-shaped support to provide a virtual interior of that vehicle. Further, many such systems often lack automatic pairing means and are often configured to manually pair with one single support design rather than adapt the corresponding computing devices to be paired with a varied collection of support designs. Indeed, many such systems provide no means to adapt the computing systems operation to particular automatically paired support. Rather, many systems include an application with a static mode of operation that is substantially identical regardless of the existence or design of a paired support.

As a result, there exists a need for novelty vehicle simulators that address the needs described above.

SUMMARY

The present disclosure is directed to novelty vehicle simulation systems including computing devices, including processors configured to execute processor executable instructions and computer readable media encoded with processor executable instructions for executing novelty vehicle simulators on the computing devices, and supports defining vehicular appearances. In some examples, supports may be configured to seat computing devices and include vehicular appearance signifying mechanisms configured to communicate encoded representations of the vehicular appearances. In some examples, computing device include vehicular appearance sensing mechanisms operatively paired with the vehicular appearance signifying mechanisms to detect the encoded representations of the vehicular appearances of the supports. In some examples, the computer readable media include processor executable instructions for translating the encoded representation of the vehicular appearances of the support to produce vehicle parameter sets corresponding to the vehicles reflected by the vehicular appearances of the supports and modifying operating parameters of the novelty vehicle simulators according to the vehicle parameter sets.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a schematic view of an example of a programmable computing device.

FIG. 2 shows a schematic view of an example of a mobile electronic device.

FIG. 3 illustrates a perspective view of an example of a novelty vehicle simulation system.

FIG. 4 is a rear elevation view of the example of the novelty vehicle simulation system illustrated in FIG. 3.

FIG. 5 illustrates a flowchart that illustrates modes of operation of a novelty vehicle simulator executed as a feature of the novelty vehicle simulation system illustrated in FIG. 3.

FIG. 6 is a top view of the novelty vehicle simulation system shown in FIG. 3 depicting a close-up of an example visual output of the computing device operating in a touchscreen-driven simulation mode.

FIG. 7 is a top view of the novelty vehicle simulation system shown in FIG. 3 depicting a close-up of an example visual output of the computing device operating in a support-driven simulation mode.

FIG. 8 illustrates a top view of the novelty vehicle simulation system shown in FIG. 3 depicting an example visual output of the computing device operating; in a support-driven simulation mode and in phantom lines illustrates two examples of modifications of the visual output produced in response to user manipulation.

FIG. 9 illustrates a second example of a novelty vehicle simulation system.

DETAILED DESCRIPTION

The disclosed novelty vehicle simulation systems will become better understood through review of the following detailed description in conjunction with the figures. The detailed description and figures provide merely examples of the various inventions described herein. Those skilled in the art will understand that the disclosed examples may be varied, modified, and altered without departing from the scope of the inventions described herein. Many variations are contemplated for different applications and design considerations; however, for the sake of brevity, each and every contemplated variation is not individually described in the following detailed description.

Throughout the following detailed description, examples of various novelty vehicle simulation systems are provided. Related features in the examples may be identical, similar, or dissimilar in different examples. For the sake of brevity, related features will not be redundantly explained in each example. Instead, the use of related feature names will cue the reader that the feature with a related feature name may be similar to the related feature in an example explained previously, Features specific to a given example will be described in that particular example. The reader should understand that a given feature need not be the same or similar to the specific portrayal of a related feature in any given figure or example.

Various disclosed examples may be implemented using electronic circuitry configured to perform one or more function. For example, with some embodiments of the invention, the disclosed examples may be implemented using one or more application-specific integrated circuits (ASICs). More typically, however, components of various examples of the invention will be implemented using a programmable computing device executing firmware or software instructions, or by some combination of purpose-specific electronic circuitry and firmware or software instructions executing on a programmable computing device.

Accordingly, FIG. 1 shows one illustrative example of a computing device. 101 that can be used to implement various embodiments of the invention. Computing device 101 may be incorporated within a variety of consumer electronic devices, such as personal media players, cellular phones, smart phones, personal data assistants, global positioning system devices, and the like.

As seen in this figure, computing device 101 has a computing unit 103. Computing unit 103 typically includes a processing unit 105 and a system memory 107, processing unit 105 may be any type of processing device for executing software instructions, but will conventionally be a microprocessor device. System memory 107 may include both a read-only memory (ROM) 109 and a random access memory (RAM) 111. As will be appreciated by those of ordinary skill in the art, both read-only memory (ROM) 109 and random access memory (RAM) 111 may store software instructions to be executed by processing unit 105.

Processing unit 105 and system memory 107 are connected, either directly or indirectly, through a bus 113 or alternate communication structure to one or more peripheral devices. For example, processing unit 105 or system memory 107 may be directly or indirectly connected to additional memory storage, such as a hard disk drive 117, a removable optical disk drive 119 removable magnetic disk drive 125, and a flash memory card 127. Processing unit 105 and system memory 107 also may be directly or indirectly connected to one or more input devices 121 and one or more output devices 123. Input devices 121 may include, for example, a keyboard, touch screen, a remote control pad, a pointing device (such as a mouse, touchpad, stylus, trackball, or joystick), a scanner, a camera or a microphone. Output devices 123 may include, for example, a monitor display, an integrated display, television, printer, stereo, or speakers.

Still further, computing unit 103 will be directly or indirectly connected to one or more network interfaces 115 for communicating with a network. This type of network interface 115, also sometimes referred to as a network adapter or network interface card (NIC), translates data and control signals from computing unit 103 into network messages according to one or more communication protocols, such as the Transmission Control Protocol (TCP), the Internet Protocol (IP), and the User Datagram Protocol (UDP). These protocols are well known in the art, and thus will not be discussed here in more detail. An interface 115 may employ any suitable connection agent for connecting to a network, including, for example, a wireless transceiver, a power line adapter, a modem, or an Ethernet connection.

It should be appreciated that, in addition to the input, output and storage peripheral devices specifically listed above, the computing device may be connected to a variety of other peripheral devices, including some that may perform input, output and storage functions, or some combination thereof. For example, the computing device 101 may be connected to a digital music player, such as an IPOD® brand digital music player or iOS or Android used smartphone. As known in the art, this type of digital music player can serve as both an output device for a computing device (e.g., outputting music from a sound file or pictures from an image file) and a storage device.

In addition to a digital music player, computing device 101 may be connected to or otherwise include one or more other peripheral devices, such as a telephone. The telephone may for example, a wireless “smart phone,” such as those featuring the Android or iOS operating systems. As known in the art, this type of telephone communicates through a wireless network using radio frequency transmissions. In addition to simple communication functionality, a “smart phone” may also provide a user with one or more data management functions, such as sending, receiving and viewing electronic messages (e.g., electronic mail messages, SMS text messages, etc.), recording or playing back sound files, recording or playing back image files (e.g., still picture or moving video image files), viewing and editing files with text (e.g., Microsoft Word or Excel files, or Adobe Acrobat files), etc. Because of the data management capability of this type of telephone, a user may connect the telephone with computing device 101 so that their data maintained may synchronized.

Of course, still other peripheral devices may be included with or otherwise connected to a computing device 101 of the type illustrated in FIG. 1, as is well known in the art. In some cases, a peripheral device may be permanently or semi-permanently connected to computing unit 103. For example, with many computing devices, computing unit 103, hard disk drive 117, removable optical disk drive 119 and a display are semi-permanently encased in a single housing.

Still other peripheral devices may be removably connected to computing device 101, however. Computing device 101 may include, for example, one or more communication ports through which a peripheral device can be connected to computing unit 103 (either directly or indirectly through bus 113). These communication ports may thus include a parallel bus port or a serial bus port, such as a serial bus port using the Universal Serial Bus (USB) standard or the IEEE 1394 High Speed Serial Bus standard (e.g., a Firewire port). Alternately or additionally, computing device 101 may include a wireless data “port,” such as a Bluetooth interface, a Wi-Fi interface, an infrared data port, or the like.

It should be appreciated that a computing device employed according various examples of the invention may include more components than computing device 101 illustrated in FIG. 1, fewer components than computing device 101, or a different combination of components than computing device 101. Some implementations of the invention, for example, may employ one or more computing devices that are intended to have a very specific functionality, such as a digital. music player or server computing device. These computing devices may thus omit unnecessary peripherals, such as the network interface 115, removable optical disk drive 119, printers, scanners, external hard drives, etc. Some implementations of the invention may alternately or additionally employ computing devices that are intended to be capable of a wide variety of functions, such as a desktop or laptop personal computing device. These computing devices may have any combination of peripheral devices or additional components as desired.

In many examples, computing devices may define mobile electronic devices, such as smartphones, tablet computing devices, or portable music players, often operating the iOS, Symbian, Windows-based (including Windows Mobile and Windows 8), or Android operating systems.

With reference to FIG. 2, an exemplary mobile electronic device, mobile electronic device 200, may include a processor unit 203 (e.g., CPU) configured to execute instructions and to carry out operations associated with the mobile electronic device. For example, using instructions retrieved for example from memory, the controller may control the reception and manipulation of input and output data between components of the mobile electronic device. The controller can be implemented on a single chip, multiple chips or multiple electrical components. For example, various architectures can be used for the controller, including dedicated or embedded processor, single purpose processor, controller, ASIC, etc. By way of example, the controller may include microprocessors, DSP, A/D converters, D/A converters, compression, decompression, etc.

In most cases, the controller together with an operating system operates to execute computing device code and produce and use data. The operating system may correspond to well known operating systems such iOS, Symbian, Windows-based (including Windows Mobile and Windows 8), or Android operating systems, or alternatively to special purpose operating system, such as those used for limited purpose appliance-type devices. The operating system, other computing device code and data may reside within a system memory 207 that is operatively coupled to the controller. System memory 207 generally provides a place to store computing device code and data that are used by the mobile electronic device. By way of example, system memory 207 may include read-only memory (ROM) 209, random-access memory (RAM) 211. Further, system memory 207 may retrieve data from storage units 294, which may include a hard disk drive, flash memory, etc. In conjunction with system memory 207, storage units 294 may include a removable storage device such as an optical disc player that receives and plays DVDs, or card slots for receiving mediums such as memory cards (or memory sticks).

Mobile electronic device 200 also includes input devices 221 that are operatively coupled to processor unit 203. Input devices 221 are configured to transfer data from the outside world into mobile electronic device 200. As shown, input devices 221 may correspond to both data entry mechanisms and data capture mechanisms. In particular, input devices 221 may include touch sensing devices 232 such as touch screens, touch pads and touch sensing surfaces, mechanical actuators 234 such as button or wheels or hold switches, motion sensing devices 236 such as accelerometers, location detecting devices 238 such as global positioning; satellite receivers, WiFi based location detection functionality, or cellular radio based location detection functionality, force sensing devices such as force sensitive displays and housings, image sensors, and microphones. Input devices 221 may also include a clickable display actuator.

Mobile electronic device 200 also includes various output devices 223 that are operatively coupled to processor unit 203. Output devices 233 are configured to transfer data from mobile electronic device 200 to the outside world. Output devices 233 may include a display unit 292 such as an LCD, speakers or jacks, audio/tactile feedback devices, light indicators, and the like.

Mobile electronic device 200 also includes various communication devices 246 that are operatively coupled to the controller. Communication devices 246 may, for example, include both an I/O port connection 247 that may be wired or wirelessly connected to selected I/O ports such as IR, USB, or Firewire ports, a global positioning satellite receiver 248, and a radio receiver 250 which may be configured to communicate over wireless phone and data connections. Communication devices 246 may also include a network interface 252 configured to communicate with a computing device network through various means which may include wireless connectivity to a local wireless network, a wireless data connection to a cellular data network, a wired connection to a local or wide area computing device network, or other suitable means for transmitting data over a computing device network.

Mobile electronic device 200 also includes a battery 254 and possibly a charging system. Battery 254 may be charged through a transformer and power cord or through a host device or through a docking station. In the cases of the docking station, the charging may be transmitted through electrical ports or possibly through an inductance charging means that does not require a physical electrical connection to be made.

The various aspects, features, embodiments or implementations of the invention described above can be used alone or in various combinations. The methods of this invention can be implemented software, hardware or a combination of hardware and software. The invention can also be embodied as computing device readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computing device system, including both transfer and non-transfer devices as defined above. Examples of the computer readable medium include read-only memory, random access memory, CD-ROMs, flash memory cards, DVDs, magnetic tape, optical data storage devices, and carrier waves. The computer readable medium can also be distributed over network-coupled computing device systems so that the computing device readable code is stored and executed in a distributed fashion.

With reference to FIGS. 3-8, a first example of a novelty vehicle simulation system, system 300, will now be described. As FIG. 3 illustrates, system 300 includes a support 305 and a computing device 335 defining a mobile electronic device. System 300 provides users with a toy device that is able to simulate a vehicle both audio and visually. As FIG. 3 illustrates, system 300 is designed to combine the novelty and enjoyment of an automobile model toy with a computing device's interactivity and ability to be modified with software. Computing device 335 is configured to execute software that graphically augments support 305, including its visual appearance, while adding interactive audio and visual features. By pairing support 305 with computing device 335, system 300 is able to provide users with a level of interactivity unavailable from a many existing novelty devices, thereby increasing enjoyment. This is particularly true in light of software's ability to dynamically adjust to support a variety of differing compatible supports.

This functionality is particularly useful in the vehicle context, as many children are particularly drawn to vehicle toys, likely due to being unable to operate them at their age. System 300 provides children a more complete simulation with more interactive features than many static vehicle toys provide. Through its interactivity and updatability provided by computing device 335, system 300 and other disclosed examples augment the functionality of vehicle-based toys in significant ways.

Further, system 300 is adoptable to a aide range of currently existing computing devices, such as iOS and Android-compatible smartphone handsets. By incorporating devices that users may already own, system 300 may provide the benefit of a fully functioning computer driving the electronic features of the toy without purchasing additional expensive computer hardware. In fact, users may simply need to download software from a computer network after purchasing a system-compatible support to access system 300′s electronic features. In some examples, the application managing the electronic features may easily upgraded in a similar manner to augment or adjust features.

As FIG. 3 illustrates, computing device 335 defines a mobile electronic device. Computing device 335 includes a display unit 337, a user input interface 339, an audio output device 342, and a vehicular appearance sensing mechanism. Computing device 335 further includes computer readable medium encoded with processor executable instructions for executing a novelty vehicle simulator 345 (whose output is displayed on at least FIGS. 3, 6, and 7). In some examples, computing devices may define mobile smartphone handsets, such as iOS or Android-based handsets that include some or all of the features discussed in connection with mobile electronic device 200.

Computing device 335 enables many of system 300's interactive features. As FIGS. 6 and 7 illustrate, computing device 335 is configured to execute novelty vehicle simulator 345, an upgradable software application, which adds interactivity to support 305′s design while graphically simulating a virtual interior for support 305. As will be discussed in more detail below, computing device 335 may, in some modes of operation, provide games or simulations associated with the vehicle represented by support 305. In some examples, novelty vehicle simulator 345 may be configured to ONLY provide an image configured to adapt to the surroundings defined by support 305.

As will be discussed more below, this disclosure discusses a particular example of one piece of novelty vehicle simulator software executable by computing device 335. Users may, for example, download additional or alternative software to augment or alter system 300's interactive features. For example, a user may install new novelty vehicle simulator software to perform a fire-truck or race-car based simulation that varies from the police car based simulation described in greater detail below. In some examples, new applications or upgrades to existing applications may be incorporated as a new application downloaded from a mobile marketplace or via an update feature executed within the novelty vehicle simulator. In these varied modes of operation, novelty vehicle simulator 345 may be configured to dynamically and/or automatically adapt to corresponding supports.

As FIG. 3 illustrates, display unit 337 is designed to display graphical features, including user interfaces, of novelty vehicle simulator 345. This may include graphically simulating certain features of the vehicle represented by support 305. As FIG. 3 illustrates, this may include displaying virtual interior of the vehicle reflected by support 305's vehicular appearance.

User input interface 339 includes at least two input interfaces: a touch-sensitive display 338 and a motion sensing device. Touch-sensitive display 338 is configured to detect user contact with display unit 337 and the location of that touch. This allows touch-sensitive display 338 to detect when a user has selected to manipulate user interfaces and/or other user-manipulable features produced by novelty vehicle simulator 345. Touch-sensitive display 338, in many examples, may define the capacitive- or resistive-touch sensing devices commonplace on mobile smartphone devices. As will become clear, computing device 335's motion sensing device, likewise, is configured to detect when computing device 335's position is adjusted. Computing device 335's motion sensing device may include or define a gyroscope, an accelerometer, a global-positioning system or other geographic positioning system, or other devices commonly used to detect movement on mobile electronic devices.

As FIG. 4 illustrates, audio output device 342 defines a pair of speakers positioned on the exterior of computing device 335. In this example, audio output device 342 is positioned near computing device 335's bottom, but this is not specifically required.

As FIG. 3 illustrates, support 305 defines a vehicular appearance reflecting an automobile. As FIG. 3 illustrates, support 305 further defines a support cavity 310. As FIG. 4 illustrates, support 305 further defines a pair of audio output ports 312 and a support surface 314. As FIG. 3 illustrates, support 305 is configured to retain computing device 335 in a fixed positioned seated within support 305.

As FIG. 3 illustrates, support cavity 310 partially encloses a cavity space 311 visible from positions external to support 305. As FIG. 3 shows, support cavity 310 is perimetraly sized to allow easy insertion and removal of computing device 335. In some examples, support cavities may define perimeters designed to fit common iOS or Android-based mobile phone handsets, thereby allowing the handsets to slide in and out of cavity space 311.

As FIG. 4 shows, audio output ports 312 extend from the rear of support 305 to support cavity 310. As 4 shows, audio output ports 312 are substantially aligned with audio output device 342. Audio output ports 312 are configured to increase the extent to which sounds produced by computing device 335 and output through audio output device 342 can be heard from the exterior of support 315.

Support 305 includes a vehicular appearance signifying mechanism 307 configured to communicate an encoded representation of the vehicular appearance. In particular, support 305 is configured to retain computing device 335 in a seated position detectable by computing device 335 to determine support 305's vehicular appearance. Accordingly, this position defines an encoded representation of support 305's vehicular appearance. As previously mentioned, the vehicular appearance sensing mechanism of computing device 335 may be paired with vehicular appearance signifying mechanism 307. Namely, the vehicular appearance sensing mechanism, in this context, defines computing device 335's motion sensing device and corresponding computer executable instructions that detect and interpret computing device 335's position as novelty vehicle simulator 345 is initialized. By detecting computing device 335's position, computing device 335 is able to translate support 305's encoded representation embodied in the position with which it seats computing device 335 within support cavity 310, to produce a vehicle parameter set corresponding an automobile operation. Based on this parameter set, novelty vehicle simulator 345 is able to modify its operating parameters to execute a novelty simulator that is able to perform many automobile-resembling features. Although this positional-detection scheme is discussed as one potential way to dynamically pair supports and computing devices, paired RFID transmitters and receivers, network signals, or other pairing means may be used other examples.

As FIG. 5 illustrates, novelty vehicle simulator 345 defines a set of processor executable instructions stored in a storage device 336 in data communication with computing device 335's processor. In many examples, storage device 116 may define computing device 335's hard drive; en other examples, however, storage device 336 may include, memory, cache, or other transient storage means. Some examples of novelty vehicle simulators, for example, may be retrieve from network locations prior to execution, including examples implemented as web applications or network-connected features of mobile phone applications. Further, some examples may define mobile app stored on a mobile electronic device, such as an Android or iOS app. These novelty simulation applications may store a portion of computing device executable code and data on the mobile electronic device while retrieving code or data from network sources to introduce additional or alternative novelty simulation features.

As FIGS. 6 and 7 illustrate, executing novelty vehicle simulator 345 includes displaying a user interface 342 which may, during some modes of operation, include one or more user manipulable elements. In various triodes of operation, users may manipulate one or more of these user-manipulable features to perform vehicle related actions that simulate particular features of an automobile.

As FIG. 5 illustrates, novelty vehicle simulator 345 includes at least three modes of operation: an initialization mode 347, a touchscreen-driven simulation mode 350, and a support-driven simulation mode 375.

Initialization mode 347 defines novelty vehicle simulator 345's initial mode of operation. In some examples, not vehicle simulator 345 is configured to operatively pair with support 305 to detect the encoded representation of the vehicular appearance of support 305 during initialization mode 347. Further, initialization mode 347 may include executing processor executable instructions for translating the encoded representation sensed by the vehicular appearance sensing mechanism to produce a vehicle parameter set corresponding to the vehicle reflected by the vehicular appearance of support 305.

Although the example use case illustrated in FIGS. 3-8 correspond to an example resembling an automobile, other vehicles are specifically contemplated. For example, airplanes, helicopters, and watercraft are some examples of alternative vehicles in which supports may reflect. Novelty vehicle simulator 345 may dynamically adapt to each of these vehicle examples through the vehicular appearance sensing mechanism. In some cases, it may adapt automatically when in an initialization mode.

During initialization mode 347, users are able to select between touchscreen-driven simulation mode 350 and support-driven simulation mode 375 via, for example, an onscreen menu or other similar user interface element. FIG. 6 illustrates an example state of novelty vehicle simulator 345 operating in touchscreen-driven simulation mode 350. Touchscreen-driven simulation mode 350 is accessible by selecting the appropriate option in initialization mode 347. As FIG. 6 shows, touchscreen-driven simulation mode 350 provides an example of user interface 342 incorporating a plurality of user-selectable elements relating to a virtual interior of support 305 and generated in response to detecting support 305's vehicular appearance and modifying the vehicle's operating parameters accordingly. As FIG. 6 illustrates, these user-manipulable elements resemble interior features commonly visible from an operational position within a typical automobile. In some examples, this generation of features may occur automatically.

As FIG. 6 shows, the user-manipulable elements displayed on user interface 342 in touchscreen-driven simulation mode include a steering wheel 352, a shifter 354, a dashboard. computer 356, a shotgun 358, a dashboard 360, and pedals 362. Some examples, of course, may have a substantially similar display while allowing the user to manipulate additional or alternative elements. Each of these user-manipulable elements may be manipulated by a user to allow the user to simulate the vehicle reflected by support 305 some way; in many cases this may include modifying the appearance of user interface 342 and outputting audio corresponding to the manipulated user-manipulable element. In many cases, users may manipulate user-manipulable elements by contacting the display, which contacting is detected by touch-sensitive display 338. By combining these features, novelty vehicle simulator 345, operating in touchscreen-driven simulation mode 150, provides users with an entertaining means of simulating an automobile.

Touchscreen-driven simulation mode 350 typically begins operation in an inactive mode, wherein every element is displayed in grayscale. In this inactive mode, user-manipulable elements are non-responsive to user manipulation. A user nay activate touchscreen-driven simulation mode 350 into an active state by shaking support 305. When user shakes support 305, novelty vehicle simulator 345 is configured to output to audio output device 342 a sound that resembles an automobile ignition. In certain cases, novelty vehicle simulator 345 may determine that the user did not shake support 305 sufficiently strong to activate touchscreen-driven simulation mode 350's active state, In this case, user interface 342 remains in grayscale and novelty vehicle simulator 345 outputs audio that resembles the sound of an automobile failing to turn over after ignition.

Once the main scene is loaded in an active state, each displayed user-manipulable element may be manipulated in response to user contact with the touch-sensitive display 338 proximate a selected user-manipulable element.

As FIG. 6 illustrates, touchscreen-driven simulation mode 330 illustrates user-manipulable steering wheel 352 on user interface 342. Steering wheel 352's onscreen appearance is configured to rotate, in response to user manipulation. For example, steering wheel 352 nay rotate in response to a user swiping laterally across display unit 337 with her finger proximate the top of steering wheel 352. Additionally or alternatively, novelty vehicle simulator 345 may direct computing device 335 to Output audio through audio output device 342 in response to a user manipulating steering wheel 352. For example, novelty vehicle simulator 345 may, for example, output a car-turning noise in response to a user turning beyond an intermediate position, e.g. with steering wheel 352 rotated 90 degrees or greater in either direction, or output a car-crash sound in response to a user turning beyond an advanced position beyond the intermediate position, e.g. with steering wheel 352 rotated. 360 degrees in either direction. As FIG. 6 shows, steering wheel 352 additionalling includes a horn 353 configured to play a sound resembling a honked automobile horn in response to user-manipulation, such as pressing on display unit 337 proximate horn 353.

As FIG. 6 illustrates, touchscreen-driven simulation mode 350 illustrates user-manipulable shifter 354 on user interface 342. Like steering wheel 352 shifter 354 is configured to move according to user manipulation. For example, novelty vehicle simulator 345 provides upshifting and downshifting functionalities, whereby a user may touch at gear positions 355i-iv to move shifter 354 to that position. In some examples, users may additionally or alternatively drag with her finger shifter 354 between these positions. Additionally or alternatively, novelty vehicle simulator 345 may direct computing device 335 to output audio through audio output device 342 in response to moving shifter 354 between these positions. For example, novelty vehicle simulator 345 rryay play audio resembling an automobile upshifting in response to moving shifter 354 upward in gear, e.g. from gear position 355i to 355ii; additionally or alternatively, novelty vehicle simulator 345 may play audio resembling an automobile downshifting in response to moving shifter 354 downward in gear, e.g. from. gear position 355ii to 355i.

As FIG. 6 illustrates, touchscreen-driven simulation mode 350 illustrates user-manipulable dashboard computer 356 on user interface 342. As FIG. 6 illustrates, dashboard computer 356 includes a dashboard monitor 357i and dashboard keyboard 357ii. As FIG. 6 shows, dashboard monitor 357i may display a selected action corresponding to a user-adjustable dashboard computing device state. For example, FIG. 6 shows a user-adjustable dashboard computing device state corresponding to a “SIREN” mode; as FIG. 6 shows, dashboard computer 356 displays the text “SIREN” to reflect this current dashboard computing device state. In each dashboard computing device state, dashboard keyboard 357ii may be selected to perform an action associated with the current dashboard computing device state. For example, when “SIREN” is displayed, a user may select dashboard keyboard 357ii to output audio to audio output device 342 that resembles the sound produced by a police siren. Additionally or alternatively, novelty vehicle simulator 345 may modify the graphical display with blue and red flashes to resemble police car blinkers.

Though dashboard computer 356 is illustrated in FIG. 6 in a “SIREN” dashboard computing device state, dashboard computer 356 may be adjusted to other states. Users may manipulate dashboard computer 356 by, for example, swiping across dashboard monitor 357i on display unit 337. As FIG. 6 illustrates, dashboard monitor 357i may display an arrow 359 on each side of dashboard monitor 357i when additional dashboard computing device states are available to be selected by swiping in the corresponding direction.

Other states may include, for example, a “CALL HQ” state, wherein novelty vehicle simulator 345 outputs audio resembling a phone ringing and proceeding to active “SIREN” state, a “MUSIC” state, wherein music stored on computing device 335 may be played through audio output device 342 (such as music from a user's personal music library, the last played song in their default media playback application, etc.), and “SETTINGS” state, which may bring up a dialog through which a user may adjust her preferences governing novelty vehicle simulator 345's behavior.

Additionally or alternatively, each state may have a color associated with it to allow users to snore dearly visually list distinguish between states. For example, the background of dashboard monitor 357i may be blue in “SIREN” state, green during “CALL HQ” state, yellow during “MUSIC” state, and red during “SETTINGS” state. While the particular colors are not necessarily selected for an inherent association with each state, they are selected for their contrast with one another.

As FIG. 6 shows, touchscreen-driven simulation mode 350 includes shotgun 358, dashboard 360, and pedals 362 that are each configured to play sounds associated with the objects associated with the objects. For example, a user may select shotgun 358 to play a shotgun noise, or pedals 362 to produce sounds that resemble an automobile accelerating or braking. Additionally or alternatively, novelty vehicle simulator 345 may animate that or other displayed features. Some examples may, of course, include additional or alternative examples of elements that provide these simple audio and graphical simulation functionality.

In some examples, novelty vehicle simulator 345 may be configured to play a soundtrack in the background during the entirety of execution. This soundtrack may, in some examples, sound like an example environment through which an automobile may travel, typical sounds of an automobile operating, or other such contextual sounds.

In various examples, each of the user-manipulable elements' visual appearance may be adjusted in response to user-manipulation. For example, various elements may be highlighted in response to user manipulation. This highlighting may allow users to more clearly detect when they have selected a particular user-manipulable element. Additionally or alternatively, various elements may be animated as a function of vehicle related actions.

When novelty vehicle simulator 345 is operating in support-driven simulation mode as displayed in FIG. 7, novelty vehicle simulator 345's operation is driven largely in response to a user manipulating sup N port 305. Novelty vehicle simulator 345 may detect such user manipulation via computing device 335's motion sensing device and drive user interaction to perform vehicle related actions that may, for example, produce sounds or animate graphical elements shown on the display.

As FIG. 7 illustrates, support-driven simulation mode 375 includes a plurality of features that are manipulated in response to user manipulation of support 305 detected by computing device 335's motion sensing device. Support-driven simulation mode 375 may, include a wide range of user-manipulable features that are responsive to user manipulation of support 305. In some contexts, novelty vehicle simulator 345, when in operating in support-driven simulation mode 375, may perform a simulation game that detects users' physical manipulation of support 305 through computing device 335's motion sensing device as input, and uses this input to drive an active simulation of the vehicle represented by support 305's vehicular appearance. A description of one such example of a simulation game wherein novelty vehicle simulator 345 executes a simple simulation of a cop car driven by a user-manipulable driver 377, is provided below. Although the simulation game is discussed primarily in connection with support-driven simulation mode 375, similar games may, of course, additionally or alternatively be executed while in touch screen-driven simulation mode 350 or other novelty simulator modes.

In the simulation game, novelty vehicle simulator 345 includes a physics engine, which controls animation of the driver and other on-screen elements in response to user manipulation. The user may manipulate driver 377 with a plurality of motions, including left and right turns, hard left and right turns, braking and acceleration, car starting, gear shifting, and navigating bumpy terrains. Users may perform gestures that manipulate support 305 to instruct novelty vehicle simulator 345 to manipulate on-screen elements in response to these gestures.

When performing these gestures, the user's goal is to avoid stalling the car. Users may stall the car, for example, producing long “idle” times (or a period wherein a user fails to manipulate support 305), manipulating support 305 with particularly jerky motions. Such stalls will instruct novelty vehicle simulator 345 to enter a stalled mode wherein the display is dimmed and/or colorless and novelty vehicle simulator 345 ceases responding to a majority of user actions. Users may re-enter an active simulation mode by shaking support 305 to instruct novelty vehicle simulator 345 to re-ignite the simulated automobile. In some contexts, the stalled mode may put the phone into a sleep mode to conserve energy.

Typically, the simulation game begins by displaying a message reading “Shake to Start Engine” displayed on display unit 337 over the displayed over the scene shown in FIG. 7. Upon the user shaking the car, novelty vehicle simulator 345 will display the car in a sitting position 379 illustrated in FIG. 8. As FIG. 8 illustrates, sitting position 379 illustrates a top view of driver 377 seated in and driving the simulated automobile in a substantially forward direction. In sitting position 379, novelty vehicle simulator 345 further outputs, to audio output device 342, audio that resembles, initially, the noise of an igniting automobile and, subsequently, an automobile in operation.

As FIG. 8 illustrates, the simulation game is responsive to certain user gestures that manipulate support 305. For example, novelty vehicle simulator 345 may be configured to produce an engine running noise through in response to a movement gesture, which s defined by any user movement of support 305 detected by computing device 335's motion sensing device that novelty vehicle simulator 345 does not recognized as any other specific gesture.

FIG. 8 illustrates two examples of gestures that may be recognized by novelty vehicle simulator 345 via computing device 335's motion sensing device, including a left turn position 380 and a right turn position 382 in response to user gestures. The user activated left turn position 380, for example, by adjusting support 305 by performing a gesture that positions support 305 leftward from its initial position. As FIG. 8 illustrates, driver 377's onscreen appearance is adjusted to reflect him turning in a leftward direction with a single hand on the illustrated steering wheel. When this occurs, novelty vehicle simulator 345 additionally outputs audio to audio output device 342 that resembles the sound of a passing-by automobile. In some examples, users may additionally or alternatively adjust support 305 in a more severe leftward position, wherein driver 377 turns the displayed steering wheel with both hands and novelty vehicle simulator 345 outputs a sound to audio output device 342 resembling tires screeching.

As FIG. 8 illustrates, a user may manipulate support 305 with a substantially similar, but rightward, gesture that adjusts novelty vehicle simulator 345 into right urn position 382. Like left turn position 380, driver 377's onscreen appearance is adjusted to reflect him turning in a rightward direction with a single hand on the illustrated steering wheel when novelty vehicle simulator 345 is in right turn position 382. A user may additionally or alternatively adjust support 305 more severely to the right to place driver 377 in the two-handed turn position discussed above and produce the aforementioned fire screeching sound.

The aforementioned left-turn gestures and right-turn gestures are not the only gestures supported by novelty vehicle simulator 345. For example, novelty vehicle simulator 345 supports an upshifting gesture wherein a user lifts the front wheels of support 305 while maintaining the rear wheels on the ground. This will provide substantially similar upshifting functionality described above in connection with shifter 354 in touchscreen--driven simulation mode 350. Further, novelty vehicle simulator 345 may be configured to respond to a downshifting gesture wherein a user lifts support 305's rear wheels up while the front wheels remain engaged with the ground to place support 305 at an angle of 5 degrees or less with the ground. Novelty vehicle simulator 345 would provide substantially similar downshifting functionality described above in connection with shifter 354 in touchscreen-driven simulation mode 350. Additionally or alternatively, novelty vehicle simulator 345 may recognize a braking gesture, wherein a user lifts the rear wheels of support 305 to place support 305 at an angle of greater than 5 degrees. Novelty vehicle simulator 345 may provide braking functionality similar to that provided by the braising pedal of pedals 362 in response to recognizing this gesture. This braking functionality outputs, through audio output device 342, a hard braking noise while animating driver 377 to snap his head back towards his seat.

Novelty vehicle simulator 345 additionally or alternatively supports a bumpy road gestures performed by shaking support 305. This gesture makes a sound that resembles the interior cabin of an automobile shaking.

Novelty vehicle simulator 345 additionally or alternatively supports left and right tilt gestures that are performed by tilting support 305 either leftwards or rightwards. In the left tilt gesture, driver 377 is animated to place his left hand on window 386 displayed on the left side of user interface 342. In the right tilt gesture, driver 377 is animated to place his right hand on passenger seat 387 of the simulated auto interior displayed on display unit 337.

Novelty vehicle simulator 345 additionally or alternatively supports gestures wherein a user rotates support 305 either clockwise or counterclockwise at or near 180 degrees. When rotating support 305 clockwise in this manner, novelty vehicle simulator 345 produces a car skidding sound through audio output device 342 as driver 377 is animated to slap the steering wheel. When rotating support 305 counterclockwise in this manner, a substantially similar car skidding sound is produced through audio output device 342 and driver 377 is animated to look upward. Additionally or alternatively, the aforementioned car skidding sound may be produced whenever support 305 is rotated more than 90 degrees in any direction. Additionally or alternatively, novelty vehicle simulator 345 may respond to sudden stops, such as may occur when support 305 is dropped, by animating driver 377 getting knocked unconscious. Novelty vehicle simulator 345 may operate in an inactive state until a user swipes driver 377 awake.

Novelty vehicle simulator 345 may additionally or alternatively be configured to respond to certain gesture sequences that include a plurality of gestures performed quickly to defile a sequence. For example, novelty vehicle simulator 345 may be configured to respond to a series of quick left and right turn motions, wherein it fluidly animates quickly inputted motions. Additionally or alternatively, novelty vehicle simulator 345 may recognize the distance in which support 305 has been moved since the beginning of operation. By tracking its movement through computing device 335's motion sensing device novelty vehicle simulator 345 may, for example, perform a vehicle related action, such as the operation associated with the “CALL HQ” state described above response to support 305 having been moved a total of 10 feet.

As FIG. 7 illustrates, novelty vehicle simulator 345 displays a plurality of buttons when operating in support-driven simulation mode 375. The buttons displayed are configured perform a vehicle related action in response to a user manipulating one of the buttons. In the example illustrated in FIG. 8, several buttons perform vehicle related actions similar to those discussed in connection with touchscreen-driven simulation mode 350, though any visual effect would be viewed from support-driven simulation mode 375′s top-down perspective. For example, selecting shotgun button 390 perform a substantially similar vehicle related action as selecting shotgun 358 in touchscreen-driven simulation mode 350, selecting radio button 391 will perform a substantially similar vehicle related action as selecting dashboard computer 356 in a “MUSIC” state when in touchscreen-driven simulation mode 350, and selecting siren button 392 will perform a substantially similar vehicle related action as selecting dashboard computer 356 in a “SIREN” state when in touchscreen-driven simulation mode 350. Other buttons have additional or alternative functions. For example, selecting window button 393 will instruct novelty vehicle simulator 345 to output a sound that resembles a window breaking. As another example, selecting clicker button 394 will instruct novelty vehicle simulator 345 to flash colors with display unit 337 to simulate a police car's flashing lights. Selecting settings button 396 will pull up a settings dialog wherein a user tray set her preferences for novelty vehicle simulator 345's operation.

This disclosure has previously discussed examples of novelty vehicle simulators that are primarily configured to simulate automobiles while including supports that reflect the appearance of an automobile. As FIG. 9 illustrates, this disclosure specifically considers examples that define vehicular appearances that resemble other vehicles as well, such as helicopters. Indeed, FIG. 9 illustrates an example wherein computing device 335 is supported in a support 405 reflecting the appearance of a helicopter and dynamically recognizes the support.

As FIG. 9 illustrates, support 405 retains computing device 335 in a substantially different position than support 305. As a result, novelty vehicle simulator 345 can detect this position and dynamically adjust its behavior in response. Like vehicular appearance signifying mechanism 307, the position with which computing device 435 is supported within support 405 is the mechanism through which support 405 signifies its vehicular appearance. When seated in support 405, computing device 335 is able to detect this position, and produce, in response, a parameter set that corresponds to helicopter-based operation. Like a result, novelty vehicle simulator 345 may modifies its operating parameters to operate in a helicopter mode. Such a mode may display a helicopter's interior and include visual and audible features that correspond to common features of helicopters, similar to touchscreen-driven simulation mode 350's and support-driven simulation mode 375's automobile-based operation.

As this disclosure has noted, some examples of disclosed devices may include computing devices executing a novelty simulator configured to dynamically adapt to a variety of support vehicle designs, such as automobiles, aircraft, watercraft, among other vehicle examples. In some examples, the novelty simulator may be configured to convey a consistent narrative wherein the computing device may be paired with appropriate supports at selected points in the narrative. For example, the narrative conveyed by the computing device may include a character that, at certain points, drives an automobile and pilots an aircraft. When the character drives the automobile, for example, the novelty simulator may operate in a mode similar in many ways to the modes described above, but particularly tailored to the character and narrative context. Similarly, when the character pilots the aircraft, the novelty simulator may operate in a mode similar in many ways to the modes described above, but particularly tailored to the narrative context, the character, and the aircraft support.

The disclosure above encompasses multiple distinct inventions with independent utility. While each of these inventions has been disclosed in a particular form, the specific embodiments disclosed and illustrated above are not to be considered in a limiting sense as numerous variations are possible. The subject matter of the inventions includes all novel and non-obvious combinations and subcombinations of the various elements, features, functions and/or properties disclosed above and inherent to those skilled in the art pertaining to such inventions. Where the disclosure or subsequently filed claims recite “a” element, “a first” element, or any such equivalent term, the disclosure or claims should be understood to incorporate one or more such elements, neither requiring nor excluding two or more such elements.

Applicant(s) reserves the right to submit claims directed to combinations and subcombinations of the disclosed inventions that are believed to be novel and non-obvious, Inventions embodied in other combinations and subcombinations of features, functions, elements and/or properties may be claimed through amendment of those claims or presentation of new claims in the present application or in a related application. Such amended or new claims, whether they are directed to the same invention or a different invention and whether they are different, broader, narrower or equal in scope to the original claims, are to be considered within the subject matter of the inventions described herein.

Claims

1. A novelty vehicle simulation system comprising:

a computing device including: a processor configured to execute processor executable instructions; and a computer readable medium encoded with processor executable instructions for executing a novelty vehicle simulator on the computing device;

a support defining a vehicular appearance, the support: configured to seat the computing device in a substantially fixed position; and including a vehicular appearance signifying mechanism configured to communicate an encoded representation of the vehicular appearance;

wherein the computing device includes: a vehicular appearance sensing mechanism operatively paired with the vehicular appearance signifying mechanism to detect the encoded representation of the vehicular appearance of the support; and wherein the computer readable medium further includes processor executable instructions for: translating the encoded representation of the vehicular appearance of the support to produce a vehicle parameter set corresponding to the vehicle reflected by the vehicular appearance of the support; and modifying operating parameters of the novelty vehicle simulator according to the vehicle parameter set.

2. The novelty vehicle simulation system of claim 1, wherein the computing device includes:

a display unit;

a user input interface; and

wherein executing the novelty vehicle. simulator includes displaying a user interface including user-manipulable elements configured to instruct the processor to execute vehicle related actions in response to user manipulation.

3. The novelty vehicle simulation system of claim 2, wherein:

the user input interface includes a touch-sensitive display defining a display area and configured to detect user contact, and a touch-selected location thereof, within the display area;

wherein the novelty vehicle simulator: includes a plurality of user-selectable elements displayed on the display unit; and is configured to perform a vehicle-related action in response to the user touching the display unit proximate a selected user-selectable element.

4. The novelty vehicle simulation system of claim 3, wherein the computing device includes an audio output device; and

the vehicle-related action associated with one or more of the user-manipulable elements defines producing, through the audio output device, a noise commonly produced by the vehicle reflected by the vehicular appearance of the support in response to the user touching the display unit proximate the selected user-selectable element.

5. The novelty vehicle simulation system of claim 3, wherein the user-manipulable elements include one or more user-selectable elements relating to the vehicle reflected by the vehicular appearance of the support, the user-selectable elements automatically generated in response to producing the vehicle parameter set.

6. The novelty vehicle simulation system of claim 2, wherein one or more of the user-manipulable elements resemble interior features commonly visible from an operational position within a typical vehicle of a type reflected by the vehicular appearance of the support.

7. The novelty vehicle simulation system of claim 6, wherein the user-manipulable elements includes a simulated control mechanism includes a simulated control mechanism of the vehicle reflected by the vehicular appearance of the support.

8. The novelty vehicle simulation system of claim 7, wherein the simulated control mechanism defines a steering wheel in response to the encoded representation of the vehicular appearance indicating that the vehicular appearance of the support reflects and automobile.

9. The novelty vehicle simulation system of claim 8, wherein the computer readable medium further includes processor executable instructions for modifying a scene displayed on the display unit in response to user manipulation of the steering wheel.

10. The novelty vehicle simulation system of claim 1, wherein the computing device includes a display unit; and

the computer readable medium further includes processor executable instructions for displaying on the display unit a scene reflecting a typical environment of use of the vehicle indicated by the vehicular appearance of the support.

11. The novelty vehicle simulation system of claim 10, wherein the computer readable medium further includes processor executable instructions for modifying the scene in response to user manipulation, the scene modified to reflect the users manipulation of the support.

12. The novelty vehicle simulation system of claim 11, wherein:

the computing device includes a motion-sensing device; and

the novelty vehicle simulation modifies the scene in response to user manipulation of the support, the user manipulation detected by the motion-sensing device,

13. The novelty vehicle simulation system of claim 10, wherein the computer readable medium further includes processor executable instructions for:

displaying on the display unit an interface including user-manipulable elements corresponding to vehicle-relate actions; and

modifying the scene in response to user manipulation of a user-manipulable element.

14. The novelty vehicle simulation system of claim 1, wherein the vehicular appearance resembles an automobile.

15. The novelty vehicle simulation system of claim 1, wherein the vehicular appearance resembles aircraft.

16. The novelty vehicle simulation system of claim 1, wherein the computing device includes an audio output device; and

the computer readable medium fur her includes processor executable instructions for outputting, through the audio output device, a noise commonly produced b the vehicle reflected by the vehicular appearance of the support.

17. The novelty vehicle simulation system of claim 1, wherein the support defines a support cavity fitted to support the computing device.

18. The novelty vehicle simulation system of claim 17, wherein:

the computing device includes a position detecting device;

the support cavity supports the computing device in a selected position that defines the encoded representation of the vehicular appearance; and

the computer readable medium further includes processor executable code for: reading the selected position with the position detecting device; and translating the selected position read with the position detecting device to the parameter set corresponding to the vehicle reflected by the vehicular appearance of the support.

19. A novelty vehicle simulation system comprising:

a support defining a vehicular appearance, the support: defining a support cavity, the support cavity partially enclosing a cavity space visible from positions external to the support and perimetraly sized to insert and display a computing device including: a processor configured to execute processor executable instructions for a novelty vehicle simulator; an audio output device; and a camera; and a display unit;

wherein the support defines: a frictional support surface that is recessed from the external surface of the support and sized to seat the computing device, the frictional support surface defining a coefficient of friction selected to reduce slipping of the computing device when seated on the frictional support surface; a camera port aligned with the camera, the camera port defining a visual path through the support from a camera-proximate position the camera s proximate position when the computing device is seated within the support cavity to external positions around the support; and an audio output port aligned with the audio output device, the audio output port defining an audible path through the support from an audio output proximate positron proximate the audio output device. to external positions around the support.

20. A novelty vehicle simulation system comprising:

a support defining a vehicular appearance, the support: configured to seat a computing device in a substantially fixed position; and

wherein the computing device defines a form factor and includes: a processor configured to execute Processor executable instructions; and processor executable instructions for: executing a novelty vehicle simulator on the computing device, executing the novelty vehicle simulator includes: detecting the form factor of the computing device; and displaying a user interface that is specifically adapted to the detected form factor; translating the encoded representation of the vehicular appearance of the support to produce a vehicle parameter set corresponding to the vehicle reflected by the vehicular appearance of the support; and modifying operating parameters of the novelty vehicle simulator according to the vehicle parameter set.