ride-sharing accessibility

Abstract

A method includes transmitting a ride-share request to a ride-share server, the ride-share request including information about an accessibility device, determining a current orientation of the accessibility device, and transmitting the current orientation of the accessibility device to the ride-share vehicle. Another method includes transmitting a current orientation of an accessibility device, receiving a target orientation of the accessibility device, illuminating a spot light, determining that the accessibility device is in the target orientation, and turning off the spot light.

Description

Technical Field

[0001] This invention relates to a method comprising: transmitting a ride-sharing request to a ride-sharing server, the ride-sharing request including information about an accessibility device; determining the current orientation of the accessibility device; and transmitting the current orientation of the accessibility device to a ride-sharing vehicle. Another method comprises: transmitting the current orientation of the accessibility device; receiving the target orientation of the accessibility device; illuminating a projector; determining that the accessibility device is in the target orientation; and turning off the projector. Background Technology

[0002] Ride-sharing services allow users to request rides via a mobile application. A server serving the mobile application sends a message to a nearby driver containing the passenger's pick-up location and requested destination. The driver then travels to the pick-up location and drives the passenger to the requested destination. Summary of the Invention

[0003] A method includes: transmitting a ride-sharing request to a ride-sharing server, the ride-sharing request including information about an accessibility device; determining the current orientation of the accessibility device; and transmitting the current orientation of the accessibility device to a ride-sharing vehicle.

[0004] In this method, information about the accessibility device may include the physical characteristics of the accessibility device, and may include a ride-sharing request indication as to whether the user of the accessibility device needs to use the accessibility device when riding in a ride-sharing vehicle.

[0005] In this method, the physical characteristic may include at least one of the physical size and weight of the accessibility device.

[0006] The method may include pairing with an accessibility device.

[0007] The method may include receiving target orientation from a ride-sharing vehicle.

[0008] The method may include directing the target to an accessibility device.

[0009] In this method, determining the current orientation of the accessibility device may include receiving the current orientation of the accessibility device from the accessibility device.

[0010] This method may include detecting ride-sharing vehicles near accessibility devices.

[0011] In this method, determining the current orientation of the accessibility device and transmitting the current orientation of the accessibility device to the ride-sharing vehicle can occur after the ride-sharing vehicle is detected to be near the accessibility device.

[0012] A method includes: transmitting the current orientation of an accessibility device; receiving the target orientation of the accessibility device; illuminating a projector; determining that the accessibility device is in the target orientation; and turning off the projector.

[0013] In this method, target orientation can be received from either a mobile device or a ride-sharing vehicle.

[0014] In this method, the current orientation of the accessibility device can be transmitted to the ride-sharing vehicle.

[0015] The method may include rotating the accessibility device until the accessibility device is in target orientation.

[0016] In this method, illuminating the projector may include illuminating a first light and a second light.

[0017] The method may include a rotational accessibility device until the first and second beams overlap.

[0018] The method may include determining that ride-sharing vehicles are near accessibility devices.

[0019] In this method, the current orientation of the transmission accessibility device and the orientation of the receiving target can occur after it is determined that the ride-sharing vehicle is near the accessibility device.

[0020] The method may include transmitting information about the accessibility device to the mobile device.

[0021] In this method, information about the accessibility device may include the physical characteristics of the accessibility device.

[0022] In this method, the physical characteristic may include at least one of the physical size and weight of the accessibility device. Attached Figure Description

[0023] Figure 1 An exemplary ride-sharing vehicle is shown that communicates with an exemplary mobile device and an exemplary accessibility device via an exemplary ride-sharing server.

[0024] Figure 2 This is a block diagram of exemplary electronic components of an accessibility device for communicating with a mobile device.

[0025] Figures 3A to 3D The diagram illustrates a ride-sharing vehicle accessibility device and how the accessibility device adjusts its orientation to facilitate boarding the ride-sharing vehicle.

[0026] Figure 4 This is a flowchart of an exemplary process that can be performed by one or more components of an accessibility device.

[0027] Figure 5 This is a flowchart of an exemplary process that can be performed by one or more components of a mobile device. Detailed Implementation

[0028] Not all vehicles are suitable for all ride-sharing passengers. For example, a large group of people requesting a ride in a small car may feel uncomfortable. Families with young children will need vehicles with space for car seats and storage (e.g., for strollers). People who need wheelchairs will need a wheelchair-accessible vehicle with space to store their wheelchairs during their commute.

