AFSCM Interface Specification v. 2.1

7/28/2019 AFSCM Interface Specification v. 2.1

1/102

AFSCM Interface Specification V2.1 February 2012 AFSCM Confidential & Proprietary p1/102

INTERFACE SPECIFICATION

between Telecom Operators and NFC Service Providers

RELEASE 2.1

Date 13/02/2012Reference 120213 - AFSCM TECH - LIVBL - Interface Specification - V2.1.doc


2/102


Name Company

Authors Jean-Franois Roueche Bouygues Telecom

Evelyne Babel NRJ mobile

Gal Grard, Mayss Chahid, Julian

Alvero, Susana Oliver-PastorOrange

Rolla Lamaa SFR

Editor Sbastien Gauthier AFSCM

Document manager Sbastien Gauthier AFSCM

Approval Laurence Becq Orange

Document management

Version Date Chapters Modification

1.2.1 03/12/2010 - Latest revision of the 1.X interface specification

2.0 DRAFT

(1.9.16)

29/04/2011 - New features & major changes:

Subscription and installation processes loosened

Compatibility responsibility detailed

Delegated management support

More refined eligibility control functionsSupport the use of a single call to perform multiple

installation step

Registry update support

2.0 04/07/2011 - Major changes since DRAFT:

New types defined, some functions and parameters

renamed

Introduced the msId and removed the idTechHeader

installMmiReq can now handle several MMI

Section 5 detailed (retry management, load control, heartbeat)

2.0.1 13/09/2011 - Minor fixes:

XML files described in appendix 1

Types mobileHandsetId and uiccProfile added; some types

and data names slightly modified to reflect the XML files

notifChangeIdTech renamed to notifChangeMsId

2.1 02/02/2012

2.2

2.5.1

2.6.4

2.7.3

2.7.5

Minor fixes:

Use of Process 1 in first use case

Process 4 entry point precised

Removed retry from figure 16

Process 7 is optional in process 8

Added binding (process 7) at end of process 10


3/102


Version Date Chapters Modification

3.9.1

4.5.3

4.6.6All

iccId: replaced AN(1) with [0-9A-F] as in the XSD file

Process 6: added MMI ID

Fixed process 13 (works with DM now)Fixed some broken links

2.1 09/02/2012

All

3.9.2

3.9.3

3.9.4

Error codes updates

Error codes descriptions have been detailed.

Added S code type for Sequence errors

Deprecated unused code 042

Deprecated codes 202, 204

Added code 223

Reclassified codes 224, 225, 226 as S errors (instead of W)

Deprecated codes 005, 006, 007

Added codes 013 to 017

Added code 210, 223

Reclassified code 211, 224, 225, 226 as a S error

Precised definition of codes 401, 900

Version 2.1: Note on deprecated error codes:

In version 2.1 of this document, some error codes have been deprecated. There may be a slight

delay between the implementation of version 2.0.1 and version 2.1 of this specification; Service

Providers are thus encouraged to implement the error codes of version 2.1 of the specification, but

still support the deprecated codes until all implementations are up-to-date with version 2.1.


4/102


TABLE OF CONTENTS ____________________________________________________________

1 INTRODUCTION ................................................................................................................... 91.1 Context .................................................................................................................................................. 91.2 Purpose of the interface specification ................................................................................................ 101.3 Content of the interface specification................................................................................................. 101.4 Assumptions ........................................................................................................................................ 101.5 How to use this specification?............................................................................................................. 111.6 Reference to the other AFSCM guidelines .......................................................................................... 121.7 References ........................................................................................................................................... 121.8 Acronyms and abbreviations ............................................................................................................... 131.9 Definitions ........................................................................................................................................... 132 FUNCTIONAL REQUIREMENTS: PROCESS DESCRIPTION AND FLOWCHARTS ........................................... 142.1 Process overall mapping...................................................................................................................... 142.2 Service discovery, subscription and installation sequences ............................................................... 152.3 Eligibility and scoring sub-processes ................................................................................................... 16

2.3.1 Eligibility and compatibility: definitions ................................................................................. 162.3.2 Sub-process A MNO eligibility .............................................................................................. 172.3.3 Sub-process B SP compatibility ............................................................................................ 172.3.4 Sub-process C SP scoring ..................................................................................................... 18

2.4 Service discovery and inquiry processes ............................................................................................. 182.4.1 Process 1 Online service discovery ...................................................................................... 192.4.2 Process 2 Inquiry to the Service Provider ............................................................................ 192.4.3 Process 3 Inquiry to the Mobile Network Operator ............................................................ 20

2.5 Subscription processes ........................................................................................................................ 212.5.1 Process 4 Subscription to a mobile NFC Service .................................................................. 21

2.6 Installation processes .......................................................................................................................... 232.6.1 Definition of the mobile NFC service ...................................................................................... 232.6.2 Installation processes sequencing .......................................................................................... 232.6.3 UICC and UICC application architecture ................................................................................. 242.6.4 Process 5 Mobile NFC UICC application installation ............................................................ 262.6.5 Process 5 Update Mobile NFC UICC application update...................................................... 282.6.6 Process 6 Service Provider MMI installation / update......................................................... 292.6.7 Process 7 MMI and UICC application binding ...................................................................... 33

2.7 Life cycle processes ............................................................................................................................. 332.7.1 Locking a mobile NFC service .................................................................................................. 342.7.2 Suspended line and restricted line ......................................................................................... 342.7.3 Process 8 Change UICC ........................................................................................................ 342.7.4 Process 9 Change mobile phone number ............................................................................ 352.7.5 Process 10 Change mobile handset ..................................................................................... 362.7.6 Process 11 Lost or stolen mobile equipment, end user contacts MNO .............................. 382.7.7 Process 12 Lost or stolen mobile equipment, end user contacts Service Provider ............. 382.7.8 Process 13 Recover mobile equipment after a loss (or theft) ............................................. 392.7.9 Process 14 Get a new mobile equipment after a loss or theft ............................................ 402.7.10 Process 15 End User requests temporary mobile service suspension ............................. 412.7.11 Process 16 Change in contract ownership ....................................................................... 422.7.12 Process 17 End user swaps Mobile Network Operator .................................................... 43


5/102


2.8 Termination processes ........................................................................................................................ 432.8.1 Process 18 Termination of Mobile subscription or NFC option by end user ....................... 432.8.2 Process 19 Mobile service termination by Mobile Network Operator ................................ 442.8.3 Process 20 Mobile NFC service termination ........................................................................ 45

3 INTERFACE SPECIFICATION ..................................................................................................... 483.1 Introduction ......................................................................................................................................... 48

3.1.1 Implementation ...................................................................................................................... 483.1.2 Elementary requests / batch .................................................................................................. 483.1.3 Naming conventions ............................................................................................................... 483.1.4 Data types ............................................................................................................................... 493.1.5 Synchronous and Asynchronous ............................................................................................. 493.1.6 Retries and validity period management for asynchronous requests.................................... 50

3.2 Headers ............................................................................................................................................... 503.2.1 syncHeader Header for Synchronous Requests ................................................................... 503.2.2 asyncHeader Header for Asynchronous Requests ............................................................... 513.3 Acknowledgments and exceptions ...................................................................................................... 513.3.1 acknowledge ........................................................................................................................... 513.3.2 acknowledgeWithValidityPeriod ............................................................................................ 523.3.3 faultMsg .................................................................................................................................. 52

