The present invention relates to electronic convenience vehicles and more specifically, to electronic convenience vehicles including a user interface.
Theme parks and other public venues, such as sports and concert venues, zoos, and other public and private venues have long been enjoyed by crowds of all ages. Other types of facilities, such as airports, hospitals, malls, retail stores, and so forth, have similar types of crowds. As understood by venues, crowds have a certain percentage of individuals who need assistance with walking due to injury, illness, age, or otherwise, and generally referred to as handicapped individuals
As has become both public policy and good business, venues provide for powered vehicles, generally referred to as electronic convenience vehicles (ECVs), that are self-propelled to enable handicapped individuals who have physical handicaps that prevent or limit walking to participate at the venue. Existing ECVs include electric powered scooters on which a handicapped individual may drive throughout the day to access different parts of a venue. Conventional ECVs are relatively simplistic, and typically include a chair mounted on a frame with wheels and a steering mechanism. A motor on the ECV is controlled to propel the ECV forward or backward by the use of a throttle, generally located on handles of the steering mechanism.
The ECVs, depending on the venue, may be rented to visitors by the facility or a third-party provider. Other facilities allow for a user to borrow ECVs while at the venue. While these ECVs are helpful to the handicapped individuals, the venues and ECV owners/operators do not receive commercial benefit during rental periods of the ECVs beyond rental rates by the handicapped individuals. Hence, ECVs that provide additional commercial benefits to the ECV owners/operators, while increasing functionality and experience to the users of the ECVs, are needed.
An electronic convenience vehicle (ECV) that improves an experience at a venue for users and improves commercial value for a venue and operator of the ECV may include a control and command unit (CCU) that improves safety for pedestrians around the ECV, reduced liability and risk of injury for users, and provides functionality that heretofore does not exist on ECVs. The functionality ranges from venue mapping and directions, rental and reservation ordering on the ECV, venue messaging between the user and venue, locking and unlocking of a lockbox on the ECV, and so on.
A more complete understanding of the method and apparatus of the present invention may be obtained by reference to the following Detailed Description when taken in conjunction with the accompanying Drawings wherein:
A. Electronic Convenience Vehicle (ECV)
An electronics convenience vehicle (ECV) may include a frame, multiple wheels configured to support and move the frame, a seat supported by the frame, and a steering mechanism disposed toward a front portion of the ECV, and configured to enable a user to rotate direction of one or more wheels to control direction of movement of the ECV. In an embodiment, the frame may include a chassis. A motor may be configured to cause at least one wheel to be propelled forward, propelled backward, or to remain in a fixed position. A throttle, when activated in a first position, causes the motor to propel the wheel(s) in a forward direction, when activated in a second position, causes the motor to propel the wheel(s) in a reverse direction, and when in a third position, causes the motor to maintain the wheel(s) in a fixed position. One or more sensors may be directed to detect objects in front of a direction of travel of the ECV, and may be configured generate sense signals indicative of an object being sensed by the sensor(s). A control and communications unit (CCU) may be disposed in front of the seat, and configured to receive the sense signals and to control operations of said motor, said CCU further configured to communicate over a communications network. The CCU is also referred to as an electronic digital dash (EDD).
With regard to
Mounted to the tiller, one more sensors are mounted. By mounting the sensors to the tiller, the sensors are able to sense objects in front of the direction of travel of the ECV. Moreover, as the sensors are mounted to the tiller that rotates, the sensors sense objects as a function of the angle of the tiller, which is different from sensors that may alternatively be mounted to a front bumper of the ECV, where bumper-mounted sensors would sense objects in front of the bumper of the ECV as opposed to an immediate directional change of the tiller that leads a directional change of the ECV.
With regard to
On a rear portion of the body of the ECV, lights that indicate that the ECV is stopping to vehicles and people behind the ECV are shown. In an environment, one or more sensors, such as proximity sensors, may be positioned on the rear of the ECV. A camera may also be positioned on the rear of the ECV, thereby enabling a user to see behind the ECV when backing up by viewing video images received from the rear camera on the CCU, for example.
Demonstrated Capability
Touchscreen display and integration 7 inch and 5 inch displays
GPS integration
WI-FI wireless functionality
EV hardware Inputs and outputs
Features
Front end is Web Browser—Easy to program and very versatile (video, audio, multimedia capability)
CCU may work with network connectivity or without networking.
Open source (free) software
External Web sites/database could be integrated (depending on web connection) easily with HTML. Can be easily integrated to custom web server over internet for additional capabilities.
Websockets and Apache web server has very good (SSL) security built in. Can be made secure.
Versatile interface allow either web browser from internet (to individual EV's) or websockets from back end servers
System can be scaled to large number of EV's
Hardware
The hardware for the proof-of-concept EDD is low cost computer board and touchscreen display, GPS and Wi-Fi adapters and a 12 to 24 volt switching converter to supply power to the computer and peripherals.
Software
The EDD software leverages the use of built-in functionality of the Linux system. The front end handles the display and user input. The back end interfaces between the hardware, networking layers (i.e. remote) and the local client (browser).
After powered, The software boots Linux and start the server processes and displays the initial screens. All software is stored on a mini SD card.
The front end EDD display:
Servers (running on EDD):
Proof of concept Hardware block diagram
EV Server
Websockets interface:
4 protocols supported:
SB_Test—for testing allows commands to test
SB_GPS—sends GPS data real time from GPOS receiver
SB_EV—send EV hardware events, Occupancy (seat switch) and unlock/lock
SB_MSG—allows sending message top EV dashboard
B2. Venue Server Communications
C. User Interface
With regard to
In one embodiment, the processor may be referred to as a central processor unit (CPU). The processor may be implemented as one or more CPU chips, one or more cores (e.g., a multi-core processor), or may be part of one or more application specific integrated circuits (ASICs) and/or digital signal processors (DSPs). The processor may be configured to implement any of the processes described herein, such as the processes of
The display may be configured to be electronically communicative with the processor. The display may be configured to display representations of data to the user. The display may display in color or monochrome and may be equipped with a touch sensor based resistive and/or capacitive technologies. The display may be further configured to be an input device that may allow the user to input commands to the processor. One of ordinary skill in the art will appreciate that a variety of methods for communicating between the user and the machine.
C1. Rental/Reservations on CCU
With regard to
With regard to
C2. Wayfinder
With regard to
C3. Character Messaging
With regard to
C4. Venue-Centric Compass
With regard to
C5. Time Lapse Video with User Generated Content (UGC) Integration
With regard to
With regard to
C6. Venue-Specific User Information
With regard to
C7. Messaging (Notices, Park Closing)
With regard to
C8. Lock/Unlock of Lockbox on Scooter
With regard to
The Electronic Convenience Vehicle (ECV) mobility scooter—the EDD system—is currently in development and will be designed, equipped and programmed with smart technology. This mobility equipment will serve guests and visitors at any venues with a control center and mapping device. See Table 1 for the EDD system's smart features and functionality.
Mobility Equipment: Initial Start-Up
At the initial startup of the EDD, as the user interface loads, the ScooterBug™ branding appears on the screen. See
Welcome Screen Navigation
The Welcome screen introduces the ECV or the mobility scooter entitled, the Electronic Digital Dashboard (EDD), and displays features to Rent or Return and to Run Vehicle. See
Reservation Management System (RMS) Main Menu
When an Administrator or a user selects the Rent or Return button, the RMS Main Menu appears as illustrated in
In a self-vending, rental environment, the user would press the Rent or Retrieve buttons on the RMS Main Menu screen.
If the user is in a managed environment, once the user pays the Attendant to rent a vehicle, the user will simply press the Run Vehicle button on the RMS Main Menu screen.
When the ECV is not in Operation: Sleep Mode
When the vehicle is not in operation and goes into sleep mode, the screensaver as shown in
Keycode Access to Unlock & Operate the ECV
Once the user selects the Run Vehicle button from the Welcome screen or touches the screensaver (See
User will have to establish a 4-digit keycode at initial use of the EDD and then remember it to access and operate it throughout the entire rental period.
Once the user submits their 4-digit keycode, a system notification as displayed in
Home Screen (Dashboard)
After the user enters their 4-digit keycode to run and operate the ECV, the Home screen (e.g., Dashboard) displays the user interface of the EDD with its respective icons as shown in
Users may navigate the EDD via the Home or Dashboard, Rent/Return, Wayfinder, Venue, Settings (i.e., user audio/visual preferences, Administrator Maintenance, etc.) or Help buttons. These features, including the date and time (top, left), WiFi and battery indicators (top, right), sensor (center, left), horn (bottom, left) and the “stop” or the Lock Vehicle button (bottom, right), will appear on every screen for easy use and navigation.
Mapping (e.g., Wayfinder) Screen
The example in this illustration displays the map of a sample theme park.
Rent/Return Screen
The RMS Main Menu above in
Lock Vehicle Button
When the user engages the Lock Vehicle button, the keypad window opens for the user to enter their keycode to lock the vehicle. Before the vehicle locks, a System Notification as illustrated in
With regards to
SENSING:
1) IF A STATIONARY OR MOVING OBJECT IS DETECTED BY THE ULTRASONIC SENSORS, THE DASH INDICATOR ACTIVATES AND THE VEHICLE PERFORMANCE CURVE IS REDUCED UNTIL THE ZONE IS CLEAR.
2) 3 FORWARD FACING SENSORS AND 2 REAR SENSORS
With regards to
CAMERAS:
1) FRONT TILLER MOUNTED CAMERA IS ACTIVATED WHEN THE SAFE-ZONE IS ACTIVE. LOW-RES VIDEO IS STORED DAILY TO PROVIDE BACKUP VIDEO FOR POTENTIAL ACCIDENT CLAIMS.
2) BACKUP CAMERA ACTIVATES WHEN THE VEHICLE IS IN REVERSE TO AVOID COLLISION WITH LOW UNSEEN OBSTACLES.
The foregoing method descriptions and the process flow diagrams are provided merely as illustrative examples and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by one of skill in the art, the steps in the foregoing embodiments may be performed in any order. Words such as “then,” “next,” etc. are not intended to limit the order of the steps; these words are simply used to guide the reader through the description of the methods. Although process flow diagrams may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.
The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed here may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
Embodiments implemented in computer software may be implemented in software, firmware, middleware, microcode, hardware description languages, or any combination thereof. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to and/or in communication with another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
The actual software code or specialized control hardware used to implement these systems and methods is not limiting of the invention. Thus, the operation and behavior of the systems and methods were described without reference to the specific software code being understood that software and control hardware can be designed to implement the systems and methods based on the description here.
When implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable or processor-readable storage medium. The steps of a method or algorithm disclosed here may be embodied in a processor-executable software module which may reside on a computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable media includes both computer storage media and tangible storage media that facilitate transfer of a computer program from one place to another. A non-transitory processor-readable storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such non-transitory processor-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible storage medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer or processor. Disk and disc, as used here, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.
The previous description is of a preferred embodiment for implementing the invention, and the scope of the invention should not necessarily be limited by this description. The scope of the present invention is instead defined by the following claims.
This Application claims benefit of U.S. Provisional Application Ser. No. 62/546,474, filed Aug. 16, 2017, entitled ELECTRONIC CONVENIENCE VEHICLE (ECV) WITH CONTROL AND COMMUNICATIONS UNIT, the contents of which are hereby incorporated by reference in their entirety.
Number | Date | Country | |
---|---|---|---|
62546474 | Aug 2017 | US |