JP2023541968A - Vehicle dispatch in the mobile ecosystem - Google Patents

Abstract

A mobile ecosystem is disclosed that includes a vehicle having an autonomous control system configured to obtain vehicle information including a vehicle location of the vehicle and obtain user information including a user location of a user device. Based on a cost function that uses the user information to estimate a confidence value above a confidence threshold, the autonomous control system determines that the user of the user device is ready for pick-up by a vehicle and uses the user information and Based on the vehicle information, a pick-up position for the vehicle can be identified and a trajectory from the vehicle position to the pick-up position can be determined. The vehicle includes a propulsion system configured to move the vehicle from a vehicle location toward a pick-up location according to a trajectory.

Description

TECHNICAL FIELD This disclosure relates generally to vehicle dispatch, and specifically to the use of a mobile ecosystem to support vehicle dispatch decisions in a mobile ecosystem.

Hailing a rideshare vehicle or other third party hire vehicle using existing application technology can be an overly complex procedure. Details that the user needs to input into the rideshare algorithm include the user's current location, desired pick-up location, desired pick-up time, user preferences for vehicle type, etc. Additionally, ride dispatch procedures often require additional interaction between both parties via text or phone calls. This is because, despite the user and driver entering a set of parameters, one party may not be able to easily locate the other party for the requested pick-up. In addition, the user of the rideshare vehicle or third party vehicle can tell the rideshare vehicle driver when to call the rideshare vehicle and where to be picked up to avoid long wait times at the pick up location. Various factors need to be considered, such as how long it will take both the user and the rideshare vehicle to travel to the pick-up location, for example, based on traffic conditions or other navigational obstacles.

Disclosed herein are embodiments of vehicle dispatch in a mobile ecosystem.

In a first aspect, a mobile ecosystem includes a user device in communication with a network and a vehicle having an autonomous control system in communication with the network. At least one of the user device, the vehicle, or the network receives user information from the user device, receives vehicle information from the vehicle, and determines that the user is ready to be picked up based on the user information. , is operable to identify rendezvous based on user information and vehicle information. The autonomous control system of the vehicle is operable to move the vehicle to the appointment in response to determining that the user is ready to be picked up.

In a first aspect, the user information includes at least one of user approval, user location, calendar information, biometric information, purchase history information, user environment information, location history information, or user preference information. Determining that the user is ready to be picked up includes receiving a user authorization from the user device. The vehicle information includes at least one of vehicle location, traffic information, current vehicle configuration, or staging location. The meeting includes at least one of a pick-up location, a pick-up time, or a pick-up vehicle configuration. The vehicle's autonomous control system is operable to cause the vehicle to change from a current vehicle configuration to a pick-up vehicle configuration when the vehicle arrives at the appointment. Determining that the user is ready to be picked up includes estimating a confidence value that is greater than a confidence threshold of the cost function. The cost function is based on user information. Changes in reliability values are based on changes in user information. The user device, vehicle, or network determines, based on the user information, that the user is ready for the vehicle to track the user, and performs tracking for the vehicle based on the user information and the vehicle information. It is operable to identify a route and cause the vehicle to travel along the tracked route. Determining that the user is ready for the vehicle to track the user includes estimating a confidence value that is below a confidence threshold of the cost function. The cost function is based on user information, and the change in confidence value is based on the change in user information. The first aspect may include any combination of the features described in this paragraph.

In a second aspect, a vehicle includes an autonomous control system configured to obtain vehicle information including a vehicle location of the vehicle and obtain user information including a user location of a user device. Based on a cost function that uses the user information to estimate a confidence value that is above a confidence threshold, the autonomous control system determines that the user of the user device is ready to be picked up by a vehicle and uses the user information and the vehicle information, the vehicle is configured to identify a pickup location for the vehicle and determine a trajectory from the vehicle location to the pickup location. The vehicle includes a propulsion system configured to move the vehicle from a vehicle position toward a pick-up position according to a trajectory.

In a second aspect, the vehicle information includes at least one of traffic information, current vehicle configuration, or staging location. The user information includes at least one of calendar information, biometric information, purchase history information, user environment information, location history information, or user vehicle configuration. The autonomous control system is configured to cause the vehicle to change from a current vehicle configuration to a user vehicle configuration at the pickup location based on a cost function that estimates a reliability value that is greater than a reliability threshold. The trajectory includes a departure time from the vehicle location, a route for the vehicle to travel between the vehicle location and the pick-up location, and an arrival time at the pick-up location. Determining that a user of a user device is ready to be picked up by a vehicle includes receiving authorization information from the user device authorizing the pickup. Based on the cost function estimating a confidence value below a confidence threshold, the autonomous control system determines that the user is ready for the vehicle to track the user based on the user information; The system is configured to identify a tracking route for the vehicle or a staging location for the vehicle based on the user information and the vehicle information, and to cause the vehicle to travel along the tracking route or move to the staging location. The second aspect may include any combination of the features described in this paragraph.

In a third aspect, a method for dispatching a vehicle includes obtaining user information including a user location from a user device and obtaining vehicle information including a vehicle location from a vehicle. In response to determining that the user is ready to be picked up by a vehicle based on the user information, the method includes: identifying a meeting based on the user information and the vehicle information; including sending commands to move the vehicle from the vehicle location to the appointment. In response to determining that the user is ready for the vehicle to track the user based on the user information, the method determines a tracking route or a tracking route for the vehicle based on the user information and the vehicle information. The method includes identifying a staging location for the vehicle and sending commands to the vehicle's autonomous control system to cause the vehicle to follow the shadow, route, or move to the staging location.

