更新停靠站狀態

本文假設您已詳讀以下文章：

  • [建立出貨工作][1]
  • [排定工作][3]簡介，詳細說明工作、停靠點和車輛之間的關係。

如「Fleet Engine 基礎知識」的「[排定工作][3]」一節所述，您可以建立工作並將其與車輛停靠點建立關聯，藉此模擬真實世界中工作與車輛預計停靠位置之間的關係，方便司機完成工作。

接著，只要將最新狀態傳送至 Fleet Engine，系統就能在工作的整個生命週期中，完善執行路線規劃和狀態更新，方便您妥善管理工作進度。很重要的一點是，在車輛接近、抵達和離開停靠點時更新停靠點。如此一來，無論是車隊營運人員或客戶，都能取得工作進度的相關報表和分析資料。這些狀態項目如下：

  • En route：VehicleStop 的 STATE 列舉值為 ENROUTE，代表停靠點是車輛行程表中的下一站。就工作而言，這表示與停靠點相關聯的工作，將是清單中下一個要完成的工作。
  • Arrived：VehicleStop 的 STATE 列舉值為 ARRIVED，代表車輛已抵達停靠點。就工作而言，這表示目前正在處理與停靠點相關聯的工作。
  • Completed：從車輛的停靠點清單中移除停靠點，即可將停靠點標示為已完成。這麼做時，Fleet Engine 會自動將所有相關聯的工作標示為「CLOSED」。如要進一步瞭解如何結束工作，請參閱 [完成工作][4]。

本文說明如何使用伺服器端方法更新停靠點狀態。如果允許司機使用信任的裝置管理工作，您也可以透過司機應用程式執行這項操作。兩種方法請擇一使用，以維持單一資料來源，並避免發生競爭狀況。

車輛正在前往停靠點

當車輛開始導航前往下一個停靠點時，系統應通知 Fleet Engine。這有助於提升預計抵達時間和路線計算的準確度。

停靠點狀態更新的必填欄位

Fleet Engine 會忽略實體中所有其他通知欄位。

欄位值
remainingVehicleJourneySegments 剩餘車輛停靠點清單，狀態標示為 State.NEW。

Enroute to stop example

下列範例說明如何使用 [Java gRPC 程式庫][5] 或對 UpdateDeliveryVehicle 發出 HTTP REST 呼叫，通知 Fleet Engine 車輛正前往下一個停靠點。所有其他停靠點都會標示為新停靠點。

gRPC

 static final String PROJECT_ID = "my-delivery-co-gcp-project";
 static final String VEHICLE_ID = "vehicle-8241890";

 DeliveryServiceBlockingStub deliveryService =
   DeliveryServiceGrpc.newBlockingStub(channel);

 // Vehicle settings
 DeliveryVehicle deliveryVehicle = DeliveryVehicle.newBuilder()
     // Next stop marked as ENROUTE
     .addRemainingVehicleJourneySegments(VehicleJourneySegment.newBuilder()  // 1st stop
        .setStop(VehicleStop.newBuilder()
            .setPlannedLocation(LocationInfo.newBuilder()
                .setPoint(LatLng.newBuilder()
                    .setLatitude(37.7749)
                    .setLongitude(122.4194)))
            .addTasks(TaskInfo.newBuilder().setTaskId(TASK1_ID))
            .setState(VehicleStop.State.ENROUTE)))
     // All other stops marked as NEW
     .addRemainingVehicleJourneySegments(VehicleJourneySegment.newBuilder()  // 2nd stop
        .setStop(VehicleStop.newBuilder()
            .setPlannedLocation(LocationInfo.newBuilder()
                .setPoint(LatLng.newBuilder()
                    .setLatitude(37.3382)
                    .setLongitude(121.8863)))
            .addTasks(TaskInfo.newBuilder().setTaskId(TASK2_ID))
            .setState(VehicleStop.State.NEW)))
     .build();

 // DeliveryVehicle request
 UpdateDeliveryVehicleRequest updateDeliveryVehicleRequest =
   UpdateDeliveryVehicleRequest.newBuilder()  // No need for the header
       .setName(vehicleName)
       .setDeliveryVehicle(deliveryVehicle)
       .setUpdateMask(FieldMask.newBuilder().addPaths("remaining_vehicle_journey_segments"))
       .build();

 try {
   DeliveryVehicle updatedDeliveryVehicle =
       deliveryService.updateDeliveryVehicle(updateDeliveryVehicleRequest);
 } catch (StatusRuntimeException e) {
   Status s = e.getStatus();
   switch (s.getCode()) {
      case NOT_FOUND:
        break;
      case PERMISSION_DENIED:
        break;
   }
   return;
 }

