System and method for performing anticipated detection of user's need for autonomous vehicle pick-up

By using computing devices in autonomous vehicles to determine the loading needs and collect data to calculate the trigger value, automatically triggering the loading, the problem of users needing to actively input in the existing system is solved, the loading efficiency and convenience are improved, and traffic congestion is reduced risk.

CN119007426APending Publication Date: 2024-11-22HYUNDAI MOTOR CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311101971.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-17
Filing Date
2023-08-29
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing autonomous vehicle loading system requires users to actively enter requests, resulting in inefficiency and inconvenience, and may lead to traffic congestion.

Method used

The computing device determines the location and loading requirements of the autonomous vehicle, collects user and destination related data, calculates the percentage of probability of the loading request, and automatically triggers the loading when the triggering value exceeds the threshold.

Benefits of technology

The autonomous vehicle pickup can be achieved without the user's active input, which improves the loading efficiency and convenience and reduces the risk of traffic congestion.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119007426A_ABST
    Figure CN119007426A_ABST
Patent Text Reader

Abstract

Systems and methods are provided for performing an anticipated detection that a user needs an autonomous vehicle pick-up. A method may include determining, using a computing device including a processor and a memory, a location of an autonomous vehicle, determining whether a pick-up is needed at the location, collecting data regarding a user and a destination when a pick-up is needed at the location, calculating, based on the data, a trigger value indicative of a percentage of likelihood that a pick-up request is needed, and transmitting the trigger value to the autonomous vehicle. It is determined whether the trigger value is greater than a threshold value, and when the trigger value is greater than the threshold value, a pick-up is triggered such that the autonomous vehicle performs the pick-up.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present disclosure are directed to systems and methods for performing anticipatory detection of a user's need for an autonomous vehicle pick-up and performing one or more vehicle actions in conjunction with the anticipatory detection. Background Art

[0002] Autonomous vehicles are generally capable of autonomously traveling to one or more locations without active steering, acceleration, and deceleration by a user. Using these capabilities, autonomous vehicles are generally capable of picking up users at desired locations. However, current systems and methods require users to make active and conscious inputs, communicate with the autonomous vehicle, and request that the autonomous vehicle pick up one or more passengers / users.

[0003] Currently, all ride-hailing services and vehicle pickup services require user input. This results in inefficiencies and uses conscious effort. User input includes, but is not limited to, information about the pickup time, pickup location, drop-off time, drop-off location, and / or other suitable information. This requires the user to plan out their pickup, and if not done preemptively, the user will not be picked up at the optimal time, and the user will be disappointed with a late pickup. Furthermore, if done too early, the autonomous vehicle will wait for the user for an extended amount of time, which may result in increased traffic and congestion.

[0004] For at least these reasons, there is a need for systems and methods for performing anticipatory detection of a user's need for a ride in an autonomous vehicle, allowing the autonomous vehicle to anticipate the user's need for a ride without requiring active input. Summary of the invention

[0005] According to the purpose of the present disclosure, a method for performing anticipatory detection of a user requiring a pick-up by an autonomous vehicle (AV) is provided. The method may include: determining a location of the AV using a computing device including a processor and a memory, determining whether a pick-up is required at the location, collecting data related to the user and the destination when a pick-up is required at the location, calculating a trigger value indicating a probability percentage of a pick-up request based on the data, determining whether the trigger value is greater than a threshold, and triggering the pick-up when the trigger value is greater than the threshold so that the AV performs the pick-up.

[0006] According to an exemplary embodiment, determining the location of the AV may include determining whether the AV is parked.

[0007] According to an exemplary embodiment, determining whether a pickup is required at the location may include determining whether the parking location meets predetermined criteria.

[0008] According to an exemplary embodiment, the user-related data may include one or more of the following: user digital behavior data; user physiological data (e.g., blood sugar, sweat, etc.); user voice recognition data; user payment history; and user historical travel data.

[0009] According to an exemplary embodiment, the data related to the destination may include one or more of the following items: historical data, including whether the user has arrived at the destination before, the average time frame for which the user has visited the destination during a trip to the destination, and the average time frame for which a typical customer visits the destination during a trip to the destination; data related to whether the destination is an institution, and when the destination is an institution, the operating hours of the institution.

[0010] According to an exemplary embodiment, calculating the trigger value may include performing one or more calculation parameters based on the data to dynamically adjust the trigger value.

[0011] According to an exemplary embodiment, the method may further include: when the trigger value is not greater than a threshold value, recalculating the trigger value.

[0012] According to an object of the present disclosure, a system for performing anticipated detection of a user requiring a pick-up by an autonomous vehicle is provided. The system may include an AV, the AV including a processor, a memory, and one or more position sensors. The processor is configured to determine the location of the AV using the one or more position sensors, determine whether a pick-up is required at the location, collect data related to the user and the destination when a pick-up is required at the location, calculate a trigger value indicating a probability percentage of a pick-up request based on the data, determine whether the trigger value is greater than a threshold, and when the trigger value is greater than the threshold, trigger the pick-up so that the AV performs the pick-up.

[0013] According to an exemplary embodiment, determining the location of the AV may include determining whether the AV is parked.

