Fleet Engine은 이동을 찾는 데 사용할 수 있는 SearchTripsRequest 엔드포인트를 제공합니다. 이 문서에서는 이 기능을 사용할 수 있는 두 가지 시나리오를 설명합니다.
gRPC의 경우 SearchTripsRequest를, REST의 경우 trips.Search을 참고하세요.
차량의 활성 여정을 확인합니다.
특정 필드의 활성 여행을 찾으려면 SearchTripsRequest 메시지를 사용하여 vehicle_id을 고려 중인 차량으로 설정하고 active_trips_only을 true로 설정합니다.
시스템과 Fleet Engine 간 차량 재고 조정
경우에 따라 시스템과 차량에서 사용할 수 있는 것으로 알려진 차량과 일치하지 않는 결과가 SearchVehicles에 의해 반환될 수 있습니다. 이는 SearchVehicles에서 활성 여정이 있는 차량을 표시하지 않거나 결과 순위에서 아래로 푸시하기 때문입니다. 이러한 문제의 한 가지 원인은 차량이 이동을 완료했지만 이동 상태가 COMPLETE 또는 CANCELED로 제대로 설정되지 않은 경우입니다. SearchTrips를 사용하여 진행 중인 여정을 찾으면 차량을 평가하여 시스템의 TripStatus이 Fleet Engine의 TripStatus과 일치하는지 확인할 수 있습니다.
이 방식으로 SearchTrips를 사용하려면 SearchTripsRequest 메시지에서 다음을 설정하세요.
vehicle_id은 비워야 합니다.
active_trips_only은 true여야 합니다.
minimum_staleness는 대부분의 이동 시간보다 긴 시간이어야 합니다(예: 1시간).
이러한 요청의 결과에는 COMPLETE도 CANCELED도 아니며 1시간 넘게 업데이트되지 않은 경로가 포함됩니다. 그런 다음 이러한 여정을 검사하여 Fleet Engine의 상태가 올바르게 업데이트되었는지 확인할 수 있습니다.
[null,null,["최종 업데이트: 2025-08-31(UTC)"],[[["\u003cp\u003eFleet Engine's \u003ccode\u003eSearchTripsRequest\u003c/code\u003e helps find trips, useful for identifying active trips and reconciling vehicle availability.\u003c/p\u003e\n"],["\u003cp\u003eUse \u003ccode\u003eSearchTripsRequest\u003c/code\u003e with \u003ccode\u003evehicle_id\u003c/code\u003e and \u003ccode\u003eactive_trips_only\u003c/code\u003e to find a specific vehicle's active trips.\u003c/p\u003e\n"],["\u003cp\u003eDiscrepancies between your system and Fleet Engine's vehicle availability can be addressed by using \u003ccode\u003eSearchTripsRequest\u003c/code\u003e to identify open trips and ensure trip statuses are synchronized.\u003c/p\u003e\n"],["\u003cp\u003eTrips older than 7 days are automatically deleted in Fleet Engine.\u003c/p\u003e\n"]]],["The `SearchTripsRequest` endpoint in Fleet Engine allows finding trips, focusing on two scenarios. First, setting `vehicle_id` and `active_trips_only` to `true` identifies active trips for a specific vehicle. Second, to reconcile vehicle availability, `vehicle_id` is left empty, `active_trips_only` is `true`, and `minimum_staleness` is set to over an hour. This identifies open, outdated trips (neither `COMPLETE` nor `CANCELED`) for status reconciliation. Trips are only searchable for seven days.\n"],null,["Fleet Engine provides the `SearchTripsRequest` endpoint that you can use to find\ntrips. This document describes two scenarios where you might use this feature.\n\nSee `SearchTripsRequest` for [gRPC](/maps/documentation/mobility/fleet-engine/reference/trips/rpc/maps.fleetengine.v1#searchtripsrequest) or `trips.Search` for [REST](/maps/documentation/mobility/fleet-engine/reference/trips/rest/v1/providers.trips/search).\n| **Note:** Trips remain active in Fleet Engine for 7 days, after which they are deleted, so `SearchTrips` only shows trips that have been active within the past 7 days.\n\nDetermine active trips for a vehicle\n\nTo do find the active trips for a specific fields, use the `SearchTripsRequest`\nmessage to set the `vehicle_id` to the vehicle under consideration and set\n`active_trips_only` to `true`.\n\nReconcile vehicle availability between your system and Fleet Engine\n\nIn some situations, you might see results returned by `SearchVehicles` that\ndon't correspond with the vehicles you know to be available in your system and\nyour fleet. This happens because `SearchVehicles` either doesn't show vehicles\nwith active trips, or pushes them down in the results ranking. One cause of this\nis when vehicles have completed trips, but the trip status not been properly set\nto either `COMPLETE` or `CANCELED`. By using `SearchTrips` to find open trips,\nyou can evaluate vehicles to ensure that `TripStatus` in your system matches\nthat of Fleet Engine.\n\nTo use `SearchTrips` in this way, set the following in the `SearchTripsRequest`\nmessage:\n\n- `vehicle_id` should be empty.\n- `active_trips_only` should be `true`.\n- `minimum_staleness` should be a time greater than most trip durations; for example, one hour.\n\nThe results of such a request include Trips that are neither `COMPLETE` nor\n`CANCELED`, and have not been updated in over an hour. You can then examine\nthese trips to ensure that their status in Fleet Engine is properly updated.\n\nWhat's next\n\n- [Delete Trip](/maps/documentation/mobility/fleet-engine/journeys/trips/delete-trip)"]]
