Chapter 3. Protocol

Table of Contents

Network identification
Recovering network identification
APIs
API: Mobile device -> Push platform
API: Push platform -> WakeUp platform (Global node)
Internal API: Local nodes
Common REST API resources

The protocol is designed to be as simple as possible (KISS philosophy).

Network identification

First of all, the mobile wanting to use this API device MUST inform their Push platforms in which mobile network are they connected. To do this, two alternatives can be used:

  • MCC - MNC (Mobile Country/Network Codes)

    This pair identifies each mobile network in a unique way.

    The ITU-T Recommendation E.212 defines mobile country codes as well as mobile network codes.

    Complete list of all MCC-MNC pairs

    This scheme is valid if the mobile network has only one segment assigned to the MCC-MCN pair.

  • Network ID (DNS Based)

    Since some mobile operators have multiple network segments under the same MCC/MNC pair (because the high number of subscribers), an alternate identification method had been designed.

    This other method identifies each mobile network by a UNIQUE HASH (selected by the MNO) but any RANDOM and UNIQUE string is valid. An UUID is recommended.

    The mobile device SHALL inform his Network ID to the Push platform and also the MCC/MNC pair.