In a third aspect, determining that the user is ready to be picked up includes estimating a confidence value that is greater than a confidence threshold of the cost function. The cost function is based on user information, and the change in confidence value is based on the change in user information. Determining that the user is ready for the vehicle to track the user includes estimating a confidence value that is below a confidence threshold of the cost function. Determining that the user is ready to be picked up includes receiving authorization information from the user device authorizing the pickup. The third aspect may include any combination of the features described in this paragraph.

1 is a block diagram of a mobile ecosystem. 1 is a diagram illustrating a vehicle and a user device in an environment; FIG. FIG. 3 is a diagram showing a procedure for dispatching an automobile. FIG. 3 illustrates a vehicle and a user device in another environment. FIG. 2 is a diagram illustrating a computing device.

A ride dispatch method and system using a mobile ecosystem is disclosed. A mobile ecosystem includes a vehicle having an autonomous control system configured to operate the vehicle without a driver, and a user device that communicates with the vehicle (e.g., via a network). Based on user information accessible to the user device, such as calendar information, biometric information, user location information, location history information, etc., the mobile ecosystem is informed of upcoming events, changes in the location of the user device, or surroundings of the user device. Ride dispatch can be streamlined by automatically determining when a user of a user device is ready for a pick-up or meet-up based on contextual clues from user information, such as changes in the environment. . In some examples, no input from the user is required and the determination of readiness determines that the impending pick-up or meet-up confidence value is associated with preparing the vehicle for the pick-up or meet-up. This can be done through the use of a cost function when the cost is high enough to justify or overcome any costs involved.

FIG. 1 is a block diagram of a mobile ecosystem 100 suitable for implementing the ride dispatch methods described herein. The mobile ecosystem may include a vehicle 102 and a user device 104. Although a single vehicle 102 and a single user device 104 are shown, multiple vehicles or multiple user devices may be part of the mobile ecosystem 100.

Vehicle 102 may include a sensor system 106, an autonomous control system 108, a propulsion system 110, and a seating system 112. These components may be attached to and/or form part of the physical structure of the vehicle 102, such as a body part, interior, suspension, or frame (not shown), and may have a wired connection. (e.g., using a wired communications bus) or via wireless data communications channels to enable the transmission of signals, data, commands, etc. therebetween. Other types of conventional components may be included in vehicle 102, such as a charging system, ventilation system, or infotainment system (not shown).

Sensor system 106 of vehicle 102 may capture or receive information about vehicle 102 referred to as vehicle information. Vehicle information may be received from components of vehicle 102 or from the external environment in which vehicle 102 is located. The external environment may be external to vehicle 102, internal to vehicle 102, or the environment surrounding vehicle 102. Vehicle information captured or received by the sensor system 106 may include information about occupants within the vehicle 102, other vehicles, pedestrians and/or objects in the external environment, the operating conditions of the vehicle 102, the operating conditions or trajectory of other vehicles, and the like. It may be related to other conditions within vehicle 102 or outside vehicle 102. For example, the vehicle information may include the vehicle location of the vehicle 102, traffic information regarding vehicle or pedestrian traffic surrounding the vehicle 102, the current vehicle configuration identifying the location of seats within the seating system 112, or other interior features of the vehicle 102. , or a staging location for the vehicle 102, ie, an area where the vehicle 102 may safely wait, park, or patrol within the external environment. The staging location may be continuously updated based on previous operation of the vehicle 102 or the route traveled by the vehicle 102.

Autonomous control system 108 uses vehicle information and sensor outputs from sensor system 106 to understand the environment around vehicle 102 and plan a trajectory for vehicle 102 . The trajectory may be based on the current vehicle position and pick-up position of the vehicle 102. Autonomous control system 108 determines, according to user information from user device 104 , a path or route for vehicle 102 to travel and a speed or speed along the path or route consistent with achieving a rendezvous with a user of user device 104 . The vehicle 102 is configured to determine one or more trajectories of the vehicle 102, including a speed profile. The term “meeting” may refer to a pickup location, pickup time or arrival time, pickup vehicle configuration, or other information consistent with the collection between the vehicle 102 and the user of the user device 104. In some examples, the user may load cargo into the vehicle 102 instead of entering the vehicle 102 for a ride, which is consistent with the term "meeting." Autonomous control system 108 may be implemented to automatically move a vehicle (eg, without a driver) using multiple components, including hardware and/or software components. As one example, autonomous control system 108 may be implemented in the form of one or more computing devices provided with control software. Control software includes computer program instructions that enable autonomous control system 108 to perform the functions described herein.

Propulsion system 110 includes components (eg, actuators, motors, batteries, axles, wheels, etc.) that move vehicle 102. As one example, propulsion system 110 may include a combustion engine configured to propel vehicle 102, such as by providing drive torque to one or more wheels. Propulsion system 110 may be controlled by commands received from autonomous control system 108. In one example, the autonomous control system 108 may cause the propulsion system 110 to move the vehicle 102 along a trajectory, such as to move the vehicle 102 to a meeting point, in response to determining that the user of the user device 104 is ready to be picked up. A command can be output to the propulsion system 110 to cause the transmission to occur.

