Method, apparatus, device, storage medium and program product for traveling

Abstract

According to embodiments of the present disclosure, methods, apparatuses, devices, computer-readable storage media, and computer program products for a trip are provided. The method includes presenting a target interface associated with a trip service provided by an autonomous vehicle; and presenting at least one target station in the target interface, the at least one target station including a pickup station and / or a drop-off station, wherein the at least one target station is determined based on a process of determining a first expected time instant for the autonomous vehicle to arrive at a set of candidate stations; determining whether the set of candidate stations are allowed to stop at the first expected time instant based on a time-sharing attribute of the set of candidate stations, the time-sharing attribute indicating stop constraints of the set of candidate stations for at least one time period; and determining the at least one target station from the set of candidate stations that are allowed to stop at the first expected time instant. In this way, embodiments of the present disclosure can enable the autonomous vehicle to safely pick up and drop off users.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein generally relate to the field of computers, and particularly to methods, apparatus, devices, computer-readable storage media, and computer program products for travel. Background Technology

[0002] With the rapid development of autonomous driving technology, it is being widely used to serve people's daily travel needs.

[0003] However, autonomous vehicles may pass through areas that are not conducive to their operation while picking up and dropping off users, which may affect their performance. Summary of the Invention

[0004] In a first aspect of this disclosure, a method for travel is provided. The method includes: presenting a target interface associated with a travel service provided by an autonomous vehicle; and presenting at least one target station in the target interface, the at least one target station including a pick-up station and / or a drop-off station, wherein the at least one target station is determined based on: determining a first expected time when the autonomous vehicle will arrive at a set of candidate stations; determining whether the set of candidate stations is permitted to stop at the first expected time based on time-sharing attributes of the set of candidate stations, the time-sharing attributes indicating stop constraints of the set of candidate stations during at least one time period; and determining from the set of candidate stations at least one target station permitted to stop at the first expected time.

[0005] In a second aspect of this disclosure, an apparatus for mobility is provided. The apparatus includes: a first display module configured to present a target interface associated with a mobility service provided by an autonomous vehicle; and a second display module configured to present at least one target station in the target interface, the at least one target station including a pick-up station and / or a drop-off station, wherein the at least one target station is determined based on the following process: determining a first expected time when the autonomous vehicle will arrive at a set of candidate stations; determining whether the set of candidate stations is permitted to stop at the first expected time based on time-sharing attributes of the set of candidate stations, the time-sharing attributes indicating stop constraints of the set of candidate stations during at least one time period; and determining from the set of candidate stations at least one target station permitted to stop at the first expected time.

[0006] In a third aspect of this disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the device to perform the method of the first aspect.

[0007] In a fourth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program that can be executed by a processor to implement the method of the first aspect.

[0008] In a fifth aspect of this disclosure, a computer program product is provided. The computer program product includes computer-executable instructions that, when executed by a processor, implement the method of the first aspect.

[0009] It should be understood that the content described in this summary section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0011] Figure 1 A schematic diagram of an example environment in which embodiments of the present disclosure can be implemented is shown;

[0012] Figures 2A to 2H Example user interfaces according to some embodiments of this disclosure are shown;

[0013] Figure 3 A flowchart illustrating an example process for a travel service according to some embodiments of this disclosure is shown;

[0014] Figure 4 A flowchart illustrating an example process for determining at least one target site according to some embodiments of the present disclosure is shown;

[0015] Figure 5 A schematic structural block diagram of an example device for travel according to certain embodiments of the present disclosure is shown; and

[0016] Figure 6 A block diagram of an apparatus capable of implementing several embodiments of the present disclosure is shown. Detailed Implementation

[0017] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0018] It should be noted that the headings of any section / subsection provided herein are not limiting. Various embodiments are described throughout this document, and embodiments of any type may be included under any section / subsection. Furthermore, embodiments described in any section / subsection may be combined in any way with any other embodiments described in the same section / subsection and / or different sections / subsections.

[0019] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below. The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0020] The embodiments of this disclosure may involve user data, data acquisition, and / or use. All of these aspects comply with applicable laws, regulations, and relevant provisions. In the embodiments of this disclosure, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, in implementing the embodiments of this disclosure, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained in accordance with relevant laws and regulations through appropriate means. The specific methods of notification and / or authorization may vary depending on the actual situation and application scenario, and the scope of this disclosure is not limited in this respect.