3.4 Identifiers ............................................................................................................................................ 523.4.1 Technical Identifier idTech ...................................................................................................... 523.4.2 Service Identifiers: serviceId and serviceVersion ................................................................... 53

3.5 Control functions ................................................................................................................................. 543.5.1 getUICCProfile ......................................................................................................................... 543.5.2 getMobileHandsetProfile ........................................................................................................ 553.5.3 isEligible .................................................................................................................................. 553.5.4 getIdTech ................................................................................................................................ 563.5.5 fullEligibilityCheck ................................................................................................................... 56

3.6 Installation requests ............................................................................................................................ 583.6.1 createOrAllocateSsdReq and createOrAllocateSsdResp ........................................................ 583.6.2 getTokens ................................................................................................................................ 593.6.3 installReq and installResp ....................................................................................................... 613.6.4 installMmiReq and installMmiResp ........................................................................................ 643.6.5 bindMmiReq and bindMmiResp ............................................................................................. 653.6.6 suppressReq and suppressResp .............................................................................................. 66

3.7 Notifications ........................................................................................................................................ 673.7.1 notifStateChangeToMno ........................................................................................................ 673.7.2 notifCallEndUserToMno ......................................................................................................... 693.7.3 notifNewDevice ...................................................................................................................... 693.7.4 notifChangeMsId .................................................................................................................... 703.7.5 notifCallEndUserToSp ............................................................................................................. 713.7.6 notifStateChangeToSp ............................................................................................................ 71

3.8 Script sending ...................................................................................................................................... 723.8.1 sendScriptsReq and sendScriptsResp ..................................................................................... 72

3.9 Data dictionary .................................................................................................................................... 743.9.1 Data types ............................................................................................................................... 743.9.2 Response and exception types ............................................................................................... 793.9.3 Response codes to asynchronous requests ............................................................................ 803.9.4 Exceptions ............................................................................................................................... 81

4 PROCESS IMPLEMENTATION REFERENCE..................................................................................... 84


6/102


4.1 Representation of the exchanges........................................................................................................ 844.2 Eligibility and scoring sub-processes ................................................................................................... 84

4.2.1 Sub-process A MNO eligibility .............................................................................................. 844.2.2 Sub-process B SP compatibility ............................................................................................ 854.2.3 Sub-process C SP scoring ..................................................................................................... 85

4.3 Service discovery and inquiry processes ............................................................................................. 854.3.1 Process 1 Online service discovery ...................................................................................... 854.3.2 Process 2 Inquiry to the Service Provider ............................................................................ 854.3.3 Process 3 Inquiry to the Mobile Network Operator ............................................................ 85

4.4 Subscription processes ........................................................................................................................ 854.4.1 Process 4 Subscription to a mobile NFC Service .................................................................. 85

4.5 Installation processes .......................................................................................................................... 854.5.1 Process 5 Mobile NFC UICC application installation ............................................................ 854.5.2 Process 5 Update Mobile NFC UICC application update...................................................... 894.5.3

Process 6 Service Provider MMI installation / Update ........................................................ 90

4.5.4 Process 7 MMI and UICC application binding ...................................................................... 92

4.6 Life cycle processes ............................................................................................................................. 924.6.1 Process 8 Change UICC ........................................................................................................ 924.6.2 Process 9 Change mobile phone number ............................................................................ 934.6.3 Process 10 Change mobile handset ..................................................................................... 934.6.4 Process 11 Lost or stolen mobile equipment, end user contacts MNO .............................. 934.6.5 Process 12 Lost or stolen mobile equipment, end user contacts Service Provider ............. 944.6.6 Process 13 Recover mobile equipment after a loss ............................................................. 944.6.7 Process 14 Get new mobile equipment after a loss or theft ............................................... 954.6.8 Process 15 End User requests temporary mobile service suspension ................................ 954.6.9 Process 16 - Change in contract ownership ............................................................................ 954.6.10 Process 17 End user swaps Mobile Network Operator .................................................... 96

4.7 Termination processes ........................................................................................................................ 964.7.1 Process 18 Termination of Mobile subscription or NFC option by end user ....................... 964.7.2 Process 19 Mobile service termination by Mobile Network Operator ................................ 964.7.3 Process 20 Mobile NFC service termination ........................................................................ 97

5 WEB SERVICE IMPLEMENTATION ............................................................................................. 995.1 Protocol ............................................................................................................................................... 995.2 Interface .............................................................................................................................................. 995.3 HEART_BEAT ........................................................................................................................................ 995.4 Protocol retry management ................................................................................................................ 995.5 Load control....................................................................................................................................... 1005.6 Request sender authentication ......................................................................................................... 101APPENDIX 1 XSD AND WSDL FILES............................................................................................ 102


7/102


TABLE OF FIGURES ______________________________________________________________

Figure 1 Process flowcharts legend ........................................................................................................... 14Figure 2 Process overall mapping .............................................................................................................. 14Figure 3 Service discovery and subscription: from a mobile web site ...................................................... 15Figure 4 Service discovery and subscription: from an application store ................................................... 15Figure 5Service discovery and subscription: at the Service Providers office .......................................... 16Figure 6 Flowchart of sub-process A MNO eligibility .............................................................................. 17Figure 7 Flowchart of sub-process B SP compatibility ............................................................................ 18Figure 8 Flowchart of sub-process C SP scoring ..................................................................................... 18Figure 9 Flowchart of process 1 Online service discovery ...................................................................... 19Figure 10 Flowchart of process 2 Inquiry to the Service Provider .......................................................... 20Figure 11 Flowchart of process 3 Inquiry to the Mobile Network Operator .......................................... 21Figure 12 Flowchart of process 4 Subscription to a mobile NFC Service ................................................ 22Figure 13 Mobile phone number authentication example ....................................................................... 22Figure 14 Representation example of the UICC application ..................................................................... 24Figure 15 Flowchart of process 5 Mobile NFC UICC application installation in Simple SD mode

personnalisation before activation .............................................................................................................. 26Figure 16 Flowchart of process 5 Mobile NFC UICC application installation in Simple SD mode

personnalisation after activation ................................................................................................................. 27Figure 17 Flowchart of process 5 Mobile NFC UICC application installation in Delegated Management

mode ............................................................................................................................................................. 27

Figure 18 Flowchart of process 5 Update Mobile NFC UICC application update in Simple SD mode .... 28Figure 19 Flowchart of process 5 Update Mobile NFC UICC application update in Delegated

Management mode ...................................................................................................................................... 29Figure 20 Flowchart of process 6 Service Provider MMI installation, case 1 ......................................... 30Figure 21 Flowchart of process 6 Service Provider MMI installation, case 2 ......................................... 31Figure 22 Flowchart of process 6 Service Provider MMI installation, case 3 ......................................... 32Figure 23 Flowchart of process 7 MMI and UICC application binding ................................................... 33Figure 24 Flowchart of process 8 Change UICC ...................................................................................... 35Figure 25 Flowchart of process 9 Change mobile phone number .......................................................... 36Figure 26 Flowchart of process 10 Change mobile handset ................................................................... 37Figure 27 Flowchart of process 11 Change UICC Lost or stolen mobile equipment, end user contacts