Seating system 112 includes a seat with a backrest that is rotatable relative to the seat pan, a seat that is rotatable or translatable relative to other seats, and a table system that is configurable to provide entertainment or a work surface for vehicle occupants. or other surfaces or components that can be moved, positioned, or otherwise configured to meet a user's specific preferences for setting up the vehicle 102 in a vehicle configuration. One example of a vehicle configuration is a mobile office configuration in which the seats in the seating system 112 are rotated to face each other and toward the table system, e.g., with a centrally located work surface in the interior of the vehicle 102. Can be mentioned. As another example of a vehicle configuration, the seats within the seating system 112 are deeply reclined or generally parallel to the seat pan to allow the occupant to lie flat, sleep, or take a nap within the vehicle 102. sleep configurations having a backrest positioned in the Another example of a vehicle configuration is a cargo configuration in which some or all seats within the seating system 112 are folded or arranged to allow the vehicle 102 to carry bulky or larger sized cargo. can be mentioned.

User device 104 may include a sensor system 114, a user interface 116, and a user profile 118. These components may be configured to enable the transmission of signals, data, commands, etc. between them via wired connections (e.g., using a wired communication bus) or via wireless data communication channels. electrically interconnected within user device 104; Other types of conventional components may be included in user device 104. For example, user device 104 may include any wired or wireless interface that allows user device 104 to communicate with other components or systems, such as by sending data transmissions, receiving data transmissions, etc. Via network 120, communication may be made with vehicle 102.

Sensor system 114 of user device 104 may help capture or receive information about a user of user device 104, which is a form of user information. User information provided by sensor system 114 may include biometric information, user location, location history information, and user environment information. Biometric information can refer to the physiological state of the user, such as the user's heart rate, walking speed, sleepiness level, or other physical or emotional characteristics. User environmental information may be captured by sensor system 114 from a physical location adjacent to user device 104. For example, user information may include the user location of the user device 104 (held by the user or in the vicinity of the user), whether the user device 104 is physically located outdoors or indoors, population density, etc. may include user environment information, such as whether the device is located in a high area, in an isolated area, in the user's hand, or not currently visible to the user.

User interface 116 may include buttons, switches, touch-sensitive input devices, audio devices, display screens, or other suitable buttons, switches, touch-sensitive input devices, audio devices, display screens, or the like for receiving input from a user of user device 104 and providing instructions to the user regarding the operation of user device 104 . It can include any type of human-machine interface, such as gestural devices. The user may interact with the user interface 116 to determine, e.g., that the user (or another user) is authorized for pick-up by the vehicle 102, e.g., at a proposed meeting or pick-up location. or otherwise provide authorization information indicating readiness. The authorization information may include an indication of the user's level of readiness, confirmation of the pickup location or confirmation of user preferences such as pickup location, user vehicle configuration, and the like.

User profile 118 may store user information related to both current and past user preferences or user activities. User information forming user profile 118 may include calendar information, biometric information, purchase history information, user environment information, location history information, and user preference information. Calendar information may include the user's scheduled meetings or events, as well as the location and time of the meetings or events. Purchase history information may include transactions completed using user device 104, such as purchasing meals, purchasing goods or services, and the like. Location history information may include map information representing the locations to which the user has moved, and temporal information representing the timing and pattern of the user's movement to such locations (e.g., the user or the user picks up the child from school around 4:30 pm on weekdays). User preference information may include user vehicle configurations that describe preferred seat settings or other vehicle settings such as air conditioner temperature, mirror position, preferred radio station, etc.

Vehicle 102 and user device 104 communicate via network 120 to form mobile ecosystem 100 . The network 120 (including, for example, a cloud computing device) or the vehicle 102 can be configured without requiring the user to provide multiple inputs to the user device 104, or in some cases without requiring the user to provide any input to the user device 104. , a user's transportation needs can be automatically detected based on user information provided by the user device 104 to streamline ride-hailing procedures (e.g., automate meet-ups or pick-ups). Various examples of vehicle dispatch performed using mobile ecosystem 100 are described herein.

FIG. 2 is a diagram illustrating a vehicle 202 and a user device 204 within an environment 222. Vehicle 202 and user device 204 are part of a mobile ecosystem and communicate with each other through a network (eg, including a remote or cloud computing system not shown). Vehicle 202 and user device 204 may have similar characteristics as vehicle 102 and user device 104 described with respect to FIG.

Vehicle 202 may be physically located at a detectable or identifiable vehicle location 224 within environment 222 . In this example, vehicle location 224 is a parking spot in an outdoor parking lot indicated by a dashed line. Vehicle location 224 can function as a staging location, ie, a location where vehicle 202 can wait until indicated to meet or pick up a user associated with user device 204 . Although shown here as a parking spot in a parking lot, the vehicle location 224 may be in many locations, such as a garage, a street parking spot, or a staging location or route, such as a route around the building where the user device 204 is located. It can be one of the following.