REST

PATCH https://fleetengine.googleapis.com/v1/providers/<project_id>/deliveryVehicles/<id>?updateMask=remainingVehicleJourneySegments`
  • <id> 是工作項目的專屬 ID。
  • 要求標頭必須包含「Authorization」欄位，值為「Bearer <token>」，其中「<token>」是由伺服器根據 [服務帳戶角色][6] 和 [JSON Web 權杖][6]中所述的準則發布。
  • 要求主體必須包含 DeliveryVehicle 實體：

curl 指令範例：

 # Set JWT, PROJECT_ID, VEHICLE_ID, TASK1_ID, and TASK2_ID in the local
 # environment
 curl -X PATCH "https://fleetengine.googleapis.com/v1/providers/${PROJECT_ID}/deliveryVehicles/${VEHICLE_ID}?updateMask=remainingVehicleJourneySegments" \
   -H "Content-type: application/json" \
   -H "Authorization: Bearer ${JWT}" \
   --data-binary @- << EOM
 {
   "remainingVehicleJourneySegments": [
     {
       "stop": {
         "state": "ENROUTE",
         "plannedLocation": {
           "point": {
             "latitude": 37.7749,
             "longitude": -122.084061
           }
         },
         "tasks": [
           {
             "taskId": "${TASK1_ID}"
           }
         ]
       }
     },
     {
       "stop": {
         "state": "NEW",
         "plannedLocation": {
           "point": {
             "latitude": 37.3382,
             "longitude": 121.8863
           }
         },
         "tasks": [
           {
             "taskId": "${TASK2_ID}"
           }
         ]
       }
     }
   ]
 }
 EOM

placeidtrips1：/maps/documentation/mobility/fleet-engine/reference/tasks/rpc/maps.fleetengine.delivery.v1.html#locationinfo placeidtrips2：/maps/documentation/mobility/fleet-engine/reference/tasks/rest/v1/LocationInfo.html placeidtrips3：/maps/documentation/mobility/fleet-engine/reference/tasks/rpc/maps.fleetengine.delivery.v1.html#maps.fleetengine.delivery.v1.LocationInfo.FIELDS.string.maps.fleetengine.delivery.v1.LocationInfo.place placeidtrips4：/maps/documentation/mobility/fleet-engine/reference/tasks/rest/v1/LocationInfo.html#FIELDS.place

車輛抵達停靠點

車輛抵達停靠點時，必須通知 Fleet Engine。

停靠點狀態更新的必填欄位

Fleet Engine 會忽略實體中所有其他通知欄位。

欄位值
remainingVehicleJourneySegments 剩餘車輛停靠點清單，狀態標示為 State.NEW。

抵達停靠點範例

下列範例說明如何使用 [Java gRPC 程式庫][5] 或對 UpdateDeliveryVehicle 發出 HTTP REST 呼叫，通知 Fleet Engine 車輛已抵達停靠點。其他所有停靠點都會標示為新停靠點。