[0014] According to an exemplary embodiment, determining whether a pick-up is required at the location may include determining whether the parking location meets predetermined criteria.

[0015] According to an exemplary embodiment, the user-related data may include one or more of the following items: user digital behavior data; user physiological data (e.g., blood sugar, sweat, etc.); user voice recognition data; user payment history; and user historical travel data.

[0016] According to an exemplary embodiment, the data related to the destination may include one or more of the following items: historical data, which includes whether the user has arrived at the destination before, the average time frame for how long the user has visited the destination during a trip to the destination, and the average time frame for how long a typical customer visits the destination during a trip to the destination; data related to whether the destination is an institution, and when the destination is an institution, the operating hours of the institution.

[0017] According to an exemplary embodiment, calculating the trigger value may include performing one or more calculation parameters based on the data to dynamically adjust the trigger value.

[0018] According to an exemplary embodiment, when the trigger value is not greater than the threshold value, the processor may be further configured to recalculate the trigger value.

[0019] According to an object of the present disclosure, a system for performing anticipated detection of a user requiring a pick-up by an autonomous vehicle is provided. The system may include an AV and a computing device, the AV including one or more location sensors, the computing device including a processor and a memory, the memory being configured to store programming instructions. When executed by the processor, the programming instructions may be configured to cause the processor to determine the location of the AV using the one or more location sensors, determine whether a pick-up is required at the location, collect data related to the user and the destination when a pick-up is required at the location, calculate a trigger value indicating a probability percentage of a pick-up request based on the data, determine whether the trigger value is greater than a threshold, and when the trigger value is greater than the threshold, trigger the pick-up so that the AV performs the pick-up.

[0020] According to an exemplary embodiment, determining the location of the AV may include determining whether the AV is parked.

[0021] According to an exemplary embodiment, determining whether a pick-up is required at the location may include determining whether the parking location meets predetermined criteria.

[0022] According to an exemplary embodiment, the user-related data may include one or more of the following items: user digital behavior data; user physiological data (e.g., blood sugar, sweat, etc.); user voice recognition data; user payment history; and user historical travel data.

[0023] According to an exemplary embodiment, the data related to the destination may include one or more of the following items: historical data, including whether the user has arrived at the destination before, the average time frame for how long the user has visited the destination during a trip to the destination, and the average time frame for how long a typical customer visits the destination during a trip to the destination; data related to whether the destination is an institution, and when the destination is an institution, the operating hours of the institution.

[0024] According to an exemplary embodiment, calculating the trigger value may include performing one or more calculation parameters based on the data to dynamically adjust the trigger value.

[0025] According to an exemplary embodiment, when the trigger value is not greater than the threshold value, the programming instructions, when executed, may be configured to further cause the processor to recalculate the trigger value. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying drawings, which are incorporated in and form a part of the detailed description, illustrate various non-limiting and non-exhaustive embodiments of the subject matter and, together with the detailed description, serve to explain the principles of the subject matter discussed below. Unless otherwise noted, the drawings referred to in the brief description of the drawings should be understood as not being drawn to scale, and like reference numerals refer to like parts throughout the various drawings unless otherwise specified.

[0027] Figure 1 A vehicle configured to perform anticipatory detection of a user requiring an autonomous vehicle pick-up and to perform one or more vehicle actions in conjunction with the anticipatory detection is shown according to an exemplary embodiment of the present disclosure.

[0028] Figure 2 A logic diagram for performing anticipatory detection of a user requiring autonomous vehicle pickup and performing one or more vehicle actions in conjunction with the anticipatory detection according to an exemplary embodiment of the present disclosure is shown.

[0029] Figure 3 A flow chart of a method for performing anticipatory detection of a user requiring autonomous vehicle pickup and performing one or more vehicle actions in conjunction with the anticipatory detection according to an exemplary embodiment of the present disclosure is shown.

[0030] Figure 4 Exemplary elements of a computing device according to an exemplary embodiment of the present disclosure are shown.

[0031] Figure 5 An exemplary architecture of a vehicle according to an exemplary embodiment of the present invention is shown. DETAILED DESCRIPTION

[0032] The following detailed description is provided by way of example only and not by way of limitation. In addition, no intention is made to be bound by any express or implied theory presented in the foregoing background or the following detailed description.

[0033] Reference will now be made in detail to different exemplary embodiments of the subject matter, examples of which are shown in the accompanying drawings. Although various embodiments are discussed herein, it will be understood that they are not intended to limit these embodiments. On the contrary, the proposed embodiments are intended to cover replacements, modifications and equivalents that may be included in the spirit and scope of the various embodiments defined by the appended claims. In addition, in this detailed description, many specific details are set forth in order to provide a thorough understanding of the embodiments of this subject matter. However, the embodiments may be practiced without these specific details. In other instances, well-known methods, processes, components and circuits are not described in detail to avoid unnecessarily obscuring the various aspects of the described embodiments.

[0034] Some parts of the following detailed description are presented in the form of other symbolic representations of the operation of data in the electronic device, such as processes, logic blocks, processing and other symbolic representations. These descriptions and representations are the means by which the technical personnel in the field of data processing use the essence of their work to be most effectively conveyed to other technical personnel in the field. In this application, processes, logic blocks, processing, etc. are envisioned as one or more self-consistent processes or instructions that lead to a desired result. These programs are those that require physical manipulation of physical quantities. Typically, although not necessarily, these quantities can take the form of electrical or magnetic signals that can be stored, transmitted, combined, compared and otherwise manipulated in electronic systems, devices and / or components.

