System and method for determining whether an autonomous vehicle can provide a requested service to an occupant

By considering passenger-related data in the autonomous vehicle system and optimizing vehicle matching and assignment, the problem of passenger-related factors affecting service quality is solved, and service experience and efficiency are improved.

CN111344725BActive Publication Date: 2024-11-26UBER TECHNOLOGIES INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201880072532.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2017-10-25
Filing Date
2018-09-13
Publication Date
2024-11-26
Estimated Expiration
2039-04-03

AI Technical Summary

Technical Problem

In autonomous vehicle systems, service assignments may be undesirable due to factors associated with the occupant (such as the state of the computing device) that may hinder the autonomous vehicle from providing services to the occupant.

Method used

The calculation system obtains the passenger's vehicle service request data, including indications such as battery power and radio performance of the user device, determines whether an autonomous vehicle can be assigned to perform service requests, ensure that the user device is active during the service period, and optimizes vehicle matching to improve the Passenger experience.

Benefits of technology

It improves the experience of autonomous vehicles and provides personalized and smooth interaction, ensures that users receive appropriate vehicle services, optimizes the vehicle assignment process, and improves service efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111344725B_ABST
    Figure CN111344725B_ABST
Patent Text Reader

Abstract

Systems and methods relate to determining whether an autonomous vehicle can be assigned to perform a trip request received from an occupant. In one example, a computer-implemented method for assigning an autonomous vehicle to perform a requested service includes: obtaining, by a computing system including one or more computing devices, a vehicle service request from an occupant. The method further includes: obtaining, by the computing system, data associated with the occupant making the vehicle service request. The method further includes: determining, by the computing system, whether the autonomous vehicle can be assigned to perform the vehicle service request based at least in part on the data associated with the occupant. The method further includes: in response to determining that the autonomous vehicle can be assigned to perform the vehicle service request, providing, by the computing system, the trip request data to the autonomous vehicle.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is based upon and claims the benefit of U.S. application No. 15 / 792,964, filed October 25, 2017, which is based upon and claims the benefit of U.S. provisional application No. 62 / 564,326, filed September 28, 2017, both of which are incorporated herein by reference in their entirety for all purposes. Technical Field

[0002] The present disclosure generally relates to the operation of autonomous vehicles for providing services. More specifically, the present disclosure relates to providing systems and methods for determining whether an autonomous vehicle can be assigned to perform a service requested by a rider. Background Art

[0003] An autonomous vehicle is a vehicle capable of perceiving its environment and navigating with little to no human input. Specifically, an autonomous vehicle can observe its surroundings using various sensors and attempt to understand them by performing various processing techniques on the data collected by the sensors. This can enable autonomous vehicles to navigate without human intervention, and in some cases, without a human driver at all. However, in some cases, providing a requested service to a rider by an autonomous vehicle may not be optimal. For example, factors associated with the rider, such as the state of their computing device, may prevent the autonomous vehicle from being assigned to provide the service. Summary of the Invention

[0004] Aspects and advantages of embodiments of the present disclosure will be set forth in part in the description which follows, or may be learned from the description, or may be learned through practice of the embodiments.

[0005] One exemplary aspect of the present disclosure relates to a computer-implemented method for assigning an autonomous vehicle to perform a requested service. The method includes obtaining, by a computing system comprising one or more computing devices, a vehicle service request from a vehicle occupant. The method further includes obtaining, by the computing system, data associated with the vehicle occupant making the vehicle service request. The method further includes determining, by the computing system, whether the autonomous vehicle can be assigned to perform the vehicle service request based at least in part on the data associated with the vehicle occupant. The method further includes providing, by the computing system, trip request data to the autonomous vehicle in response to determining that the autonomous vehicle can be assigned to perform the vehicle service request.

[0006] The method may further include: wherein obtaining data associated with the occupant making the vehicle service request includes obtaining one or more indications from a user device associated with the occupant. The method may further include: wherein the one or more indications from the user device associated with the occupant include an indication of a remaining battery charge of the user device. The method may further include: wherein determining whether the autonomous vehicle can be assigned to perform the vehicle service request includes determining whether the remaining battery charge of the user device is above a selected threshold. The method may further include: wherein the one or more indications from the user device associated with the occupant include one or more indications regarding radio performance of the user device. The method may further include: wherein obtaining data associated with the occupant making the vehicle service request includes obtaining an occupant profile associated with the occupant making the vehicle service request. The method may further include: wherein the occupant profile includes information regarding the type of vehicle that should be assigned to provide the requested service.

[0007] Another exemplary aspect of the present disclosure relates to a computing system. The computing system includes one or more processors and one or more memories storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations. The operations include obtaining a vehicle service request from a vehicle occupant. The operations further include obtaining data associated with the vehicle occupant making the vehicle service request. The operations further include determining, based at least in part on the data associated with the vehicle occupant, whether an autonomous vehicle can be assigned to perform the vehicle service request. The operations further include providing trip request data to the autonomous vehicle in response to determining that the autonomous vehicle can be assigned to perform the vehicle service request.

[0008] Obtaining data associated with the occupant making the vehicle service request may include obtaining one or more indications from a user device associated with the occupant. The one or more indications from the user device associated with the occupant may include an indication of a remaining battery charge of the user device. Determining whether the autonomous vehicle can be assigned to perform the vehicle service request may include determining whether the remaining battery charge of the user device is above a selected threshold. The one or more indications from the user device associated with the occupant may include one or more indications regarding radio capabilities of the user device. Obtaining data associated with the occupant making the vehicle service request may include obtaining an occupant profile associated with the occupant making the vehicle service request. The occupant profile may include information regarding the type of vehicle that should be assigned to provide the requested service.

[0009] Another exemplary aspect of the present disclosure relates to one or more tangible, non-transitory, computer-readable media storing computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform operations. The operations include obtaining a vehicle service request from an occupant. The operations further include obtaining data associated with the occupant making the vehicle service request. The operations further include determining, based at least in part on the data associated with the occupant, whether an autonomous vehicle can be assigned to perform the vehicle service request. The operations further include providing trip request data to the autonomous vehicle in response to determining that the autonomous vehicle can be assigned to perform the vehicle service request.

[0010] Obtaining data associated with the occupant making the vehicle service request may include obtaining one or more indications from a user device associated with the occupant. The one or more indications from the user device associated with the occupant may include an indication of a remaining battery charge of the user device. Determining whether the autonomous vehicle can be assigned to perform the vehicle service request may include determining whether the remaining battery charge of the user device is above a selected threshold. The one or more indications from the user device associated with the occupant may include one or more indications regarding radio performance of the user device. Obtaining data associated with the occupant making the vehicle service request may include obtaining an occupant profile associated with the occupant making the vehicle service request.

[0011] Other aspects of the disclosure relate to various systems, apparatuses, non-transitory computer-readable media, user interfaces, and electronic devices.

[0012] These and other features, aspects and advantages of the various embodiments of the present disclosure will be better understood with reference to the following description and appended claims.The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the present disclosure and, together with the description, serve to explain the relevant principles. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] With reference to the accompanying drawings, a detailed discussion of the embodiments for those skilled in the art is set forth in the specification, in which:

[0014] Figure 1 A block diagram illustrating an exemplary system for controlling navigation of a vehicle according to an exemplary embodiment of the present disclosure is shown;

[0015] Figure 2 A flowchart illustrating an exemplary method for determining whether to assign an autonomous vehicle to a service request according to an exemplary embodiment of the present disclosure is shown;

[0016] Figure 3 A flowchart illustrating an exemplary method for determining whether to assign an autonomous vehicle to a service request according to an exemplary embodiment of the present disclosure is shown;

[0017] Figure 4 shows an example of an occupant / user profile data structure according to an exemplary embodiment of the present disclosure;

[0018] Figure 5 A block diagram illustrating an exemplary computing system according to exemplary embodiments of the present disclosure is shown; and