User device 204 is physically located at a detectable or identifiable user location 226 . In this example, user location 226 is an office or room in a building near the parking lot associated with vehicle location 224, shown as a dotted line. The user may hold the user device 204 in a hand, pocket, or bag, or the user device 204 may be placed on a desk or table within the user location 226. User device 204 may include or have access to user information such as user location 226, calendar information, biometric information, purchase history information, user environmental information, location history information, or user preference information.

Each user information accessible to the user device 204 is used to determine the probability or likelihood that the user associated with the user device 204 is ready for pick-up by or rendezvous with the vehicle 202. can be used as input to the cost function of The cost function can determine a confidence value of the user's readiness for the pick-up or rendezvous, such as a low confidence value, a medium confidence value, or a high confidence value. The cost function may be associated with a confidence threshold such that when the cost function has a high confidence value or a value above the confidence threshold, the vehicle 202 picks up or meets the user of the user device 204. can be controlled to When having a low confidence value, a medium value, or a value below a confidence threshold, the vehicle may be controlled to stage to a staging location or parking lot, as illustrated by vehicle 202 in FIG. 2 .

Changes in the confidence value determined by the cost function may be based on changes in user information associated with user device 204. For example, calendar information and location history information may indicate that a user of user device 204 has a weekly tennis match across town in 45 minutes from now, and previously traveled to a vehicle about 30 minutes before this weekly tennis match. It can be shown that 202 has been dispatched. The user environment information may indicate that the user of the user device 204 has turned off the lights in the office (user location 226) or moved the user device 204 from the desk to the bag. The biometric information may indicate that the user of user device 204 has been sitting for a period of time and is now walking based on a change in the user's heart rate or a change in user position 226. While user location 226 may have been limited to an office or set of offices within a building for some period of time, it is now possible for the user (e.g., carrying user device 204 in a pocket or bag) to Upon leaving the user location 226 and moving toward a building exit or door, for example, as shown by arrow A, user device 204 begins to move along the path or route shown by dashed arrow A in FIG. It is changing over time.

If the change in the reliability value determined using the cost function is sufficient to raise the value above a reliability threshold, for example, the vehicle 202 may pick up or drop off the user of the user device 204. It can be controlled to perform a meeting with a user. The cost function may also be based on the cost associated with having the vehicle 202 immediately ready to perform the pick-up or rendezvous. The costs that the user of the user device 204 immediately provides for the vehicle 202 include parking costs, fuel costs (eg, when performing a staging route), traffic impacts on the environment 222, and the like. The confidence value of the impending pick-up or rendezvous determined using the cost function is sufficiently high to justify or overcome the costs associated with preparing the vehicle 202 to perform the pick-up or rendezvous. It has to be something.

The term meeting refers to the route that vehicle 202 travels from vehicle location 224 to pick-up location 228, the departure time at which vehicle 202 departs from vehicle location 224, the arrival time at which vehicle 202 arrives at pick-up location 228, and the vehicle. It can be used to cover specific details such as vehicle configurations or other vehicle settings available for vehicle 202 based on both information and user information. The term trajectory can also be used to describe a path or route between locations. In the example of FIG. 2, the path or route indicated by dashed arrow B may coincide with vehicle 202 moving to a previous (not shown) pick-up position for the user of user device 204. However, vehicle information related to the traffic pattern indicates that the path or route indicated by arrow B is blocked or congested due to an obstacle 230 (e.g., a pothole, a stranded vehicle, etc.). This can be indicated to vehicle 202.

Because the path or route indicated by arrow B is blocked or congested by an obstacle 230, vehicle 202 takes an alternative route or route indicated by arrow C, shown in dotted line, which takes the vehicle to pick-up location 228. It can be controlled to run according to a route. If the pick-up location 228 deviates from a location where the user of the user device 204 would expect to meet the vehicle 202 for a meet-up or pick-up, the user device 204 may send a notification to the user identifying the new pick-up location 228. can. In another example, the vehicle may prompt the user of the user device 204 to provide, as an input to the user device 204, authorization to direct the vehicle 202 to the pick-up location 228 for a pick-up, for example.

Other forms of user information may also be used by vehicle 202 to select between various routes or routes, such as shown by arrows B and C. For example, the speed at which user device 204 is moving along the path or route indicated by arrow A determines how fast the user will arrive at pick-up location 228 (or an alternate pick-up location, not shown) when the vehicle is moving. 202. The calendar information may indicate available time in the user's calendar prior to an event requiring a pickup. In some examples, the user may provide user approval to send the vehicle 202 to the pick-up location 228 when, for example, the confidence value of the cost function has a moderate level, such as less than a confidence threshold. , may be prompted by user device 204.

FIG. 3 is a diagram illustrating a procedure 332 for dispatching an automobile. Procedure 332 may be performed using mobile ecosystem 100 of FIG. 1, vehicle 202, and/or user device 204 of FIG. 2. Procedure 332 is described by referring back to mobile ecosystem 100, which includes both vehicle 102 and user device 104 in communication with network 120 of FIG. 1, and vehicle 202 and user device 204 of FIG. 2.