[0029] One solution includes a method executed via a mobile device or another type of computer, which allows a user to request a ride-sharing vehicle that accommodates a wheelchair (hereinafter referred to as an accessibility device). The method may include transmitting a ride-sharing request to a ride-sharing server. The ride-sharing request may include information about the accessibility device. The method may also include determining the current orientation of the accessibility device and transmitting the current orientation of the accessibility device to the ride-sharing vehicle. The information about the accessibility device may include physical characteristics of the accessibility device. These physical characteristics may include at least one of the physical dimensions and weight of the accessibility device. The ride-sharing request may indicate whether a user of the accessibility device needs to use the accessibility device when riding in the ride-sharing vehicle. The method may also include pairing a mobile device with the accessibility device. The method may also include receiving a target orientation from the ride-sharing vehicle. In this case, the method may include transmitting the target orientation to the accessibility device. In some cases, determining the current orientation of the accessibility device may include receiving the current orientation of the accessibility device from the accessibility device. In some exemplary embodiments, the method may include detecting that the ride-sharing vehicle is near the accessibility device. In this case, determining the current orientation of the accessibility device and transmitting the current orientation of the accessibility device to the ride-sharing vehicle can occur after the ride-sharing vehicle is detected to be near the accessibility device.

[0030] Another possible method can be implemented by an accessibility device. The method performed by the accessibility device may include: transmitting the current orientation of the accessibility device; receiving the target orientation of the accessibility device; illuminating a projector; determining that the accessibility device is in the target orientation; and turning off the projector. The target orientation can be received from either a mobile device or a ride-sharing vehicle. The current orientation of the accessibility device may be transmitted to the ride-sharing vehicle. The method may also include rotating the accessibility device until it is in the target orientation. In some exemplary methods, illuminating the projector may include illuminating a first light and a second light. In this example, the method may also include rotating the accessibility device until the first light and the second light overlap. The method may include determining that the ride-sharing vehicle is near the accessibility device. In this case, transmitting the current orientation of the accessibility device and receiving the target orientation occur after determining that the ride-sharing vehicle is near the accessibility device. In some possible implementations, the method may include transmitting information about the accessibility device to the mobile device. The information about the accessibility device may include physical characteristics of the accessibility device. These physical characteristics may include at least one of the physical dimensions and weight of the accessibility device.

[0031] The elements shown may take many different forms and include multiple and / or alternative components and facilities. The exemplary components shown are not intended to be limiting. In practice, additional or alternative components and / or implementations may be used. Furthermore, unless explicitly stated otherwise, the elements shown are not necessarily drawn to scale.

[0032] like Figure 1 As shown, the ride-sharing vehicle 100 communicates with the mobile device 105 and the accessibility device 110 via the ride-sharing server 115.

[0033] Ride-sharing vehicle 100 can be any passenger or commercial vehicle, such as cars, trucks, SUVs, crossovers, vans, minivans, taxis, buses, etc. In some possible ways, ride-sharing vehicle 100 is an autonomous vehicle that can operate in autonomous (e.g., driverless) mode, partially autonomous mode, or non-autonomous mode.

[0034] Mobile device 105 can be any portable computer carried by the user, such as a mobile phone, tablet, laptop, smartwatch, etc. Mobile device 105 may include circuitry and chips that allow it to execute computer code. Mobile device 105 may also include antennas, circuitry, and chips that facilitate wireless communication with ride-sharing vehicle 100 and accessibility device 110 via ride-sharing server 115. Mobile device 105 may include a user interface (e.g., touchscreen, keyboard, keypad, etc.) for receiving user input requesting ride-sharing. This request may indicate whether the user needs to remain in accessibility device 110 during the trip, or whether the user can move to one of the vehicle seats. The user may provide such information to mobile device 105 via the user interface. Mobile device 105 may transmit the ride-sharing request to ride-sharing server 115. Furthermore, as discussed in more detail below, mobile device 105 may retrieve information from accessibility device 110 and send that information along with the ride-sharing request. Mobile device 105 may also send commands received from ride-sharing server 115, ride-sharing vehicle 100, or both to accessibility device 110. Mobile device 105 may also include sensors programmed to detect movement of mobile device 105.