[0019] Figure 6 A block diagram of an exemplary system according to an exemplary embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0020] Reference will now be made in detail to the embodiments, one or more examples of which are shown in the accompanying drawings. Each example is provided by way of illustration and does not limit the present disclosure. Indeed, it will be apparent to those skilled in the art that various modifications and variations may be made to the embodiments without departing from the scope of the present disclosure. For example, features shown or described as part of one embodiment may be used in conjunction with another embodiment to produce yet another embodiment. Therefore, it is intended that aspects of the present disclosure cover such modifications and variations.

[0021] An exemplary aspect of the present disclosure relates to determining whether a rider's trip request can be assigned to an autonomous vehicle. Specifically, the systems and methods of the present disclosure can obtain data associated with the rider for use in matching the rider's request with an autonomous vehicle or a human-operated vehicle. The systems and methods of the present disclosure can provide a method for determining an appropriate vehicle to be assigned to provide the requested service.

[0022] Specifically, according to one aspect of the present disclosure, a user (e.g., a rider) may request a vehicle service from an entity, such as a service provider, that maintains a fleet of vehicles, including autonomous vehicles and driver-operated vehicles. The service provider may obtain data associated with the rider that may be used to determine whether an autonomous vehicle or a driver-operated vehicle can be assigned to perform the requested vehicle service. For example, an operational computing system associated with the service provider may obtain data associated with the rider from one or more sources that may be relevant to determining the type of vehicle that can be assigned to perform the requested service. In one example, the operational computing system may obtain one or more indications from a user device associated with the rider that may be relevant to determining the autonomous vehicle assignment. In another example, the operational computing system may also access a user or rider profile associated with the rider and maintained by the service provider, which may include one or more profile attributes or settings that may be relevant to determining the autonomous vehicle assignment.

[0023] More specifically, an entity (e.g., a service provider, an owner, a manager) may use one or more vehicles (e.g., ground vehicles) to provide vehicle services, such as transportation services (e.g., ride-sharing services), courier services, delivery services, etc. The vehicle may be an autonomous vehicle that includes various systems and devices configured to control the operation of the vehicle. For example, an autonomous vehicle may include an onboard vehicle computing system (e.g., located on or within the autonomous vehicle) for operating the vehicle. The vehicle computing system may receive sensor data from sensors onboard the vehicle (e.g., cameras, lidar, radar), attempt to understand the vehicle's surroundings by performing various processing techniques on the sensor data, and generate appropriate motion plans based on the vehicle's surroundings. In addition, the autonomous vehicle may be configured to communicate with one or more computing devices remote from the vehicle. For example, the autonomous vehicle may communicate with an operating computing system that may be associated with the entity. The operating computing system may help the entity monitor, communicate with, manage, and the like its fleet of vehicles. Further, the operating computing system may obtain data associated with the occupant from one or more sources in response to the occupant's service request and consider the data associated with the occupant in determining whether to assign the autonomous vehicle to perform the requested service for the occupant.

[0024] According to an exemplary aspect of the present disclosure, an operational computing system associated with a service provider may receive a request for a vehicle service from a user (e.g., a rider), for example, via a vehicle service application associated with the service provider, the vehicle service application being executed on the rider's user device. The operational computing system may obtain data associated with the rider, which may then be considered by the operational computing system when determining whether an autonomous vehicle may be assigned to perform the requested service for the rider. For example, the data associated with the rider obtained by the operational computing system may inform a determination of whether the rider would be able to complete a trip if an autonomous vehicle were assigned to perform the requested service.

[0025] More specifically, in some embodiments, the operating computing system may obtain data from the occupant's user device that may be relevant to determining whether the autonomous vehicle can be assigned to perform the requested service. For example, the operating computing system may obtain from the occupant's user device an indication of parameters or settings associated with the user device. In some embodiments, the operating computing system may receive an indication of one or more of: location, battery level, radio availability (e.g., Bluetooth availability, Bluetooth Low Energy (BLE) availability, Near Field Communication (NFC) availability, etc.), radio status (e.g., Bluetooth status, BLE status, NFC status, etc.), and / or similar factors to be considered when determining the vehicle to be assigned to provide the requested service to the occupant. In some embodiments, additional data associated with the occupant may also be obtained from the user device for use in determining vehicle assignment, such as the occupant's schedule (e.g., upcoming events), the occupant's social network activity, etc.

[0026] More specifically, in some embodiments, a service provider application running on the rider's user device may provide functionality such as user authentication, vehicle unlock commands, and the like that requires the rider's user device to be active in order to initiate vehicle service at the autonomous vehicle. Accordingly, the operational computing system may obtain an indication of remaining battery charge from the user device to determine that the user device is likely to be operational (e.g., has sufficient remaining battery life so that the user device does not power down before the autonomous vehicle arrives to pick up the rider and begin service) when the autonomous vehicle is dispatched to arrive to initiate the requested service. For example, as part of determining whether the autonomous vehicle can be assigned to perform the requested service, the operational computing system may compare the indication of remaining battery charge to a threshold to determine whether the battery charge is above the threshold.

[0027] In some embodiments, the required battery charge threshold can be determined based on factors associated with the requested service and the availability of the autonomous vehicle. For example, the battery charge threshold can be selected so that the user device will be active for at least a certain period of time after the autonomous vehicle arrives as scheduled to begin the requested service, such that the user device is necessarily active for at least the time the rider boards the vehicle and initiates the requested service. In such cases, the battery charge threshold can be determined based on consideration of the rider's entry time (e.g., the time frame of the autonomous vehicle's arrival and the time frame of the rider entering the vehicle and initiating the service).

[0028] In another example, the battery level threshold can be selected so that the user device will be active throughout the lifecycle of the requested service (e.g., the user device must be active for the duration of the service, from boarding to exiting the vehicle), for example, to ensure that the occupant's user device is active throughout the service to allow interaction between the occupant and the autonomous vehicle. In such cases, the battery level threshold can be determined based on considerations of the autonomous vehicle's entry time and the expected duration of the vehicle service (e.g., taking into account factors such as route, traffic, etc.).

[0029] In some embodiments, a service provider application running on an occupant's user device can use radio (e.g., Bluetooth, etc.) functionality to provide interaction between the service provider application and the autonomous vehicle, for example, to improve the user experience. In such embodiments, the operating computing system can obtain an indication of whether the occupant's user device has radio (e.g., Bluetooth, etc.) functionality and whether the user device's radio (e.g., Bluetooth, etc.) service is active, and take these factors into account when determining whether to assign the autonomous vehicle for the requested service.

[0030] In some embodiments, the operating computing system can obtain driver schedule information to determine whether to assign an autonomous vehicle to provide the requested service. For example, if the rider has an upcoming appointment, the operating computing system can take this into account to allow selection of a vehicle that can provide the rider with the fastest service.

[0031] In some embodiments, the operating computing system may obtain driver social network information to determine whether to assign an autonomous vehicle to provide the requested service. For example, if the requested service is for the rider to attend an event with friends, the operating computing system may take this into account to select a vehicle that can allow the rider's friends to join the trip.

[0032] According to another aspect of the present disclosure, in some embodiments, the operating computing system may additionally or alternatively access an occupant or user profile associated with the rider and maintained by the service provider, which may include one or more profile attributes or settings that may be relevant to determining whether an autonomous vehicle can be assigned to provide the rider with the requested service. For example, the occupant profile may include data related to the rider's comfort level with autonomous vehicles (e.g., first-time or novice rider, experienced rider, does not want autonomous vehicle service, etc.), the type of vehicle the rider typically requests (e.g., wheelchair accessible, extra storage space, etc.), or their use of ride-sharing services. By taking the occupant profile data into account as part of the vehicle determination, the operating computing system can ensure that the appropriate vehicle is assigned to provide the requested service.

[0033] For example, in some embodiments, the operating computing system can determine that the occupant generally desires a vehicle with wheelchair accessibility based on the stored occupant profile settings. Subsequently, the operating computing system can take wheelchair accessibility into account when determining to assign a vehicle to provide the requested service.

[0034] In some embodiments, rider profile attributes or settings may provide default data for use in vehicle assignment determinations. However, rider profile settings may also be overridden based on a specific service request. For example, rider profile data may indicate that the rider is generally willing to move to a designated pickup location to utilize vehicle services, but the rider may indicate in the request that this selection should be modified for the current request (e.g., the rider has a package and does not wish to bring it to the designated pickup location), thereby affecting the determination of which vehicle to assign for the requested service.