MNO ............................................................................................................................................................. 38Figure 28 Flowchart of process 12 Change UICC Lost or stolen mobile equipment, end user contacts

SP .................................................................................................................................................................. 39Figure 29 Flowchart of process 13 Recover mobile equipment after a loss (or theft) ........................... 40Figure 30 Flowchart of process 14 Get a new mobile equipment after a loss of theft .......................... 41Figure 31 Flowchart of process 15 End User requests temporary mobile service suspension .............. 42Figure 32 Flowchart of process 16 Change in contract ownership ........................................................ 43Figure 33 Flowchart of process 18 Termination of mobile subscription or NFC option by end user ..... 44Figure 34 Flowchart of process 19 Mobile service termination by Mobile Network Operator ............. 45Figure 35 Flowchart of process 20 Mobile NFC service termination in Simple SD mode ...................... 46Figure 36 Flowchart of process 20 Mobile NFC service termination in Delegated Management mode46


8/102


Figure 37 Architecture overview ............................................................................................................... 48Figure 38 Sample sequence diagram of synchronous and asynchronous exchanges ............................... 49Figure 39 Validity period management ..................................................................................................... 50Figure 40 Simplified representation used in sequence diagrams ............................................................. 84Figure 41 Legend of sequence diagrams ................................................................................................... 84Figure 42 Sequence diagram of Sub-process A MNO eligibility ............................................................. 85Figure 43 Sequence diagram of Sub-process B SP compatibility ............................................................ 85Figure 44 - Sequence diagram of Process 5 Installation of UICC application in Simple SD mode

(personalization then activation) ................................................................................................................. 86Figure 45 Sample sequence diagram of Process 5 Installation of UICC application in Simple SD mode

using grouped requests (activation then personalization)........................................................................... 87Figure 46 - Sequence diagram of Process 5 Installation of UICC application in Delegated Management

mode ............................................................................................................................................................. 88Figure 47 - Sequence diagram of Process 5 UICC application update in Simple SD mode ........................ 89Figure 48 - Sequence diagram of Process 5 UICC application update in Delegated Management mode ... 89Figure 49 - Sequence diagram of Process 6 MMI installation managed by MNO ..................................... 90Figure 50 - Sequence diagram of Process 6 MMI installation launched by MNO ........................................ 90Figure 51 - Sequence diagram of Process 6 MMI Installation launched by Service Provider ................... 91Figure 52 - Sequence diagram of Process 6 End user installs the MMI from an application store ........... 91Figure 53 - Sequence diagram of Process 6 Critical MMI update.............................................................. 92Figure 54 Sequence diagram of Process 7 MMI and UICC application binding ...................................... 92Figure 55 - Sequence diagram of Process 8 Change UICC ......................................................................... 92Figure 56 - Sequence diagram of Process 9 Change mobile phone number ............................................. 93Figure 57 - Sequence diagram of Process 10 Change mobile handset ...................................................... 93Figure 58 - Sequence diagram of Process 11 Lost or stolen mobile equipment, end user contacts MNO

...................................................................................................................................................................... 93Figure 59 - Sequence diagram of Process 12 Lost or stolen mobile equipment, end user contacts SP .... 94 Figure 60 - Sequence diagram of Process 13 Recover mobile equipment after a loss ............................. 94Figure 61 - Sequence diagram of Process 14 Get new mobile equipment after a loss or theft ................ 95Figure 62 - Sequence diagram of process 15Suspension of mobile service upon end users request ..... 95Figure 63 - Sequence diagram of process 16 Change in contract ownership ........................................... 96Figure 64 - Sequence diagram of Process 18 Termination of mobile subscription or NFC option by enduser ............................................................................................................................................................... 96Figure 65 - Sequence diagram of Process 19 Mobile service termination by MNO .................................. 97Figure 66 - Sequence diagram of Process 20 Mobile NFC service termination in Simple SD mode ......... 97Figure 67 - Sequence diagram of Process 20 Mobile NFC service termination in DM mode .................... 97Figure 68 Retry management illustration ................................................................................................ 100


9/102


1 INTRODUCTION1.1 Context

The Mobile Network Operators Bouygues Telecom, Orange and SFR have founded the AFSCM

(Association Franaise du Sans Contact Mobile) to foster the development of mobile contactless

services.

The Service Providers Credit Mutuel, Socit Gnrale and Volia have already joined the AFSCM

as associate members.

The AFSCM objective is to support the inception of new contactless services for mobile phone

users. In particular, AFSCM endeavours:

- To support service providers such as banks or transit authorities in the definition and

deployment of contactless solutions suited for mobile subscribers to any available mobile

network;

- To specify technical guidelines for the development of mobile contactless services to ensure

seamless installation and consistent user experience;

- To promote the benefits of the mobile phone platform for contactless service providers, for

technology providers and for end users.

To define a mutually beneficial mobile contactless eco-system, AFSCM will propose a shared

mobile contactless target mark and a shared brand that will distinguish those contactless services

that are available to mobile phone users.

AFSCM constituency will include all companies involved in the development of a sustainable

market for mobile contactless services such as Service Providers, handset makers, smart card

manufacturers, Mobile Network Operators, MVNOs. Together, AFSCM members will contribute tothe definition of innovative industry standards and best practices.

The stated objective of the AFSCM is to facilitate the development of mobile contactless services.

To this end, the founding members recognize the significance of the following success factors:

- Virtuous eco-system in which all parties involved can develop a sustainable market position,

- Efficient customer support,

- Smooth customer experience,

- State-of-the art application life cycle management,

- Service portability in the event of a mobile equipment swap,

-

Service portability in the event of a Mobile Network Operator swap.


10/102


1.2 Purpose of the interface specificationThe purpose of this document is to facilitate a deployment of mobile NFC services involving the

French Mobile Network Operators and various profiles of Service Providers.

To this end, AFSCM members have recognized the definition of a standardized interface and

processes. That ensures interoperability between the actors simplifies the deployment and avoids

redundancy in a multi-actors environment.

From the point of view of a Service Provider, this interface specification ensures that the same

mechanisms and the same server will be applicable regardless of the mobile network selected by

the end user.

From the point of view of a Mobile Network Operator, this interface specification provides a

unified way of exchanging data with any Service Providers of mobile NFC services.

Furthermore, this specification covers the entire life cycle of a mobile NFC service from the

perspective of the end user.

1.3 Content of the interface specificationThis document describes in chapter2 Functional Requirements: process description and flowcharts

the processes for every step of the customer journey: inquiry of information, subscription and

installation of the mobile NFC service, use and termination of the mobile NFC service.

Then, the document presents the detailed specification of the interface between Mobile Network

Operators and Service providers in section3 Interface Specification.

Section4 Process implementation referencepresents the exchanges on the SP/MNO interface for

all processes of the customer journey,

Web service implementation, exchange protocol and the connection between the information

systems of both actors are described in section5 Web service implementation.

1.4 AssumptionsThe work of the Process and Technical committees of the ASFCM, resulting in the current