At act 334, network 120, vehicle 102, or user device 104 may receive user information from user device 104. User information includes user authorization (indicating authorization for vehicle 102 to pick up the user), user location, calendar information such as the schedule and location of events or meetings the user plans to attend, and where the user is sitting. biometric information such as whether the user is sitting, standing, or walking; the user's heart rate; the walking speed or stride length at which the user (who is holding the user device 104) is moving; the user's sleepiness level; and recent meals. Purchase history information detailing user purchases, such as payments or recent purchases of goods or services, and whether the user device 104 is located outdoors, indoors, or in the user's hand. user environment information, such as whether the environment in which the user device 104 is located is static, changing, dark, or bright; Location history information, such as whether you often move between locations, or, for example, seat settings, air conditioning settings, audio settings, mirror settings, or other settings of the vehicle 102 that are preferred (or required) by the user. and user preference information, such as a pick-up vehicle configuration describing setup information for a vehicle.

At act 336, network 120, vehicle 102, or user device 104 may receive vehicle information from vehicle 102. Vehicle information includes vehicle location, such as the current location where vehicle 102 is located, traffic information, such as traffic density, obstacles, and traffic flow patterns, and existing seat settings or positions, air conditioning settings, audio settings, mirror settings, the current vehicle configuration of the vehicle 102, such as or other current setup information, and previously used locations or staging that allows the vehicle 102 to be easily or quickly made available to the user of the user device 104; and a staging location, such as a route.

At decision block 338, network 120, vehicle 102, or user device 104 may determine whether the user is ready to be picked up based on the user information. The user information may provide various context hints to support estimating a confidence value above a predetermined confidence threshold of the cost function, eg, a high confidence value. The cost function may be based on user information available from the user device 104, and the change in confidence value may be based on the change in the user information. The cost function may be similar to the cost function described with respect to Figure 2, and may include whether the user has recently made a purchase or other payment, whether the user has completed training, and whether the user has an upcoming appointment. , or whether the user has the user device 104 in a bag, can be weighted and compared to determine a confidence value that the user is ready to be picked up. Determining that the user is ready to be picked up may also include receiving a user authorization from the user device 104. For example, if a low or medium confidence value is determined using the cost function, the user device 104 may prompt the user to specify whether he or she wishes to be picked up or met, and the user may provide user approval through user device 104 in response to the prompt.

If decision block 338 determines that the user is ready to be picked up, step 332 causes network 120, vehicle 102, or user device 104 to identify a meeting based on the user information and vehicle information. Proceed to operation 340 where the process can be performed. Details related to the meeting may include one or more of a pick-up location, arrival time or pick-up time, or pick-up vehicle configuration. Returning to FIG. 2 to illustrate a detailed example, the pick-up location 228 includes the vehicle location 224, the user location 226, and whether the user is carrying heavy purchases or before the user arrives at the pick-up location 228. It can be based on other user information, such as whether he enjoys walking a particular route or a particular number of steps to reach a fitness goal, and other vehicle information, such as traffic patterns around the vehicle 202. The pick-up time may be determined by the distance of the vehicle 202 or user device 204 from the pick-up location 228, the speed at which the user device 204 or the vehicle 202 is moving toward the pick-up location 228, or the user's upcoming meeting or It can be based on calendar information within the user device 204 indicating the time and location of the appointment. The pick-up time and pick-up location 228 may optionally be communicated to the user through the user device 204. The pick-up time and pick-up location 228 may also change based on changes in user or vehicle information as the user device 204 and vehicle 202 approach the pick-up location 228.

The pickup vehicle configuration may be based on user information such as the user's preferences for seating, air conditioning, or audio, recent user purchases, biometric information, or calendar information. The term user vehicle configuration may also be used to describe vehicle configuration based on user information. Determining whether to change from the current vehicle configuration to the user vehicle configuration or the pick-up vehicle configuration also determines whether the user's pick-up is required, as determined by a cost function, such as a confidence value that exceeds a confidence threshold. It can be based on the confidence value of that. For example, in situations where the confidence value is a high value, a change in vehicle configuration from the current vehicle configuration to the pick-up vehicle configuration or user vehicle configuration may be performed before the vehicle 202 moves to the pick-up location 228. In situations where the confidence level is moderate or low, such as below a confidence threshold, no changes to the vehicle configuration may be made or no changes may be made to the vehicle configuration until user approval is received from the user device 204. No changes need to be made.

In some examples, the vehicle's autonomous control system 108 may change the vehicle 102 from the current vehicle configuration to the pick-up location when the meeting is identified or when the vehicle 102 arrives at the meeting (in the example of FIG. 2, the pick-up location 228). Vehicle configuration can be changed. If the user device 104 has user information that the user recently completed a workout and cooled down, the seating system 112 may use past user information or vehicle user information to indicate that the user rested or cooled down in a reclined position after the workout. If it indicates that you have enjoyed your sleep, you may be configured to lounge or recline deeply. If user device 104 provides user information to network 120 or vehicle 102 that the user recently purchased a large birthday cake, seating system 112 may stow, fold, or flatten one or more seats within vehicle 102. may be configured to do so. Additionally, a door or rear hatch of vehicle 102 may open automatically when a user (with user device 104 and birthday cake) approaches vehicle 102 to facilitate loading the birthday cake into the vehicle. . Other systems within vehicle 102 may also be modified, changed, or otherwise configured as part of the pickup vehicle configuration to suit the needs or preferences of the user.

