RMC ID (Rich Media Client IDentifier) is a key that identifies a given application on a given device.

1. How is generated the RMC ID?

The RMC ID is generated at the very first connection of the Rich Media Client to the Rich Media Server, which then returns a RMC ID which is then stored on the handset. This RMC ID will then be transmitted in every request of this RMC to any Rich Media Server

2. For how long is the RMC ID kept?

There is no time limit for the RMC ID.
If a new version of the Rich Media Client is installed "over" a former RMC, the RMC ID will be kept. On the other hand, if the current RMC is uninstalled before the installation of a new RMC, then the RMC ID will be different (a new one will be generated server-side, folliwng the process explained above).

3. Is the RMC ID unique?

Theoretically, it is mathematically not impossible to have two RMC with the same ID. But this possibility is infinitesimal, and you can consider that this situation might never happen, as its generation takes into account (among other data) the Rich Media Server licence ID, the time in milliseconds and a random number (32 bits).

4. How to get the RMC ID?

You can obtain it on the server side thanks to the UserAgent object provided in the StzService API. Check the Javadoc entry in the "doc" directory of Workbench Developer installation folder. Typically, in you RSP code, you can use the Java method "stzRequest.getUserAgent().getID()".

5. Do all applications installed on a device share the same RMC ID?

The RMC ID is associated to a RMC, not to an application:

• On Java devices, every MIDlet embeds its own engine, so every application will have a different RMC ID
• On native devices,
  • If the RMC (Viewer) and the Launchers are installed separated applications, the RMC ID will be identical for every application that shares the same Viewer
  • Else if you install a single applications that gathers in a same installer both the RMC and the Launcher, then the application will have its own RMC ID.