document, has been based on two sources of information:

- On one hand, the existing specifications of Mobile NFC services. These specifications target

implementation for dedicated service domains:

o Ulysse specifications for mobile NFC transport ticketing services,

o and Payez Mobile specifications for mobile NFC payment services.

- And on the other hand, the technical capabilities of the different components of the NFC

ecosystem including the NFC mobile handset, the UICC and the MNO information systems.A key driver is to propose a simple and efficient solution, which covers all identified NFC use cases

for a UICC centric model. It is a more mature solution than version 1 and targets large commercial

deployments.

The AFSCM also specifies high level requirements for both UICC and mobile handsets in separate

documents. These documents are only provided to the relevant suppliers on request.

UICC technology

The NFC application is hosted on the UICC of the mobile equipment.

The UICC uses JavaCard 2.2.2 technology and implements GlobalPlatform 2.2.

Supported GlobalPlatform features

Within the features defined by GlobalPlatform for remote application management, both Simple

SD management (with DAP as an option) and Delegated Management are supported. Confidential

Loading for packages is not supported in this version of the specification.


11/102


Mandated DAP is supported but has no impact on this interface specification. Mandated DAP is a

feature that automatically ensures that the applications loaded on the UICC were previously

validated.

UICC memory sizeIn version 2 of the specification, it is not possible to manage memory space booking on a UICC as

described in Payez Mobile.

OTA capabilities

The SSD are created in the UICC. SSD can be created in two different ways:

- SSD creation in factory in this case, the SSD root keys may not be managed by the MNO.

- Or SSD creation OTA in this case, the SSD temporary keys are managed by the MNO.

The application package is loaded in the UICC. It can be loaded either in factory or OTA. Once the

application is available in the UICC, the application activation (or deactivation) is performed upon

request of the Service Provider.

Process and Information Systems

The following assumptions are made based on the current Information System limitations:

- The Mobile Network Operators will not send notifications to the Service Providers prior to line

suspension, termination or UICC change for instance. The Service Providers are informed once

the suspension or termination is effective.

- A technical identifier is used to identify the end user in the communication between Mobile

Network Operator and Service Providers. The Mobile Network Operator is identified in the

header of each request, response and notification with the mnoId data.

- Another restriction is related to the synchronisation of actions in case of urgent situations

such as loss or theft. This specification requires the UICC application to be locked or deletedbefore the line is suspended or terminated in order to avoid uncontrolled applications in the

wild. Yet, it relies on the capacity of the Mobile Network Operator s information system to

perform the locking actions before line suspension or termination, which is not guaranteed in

version 2 of this specification.

Interoperability and multi application management

The support of multi applications is possible thanks to the Java Card and GP technologies ensuring

secure partition between applications.

The AFSCM development guides ([R2] MIDlet Development Guide and [R3] Cardlet Development

Guide) define rules regarding interaction between NFC homepage application and the Service

Providers' applications.

1.5 How to use this specification?Mandatory, conditional and optional features

In the specifications below, some features are optional or conditional. They are represented in

dotted line in the flowcharts and the conditions are mentioned in the description.

These features are optional or conditional for the Service Provider, except for the MMI and UICC

application binding, the implementation of which is a decision of the MNO.

Each Service Provider is responsible for selecting within the optional and conditional features

proposed in this specification the ones that are the most appropriate for its mobile NFC servicethus resulting in a fine tuned configuration. From this perspective, this specification can be

considered as a tool box in which the Service Provider selects the set of features that is best suited

for its mobile NFC service.


12/102


All features that are not explicitly optional or conditional are mandatory features. They must be

implemented by each Service Provider in order to be AFSCM compatible.

The MNO platform is ready to manage all the possible Service Provider configurations provided

that they are compliant with the current interface specification.

Versions

Version 1 of this specification was designed to meet the requirements for short term deployments

in 2010.

Version 2 is designed for commercial deployment and improves on version 1 by

- bringing new features such as Delegated Management support,

- adding more functions, which are more modular, while retaining the simplicity of version 1,

- including various feedbacks from Service Provider and industry partners following the 2010

short term deployments.

- Improving reliability mechanisms (validity period, retries)

1.6 Reference to the other AFSCM guidelinesThe definition of the Service Provider/MNO interface is essential to ensure the interoperability.

This specification is coherent with the other guidelines of the AFSCM that are related to:

- The NFC applications validation process. The purpose of this document is to provide the

Service Providers with a unique process and rules for elaborating NFC applications taking into

account the MNO requirements.

- The NFC applications (Cardlet and MMI) development guidelines. The rules for elaborating

NFC applications are fully detailed in a guidelines book that gather all the functional, technical

and security requirements regarding the process for validation, loading and hosting of NFC

applications.

- The definition of Secure Service Management roles,

- The guidelines for interconnection of Service Providers' and MNOs' Information Systems. This

document is the continuation of the interface specification, providing information on the

process to be applied and the data that must be exchanged prior to establishing any

connection between information systems. This document specifies the provisioning

mechanisms for compatibility.

- The customer support guidelines

1.7 ReferencesThe following documents are available for the Service Providers:

AFSCM

[R1] NFC Applications Validation Process[R2] MIDlet Development Guide[R3] Cardlet Development Guide[R4] Secure Services Management Role[R5] Guidelines for interconnection of Service Providers' and MNOs' Information Systems[R6] Customer support guidelinesPayez Mobile (AEPM)

[R7] Book 0 - General Description v1.1[R8] Book 1 - Mobile Handset UICC Applications v1.1


13/102


14/102


2 FUNCTIONAL REQUIREMENTS: PROCESS DESCRIPTION AND FLOWCHARTSThis section presents all the user experiences as they can be implemented in version 2. The

restrictions compared to the mid term and long term target as defined for instance in Payez

Mobile or Ulysse are highlighted.

Action

Process

Choice

Optional action or

process

Covers a process already

descr ibed

Notifications

Figure 1 Process flowcharts legend

2.1 Process overall mappingThe following chart presents the processes that are described in this document, grouped in

categories. Optional or conditional processes are represented with a dotted outline.

Termination

Global process mapping

Sub-processesInquiry

Su

bscription

Installation

Use

MNO eligibility

Sub-process A

Lost/stolen Mobileequipment, user contacts

MNO - Process 11

Inquiry to Service Provider

Process 2

Lost/stolen Mobileequipment, user contacts

SP - Process 12

SP compatibility

Sub-process B

Mobile NFC service

termination - Process 20

Change in contract

ownership - Process 16

SP scoring

Sub-process C

Change UICC

Process 8

Mobile service termination

by MNO - Process 19

Change Mobile Handset

Process 10

Service subscription

Process 4

MMI and UICC application

binding - Process 7

Update UICC application

Process 5 Update

Online service discovery

Process 1

Install UICC application

Process 5

Conditional,

mandatory only if

MMI is necessary

Termination of Mobile

subscription or NFC option

by end user - Process 18

Install / Update MMI

Process 6

Subscription is mandatory but

can come before or after some

installation processes

Change Mobile Phone

Number - Process 9

Recover mobile equipment

Process 13

End user requestsTemporary mobile service

supsension - Process 15

Inquiry to MNO

Process 3