At act 342, the autonomous control system 108 of the vehicle 102 may move the vehicle to the appointment in response to the network 120 or the vehicle 102 determining that the user is ready to be picked up. For example, the autonomous control system 108 may be configured to move from a vehicle position (e.g., vehicle position 224 in FIG. 2) to a pick-up position (e.g., in the direction shown by arrow C in FIG. A command may be sent to the propulsion system 110 to move the vehicle 102 toward a pick-up location 228).

If decision block 338 determines that the user is not ready to be picked up, procedure 332 proceeds to optional decision block 344, shown as optional using a dotted line. At optional decision block 344, network 120, vehicle 102, or user device 104 optionally determines, based on the user information, whether the user is ready for vehicle 102 to track the user. can be determined. The term "tracking" refers to the fact that the vehicle 102 is positioned or located for immediate use by the user, e.g. Used to indicate that the vehicle 102 is placed in a staging position (such as vehicle position 224 in FIG. 2) in preparation for readiness, or is sent to follow a tracking route that keeps the vehicle 102 close to the user. Ru.

At decision block 344, determining the readiness of the user for the vehicle 102 to track the user may include estimating a confidence value below a confidence threshold of the cost function. . For example, the confidence value may be close to, but below (eg, within 5% or 10% of the value) a confidence threshold. In another example, the confidence value may exceed a second confidence threshold that is lower than the (first) confidence threshold associated with the user ready to be picked up at decision block 338. be. In these examples, the confidence value determined by the cost function can be based on user information, and the change in confidence value can be based on the change in user information.

If the decision block 344 determines that the user is ready for the vehicle 102 to track the user, the procedure 332 proceeds to an optional operation 346 to determine whether the vehicle 102 is tracking the user based on the user information and the vehicle information. Identify a tracking route or staging location for 102. Returning to the example of FIG. 2, vehicle 202 is currently at vehicle position 224. Vehicle location 224 is close to user device 204 in that the parking lot is at one corner of the intersection and user device 204 is inside a building at another corner of the same intersection; serves as a suitable staging location. Vehicle 202 may remain at vehicle location 224 as a staging location and await further input.

In some examples, procedure 332 proceeds to optional operation 348, where vehicle 102 is directed to travel along a tracking route or to move to a staging position. Returning to the example of FIG. 2, if the parking lot where vehicle 202 is stored at vehicle location 224 is some distance away from user device 204 (such as several blocks or miles away), vehicle 202 will It may be controlled to start moving along the path or route indicated by arrow C or, under optional action 348, along the path or route indicated by arrow C as a tracking route. The vehicle 202 also moves around the block (not shown) or otherwise locates the user device 204, such as by finding a nearby parking location to serve as a staging location. It can be controlled to stage, patrol, or remain near a building. In this example, the tracking route may lead to a staging location. Thus, the tracking route and/or staging location allows the vehicle 202 to remain close to the user device 204 such that vehicle dispatch is a quick and easy procedure for the user of the user device 204.

If the optional decision block 344 determines that the user is not ready for the vehicle 102 to track the user, the procedure 332 returns to operation 334 to receive user information and to Returning to operation 336 to receive, procedure 332 starts over.

FIG. 4 shows a vehicle 402, a first user device 404 (e.g., owned by a first user), and a second user device 450 (e.g., owned by a second user) within an environment 422. It is a diagram. Vehicle 402 and first user device 404 are part of a mobile ecosystem and communicate with each other over a network (eg, including a remote or cloud computing system not shown). First user device 404 may also communicate with second user device 450 over the network. Vehicle 402 and user devices 404, 450 may have similar features as vehicle 102, 202 and user device 104, 204 described with respect to FIGS. 1 and 2.

Vehicle 402 may be physically located within environment 422 at vehicle location 424 . In this example, vehicle location 424 is a parking spot in an outdoor parking lot. First user device 204 is physically located at first user location 426 . In this example, first user location 426 is an office or room in a building near the parking lot associated with vehicle location 424. In this example, vehicle 402 may be part of a mobile ecosystem that is associated with and readily available to the first user for ride-hailing purposes. Vehicle location 424 is also physically available to the first user, e.g., at a staging location, given the proximity of vehicle location 424 to first user location 426. A second user device 450 is physically located at a second user location 452 . In this example, second user location 452 is a store, office, or room in a building remote from first user location 426 and vehicle location 424.

The first user device 404 includes or has access to first user information, such as the first user's location 426, calendar information, biometric information, purchase history information, environmental information, location history information, or preference information. may have access. The second user device 450 includes or has access to second user information, such as a second user's location 452, calendar information, biometric information, purchase history information, environmental information, location history information, or preference information. may have access. With the first user device 404 and the second user device 450 communicating, e.g. It may be possible to provide the second user information to the network, to the first user device 404, or to the vehicle 402 for the purpose of doing so. The term "borrowed" means that the second user device 450 may not be part of the mobile ecosystem of the vehicle 402 and the first user device 404, but is still given authorization to use the vehicle 402. used to explain something.

For example, second user device 450 can be used to send requests related to borrowing vehicle 402 to first user device 404 . If the first user is able to accept lending the vehicle 402 to the second user, user approval from the first user may be received by the first user device 404. Based on the user approval, the vehicle 402 (or the first user device 404 or network) sends a second User information may be obtained (eg, from second user device 450). Vehicle 402 identifies the meeting and follows a trajectory indicated by dotted arrow D such that vehicle 402 travels to a pick-up location 428 at a convenient spot for user device 450 at the appropriate pick-up time. can be controlled as follows. The second user may be enjoying dinner or drinks with friends, and borrowing the vehicle 402 may be done by the second user to a third-party rideshare if the first user authorizes the borrowing of the vehicle 402. It helps to avoid contacting the service and save the user's time and money.