[0035] Accessibility device 110 may be a wheelchair, walking aid, walker, walking frame, etc. Accessibility device 110 may be manually operated or motorized. Accessibility device 110 includes electronic components that allow accessibility device 110 to communicate with mobility device 105 (see [link to mobile device]). Figure 2 Therefore, the accessibility device 110 can communicate indirectly with the ride-sharing vehicle 100. In some cases, the accessibility device 110 can receive instructions from the ride-sharing vehicle 100. These instructions can help the user navigate the accessibility device 110 to the boarding location, orient the accessibility device 110 for easy boarding of the ride-sharing vehicle 100, etc. When the accessibility device 110 is motorized, these instructions can cause the accessibility device 110 to automatically navigate to the boarding location and orient itself relative to the ride-sharing vehicle 100.

[0036] Now for reference Figure 2 The electronic components of the accessibility device 110 may include a motion sensor 120, a communication transceiver 125, a projector 130, a memory 135, and a processor 140.

[0037] Motion sensor 120 is implemented via circuitry, a chip, or other electronic components that detect the motion of accessibility device 110. For example, motion sensor 120 may include an accelerometer, gyroscope, magnetometer, etc. Motion sensor 120 may output a signal representing the motion of accessibility device 110. The motion represented by the signal output by motion sensor 120 may include whether accessibility device 110 is moving forward or backward, moving laterally, turning, traveling on an uneven surface, traveling on a rugged surface, etc. The signal may alternatively or additionally indicate the velocity of accessibility device 110. In some cases, motion sensor 120 may determine the current orientation of accessibility device 110. The current orientation may represent the heading of accessibility device 110 relative to a fixed location (e.g., magnetic north). Motion sensor 120 may output the current orientation to memory 135, processor 140, or both. In some cases, motion sensor 120 may include a position sensor such as a Global Positioning System (GPS) sensor, which can triangulate the position of accessibility device 110 by communicating with a series of satellites in Earth orbit. In this configuration, motion sensor 120 can output the position of accessibility device 110 to memory 135, processor 140, or both. In some possible approaches, accessibility device 110 may include multiple motion sensors 120. If accessibility device 110 has multiple motion sensors 120, not all motion sensors 120 need to be of the same type. Therefore, accessibility device 110 may include any one or more of a position sensor, accelerometer, gyroscope, and magnetometer.

[0038] The transceiver 125 is implemented via an antenna, circuitry, a chip, or other electronic components that facilitate wireless communication between the accessibility device 110 and the mobile device 105, the ride-sharing server 115, the ride-sharing vehicle 100, or combinations thereof. For example, the transceiver 125 may receive requests for information about the accessibility device 110 from the mobile device 105. It may also receive commands from the mobile device 105. These commands may include instructions for boarding the ride-sharing vehicle 100. In some possible implementations, the transceiver 125 may broadcast signals generated by the motion sensor 120, thereby allowing the mobile device 105 to determine, for example, whether the movement of the accessibility device 110 is similar to the movement of the mobile device 105. If so, the mobile device 105 can determine that the user of the mobile device 105 is also using the accessibility device 110. The transceiver 125 can be programmed to communicate according to any number of wired or wireless communication protocols. For example, the transceiver 125 can be programmed according to satellite communication protocols, cellular communication protocols (LTE, 3G, etc.), etc. It communicates using low-power, Ethernet, Controller Area Network (CAN) protocol, WiFi, Local Area Network (LIN) protocol, etc.

[0039] The projector 130 is implemented via one or more light sources, such as one or more light-emitting diodes, light bulbs, etc. The projector 130 illuminates upon receiving a command from, for example, a processor 140. The projector 130 may illuminate a first light 145 indicating the target orientation of the accessibility device 110 and a second light 150 indicating the current orientation of the accessibility device 110. Figure 3C As shown, the first light 145 can emit light at a position on the ground near the accessibility device 110, indicating how far the accessibility device 110 needs to rotate to be in target orientation. Similarly, as... Figure 3C As shown, the second light 150 can emit light on the ground, but can be fixed relative to the accessibility device 110. Therefore, the second light 150 can approach the position of the first light 145 when the accessibility device 110 rotates about a fixed axis. When the first light 145 and the second light 150 are aligned (see...), Figure 3D Accessibility device 110 can be in target orientation. As discussed in more detail below, projector 130 can illuminate a first light 145 and a second light 150 based on commands received from processor 140.