Get new mobile equipment

Process 14

Optional, only

if SP wants to

update OTA

End user swaps MNO

Process 17Optional process

Not supported yet

Conditional,

mandatory when

MNO supports it

Figure 2 Process overall mapping


15/102


2.2 Service discovery, subscription and installation sequencesThere are several ways to sequence the inquiry, subscription and installation steps.

The Service Provider must be compliant with either of the possibilities presented in the following

diagrams:

Figure 3 Service discovery and subscription: from a mobile web site

In the diagram above, Process 1 can be accessed from the MNO wallet for instance.

Use case example #2: service discovery from a mobile

application store and subscription from inside the MMI

Process 4 Subscription to a

mobile NFC Service

Process 5 Installation of

UICC application

Process 6 Service Provider

MMI installation

The end user launches his MMI, that

initiates the subscription

Service available for use

Notify MNO about MMI

installation/update

Process 7 MMI and UICC

application binding

Process 1 Online service

discovery

Figure 4 Service discovery and subscription: from an application store


16/102


Use case example #3: subscription in the serviceproviders offices

The end user goes at the serviceproviders office to subscribe

Process 4 Subscription to a mobile NFC

Service

Process 5 Installation of UICC

application

Process 2 End user asks his Service Provider

about available mobile NFC services

Process 6 Service Provider MMI

installation

Service available for use


application binding


application

Process 6 Service Provider MMI

installation


application binding

OR

Figure 5 Service discovery and subscription: at the Service Providers office

2.3 Eligibility and scoring sub-processesThis section presents sub-processes regarding eligibility and scoring, that will be used further in

several processes.

2.3.1 Eligibility and compatibility: definitionsThis version of the specification introduces the notion of compatibility, in order to be able to

manage a growing number of UICC and handset models.

Eligibility is still the responsibility of the MNO, and ensures an end users equipment is eligible to

mobile NFC services (seeSub-process A).

Compatibility is the responsibility of the Service Provider, who ensures a handset model and a

UICC model are compatible with his services (the SP assures that he has tested his service on this

mobile reference, or that his MMI is available for this reference, etc). A given mobile NFC service

may for instance be available for a handset model and not for another. A sub-process has been

created to handle compatibility checks (seeSub-process B SP compatibility)

In order to provide the best user experience to the end-user, it is important for the MNO to be

able to:

Inform the end user about the available services on his mobile handset at the earliest

stage of his subscription,

Inform the end user about new services now available for his mobile handset,

Present to the end user only the services that are compatible with his device during service

discovery.


17/102


This will be achieved at provisioning stage. The SP will provide the MNO with a list of compatible

devices/operating systems with its services. This provisioning solution is described in [R5]

Guidelines for interconnection of Service Providers' and MNOs' Information Systems.

In addition to helping the end user find the services compatible with his handset, this will help the

Service Provider avoid compatibility issues or end user complaints.

2.3.2 Sub-process A MNO eligibilityFlowchart

MNOe

ligibility

Sub-process A MNO eligibility

Mobile Network OperatorService Provider

Yes

NoEnd user is not eligible

(reason)

Check eligibility of the end user (based on the

technical identifier provided) to the service:

- mobile handset eligibility

- UICC eligibility- MNO offer eligibility

End user is eligible

Request for eligibility

of end user

Is end user eligible

from MNO perspective?

Figure 6 Flowchart of sub-process A MNO eligibility

Description

This sub-process is used whenever the SP needs to ensure an end users equipment is eligible to

the mobile NFC service.

In this sub-process, the MNO is responsible for ensuring the said eligibility, based on the

information at his disposal and the following criteria:

- Commercial contract: the end-user has a contract with the Mobile Network Operator, and has

access to NFC services

- Technical: UICC and mobile handset are NFC capable

- Available memory space on UICC

[Note] Should the end user gets his mobile equipment outside of the Mobile Network Operators'point of sales network, the MNO cannot guarantee its eligibility, even if it is NFC capable.

Restrictions specific to Version 2

In Version 2 of this specification, the way the eligibility check works might differ from one MNO to

another especially regarding the available memory space on UICC; moreover, the accuracy of the

information regarding the available memory space is not guaranteed.

2.3.3 Sub-process B SP compatibilityFlowchart


18/102


SPcompatibility

Sub-process B SP compatibility


YesNo

Provide detailed informationabout the end users UICC

and/or mobile handset

Mobile equipment

is compatible

Mobile equipment is not

compatible (reason)

Request detailed informationabout the end users mobile

equipment (UICC and/or mobile

handset)

Is the mobile equipment

compatible with the service?

Figure 7Flowchart of sub-process B SP compatibility

Description

This sub-process is used whenever the SP needs to ensure that an end users equipment is

technically compatible with his mobile NFC service.

The Service Provider is responsible for maintaining a list of mobile handsets and UICC models that

are compatible with his mobile NFC service.

In this sub-process, the MNO provides the necessary technical information to the SP, and the SP

checks the said technical compatibility.

2.3.4 Sub-process C SP scoringFlowchart

SPscoring

Sub-process C SP scoring

Service ProviderEnd user

Positive Negative

End user cannot

subscribe to the

service (reason)

Perform internal

service scoring

End user can

subscribe to the

service

Ask necessary information for user

subscription

Provide

information

Figure 8 Flowchart of sub-process CSP scoring

Description

This sub-process includes the verifications that the SP requires to allow user subscription.

The MNO takes no part in this process.

2.4 Service discovery and inquiry processesIn these processes, the end user discovers the NFC services.

In theProcess 1, he discovers a mobile NFC service on an online application store. This process is

optional.


19/102


In the other processes, the end user inquires about a mobile NFC service and contacts either the

Service Provider (Process 2) or the Mobile Network Operator (Process 3). Both processes are

mandatory.

2.4.1

Process 1

Online service discovery

Flowchart

Inquiry

Process 1 - Online service discovery

Mobile Network OperatorEnd user

Proceed to subscription or installation

processes

End user browses an application store

End user chooses to intall the MMI of

the mobile NFC service[Note]On a MNO application store, the

MNO may only present eligible and

compatible services to the end user

Check services to which the end

users equipment is eligible

Check services with which the end

users equipment is compatible

Figure 9 Flowchart of process 1 Online service discovery

Description

There are two kinds of application stores that the end user can use:

Independent application stores are set up and maintained by the mobile handset maker, or

the mobile handset OS provider;MNO application stores contains applications that are showcased by the MNO ; in this

case, the MNO is able to perform a pre-emptive eligibility and compatibility check (the SP

provides the compatibility information)

[Note] In order for the MNO to provide more compatibility information to the end user, the SP needsto provide the MNO its service compatibility information. The provisioning of this information

is described in[R5].

2.4.2 Process 2 Inquiry to the Service ProviderFlowchart


20/102


Inquiry

Process 2 End user asks his Service Provider about available

mobile NFC services

Service Provider MNOEnd user

User eligible

End user inquires about

mobile NFC services

Process 4 Subscription to a

mobile NFC Service

User not

eligible

Inform the End user about:

- mobile NFC services

- subscription requirements

Ask the end user to

contact his MNO

Sub-process A

MNO eligibility

Figure 10 Flowchart of process 2 Inquiry to the Service Provider

