Send GCM id to DMServer

components/policy/proto/device_management_backend.proto

Index: components/policy/proto/device_management_backend.proto
diff --git a/components/policy/proto/device_management_backend.proto b/components/policy/proto/device_management_backend.proto
index d196a4c015718ed46fd8adb57e5709bd2ecc31b8..f3bfde7410682cab6052977fc47f130610e7a4ca 100644
--- a/components/policy/proto/device_management_backend.proto
+++ b/components/policy/proto/device_management_backend.proto
@@ -998,6 +998,16 @@ message DeviceAttributeUpdateResponse {
   optional ResultType result = 1;
 }
 
+// Sent by the client to server to update the mapping from GCM id to DM token
+// on the server side.
+message GcmIdMappingRequest {
+  optional string gcm_id = 1;
+}
+
+// Response for GcmIdMappingRequest, an empty message for now.
+message GcmIdMappingResponse {
+}
+
 // Request from the DMAgent on the device to the DMServer.  This is
 // container for all requests from device to server.  The overall HTTP
 // request MUST be in the following format:
@@ -1098,6 +1108,9 @@ message DeviceManagementRequest {
   // Update device attribute.
   optional DeviceAttributeUpdateRequest device_attribute_update_request
       = 15;
+
+  // Update the GCM id to DM token mapping.
+  optional GcmIdMappingRequest gcm_id_mapping_request = 16;
 }
 
 // Response from server to device.
@@ -1162,4 +1175,7 @@ message DeviceManagementResponse {
 
   // Response to update device attribute.
   optional DeviceAttributeUpdateResponse device_attribute_update_response = 16;
+
+  // Response to GCM id mapping request.
+  optional GcmIdMappingResponse gcm_id_mapping_response = 17;
 }