Google Cloud Messaging (commonly referred to as GCM ) is a mobile notification service developed by Google that allows third-party app developers to send data or notification information from the server that the developer runs into the app which targets the Google Android Operating System, as well as apps or extensions developed for Google Chrome's internet browser. It is available for developers for free. The GCM service was first announced in June 2012 as a replacement for Google's now obsolete Google Cloud to Device Messaging (C2DM) service, citing improvements to authentication and delivery, API endpoints and new messaging parameters, and deletion of restrictions on tariff API shipments and message size. It has been replaced by Google's Firebase Cloud Messaging (FCM).
Video Google Cloud Messaging
Development
GCM was first launched as Google Cloud to Device Messaging (C2DM) service, first shown on Android 2.2 by Google.
The transition to Google Cloud Messaging was first announced when the Android service was launched on June 27, 2012, at Google I/O. Shortly after announcing Google Cloud Messaging service, Google published documentation to guide app developers by migrating from C2DM and to the new service. Migrate to required SDK services and code changes, and release app updates to published repositories (such as Google Play) to download and update.
The Chrome service was announced before Google I/O 2013 in a blog post titled 'Building apps and extensions efficiently with push messages.'
On I/O 2015, Google announces new SDK and iOS support.
Maps Google Cloud Messaging
Technical details
The Google Cloud Messaging function uses both the API and the server SDK, both managed by Google. GCM has the ability to send push notifications, deep link commands, and app data. Larger messages can be sent with up to 4 KB of payload data.
After allowing app permission to receive and display notifications, the client application sends a registration API request to the Google Cloud Messaging interface to begin the sign up process. The GCM service accepts and acknowledges requests and responds by providing a GCM Registration ID device, a unique identifier that developers will later use to send notifications to individual devices. The identifier is saved to the device, and is usually sent to the developer application server for storage. GCM Registration ID is a randomly generated identifier that does not contain any personal information or devices that allow the developer to discover the user's personal identity. When a developer wants to send a notification event to the device, the process begins with a POST API request sent to GCM Authentication Service. POST requests include GCM Registration IDs, priorities, optional values ​​and links, and information to be displayed on the device upon arrival. Once the GCM Registration ID verification and other credentials are successful, the authentication tokens are returned. Both identifiers are then sent to the GCM Service to be entered and sent to the device.
See also
- Firebase Cloud Messaging (FCM)
- Android software development
- Apple Push Notification Service
- SQL Server Notice Service
- Windows Notification Service
References
External links
- The Official Google Cloud Messaging Website
- Official Firebase Cloud Messaging
- Official Android Developer Pages
- Official Chrome Developers page
- GCM Collegelib Seminar
- Implementation of Google Chrome Push Notifications by MindAsk
- PushEm - Google Cloud Message Provider
Source of the article : Wikipedia
0 Comments