Description

The Service Provider is responsible for the information regarding the mobile NFC service and its

delivery to his customers. The Service Provider verifies the end users equipment eligibility and

invites him to subscribe.

Shoud the end user not be eligible, the Service Provider can mention that there are pre requisites

on the UICC and mobile NFC handset for accessing a mobile NFC service and invite the end user

to contact his Mobile Network Operator (Process 3) to get proper mobile equipment.

2.4.3 Process 3 Inquiry to the Mobile Network OperatorFlowchart


21/102


ProvideenduserwithNFC

device

Process 3 End user asks his MNO about available mobile NFC services

Mobile Network OperatorEnd user

NoNo

Yes

NoNo

Yes

Inq

uiry

Process 2 End user asks his Service

Provider about available mobile NFC services

Does the end user

wish to buy one?

End user inquires aboutmobile NFC services

Does the end user

wish to subscribe to

the offer ?

End user is not eligible to

mobile NFC services

Yes

Yes

Sell appropriate

offer

Sell an NFC

device

Inform the end user about the services

compatible with the mobile device

Does end user have an

NFC device?

Does the current end user

offer allow the access to

NFC services?

Inform the end user about contractual and technicalprerequisites as well as Service Provider requirements

Ask the end user to contact his targeted Service

Provider to subscribe to a mobile NFC service

Figure 11 Flowchart of process 3 Inquiry to the Mobile Network Operator

Description

The Mobile Network Operator is responsible for informing about mobile NFC services and their

requirements; the MNO will thus check the end users eligibility and, shou ld the end user not be

eligible, propose the appropriate mobile equipment and offer.

The MNO can invite the end user to contact the Service Provider for additional information about

the service (Process 2) or subscription (Process 4).

2.5 Subscription processesThe subscription to a new or to an additional mobile NFC service can take place through different

channels:

-The Service Provider's local office or web site

- From the mobile handset in a WAP session (in a WAP browser or through the MMI, if it has

already been installed)

The Service Provider must use at least one of these channels.

2.5.1 Process 4 Subscription to a mobile NFC ServiceFlowchart


22/102


Figure 12 Flowchart of process 4 Subscription to a mobile NFC Service

The following diagram is an example of how the Service Provider can ensure the authentication of

the mobile phone number provided by the end user.

Get the end user MSISDN to check its elibigility

(sub-process example)

Example of end user and m obi le authentication using an authentication key

Short leadtime (except

if network troubles)

MSISDN authenticated

No

Send SMS containing an

authentication key to end user

Authentication key match?

SMS reception.

Communicate the

authentication key to theService Provider

Useragrees

Ask the end users mobile phone number

and his approval for checking its elibigility

to NFC service (legal impacts)

User refuses

The SP needs to get and authenticate the

MSISDN (for eligibility purposes for instance)

Figure 13 Mobile phone number authentication example

Description

The same process applies whether it is the end users first subscription to a mobile NFC service or a

subscription to an additional mobile NFC service.

During the course of this process, the Service Provider must identify the end user in order to beable to communicate with the MNO; several possibilities exist:


23/102


- The Service Provider can ask the end users mobile phone number and his approval for

submitting an eligibility request to the Mobile Network Operator (this case is presented in

Figure 13)

- The Service Provider can use the MNO WAP alias (technical identifier from a WAP session,

provided upon agreement by the MNO)

2.6 Installation processes2.6.1 Definition of the mobile NFC serviceA mobile NFC service is constituted by one or several UICC applications and may include one or

several mobile applications (MMI, which are optional).

In this specification, a mobile NFC service is identified by a serviceId. The following precisions are

made concerning this identifier:- All application instances of a mobile NFC service identified by the same serviceId are in the

same SSD

- If the SP updates one of his UICC application packages, the serviceVersion must be

incremented

- A service can only be installed once, and in only one serviceVersion, on a given UICC

- A single UICC application package can be used to instantiate several cardlet applications, but

with a different serviceId for each instance : the package is then shared between services

- A single UICC application instance cannot be used by 2 different services

The following precisions are made regarding the MMI in a mobile NFC service:- The MMI can be available in different formats and versions in order to address different

handset models; more information about MMI formats for compatibility can be found in[R5]

Guidelines for interconnection of Service Providers' and MNOs' Information Systems

- The evolution of the versioning of the MMI has no impact on the evolution of the

serviceVersion parameter (if the version of the mobile application of a service is incremented,

it does not increment the serviceVersion of the service)

- A single MMI instance can use several UICC application instances with different serviceId

identifiers

- A UICC application can be used by several MMI that have the same serviceId

- This document takes MMI installation into account, but direct implementation of this

installation is not detailed.

2.6.2 Installation processes sequencingThe mobile NFC services installation process is divided in three steps:

- Mobile NFC UICC application installation (Process 5): this process is mandatory and depending

on the implementation decided by the Service Provider, can be done using the Simple SD

mode or the Delegated Management mode.

- Service Provider MMI installation / update (Process 6): this process is conditional. It is possible

that some mobile NFC services do not require a MMI. In this case the Process 6 is not

applicable.

- MMI and UICC application binding (Process 7): this process is conditional: if the MNO

implements bindings, the SP has to implement this process.


24/102


These steps may be performed in the order of preference of the Service Provider, the only

condition being that Process 7 must always come after Process 5 or Process 5 Update. The

installation sequences are detailed in section 2.2 Service discovery, subscription and installation

sequences .

A mobile NFC service is considered completely installed, and is indeed fully operational for the End

user, once the UICC application(s) AND the MMI are installed: it is thus imperative, particularly for

the customer services, that the Service Provider notifies the MNO of the MMI installation progress.

These installation processes also include the update of applications, described by the following

processes:

- Process 5 Updatefor the UICC application update. Implementation of this process is optional,

depending on the Service Providers decision to be able to update OTA its UICC application. As

for the installation of the UICC application, this process can be implemented using the Simple

SD mode or the Delegated Management mode- Process 6for the MMI update. Implementation of this process is mandatory when there is a

MMI.

[Note] In the mobile NFC service lifespan, the MMI might be deleted from the end users mobilehandset. The Service Provider is responsible for the tolerance or not that his mobile NFC

service is used without the MMI on the mobile handset. In case the SP tolerates such use, it is

recommended to inform the end user that he cannot benefit from full capacity of his mobile

NFC service. If not, the SP should either launch the MMI installation or lock or delete the UICC

application.

2.6.3 UICC and UICC application architectureThe UICC application, also named application, is composed of one or several packages, one or

several instances and personalisation data hosted in the UICC as represented below. The drawing

below is an example of representation of all that is necessary on the UICC before the mobile NFC

service can be used.

ISD SP SSD

Package

Instance

Perso Data

Figure 14 Representation example of the UICC application

In Simple SD management mode, the MNO sends the CCM commands to the UICC upon request of

the Service Provider.

In the Delegated Management mode, the Service Provider sends the CCM commands to the UICC

after having been authorized by the MNO:

Before sending an OTA command, the SP requests a token from the MNO for each action

to be done on the UICC (package loading, application installation).

Once it has the tokens, the Service Provider is authorized by the MNO and sends OTA theGlobalPlatform commands to the UICC