In another example, a request to send vehicle 402 along the trajectory specified by arrow D to pickup location 428 may be performed by a first user using first user device 404 . In this example, the second user who owns the second user device 450 may be a pet, such as a turtle, and the second user device 450 may be a smart tag with location information of the turtle. , the pick-up location 428 may be close to a veterinarian's office where the turtle is undergoing an annual checkup. Vehicle 402 is at pick-up position 428 before vehicle 402 is controlled to return to vehicle position 424 such that the turtle is reunited with the first user (e.g., the turtle's owner) of first user device 404 The veterinarian may then be able to load the turtle (and associated smart tag) into the vehicle 402. Although an example using a camera is given, the second user may be located by a family member, friend, or mobile ecosystem known to the first user, and who uses the vehicle 402 to It may be any other entity or shipment authorized by the user.

In another example, vehicle 402 may be part of a fleet of vehicles (not shown). First user device 404 and second user device 450 may be part of a user network (not shown). Vehicle 402, first user device 404, and second user device 450 each provide vehicle information and user information to communicate across a user network using the techniques and cost functions described herein. and across a population of vehicles. Forecasting the demand for vehicles within a fleet can improve fleet operational efficiency and reduce costs.

For example, user information accessible to the user device 404 , 450 may be used as input to a cost function to prepare the user associated with the user device 404 , 450 for pick-up or rendezvous with the vehicle 402 . It is possible to determine the probability or likelihood that The staging location for vehicle 402 may be selected based generally on which of the proximate user devices 404, 450 has a higher probability of an impending ride request. This staging method can be extended beyond the scope of vehicles 402 and user devices 404, 450 to the entire population of vehicles and user devices in a user network, such that the population is responsive to demand from various user devices. are predictively staged in proximity to various user devices in the user network based on the predicted probabilities of . This predictive staging is based, for example, on changes in user information from user devices within the user network that lead to changes in the probability of impending vehicle dispatch as calculated using the cost functions described herein. This may result in some vehicles in the population being relocated to different physical locations.

FIG. 5 shows an example of a computing device 554 that may be used to implement the autonomous control system 108 or other components of the mobile ecosystem 100, vehicle 202, or user device 204, 404, 450. In the illustrated example, computing device 554 may include a processor 556, a memory device 558, a storage device 560, one or more input devices 562, and one or more output devices 564. These components may be interconnected by hardware such as a bus 566 that allows communication between the components.

Processor 556 may be a conventional device, such as a central processing unit, and is operable to execute computer program instructions and perform operations described by the computer program instructions. Memory device 558 may be a volatile high speed short term information storage device such as a random access memory module. Storage device 560 may be a non-volatile information storage device such as a hard drive or solid state drive. Input devices 562 may include sensors and/or any type of human-machine interface, such as buttons, switches, keyboards, mice, touch screen input devices, gesture input devices, or audio input devices. Output device 564 is operable to transmit commands associated with communication or autonomous operation, or to provide instructions regarding authorization or status to a user, such as, for example, a display screen, an interface for vehicle operation, or audio output. , can include all kinds of devices.

As discussed above, aspects of the present technology may be obtained from various sources, such as sensor systems 106, 114 or user profiles 118, to improve the functionality of a mobile ecosystem, such as mobile ecosystem 100 of FIG. collecting and using relevant data. This disclosure provides that, in some cases, this collected data may contain personal information data that uniquely identifies a particular person or that can be used to contact or locate a particular person. Consider what it can include. Such personal information data may include demographic data, location-based data, phone number, email address, Twitter ID, home address, user's health or fitness level (e.g., vital sign measurements, medication information, exercise information). may include data or records relating to, date of birth, or any other identifying or personal information.

This disclosure recognizes that the use of personal information data in the present technology may be a use to the benefit of the user. For example, personal information data may be used within the mobile ecosystem to best match user preferences, or may be stored and protected in association with a user profile 118 within the user device 104, for example. Other uses of personal information data that are beneficial to the user are also possible. For example, health and fitness data can be used to provide insights into a user's overall wellness, or provide proactive feedback to individuals using technology in pursuit of wellness goals. It can also be used as

This disclosure contemplates that entities involved in the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will adhere to robust privacy policies and/or practices. Specifically, such entity shall implement privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining personal information data in the strictest confidence. and should be used consistently. Such policies must be easily accessible by users and updated as data collection and/or use changes. Personal information from users should be collected for the lawful and legitimate use of that entity and should not be shared or sold except for those lawful uses. Moreover, such collection/sharing should be performed after informing the users and obtaining their consent.

Moreover, such entities shall protect and secure access to such Personal Information Data and ensure that others with access to such Personal Information Data adhere to their privacy policies and procedures. Consideration should be given to taking all necessary steps to ensure that Additionally, such entities may submit themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific types of personal information data collected and/or accessed, and be consistent with applicable laws and standards, including jurisdiction-specific considerations. should be adapted. For example, in the United States, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA). On the other hand, health data in other countries may be subject to other regulations and policies and should be treated accordingly. Therefore, different privacy practices should be maintained in each country regarding different types of personal data.