[0040] The memory 135 is implemented via circuitry, a chip, or other electronic components, and may include one or more of the following: read-only memory (ROM), random access memory (RAM), flash memory, electrically programmable memory (EPROM), electrically programmable and erasable memory (EEPROM), embedded multimedia card (eMMC), hard disk drive, or any volatile or non-volatile media. The memory 135 may store instructions and data executable by the processor 140, such as information about the accessibility device 110. Information about the accessibility device 110 may include the type of accessibility device 110 (wheelchair, walking aid, mobility aid, walking frame, etc.), model, unique identifiers such as serial number, physical characteristics such as the physical dimensions (length, width, height, etc.) and weight of the accessibility device 110, current orientation, target orientation received from the ride-sharing vehicle 100, information about the user, or other ride-sharing information that the accessibility device 110 or mobile device 105 can transmit to the ride-sharing server 115, the ride-sharing vehicle 100, or both to facilitate the provision of seating for users of the accessibility device 110. Instructions and data stored in memory 135 may be accessed by processor 140 and other possible components of the accessibility device 110, mobile device 105, ride-sharing vehicle 100, or combinations thereof.

[0041] Processor 140 is implemented via circuitry, chips, or other electronic components and may include one or more microcontrollers, one or more field-programmable gate arrays (FPGAs), one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more client-specific integrated circuits, etc. Processor 140 may be programmed to pair with mobile device 105. Pairing with mobile device 105 may include processor 140 commanding communication transceiver 125 to establish communication with mobile device 105 and periodically exchanging information with mobile device 105. The exchanged information may include information about accessibility device 110 stored in memory 135 or signals captured by motion sensor 120. Processor 140, mobile device 105, or both may compare the signals captured by motion sensor 120 with motion captured by sensors on mobile device 105 to confirm that a person carrying mobile device 105 is also using accessibility device 110. Therefore, when multiple mobile devices 105 and multiple accessibility devices 110 are nearby, the processor 140, mobile device 105, or both can determine which accessibility device 110 and which mobile device 105 the user is currently using, especially if the user owns multiple accessibility devices 110 and multiple mobile devices 105, or if the user rents or borrows accessibility devices 110, in which case the user may not know much about accessibility devices 110.

[0042] Upon receiving a command from mobile device 105, processor 140 may instruct transceiver 125 to transmit information about accessibility device 110 stored in memory 135 to mobile device 105. Mobile device 105 may then incorporate this information into a request to ride-sharing server 115.

[0043] When ride-sharing vehicle 100 is nearby, processor 140 may further instruct mobile device 105 to transmit the current orientation of accessibility device 110 to ride-sharing vehicle 100. Ride-sharing vehicle 100 may respond with a target orientation of accessibility device 110. Target orientation may represent the orientation of accessibility device 110 relative to, for example, a street, which is most suitable for boarding ride-sharing vehicle 100. In some cases, target orientation will orient accessibility device 110 towards (e.g., perpendicular to) the street. Ride-sharing vehicle 100 may determine a target orientation relative to its heading. For example, ride-sharing vehicle 100 may determine a target orientation as, for example, perpendicular to its heading, especially if accessibility device 110, user, or both will board ride-sharing vehicle 100 from the side.

[0044] The processor 140 may be further programmed to respond to commands from the ride-sharing vehicle 100. For example, the ride-sharing vehicle 100 may recommend how to orient the accessibility device 110 to make boarding the ride-sharing vehicle 100 easier. The command may include instructions for orienting the accessibility device 110 relative to the street according to, for example, target orientation. In one possible approach, the processor 140 may be programmed to command a light source to illuminate a first light 145 at a location identified by the ride-sharing vehicle 100. When in target orientation, the location identified by the ride-sharing vehicle 100 may correspond to the heading of the accessibility device 110. The processor 140 may be further programmed to command a second light 150 to illuminate. Using the first light 145 and the second light 150 as guides, a user may manually rotate the accessibility device 110 until the second light 150 overlaps with the first light 145. When the second light 150 overlaps with the first light 145, the accessibility device 110 may be in target orientation for boarding the ride-sharing vehicle 100.

[0045] When the accessibility device 110 is powered on, the processor 140 can output a signal to, for example, an electric motor, causing the accessibility device 110 to rotate until the second light 150 overlaps with the first light 145. The processor 140 can determine the overlap of the second light 150 with the first light 145 based on camera images, feedback from the user (i.e., the processor 140 commands the accessibility device 110 to rotate clockwise or counterclockwise until the user presses a button indicating that the accessibility device 110 should stop), etc. In another possible method, the processor 140 can command a motor to rotate the accessibility device 110 until the current orientation measured by the motion sensor 120 is the target orientation. In this way, the accessibility device 110 can omit the light source, camera, etc.