[0035] However, it should be remembered that these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless otherwise stated, as will be apparent from the following discussion, it should be recognized that throughout the description of the embodiments, discussions utilizing terms such as "determine," "communicate," "take," "compare," "monitor," "calibrate," "estimate," "start," "provide," "receive," "control," "transmit," "isolate," "generate," "align," "synchronize," "identify," "maintain," "display," "switch," etc. refer to the actions and processes of an electronic component, such as a processor, a sensor processing unit (SPU), a processor of a sensor processing unit, an application processor of an electronic device / system, etc., or a combination thereof. The component manipulates data represented as physical (electronic and / or magnetic) quantities in registers and memories and converts it to other data similarly represented as physical quantities within a memory or register or other such information storage, transmission, processing or display component.

[0036] It should be understood that the term "vehicle" or "vehicle-based" or other similar terms as used herein include a broad range of motor vehicles, such as passenger cars, including sport utility vehicles (SUVs), buses, trucks, various commercial vehicles, ships (including various boats and vessels), aircraft, etc., and include hybrid vehicles, electric vehicles, plug-in hybrid electric vehicles, hydrogen-powered vehicles, and other alternative fuel vehicles (e.g., fuels derived from resources other than petroleum). As mentioned herein, a hybrid vehicle is a vehicle with two or more power sources, for example, gasoline-powered and electric vehicles. In various aspects, a vehicle may include an internal combustion engine system as disclosed herein.

[0037] The terms used herein are only used for the purpose of describing specific embodiments, and are not intended to limit the present disclosure. As used herein, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to also include plural forms. These terms are only intended to distinguish one component from another component, and these terms do not limit the nature, order or sequence of the constituent components. It should also be understood that when the terms "comprises" and / or "comprising" are used in this specification, they specify the presence of the features, wholes, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, parts and / or their combinations. As used in this article, the term "and / or" includes any and all combinations of one or more related listed items. Throughout the specification, unless explicitly described to the contrary, the word "comprise" and variants such as "comprises" or "comprising" will be understood to imply the inclusion of the elements, but do not exclude any other elements. In addition, the terms “unit”, “-er”, “-or”, and “module” described in the specification mean a unit for processing at least one function and operation, and may be implemented by a hardware component or a software component and a combination thereof.

[0038] Although the exemplary embodiments are described as using multiple units to perform the exemplary processes, it should be understood that the exemplary processes can also be performed by one or more modules. In addition, it should be understood that the term controller / control unit refers to a hardware device that includes a memory and a processor and is specifically programmed to perform the processes described herein. The memory is configured to store the modules, and the processor is specifically configured to execute the modules to perform one or more processes described further below.

[0039] In addition, the control logic of the present disclosure may be embodied as a non-volatile computer-readable medium on a computer-readable medium containing executable program instructions executed by a processor, a controller, etc. Examples of computer-readable media include, but are not limited to, ROM, RAM, compact disk (CD)-ROM, magnetic tape, floppy disk, flash drive, smart card, and optical data storage device. The computer-readable medium may also be distributed in a network-coupled computer system so that the computer-readable medium is stored and executed in a distributed manner, such as by a telematics server or a controller area network (CAN).

[0040] Unless otherwise specified or apparent from the context, as used herein, the term "about" should be understood to be within the normal tolerance range in the art, such as within 2 standard deviations of the mean. "About" can be understood to be within 10%, 9%, 8%, 7%, 6%, 5%, 4%, 3%, 2%, 1%, 0.5%, 0.1%, 0.05% or 0.01% of the value. Unless otherwise clear from the context, all numerical values ​​provided herein are modified by the term "about".

[0041] The embodiments described herein may be discussed in the general context of processor-executable instructions residing on some form of non-transient processor-readable media (such as program modules) executed by one or more computers or other devices. Typically, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functionality of program modules may be combined or distributed as desired in different embodiments.

[0042] In the accompanying drawings, a single box may be described as performing one or more functions; however, in actual practice, a function or functions performed by the box may be performed in a single component or across multiple components, and / or may be performed using hardware, using software, or using a combination of hardware and software. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, boxes, modules, logic, circuits, and steps have been described as a whole in terms of their functions. Whether these functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. Those skilled in the art may implement the described functions in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. In addition, the example device vibration sensing system and / or electronic device described herein may include components other than those shown, including well-known components.

[0043] The various techniques described herein may be implemented in hardware, software, firmware, or any combination thereof, unless specifically described as being implemented in a particular manner. Any features described as modules or components may also be implemented together in an integrated logic device, or separately as discrete but interoperable logic devices. If implemented in software, the techniques may be implemented at least in part by a non-transitory processor-readable storage medium that includes instructions that, when executed, perform one or more of the methods described herein. The non-transitory processor-readable data storage medium may form part of a computer program product, which may include packaging materials.