[0021] In this specification and the embodiments, any processing of personal information will be carried out only under the premise of legality (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be carried out within the scope stipulated or agreed upon. A user's refusal to process personal information other than that necessary for basic functions will not affect the user's use of basic functions.

[0022] As briefly mentioned earlier, autonomous vehicles can typically only operate within a pre-defined area. Certain areas within this area experience high pedestrian or vehicular traffic during peak hours. Examples include hospitals, schools, and subway stations serving as transportation hubs. These areas are unsuitable for autonomous vehicles during peak hours.

[0023] Embodiments of this disclosure propose a scheme for travel. The scheme includes: presenting a target interface associated with a travel service provided by an autonomous vehicle; and presenting at least one target station in the target interface, the at least one target station including a pick-up station and / or a drop-off station, wherein the at least one target station is determined based on the following process: determining a first expected time when the autonomous vehicle will arrive at a set of candidate stations; determining whether the set of candidate stations is permitted to stop at the first expected time based on time-sharing attributes of the set of candidate stations, the time-sharing attributes indicating stopping constraints of the set of candidate stations during at least one time period; and determining at least one target station from the set of candidate stations that is permitted to stop at the first expected time.

[0024] In this way, the embodiments of this disclosure can complete the order placement, dispatch, and drop-off stages of a travel order based on the time-sharing attributes of the area involved in the trip, so that autonomous vehicles can avoid arriving at stations where the corresponding stations are in no-stopping periods when picking up and dropping off users, thereby affecting users' travel.

[0025] The following section provides a detailed description of various example implementations of this scheme, with reference to the accompanying drawings.

[0026] Example Environment

[0027] Figure 1 A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. For example... Figure 1 As shown, example environment 100 may include terminal device 110.

[0028] In this example environment 100, terminal device 110 may run an application 120 for travel. Application 120 may be any suitable type of application for travel, examples of which may include, but are not limited to, ride-hailing applications, ride-hailing apps, or other suitable applications. User 140 may interact with application 120 via terminal device 110 and / or its attached devices.

[0029] exist Figure 1 In environment 100, if application 120 is active, terminal device 110 can use application 120 to present interface 150 for supporting travel.

[0030] In some embodiments, terminal device 110 communicates with server 130, enabling server 130 to allocate autonomous vehicle 160 for providing travel services to user 140, thereby providing services to application 120. Terminal device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, handheld computers, portable gaming terminals, VR / AR devices, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, terminal device 110 can also support any type of interface for user 140 (such as "wearable" circuitry).

[0031] Server 130 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. Server 130 may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in a cloud environment, etc. Server 130 can provide backend services for the travel application 120 in terminal device 110.

[0032] A communication connection can be established between server 130, terminal device 110, and autonomous vehicle 160. This communication connection can be established via wired or wireless means. The communication connection may include, but is not limited to, Bluetooth, mobile network, Universal Serial Bus (USB), and Wireless Fidelity (WiFi) connections; the embodiments of this disclosure are not limited in this respect. In the embodiments of this disclosure, server 130 and terminal device 110 can achieve signaling interaction through their communication connection.

[0033] A communication connection can be established between the autonomous vehicle 160 and the terminal device 110. This communication connection can be established via wired or wireless means. The communication connection may include, but is not limited to, Bluetooth, mobile network, Universal Serial Bus (USB), and Wireless Fidelity (WiFi) connections, and the embodiments of this disclosure are not limited in this respect. In the embodiments of this disclosure, the autonomous vehicle 160 and the terminal device 110 can achieve signaling interaction through the communication connection between them.

[0034] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of this disclosure.

[0035] The following description will continue with reference to the accompanying drawings, which will provide some exemplary embodiments of this disclosure.

[0036] Example interactive interface

[0037] Figures 2A to 2H Example interfaces 200A to 200H according to some embodiments of the present disclosure are shown. Interfaces 200A to 200H may, for example, be provided by... Figure 1 The terminal device 110 shown is provided.

[0038] like Figure 2A As shown, when the travel application 120 on the terminal device 110 is launched by the user 140, the terminal device 110 can present an interface 200A. In some embodiments, the interface 200A may include a station input area 210 for inputting a boarding station and a drop-off station. The station input area 210 may display a prompt indicating the boarding station and its location name, and a prompt indicating the drop-off station and its location name. As an example, the prompt may be the words "boarding point" and "drop-off point".

[0039] In some embodiments, the terminal device 110 may obtain the location name corresponding to the boarding station in the station input area 210 through its configured positioning system or by obtaining the content input by the user 140.

[0040] In some embodiments, the area corresponding to the "boarding point" in the station input area 210 may be configured with a control 215 for inputting the boarding point. For example, the control 215 may display the word "Select". As an example, when the application 120 for travel is launched by the user 140, the interface presented by the terminal device 110 may display the location name of the boarding point obtained through the location system. If the boarding point indicated by the location name displayed at this time is not the boarding point expected by the user 140, the user 140 can click the control 215 to reselect the boarding point.

[0041] Reference Figure 2B In some embodiments, when the terminal device 110 receives operation information from the user 140 on the control 215 on the interface 200A, the terminal device 110 can display the interface 200B for selecting the boarding or alighting station.

[0042] Continue to refer to Figure 2A In some embodiments, the terminal device 110 can obtain the location name corresponding to the drop-off point in the station input area 210 by acquiring the content input by the user 140. As an example, a text box corresponding to the words "drop-off point" can be configured in the station input area 210. The text box can display the words "Please enter the destination" to guide the user 140 to perform the operation.

[0043] Continue to refer to Figure 2B In some embodiments, when the terminal device 110 receives the operation information of the user 140 on the text box on the interface 200A, the terminal device 110 can display the interface 200B.

[0044] In some embodiments, interface 200B may include a search area 220 and a map display area 230. The search area 220 is used for user 140 to input the name of their desired boarding or alighting point. The map display area 230 is used to display the current location of user 140. As an example, the map display area 230 may also be configured with a first icon 231 to mark the current location of user 140.

[0045] In some embodiments, the search area 220 may be configured with a search box 222 and a control 224 for triggering a search. User 140 can select a boarding or alighting station by entering a location name in the search box 222. As an example, the search box 222 may display text guiding user 140's operation, such as "Please enter a location name." User 140 can enter the location name in the search box 222 using input methods such as writing or voice input. The control 224 may display the word "Search" or an icon indicating the search meaning. When terminal device 110 receives the operation information of user 140 on control 224 on interface 200B, terminal device 110 can obtain the location name of the boarding or alighting station desired by user 140 and perform a search. Subsequently, terminal device 110 can display interface 200C to display search results related to the location name entered by user 140. User 140 can select from multiple candidate stations in the search results.

[0046] Reference Figure 2C In some embodiments, interface 200C may include a search area 220 and a map display area 230. Search area 220 may include a search box 222, a control 224 for triggering a search, and a result display area 240 for displaying search results. As an example, the style and function of the search box 222 and control 224 in interface 200C may be consistent with those in interface 200B. When terminal device 110 displays interface 200C, the search box 222 may display the location name entered by user 140. If multiple sites in the search results are not the sites expected by user 140, terminal device 110 may, upon receiving operation information from user 140 on control 224 in interface 200C, search for the location name re-entered by user 140.

[0047] In some embodiments, the results display area 240 may display multiple stations associated with the location name entered by the user 140. The results display area 240 may also display time-sharing attributes 245 for multiple stations. Time-sharing attributes 245 indicate the station's stopping constraints during at least one time period. As an example, when a station is a time-sharing station, the results display area 240 displays the time-sharing period for that station. Additionally, the results display area 240 may also display the reason for the station's no-stopping policy. The reason for the no-stopping policy is the reason why the station is prohibited from stopping during the time-sharing period. When a station is not a time-sharing station, the results display area 240 may display the station's location name. For some stations that are not time-sharing stations, they may also be no-stopping stations. In this case, the results display area 240 may display the reason for the station's no-stopping policy.

[0048] In some embodiments, since multiple sites in the search results may have time-sharing stations or no-parking stations that are not conducive to the parking of the autonomous vehicle 160, these time-sharing stations and no-parking stations need to be set to an unselectable state. As an example, the unselectable state can be achieved by graying out the time-sharing stations and no-parking stations. For time-sharing stations, it is necessary to consider whether the current time falls within the time-sharing period. When the current time falls within the time-sharing period of the station, the terminal device 110 can gray out the station.

[0049] In some embodiments, for time-sharing stations that are about to fall into a time-sharing period, the terminal device 110 may set the wording of the station to prompt the user 140. As an example, the terminal device 110 may set the font color of the time-sharing station that is about to fall into a time-sharing period to red.

[0050] When terminal device 110 receives operation information from user 140 in the result display area 240 of interface 200C, terminal device 110 can mark the station selected by user 140. For example, the selected station can be highlighted in the result display area 240, the font style of the selected station can be modified, or a marker such as "●" can be added before the selected station. As an example, map display area 230 can display the current location of user 140 and the location of the station selected by user 140. When user 140 selects a boarding station and an alighting station, and the boarding station is different from the user 140's current location, map display area 230 can also display the current location of user 140 and the locations of the boarding and alighting stations selected by user 140 simultaneously. Alternatively, map display area 230 can display the locations of the boarding and alighting stations selected by user 140 simultaneously. A second icon 232 for marking the location of the station selected by user 140 can be configured in map display area 230. If user 140 selects a boarding station and an alighting station, and the boarding station is not the same as the location of user 140, the first icon 231 in the map display area 230 can be used to represent the location of the boarding station selected by user 140.

[0051] The interfaces 200A to 200C described above allow user 140 to select a boarding or alighting station. In addition to the methods described above, terminal device 110 provides a second method for user 140 to select a boarding or alighting station. As an example, this second method is a "drag-and-drop" method. The interfaces supporting this method will be further described below.

[0052] Continue to refer to Figure 2BIn some embodiments, the area and scale of the map display area 230 can be adjusted. For example, different gestures can be used to adjust the area and scale of the map display area 230. When it is necessary to zoom in on a certain area displayed in the map display area 230, a release gesture can be used on the area's position on the interface 200B. The zoom level depends on the magnitude of the gesture; the greater the magnitude, the greater the zoom level. When it is necessary to zoom out on a certain area displayed in the map display area 230, a pinch gesture can be used on the area's position on the interface 200B. The zoom level depends on the magnitude of the gesture; the greater the magnitude, the greater the zoom level.

[0053] The interface supporting the second method of selecting the boarding station is described below. User 140 can choose not to enter the desired boarding station name in the search box 222, but instead perform a gesture operation 250 on the map display area 230 of interface 200B. When terminal device 110 receives the operation information from user 140 on the map display area 230 of interface 200B, terminal device 110 displays as follows: Figure 2D The interface shown is 200D.

[0054] Reference Figure 2D The content displayed in interface 200D is a magnified view of the area where user 140 is currently located. In some embodiments, interface 200D may display a first icon 231 indicating the current location of user 140 and a second icon 232 indicating the location of the desired boarding stop. When terminal device 110 displays interface 200D, the location of the second icon 232 is defaulted to the location of the first icon 231. User 140 can drag the second icon 232 in interface 200D to select the desired boarding stop. As an example, to prevent user 140 from accidentally dragging the first icon 231 while dragging the second icon 232, terminal device 110 may set the first icon 231 to be a non-draggable icon.

[0055] In some embodiments, when terminal device 110 receives operation information from user 140 on interface 200D, terminal device 110 may display the connecting line 233 between the first icon 231 and the second icon 232. When terminal device 110 no longer receives operation information from user 140 on interface 200D, terminal device 110 may obtain the location of the second icon 232 and determine whether the station corresponding to the location of the second icon 232 has a time-sharing attribute 245 or is a no-stopping station. When terminal device 110 determines that the station corresponding to the location of the second icon 232 is an optional station, terminal device 110 may update the location name corresponding to the "boarding point" in interface 200A based on the location name of the station.

[0056] When the station corresponding to the location of the second icon 232 is a time-sharing station, the terminal device 110 can further determine whether the current time falls within the time-sharing period of that station.

[0057] As an example, if the current time does not fall within the time slot of the station, the terminal device 110 can set the connection line 233 to a solid line to indicate that the station is available. In some embodiments, if the current time is close to the time slot of the station, the terminal device 110 can configure a label 234 pointing to the station in the interface 200D. The label 234 is used to indicate the time slot of the station and the reason for prohibition.

[0058] As an example, if the current time falls within the time slot of the station, the terminal device 110 can set the connection line 233 to an unselectable state to indicate that the station corresponding to the location of the second icon 232 is unselectable. The terminal device 110 can present the unselectable state by setting the connection line 233 to a dashed line or graying it out. In some embodiments, the terminal device 110 can configure a label 234 pointing to the station in the interface 200D. The label 234 is used to indicate the time slot of the station and the reason for prohibition.

[0059] In some embodiments, when the station corresponding to the location of the second icon 232 is a prohibited station, the terminal device 110 can process the station corresponding to the location of the second icon 232 in the same way as the case where the station is a time-sharing station and the current time falls within the time-sharing period. Specifically, the terminal device 110 can present the unselectable state of the station by setting the connecting line 233 to a dashed line or graying it out. Additionally, the terminal device 110 can configure a label 234 pointing to the station in the interface 200D. The label 234 is used to indicate the reason for prohibiting parking at the station.

[0060] In some embodiments, if the station corresponding to the location of the second icon 232 is not a time-sharing station or a no-stopping station, the terminal device 110 can present the optional status of the station by setting the connection line 233 as a solid line.

[0061] If the boarding station selected by user 140 by dragging the second icon 232 is unavailable, user 140 can drag the second icon 232 again to select a new boarding station.

[0062] The interface described above can only support situations where the boarding station desired by user 140 is within the preset range of user 140's location.

[0063] In some scenarios, the following situation may occur: For example, user 140 is currently at point A at time T0, but wants to board the bus at point B at time T1. The following section provides further details on the interface that supports selecting the boarding station in this situation.

[0064] Continue to refer to Figure 2C In some embodiments, when terminal device 110 receives operation information from user 140 on control 224 in interface 200B, terminal device 110 displays interface 200C. In interface 200C, the area range and scale of the map display area 230 can also be adjusted. As an example, the adjustment method for map display area 230 in interface 200C can be consistent with the adjustment method for map display area 230 in interface 200B. When multiple stations displayed in result display area 240 are not the boarding stations expected by user 140, the second icon 232 in map display area 230 can represent the station corresponding to the location name entered by user 140 in search box 222. At this time, user 140 can perform gesture operation 250 on map display area 230 in interface 200C to further select a boarding station. After receiving operation information from user 140 on map display area 230 in interface 200C, terminal device 110 displays as follows: Figure 2E The interface shown is 200E.

[0065] Reference Figure 2E The content displayed on interface 200E is a magnified target area. The target area is the area where the station corresponding to the location name entered by user 140 in search box 222 is located. In some embodiments, interface 200E may display a second icon 232 and a third icon 235. The second icon 232 may represent the location of the station corresponding to the location name entered by user 140 in search box 222. The third icon 235 may represent the location of the boarding station desired by user 140. When terminal device 110 displays interface 200E, the location of the third icon 235 defaults to the location of the second icon 232. User 140 can drag the third icon 235 in interface 200E to select the desired boarding station. As an example, to prevent user 140 from accidentally dragging the second icon 232 while dragging the third icon 235, terminal device 110 may set the second icon 232 as a non-draggable icon.

[0066] In some embodiments, the configuration of interface 200E by terminal device 110 is the same as the configuration of interface 200D. Specifically, when terminal device 110 receives operation information from user 140 on interface 200E, terminal device 110 can display the connecting line 233 between the second icon 232 and the third icon 235. When terminal device 110 no longer receives operation information from user 140 on interface 200E, terminal device 110 can obtain the location of the third icon 235 and determine whether the station corresponding to the location of the third icon 235 has a time-sharing attribute 245 or is a no-stopping station. When terminal device 110 determines that the station corresponding to the location of the third icon 235 is an optional station, terminal device 110 updates the location name corresponding to the "boarding point" in interface 200A based on the location name of the station.

[0067] When the station corresponding to the location of the third icon 235 is a time-sharing station, the terminal device 110 can further determine whether the current time falls within the time-sharing period of that station.

[0068] As an example, if the current time does not fall within the time slot of the station, the terminal device 110 can set the connection line 233 to a solid line to indicate that the station is available. If the current time is close to the time slot of the station, in some embodiments, the terminal device 110 can configure a label 234 pointing to the station in the interface 200E. The label 234 is used to indicate the time slot of the station and the reason for prohibition.

[0069] As an example, if the current time falls within the time slot of the station, the terminal device 110 can set the connection line 233 to an unselectable state to indicate that the station corresponding to the location of the third icon 235 is unselectable. The terminal device 110 can present the unselectable state by setting the connection line 233 to a dashed line or graying it out. In some embodiments, the terminal device 110 can configure a label 234 pointing to the station in the interface 200E. The label 234 is used to indicate the time slot of the station and the reason for prohibition.

[0070] In some embodiments, when the station corresponding to the location of the third icon 235 is a prohibited station, the terminal device 110 can process the station corresponding to the location of the third icon 235 in the same way as the case where the station is a time-sharing station and the current time falls within the time-sharing period. Specifically, the terminal device 110 can present the unselectable state of the station by setting the connecting line 233 to a dashed line or graying it out. Additionally, the terminal device 110 can configure a label 234 pointing to the station in the interface 200E. The label 234 is used to indicate the reason for prohibiting parking at the station.

[0071] In some embodiments, if the station corresponding to the location of the third icon 235 is not a time-sharing station or a no-stopping station, the terminal device 110 can present the optional status of the station by setting the connection line 233 as a solid line.

[0072] If the boarding station selected by user 140 by dragging the third icon 235 is unavailable, user 140 can drag the third icon 235 again to select a new boarding station.

[0073] Reference Figure 2B and Figure 2C The interface supporting the second method of selecting a drop-off point is described below. In some embodiments, when the terminal device 110 receives operation information from the user 140 on the control 224 in the interface 200B, the terminal device 110 displays the interface 200C. When the multiple stations displayed in the result display area 240 are not the drop-off points expected by the user 140, the second icon 232 in the map display area 230 can represent the station corresponding to the location name entered by the user 140 in the search box 222. At this time, the user 140 can perform a gesture operation 250 on the map display area 230 in the interface 200C to further select a drop-off point. After the terminal device 110 receives the operation information from the user 140 on the map display area 230 in the interface 200C, the terminal device 110 displays as follows: Figure 2E The interface shown is 200E.

[0074] Reference Figure 2E In some embodiments, interface 200E may display a second icon 232 and a third icon 235. The second icon 232 may represent the location of the station corresponding to the location name entered by user 140 in search box 222. The third icon 235 may represent the location of the drop-off station desired by user 140. When terminal device 110 displays interface 200E, the location of the third icon 235 defaults to the location of the second icon 232. User 140 can drag the third icon 235 in interface 200E to select the desired drop-off station. As an example, to prevent user 140 from accidentally dragging the second icon 232 while dragging the third icon 235, terminal device 110 may set the second icon 232 as a non-draggable icon.

[0075] In some embodiments, when terminal device 110 receives operation information from user 140 on interface 200E, terminal device 110 may display the connecting line 233 between the second icon 232 and the third icon 235. When terminal device 110 no longer receives operation information from user 140 on interface 200E, terminal device 110 may obtain the location of the third icon 235 and determine whether the station corresponding to the location of the third icon 235 has a time-sharing attribute 245 or is a no-stopping station. When terminal device 110 determines that the station corresponding to the location of the third icon 235 is an optional station, terminal device 110 may update the location name corresponding to the "drop-off point" in interface 200A based on the location name of that station.

[0076] When the station corresponding to the location of the third icon 235 is a time-sharing station, the terminal device 110 can further determine whether the current time falls within the time-sharing period of that station.

[0077] As an example, if the current time does not fall within the time slot of the station, the terminal device 110 can set the connection line 233 to a solid line to indicate that the station is available. If the current time is close to the time slot of the station, in some embodiments, the terminal device 110 can configure a label 234 pointing to the station in the interface 200E. The label 234 is used to indicate the time slot of the station and the reason for prohibition.

[0078] As an example, if the current time falls within the time slot of the station, the terminal device 110 can set the connection line 233 to an unselectable state to indicate that the station corresponding to the location of the third icon 235 is unselectable. The terminal device 110 can present the unselectable state by setting the connection line 233 to a dashed line or graying it out. In some embodiments, the terminal device 110 can configure a label 234 pointing to the station in the interface 200E. The label 234 is used to indicate the time slot of the station and the reason for prohibition.

[0079] In some embodiments, when the station corresponding to the location of the third icon 235 is a prohibited station, the terminal device 110 can process the station corresponding to the location of the third icon 235 in the same way as the case where the station is a time-sharing station and the current time falls within the time-sharing period. Specifically, the terminal device 110 can present the unselectable state of the station by setting the connecting line 233 to a dashed line or graying it out. Additionally, the terminal device 110 can configure a label 234 pointing to the station in the interface 200E. The label 234 is used to indicate the reason for prohibiting parking at the station.

[0080] In some embodiments, if the station corresponding to the location of the third icon 235 is not a time-sharing station or a no-stopping station, the terminal device 110 can present the optional status of the station by setting the connection line 233 as a solid line.

[0081] If the drop-off station selected by user 140 by dragging the third icon 235 is unavailable, user 140 can drag the third icon 235 again to select a new drop-off station.

[0082] In some embodiments, if the boarding or alighting station selected by user 140 is unselectable, terminal device 110 can also reselect the boarding or alighting station by switching stations.

[0083] Reference Figure 2D and Figure 2E In some embodiments, for example, during the order placement phase, when the terminal device 110 determines that the pick-up or drop-off station selected by the user 140 is an unselectable station, the terminal device 110 can select a station whose distance from the station selected by the user 140 is less than a preset distance as a recommended station from interfaces such as interface 200D and interface 200E. The recommended station is an selectable station and can be displayed in interfaces such as interface 200D and interface 200E. As an example, the terminal device 110 can configure a fourth icon 236 for representing the location of the transfer station for interfaces 200D and interface 200E. That is, when the terminal device 110 determines that the pick-up or drop-off station selected by the user 140 is an unselectable station, the terminal device 110 causes interfaces 200D and interface 200E to display the fourth icon 236.

[0084] In some embodiments, while interfaces 200D and 200E display the fourth icon 236, the terminal device 110 can also configure a label 237 pointing to the station represented by the fourth icon 236 in interfaces 200D and 200E. Label 237 is used to indicate the station's information and the reason for the station's relocation. As an example, the station information may include whether the station has a time-sharing attribute 245 and the station's time-sharing period, etc.

[0085] In some embodiments, the terminal device 110 may also configure a site transfer arrow 238 in interfaces 200D and 200E. The site transfer arrow 238 points from the site represented by the second icon 232 or the third icon 235 to the site represented by the fourth icon 236. Additionally, the outline of the second icon 232 or the third icon 235 may be changed to a dashed line to indicate that a transfer has occurred to the site represented by the second icon 232 or the third icon 235.

[0086] In some embodiments, when the fourth icon 236 is displayed in interfaces 200D and 200E, the user 140 can still drag the second icon 232 or the third icon 235 to reselect the boarding or alighting station. When the terminal device 110 receives operation information from the user 140 on the second icon 232 or the third icon 235 again, the terminal device 110 will prevent the fourth icon 236 from being displayed in interfaces 200D and 200E.

[0087] In some embodiments, for scenarios where the order placement stage is completed and the next stage is entered, the terminal device 110 may also cause the site selected by the user 140 in the interface 200D or interface 200E to be transferred.

[0088] In some embodiments, after the terminal device 110 causes the user 140 to transfer the selected site in interface 200D or interface 200E, a fourth icon 236 is displayed in interface 200D or interface 200E. The site corresponding to the fourth icon 236 may be a recommended site. As an example, interface 200D or interface 200E may display a label 237 pointing to the site corresponding to the fourth icon 236. Label 237 is used to indicate the site information of the site corresponding to the fourth icon 236 and the reason for the transfer. Additionally, interface 200D or interface 200E may display a site transfer arrow 238.

[0089] Reference Figure 2F and Figure 2G In some embodiments, after the terminal device 110 transfers the boarding or alighting station selected by the user 140 in the interfaces 200D and 200E, the terminal device 110 can display a prompt box 260 on the interfaces 200D and 200E, such as... Figure 2F The interface shown is 200F and as follows Figure 2G The interface shown is 200G. The prompt box 260 is used to indicate that the site has been moved.

[0090] In some embodiments, the prompt box 260 may include a prompt word 262 and a confirmation control 264. The prompt word 262 may indicate the station where the transfer occurred and the new station. For example, the prompt word 262 may read, "Your selected pick-up / drop-off station has been changed from xxxx to xxxx." The confirmation control 264 is used to determine whether the user 140 is aware of the station transfer. For example, the confirmation control 264 may display the words "Confirm" or "I understand."

[0091] In some embodiments, the following are possible scenarios in which the site selected by user 140 is transferred:

[0092] In the first scenario, user 140 booked a ride with autonomous vehicle 160 at a pick-up point. The current time is earlier than the pick-up point's designated time slot, and the current time is close to the start time of the pick-up point's designated time slot. Autonomous vehicle 160 is expected to arrive at the pick-up point earlier than its designated time slot, but in reality, the pick-up point enters its designated time slot while autonomous vehicle 160 is en route to the pick-up point.

[0093] Scenario 2: User 140 books a ride with autonomous vehicle 160 before arriving at the pick-up point. Autonomous vehicle 160's estimated arrival time at the pick-up point is earlier than the pick-up point's designated time slot and close to the start time of that time slot. Autonomous vehicle 160 arrives at the pick-up point at the estimated time, but user 140 has not yet arrived. When user 140 arrives at the pick-up point, the pick-up point enters its designated time slot.

[0094] The third scenario: When user 140 books a ride with autonomous vehicle 160, the estimated arrival time at the drop-off point is earlier than the designated time slot for that drop-off point, and the estimated arrival time is close to the start time of that drop-off point's designated time slot. Autonomous vehicle 160 is en route to the drop-off point when the drop-off point enters its designated time slot.

[0095] The fourth scenario: When user 140 booked a ride with autonomous vehicle 160, the estimated arrival time at the drop-off point was later than the drop-off point's designated time slot, and the estimated arrival time was close to the end time of the drop-off point's designated time slot. When autonomous vehicle 160 dropped user 140 off at the drop-off point, the drop-off point's designated time slot had not yet ended.

[0096] For the station transfers caused by the first and second scenarios described above, user 140 cannot select a boarding station again. In some embodiments, after a boarding station transfer, terminal device 110 may display the prompt box 260 in interfaces 200F and 200G on the current screen.

[0097] For the station transfers caused by the third and fourth scenarios mentioned above, user 140 can select a drop-off station again. In some embodiments, after the drop-off station is transferred, the terminal device 110 can display the following on the current interface: Figure 2H The prompt box 260 in the interface 200H shown. As an example, prompt box 260 may display the message "Your selected drop-off point has been changed from xxxx to xxxx. You can change your drop-off point again." Alternatively, prompt box 260 may display a confirmation control 264 and a modification control 266. Modification control 266 is used by user 140 to modify the drop-off point. Modification control 266 may display the word "Modify".

[0098] In this way, the embodiments of this disclosure enable user 140 to select pick-up or drop-off stations that do not impose stopping restrictions on autonomous vehicle 160, so that autonomous vehicle 160 can avoid arriving at the station when picking up or dropping off user 140, as the corresponding station is in a no-stopping period, thereby affecting the user's travel.

[0099] Example process

[0100] Figure 3 A flowchart of an example process 300 for a travel service according to some embodiments of the present disclosure is shown. Process 300 can be implemented at terminal device 110. Reference is made below. Figure 1 To describe process 300.

[0101] like Figure 3 As shown in box 310, terminal device 110 presents a target interface associated with the travel services provided by autonomous vehicle 160.

[0102] In some embodiments, the travel service provided by the autonomous vehicle 160 is a service that transports the user 140 from a point of origin to a destination via the autonomous vehicle 160. The target interface presented by the terminal device 110 can be operated by the user 140 so that the autonomous vehicle 160 can pick up and drop off the user 140.

[0103] In box 320, terminal device 110 presents at least one target station in the target interface, wherein the at least one target station includes a boarding station and / or an alighting station.

[0104] In some embodiments, the terminal device 110 may display a pick-up station or a drop-off station on the target interface, or display both pick-up and drop-off stations simultaneously, so that the station planning presented on the target interface can avoid drop-off routes that are not conducive to the autonomous vehicle 160 stopping.

[0105] The following will be further combined Figure 4 This describes the specific process for identifying at least one target site. Figure 4 A flowchart illustrating an example process 400 for determining at least one target site according to some embodiments of the present disclosure is shown. It should be understood that at least one target site can be determined by terminal device 110 and / or server 130. Process 400 will be described below using server 130 as an example.

[0106] Reference Figure 4 In box 410, server 130 determines the first expected moment when autonomous vehicle 160 arrives at a set of candidate stations.

[0107] In some real-time examples, a set of candidate stations consists of stations associated with at least one target station. When the at least one target station is determined to be a boarding station, a set of candidate stations consists of stations associated with the boarding station. When the at least one target station is determined to be a disembarkation station, a set of candidate stations consists of stations associated with the disembarkation station.

[0108] As an example, a set of candidate stations can be stations within a preset distance from the location entered by user 140 in the target interface. Among these stations, those that are convenient for user 140 to reach the location entered in the target interface can be considered as a set of candidate stations. By determining the first expected time when the autonomous vehicle 160 arrives at a set of candidate stations, stations that are unfavorable to the autonomous vehicle 160's parking can be selected to facilitate the autonomous vehicle 160's pick-up and drop-off of user 140.

[0109] In some embodiments, where user 140 has already entered a desired drop-off point, the process by which server 130 determines the first expected time when autonomous vehicle 160 arrives at a set of candidate stations can be as follows:

[0110] First, before allocating service vehicles for the ride-hailing service, server 130 determines the first limited stopping time at each pick-up point. In some embodiments, the first limited stopping time can be the maximum waiting time for autonomous vehicle 160 to wait for user 140 to board at each pick-up point. Road conditions vary at each pick-up point, causing the autonomous vehicle 160 to stay at each pick-up point for varying durations. The first limited stopping time can be determined based on the location of the pick-up point. For pick-up points without a specified first limited stopping time, server 130 can default to a first limited stopping time of 5 minutes.

[0111] Then, server 130 determines a first expected time of arrival at a set of candidate stations based on a first limited stop duration and the expected travel time from the pick-up point to the set of candidate stations. In some embodiments, the expected travel time of autonomous vehicle 160 from the pick-up point to the set of candidate stations can be estimated by the route from the pick-up point to the set of candidate stations and the autonomous vehicle's speed. As an example, the first expected time can be the current time plus the first limited stop duration and the expected travel time. Additionally, when determining the first expected time, server 130 may also consider the time spent allocating a service vehicle and the time spent by autonomous vehicle 160 picking up the vehicle. As an example, the time spent allocating a service vehicle can be assumed to be 1 minute by default. The time spent by autonomous vehicle 160 picking up the vehicle can be assumed to be 10 minutes by default.

[0112] The above method can be used to determine the expected travel time for autonomous vehicle 160 to reach each candidate station in a set of candidate stations, and then the first expected time for autonomous vehicle 160 to reach each candidate station in a set of candidate stations can be determined.

[0113] In box 420, server 130 determines whether a set of candidate sites are allowed to dock at a first expected time based on time-sharing attribute 245, wherein time-sharing attribute 245 indicates docking constraints for the set of candidate sites at least during a time period.

[0114] In some embodiments, some of the candidate sites in a set of candidate sites may have a time-sharing attribute 245. For candidate sites with a time-sharing attribute 245, server 130 needs to consider whether autonomous vehicle 160 will be affected by docking constraints when arriving at the candidate site. For candidate sites that are not time-sharing sites, server 130 does not need to consider whether autonomous vehicle 160 will be affected by docking constraints.

[0115] In some embodiments, for candidate sites with time-sharing attribute 245, server 130 can determine whether a candidate site is allowed to dock at the first expected time by whether the first expected time of arrival at the candidate site falls within the time period during which the candidate site generates docking constraints. Specifically, if the first expected time of a candidate site falls within the time period during which the site generates docking constraints, server 130 can consider that the site is not allowed to dock at the first expected time. Conversely, if the first expected time of a candidate site does not fall within the time period during which the site generates docking constraints, server 130 considers that the site is allowed to dock at the first expected time.

[0116] In box 420, server 130 determines from a set of candidate sites at at least one target site that is allowed to dock at the first expected time.

[0117] In some embodiments, server 130 may determine multiple candidate sites that are allowed to dock at a first expected time from a set of candidate sites, and then determine at least one target site from these candidate sites. The multiple candidate sites allowed to dock at the first expected time may be candidate sites whose time periods do not fall within the corresponding docking constraints, or candidate sites that do not have the time-sharing attribute 245.

[0118] In some embodiments, when all candidate sites are time-sharing sites, and the first expected time of each candidate site falls within the corresponding docking constraint period, server 130 can present at least one recommended site on the target interface to facilitate transferring to the target site. The recommended site can be a site where the autonomous vehicle 160 is allowed to dock.

[0119] Through the above process, server 130 enables autonomous vehicle 160 to effectively avoid locations that are unfavorable for autonomous vehicle 160 to park.

[0120] Once the server 130 determines at least one target site, it can allocate service vehicles for the travel service based on the pick-up and drop-off sites included in the at least one target site.

[0121] In some embodiments, the process of server 130 allocating service vehicles can be as follows: First, server 130 determines a second expected time when candidate service vehicles will arrive at the boarding station. Then, server 130 determines the target autonomous vehicle based on a comparison between the second expected time and the stopping constraints of the boarding station.

[0122] In some embodiments, the second expected time can be determined based on the current location of the candidate service vehicle. Specifically, taking a candidate service vehicle as an example, the process by which server 130 determines the second expected time of its arrival at the boarding station can be as follows: Server 130 first determines the current location of the candidate service vehicle. Then, server 130 determines the route from the candidate service vehicle to the boarding station. Server 130 then determines the time taken for the candidate service vehicle to reach the boarding station based on the route from the candidate service vehicle to the boarding station and the travel speed of the candidate service vehicle. Finally, server 130 determines the second expected time based on the current time and the time taken for the candidate service vehicle to reach the boarding station. Based on the above process, the second expected time of arrival at the boarding station for each candidate service vehicle can be determined.

[0123] In some embodiments, some boarding stations also have a time-sharing attribute 245. For boarding stations with time-sharing attribute 245, server 130 can determine whether a candidate service vehicle can be allowed to stop at the second expected time based on the second expected time and the stop constraints of the boarding station. Specifically, when the second expected time of a candidate service vehicle falls within the time period during which the boarding station generates stop constraints, server 130 determines that the candidate service vehicle cannot be allowed to stop at the boarding station during the second expected time. Conversely, when the second expected time of a candidate service vehicle does not fall within the time period during which the boarding station generates stop constraints, server 130 determines that the candidate service vehicle can be allowed to stop at the boarding station during the second expected time. In this way, server 130 can determine all candidate service vehicles that are allowed to stop at the boarding station during the second expected time. Based on this, server 130 can further select one candidate service vehicle from these candidate service vehicles as the target autonomous vehicle to be responsible for this trip service.

[0124] In some embodiments, if none of the candidate service vehicles are allowed to stop at the pick-up station at the second expected time, the server 130 may remind the user 140 to re-enter the desired pick-up location, or may trigger the presentation of at least one recommended station on the target interface to facilitate the transfer to the target station.

[0125] Through the above process, server 130 enables autonomous vehicle 160 to effectively avoid locations that are unfavorable for autonomous vehicle 160 to park.

[0126] In some embodiments, for travel orders with assigned service vehicles, during the pick-up and drop-off process of the target autonomous vehicle, repeatedly estimating the arrival time at the pick-up or drop-off point based on real-time traffic conditions can enable the target autonomous vehicle to further avoid locations unfavorable to the autonomous vehicle 160's parking. As an example, the server 130 can achieve the above function by configuring the target autonomous vehicle.

[0127] In some embodiments, after a target autonomous vehicle is assigned a ride service, the target autonomous vehicle can be configured to: determine a third expected time when the target autonomous vehicle will arrive at the boarding station, and trigger a reallocation of the service vehicle in response to the boarding station prohibiting stopping at the third expected time.

[0128] In some embodiments, server 130 may first determine the current location of the target autonomous vehicle, and then determine the route between the target autonomous vehicle and the boarding station. Server 130 then determines a third expected time for the target autonomous vehicle to arrive at the boarding station based on the route between the target autonomous vehicle and the boarding station and the speed of the target autonomous vehicle. As an example, the third expected time is the current time plus the time taken for the target autonomous vehicle to arrive at the boarding station.

[0129] In some embodiments, when the third expected time falls within the period during which the boarding station generates a stopping constraint, it indicates that the target autonomous vehicle cannot stop at the boarding station at the third expected time. In this case, the server 130 can trigger a reallocation of service vehicles. Conversely, when the third expected time does not fall within the period during which the boarding station generates a stopping constraint, it indicates that the target autonomous vehicle can stop at the boarding station at the third expected time.

[0130] Through the above process, server 130 enables the target autonomous vehicle to effectively avoid locations that are unfavorable for autonomous vehicle 160 to park.

[0131] In some embodiments, when a target autonomous vehicle arrives at a pick-up point, the target autonomous vehicle can be configured to determine a fourth expected arrival time at the drop-off point based on a first limited stop duration at the pick-up point and the expected travel time from the pick-up point to the drop-off point. In response to the drop-off point prohibiting stopping at the fourth expected time, a reassignment of a service vehicle is triggered.

[0132] In some embodiments, the fourth expected time can be the current time plus the first limited stop duration and the expected travel time from the boarding station to the alighting station. If the alighting station has a time-sharing attribute 245, and the fourth expected time falls within the period when the alighting station incurs a stop constraint, it means the target autonomous vehicle cannot stop at the alighting station at the fourth expected time. In this case, server 130 can trigger a reallocation of service vehicles. Conversely, if the fourth expected time does not fall within the period when the alighting station incurs a stop constraint, it means the target autonomous vehicle can stop at the alighting station at the fourth expected time.

[0133] Through the above process, server 130 enables the target autonomous vehicle to effectively avoid locations that are unfavorable for autonomous vehicle 160 to park.

[0134] In some embodiments, as the target autonomous vehicle travels to the drop-off station, the target autonomous vehicle can be configured to: periodically determine the fifth expected time when the target autonomous vehicle arrives at the drop-off station, and trigger the presentation of at least one recommended station in the target interface in response to the drop-off station prohibiting stopping at the fifth expected time.

[0135] In some embodiments, when determining the fifth expected time, the server 130 may first determine the current location of the target autonomous vehicle. Then, the server 130 determines the route between the current location of the target autonomous vehicle and the drop-off point. The server 130 then determines the time taken for the target autonomous vehicle to reach the drop-off point based on the route between the current location and the drop-off point and the speed of the target autonomous vehicle. Finally, the server 130 determines the fifth expected time based on the current time and the time taken for the target autonomous vehicle to reach the drop-off point.

[0136] In some embodiments, if the fifth expected time falls within the period when a stop constraint is generated at the drop-off station, it indicates that the target autonomous vehicle cannot stop at the drop-off station at the fifth expected time. In this case, the server 130 may trigger the display of at least one recommended station on the target interface to facilitate the transfer of the target station. Conversely, if the fifth expected time does not fall within the period when a stop constraint is generated at the drop-off station, it indicates that the target autonomous vehicle can stop at the drop-off station at the fifth expected time.

[0137] In some embodiments, the recommended site may be a site where the target autonomous vehicle is allowed to dock.

[0138] In some embodiments, the condition for triggering server 130 to determine the fifth expected moment may be triggered when the target autonomous vehicle travels a preset distance, or when the target autonomous vehicle travels a preset time.

[0139] In some embodiments, when user 140 sends a request to the travel platform to modify the drop-off point, the travel platform can be configured to: determine the fifth expected time when autonomous vehicle 160 arrives at the modified drop-off point, and reject the request in response to the modified drop-off point prohibiting stopping at the fifth expected time.

[0140] As an example, the travel platform can be deployed on server 130.

[0141] In some embodiments, server 130 may first determine the current location of autonomous vehicle 160. Then, server 130 determines the route between the current location of autonomous vehicle 160 and the modified drop-off point. Server 130 then determines the time it will take for autonomous vehicle 160 to reach the modified drop-off point based on the route between the current location of autonomous vehicle 160 and the modified drop-off point, and the travel speed of autonomous vehicle 160. Finally, server 130 can determine the fifth expected time of arrival at the modified drop-off point based on the current time and the time it will take for autonomous vehicle 160 to reach the modified drop-off point.

[0142] In some embodiments, when the modified drop-off station has a time-sharing attribute 245, if the fifth expected time falls within the time period during which the modified drop-off station generates a stopping constraint, it means that the autonomous vehicle 160 cannot stop at the modified drop-off station at the fifth expected time. In this case, the server 130 can reject the request. Conversely, if the fifth expected time does not fall within the time period during which the modified drop-off station generates a stopping constraint, it means that the autonomous vehicle 160 can stop at the drop-off station at the fifth expected time. In this case, the server 130 can accept the request.

[0143] It should be understood that the autonomous vehicle 160 mentioned in the above process is the target autonomous vehicle allocated by server 130 for travel services.

[0144] Through the above process, server 130 enables the target autonomous vehicle to effectively avoid locations that are unfavorable for autonomous vehicle 160 to park.

[0145] Additionally, when the target autonomous vehicle arrives at the drop-off point, the target autonomous vehicle can be configured to: determine the remaining duration of the initial stop time at the drop-off point, and determine the stop time limit information of the target autonomous vehicle at the drop-off point based on the comparison between the second stop time limit at the drop-off point and the remaining duration.

[0146] In some embodiments, the second parking time limit is similar to the first parking time limit, and the second parking time limit is the maximum duration for which the autonomous vehicle 160 can stay at the drop-off point. The road conditions at each drop-off point are different, which causes the autonomous vehicle 160 to stay at each drop-off point for a different amount of time. The second parking time limit can be obtained based on the location of the drop-off point.

[0147] For drop-off stations with a time-sharing attribute (245), especially when the arrival time of the target autonomous vehicle at the drop-off station is close to the time period during which the drop-off station incurs a stop constraint, the time period during which the stop constraint is incurred can affect the dwell time of the target autonomous vehicle at the drop-off station. Therefore, server 130 needs to determine the stop time limit information for the target autonomous vehicle at the drop-off station. The stop time limit information is the dwell time of the target autonomous vehicle at the drop-off station.

[0148] In some embodiments, the remaining time until the start of the stop restriction at the alighting station can be the difference between the start of the stop restriction at the alighting station and the current time. The start of the stop restriction at the alighting station is the time when the stop constraint is generated at the alighting station.

[0149] In some embodiments, when the second restricted stop duration is greater than the remaining duration, the dwell time of the target autonomous vehicle at the drop-off point can be the remaining duration. When the second restricted stop duration is less than or equal to the remaining duration, the dwell time of the target autonomous vehicle at the drop-off point can be the second restricted stop duration. As an example, when the remaining duration is less than 1 minute, the dwell time of the target autonomous vehicle at the drop-off point can be 1 minute.

[0150] In some embodiments, during the process of estimating the first, second, third, fourth, and fifth expected times, the impact of areas with time-sharing attributes on the autonomous vehicle 160 may also be considered. Areas with time-sharing attributes are those that impose traffic constraints on the autonomous vehicle 160 at least during at least one time period. As an example, areas with time-sharing attributes may be determined based on real-time traffic conditions, road congestion, and road construction.

[0151] In some embodiments, when determining the route to the boarding or alighting point based on the location of the autonomous vehicle 160, or when determining the route to the alighting point based on the boarding point, the server 130 may choose to avoid areas with time-sharing attributes. Through the above process, the server 130 enables the autonomous vehicle 160 to effectively avoid locations or areas that are unfavorable for the autonomous vehicle 160 to stop.

[0152] Example devices and equipment

[0153] Figure 5 A schematic structural block diagram of an apparatus 500 for travel services according to certain embodiments of the present disclosure is shown. The apparatus 500 may be implemented as or included in a terminal device 110. The various modules / components in the apparatus 500 may be implemented by hardware, software, firmware, or any combination thereof.

[0154] like Figure 5As shown, the device 500 includes a first display module 510 configured to present a target interface associated with a travel service provided by an autonomous vehicle; and a second display module 520 configured to present at least one target station in the target interface, the at least one target station including a pick-up station and / or a drop-off station, wherein the at least one target station is determined based on the following process: determining a first expected time when the autonomous vehicle will arrive at a set of candidate stations; determining whether the set of candidate stations are allowed to stop at the first expected time based on time-sharing attributes of the set of candidate stations, the time-sharing attributes indicating stop constraints of the set of candidate stations in at least one time period; and determining at least one target station from the set of candidate stations that is allowed to stop at the first expected time.

[0155] In some embodiments, determining the first expected time when an autonomous vehicle arrives at a set of candidate stations includes: determining a first limited stop duration at the pick-up station before allocating a service vehicle for the ride service; and determining the first expected time of arrival at the set of candidate stations based on the first limited stop duration and the expected travel time from the pick-up station to the set of candidate stations.

[0156] In some embodiments, the target autonomous vehicle for the mobility service is determined based on the following process: determining a second expected time for candidate service vehicles to arrive at the pick-up station during the allocation of service vehicles for the mobility service; and determining the target autonomous vehicle based on a comparison of the second expected time with the stop constraints of the pick-up station.

[0157] In some embodiments, the target autonomous vehicle is further configured to: determine a third expected time when the target autonomous vehicle arrives at the boarding station in response to the target autonomous vehicle being assigned a ride service; and trigger a reallocation of the service vehicle in response to the boarding station prohibiting stopping at the third expected time.

[0158] In some embodiments, the target autonomous vehicle is further configured to: in response to the target autonomous vehicle arriving at the boarding station, determine a fourth expected time of arrival at the alighting station based on a first limited stop duration at the boarding station and the expected travel time from the boarding station to the alighting station; and in response to the alighting station prohibiting stopping at the fourth expected time, trigger a reallocation of service vehicles.

[0159] In some embodiments, the target autonomous vehicle is further configured to: periodically determine a fifth expected time when the target autonomous vehicle arrives at the drop-off point while traveling to the drop-off point; and trigger the presentation of at least one recommended station in the target interface in response to the drop-off point prohibiting stopping at the fifth expected time.

[0160] In some embodiments, the target autonomous vehicle is further configured to: determine the remaining duration of the initial limited stop time at the drop-off point in response to the target autonomous vehicle arriving at the drop-off point; and determine the stop time limit information of the target autonomous vehicle at the drop-off point based on a comparison between the second limited stop time at the drop-off point and the remaining duration.

[0161] In some embodiments, during a trip, a request to modify the drop-off point is sent to the trip platform, wherein the trip platform is configured to: determine a fifth expected time for the autonomous vehicle to arrive at the modified drop-off point; and reject the request in response to the modified drop-off point prohibiting stopping at the fifth expected time.

[0162] Figure 6 A block diagram of an electronic device 600 in which one or more embodiments of the present disclosure may be implemented is shown. It should be understood that... Figure 6 The electronic device 600 shown is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. Figure 6 The electronic device 600 shown can be used to achieve Figure 1 Terminal equipment 110.

[0163] like Figure 6 As shown, electronic device 600 is in the form of a general-purpose computing device. Components of electronic device 600 may include, but are not limited to, one or more processors or processing units 610, memory 620, storage device 630, one or more communication units 640, one or more input devices 650, and one or more output devices 660. Processing unit 610 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 620. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 600.

[0164] Electronic device 600 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to electronic device 600, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 620 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 630 can be a removable or non-removable medium and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data (e.g., training data for training) and can be accessed within electronic device 600.

[0165] Electronic device 600 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 6 As shown, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks can be provided. In these cases, each drive can be connected to a bus (not shown) via one or more data media interfaces. Memory 620 may include computer program product 625 having one or more program modules configured to perform various methods or actions of various embodiments of this disclosure.

[0166] The communication unit 640 enables communication with other computing devices via a communication medium. Additionally, the functionality of the components of the electronic device 600 can be implemented as a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the electronic device 600 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0167] Input device 650 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 660 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 600 can also communicate as needed with one or more external devices (not shown) via communication unit 640. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user 140 to interact with electronic device 600, or with any device that enables electronic device 600 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