[0046] Messages (including commands) from ride-sharing vehicle 100 can be received at processor 140 via transceiver 125. In some cases, transceiver 125 receives messages directly from ride-sharing vehicle 100. In other possible implementations, mobile device 105 receives messages directly or via ride-sharing server 115 from ride-sharing vehicle 100, and transceiver 125 receives messages from mobile device 105.

[0047] Figures 3A to 3D An exemplary scenario is illustrated, in which the ride-sharing vehicle 100 facilitates boarding as it approaches the accessibility device 110. Figure 3AIn this scenario, a user will board the ride-sharing vehicle 100 at its designated pick-up location as the ride-sharing vehicle 100 approaches the accessibility device 110. As shown, the accessibility device 110 faces away from the street. Before the ride-sharing vehicle 100 reaches the pick-up location, it exchanges information with the accessibility device 110. This information can be exchanged directly between the accessibility device 110 and the ride-sharing vehicle 100, or via an intermediary device such as a mobile device 105, a ride-sharing server 115, or both. The exchanged information may include the location of the accessibility device 110, its orientation, or any other information output by one or more motion sensors 120. Information such as the type and size of the accessibility device 110 may have been exchanged before the ride-sharing vehicle 100 is very close to the pick-up location. As the ride-sharing vehicle 100 approaches the accessibility device 110, the ride-sharing vehicle 100 can determine from the output of the motion sensor 120 that the accessibility device 110 is not oriented for easy boarding of the ride-sharing vehicle 100. For example... Figure 3B As shown, the ride-sharing vehicle 100 can respond by transmitting a signal with target orientation. The accessibility device 110 responds to this signal by commanding the accessibility device 110 to rotate to the target orientation or by assisting the user in manually rotating the accessibility device 110 to the target orientation via a light source, such as... Figure 3C As shown. For example, as Figure 3C As shown, the light source can illuminate the first light 145 and the second light 150. When the accessibility device 110 is energized, the motor can rotate the accessibility device 110 until the second light 150 overlaps with the first light 145. This overlap can be detected based on camera images, feedback from the user (i.e., the user pressing a button instructing the accessibility device 110 to stop rotating), etc. In another possible method, the motor can continue to rotate the accessibility device 110 until the current orientation measured by the motion sensor 120 matches the target orientation. In this way, the accessibility device 110 can omit the light source, camera, etc. Figure 3C In this example, target orientation will orient the accessibility device 110 toward the street, making it easier for users to access the ride-sharing vehicle 100. The current orientation of the accessibility device 110 is at a certain angle relative to the street, indicated by non-overlapping first light 145 and second light 150. Rotating the accessibility device 110 until the first light 145 and second light 150 overlap will position the accessibility device 110 in target orientation. Figure 3D The accessibility device 110 is shown to be in target orientation after being rotated to make the first light 145 and the second light 150 overlap.

[0048] Figure 4This is a flowchart of an exemplary process 400 that can be performed by the accessibility device 110. Process 400 can begin at any time, such as before the user of the accessibility device 110 is ready to board the ride-sharing vehicle 100.

[0049] In box 405, accessibility device 110 is paired with mobile device 105. For example, processor 140 commands transceiver 125 to establish wireless communication with mobile device 105. Transceiver 125 can communicate via short-range wireless communication protocols such as... or Low-power communication is established with mobile device 105.

[0050] In box 410, accessibility device 110 sends information about accessibility device 110 to mobile device 105. Information about accessibility device 110 may include the type of accessibility device 110 (wheelchair, walking aid, walker, walker frame, etc.), model, unique identifiers such as serial number, physical characteristics such as the physical dimensions and weight of accessibility device 110, current orientation, target orientation received from ride-sharing vehicle 100, information about the user, or other ride-sharing information that accessibility device 110 or mobile device 105 can transmit to ride-sharing server 115, ride-sharing vehicle 100, or both to facilitate providing seating for users of accessibility device 110. Processor 140 can access information from memory 135 and instruct communication transceiver 125 to transmit that information directly or via mobile device 105 to ride-sharing vehicle 100.