[0044] Non-transitory processor-readable storage media may include random access memory (RAM) (e.g., synchronous dynamic random access memory (SDRAM)), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, other known storage media, etc. Additionally or alternatively, the techniques may be implemented at least in part by a processor-readable communication medium that carries or communicates code in the form of instructions or data structures that can be accessed, read, and / or executed by a computer or other processor.

[0045] The various embodiments described herein may be performed by one or more processors, such as one or more motion processing units (MPUs), sensor processing units (SPUs), host processors or cores thereof, digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), application specific instruction set processors (ASIPs), field programmable gate arrays (FPGAs), programmable logic controllers (PLCs), complex programmable logic devices (CPLDs), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein, or other equivalent integrated or discrete logic circuits. The term "processor" as used herein may refer to any of the foregoing structures or any other structure suitable for implementing the techniques described herein. As used in this specification, the term "processor" may refer to substantially any computing processing unit or device, including but not limited to single-core processors; single processors with software multithreading execution capability; multi-core processors; multi-core processors with software multithreading execution capability; multi-core processors with hardware multithreading technology; parallel platforms; and parallel platforms with distributed shared memory. In addition, the processor may utilize nanoscale architectures, such as, but not limited to, molecular and quantum dot based transistors, switches, and gates, in order to optimize space usage or enhance performance of user devices. The processor may also be implemented as a combination of computational processing units.

[0046] In addition, in some aspects, the functionality described herein may be provided within a dedicated software module or hardware module configured as described herein. Moreover, the technology may be fully implemented in one or more circuits or logic elements. A general-purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of an SPU / MPU and a microprocessor, multiple microprocessors, one or more microprocessors combined with an SPU core, an MPU core, or any other such configuration. One or more components of the SPU or electronic device described herein may be implemented in the form of one or more of a "chip," a "package," an integrated circuit (IC).

[0047] According to exemplary embodiments, systems and methods are provided for performing anticipatory detection of a user requiring an autonomous vehicle pick-up and performing one or more vehicle actions in conjunction with the anticipatory detection without active input, thereby improving the convenience and efficiency of vehicle autonomy.

[0048] Existing ride-hailing / vehicle pickup services require active input from the user to request a pickup. According to an exemplary embodiment, the system and method of the present disclosure do not require any conscious user input, nor are they limited to location or time constraints. In addition, according to an exemplary embodiment, the system and method of the present disclosure do not require any additional sensors on the vehicle.

[0049] Now refer to Figure 1 , a system 10 for performing anticipatory detection of a user requiring an autonomous vehicle pick-up and performing one or more vehicle actions in conjunction with the anticipatory detection is illustratively depicted according to an exemplary embodiment of the present disclosure.

[0050] According to an exemplary embodiment, the system includes a vehicle 100 , one or more users 140 , and one or more smart devices 145 (eg, smart phones, tablet computers, laptop computers, and / or other suitable devices) in electronic communication with the vehicle 100 .

[0051] The vehicle 100 may be an autonomous vehicle, a semi-autonomous vehicle, and / or other suitable vehicle. According to an exemplary embodiment, the vehicle 100 may include one or more sensors, such as one or more LiDAR sensors 105, one or more radio detection and ranging (RADAR) sensors 110, one or more cameras 115, and / or one or more position determination sensors 120 (e.g., one or more global positioning system devices), in addition to other suitable sensors. According to an exemplary embodiment, the one or more sensors may be in electronic communication with one or more computing devices 125. The one or more computing devices 125 may be separate from the one or more sensors and / or may be incorporated into the one or more sensors. According to an exemplary embodiment, the one or more smart devices 145 may communicate wired and / or wirelessly with the one or more computing devices 125 (directly and / or via one or more intermediaries, such as the cloud 150 and / or other suitable communication devices). According to an exemplary embodiment, the vehicle 100 and / or the one or more computing devices 125 may include one or more transceivers 155 configured to send and / or receive digital information through, for example, the cloud 150. According to an exemplary embodiment, data from the vehicle 100 and / or one or more smart devices 145 can be used to calculate the possible need for a ride based on an index value (trigger value). Figure 2 is shown in the logical diagram.

[0052] like Figure 2 As shown, the data may include real-time user information 216, organization information 218, and historical user information 220. According to an exemplary embodiment, three main areas of the component feed information / data into the aggregate information subsections 216, 218, 220. These areas of the component are known data sources.

[0053] According to an exemplary embodiment, the first data source 202 can feed into the real-time user information 216. The first data source 202 can include data from one or more mobile applications 204, data from one or more wearable smart devices 206 (e.g., smart device 145), one or more smart devices 208 (e.g., smart device 145), and / or other suitable data segments and / or data sources. According to an exemplary embodiment, the one or more wearable smart devices 206 and / or one or more smart devices (e.g., smart devices 145, 208) can include one or more health / fitness devices, smart phones, laptops, desktop computers, tablets, smart wearable devices, bio-modifications, and / or other suitable smart technologies.

[0054] According to an exemplary embodiment, the second data source 210 can feed into the organization information 218. The second data source 210 can include data from one or more smart devices 208 (e.g., smart device 145), one or more map / location management applications and / or devices 212, and / or other suitable data segments and / or data sources.

