Mobile Signature Service Model

Service model defines how the Application Provider (AP) can get the Mobile Signature Service.

The ETSI TR 102 203 report introduces the following service models:

  • Mobile operator’s portal. Whilst it may be attractive for an operator to provide such a portal facility for its subscribers, this is limiting for the AP. The AP is either restricted to offering a service to the customers of one mobile network or needing to implement multiple variations of the solution for each mobile network he/she wishes to address. Either way, the financial attractiveness of providing the service is likely to be impacted negatively.
  • Multiple operators provide the same service. The AP connects to all operators and makes a contract with them. Whilst such an approach might address cost issues associated with technology, it out-sources commercial problems to AP. The AP may still be faced with the administrative cost burden of negotiating/integrating with as many operators as he/she wishes to address.MSS_Portal
  • Roaming MSSP. Roaming MSSP resolves the AP’s problems and enables the Four-corner business model. In roaming model a mobile operator’s Mobile Signature Service is interconnected with other mobile signature services (e.g. a “Roaming Mobile Signature Service”) using the standard interface. In addition to simplifying matters for the AP, this approach also addresses issues of interoperability between operators in a single country or, indeed, operators in different countries. An interoperable solution also provides the largest mobile user community for APs and as such may motivate new application developers.

Nevertheless, the Kiuru MSSP software design does not depend on or impact the service model. The mobile operator can select whichever service model it prefers.

Methics focuses in the Roaming MSSP model. We believe that it is the preferred model in a long run for each party.