 Overview of the GCM Service architecture. | |
| Developer(s) | |
|---|---|
| Target platform(s) | Android,Chrome |
| Programming language(s) | Java |
| Status | Defunct |
| License | Proprietary |
Google Cloud Messaging (GCM) was a mobilenotification service developed byGoogle that enables third-party application developers to send notification data or information from developer-run servers to applications that target theGoogle Android Operating System, as well as applications or extensions developed for theGoogle Chrome web browser. It was available to developers free of charge. The GCM Service was first announced in June 2012[1] as a successor to Google's now-defunctAndroid Cloud to Device Messaging (C2DM) service, citing improvements to authentication and delivery, new API endpoints and messaging parameters, and the removal of limitations on API send-rates and message sizes.[2] It has been superseded by Google'sFirebase Cloud Messaging (FCM) on May 29, 2019.[3]
GCM first launched as Google'sAndroid Cloud to Device Messaging (C2DM) service, first featured inAndroid 2.2 byGoogle.[4][5][6]
The transition toGoogle Cloud Messaging was first announced when the Android service was unveiled on June 27, 2012, atGoogle I/O.[7] Shortly after announcing the Google Cloud Messaging service, Google published documentation to guide application developers with migrating from the C2DM and onto the new service.[8] Migrating to the service requiredSDK and code changes, as well as a release of an application update to the publish repository (such asGoogle Play) for downloading and updating.
The Chrome service was announced before Google I/O 2013 in a blog post titled 'Building efficient apps and extensions with push messaging.'[9]
AtI/O 2015, Google announced a new SDK andiOS support.
Google Cloud Messaging functions using serverAPIs andSDKs, both maintained by Google. The GCM has the ability to sendpush notifications, deep-linking commands, and application data. Larger messages can be sent with up to 4 KB ofpayload data.[10]
Upon allowing the application permission to receive and display notifications, the client application sends a registration API request to the Google Cloud Messaging interface to begin the registration process. The GCM Service receives and acknowledges the request and responds by giving the device aGCM Registration ID, a unique identifier that the developer later uses to send a notification to the individual device. The identifier is stored onto the device, and is typically sent to the developer's application server to be stored. The GCM Registration ID is a randomly-generated identifier that does not contain any personal or device information that could allow a developer to discover the personal identity of the user.[11] When the developer wishes to send a notification event to a device, the process begins with an API POST request being sent to the GCM Authentication Service. The POST request includes the GCM Registration ID, priority, optional values and links, and the information that is to be displayed on the device upon its arrival. Upon successful verification of the GCM Registration ID and other credentials, an authentication token is returned. Both identifiers are then sent to the GCM Service to be enqueued and delivered to the device.