[0055] According to an exemplary embodiment, the third data source 214 can feed into the historical user information 220. The third data source 214 can include data from one or more smart devices 208 (e.g., smart device 145), one or more map / location management applications and / or devices 212, and / or other suitable data segments and / or data sources.

[0056] According to an exemplary embodiment, data may flow to a smart wearable and / or software / system logic controller 222. The logic controller 222 may be configured to generate and send a signal and / or request to the vehicle 100 instructing the vehicle 100 to pick up a user.

[0057] According to an exemplary embodiment, the logic controller 222 may be configured to generate and / or calculate a trigger value.

[0058] According to an exemplary embodiment, the vehicle 100 may be configured to determine whether a trigger value exceeds a threshold and generate a confirmation of the pick-up after the trigger value exceeds the threshold.

[0059] According to an exemplary embodiment, when the vehicle 100 is parked, once the user leaves the vehicle 100, real-time user information 216, facility information 218, and historical user information 220 may be collected. According to an exemplary embodiment, once the user leaves the vehicle 100, real-time user information 216, facility information 218, and historical user information 220 are continuously collected.

[0060] According to an exemplary embodiment, real-time user information 216, establishment information 218, and historical user information 220 are known data sources. Real-time user information 216 may be new data received from a user. Establishment information 218 may be data related to a user's destination, collected and eliminated from multiple users over time. Historical user information 220 may be data of a user's historical patterns.

[0061] According to an exemplary embodiment, the data may be processed in conjunction with machine learning to calculate the likelihood of a user's pick-up request. Through machine learning, the system 10 may be configured to recognize previous patterns and behaviors of visited destinations to more accurately predict pick-ups. According to an exemplary embodiment, for new destinations, the system 10 may use a larger amount of data input compared to previously visited destinations. According to an exemplary embodiment, certain data segments may be given a higher value than other data segments based on reliability to aid in the anticipation of pick-up trigger values.

[0062] According to an exemplary embodiment, the default weights of the data may be changed dynamically based on the user's behavior. According to an exemplary embodiment, no two users will have the same calculations to anticipate a ride request. According to an exemplary embodiment, the default weights may be adjusted dynamically via machine learning of user behavior.

[0063] According to an exemplary embodiment, the system 10 and associated logic may be applied to ride-sharing applications and services, robo-taxi applications and services, and / or other suitable applications and services, such as but not limited to bicycle sharing, scooter sharing, car sharing, etc.

[0064] According to an exemplary embodiment, none of this data originates or needs to originate from within the vehicle 100, thereby eliminating the need for one or more vehicle sensors to anticipate a user pickup. For example, according to an exemplary embodiment, if a user is expected to approach the vehicle for a pickup, the system can utilize existing biometric / location sensors on the user to anticipate a stop for a pickup. However, it should be noted that other means of automatically determining user pickups and / or data collection may be utilized while maintaining the spirit and functionality of the present disclosure.

[0065] According to an exemplary embodiment, the computing device 125 and / or the system logic controller 222 may include a processor 130 and / or a memory 135. The memory 135 may be configured to store programming instructions that, when executed by the processor 130, may be configured to cause the processor 130 to perform one or more tasks, such as, for example, determining whether an autonomous vehicle (AV) is stopped, determining the location of the AV, determining whether a pick-up is available based on the location of the AV, determining whether a pick-up is required, analyzing stored data and / or collected / generated data related to user destinations, facilities / destinations, and users, calculating a trigger value, performing one or more calculation parameters to dynamically adjust the trigger value, determining whether the trigger value is greater than a threshold, triggering the AV to pick up, and / or performing one or more vehicle actions (e.g., performing the AV pick-up, applying generated brakes, adjusting the speed of the vehicle, etc.), among other functions.

[0066] Now refer to Figure 3 , illustratively depicts a flow chart of a method 300 for performing anticipatory detection of a user requiring autonomous vehicle pickup and performing one or more vehicle actions in conjunction with the anticipatory detection according to an exemplary embodiment of the present disclosure.

[0067] At 302, it is determined whether the autonomous vehicle (AV) is parked. According to an exemplary embodiment, when the AV is not parked, the method ends. According to an exemplary embodiment, when the AV is parked, then at 304, the parking position of the AV is determined.

[0068] According to an exemplary embodiment, the parking position of the AV may be determined using, for example, a sensor such as a GPS sensor, a camera sensor, and / or other suitable position determination sensor. According to an exemplary embodiment, determining the parking position of the AV may include determining the type of parking place (e.g., driveway, parking lot, street parking, parking garage, etc.) where the AV is currently parked.

[0069] According to an exemplary embodiment, it may be determined whether the position of the AV is a new position at 306. According to an exemplary embodiment, when the position of the AV is not a new position, stored data related to the position may be analyzed at 308 and then used to calculate a trigger value at 318.

[0070] According to an exemplary embodiment, when the location of the AV is a new location, then at 310, it is determined whether remote parking is available for the new location and whether a pick-up is required at the location. According to an exemplary embodiment, determining whether the location is available for remote parking includes determining whether the parking location meets predetermined criteria, such as, but not limited to, the ability of the AV to park at the destination, the distance from the destination, and / or other suitable criteria. For example, when the parking spot location is a minimum threshold distance from the destination, a pick-up may be required at the location, while when the parking spot location is not the minimum threshold distance from the destination, a pick-up is not required. According to an exemplary embodiment, when remote parking is not available for the new location and / or a pick-up is not required, the method ends.