[0051] In decision block 415, accessibility device 110 determines whether ride-sharing vehicle 100 is nearby. Processor 140 can determine that ride-sharing vehicle 100 is nearby based on a location signal transmitted from ride-sharing vehicle 100 directly or via ride-sharing server 115, mobile device 105, or both to accessibility device 110. Processor 140 can be programmed to compare the location of ride-sharing vehicle 100 with the location of accessibility device 110. When ride-sharing vehicle 100 is within a predetermined distance (e.g., within a quarter mile, a tenth mile, etc.), processor 140 can determine that ride-sharing vehicle 100 is nearby. Upon determining that ride-sharing vehicle 100 is nearby, process 400 can proceed to block 420. Otherwise, block 415 can continue execution until ride-sharing vehicle 100 is nearby.

[0052] At box 420, accessibility device 110 transmits its current orientation to ride-sharing vehicle 100. The current orientation may represent the heading of accessibility device 110 relative to a fixed location (e.g., magnetic north). Motion sensor 120 may output the current orientation to memory 135, processor 140, or both, and processor 140 may instruct transceiver 125 to transmit the current orientation to ride-sharing vehicle 100 directly or via mobile device 105, ride-sharing server 115, or both.

[0053] At box 425, accessibility device 110 receives target orientation from ride-sharing vehicle 100. Target orientation may represent the orientation of accessibility device 110 relative to, for example, a street, which is most suitable for boarding ride-sharing vehicle 100. Transceiver 125 may receive target orientation from ride-sharing vehicle 100, mobile device 105, or ride-sharing server 115. Target orientation may be transmitted from transceiver 125 to processor 140, memory 135, or both.

[0054] At frame 430, accessibility device 110 can illuminate a light source. Processor 140 can command the light source to illuminate a first light 145 at a location identified by ride-sharing vehicle 100. When in target orientation, the location identified by ride-sharing vehicle 100 can correspond to the heading of accessibility device 110. Processor 140 can further command a second light 150 to illuminate.

[0055] At frame 435, accessibility device 110 can be rotated. Accessibility device 110 can be rotated manually by a user, or processor 140 can command an electric motor to rotate accessibility device 110. The user can manually rotate accessibility device 110 until the second light 150 overlaps with the first light 145. When the second light 150 overlaps with the first light 145, accessibility device 110 is in a target orientation for boarding ride-sharing vehicle 100. With accessibility device 110 powered on, processor 140 can output a signal, for example, to an electric motor, causing accessibility device 110 to rotate until the second light 150 overlaps with the first light 145. Processor 140 can determine the overlap of the second light 150 and the first light 145 based on camera images, feedback from the user (i.e., processor 140 commands accessibility device 110 to rotate clockwise or counterclockwise until the user presses a button indicating that accessibility device 110 should stop), etc. In another possible approach, the processor 140 may command the motor to rotate the accessibility device 110 until the current orientation measured by the motion sensor 120 is the target orientation. In this way, the accessibility device 110 can omit light sources, cameras, etc.

[0056] In decision block 440, accessibility device 110 determines whether it is in target orientation. As described above, processor 140 may determine whether accessibility device 110 is in target orientation based on feedback from the user (e.g., user input), by comparing camera images of first light 145 and second light 150, based on data collected by motion sensor 120, etc. When accessibility device 110 is in target orientation, process 400 may proceed to block 445. Otherwise, block 440 may be repeated until accessibility device 110 is in target orientation.

[0057] At frame 445, accessibility device 110 can turn off projector 130. Processor 140 can be programmed to turn off projector 130 and can send control signals to projector 130. The control signals can cause projector 130 to stop projecting both first light 145 and second light 150.

[0058] Figure 5 This is a flowchart of an exemplary process 500 that can be performed by the mobile device 105. Process 500 can begin at any time, such as before a user of the accessibility device 110 requests a ride to the ride-sharing vehicle 100.

[0059] At box 505, mobile device 105 is paired with accessibility device 110. For example, mobile device 105 can be paired via short-range wireless communication protocols such as... or The low-power establishment and accessibility device 110 enables wireless communication of the communication transceiver 125.