[0035] In some embodiments, the operating computing system may determine that the occupant is a first-time autonomous vehicle occupant (or has little experience with autonomous vehicles) and may take this into account when determining which vehicle to assign to provide the requested service. Thus, the operating computing system may take this factor into account in its determination and, for example, assign a vehicle that is more occupant-friendly to provide the requested service (e.g., an autonomous vehicle with a tablet or screen to provide more interaction with the occupant).

[0036] In some embodiments, the operating computing system may determine that the rider is experienced with autonomous vehicles and may take this into account when determining which vehicle to assign to provide the requested service. Thus, the operating computing system may factor this into its determination and, for example, assign a new or different vehicle to provide the rider with the requested service (e.g., allowing the rider to experience different vehicles in the fleet).

[0037] As another example, the occupant profile may indicate that the occupant is uncomfortable with autonomous vehicles, and the operating computing system may take this into account and determine that the autonomous vehicle should not be dispatched, if possible.

[0038] The systems and methods described herein can provide numerous technical effects and benefits. For example, according to the present disclosure, considering occupant data when determining whether to assign an autonomous vehicle to provide vehicle services can enable appropriate vehicle services to be provided to the occupant, thereby improving the autonomous vehicle occupant experience. Incorporating occupant data into the vehicle determination process can also provide the user with a more personalized and improved experience, and can provide the user with a smoother autonomous vehicle interaction. Additionally, considering occupant profile attributes or settings can provide improvements to the occupant-vehicle matching experience and can allow for more contextual determination to tailor vehicle selection based on a specific trip request.

[0039] The systems and methods described herein may also provide improvements to the computing technology required for the operation of autonomous vehicles (e.g., routing and user experience). For example, by using data associated with occupants in vehicle assignment determinations, autonomous vehicles (e.g., vehicle computing systems) may be able to optimize processing and efficiency by ensuring that occupant-vehicle interactions can be performed quickly and efficiently.

[0040] With reference to the accompanying drawings, exemplary embodiments of the present disclosure will be discussed in further detail.

[0041] Figure 1 A block diagram of an exemplary system 100 for controlling navigation of an autonomous vehicle 102 according to an exemplary embodiment of the present disclosure is shown. Autonomous vehicle 102 is capable of sensing its environment and navigating with little or no human input. Autonomous vehicle 102 can be an autonomous vehicle on the ground (e.g., a car, truck, bus, etc.), an autonomous vehicle in the air (e.g., an airplane, drone, helicopter, or other aircraft), or other types of vehicles (e.g., a boat). Autonomous vehicle 102 can be configured to operate in one or more modes, such as a fully autonomous operating mode, a semi-autonomous operating mode, and / or a non-autonomous operating mode. A fully autonomous (e.g., self-driving) operating mode can be a mode in which the autonomous vehicle can provide driving and navigation operations with minimal and / or no interaction from a human driver present in the vehicle. A semi-autonomous (e.g., driver-assisted) operating mode can be a mode in which the autonomous vehicle operates with some interaction from a human driver present in the vehicle.

[0042] Autonomous vehicle 102 may include one or more sensors 104, a vehicle computing system 106, and one or more vehicle controllers 108. Vehicle computing system 106 may assist in controlling autonomous vehicle 102. Specifically, vehicle computing system 106 may receive sensor data from one or more sensors 104, attempt to understand the surrounding environment by performing various processing techniques on the data collected by sensors 104, and generate an appropriate motion path through such surrounding environment. Vehicle computing system 106 may control one or more vehicle control devices 108 to operate autonomous vehicle 102 according to the motion path.

[0043] The vehicle computing system 106 may include one or more processors 130 and at least one memory 132. The one or more processors 130 may be any suitable processing device (e.g., a processor core, a microprocessor, an ASIC, an FPGA, a controller, a microcontroller, etc.), and may be a single processor or multiple processors operatively connected. The memory 132 may include one or more non-transitory computer-readable storage media, such as RAM, ROM, EEPROM, EPROM, flash memory devices, magnetic disks, etc., and combinations thereof. The memory 132 may store data 134 and instructions 136 that, when executed by the processors 130, cause the vehicle computing system 106 to perform operations. In some embodiments, the one or more processors 130 and the at least one memory 132 may be included in one or more computing devices, such as a computing device 129 included within the vehicle computing system 106.

[0044] In some embodiments, vehicle computing system 106 may be further connected to or include a positioning system 120. Positioning system 120 may determine the current geographic location of autonomous vehicle 102. Positioning system 120 may be any device or circuit system for analyzing the location of autonomous vehicle 102. For example, positioning system 120 may determine the actual location or relative location by using a satellite navigation positioning system (e.g., GPS system, Galileo positioning system, Global Navigation Satellite System (GLONASS), BeiDou satellite navigation and positioning system), an inertial navigation system, a dead reckoning system, based on an IP address, by using triangulation and / or proximity to cellular towers or WiFi hotspots, and / or other suitable techniques for determining location. The location of autonomous vehicle 102 may be used by various systems of vehicle computing system 106.

[0045] like Figure 1 As shown, in some embodiments, vehicle computing system 106 may include perception system 110 , prediction system 112 , and motion planning system 114 , which cooperate to perceive the surrounding environment of autonomous vehicle 102 and determine a motion plan for controlling the movement of autonomous vehicle 102 accordingly.

[0046] Specifically, in some embodiments, perception system 110 can receive sensor data from one or more sensors 104 coupled to or otherwise included in autonomous vehicle 102. By way of example, one or more sensors 104 can include a laser detection and ranging (LIDAR) system, a radio detection and ranging (RADAR) system, one or more cameras (e.g., a visible spectrum camera, an infrared camera, etc.), and / or other sensors. The sensor data can include information describing the location of objects within the surrounding environment of autonomous vehicle 102.

[0047] As an example, for a LIDAR system, the sensor data may include the positions of multiple points (e.g., in three-dimensional space relative to the LIDAR system) corresponding to a target that has reflected a ranging laser. For example, a LIDAR system can measure distance by measuring the time of flight (TOF), which is the time it takes for a short laser pulse to travel from the sensor to the target and back, and calculating the distance based on the known speed of light.

[0048] As another example, for a RADAR system, sensor data may include the positions of multiple points (e.g., in three-dimensional space relative to the RADAR system) corresponding to targets that have reflected ranging radio waves. For example, radio waves (pulsed or continuous) transmitted by the RADAR system may be reflected by the target and returned to the RADAR system's receiver, thereby generating information about the target's position and velocity. Thus, the RADAR system can provide useful information about the target's current velocity.

[0049] As yet another example, various processing techniques (e.g., range imaging techniques such as, for example, structure from motion, structured light, stereo triangulation, and / or other techniques) may be performed for one or more cameras to identify the locations of a plurality of points (e.g., in three-dimensional space relative to the one or more cameras) corresponding to an object depicted in images captured by the one or more cameras. Other sensor systems may also identify the locations of points corresponding to the object.

[0050] Thus, one or more sensors 104 may be used to collect sensor data including information describing the locations of points corresponding to objects within the surrounding environment of autonomous vehicle 102 (e.g., in three-dimensional space relative to autonomous vehicle 102).

[0051] In addition to sensor data, perception system 110 may also retrieve or otherwise obtain map data 118, which provides detailed information about the surroundings of autonomous vehicle 102. Map data 118 may provide information regarding: the identification and location of different travel routes (e.g., roads), road segments, buildings, or other objects or targets (e.g., lampposts, crosswalks, curbs, etc.); the location and orientation of travel lanes (e.g., the location and orientation of parking lanes, turn lanes, bike lanes, or other lanes within a particular road or other travel route); traffic control data (e.g., the location and description of signs, traffic lights, or other traffic control devices); and / or any other map data that provides information that helps vehicle computing system 106 understand and perceive its surroundings and its relationship to them.