[0071] According to an exemplary embodiment, when a ride is needed at the location, data related to the use of the ride is collected. The data collection includes, but is not limited to, collecting user destination information at 312, collecting facility information at 314, and collecting user information at 316. At 318, the data can be used to calculate a trigger value.

[0072] According to an exemplary embodiment, user destination information may be collected and / or determined based on the parking spot location and user information such as location. According to an exemplary embodiment, once the user destination is determined, data specific to the institution may be collected at 314, and data related to the user information may be collected at 316. The institution information may include, but is not limited to, the institution's working hours, historical data (such as, for example, the average time that the user or others have previously spent at the institution), and / or other suitable information. The user information may include, but is not limited to, real-time information related to the user (e.g., user digital behavior, user vital signs / data, voice recognition, payment, and / or other suitable real-time information), historical information related to the user (e.g., user historical travel data, institution visit frequency, visit duration, and / or other suitable historical information) and / or other suitable data related to the user. According to various embodiments, one or more portions of the data may be tracked and / or collected by the AV.

[0073] According to an exemplary embodiment, using machine learning and pattern recognition, the AV can be configured to recognize the user's behavior and anticipate pick-ups based on the collected data. For example, if the user repeatedly visits an establishment, the logic can recognize this and more accurately predict pick-up requests.

[0074] According to an exemplary embodiment, using machine learning and pattern recognition, the system can calculate a trigger value at 318. According to an exemplary embodiment, the data inputs contributing to the trigger value are calculated based on a weight of the likelihood of signaling a request for a ride based on the behavior pattern. Once the trigger value is calculated, one or more calculation parameters are executed at 320.

[0075] The trigger value indicates a probability percentage that a pickup request is needed. According to various embodiments, the calculation parameter dynamically adjusts the trigger value based on one or more data points collected and / or generated.

[0076] According to an exemplary embodiment, once the calculation parameters are performed, it is determined whether the trigger value is greater than a threshold at 322. When the trigger value exceeds the threshold, the trigger value is calculated again at 318. When the trigger value does not exceed the threshold, the remote parking pick-up is triggered at 324, so that the AV begins the expected remote parking pick-up.

[0077] Reference now Figure 4 , provides an illustration of an example architecture for computing device 400. According to an exemplary embodiment, one or more functions of the present disclosure may be implemented by a computing device, such as, for example, computing device 400 or a computing device similar to computing device 400.

[0078] Figure 4 The hardware architecture of represents an exemplary embodiment of a representative computing device configured to execute one or more methods and apparatus for performing an anticipated detection of a need for an autonomous vehicle pick-up and performing one or more vehicle actions in conjunction with the anticipated detection, as described herein. Figure 4 The computing device 400 may be configured to implement the method(s) described herein (eg, Figure 3 300) and / or implement at least a portion of the system(s) described herein (e.g., Figure 1 at least a portion of the functionality of system 100).

[0079] Some or all components of computing device 400 may be implemented as hardware, software, and / or a combination of hardware and software. Hardware may include, but is not limited to, one or more electronic circuits. Electronic circuits may include, but are not limited to, passive components (e.g., resistors and capacitors) and / or active components (e.g., amplifiers and / or microprocessors). Passive and / or active components may be adapted, arranged, and / or programmed to perform one or more of the methods, processes, or functions described herein.

[0080] like Figure 4 As shown, computing device 400 may include user interface 402, central processing unit ("CPU") 406, system bus 410, memory 412 connected to and accessible by other parts of computing device 400 via system bus 410, and hardware entities 414 connected to system bus 410. The user interface may include input devices and output devices, which may be configured to facilitate user-software interaction for controlling the operation of computing device 400. Input devices may include, but are not limited to, physical and / or tactile keyboard 440. Input devices may be connected via a wired or wireless connection (e.g., The output device may include, but is not limited to, a speaker 442, a display 444, and / or a light emitting diode 446.

[0081] At least some of the hardware entities 414 may be configured to perform actions involving access to and use of memory 412, which may be random access memory (RAM), a disk drive, and / or a compact disk read-only memory (CD-ROM), among other suitable memory types. The hardware entities 414 may include a disk drive unit 416, which includes a computer-readable storage medium 418 on which may be stored one or more sets of instructions 420 (e.g., program instructions such as, but not limited to, software code) configured to implement one or more of the methods, processes, or functions described herein. The instructions 420 may also reside, in whole or in part, within the memory 412 and / or the CPU 406 during execution thereof by the computing device 400.

[0082] The memory 412 and the CPU 406 may also constitute machine-readable media. As used herein, the term "machine-readable medium" refers to a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) that store one or more sets of instructions 420. As used herein, the term "machine-readable medium" also refers to any medium that can store, encode, or carry a set of instructions 420 for execution by the computing device 400 and cause the computing device 400 to perform any one or more of the methods of the present disclosure.

[0083] Now refer to Figure 5 , an example vehicle system architecture 500 for a vehicle according to an exemplary embodiment of the present disclosure is provided.