Notwithstanding the foregoing, this disclosure also contemplates embodiments in which a user selectively prevents use of or access to personal information data. That is, the present disclosure contemplates that hardware and/or software elements may be provided to prevent or block access to such personal information data. For example, in the case of user profile-based mobile ecosystems, the technology allows users to choose to "opt in" or "opt out" of participating in personal information data collection during service registration or at any time thereafter. may be configured. In addition to providing "opt-in" and "opt-out" choices, this disclosure is intended to provide notices regarding access or use of personal information. For example, the user may be informed at the time of downloading an app that will access the user's personal information data, and then reminded the user again just before the personal information data is accessed by the app.

Furthermore, it is the intent of this disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data when it is no longer needed. Additionally, and where applicable in certain health-related applications, data anonymization can be used to protect user privacy. Anonymization may include, where appropriate, removing certain identifiers (e.g. date of birth), controlling the amount or specificity of stored data (e.g. moving location data to city rather than address level). (e.g., by aggregating data across users), and/or by other methods.

Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, this disclosure also covers the use of personal information data to implement one or more of the various disclosed embodiments, but this disclosure also covers the use of personal information data to It is contemplated that the various embodiments may be implemented without the need to do so. That is, various embodiments of the present technology are not rendered inoperable by the absence of all or any portion of such personal information data. For example, changes in the behavior of the mobile ecosystem may be based on user preferences or based on non-personal information data, minimal amounts of personal information, other non-personal information available on the system, or publicly available information. It may be implemented for a given user by inferring user status.

Claims (15)

a user device that communicates with the network;
a vehicle having an autonomous control system communicating with the network;
A mobile ecosystem that includes
At least one of the user device, the vehicle, or the network,
receiving user information from the user device;
receiving vehicle information from the vehicle;
determining that the user is ready to be picked up based on the user information;
is operable to specify a meeting based on the user information and the vehicle information;
The autonomous control system of the vehicle,
operable to drive the vehicle to the meeting point in response to determining that the user is ready to be picked up;
mobile ecosystem. The mobile eco-friendly device according to claim 1, wherein the user information includes at least one of user approval, user location, calendar information, biometric information, purchase history information, user environment information, location history information, or user preference information. system. 3. The mobile ecosystem of claim 2, wherein determining that the user is ready to be picked up includes receiving the user authorization from the user device. Mobile ecosystem according to any one of claims 1 to 3, wherein the vehicle information includes at least one of vehicle location, traffic information, current vehicle configuration, or staging location. A mobile ecosystem according to any one of claims 1 to 4, wherein the meeting includes at least one of a pick-up location, a pick-up time, or a pick-up vehicle configuration. The autonomous control system of the vehicle,
6. The mobile ecosystem of claim 5, operable to cause the vehicle to change from the current vehicle configuration to the pick-up vehicle configuration when the vehicle arrives at the meeting. determining that the user is ready to be picked up includes estimating a confidence value greater than a confidence threshold of a cost function, wherein the cost function is based on the user information; Mobile ecosystem according to any one of claims 1 to 6, wherein the change in the value of trustworthiness is based on the change in the user information. The user device, the vehicle, or the network,
determining that the user is ready for the vehicle to track the user based on the user information;
identifying a tracking route for the vehicle based on the user information and the vehicle information;
A mobile ecosystem according to any one of claims 1 to 5, operable to cause the vehicle to travel according to the tracking route. Determining that the user is ready for the vehicle to track the user includes estimating a confidence value below a confidence threshold of a cost function, wherein the cost function is 9. The mobile ecosystem of claim 8, wherein the mobile ecosystem is based on user information, and the change in the value of the trust factor is based on the change in the user information. Obtaining user information including user location from a user device;
Obtaining vehicle information including vehicle position from the vehicle;
In response to determining that the user is ready to be picked up by the vehicle based on the user information,
identifying a meeting based on the user information and the vehicle information;
sending a command to an autonomous control system of the vehicle to move the vehicle from the vehicle location to the meeting point;
In response to determining that the user is ready for the vehicle to track the user based on the user information,
identifying a tracking route for the vehicle or a staging position for the vehicle based on the user information and the vehicle information;
sending a command to the autonomous control system of the vehicle to cause the vehicle to travel along the tracking route or to the staging position;
How to dispatch a vehicle, including: 11. The method of claim 10, wherein the meeting includes at least one of a pick-up location, a pick-up time, or a pick-up vehicle configuration. changing the vehicle from the current vehicle configuration to the pick-up vehicle configuration when the vehicle arrives at the meeting in response to determining that the user is ready to be picked up by the vehicle based on the user information; to let;
12. The method of claim 11, further comprising: determining that the user is ready for the pick-up includes estimating a confidence value of a cost function that is greater than a confidence threshold; the cost function is based on the user information; A method according to any one of claims 10 to 12, wherein the change in the value of degree is based on a change in the user information. Claim: wherein determining the readiness of the user for the vehicle to track the user comprises estimating the value of the confidence below the confidence threshold of the cost function. The method according to item 13. 15. The method of any one of claims 10-14, wherein determining that the user is ready for the pick-up includes receiving authorization information from the user device authorizing the pick-up.