The SP must notify the MNO of the status of the OTA actions and send the token receipts.


25/102


Three different scenarios are considered in these specifications for the UICC application

installation. For each scenario, the content of the UICC is represented before any OTA operation as

available in the end users mobile handset, therefore highlighting all the items that will need to be

installed OTA.

ISD SP SSD

PackageInstance

Or

ISD SP SSD

Package

Instance

FULLY PRELOADED

The SSD is created in factory. The application is loaded, instantiated and

extradited in factory. The personalisation can be done by the Service

Provider in factory. The following operations are to be done OTA:

If UICC application personalisation was not done in factory, it is

done by the SP

After the UICC application personalisation, only the activation of

the application remains to be done OTA on the end users UICC,

either by the MNO (upon SP request, Simple SD mode) or the SP

(upon MNO authorization, Delegated Management mode).

[Note] For this Fully preloaded scenario, the Service Provider onlyneeds to send an activation request to the MNO.

ISD

Package

SP SSD

or

ISD

Package

SP SSD

PARTIALLY OTA

In this scenario, the application is loaded in factory.The SSD may be

created in factory (as represented) or OTA (by the MNO). The following

operations are to be done OTA:

UICC application instantiation and extradition to the security

domain of the SP in simple SD are done by the MNO

UICC application instantiation in DM is done by the SP

UICC application personalisation is done by the SP

Mobile NFC service activation is done either by the MNO (Simple

SD) or the SP (DM)

ISD

Or

SP SSDISD

FULLY OTA

In this scenario, only the SSD may be created in factory; all operations

are performed OTA:

If necessary, the SSD may be created OTA by the MNO

Package loading, UICC application instantiation and extradition to

the security domain of the SP in simple SD are done by the MNO

UICC application instantiation in DM is done by the SP

UICC application personalisation is done by the SP

Mobile NFC service activation is done either by the MNO (Simple

SD) or the SP (DM)


26/102


2.6.4 Process 5 Mobile NFC UICC application installationFlowchart

The following flowcharts present the UICC application installation process:

-First in Simple SD modeo With the personalisation step before the activation step

o With the personalisation step after complete installation and activation

- Then, in Delegated Management mode

o With the personalisation step after complete installation and activation (A

personalisation step before the activation step is also possible but is not represented)

Installation

Process 5 Installation of UICC application Simple SD mode personnalisation

before activation


Yes

Install the mobile NFC

service on the UICC

Inform SP of

successful installation

Successful

installation?

Inform Service

Provider of failure

Inform end user of

failure

Application

personalisation

Activate the mobile NFCservice

Successful

activation?

Yes

NoInform Service

Provider of failure

Inform Service Provider of

successful activation

No

Request installation

Request applicationactivation

Initiate installation

Notify the MNO about the

personalisation completion

Proceed to next steps

Figure 15 Flowchart of process 5 Mobile NFC UICC application installation in Simple SD mode

personnalisation before activation


27/102


Figure 16 Flowchart of process 5 Mobile NFC UICC application installation in Simple SD mode

personnalisation after activation

Installation

Process 5 Installation of UICC application Delegated Management Mode

Service ProviderMobile Network

Operator

Application personalisation

Deliver, if authorized, the

token(s) to the Service

Provider

Request authorization(s)

from the MNO

[Note]The activation

step may be performed

before or after application

personnalisation

No

Install and activate the

mobile NFC service on the

UICC

Inform End user of

failure

Notify MNO about

failure

Successful installation &

activation?

Notify the MNO about theinstallation, personalisation

and send the receipts

Initiate installation


Figure 17 Flowchart of process 5 Mobile NFC UICC application installation in Delegated Management

mode

Description

In simple SD mode, the package is loaded OTA by the MNO: it is thus mandatory that the

application certified package(s) and the corresponding installation parameters are available on theMNOs platform before submitting requests for loading the package. The installation parameters

are pre validated by the MNO.

In both modes, the personalisation step may also occur after the activation.


28/102


2.6.5 Process 5 Update Mobile NFC UICC application updateFlowchart

The following flowcharts present the UICC application update process:

-First in Simple SD mode

- Then, in Delegated Management mode

Installation

Process 5 Update Update of UICC application Simple SD mode

Service ProviderEnd userMobile Network

Operator

Inform end user about temporary

service suspension

Delete application and

inform SP

Replace/renewal of NFC offer

(upon request of end user or

SP)

Initiates update of the mobile NFC

service by the Service Provider

After some leadtime, request

application deletion

Sign contract or

contract amendment is

necessary


application Simple SD mode

Process 3 - End user asks his MNO about

available mobile NFC services

Inform end user to contact

his MNO, specifying the

reason why he is not eligible

Eligible Sub-process A

MNO eligiblity

End user cannot

update UICC to

service

CompatibleNot compatible

Sub-process B

SP compatibility

Not eligible

Figure 18 Flowchart of process 5 Update Mobile NFC UICC application update in Simple SD mode


29/102


Installation

Process 5 Update Update of UICC application Delegated Management Mode

Service ProviderMobile Network

OperatorEnd user

Process 5 Installation of UICC applicationDelegated Management Mode

Process 3 - End user asks his MNOabout available mobile NFC services

Eligible

Not eligible

Sign contract or

contract amendment is

necessary

Deliver, if authorized, a

token to SP

Initiates update of the mobile NFCservice by the Service Provider

Replace/renewal of NFC offer

(upon request of end user or

SP)

Inform end user about temporary

service suspension

After some leadtime, request

application deletion authorization

Sub-process A

MNO eligiblity

Inform end user to contact

his MNO, specifying the

reason why he is not eligible

Delete application and send a

receipt to the MNO

CompatibleNot compatibleEnd user cannot

subscribe to service

Sub-process B

SP compatibility

Figure 19 Flowchart of process 5 Update Mobile NFC UICC application update in Delegated

Management mode

Description

This process is optional and allows the SP to update deployed UICC application OTA.

It applies in following circumstances:

- The end user replaces or updates his mobile NFC service requiring the installation of a new

NFC application,

-The Service Provider wants to update his NFC service or deploy a new service for one or all ofhis end users

It should be noted that:

- Since it is necessary to delete the existing application, the SP must first check the compatibility

of the end users mobile equipment with the new version of the service.

- The eligibility check after the MMI application deletion allows the SP to ensure that there is

enough memory space in the UICC for the new application.

- Optionally the end user might have to sign a new contract or contract amendment.

The installation process is otherwise similar to the one described in Process 5.

2.6.6 Process 6 Service Provider MMI installation / updateThis process is conditional. It is mandatory when a MMI is necessary for the mobile NFC service.


30/102


There are three ways to initiate this process:

- Case 1: Upon Service Provider request, the MNO launches the MMI installation or update,

- Case 2: the Service Provider launches the MMI installation or update.

-Case 3: the end user installs the MMI from an application store

In all cases, it is assumed that the MMI hosting is not under the responsibility of the MNO.

The MMI may be specific to each mobile handset model: the Service Provider is responsible for

keeping an up-to-date database of compatible handset models and the associated MMI

applications.

There might be several MMIs in a service, using the same UICC applications: in this case, should