[0084] The vehicle 100 may be configured to be combined with Figure 5 Therefore, the following discussion of vehicle system architecture 500 is sufficient to understand one or more components of vehicle 100 .

[0085] like Figure 5 As shown, the vehicle system architecture 500 may include an engine, an electric motor or a propulsion device (e.g., a booster) 502 and various sensors 504-518 for measuring various parameters of the vehicle system architecture 500. In a gas-powered or hybrid vehicle having a fuel-powered engine, the sensors 504-518 may include, for example, an engine temperature sensor 504, a battery voltage sensor 506, an engine revolutions per minute (RPM) sensor 508, and / or a throttle position sensor 510. If the vehicle is an electric vehicle or a hybrid vehicle, then the vehicle may include an electric motor and, accordingly, may include sensors such as a battery monitoring system 512 (for measuring the current, voltage, and / or temperature of the battery), motor current 514 and voltage 516 sensors, and motor position sensors such as resolvers and encoders 518.

[0086] Operating parameter sensors common to both types of vehicles may include, for example: a position sensor 534, such as an accelerometer, gyroscope, and / or inertial measurement unit; a speed sensor 536; and / or an odometer sensor 538. The vehicle system architecture 500 may also include a clock 542, which the system uses to determine the vehicle time and / or date during operation. The clock 542 may be encoded into the onboard computing device 520, it may be a separate device, or multiple clocks may be available.

[0087] The vehicle system architecture 500 may also include various sensors that operate to collect information about the environment in which the vehicle is traveling. These sensors may include, for example: a position sensor 544 (e.g., a global positioning system (GPS) device); an object detection sensor, such as one or more cameras 546; a LiDAR sensor system 548; and / or a radar and / or sonar system 550. The sensors may also include an environmental sensor 552, such as, for example, a humidity sensor, a precipitation sensor, a light sensor, and / or an ambient temperature sensor. The object detection sensor may be configured to enable the vehicle system architecture 500 to detect objects within a given distance range of the vehicle in any direction, while the environmental sensor 552 may be configured to collect data about environmental conditions within the vehicle's travel area. According to an exemplary embodiment, the vehicle system architecture 500 may include one or more lights 554 (e.g., headlights, floodlights, flashlights, etc.).