[0052] Perception system 110 can identify one or more objects in proximity to autonomous vehicle 102 based on sensor data received from one or more sensors 104 and / or map data 118. Specifically, in some embodiments, perception system 110 can determine, for each object, state data describing the current state of the object. By way of example, the state data for each object can describe an estimate of the following state information for the object: current position (also referred to as localization); current speed; current heading (also collectively referred to as velocity); current acceleration; current direction; size / occupancy (e.g., represented by a bounding shape (such as a bounding polygon or polyhedron)); category (e.g., vehicle, pedestrian, bicycle, other); yaw rate, and / or other state information.

[0053] In some embodiments, perception system 110 may determine the state data for each target over multiple iterations. Specifically, perception system 110 may update the state data for each target at each iteration. Thus, perception system 110 may detect and track targets (e.g., vehicles, pedestrians, bicycles, etc.) in proximity to autonomous vehicle 102 over time.

[0054] Prediction system 112 can receive state data from perception system 110 and, based on such state data, predict one or more future locations of each target. For example, prediction system 112 can predict where each target will be in the next 5 seconds, 10 seconds, 20 seconds, and so on. As an example, a target's current velocity can be used to predict that the target will adhere to its current trajectory. As another example, other more complex prediction techniques or modeling can be used.

[0055] Motion planning system 114 may determine a motion plan for autonomous vehicle 102 based at least in part on the predicted one or more future positions of the target provided by prediction system 112 and / or the state data of the target provided by perception system 110. In other words, given information about the current position of the target and / or the predicted future positions of neighboring targets, motion planning system 114 may determine a motion plan for autonomous vehicle 102 that optimally navigates autonomous vehicle 102 relative to the targets at such positions.

[0056] As an example, in some embodiments, motion planning system 114 can determine a cost function for each of one or more candidate motion plans for autonomous vehicle 102 based at least in part on the current location and / or predicted future location of the target. For example, the cost function can describe the cost (e.g., time) of adhering to a particular candidate motion plan. For example, the cost described by the cost function can increase when autonomous vehicle 102 approaches a possible collision with another target and / or deviates from a preferred path (e.g., a pre-approved path).

[0057] Thus, given information about the current location and / or predicted future location of the target, the motion planning system 114 can determine the cost of adhering to a particular candidate path. The motion planning system 114 can select or determine a motion plan for the autonomous vehicle 102 based at least in part on the cost function. For example, the candidate motion plan that minimizes the cost function can be selected or otherwise determined. The motion planning system 114 can provide the selected motion plan to the vehicle controller 116, which controls one or more vehicle control devices 108 (e.g., actuators or other devices that control airflow, acceleration, steering, braking, etc.) to execute the selected motion plan.

[0058] Each of the perception system 110, prediction system 112, motion planning system 114, and vehicle controller 116 may include computer logic for providing the desired functionality. In some embodiments, each of the perception system 110, prediction system 112, motion planning system 114, and vehicle controller 116 may be implemented in hardware, firmware, and / or software that controls a general-purpose processor. For example, in some embodiments, each of the perception system 110, prediction system 112, motion planning system 114, and vehicle controller 116 includes a program file stored on a memory device, loaded into the memory, and executed by one or more processors. In other embodiments, each of the perception system 110, prediction system 112, motion planning system 114, and vehicle controller 116 includes one or more sets of computer-executable instructions stored in a tangible computer-readable storage medium (such as a RAM hard disk or optical or magnetic media).

[0059] Figure 2 A flow chart of an exemplary method 200 for determining whether to assign an autonomous vehicle to a service request according to an exemplary embodiment of the present disclosure is shown. One or more portions of operation 200 may be implemented by one or more computing devices, such as, for example, Figure 1 The vehicle computing system 106, Figure 5 computing system 106 and / or a remote computing system, Figure 6 In addition, one or more parts of the operation 200 can be implemented as the device described herein (for example, Figure 1 、 5 and 6 ) to, for example, provide algorithms for determining whether an autonomous vehicle can be assigned to perform a service requested by a rider.

[0060] At 202, one or more computing devices included in a computing system (e.g., an operating computing system, a service platform system 604, etc.) may obtain a vehicle service request (e.g., a trip request) from a rider. For example, a rider may request vehicle service from a service provider that maintains a fleet of vehicles, including autonomous vehicles and driver-operated vehicles. A computing system associated with the service provider may receive the vehicle service request from the rider, for example, via a vehicle service application associated with the service provider, the vehicle service application being executed on a user device of the rider.

[0061] At 204, the computing system can obtain data associated with the occupant that can be considered when determining whether an autonomous vehicle or a driver-operated vehicle can be assigned to perform the requested vehicle service for the occupant. For example, in some embodiments, the computing system can obtain one or more indications from a user device associated with the occupant that can be relevant to the autonomous vehicle assignment determination. The data associated with the occupant can inform the determination of whether the occupant will be able to complete the trip if the autonomous vehicle is assigned to perform the requested service.

[0062] For example, in some embodiments, the computing system may obtain from the occupant's user device an indication of parameters or settings associated with the user device that may be relevant to determining whether the autonomous vehicle can be assigned to perform the requested service. In some embodiments, the computing system may obtain an indication of one or more of: location, battery level, radio availability (e.g., Bluetooth availability, BLE availability, NFC availability, etc.), radio status (e.g., Bluetooth status, BLE status, NFC status, etc.), and / or similar factors to be considered when determining the vehicle to be assigned to provide the requested service to the occupant. In some embodiments, additional data associated with the occupant may also be obtained from the user device for use in determining vehicle assignment, such as the occupant's calendar (e.g., upcoming events), the occupant's social network activity, etc.

[0063] As another example, in some embodiments, the computing system may additionally or alternatively access a user profile associated with the occupant, maintained by the service provider, and obtain one or more profile attributes or settings that may be relevant to determining whether the autonomous vehicle can be assigned to provide the requested service to the occupant.

