Patent Application
20190369203
This invention relates to systems and methods for implementing a bicycle-sharing system.
Today, many bicycle-sharing programs are designed such that users take out and return bicycles from docking station hubs placed throughout a city or region. Although the bike-share operator (typically a company responsible for maintaining the service, e.g. MOTIVATE) can easily identify the hubs at which a given bike begins and ends its journey, this information does not detail the path between hubs that the bicycle may have traveled. Unfortunately, the use of GPS modules to track bicycles often proves inaccurate in cities with tall buildings due to the “urban canyon” effect.
The system and method disclosed herein provide an improved approach for tracking shared bicycles.
In order that the advantages of the invention will be readily understood, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered limiting of its scope, the invention will be described and explained with additional specificity and detail through use of the accompanying drawings, in which:
Referring to
The shared bicycle 104 may lack a GPS receiver and may further lack the ability to communicate information, other than to broadcast a fixed signal using the beacon 106. In other instances, the shared bicycle may have a GPS receiver. However, the system and method disclosed herein are particularly useful where a GPS receiver does not function properly due to the urban canyon effect or other limitations.
In some embodiments, the shared bicycle 104 has a beacon 106 mounted thereto that is embodied as a BLUETOOTH low energy (BLE) beacon. Accordingly, the sensors 102 may be embodied as BLE receivers. The sensors 102 may be in data communication with a server system 110 through wired connections or by communication with one or more cellular communication towers 112. The cellular communication towers 112 may be in data communication with the server system 110 by means of a network 114. The network 114 may include a local area network (LAN), wide area network (WAN), the Internet, or any other wired or wireless connection.
A BLE sensor 102 may detect both the presence of a BLE beacon 106 and measure strength of a signal from the BLE beacon. The signal may include an identifier of the beacon 106. A bike-sharing program may include many bicycles each having a BLE beacon 106 mounted thereto that broadcasts a signal communicating unique identifier. The BLE sensors 102 may therefore transmit to the server system 110 records for each detection of a BLE beacon 106, the record including a time of detection, the identifier of the detected BLE beacon 106, and the signal strength of the signal detected from the BLE beacon 106.
The server system 110 interprets these records in order to estimate the trajectory 108 of the shared bicycle 104. The starting point of the trajectory 108 may be set by the server system 110 to be a check-out station 116, from which the shared bicycle 104 was taken. Likewise, a check-in station 118 to which the shared bicycle 104 is checked in may be set by the server system 110 to be the location of the check-in station. The check-in station 118 and check-out station 116 may both function as either a check-in or check-out station as known in the art of bicycle-sharing programs. The check-out station and check-in station 116, 118 may include computer devices that are programmed to report identifiers of bicycles 104 that are checked into and checked out of the station 116, 118 to the server system 110. The reports of identifiers may include an identifier of the station 116, 118 making the report and the server system 110 may have access to a database storing locations for each station identifier.
Referring to
The method 200 may then include receiving zero or more reports from sensors 102 reporting sensing of the beacon 106 mounted to the shared bicycle. If a sensor 102 is found 204 to detect the beacon of the shared bicycle, this report may be logged 206 for the shared bicycle 104. As noted above, the sensor 102 may report the identifier of the beacon 106, an identifier or location of the sensor 102, and the strength of the signal received from the beacon 106. The server system 110 may resolve the location of the sensor 102 according to a database mapping sensor identifiers to locations. Steps 204 and 206 may be repeated throughout a ride. There may also be cases where no sensors 102 detect a beacon 106 during a trip.
The method 200 may further include detecting 208 check in of the shared bicycle 104. Such as by receiving a report from the station 118 to which the shared bicycle was checked in. As before, this report may include an identifier of the shared bicycle 104 that was checked in and an identifier or location of the check-in station 118, or an identifier that the server system 110 resolves to a location. The method 200 includes logging 210 the location of the check-in station 118.
The method 200 may include triangulating 212 a position of the shared bicycle 104. For example,
Using the check-out location of step 202, the check-in location of step 210, the locations of sensors 102 that detected the beacon 106, and any locations determined by triangulation at step 212, hereinafter the “known locations,” a trajectory of the bicycle may be estimated 214. Note that triangulation may not always be possible such that only the location of a sensor 102 is used in some cases rather than a triangulated position of the beacon 106. For example, a trajectory may be determined that passes through the known locations. The estimated trajectory may also be a trajectory that does not pass within a detection range of sensors 102 that did not detect the beacon of the shared bicycle between the time of check out and the time of check in.
Subject to the constraints of passing through the known location and not passing within range of non-detecting sensors 102, the trajectory may be estimated to be a shortest route that meets these constraints. The trajectory may be estimated as a route that does not pass through roads that are impassible for bikes, e.g. freeways or heavy traffic areas. The selection of the estimated trajectory may also be biased towards roads having bike lanes or that are otherwise flagged as being suitable for bike traffic.
The method 200 may then include processing 216 the bicycle trajectory in some way. Knowing the trajectory of shared bicycles may be used for various purposes. For example, a city planner may determine preferred routes of cyclists in order to determine where to put a bike lane or where to place bicycle-sharing stations. Processing 216 of the trajectory may also be performed in order to determine the location of a stolen bicycle or a bicycle that was otherwise not properly returned to a bicycle-sharing station.
Computing device 400 includes one or more processor(s) 402, one or more memory device(s) 404, one or more interface(s) 406, one or more mass storage device(s) 408, one or more Input/Output (I/O) device(s) 410, and a display device 430 all of which are coupled to a bus 412. Processor(s) 402 include one or more processors or controllers that execute instructions stored in memory device(s) 404 and/or mass storage device(s) 408. Processor(s) 402 may also include various types of computer-readable media, such as cache memory.
Memory device(s) 404 include various computer-readable media, such as volatile memory (e.g., random access memory (RAM) 414) and/or nonvolatile memory (e.g., read-only memory (ROM) 416). Memory device(s) 404 may also include rewritable ROM, such as Flash memory.
Mass storage device(s) 408 include various computer readable media, such as magnetic tapes, magnetic disks, optical disks, solid-state memory (e.g., Flash memory), and so forth. As shown in
I/O device(s) 410 include various devices that allow data and/or other information to be input to or retrieved from computing device 400. Example I/O device(s) 410 include cursor control devices, keyboards, keypads, microphones, monitors or other display devices, speakers, printers, network interface cards, modems, lenses, CCDs or other image capture devices, and the like.
Display device 430 includes any type of device capable of displaying information to one or more users of computing device 400. Examples of display device 430 include a monitor, display terminal, video projection device, and the like.
Interface(s) 406 include various interfaces that allow computing device 400 to interact with other systems, devices, or computing environments. Example interface(s) 406 include any number of different network interfaces 420, such as interfaces to local area networks (LANs), wide area networks (WANs), wireless networks, and the Internet. Other interface(s) include user interface 418 and peripheral device interface 422. The interface(s) 406 may also include one or more peripheral interfaces such as interfaces for printers, pointing devices (mice, track pad, etc.), keyboards, and the like.
Bus 412 allows processor(s) 402, memory device(s) 404, interface(s) 406, mass storage device(s) 408, I/O device(s) 410, and display device 430 to communicate with one another, as well as other devices or components coupled to bus 412. Bus 412 represents one or more of several types of bus structures, such as a system bus, PCI bus, IEEE 1394 bus, USB bus, and so forth.
For purposes of illustration, programs and other executable program components are shown herein as discrete blocks, although it is understood that such programs and components may reside at various times in different storage components of computing device 400, and are executed by processor(s) 402. Alternatively, the systems and procedures described herein can be implemented in hardware, or a combination of hardware, software, and/or firmware. For example, one or more application specific integrated circuits (ASICs) can be programmed to carry out one or more of the systems and procedures described herein.
In the above disclosure, reference has been made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific implementations in which the disclosure may be practiced. It is understood that other implementations may be utilized and structural changes may be made without departing from the scope of the present disclosure. References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
Implementations of the systems, devices, and methods disclosed herein may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed herein. Implementations within the scope of the present disclosure may also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media that store computer-executable instructions are computer storage media (devices). Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, implementations of the disclosure can comprise at least two distinctly different kinds of computer-readable media: computer storage media (devices) and transmission media.
Computer storage media (devices) includes RAM, ROM, EEPROM, CD-ROM, solid state drives (“SSDs”) (e.g., based on RAM), Flash memory, phase-change memory (“PCM”), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
An implementation of the devices, systems, and methods disclosed herein may communicate over a computer network. A “network” is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmissions media can include a network and/or data links, which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.
Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.
Those skilled in the art will appreciate that the disclosure may be practiced in network computing environments with many types of computer system configurations, including, an in-dash vehicle computer, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, various storage devices, and the like. The disclosure may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.
Further, where appropriate, functions described herein can be performed in one or more of: hardware, software, firmware, digital components, or analog components. For example, one or more application specific integrated circuits (ASICs) can be programmed to carry out one or more of the systems and procedures described herein. Certain terms are used throughout the description and claims to refer to particular system components. As one skilled in the art will appreciate, components may be referred to by different names. This document does not intend to distinguish between components that differ in name, but not function.
It should be noted that the sensor embodiments discussed above may comprise computer hardware, software, firmware, or any combination thereof to perform at least a portion of their functions. For example, a sensor may include computer code configured to be executed in one or more processors, and may include hardware logic/electrical circuitry controlled by the computer code. These example devices are provided herein purposes of illustration, and are not intended to be limiting. Embodiments of the present disclosure may be implemented in further types of devices, as would be known to persons skilled in the relevant art(s).
At least some embodiments of the disclosure have been directed to computer program products comprising such logic (e.g., in the form of software) stored on any computer useable medium. Such software, when executed in one or more data processing devices, causes a device to operate as described herein.
While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the disclosure. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. The foregoing description has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. Further, it should be noted that any or all of the aforementioned alternate implementations may be used in any combination desired to form additional hybrid implementations of the disclosure.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/US2016/066358 | 12/13/2016 | WO | 00 |