[0088] During operation, information may be transmitted from sensors to the onboard computing device 520 (e.g., Figure 4 The onboard computing device 520 may be configured to analyze data captured by sensors and / or data received from data providers, and may be configured to selectively control operation of the vehicle system architecture 500 based on the results of the analysis. For example, the onboard computing device 520 may be configured to control: braking via a brake controller 522; direction via a steering controller 524; speed and acceleration via a throttle controller 526 (in a gas-powered vehicle) or a motor speed controller 528 (such as a current level controller in an electric vehicle); a differential gear controller 530 (in a vehicle with a transmission); and / or other controllers. The brake controller 522 may include a pedal force sensor and / or a simulator temperature sensor, as described herein.

[0089] The geographic location information may be transmitted from the location sensor 544 to the onboard computing device 520, which may then access a map of the environment corresponding to the location information to determine known fixed features of the environment, such as streets, buildings, stop signs, and / or stop / go signals. Captured images from the camera 546 and / or object detection information captured from sensors such as LiDAR 548 may be transmitted from those sensors to the onboard computing device 520. The object detection information and / or captured images may be processed by the onboard computing device 520 to detect objects in the vicinity of the vehicle. Any known or known techniques for performing object detection based on sensor data and / or captured images may be used in the embodiments disclosed in this document.

[0090] What has been described above includes examples of the present disclosure. Of course, for the purpose of describing the subject matter, it is not possible to describe every conceivable combination of components or methods, but it should be understood that many further combinations and permutations of the present disclosure are possible. Therefore, the claimed subject matter is intended to cover all such changes, modifications and variations that fall within the spirit and scope of the appended claims.

[0091] Specifically and with respect to the different functions performed by the components, devices, systems, etc. described above, unless otherwise indicated, the terms used to describe such components (including references to "means") are intended to correspond to any components that perform the specified functions of the described components (e.g., functional equivalents), even if such components are not structurally equivalent to the disclosed structures, which perform the functions in the exemplary aspects of the claimed subject matter presented herein.

[0092] The aforementioned systems and components have been described with respect to the interaction between several components. It is to be understood that such systems and components may include those components or specified subcomponents, some specified components or subcomponents, and / or additional components, and according to the aforementioned different permutations and combinations. Subcomponents may also be implemented as components that are communicatively coupled to other components, rather than being included in a parent component (hierarchical). In addition, it should be noted that one or more components may be combined into a single component that provides an aggregation function or may be divided into several separate subcomponents. Any component described herein may also interact with one or more other components that are not specifically described herein.

[0093] Furthermore, while particular features of the invention may be disclosed with respect to only one of several implementations, such features may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms "comprises," "including," "having," "comprising," variations thereof, and other similar words are used in the detailed description or claims, these terms are intended to be inclusive in a manner similar to the term "comprising" as an open transitional word and do not exclude any additional or other elements.

[0094] Therefore, the embodiments and examples set forth herein are presented in order to best explain the various selected embodiments of the present invention and their specific applications, and thereby enable those skilled in the art to make and use the embodiments of the present invention. However, those skilled in the art will recognize that the above description and examples have been given for purposes of illustration and example only. The set forth description is not intended to be exhaustive or to limit the embodiments of the present invention to the precise forms disclosed.

Claims

1. A method for performing anticipatory detection of a user requiring a pick-up by an autonomous vehicle, include: Using a computing device comprising a processor and a memory: Determine the location of the autonomous vehicle; determining whether a pickup is required at the location; When a ride is needed at the location, collecting data related to the user and the destination; Based on the data, a trigger value is calculated, wherein the trigger value indicates a probability percentage of requiring a pick-up request; determining whether the trigger value is greater than a threshold; and When the trigger value is greater than the threshold, the pick-up is triggered, so that the autonomous vehicle performs the pick-up.

2. The method according to claim 1, in, Determining the position of the autonomous vehicle includes determining whether the autonomous vehicle is stopped.

3. The method according to claim 1, in, Determining whether a pickup is required at the location includes determining whether the parking location meets predetermined criteria.

4. The method according to claim 1, in, The data related to the user includes one or more of the following: User digital behavior data; User physiological data; User voice recognition data; User payment history; and User historical travel data.

5. The method according to claim 1, in, The data related to the destination includes one or more of the following: Historical data, including: whether the user has previously been to the destination; the average time frame for how long a user has visited a destination during a journey to the destination; and the average time frame for how long a typical customer visits a destination during the journey to that destination; Data on whether the destination in question is an institution; and When the destination is an institution, the working hours of the institution.

6. The method according to claim 1, in, Calculating the trigger value includes: One or more calculation parameters are performed based on the data to dynamically adjust the trigger value. The method according to claim 1 , further comprising, when the trigger value is not greater than the threshold value, recalculating the trigger value.

8. A system for performing anticipatory detection of a user requiring a pick-up by an autonomous vehicle, include: Autonomous vehicles, including: processor; Memory; and one or more position sensors, Wherein, the processor is configured to: determining a position of the autonomous vehicle using the one or more position sensors; determining whether a pickup is required at the location; When a ride is needed at the location, collecting data related to the user and the destination; Based on the data, a trigger value is calculated, wherein the trigger value indicates a probability percentage of requiring a pick-up request; determining whether the trigger value is greater than a threshold; and When the trigger value is greater than the threshold, the pick-up is triggered, so that the autonomous vehicle performs the pick-up.

9. The system according to claim 8, in, Determining the position of the autonomous vehicle includes determining whether the autonomous vehicle is stopped.

10. The system according to claim 8, in, Determining whether a pickup is required at the location includes determining whether the parking location meets predetermined criteria.

11. The system according to claim 8, in, The data related to the user includes one or more of the following: User digital behavior data; User physiological data; User voice recognition data; User payment history; and User historical travel data.

12. The system according to claim 8, in, The data related to the destination includes one or more of the following: Historical data, including: Whether the user has reached the destination before; the average time frame for how long a user has visited a destination during a trip to the destination; and The average time frame for how long a typical customer visits a destination during a trip to the destination; Data on whether the destination in question is an institution; and When the destination is an institution, the working hours of the institution.

13. The system according to claim 8, in, Calculating the trigger value includes: One or more calculation parameters are performed based on the data to dynamically adjust the trigger value.

14. The system according to claim 8, in, When the trigger value is not greater than the threshold, the processor is further configured to recalculate the trigger value.

15. A system for performing anticipatory detection of a user requiring a pick-up by an autonomous vehicle, include: an autonomous vehicle, including one or more position sensors; as well as A computing device comprising a processor and a memory, the memory being configured to store program instructions which, when executed by the processor, cause the processor to: determining a position of the autonomous vehicle using the one or more position sensors; determining whether a pickup is required at the location; When a ride is needed at said location, data related to the user and the destination is collected; Based on the data, a trigger value is calculated, wherein the trigger value indicates a probability percentage of requiring a pick-up request; determining whether the trigger value is greater than a threshold; and When the trigger value is greater than the threshold, the pick-up is triggered, so that the autonomous vehicle performs the pick-up.

16. The system according to claim 15, in, Determining the position of the autonomous vehicle includes determining whether the autonomous vehicle is stopped.

17. The system according to claim 15, in, Determining whether a pickup is required at the location includes determining whether the parking location meets predetermined criteria.

18. The system according to claim 15, in: The data related to the user includes one or more of the following: User digital behavior data; User physiological data; User voice recognition data; User payment history; as well as User historical travel data, and The data related to the destination includes one or more of the following: Historical data, including: Whether the user has reached the destination before; the average time frame for how long a user has visited a destination during a trip to the destination; and The average time frame for how long a typical customer visits a destination during a trip to the destination; Data on whether the destination in question is an institution; and When the destination is an institution, the working hours of the institution.

19. The system according to claim 15, in, Calculating the trigger value includes: One or more calculation parameters are performed based on the data to dynamically adjust the trigger value.

20. The system according to claim 15, in, When the trigger value is not greater than the threshold, the program instructions, when executed, further cause the processor to recalculate the trigger value.