[go: nahoru, domu]
Jump to content

Google Cloud Messaging: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Remove repetition, and update citation for when GCM was introduced
Firebase
Line 15: Line 15:
}}
}}


'''Google Cloud Messaging''' (commonly referred to as '''GCM''') is a mobile service developed by [[Google]] that enables third-party application developers to send notification data or information from developer-run servers to applications that target the [[Android (operating system)|Google Android]] Operating System, as well as applications or extensions developed for the [[Chrome (browser)|Google Chrome]] internet browser. It is available to developers free of charge. The GCM Service was first announced in June 2012<ref>{{Cite web|url=https://android-developers.blogspot.ca/2012/06/introducing-android-41-jelly-bean.html|title=Android Developers Blog|last=Ghosh|first=Angana|date=2012-06-27|website=Introducing Android 4.1 (Jelly Bean) preview platform, and more|publisher=|access-date=2016-09-09}}</ref> as a successor to Google's now-defunct [[Android 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.<ref name="InfoQ">{{cite web|url=http://www.infoq.com/news/2012/08/GoogleCMReplacesC2Dm|last=Rubio|first=Daniel|title=Google Cloud Messaging for Android (GCM) Unveiled, to Replace C2DM Framework|date=August 12, 2012|accessdate=October 15, 2015}}</ref>
'''Google Cloud Messaging''' (commonly referred to as '''GCM''') is a mobile service developed by [[Google]] that enables third-party application developers to send notification data or information from developer-run servers to applications that target the [[Android (operating system)|Google Android]] Operating System, as well as applications or extensions developed for the [[Chrome (browser)|Google Chrome]] internet browser. It is available to developers free of charge. The GCM Service was first announced in June 2012<ref>{{Cite web|url=https://android-developers.blogspot.ca/2012/06/introducing-android-41-jelly-bean.html|title=Android Developers Blog|last=Ghosh|first=Angana|date=2012-06-27|website=Introducing Android 4.1 (Jelly Bean) preview platform, and more|publisher=|access-date=2016-09-09}}</ref> as a successor to Google's now-defunct [[Android 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.<ref name="InfoQ">{{cite web|url=http://www.infoq.com/news/2012/08/GoogleCMReplacesC2Dm|last=Rubio|first=Daniel|title=Google Cloud Messaging for Android (GCM) Unveiled, to Replace C2DM Framework|date=August 12, 2012|accessdate=October 15, 2015}}</ref> It has been superseded by Google's [[Firebase]] Cloud Messaging (FCM).


==Development==
==Development==
Line 25: Line 25:
The Chrome service was announced before Google I/O 2013 in a blog post titled 'Building efficient apps and extensions with push messaging.'<ref name = "Building efficient apps and extensions with push messaging">{{cite web|url=http://googledevelopers.blogspot.com/2013/05/building-efficient-apps-and-extensions.html|title=Building efficient apps and extensions with push messaging|publisher=[[Google]]|last=Scott|first=Mark|date=May 9, 2013|accessdate=May 14, 2013}}</ref>
The Chrome service was announced before Google I/O 2013 in a blog post titled 'Building efficient apps and extensions with push messaging.'<ref name = "Building efficient apps and extensions with push messaging">{{cite web|url=http://googledevelopers.blogspot.com/2013/05/building-efficient-apps-and-extensions.html|title=Building efficient apps and extensions with push messaging|publisher=[[Google]]|last=Scott|first=Mark|date=May 9, 2013|accessdate=May 14, 2013}}</ref>


At [[Google I/O|[I/O] 2015]], Google announced a new SDK and [[iOS]] support.
At [[Google I/O|I/O 2015]], Google announced a new SDK and [[iOS]] support.


==Technical details==
==Technical details==
Line 43: Line 43:
==External links==
==External links==
* [https://developers.google.com/cloud-messaging/ Official Google Cloud Messaging Website]
* [https://developers.google.com/cloud-messaging/ Official Google Cloud Messaging Website]
* [https://firebase.google.com/docs/cloud-messaging/ Official Firebase Cloud Messaging]
* [http://developer.android.com/google/gcm/index.html Official Android Developer Page]
* [http://developer.android.com/google/gcm/index.html Official Android Developer Page]
* [https://developers.google.com/cloud-messaging/chrome/client Official Chrome Developer Page]
* [https://developers.google.com/cloud-messaging/chrome/client Official Chrome Developer Page]

Revision as of 15:02, 5 October 2016

Google Cloud Messaging
Overview of the GCM Service architecture.
Developer(s)Google
Target platform(s)Android, Chrome
Programming language(s)Java
StatusActive
LicenseProprietary

Google Cloud Messaging (commonly referred to as GCM) is a mobile service developed by Google that enables third-party application developers to send notification data or information from developer-run servers to applications that target the Google Android Operating System, as well as applications or extensions developed for the Google Chrome internet browser. It is available to developers free of charge. The GCM Service was first announced in June 2012[1] as a successor to Google's now-defunct Android 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's Firebase Cloud Messaging (FCM).

Development

GCM first launched as Google's Android Cloud to Device Messaging (C2DM) service, first featured in Android 2.2 by Google.[3][4][5]

The transition to Google Cloud Messaging was first announced when the Android service was unveiled on June 27, 2012, at Google I/O.[6] 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.[7] Migrating to the service required SDK and code changes, as well as a release of an application update to the publish repository (such as Google 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.'[8]

At I/O 2015, Google announced a new SDK and iOS support.

Technical details

Google Cloud Messaging functions using server APIs and SDKs, both maintained by Google. The GCM has the ability to send push notifications, deep-linking commands, and application data. Larger messages can be sent with up to 4 KB of payload data.[9]

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 a GCM 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.[10] 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 authenication token is returned. Both identifiers are then sent to the GCM Service to be enqueued and delivered to the device.

See also

References

  1. ^ Ghosh, Angana (2012-06-27). "Android Developers Blog". Introducing Android 4.1 (Jelly Bean) preview platform, and more. Retrieved 2016-09-09.
  2. ^ Rubio, Daniel (August 12, 2012). "Google Cloud Messaging for Android (GCM) Unveiled, to Replace C2DM Framework". Retrieved October 15, 2015.
  3. ^ "Android Cloud to Device Messaging Framework". Google Inc.
  4. ^ "Android 2.2 Platform Highlights". Google Inc.
  5. ^ "Google Cloud Messaging (GCM) - Google Play for Developers Help". Google Inc.
  6. ^ Tarantola, Andrew (June 27, 2012). "Google's New Cloud Messaging System Does More for Less". Gizmodo. Retrieved August 10, 2012.
  7. ^ "Migration from C2DM". Google. Retrieved October 15, 2015.
  8. ^ Scott, Mark (May 9, 2013). "Building efficient apps and extensions with push messaging". Google. Retrieved May 14, 2013.
  9. ^ "Google Cloud Messaging for Android". Google.
  10. ^ "Registering Client Apps". Google. January 14, 2016. Retrieved February 5, 2016.

External links

Retrieved from "https://en.wikipedia.org/w/index.php?title=Google_Cloud_Messaging&oldid=742747443"