gRPC

  static final String PROJECT_ID = "my-delivery-co-gcp-project";
  static final String VEHICLE_ID = "vehicle-8241890";

  DeliveryServiceBlockingStub deliveryService =
    DeliveryServiceGrpc.newBlockingStub(channel);

  // Vehicle settings
  String vehicleName = "providers/" + PROJECT_ID + "/deliveryVehicles/" + VEHICLE_ID;
  DeliveryVehicle deliveryVehicle = DeliveryVehicle.newBuilder()
      // Marking the arrival at stop.
      .addRemainingVehicleJourneySegments(VehicleJourneySegment.newBuilder()
         .setStop(VehicleStop.newBuilder()
             .setPlannedLocation(LocationInfo.newBuilder()
                 .setPoint(LatLng.newBuilder()
                     .setLatitude(37.7749)
                     .setLongitude(122.4194)))
             .addTasks(TaskInfo.newBuilder().setTaskId(TASK1_ID))
             .setState(VehicleStop.State.ARRIVED)))
      // All other remaining stops marked as NEW.
      .addRemainingVehicleJourneySegments(VehicleJourneySegment.newBuilder()  // 2nd stop
         .setStop(VehicleStop.newBuilder()
             .setPlannedLocation(LocationInfo.newBuilder()
                 .setPoint(LatLng.newBuilder()
                     .setLatitude(37.3382)
                     .setLongitude(121.8863)))
             .addTasks(TaskInfo.newBuilder().setTaskId(TASK2_ID))
             .setState(VehicleStop.State.NEW))) // Remaining stops must be NEW.
      .build();

  // DeliveryVehicle request
  UpdateDeliveryVehicleRequest updateDeliveryVehicleRequest =
    UpdateDeliveryVehicleRequest.newBuilder()  // No need for the header
        .setName(vehicleName)
        .setDeliveryVehicle(deliveryVehicle)
        .setUpdateMask(FieldMask.newBuilder()
            .addPaths("remaining_vehicle_journey_segments"))
        .build();

  try {
    DeliveryVehicle updatedDeliveryVehicle =
        deliveryService.updateDeliveryVehicle(updateDeliveryVehicleRequest);
  } catch (StatusRuntimeException e) {
    Status s = e.getStatus();
    switch (s.getCode()) {
       case NOT_FOUND:
         break;
       case PERMISSION_DENIED:
         break;
    }
    return;
  }

REST

`PATCH https://fleetengine.googleapis.com/v1/providers/<project_id>/deliveryVehicles/<id>?updateMask=remainingVehicleJourneySegments`
  • <id> 是工作項目的專屬 ID。
  • 要求標頭必須包含「Authorization」欄位，值為「Bearer <token>」，其中「<token>」是由伺服器根據 [服務帳戶角色][6] 和 [JSON Web 權杖][6]中所述的準則發布。
  • 要求主體必須包含 DeliveryVehicle 實體：

curl 指令範例：

  # Set JWT, PROJECT_ID, VEHICLE_ID, TASK1_ID, and TASK2_ID in the local
  # environment
  curl -X PATCH "https://fleetengine.googleapis.com/v1/providers/${PROJECT_ID}/deliveryVehicles/${VEHICLE_ID}?updateMask=remainingVehicleJourneySegments" \
    -H "Content-type: application/json" \
    -H "Authorization: Bearer ${JWT}" \
    --data-binary @- << EOM
  {
    "remainingVehicleJourneySegments": [
      {
        "stop": {
          "state": "ARRIVED",
          "plannedLocation": {
            "point": {
              "latitude": 37.7749,
              "longitude": -122.084061
            }
          },
          "tasks": [
            {
              "taskId": "${TASK1_ID}"
            }
          ]
        }
      },
      {
        "stop": {
          "state": "NEW",
          "plannedLocation": {
            "point": {
              "latitude": 37.3382,
              "longitude": 121.8863
            }
          },
          "tasks": [
            {
              "taskId": "${TASK2_ID}"
            }
          ]
        }
      }
    ]
  }
  EOM

車輛完成停靠

車輛完成停靠時，必須通知 Fleet Engine。系統會將停靠點相關聯的所有工作都設為「CLOSED」狀態。

停靠點狀態更新的必填欄位

Fleet Engine 會忽略實體中所有其他通知欄位。

欄位值
remainingVehicleJourneySegments 剩餘車輛停靠點清單，狀態標示為 State.NEW。 清單上的第一個停靠點必須標示為 State.ENROUTE 狀態。

完成停靠範例

下列範例說明如何使用 [Java gRPC 程式庫][5] 或對 UpdateDeliveryVehicle 發出 HTTP REST 呼叫，通知 Fleet Engine 車輛已抵達停靠點。其他所有停靠點都會標示為新停靠點。