[0060] At box 510, mobile device 105 transmits a ride-sharing request to ride-sharing server 115. Transmitting the ride-sharing request may include wireless communication between mobile device 105 and ride-sharing server 115. The ride-sharing request may identify the pick-up location, the requested destination, and the user's accessibility needs. For example, the ride-sharing request may indicate whether the user needs to remain in accessibility device 110 during the trip, or whether the user can move to one of the vehicle seats. The user may provide such information to mobile device 105 via a user interface. Furthermore, mobile device 105 may retrieve information about accessibility device 110 from accessibility device 110 and send that information along with the ride-sharing request to ride-sharing server 115.

[0061] In decision box 515, mobile device 105 determines whether ride-sharing vehicle 100 is nearby. Mobile device 105 may determine that ride-sharing vehicle 100 is nearby based on location signals transmitted from ride-sharing vehicle 100 to ride-sharing server 115, directly to mobile device 105, or both. Mobile device 105 may be programmed to compare the location of ride-sharing vehicle 100 with the location of mobile device 105. When ride-sharing vehicle 100 is within a predetermined distance (e.g., within a quarter mile, a tenth mile, etc.), mobile device 105 may determine that ride-sharing vehicle 100 is nearby. Upon determining that ride-sharing vehicle 100 is nearby, process 500 may proceed to box 520. Otherwise, box 515 may continue execution until ride-sharing vehicle 100 is nearby.

[0062] At box 520, mobile device 105 receives the current orientation from accessibility device 110 and transmits the current orientation to ride-sharing vehicle 100. Mobile device 105 can determine the current orientation of accessibility device 110 based on communication with accessibility device 110. That is, the transceiver 125 of accessibility device 110 can transmit the current orientation to mobile device 105. As described above, the current orientation can be determined from motion sensor 120 of accessibility device 110. Mobile device 105 can wirelessly transmit the current orientation to ride-sharing vehicle 100, either directly or via ride-sharing server 115.

[0063] At box 525, mobile device 105 receives target orientation from ride-sharing vehicle 100 and transmits the target orientation to accessibility device 110. As previously described, target orientation may represent the orientation of accessibility device 110 relative to, for example, a street, which is most suitable for boarding ride-sharing vehicle 100. Mobile device 105 may wirelessly transmit the target orientation to accessibility device 110.

[0064] Typically, the described computing system and / or device may employ any of many computer operating systems, including, but not limited to, the following versions and / or variants of operating systems: Ford Applications, AppLink / SmartDevice Link middleware, Microsoft Operating system, Microsoft Operating systems, Unix operating systems (e.g., those released by Oracle Corporation on Redwood Coast, California). Operating systems include AIX UNIX (published by International Business Machines, Armonk, New York), Linux, Mac OSX and iOS (published by Apple Inc., Cupertino, California), BlackBerry OS (published by BlackBerry Ltd., Waterloo, Canada), Android (developed by Google Inc.), and Open Handset Alliance (supplied by QNX Software Systems). CAR infotainment platform. Examples of computing devices include, but are not limited to, in-vehicle computers, computer workstations, servers, desktop computers, laptop computers, or handheld computers, or some other computing systems and / or devices.

[0065] Computing devices generally include computer-executable instructions, which can be executed by one or more computing devices (such as those listed above). Computer-executable instructions can be compiled or interpreted from computer programs created using various programming languages ​​and / or technologies, including but not limited to, individually or in combination: Java. TM C, C++, Visual Basic, JavaScript, Perl, etc. Some of these applications can be compiled and executed on virtual machines (such as the Java Virtual Machine, Dalvik Virtual Machine, etc.). Generally, a processor (e.g., a microprocessor) receives instructions from, for example, memory, computer-readable media, etc., and executes those instructions, thereby performing one or more processes, including one or more of those described herein. A variety of computer-readable media can be used to store and transfer such instructions and other data.

