This node integrates user-defined on-demand delivery apps with autonomous driving systems.
Following use-cases are realized by connecting with FMS (fleet management service) providing by TIER IV, inc.
- Switch operation mode between on-demand delivery and regular delivery.
- Call an ego vehicle to a designated stop.
- Send an ego vehicle to a designated stop.
- input
- from Web.Auto (DevOps Platform provided by TIER IV)
/webauto/vehicle_info
[std_msgs/msg/String]:
Gets unique ID of the ego vehicle managed by Web.Auto.
- from autoware_state_machine
/req_change_lock_flg
[go_interface_msgs/msg/ChangeLockFlg]:
Receives reservations for on-demand delivery.
- from on-demand delivery apps (user-defined)
GET API
:
Gets the current reservation status for on-demand delivery in the ego vehicle.
- from Web.Auto (DevOps Platform provided by TIER IV)
- output
- to autoware_state_machine
/api_vehicle_status
[go_interface_msgs/msg/VehicleStatus]:
The current reservation status for on-demand delivery in the ego vehicle.
- to on-demand delivery apps (user-defined)
PATCH API
:
Updates the reservation status for on-demand delivery in the ego vehicle.
- to autoware_state_machine
Name | Description |
---|---|
operation_mode | Select the following operation modes; product , server_test , local_test , not_use . The URLs corresponding to these modes are set in go_interface_params. This URL applies to the delivery_reservation_service_url parameter. |
access_token | Access token of on-demand delivery application. This value is passed directly to the access_token parameter. |
Name | Description |
---|---|
delivery_reservation_service_url | URL of on-demand delivery application. |
access_token | Access token of on-demand delivery application. |
The following features need to be provided by on-demand delivery apps.
- Search for available vehicles using the fleet management service.
- Providing a UI, the user can specify an arbitrary destination after identifying the vehicle.
- Reserve a delivery schedule for the fleet management service.
On-demand delivery apps must be implemented according to the following specifications.
See the README in go_interface_params.
The following contents are output as Headers.
The token authentication specifications follow the Django REST framework.
Headers sample
{
"Accept": "application/json",
"Content-Type": "application/json",
"Authorization": "Token 0123456789abcdefgh"
}