gRPC

  static final String PROJECT_ID = "my-delivery-co-gcp-project";
  static final String VEHICLE_ID = "vehicle-8241890";

  DeliveryServiceBlockingStub deliveryService =
    DeliveryServiceGrpc.newBlockingStub(channel);

  // Vehicle settings
  String vehicleName = "providers/" + PROJECT_ID + "/deliveryVehicles/" + VEHICLE_ID;
  DeliveryVehicle deliveryVehicle = DeliveryVehicle.newBuilder()
      // This stop has been completed and is commented out to indicate it
      // should be removed from the list of vehicle journey segments.
      // .addRemainingVehicleJourneySegments(VehicleJourneySegment.newBuilder()
      //    .setStop(VehicleStop.newBuilder()
      //        .setPlannedLocation(LocationInfo.newBuilder()
      //            .setPoint(LatLng.newBuilder()
      //                .setLatitude(37.7749)
      //                .setLongitude(122.4194)))
      //        .addTasks(TaskInfo.newBuilder().setTaskId(TASK1_ID))
      //        .setState(VehicleStop.State.ARRIVED)))
      // All other remaining stops marked as NEW.
      // The next stop could be marked as ENROUTE if the vehicle has begun
      // its journey to the next stop.
      .addRemainingVehicleJourneySegments(VehicleJourneySegment.newBuilder()  // Next stop
         .setStop(VehicleStop.newBuilder()
             .setPlannedLocation(LocationInfo.newBuilder()
                 .setPoint(LatLng.newBuilder()
                     .setLatitude(37.3382)
                     .setLongitude(121.8863)))
             .addTasks(TaskInfo.newBuilder().setTaskId(TASK2_ID))
             .setState(VehicleStop.State.NEW)))
      .build();

  // DeliveryVehicle request
  UpdateDeliveryVehicleRequest updateDeliveryVehicleRequest =
    UpdateDeliveryVehicleRequest.newBuilder()  // no need for the header
        .setName(vehicleName)
        .setDeliveryVehicle(deliveryVehicle)
        .setUpdateMask(FieldMask.newBuilder()
            .addPaths("remaining_vehicle_journey_segments"))
        .build();

  try {
    DeliveryVehicle updatedDeliveryVehicle =
        deliveryService.updateDeliveryVehicle(updateDeliveryVehicleRequest);
  } catch (StatusRuntimeException e) {
    Status s = e.getStatus();
    switch (s.getCode()) {
       case NOT_FOUND:
         break;
       case PERMISSION_DENIED:
         break;
    }
    return;
  }

REST

PATCH https://fleetengine.googleapis.com/v1/providers/<project_id>/deliveryVehicles/<id>?updateMask=remaining_vehicle_journey_segments`
  • <id> 是工作項目的專屬 ID。
  • 要求標頭必須包含「Authorization」欄位，值為「Bearer <token>」，其中「<token>」是由伺服器根據 [服務帳戶角色][6] 和 [JSON Web 權杖][6]中所述的準則發布。
  • 要求主體必須包含 DeliveryVehicle 實體：

curl 指令範例：

 # Set JWT, PROJECT_ID, VEHICLE_ID, TASK1_ID, and TASK2_ID in the local
 # environment
 curl -X PATCH "https://fleetengine.googleapis.com/v1/providers/${PROJECT_ID}/deliveryVehicles/${VEHICLE_ID}?updateMask=remainingVehicleJourneySegments" \
   -H "Content-type: application/json" \
   -H "Authorization: Bearer ${JWT}" \
   --data-binary @- << EOM
 {
   "remainingVehicleJourneySegments": [
     {
       "stop": {
         "state": "NEW",
         "plannedLocation": {
           "point": {
             "latitude": 37.3382,
             "longitude": 121.8863
           }
         },
         "tasks": [
           {
             "taskId": "${TASK2_ID}"
           }
         ]
       }
     }
   ]
 }
 EOM

placeidtrips1：/maps/documentation/mobility/fleet-engine/reference/tasks/rpc/maps.fleetengine.delivery.v1.html#locationinfo placeidtrips2：/maps/documentation/mobility/fleet-engine/reference/tasks/rest/v1/LocationInfo.html placeidtrips3：/maps/documentation/mobility/fleet-engine/reference/tasks/rpc/maps.fleetengine.delivery.v1.html#maps.fleetengine.delivery.v1.LocationInfo.FIELDS.string.maps.fleetengine.delivery.v1.LocationInfo.place placeidtrips4：/maps/documentation/mobility/fleet-engine/reference/tasks/rest/v1/LocationInfo.html#FIELDS.place

後續步驟

  • [完成工作][4]

[1]：/maps/documentation/mobility/fleet-engine/journeys/tasks/create-shipment-tasks [3]：/maps/documentation/mobility/fleet-engine/essentials/tasks-intro [4]：/maps/documentation/mobility/fleet-engine/journeys/tasks/finalize-tasks [5]：/maps/documentation/mobility/fleet-engine/essentials/client-libraries-tasks [6]：/maps/documentation/mobility/fleet-engine/essentials/set-up-fleet/service-accounts