[0168] According to an exemplary implementation of this disclosure, a computer-readable storage medium is provided that stores computer-executable instructions thereon, wherein the computer-executable instructions are executed by a processor to implement the methods described above. According to an exemplary implementation of this disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the methods described above.

[0169] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0170] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0171] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0172] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0173] Various implementations of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for travel, comprising: Presents the target interface associated with the mobility services provided by autonomous vehicles; as well as The target interface displays at least one target station, which includes a boarding station and / or an alighting station. The at least one target site is determined based on the following process: Determine the first expected time when the autonomous vehicle arrives at a set of candidate stations; Based on the time-sharing attributes of the group of candidate stations, it is determined whether the group of candidate stations is allowed to dock at the first expected time, wherein the time-sharing attributes indicate the docking constraints of the group of candidate stations in at least one time period; as well as From the set of candidate sites, determine at least one target site that is permitted to dock at the first expected time.

2. The method of claim 1, wherein determining the first expected time for the autonomous vehicle to arrive at a set of candidate stations comprises: Before allocating service vehicles for the travel service, determine the first limited stop duration at the boarding station; as well as Based on the first restricted stop duration and the expected travel time from the boarding station to the group of candidate stations, the first expected arrival time at the group of candidate stations is determined.

3. The method of claim 1, wherein the target autonomous vehicle for the mobility service is determined based on the following process: During the allocation of service vehicles for the travel service, a second expected time for the candidate service vehicles to arrive at the boarding station is determined; and The target autonomous vehicle is determined by comparing the second expected time with the stopping constraints of the boarding station.