[0066] Computer-readable media (also known as processor-readable media) include any non-transitory (e.g., tangible) medium that participates in providing data (e.g., instructions) that can be read by a computer (e.g., by the computer's processor). Such media can take many forms, including but not limited to non-volatile and volatile media. Non-volatile media can include, for example, optical discs or magnetic disks, and other persistent storage. Volatile media can include, for example, dynamic random access memory (DRAM), which typically constitutes main memory. Such instructions can be transmitted by one or more transmission media, including coaxial cables, copper wires, and optical fibers, including wires that include a system bus coupled to the computer's processor. Common forms of computer-readable media include, for example, floppy disks, flexible disks, hard disks, magnetic tape, any other magnetic media, CD-ROMs, DVDs, any other optical media, punched cards, paper tape, any other physical media with a perforated pattern, RAM, PROM, EPROM, FLASH-EEPROM, any other memory chip or cassette tape, or any other medium from which a computer can read.

[0067] The databases, data repositories, or other data stores described herein can include various mechanisms for storing, accessing, and retrieving various types of data, including hierarchical databases, a set of files in a file system, application databases in proprietary formats, relational database management systems (RDBMS), and so on. Each such data store is typically contained within a computing device employing a computer operating system such as one of the operating systems mentioned above, and is accessed via a network in any one or more of various ways. File systems can be accessed through a computer operating system and can include files stored in various formats. In addition to languages ​​used for creating, storing, editing, and executing stored programs (such as PL / SQL mentioned above), RDBMS typically employs Structured Query Language (SQL).

[0068] In some instances, system elements may be implemented as computer-readable instructions (e.g., software) on one or more computing devices (e.g., servers, personal computers, etc.) and stored on an associated computer-readable medium (e.g., disks, storage, etc.). A computer program product may include such instructions stored on a computer-readable medium for performing the functions described herein.

[0069] Regarding the processes, systems, methods, heuristics, etc., described herein, it should be understood that although the steps of such processes are described as occurring according to an ordered sequence, such processes can be practiced with the described steps performed in an order other than that described herein. It should also be understood that some steps may be performed simultaneously, other steps may be added, or some steps described herein may be omitted. In other words, the description of processes herein is provided to illustrate certain embodiments and should in no way be construed as limiting the scope of the claims.

[0070] Therefore, it should be understood that the above description is intended to be illustrative rather than restrictive. Many embodiments and applications beyond the examples provided will become apparent upon reading the above description. The scope should not be determined by reference to the above description, but rather by reference to the appended claims and the full scope of their equivalents. Future developments are envisioned and anticipated in the art discussed herein, and the disclosed systems and methods will be incorporated into such future embodiments. In conclusion, it should be understood that modifications and variations are possible with respect to this application.

[0071] All terms used in the claims are intended to be given their ordinary meaning as understood by one skilled in the art as discussed herein, unless expressly indicated otherwise herein. Specifically, unless expressly limited to the contrary by the claims, the use of singular articles such as “a,” “the,” or “the” should be interpreted as one or more of the elements indicated by the claims.

[0072] The abstract of this specification is provided to allow the reader to quickly determine the nature of this technical disclosure. It should be understood at the time of submission that the abstract will not be used to interpret or limit the scope or meaning of the claims. Furthermore, as can be seen in the above detailed description, various features are combined in different embodiments for the purpose of making the disclosure fluent. This approach of the disclosure should not be construed as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as reflected in the following claims, the inventive subject matter lies in fewer than all features of a single disclosed embodiment. Therefore, the appended claims are hereby incorporated into the detailed description, wherein each claim is independently claimed as a separate subject matter.

Claims

1. A method for ride-sharing accessibility comprising: transmitting a current orientation of an accessibility device relative to a heading of a vehicle; receiving a target orientation of the accessibility device relative to the heading of the vehicle; illuminating a spot light, illuminating the spot light including shining a first light indicating the target orientation of the accessibility device and a second light indicating the current orientation of the accessibility device; rotating the accessibility device until the first light overlaps the second light, indicating that the accessibility device is in the target orientation, the target orientation facilitating the accessibility device boarding the vehicle, the second light being fixed relative to the accessibility device and the accessibility device moving relative to the first light during the rotating; and turning off the spot light.

2. The method of claim 1, wherein the target orientation is received from one of a mobile device and a ride-sharing vehicle.

3. The method of claim 1, wherein the current orientation of the accessibility device is transmitted to a ride-sharing vehicle.

4. The method of claim 1, wherein, the current orientation of the accessibility device is at an angle of inclination relative to a street, and the target orientation is perpendicular to the heading of the vehicle.

5. The method of claim 1, further comprising determining that a ride-sharing vehicle is in the vicinity of the accessibility device.

6. The method of claim 5, wherein transmitting the current orientation of the accessibility device and receiving the target orientation occur after determining that the ride-sharing vehicle is in the vicinity of the accessibility device.

7. The method of claim 1, further comprising transmitting information about the accessibility device to a mobile device.

8. The method of claim 7, wherein the information about the accessibility device includes physical characteristics of the accessibility device.

9. The method of claim 8, wherein the physical characteristics include at least one of a physical size and a weight of the accessibility device.

Images