[0064] At 206, the computing system may determine whether the autonomous vehicle can be assigned to perform the vehicle service request based at least in part on the data associated with the occupant. For example, in some embodiments, the computing system may compare the data associated with the occupant (such as one or more indications from the occupant's user device regarding parameters or settings associated with the user device) to one or more requirements or thresholds that should be met to allow the autonomous vehicle to be assigned to perform the vehicle service request for the occupant.

[0065] As an example, in some embodiments, a service provider application running on an occupant's user device may provide functionality, such as user authentication, a vehicle unlock command, and the like, that requires the occupant's user device to be in an active state to initiate vehicle service at an autonomous vehicle. Accordingly, the computing system may obtain an indication of remaining battery charge from the occupant's user device to determine that the user device is likely to be operating when the autonomous vehicle is dispatched to arrive to initiate the requested service (e.g., has sufficient remaining battery life so that the user device does not power off before the autonomous vehicle arrives to pick up the occupant and begin the service). In some embodiments, as part of determining whether the autonomous vehicle can be assigned to perform the requested service, the computing system may compare the indication of remaining battery charge from the occupant's user device to a battery threshold to determine whether the battery charge is equal to or above the threshold and, therefore, the user device should be enabled to remain in an active state.

[0066] In some embodiments, a battery threshold can be determined based on factors related to the requested service and the availability of the autonomous vehicle. For example, the battery threshold can be selected so that the user device is active for at least a certain period of time after the autonomous vehicle arrives as scheduled to begin the requested service, ensuring that the user device is active for at least the duration of the occupant's boarding and initiating the requested service. In such cases, the battery threshold can be determined based on consideration of the occupant's entry time (e.g., the timeframe of the autonomous vehicle's arrival and the timeframe of the occupant's entry and initiation of the service). As another example, the battery threshold can be selected so that the user device is active for the entire lifecycle of the requested service (e.g., the user device is active for the duration of the service, from boarding to exiting the vehicle), for example, to ensure that the occupant's user device is active throughout the service, thereby allowing interaction between the occupant and the autonomous vehicle. In such cases, the battery threshold can be determined based on consideration of the autonomous vehicle's entry time and the expected duration of the vehicle's service (e.g., taking into account factors such as route and traffic).

[0067] In some embodiments, a service provider application running on an occupant's user device can use radio (e.g., Bluetooth, BLE, NFC, etc.) functionality to provide interaction between the service provider application and the autonomous vehicle, for example, to improve the user experience. In such embodiments, the computing system can obtain an indication of whether the occupant's user device has the desired radio (e.g., Bluetooth, BLE, NFC, etc.) functionality and whether the user device's radio (e.g., Bluetooth, BLE, NFC, etc.) service is currently active, and take these factors into account when determining whether to assign the autonomous vehicle for the requested service.

[0068] At 208 , if it is determined that the autonomous vehicle can be assigned to provide the requested service to the occupant, then operations continue to 210 . If it is determined at 208 that the autonomous vehicle cannot be assigned to provide the requested service to the occupant, then operations proceed to 212 .

[0069] At 210 , in response to determining that an autonomous vehicle can be assigned to perform the requested service, the computing system can assign an autonomous vehicle to the service request and provide associated request / occupant data to the assigned autonomous vehicle.

[0070] At 212 , in response to determining that the autonomous vehicle cannot be assigned to perform the requested service, the computing system may provide the service request to be accessed by a human driver.

[0071] Figure 3Flowchart showing an exemplary method 300 for determining whether to assign an autonomous vehicle to a service request according to an exemplary embodiment of the present disclosure. One or more portions of operation 300 may be implemented by one or more computing devices, for example, Figure 1 The vehicle computing system 106, Figure 5 computing system 106 and / or a remote computing system, Figure 6 In addition, one or more parts of the operation 300 can be implemented as the device described herein (for example, Figure 1 、 5 and 6 ) to, for example, provide algorithms for determining whether an autonomous vehicle can be assigned to perform a service requested by a rider.

[0072] At 302, one or more computing devices included in a computing system (e.g., an operating computing system, a service platform system 604, etc.) may obtain a vehicle service request (e.g., a trip request) from a rider. For example, a rider may request vehicle service from a service provider that maintains a fleet of vehicles, including autonomous vehicles and driver-operated vehicles. A computing system associated with the service provider may receive the vehicle service request from the rider, for example, via a vehicle service application associated with the service provider, the vehicle service application being executed on a user device of the rider.

[0073] At 304, the computing system may obtain data associated with the occupant, maintained in an occupant profile (e.g., a user profile), which may be considered when determining whether an autonomous vehicle or a driver-operated vehicle can be assigned to perform the requested vehicle service for the occupant. For example, the computing system may access an occupant profile associated with the occupant, maintained by a service provider, and obtain one or more profile attributes or settings from the occupant profile that may be relevant to the autonomous vehicle assignment determination. For example, the occupant profile may include data related to the occupant's comfort / experience level with autonomous vehicles (e.g., first-time or novice occupant, experienced occupant, occupant who does not desire autonomous vehicle services, etc.), the type of vehicle the occupant typically requests (e.g., wheelchair accessibility, additional storage space, vehicle class, etc.), use of ride-sharing services, etc. By taking the occupant profile data into account as part of the vehicle assignment determination, the computing system may ensure that an appropriate vehicle is assigned to provide the requested service.

[0074] In some embodiments, for example, the computing system may determine that the rider generally desires a vehicle that is wheelchair accessible based on stored rider profile settings / attributes. Subsequently, the computing system may take the vehicle's wheelchair accessibility into account when determining to assign a vehicle to provide the requested service. In some embodiments, the rider profile attributes and / or settings may provide default data for use in vehicle assignment determinations. However, the rider profile settings may also be overridden based on a specific service request from the rider. For example, rider profile data may indicate that the rider is generally willing to move to a designated pickup location to use a vehicle service, but the rider may also indicate in the request that this selection should be modified for the current request (e.g., the rider has a package and does not wish to carry it to the designated pickup location), thereby affecting the determination of which vehicle to assign for the requested service.

[0075] As another example, in some embodiments, the computing system may determine, based on the occupant profile data, that the occupant is a first-time autonomous vehicle occupant (or has little experience with autonomous vehicles), and may take this into account when determining which vehicle to assign to provide the requested service. Thus, the computing system may factor this into its determination and, for example, assign a vehicle that is more occupant-friendly to provide the requested service (e.g., an autonomous vehicle with a tablet or screen to provide more interaction with the occupant).

[0076] As another example, in some embodiments, the computing system may determine, based on the occupant profile data, that the occupant is experienced with autonomous vehicles and may take this into account when determining which vehicle to assign to provide the requested service. Thus, the computing system may factor this into its determination and, for example, assign a new or different vehicle to provide the requested service to the occupant (e.g., allowing the occupant to experience different vehicles in the fleet).

[0077] As another example, in some embodiments, the occupant profile may indicate that the occupant is uncomfortable with autonomous vehicles, and the computing system may take this into account and, e.g., determine that the autonomous vehicle should not be assigned to provide the requested service, if possible.

[0078] At 306, the computing system may obtain data associated with the user device of the occupant that may be considered when determining whether an autonomous vehicle or a driver-operated vehicle may be assigned to perform the requested vehicle service for the occupant. For example, the computing system may obtain one or more indications from the user device associated with the occupant that may be relevant to the autonomous vehicle assignment determination. The data associated with the occupant may inform the determination of whether the occupant will be able to complete the trip if the autonomous vehicle is assigned to perform the requested service.

[0079] For example, in some embodiments, the computing system may obtain from the occupant's user device an indication of parameters or settings associated with the user device that may be relevant to determining whether the autonomous vehicle can be assigned to perform the requested service, as described above with respect to Figure 2 As discussed. For example, in some embodiments, the computing system may obtain an indication including one or more of: location, battery level, radio availability (e.g., Bluetooth availability, BLE availability, NFC availability, etc.), radio status (e.g., Bluetooth status, BLE status, NFC status, etc.), and / or similar factors to be considered in determining a vehicle to be assigned to provide the requested service to the occupant. In some embodiments, additional data associated with the occupant may also be obtained from the user device for use in determining vehicle assignment, such as the occupant's schedule (e.g., upcoming events), the occupant's social networking activity, etc.

[0080] At 308, the computing system may determine whether the autonomous vehicle can be assigned to perform the vehicle service request based at least in part on the occupant profile data and the occupant's user device data. For example, in some embodiments, the computing system may compare data associated with the occupant, such as one or more occupant profile settings and / or preferences, with one or more indications from the occupant's user device regarding parameters or settings associated with the user device to determine whether the autonomous vehicle can be assigned to perform the vehicle service request for the occupant.

[0081] At 310 , if it is determined that the autonomous vehicle can be assigned to provide the requested service to the occupant, then operations continue to 312 . If it is determined at 310 that the autonomous vehicle cannot be assigned to provide the requested service to the occupant, then operations proceed to 314 .

[0082] At 312 , in response to determining that an autonomous vehicle can be assigned to perform the requested service, the computing system can assign the autonomous vehicle to the service request and provide the associated request / occupant data to the assigned autonomous vehicle.

[0083] At 314 , in response to determining that the autonomous vehicle cannot be assigned to perform the requested service, the computing system may provide the service request to be accessed by a human driver.

[0084] Figure 4An example of an occupant profile (e.g., user profile) data structure 400 is shown, according to an exemplary embodiment of the present disclosure. Specifically, in some embodiments, an operating computing system (e.g., a computing system of an entity associated with an autonomous vehicle) may generate an occupant profile associated with a particular user. For example, information that may be used in generating and / or maintaining the occupant profile may be collected from one or more application platforms (such as a ride-sharing application platform), from one or more vehicle computing systems, or directly from the user (e.g., via an application user interface presented on a user device). For example, a user may provide user input to a user device to provide information to be stored within the occupant profile. For example, a user profile may be generated for a user, and the occupant profile may be associated with or part of a user account for an application platform, such as a ride-sharing application platform. Additionally, in some embodiments, the application platform may be associated with an entity associated with the autonomous vehicle (e.g., an owner of the autonomous vehicle, a management entity for a fleet of autonomous vehicles, etc.).

[0085] More specifically, Figure 4 An exemplary rider profile data repository 400 is shown that can be used to store preferences / attributes of multiple users related to services associated with an application platform, such as a ride-sharing service. In some embodiments, a user / rider profile can be generated for a user after the user has established a user account on the application platform, and in some embodiments, rider profile data repository 400 can be used to store and organize the user's data.

[0086] like Figure 4 As shown, the rider profile data repository 400 may include one or more rider profiles (e.g., rider profiles 402, 404, and 406) for users of an application platform, such as a ride-sharing platform. Rider profiles 402, 404, 406 may include various data associated with the user and associated with the user's use of services provided by the application platform. For example, in some embodiments, rider profile 402 may include user / rider identification data 408 to uniquely identify the user within the application platform. As an example, the user identification data may be associated with a user account on the application platform and may be securely stored. Rider profiles 404 and 406 may include the same data structure and type as rider profile 402 and therefore will not be described in detail for the sake of brevity.

[0087] Additionally, occupant profile 402 may include various historical data 410 associated with the user's use of services provided by the application platform and autonomous vehicles, such as, for example, previous requests and / or trip history. Occupant profile 402 may include data for a plurality of attributes 412 identifying the user's preferences for selections, settings, and behaviors / operations of autonomous vehicles providing services to the user. By way of example, occupant profile 402 may include a data structure including the name, type, and / or category of each user preference / attribute stored for the user, an indication of the settings for each user preference / attribute, and, in some cases, one or more conditions associated with the user preference / attribute.

[0088] Specifically, for each user preference / attribute stored for the user, the occupant profile 402 may include one or more indications of the user's preferred settings. For example, the occupant profile may include preferences or attributes for one or more of: vehicle setup, driving, driving characteristics, autonomous vehicle experience level, route preferences, parking, driving mode, preferred vehicle type, vehicle accessibility requirements, etc.

[0089] Additionally, in some embodiments, the occupant profile 402 may include one or more conditions associated with one or more user preferences / attributes. For example, in some embodiments, the occupant profile 402 may include date and time of day information associated with one or more user preferences / attributes, such as preferences associated with work commutes versus preferences associated with social trips, weekday preferences versus weekend preferences, etc. As another example, the occupant profile 402 may also include seasonal information / conditions associated with one or more user preferences / attributes, such as vehicle environment preferences during winter versus vehicle environment preferences during summer, etc.

[0090] In some embodiments, a computing system associated with a service provider can access an occupant profile maintained in an occupant profile data store 400 associated with an occupant requesting a vehicle service and obtain one or more profile attributes or settings 412 that can be relevant to determining whether an autonomous vehicle can be assigned to provide the requested service to the occupant. For example, the occupant profile can include data related to the occupant's comfort / experience level with autonomous vehicles (e.g., first-time or novice occupant, experienced occupant, occupant who does not want autonomous vehicle service, etc.), the type of vehicle the occupant typically requests (e.g., wheelchair accessible, with additional storage space, etc.), whether the occupant uses a ride-sharing service, etc. By taking the occupant profile data into account as part of the vehicle determination, the computing system can ensure that an appropriate vehicle is assigned to provide the requested service.

[0091] In some embodiments, profile attributes or settings 412 may provide default data for use in vehicle assignment determinations, however, such default profile settings may be overridden based on the rider's specific service request. For example, profile data may indicate that the rider is generally willing to move to a designated pickup location to utilize vehicle services, but the rider may also indicate in the request that this selection should be modified for the current request (e.g., the rider has a package and does not wish to bring it to the designated pickup location), thereby affecting the determination of which vehicle to assign for the requested service.

[0092] As another example, in some embodiments, the computing system may determine, based on the profile data, that the occupant is a first-time autonomous vehicle occupant (or has little experience with autonomous vehicles), and may take this into account when determining which vehicle to assign to provide the requested service. Thus, the computing system may factor this into its determination and, for example, assign a vehicle that is more occupant-friendly to provide the requested service (e.g., an autonomous vehicle with a tablet or screen to provide more interaction with the occupant).

[0093] As another example, in some embodiments, the computing system may determine, based on the profile data, that the rider is experienced with autonomous vehicles and may take this into account when determining which vehicle to assign to provide the requested service. Accordingly, the operating computing system may factor this into the determination and, for example, assign a new or different vehicle to provide the rider with the requested service (e.g., allowing the rider to experience different vehicles in the fleet).

[0094] Figure 5 A block diagram of an exemplary computing system 500 is shown, according to an exemplary embodiment of the present disclosure. Figure 5 The exemplary computing system 500 shown in FIG. 5 is provided by way of example only. Figure 5 The components, systems, connections, and / or other aspects shown in the drawings are optional and are provided as examples of possible, but not required, implementations of the present disclosure. Exemplary computing system 500 may include vehicle computing system 106 of autonomous vehicle 102 and, in some embodiments, a remote computing system 510 comprising a remote computing device (e.g., an operating computing system) remote from autonomous vehicle 102 that may be communicatively coupled to one another via one or more networks 520. Remote computing system 510 may be associated with a central operating system and / or an entity associated with autonomous vehicle 102, such as a vehicle owner, a vehicle manager, a fleet operator, a service provider, and the like.

[0095] The computing device 129 of the vehicle computing system 106 may include a processor 502 and a memory 504. The one or more processors 502 may be any suitable processing device (e.g., a processor core, a microprocessor, an ASIC, an FPGA, a controller, a microcontroller, etc.), and may be a single processor or multiple processors operatively connected. The memory 504 may include one or more non-transitory computer-readable storage media, such as RAM, ROM, EEPROM, EPROM, one or more memory devices, a flash memory device, etc., and combinations thereof.

[0096] Memory 504 can store information accessible by one or more processors 502. For example, memory 504 (e.g., one or more non-transitory computer-readable storage media, memory devices) onboard autonomous vehicle 102 can include computer-readable instructions 506 that are executable by one or more processors 502. Instructions 506 can be software written in any suitable programming language or can be implemented in hardware. Additionally or alternatively, instructions 506 can be executed on processor 502 in logically and / or virtually independent threads.

[0097] For example, memory 504 onboard autonomous vehicle 102 may store instructions 506 that, when executed by one or more processors 502 onboard autonomous vehicle 102, cause one or more processors 502 (vehicle computing system 106) to perform operations, such as any of the operations and functions of computing device 129 described herein or for which computing device 129 is configured, including, for example Figure 2 and / or Figure 3 operation.

[0098] Memory 504 can store data 508, which can be acquired, received, accessed, written, manipulated, created, and / or stored. Data 508 can include, for example, sensor data, map data, data identifying detected objects including current object states and predicted object positions and / or trajectories, service request data (e.g., trip and / or user data), motion plans, etc., as described herein. In some embodiments, computing device 129 can obtain data from one or more memory devices remote from autonomous vehicle 102.

[0099] Computing device 129 may also include one or more communication interfaces 509 for communicating with one or more other systems onboard autonomous vehicle 102 and / or remote computing devices located remote from autonomous vehicle 102 (e.g., remote computing system 510). Communication interface 509 may include any circuitry, components, software, etc. for communicating with one or more networks (e.g., 520). In some embodiments, communication interface 509 may include, for example, one or more of a communication controller, a receiver, a transceiver, a transmitter, a port, a conductor, software, and / or hardware for transmitting data.

[0100] In some embodiments, vehicle computing system 106 may further include a positioning system 512. Positioning system 512 may determine the current location of autonomous vehicle 102. Positioning system 512 may be any device or circuitry for analyzing the location of autonomous vehicle 102. For example, positioning system 512 may determine location using one or more inertial sensors, a satellite positioning system, based on an IP address, by using triangulation and / or proximity relative to a network access point or other network component (e.g., a cellular tower, a WiFi access point, etc.), and / or other suitable techniques. The location of autonomous vehicle 102 may be used by various systems of vehicle computing system 106.

[0101] The network 520 can be any type of network or combination of networks that allows communication between devices. In some embodiments, the network can include one or more of a local area network, a wide area network, the Internet, a secure network, a cellular network, a mesh network, a peer-to-peer communication link, and / or some combination thereof, and can include any number of wired or wireless links. Communication on the network 520 can be accomplished, for example, via a communication interface using any type of protocol, protection scheme, encoding, format, encapsulation, etc.

[0102] Remote computing system 510 may include one or more remote computing devices that are remote from vehicle computing system 106. The remote computing devices may include components similar to those described herein for computing device 129 (e.g., processors, memory, instructions, data, etc.). Furthermore, remote computing system 510 may be configured to perform one or more operations of operating a computing system as described herein, including, for example, Figure 2 and / or Figure 3 operation.

[0103] Figure 6 A block diagram of an exemplary system 600 is shown, according to an exemplary embodiment of the present disclosure. Figure 6 The exemplary system 600 shown in FIG. 6 is provided by way of example only. Figure 6 The components, systems, connections, and / or other aspects shown in the drawings are optional and are provided as examples of possible, but not required, implementations of the present disclosure. Figure 6An exemplary system 600 is shown including a service platform system 604 , a vehicle computing system 606 , and a user device 602 , which may be communicatively coupled to one another via one or more networks 608 and may provide one or more operations according to exemplary embodiments of the systems and methods of the present disclosure.

[0104] As shown, user device 602 can provide a user with access to an application platform, such as a ride-sharing platform, maintained by a service provider, and allow the user to establish / maintain a user account for the application platform, request services associated with the application platform, and / or establish / maintain a rider profile including preferences for the services provided. User device 602 can be any type of computing device, such as, for example, a personal computing device (e.g., a laptop computer, a desktop computer, etc.), a mobile computing device (e.g., a smartphone, a tablet computer, etc.), a game console or controller, a wearable computing device, an embedded computing device, a personal assistant computing device, or any other type of computing device.

[0105] More specifically, the user device 602 may include one or more processors 610 and at least one memory 612. The one or more processors 610 may be any suitable processing device (e.g., a processor core, a microprocessor, an ASIC, an FPGA, a controller, a microcontroller, etc.), and may be a single processor or multiple processors operably connected. The memory 612 may include one or more non-transitory computer-readable storage media, such as RAM, ROM, EEPROM, EPROM, flash memory devices, disks, etc., and combinations thereof. The memory 612 may store data 614 and computer-readable instructions 616 that, when executed by the processor 610, cause the user device 602 to perform operations such as those described herein. The instructions 616 may be software written in any suitable programming language, or may be implemented in hardware. Additionally or alternatively, the instructions 616 may be executed on the processor 610 as logically and / or virtually independent threads.

[0106] In some embodiments, the one or more processors 610 and the at least one memory 612 may be included in one or more computing devices within the user device 602. In some embodiments, the user device 602 may obtain data from one or more memory devices that are remote from the user device 602.

[0107] The user device 602 may also include one or more input / output interfaces 620 that may be used to receive input, such as from a user, and provide output, such as for display and / or playback, to the user. The input / output interfaces 620 may include, for example, devices for receiving information from a user or providing information to a user, such as a display device, a touch screen, a touchpad, a mouse, data input keys, an audio output device, such as one or more speakers, a microphone, a tactile feedback device, and the like. The input / output interfaces 620 may be used, for example, by a user to control the operation of the user device 602.

[0108] The user device 602 may also include one or more communication interfaces 618 for communicating with one or more systems or devices, including systems or devices remotely located from the user device 602, such as the service platform system 604 and / or the like. The communication interface 618 may include any circuitry, components, software, etc. for communicating with one or more networks (e.g., network 608). In some embodiments, the communication interface 618 may include, for example, one or more of a communication controller, a receiver, a transceiver, a transmitter, a port, a conductor, software, and / or hardware for transmitting data.

[0109] The network 608 can be any type of network or combination of networks that allows communication between devices. In some embodiments, the network can include one or more of a local area network, a wide area network, the Internet, a secure network, a cellular network, a mesh network, a peer-to-peer communication link, and / or some combination thereof, and can include any number of wired or wireless links. Communication on the network 608 can be accomplished, for example, via a communication interface using any type of protocol, protection scheme, encoding, format, encapsulation, etc.

[0110] As further shown, system 600 may include a service platform system 604 that can provide services for application platforms maintained by service providers such as ride-sharing platforms. For example, service platform system 604 can communicate with one or more user devices 602 to provide users with access to application platforms. Service platform system 604 can also communicate with one or more vehicle computing systems 606 to provide services associated with application platforms such as ride-sharing platforms, delivery service platforms, courier service platforms, and / or other service platforms. Service platform system 604 can be associated with a central operating system and / or entities associated with autonomous vehicles and / or application platforms, such as, for example, vehicle owners, vehicle managers, fleet operators, service providers, and the like.

[0111] More specifically, the service platform system 604 may include one or more computing devices 605 for performing operations associated with the application platform. The computing device 605 may include one or more processors 622 and at least one memory 624. The one or more processors 622 may be any suitable processing device (e.g., a processor core, a microprocessor, an ASIC, an FPGA, a controller, a microcontroller, etc.), and may be a single processor or multiple processors operatively connected. The memory 624 may include one or more non-transitory computer-readable storage media, such as RAM, ROM, EEPROM, EPROM, flash memory devices, magnetic disks, etc., and combinations thereof.

[0112] The memory 624 may store data 626 and computer-readable instructions 628 that, when executed by the processor 622, cause the computing device 605 to perform operations such as those described herein. The instructions 628 may be software written in any suitable programming language, or may be implemented in hardware. Additionally or alternatively, the instructions 628 may be executed on the processor 622 in logically and / or virtually independent threads. For example, the memory 624 may store instructions 628 that, when executed by the one or more processors 622, cause the one or more processors 622 to perform any of the operations and / or functions described herein, including, for example, Figure 2 and / or Figure 3 Additionally, in some embodiments, the memory 624 can store data 626, which can include data such as described herein, and the service platform system 604 can provide at least a portion of the data to one or more remote computing systems, such as, for example, a vehicle computing system in an autonomous vehicle (e.g., Figure 1 vehicle computing system 106) and / or user device 602.

[0113] In some embodiments, the one or more processors 622 and the at least one memory 624 may be included in one or more computing devices within the service platform system 604. In some embodiments, the service platform system 604 may obtain data from one or more memory devices that are remote from the service platform system 604.

[0114] The one or more computing devices 605 included in the service platform system 604 may also include one or more input / output interfaces 632, which may be used to receive input, such as from a user, and provide output, such as for display and / or playback, to the user. The input / output interfaces 632 may include, for example, devices for receiving information from a user or providing information to a user, such as a display device, a touch screen, a touchpad, a mouse, data input keys, an audio output device such as one or more speakers, a microphone, a tactile feedback device, etc. The input / output interfaces 632 may be used, for example, by a user to control the operation of the computing device 605 included in the service platform system 604.

[0115] The computing device 605 may also include one or more communication interfaces 630 for communicating with one or more systems or devices, including systems or devices remotely located from the computing device 605, such as the user device 602, the vehicle computing system 606, and / or the like. The communication interface 630 may include any circuitry, components, software, etc. for communicating with one or more networks (e.g., the network 608). In some embodiments, the communication interface 630 may include, for example, one or more of a communication controller, a receiver, a transceiver, a transmitter, a port, a conductor, software, and / or hardware for transmitting data.

[0116] In some embodiments, the service platform system 604 may include one or more server computing devices. If the service platform system 604 includes multiple server computing devices, such server computing devices may operate according to various computing architectures, including, for example, sequential computing architectures, parallel computing architectures, or some combination thereof.

[0117] As further shown, the system 600 may include a vehicle computing system 606 (e.g., included in a computer system such as Figure 1 In some embodiments, vehicle computing system 606 can perform autonomous vehicle motion planning and implement operations of the autonomous vehicle, as described herein.

[0118] More specifically, vehicle computing system 606 may include one or more computing devices 607 for performing operations associated with the autonomous vehicle. Computing device 607 may include one or more processors 634 and at least one memory 636. One or more processors 634 may be any suitable processing device (e.g., a processor core, a microprocessor, an ASIC, an FPGA, a controller, a microcontroller, etc.), and may be a single processor or multiple processors operatively connected. Memory 636 may include one or more non-transitory computer-readable storage media, such as RAM, ROM, EEPROM, EPROM, flash memory devices, magnetic disks, etc., and combinations thereof.

[0119] The memory 636 may store data 638 and computer-readable instructions 640 that, when executed by the processor 634, cause the computing device 607 to perform operations such as those described herein, including providing operation of the autonomous vehicle to, for example, provide requested services to the occupants. The instructions 640 may be software written in any suitable programming language, or may be implemented in hardware. Additionally or alternatively, the instructions 640 may be executed on the processor 634 in logically and / or virtually independent threads. For example, the memory 636 may store instructions 640 that, when executed by the one or more processors 634, cause the one or more processors 634 to perform any of the operations and / or functions described herein, including, for example, Figure 2 and / or Figure 3 One or more operations.

[0120] In some embodiments, the one or more processors 634 and the at least one memory 636 may be included in one or more computing devices within the vehicle computing system 606. In some embodiments, the vehicle computing system 606 may obtain data from one or more memory devices that are remote from the vehicle computing system 606.

[0121] The one or more computing devices 607 included in the vehicle computing system 606 may also include one or more input / output interfaces 644 that may be used to receive input, such as from a user, and provide output to the user, such as for display and / or playback. The input / output interfaces 644 may include, for example, devices for receiving information from a user or providing information to a user, such as a display device, a touch screen, a touchpad, a mouse, data input keys, an audio output device such as one or more speakers, a microphone, a tactile feedback device, etc. The input / output interfaces 644 may be used, for example, by a user to control the operation of the computing device 607 included in the vehicle computing system 606.

[0122] Computing device 607 may also include one or more communication interfaces 642 for communicating with one or more systems or devices, including systems and devices onboard the autonomous vehicle and systems or devices remote from computing device 607 and / or the autonomous vehicle, such as service platform system 604, user device 602, and / or the like. Communication interface 642 may include any circuitry, components, software, etc. for communicating with one or more networks (e.g., network 608). In some embodiments, communication interface 642 may include, for example, one or more of a communication controller, a receiver, a transceiver, a transmitter, a port, a conductor, software, and / or hardware for transmitting data.

[0123] Computing tasks discussed herein as being performed at a computing device remote from the vehicle may alternatively be performed at the vehicle (e.g., via the vehicle computing system), and vice versa. Such configurations may be implemented without departing from the scope of this disclosure. The use of computer-based systems allows for a variety of possible configurations, combinations, and divisions of tasks and functions between and within components. Computer-implemented operations may be performed on a single component or on multiple components. Computer-implemented tasks and / or operations may be performed sequentially or in parallel. Data and instructions may be stored in a single memory device or on multiple memory devices.

[0124] Although the subject matter has been described in detail with respect to various specific exemplary embodiments of the subject matter, each example is provided as an explanation of the present disclosure, not as a limitation. After understanding the foregoing, those skilled in the art can easily obtain changes, modifications and equivalents to such embodiments. Therefore, the present disclosure does not exclude the inclusion of such modifications, modifications and / or additions to the subject matter, as this is obvious to those of ordinary skill in the art. For example, a feature shown or described as part of one embodiment can be used together with another embodiment to produce yet another embodiment. Therefore, it is intended that the present disclosure cover such changes, modifications and equivalents.

Claims

1. A computer-implemented method for assigning an autonomous vehicle to perform a requested service, comprising: Obtaining, by a computing system comprising one or more computing devices, a vehicle service request from a vehicle occupant; in response to receiving the vehicle service request, obtaining, by the computing system, data indicating a remaining battery charge of a user device associated with the vehicle occupant making the vehicle service request, wherein the data is further related to determining a type of vehicle to be assigned to perform the requested service, the type of vehicle associated with managing a plurality of vehicles; determining, by the computing system, whether the remaining battery charge of the user device is above a battery threshold to determine whether the vehicle service request can be assigned to the autonomous vehicle; as well as By the computing system, in response to determining that the remaining battery power of the user device is above the battery threshold, the autonomous vehicle is assigned to perform the vehicle service request, or in response to determining that the remaining battery power of the user device is not above the battery threshold, a human-operated vehicle is assigned to perform the vehicle service request.

2. The computer-implemented method of claim 1 , further comprising: Data indicative of an occupant profile associated with the occupant making the vehicle service request is obtained by the computing system. 3 . The computer-implemented method of claim 2 , wherein the data indicative of the occupant profile includes information regarding a type of vehicle that can be assigned to provide the requested service.

4. The computer-implemented method of claim 1 , further comprising: Data indicative of a status of a radio of the user device is obtained by the computing system.

5. The computer-implemented method of claim 4, wherein the radio comprises near field communication (NFC).

6. The computer-implemented method of claim 4, further comprising: A determination is made, by the computing system, whether the radio is in an active state based at least in part on the data indicative of the state of the radio.

7. The computer-implemented method of claim 6, further comprising: The autonomous vehicle is assigned, by the computing system, to perform the vehicle service request in response to determining that the radio is active, or the human-operated vehicle is assigned in response to determining that the radio is not active.

8. A computing system comprising: one or more processors; and one or more memories comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: Obtaining a vehicle service request from a passenger; in response to receiving the vehicle service request, obtaining data indicative of a remaining battery charge of a user device associated with the vehicle occupant making the vehicle service request, wherein the data is further related to determining a type of vehicle to be assigned to perform the requested service, the type of vehicle associated with managing a plurality of vehicles; determining whether the remaining battery charge of the user device is above a battery threshold to determine whether the vehicle service request can be assigned to an autonomous vehicle; as well as In response to determining that the remaining battery charge of the user device is above the battery threshold, assigning the autonomous vehicle to perform the vehicle service request, or in response to determining that the remaining battery charge of the user device is not above the battery threshold, assigning a human-operated vehicle to perform the vehicle service request.

9. The computing system of claim 8, wherein the operations further comprise: Data indicative of an occupant profile associated with the occupant making the vehicle service request is obtained.

10. The computing system of claim 9, wherein the data indicative of the occupant profile includes information regarding a type of vehicle that can be assigned to provide the requested service.

11. The computing system of claim 8, wherein the operations further comprise: The battery threshold is determined based at least in part on one or more factors associated with the requested service.

12. The computing system of claim 8, wherein the battery threshold is determined such that the user device will be active during at least a predetermined amount of time after the autonomous vehicle is scheduled to arrive to initiate the requested service.

13. The computing system of claim 12, wherein the predetermined amount of time corresponds to an amount of time required for the autonomous vehicle to complete the requested service.

14. The computing system of claim 8, further comprising: obtaining data indicative of an electronic calendar associated with the occupant making the vehicle service request; as well as A determination is made as to whether the vehicle service request is assignable to the autonomous vehicle based at least in part on the data indicative of the electronic calendar.

15. One or more tangible, non-transitory computer-readable media storing computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising: Obtaining a vehicle service request from a passenger; in response to receiving the vehicle service request, obtaining data indicative of a remaining battery charge of a user device associated with the vehicle occupant making the vehicle service request, wherein the data is further related to determining a type of vehicle to be assigned to perform the requested service, the type of vehicle associated with managing a plurality of vehicles; determining whether the remaining battery charge of the user device is above a battery threshold to determine whether the vehicle service request can be assigned to an autonomous vehicle; In response to determining that the remaining battery charge of the user device is above the battery threshold, assigning the autonomous vehicle to perform the vehicle service request, or in response to determining that the remaining battery charge of the user device is not above the battery threshold, assigning a human-operated vehicle to perform the vehicle service request.

16. The one or more tangible, non-transitory computer-readable media of claim 15, wherein the operations further comprise: Data indicative of an occupant profile associated with the occupant making the vehicle service request is obtained.

17. The one or more tangible, non-transitory computer-readable media of claim 15, the operations further comprising: Data indicative of a status of a radio of the user device is obtained.

18. The one or more tangible, non-transitory computer-readable media of claim 17, the operations further comprising: Based at least in part on the data indicative of the state of the radio, a determination is made as to whether the radio is in an active state or an inactive state.

19. The one or more tangible, non-transitory computer-readable media of claim 18, the operations further comprising: In response to determining that the radio is active, assigning the autonomous vehicle to perform the vehicle service request, or in response to determining that the radio is not active, assigning the human-operated vehicle to perform the vehicle service request.

20. The one or more tangible, non-transitory computer-readable media of claim 15, wherein the operations further comprise: The battery threshold is determined based at least in part on one or more factors associated with the requested service.