4. The method of claim 3, wherein the target autonomous vehicle is further configured to: In response to the target autonomous vehicle being assigned the travel service, a third expected time for the target autonomous vehicle to arrive at the boarding station is determined; and In response to the boarding station prohibiting stopping at the third anticipated time, a reassignment of service vehicles is triggered.

5. The method of claim 3, wherein the target autonomous vehicle is further configured to: In response to the arrival of the target autonomous vehicle at the boarding station, a fourth expected arrival time at the disembarkation station is determined based on the first limited stop duration at the boarding station and the expected travel time from the boarding station to the disembarkation station; and In response to the prohibition of stopping at the drop-off station at the fourth anticipated time, a reassignment of service vehicles is triggered.

6. The method of claim 3, wherein the target autonomous vehicle is further configured to: During the journey of the target autonomous vehicle to the drop-off point, the fifth expected time of the target autonomous vehicle's arrival at the drop-off point is periodically determined; and In response to the disembarkation station prohibiting stopping at the fifth expected time, at least one recommended station is displayed on the target interface.

7. The method of claim 3, wherein the target autonomous vehicle is further configured to: In response to the arrival of the target autonomous vehicle at the drop-off point, determine the remaining time until the initial stop time at the drop-off point; and Based on the comparison between the second limited stopping time at the drop-off station and the remaining time, the stopping time limit information of the target autonomous vehicle at the drop-off station is determined.

8. The method according to claim 1, further comprising: During the travel service, a request to modify the drop-off point is sent to the travel platform. The travel platform is configured to: determine the fifth expected time when the autonomous vehicle will arrive at the modified drop-off point; and, in response to the modified drop-off point prohibiting stopping at the fifth expected time, reject the request.

9. A device for travel, comprising: The first display module is configured to present a target interface associated with the mobility services provided by autonomous vehicles; as well as The second display module is configured to present at least one target station in the target interface, the at least one target station including a pick-up station and / or a drop-off station, wherein the at least one target station is determined based on the following process: determining a first expected time when the autonomous vehicle will arrive at a set of candidate stations; and determining whether the set of candidate stations is allowed to stop at the first expected time based on the time-sharing attributes of the set of candidate stations, the time-sharing attributes indicating the stopping constraints of the set of candidate stations in at least one time period. And determine from the set of candidate sites at at least one target site that is permitted to dock at the first expected time.

10. An electronic device, comprising: At least one processing unit; as well as At least one memory, coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, which, when executed by the at least one processing unit, cause the electronic device to perform the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program stored thereon, the computer program being executable by a processor to implement the method according to any one of claims 1 to 8.

12. A computer program product comprising computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the method according to any one of claims 1 to 8.

Images