several MMIs be installed, this process may be repeated as many times as necessary.

Case 1: flowchart

Installation

Process 6 Service Provider MMI installation/updateCase 1: Upon Service Providers request, MNO launches MMI installation/update

Service Provider MNOEnd user

MMI needs to be

installed

MMI needs to be

updated

Request MMI installation

Load MMI applicationYes

No (option ii)

Yes (option i)

No

Is a local synchro

mechanism ?

MMI installationaborted

MMI loaded

Accept MMI

download ?

Option i

Inform SP about

MMI loading

Wait for local

synchro install

notification

Installation mode

Trigger MMI loading on mobile

handset

Inform SP about

MMI triggering

Notify MNO about MMIinstallation/update


Option ii

MMI needs to be

re-installed

Option i

Figure 20 Flowchart of process 6 Service Provider MMI installation, case 1

Case 1: description

In this case, it is not the Service Provider, but the MNO who initiates the OTA connection with the

mobile handset, in order to load the MMI application on the end users mobile handset.

Depending on the agreement between the Service Provider and the MNO, there are two

possibilities:

i. The MNO manages the entire installation including retries if necessary.

The MNO informs the Service Provider once the MMI is actually loaded in the mobile handset.In case of connection interruption during the MMI loading, the MNO manages the retry policy.

In this situation, there is a local synchronisation mechanism in the mobile handset to ensure

the MMI download. This mechanism is an option that can be proposed by the MNO. It can only

be available on NFC mobile handsets sold by the MNOs implementing it.


31/102


ii. Or the MNO sends a WAP push SMS to the handset to establish a connection with the Service

Providers MMI server. In case of connection interruption during the MMI loading, the SP

manages the retry policy, by sending a new request to the MNO.

Case 2: flowchart

Installation

Process 6 Service Provider MMI installation/updateCase 2: Service Provider launches MMI installation/update


Load MMI application

Trigger MMI loading on

mobile handset

No

Accept MMI

download ?

MMI loaded

MMI installation

aborted

Yes

MMI needs to be

updated

MMI needs to be

installed

Notify MNO about

MMI installation/update



Case 2: description

In this case, the Service Provider is fully in charge of the MMI download and installation.

Several reasons might cause failure of the MMI download (network coverage loss, mobile handset

switched off, end user rejects or does not approve opt-in ). It is recommended to attempt several

consecutive times to download the MMI before considering that it has failed.

In case the MMI is never installed, the SP notifies the MNO and may:

- suppress the UICC application,

- inform the end user in case of installation failure.

Case 3: flowchart


32/102


Installation

Process 6 Service Provider MMI installation/updateCase 3: End user installs the MMI from an application store


End user installs the MMI on an

application store

MMI installation

End user launches the applicationThe MMI notifies the Service Provider

of the installation


Has the end user already

subscribed?

Yes

No


installation/update


installation/update

[Note]Once the end user has

subscribed, the SP must notify

the MNO about the MMI

installation status


Case 3: descriptionIn case 3, the end user directly installs his MMI from an application store.

MMI installation notification

In all cases, the SP must notify the MNO of the installation or update status: this is particularly

important for the MNO to have the correct information in order to deliver the best customer

service possible.

Thus, during the MMI installation process, the Service Provider must notify the MNO of the

following events:

- MMI installation completion

-Failure during MMI installation

- No MMI has been installed, because the MMI is already installed (no installation is needed)

- MMI update completion

- Failure MMI update

[Note] In some cases, the handset is able to notify the installation to the SP (see installationnotification in JAD files for instance); in absence of any such mechanism, the SP must build a

notification inside the MMI to be triggered at first launch.

MMI update

When the Service Provider needs to update the MMI on the end users mobile handset, the twoprocesses described above (case 1 and case 2) also apply.

For case 3, the standard update mechanisms used by the application store apply.


33/102


In case the Service Provider estimates that it is urgent and mandatory, ie critical, to update the

MMI for using the mobile NFC service, the Service Provider might decide to lock the service until

the MMI update is effective. The Service Provider is responsible for such a decision and must notify

the MNO.

2.6.7 Process 7 MMI and UICC application bindingFlowchart

MMI&UICC

appbinding

Process 7 MMI and UICC application binding

Mobile Network OperatorService ProviderEnd user

Request MMI and UICC

application bindingLoad required bindings

Binding successful?Inform end user of

failure


No

Yes

Figure 23 Flowchart of process 7MMI and UICC application binding

Description

This process is used during the installation process: the SP asks the MNO to bind the MMI and the

UICC application. The Service Provider should use this process when the UICC applications are

installed and active.This process is conditional since MMI and UICC application binding support is optional for the

MNO.

This binding adds further security to the MMI access to the UICC applications and could be

implemented using ACF files in the UICC for instance.

In case of MMI update, the Service Provider is responsible for explicitly requesting the update of

the bindings when it is necessary (in case a new version is provisioned on the MNO platform, or

when the MMI bears a new certificate). The MNO always loads the most recent bindings available

for this service version.

2.7 Life cycle processesThe following processes can be encountered during the use of a mobile NFC service. Their support

is mandatory to implement a mobile NFC service and ensure a consistent end users experience.

- Change UICC (Process 8)

- Change mobile phone number (Process 9)

- Change mobile handset (Process 10)

- Lost or stolen mobile equipment, end user contacts Mobile Network Operator (Process 11)

- Lost or stolen mobile equipment, end user contacts Service Provider (Process 12)

- Recover mobile equipment after a lost or theft (Process 13)

- Get a new mobile equipment after a lost of theft (Process 14)

- End User requests temporary mobile service suspension (Process 15)


34/102


- Change in contract ownership (Process 16)

- End user swaps Mobile Network Operator (Process 17)

2.7.1 Locking a mobile NFC serviceThe processes in this specification use several ways to lock a mobile NFC service. This could

happen following a theft, loss or in any other process that requires it.

The locks performed by the Mobile Network Operator are OTA locks. They can be of two kinds:

- Set the GlobalPlatform status of SD or the UICC application(s) to LOCKED

- Use a OTA command which blocks the contactless interface of the UICC

The locks performed by the Service Provider could be:

- OTA locks

o The SP sets the GlobalPlatform status of the UICC application(s) of the service to LOCKED

o If the UICC application(s) of the service has a built-in lock feature, the SP locks it by

sending it the appropriate OTA command (referred to as OTA applicative lock, for

instance with an EMV script processing command APPLICATION BLOCK)

- IS locks

o The SP blocks the use of the end users service in i ts Information Systems (IS). The SP is

then responsible for the corresponding lock policy: temporary or definitive lock, blacklist,

etc

[Note] There is no guaranty that an OTA lock can be successfully achieved since it requires that themobile handset be under mobile network coverage and switched on.

[Note] It is recommended that only the party which locked an application is in charge of unlocking itwhen necessary. Each party must thus clearly register in its Information System the

responsibility of each lock.

2.7.2 Suspended line and restricted lineIn some situations, the MNO suspends the end users line. But it can also be useful to only

restrict the line in some cases:

- When a users line is suspended, he cannot access at all the MNOs network and thus has no

access to any telecom service.

- When a users line is rest

Documents

AFSCM Interface Specification v. 2.1